Message notification method, device, apparatus and storage medium

Abstract

The application provides a message notification method and device, equipment and storage medium. It relates to the technical field of computers. The method comprises the following steps: in response to obtaining a first kafka message, obtaining a pre-configured data acquisition rule corresponding to a current link, the first kafka message being generated in response to a business application of a third-party platform, the first kafka message indicating the current link; acquiring message data from the data generated in the process of processing the business application according to the data acquisition rule; filling the message data into a configurable message template to generate a message carrying a notification message; and sending the message to the third-party platform to display the notification message in the third-party platform. The method of the application automatically generates and sends a message carrying a notification message to a third-party platform by pre-configuring a data acquisition rule and a message template, thereby improving user experience.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a message notification method, apparatus, device, and storage medium. Background Technology

[0002] With the development of the internet, banking services have begun to integrate with third-party platforms. Users can submit banking-related applications on these platforms, such as applying for a bank card, which the bank then processes. After submitting an application, users may need to monitor its progress, such as whether it has been approved. Therefore, the bank needs to update the third-party platform on the processing progress of each application in real time.

[0003] Currently, in order to enable banks to synchronize the processing progress of business applications with third-party platforms in real time, relevant personnel need to write software programs corresponding to this function based on information from the third-party platform, the information on business applications that the third-party platform can submit, and the business application processing flow. These software programs are then deployed at the bank's end. After the bank receives a business application from the third-party platform, it can run the software program to synchronize the processing progress of the business application with the third-party platform during the processing process.

[0004] However, if the information on which the software program is based changes, there may be situations where third-party platforms are unable to obtain information on the processing progress of business applications. Summary of the Invention

[0005] This application provides a message notification method, apparatus, device, and storage medium to solve the problem in the prior art where changes in the information on which the software program is based cause third-party platforms to be unable to obtain the processing progress of business applications.

[0006] In a first aspect, this application provides a message notification method, including: responding to the receipt of a first Kafka message, obtaining a pre-configured data acquisition rule corresponding to the current flow stage, wherein the first Kafka message is generated in response to a business application from a third-party platform when the process of processing the business application reaches a certain stage, and the first Kafka message indicates the current flow stage;

[0007] According to the data acquisition rules, message data is obtained from the data generated during the processing of the business application;

[0008] The message data is filled into a configurable message template to generate a message carrying a notification message;

[0009] The message is sent to the third-party platform to display the notification message on the third-party platform.

[0010] In one possible design, the data retrieval rules include multiple Structured Query Language (SQL) files.

[0011] According to the data acquisition rules, message data is obtained from the data generated during the processing of the service application, including:

[0012] Based on the query conditions of each of the multiple SQL files, the message data is obtained from the data generated during the processing of the business application.

[0013] In one possible design, the query conditions of the SQL file may include at least one of the following: order number, product code, or code of a third-party application.

[0014] In one possible design, the message template includes a first message template and / or a second message template, wherein the first message template is used to generate a notification message of the progress of the service application, and the second message template is used to generate a notification message of the processing result of the service application.

[0015] In one possible design, sending the message to the third-party platform to display the notification message on the third-party platform includes:

[0016] Based on the transaction identifier of the business application, the first message is sent to the third-party platform through the interface corresponding to the transaction identifier, so as to display a first notification message on the third-party platform. The first message is generated by filling data into the first message template. The first notification message is used to prompt the user that the business application has entered the current stage of the process.

[0017] In one possible design, sending the message to the third-party platform to display the notification message on the third-party platform includes:

[0018] Based on the transaction identifier of the business application, the second message is sent to the third-party platform through the interface corresponding to the transaction identifier, so as to display a second notification message on the third-party platform. The second message is generated by filling data into the second message template. The second notification message is used to prompt the user that the business application has passed the review of the current stage.

[0019] In one possible design, the response, before receiving the first Kafka message, includes:

[0020] In response to receiving the second Kafka message, it is determined whether the third-party platform needs to send a message notification. The second Kafka message is generated upon receiving a business application from the third-party platform.

[0021] After obtaining the first Kafka message, the process includes:

[0022] Based on the first Kafka message, determine whether the current flow stage is configured with data acquisition rules, the transaction identifier of the business application, and the message template;

[0023] If configured, the data acquisition rules of the current process, the transaction identifier of the business application, and the message template are obtained.

[0024] In one possible design, the method further includes: generating a transmission record of the message, the transmission record including the content of the message, the transmission time of the message, and whether the message was successfully transmitted; for messages that fail to be transmitted, sending the message that failed to be transmitted to the third-party platform at a preset time, wherein the interval between the preset time and the transmission time of the message that failed to be transmitted is greater than or equal to a preset value.

[0025] In one possible design, the method further includes: receiving configuration information of the third-party platform input by the user, the configuration information including data acquisition rules for each of the multiple stages of the business application, transaction identifier of the business application, and message template; the number of message templates is greater than or equal to the number of stages of the business application.

[0026] Secondly, this application provides a message notification device, including: an acquisition module, used to respond to the acquisition of a first Kafka message, acquire the pre-configured data acquisition rules corresponding to the current flow stage, wherein the first Kafka message is generated when the process of processing the business application of a third-party platform flows to a stage, and the first Kafka message indicates the current flow stage;

[0027] The acquisition module is also used to acquire message data from the data generated during the processing of the business application, according to the data acquisition rules.

[0028] The processing module is used to fill the message data into a configurable message template to generate a message carrying a notification message;

[0029] The sending module is used to send the message to the third-party platform so as to display the notification message on the third-party platform.

[0030] Thirdly, embodiments of this application provide an electronic device, including: at least one processor and a memory; the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored in the memory, causing the at least one processor to perform the message notification method as described in the first aspect and various possible designs of the first aspect.

[0031] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions. When a processor executes the computer-executable instructions, it implements the message notification method described in the first aspect and various possible designs of the first aspect.

[0032] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the message notification method described in the first aspect and various possible designs of the first aspect.

[0033] The message notification method, apparatus, device, and storage medium provided in this application obtain a first Kafka message in response to receive the first Kafka message. This first Kafka message, generated during the processing of a business application from a third-party platform, indicates the current processing stage. Based on the data acquisition rules, message data is retrieved from the data generated during the processing of the business application. The message data is then filled into a configurable message template to generate a message carrying a notification message. Finally, the message is sent to the third-party platform for display. Because data acquisition rules and message templates are pre-configured for multiple stages of the third-party platform's business application, no software programming is required for the third-party platform. Even when the information on the third-party platform changes, the electronic device can still automatically retrieve the corresponding data according to the data acquisition rules, fill the data into the message template to generate a message carrying a notification message, and still display the notification message on the third-party application platform. Therefore, the message notification method provided in this application effectively improves the problem of third-party platforms being unable to obtain the processing progress of business applications due to changes in the information upon which the software program is based. Attached Figure Description

[0034] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0035] Figure 1 This is a schematic diagram illustrating an application scenario of a message notification method provided in an embodiment of this application.

[0036] Figure 2A flowchart illustrating the message notification method provided in this application embodiment;

[0037] Figure 3 A schematic diagram of an interface for displaying a first notification message on a third-party platform, provided as an embodiment of this application;

[0038] Figure 4 A schematic diagram of an interface for displaying a second notification message on a third-party platform, provided as an embodiment of this application;

[0039] Figure 5 This is a schematic flowchart of another message notification method provided in an embodiment of this application;

[0040] Figure 6 A flowchart illustrating another message notification method provided in an embodiment of this application;

[0041] Figure 7 A schematic diagram of the structure of the message notification device provided in the embodiments of this application;

[0042] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0043] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0044] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0045] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0046] Application Acceptance: This refers to the process by which a user submits supporting documents to a bank through a third-party platform when applying for a certain service, such as a special installment plan. The supporting documents may include personal application information and corresponding image data.

[0047] Cross-checking: refers to a series of compliance checks conducted by the bank on the supporting documents submitted by the user.

[0048] Rating: This refers to the comprehensive evaluation that banks give to users who submit applications by querying their credit information.

[0049] Credit reporting: including manual credit reporting and automatic credit reporting, refers to the process by which banks verify the application information of users who submit applications.

[0050] Approval: This includes manual approval and automatic approval. It refers to the process by which the bank analyzes the creditworthiness of the user who submits the application and gives the final approval result and credit limit.

[0051] File creation: Establishing information records such as card, account, and customer information for users. When a business application is for a specific installment application, a special installment credit card can be issued to the user.

[0052] Request for Funds: The user applies for the approved credit limit and submits relevant supporting documents.

[0053] Credit Limit Adjustment: Adjust the credit limit of the special installment card based on the amount requested.

[0054] Loan disbursement: Deduct the special installment credit card limit and transfer the funds to the merchant's or customer's designated account.

[0055] Users can submit banking applications through an application installed on their terminal device. This application can be either developed by the bank itself or provided by a third-party platform. For example, Bank A may have its own application, A, through which users can conduct transactions such as fund transfers. Users can also use application B, provided by a third-party platform, to open credit cards and perform other banking services.

[0056] When a user submits a business application through a third-party platform, the bank can process the application. For example, if a user submits a credit card application through a third-party platform, the bank can receive the user's card application information and, through multiple approval processes, activate the credit card for the user.

[0057] During the processing of business applications, banks can synchronize the processing progress of business applications with third-party platforms, allowing users to track the progress of their submitted applications on these platforms.

[0058] In some implementations, banks batch process business applications submitted by users through third-party platforms. For example, they process user-submitted business applications in batches every few days or every few hours. Once the bank has finished processing the business application, it sends the processing result to the third-party platform, allowing the platform to display a notification message about the processing result.

[0059] However, processing business applications in batch mode and returning the results to the third-party platform cannot synchronize the processing progress of business applications with the third-party platform in real time. As a result, users cannot know the progress of their business applications in real time, leading to a poor user experience.

[0060] In other implementations, relevant personnel can develop corresponding software programs based on information from third-party platforms, the business applications that can be submitted through these platforms, and the processing flow of those applications. These software programs can synchronize the progress of business applications with the third-party platforms and are then deployed at the bank's end. In this way, when the bank receives a business application submitted by a user through a third-party platform, the bank can run the pre-deployed software program to synchronize the processing progress of the business application with the third-party platform.

[0061] However, in the above implementation, the software program is written by relevant personnel based on information from the third-party platform, the information on business applications that can be submitted by the third-party platform, and the processing flow of business applications. When the third-party platform updates its version, the information on which the software program is based changes. If the relevant personnel do not update the software program in a timely manner, the bank may not be able to synchronize the processing progress of business applications to the third-party platform, and users will not be able to view the progress of business applications on the third-party platform, resulting in a poor user experience.

[0062] To address the aforementioned technical issues, this application provides a message notification method. Relevant personnel can pre-configure data acquisition rules and message templates for business applications submitted to third-party platforms. The data acquisition rules can be used to extract data from the large amounts of data generated during business application processing, synchronizing the processing progress of the business application with the third-party platform. In this way, the bank can automatically obtain the necessary data according to the data acquisition rules and populate the data into the message template, generating a message carrying a notification message. This allows the third-party platform to display the corresponding notification message upon receiving the message. Relevant personnel do not need to write software programs based on information from third-party platforms, effectively improving the problem of third-party platforms being unable to obtain the processing progress of business applications due to changes in the information upon which the software program is based, thus enhancing the user experience.

[0063] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0064] Figure 1 This is a schematic diagram illustrating an application scenario of a message notification method provided in an embodiment of this application. For example...Figure 1 As shown, in the first instance, a user can submit a business application through a third-party platform (an application installed on the terminal device) on their terminal device. The bank's electronic device can receive the application, process it, and perform cross-checks. Cross-checks may include scoring, credit investigation, approval, and record keeping. For example, when a user submits a specific installment application, the bank performs scoring, credit investigation, and approval. If all submitted materials are approved, the bank can issue a specific installment credit card to the user and process payment requests and credit limit adjustments. Therefore, the processing of business applications submitted by users through third-party platforms by the bank's electronic device can include multiple stages. The number of stages may be the same or different for different business applications, and this embodiment does not limit this.

[0065] For example, when an electronic device processes (or approves) a business application at a certain stage, the electronic device can obtain the corresponding data from the large amount of data generated during the processing of the business application according to the data acquisition rules of the current stage, and fill the obtained data into the message template to generate a message carrying a notification message.

[0066] Secondly, the electronic device can send the message to a third-party platform, causing the platform to display a notification. This allows the electronic device to synchronize the processing progress of the application with the third-party platform in real time, enabling users to stay informed about the status of their submitted applications and improving user experience.

[0067] based on Figure 1 As shown in the application scenario, this application embodiment also provides a message notification method. Figure 2 This is a flowchart illustrating the message notification method provided in an embodiment of this application. Figure 2 As shown, the message notification method includes:

[0068] S201. The electronic device responds by receiving the first Kafka message and obtains the pre-configured data acquisition rules corresponding to the current stage of the process.

[0069] The first Kafka message is generated when the application is processed in response to a business request from a third-party platform. It indicates the current stage of the process.

[0070] The third-party platform can be any application other than the bank's application. The number of third-party platforms can be one or more, and this application embodiment does not limit this.

[0071] For example, the entity executing the method in the embodiments of this application may be... Figure 1The diagram shows an electronic device used by a bank to process business applications. This electronic device can be a single device or a cluster. Therefore, the first Kafka message received by the electronic device can be generated by that device itself, or it can be generated and sent to it by other electronic devices. This embodiment does not limit this.

[0072] For example, an electronic device may store multiple pre-configured data acquisition rules. Different data acquisition rules may correspond to different stages of the same business application or different business applications. This application embodiment does not limit this.

[0073] For example, an electronic device can obtain the data acquisition rule corresponding to the current stage of the flow from multiple data acquisition rules based on the information of the current stage. The information of the current stage of the flow can be information such as the identifier of the current stage, which is not specifically limited in this embodiment.

[0074] S202. The electronic device obtains message data from the data generated during the processing of business applications according to the data acquisition rules.

[0075] Electronic devices can obtain the data needed to generate messages at the current stage of the process according to data acquisition rules. For example, electronic devices can obtain message data such as the identifier or transaction number of the current stage according to data acquisition rules. As another example, when the business application is a special installment application, electronic devices can obtain message data such as order number, loan disbursement number, special dispute application type number, brand number, application processing code number, application processing status code, product code, channel number, and third-party platform identifier according to data acquisition rules.

[0076] S203. The electronic device fills the message data into the configurable message template to generate a message carrying a notification message.

[0077] For example, the configurable message template is the message template corresponding to the current stage of the process. The notification message can be the processing progress of the current stage of the business application, such as a notification message that the business application is in the current stage, or a notification message that the approval of the current stage has been completed or passed. This application embodiment does not specifically limit the notification message.

[0078] Electronic devices can dynamically populate message data into configurable message templates to generate messages carrying notification messages.

[0079] It should be noted that during the processing of the current flow stage, the electronic device can generate one or more messages carrying notification messages, and the data in each message is different. This application embodiment does not limit the number and content of the messages carrying notification messages generated by the electronic device in a stage.

[0080] S204. The electronic device sends a message to a third-party platform to display a notification message on the third-party platform.

[0081] For example, an electronic device can send a message to a server of a third-party platform, and the third-party server can display the corresponding notification message on the third-party platform based on the message.

[0082] In this embodiment, by pre-setting data acquisition rules and configurable message templates, the electronic device can automatically retrieve the necessary data from the data generated during the processing of business applications and fill the retrieved data into the message template to generate a message carrying a notification message. This eliminates the need for personnel to write software templates based on information from third-party platforms. Thus, even if the information on the third-party platform changes, the electronic device can still generate a message carrying a notification message, and the third-party platform can still display the notification message, improving the user experience.

[0083] For example, the data acquisition rules obtained by the electronic device may include multiple SQL files. The electronic device can obtain message data from the data generated by processing business applications based on the query conditions of each SQL file.

[0084] When processing business applications, electronic devices can generate multiple data lists, each containing slightly different data. When acquiring message data, the electronic device can query and retrieve the required data from these multiple data lists based on the query conditions of each SQL file. For example, based on the query conditions of one SQL file, it can query and retrieve the special installment application type code from data list A, and based on the query conditions of another SQL file, it can query and retrieve the loan disbursement number from data list B.

[0085] In this way, electronic devices can accurately obtain the message data required for the current stage of the process, so as to generate message templates.

[0086] For example, the query conditions of an SQL file may include at least one of the following: order number, product code, or code of a third-party application.

[0087] It should be noted that the query conditions of the SQL file may also include other information; the embodiments in this application are only illustrated using the above example.

[0088] In this way, electronic devices can acquire all the necessary data without the need to write corresponding software programs.

[0089] In this embodiment of the application, the current stage of the business application process may include one or more message templates. For example, the message templates may include a first message template and / or a second message template. The first message template is used to generate a notification message about the progress of the business application, and the second message template is used to generate a notification message about the processing result of the business application.

[0090] In this way, third-party platforms can display notification messages about the progress of business applications and / or the processing results of business applications, allowing users to understand the processing progress of business applications in real time and improving user experience.

[0091] The following sections will explain the cases where the message template includes the first message template and the cases where the message template includes the second message template.

[0092] For example, when the message template includes a first message template, when the electronic device fills the acquired message data into the first message template, the electronic device can send the first message to a third-party platform through the interface corresponding to the transaction identifier of the business application, so as to display the first notification message on the third-party platform. The first message is generated after the data is filled into the first message template, and the first notification message is used to prompt the user that the business application has entered the current stage of the process.

[0093] Understandably, electronic devices can send the first message to the server of a third-party platform through the interface corresponding to the transaction identifier in the business application. The server of the third-party platform then displays the first notification message.

[0094] For example, the interface on a third-party platform that displays the first notification message can be found here. Figure 3 As shown, Figure 3 This is a schematic diagram of an interface for displaying a first notification message on a third-party platform, provided as an embodiment of this application.

[0095] This allows third-party platforms to display business notifications indicating the current stage of a business application's processing. Users can then view these notifications to understand the current stage of the application's processing, thus improving the user experience.

[0096] For example, when the message template includes a second message template, when the electronic device fills the acquired message data into the second message template, the electronic device can send the second message to a third-party platform through the interface corresponding to the transaction identifier of the business application, so as to display the second notification message on the third-party platform. The second message is generated after the data is filled into the second message template, and the second notification message is used to prompt the user that the business application has passed the review of the current stage.

[0097] Understandably, electronic devices can send a second message to the server of a third-party platform through the interface corresponding to the transaction identifier in the business application. The server of the third-party platform then displays the second notification message.

[0098] For example, the interface for a third-party platform to display the second notification message can be found here. Figure 4 As shown, Figure 4 This is a schematic diagram of an interface for displaying a second notification message on a third-party platform, provided as an embodiment of this application.

[0099] It should be noted that a business application may also fail the review at the current stage of the process. When a business application fails the review at the current stage of the process, the electronic device can send a message with a notification message of failure to the third-party platform. This will cause the third-party platform to display the notification message of failure to the current stage of the process, so that the user can modify the application information and resubmit the business application.

[0100] This allows third-party platforms to display notifications that a business application has passed the current stage of review. Users can see this notification and know that their application has passed the current stage of review and may proceed to the next stage, thus improving the user experience.

[0101] Based on the above embodiments, relevant personnel can pre-configure configuration information for sending notification messages to third-party platforms.

[0102] For example, an electronic device can receive configuration information from a third-party platform input by the user. This configuration information includes data acquisition rules for each stage of the business application process, the transaction identifier for the business application, and message templates. The number of message templates is greater than or equal to the number of stages in the business application process.

[0103] The transaction identifier in the business application can be used to determine the interface for data transmission between the electronic device and the third-party platform. The transaction identifier can be a code set by relevant personnel based on the characteristics of the third-party platform, such as the name of the third-party platform, and is unrelated to information such as the version of the third-party platform. Thus, changes to the information of the third-party platform will not affect the message notification method in this application's embodiments.

[0104] In this way, relevant personnel do not need to write corresponding software programs for third-party platforms, which can effectively improve the situation where it is impossible to send message notifications to third-party platforms due to changes in information on the third-party platforms, thus improving the user experience.

[0105] Based on the above embodiments, after receiving a business application, the bank's electronic device can process it. By using Kafka messages, the message notification processing flow can be decoupled from the business application processing flow, ensuring that the two flows do not interfere with each other. Furthermore, the two flows can be executed by the same device or by different devices. The following description, using the example of the same device executing both flows, illustrates the process from receiving a business application to sending a message carrying a notification message.

[0106] Figure 5 This is a schematic flowchart illustrating another message notification method provided in an embodiment of this application. Figure 5 As shown, the process by which an electronic device receives a service request and sends a message carrying a notification message may include the following steps:

[0107] S501. The electronic device receives a service application submitted by the user through a third-party platform.

[0108] Business applications can include a variety of types, and this application embodiment does not impose specific limitations.

[0109] S502, The electronic device generates a second Kafka message.

[0110] S503: The electronic device responds to the second Kafka message it receives and determines whether the third-party platform needs to send a message notification.

[0111] For example, an electronic device can determine whether a third-party platform needs to send a message notification by detecting whether a configuration file for sending message notifications to the third-party platform is stored. If so, it can be determined that the third-party platform needs to send a message notification, and step S504 can be executed. If not, it can be determined that the third-party platform does not need to send a message notification, and step S508 can be executed.

[0112] S504, the electronic device generates a third Kafka message.

[0113] The third Kafka message is generated when the electronic device enters the first stage of processing the business request.

[0114] S505: Upon receiving the third Kafka message, the electronic device determines whether the first step of the business application is configured with data acquisition rules, the transaction identifier of the business application, and the message template.

[0115] The electronic device can sequentially determine whether the first step is configured with data acquisition rules, transaction identifier of business application, and message template, or it can simultaneously determine whether the first step is configured with data acquisition rules, transaction identifier of business application, and message template. This application embodiment does not limit this.

[0116] For example, when the electronic device sequentially determines whether the first step is configured with data acquisition rules, a transaction identifier for a service application, and a message template, if the electronic device determines that no data acquisition rules are configured in the first step, it can execute the following step S508, without performing other configuration file checks, and determine that the first step does not need to send a message notification. If the electronic device determines that the first step is configured with data acquisition rules, a transaction identifier for a service application, and a message template, it can execute the following step S506.

[0117] It should be noted that during the process of electronic devices processing business applications, a Kafka message can be generated at each stage. The electronic devices determine whether a message notification is required at that stage based on the Kafka message.

[0118] This decouples the various stages of business processing from the process of sending notification messages, reducing the impact of the notification message sending process on the processing flow.

[0119] S506, Data acquisition rules for the first stage of electronic equipment obtaining service applications, transaction identifiers for service applications, and message templates.

[0120] For example, an electronic device can obtain the data acquisition rules, transaction identifiers, and message templates for the first stage from a large number of data acquisition rules, transaction identifiers for business applications, and message templates, based on the identifier of the first stage. For example, the identifier of the first stage can be "third-party platform A, stage 1", or an identifier composed of other information, which is not limited in this embodiment.

[0121] S507. The electronic device generates a message carrying a notification message based on the data acquisition rules of the first stage, the transaction identifier of the business application, and the message template, and sends the message to a third-party platform to display the notification message on the third-party platform.

[0122] For example, the method for generating and sending messages by an electronic device can be found in the above embodiments, and will not be repeated here in the embodiments of this application.

[0123] Understandably, when a business application moves to the second stage, the electronic device can execute the above steps S504-S507, so that a notification message on the processing progress of the business application is displayed on the third-party platform.

[0124] S508, End.

[0125] In this embodiment of the application, the electronic device can generate a message transmission record, which may include information such as the message content, the message transmission time, and whether the message was successfully transmitted.

[0126] For messages that fail to be sent, the electronic device can send the failed message to a third-party platform at a preset time. The interval between the preset time and the time when the failed message is sent is greater than or equal to a preset value.

[0127] The preset value can be 10 minutes or 30 minutes, or other times can be obtained. This application embodiment does not limit this.

[0128] It should be noted that when relevant personnel need to check the sending status of notification messages, they can do so by querying the records.

[0129] This improves the situation where third-party platforms cannot promptly notify users of messages due to message transmission failures, thus enhancing the user experience.

[0130] To facilitate understanding of the message notification method described in the above embodiments, the process of an electronic device sending notification messages will be described in detail below. Figure 6 This is a flowchart illustrating another message notification method provided in an embodiment of this application.

[0131] like Figure 6 As shown, the message notification method may include the following steps:

[0132] S601, Begin.

[0133] For example, this step may include an electronic device receiving a service request submitted by a user through a third-party platform.

[0134] S602. Determine if the scenario is configured.

[0135] A scenario can refer to a third-party platform; one third-party platform constitutes one scenario.

[0136] To determine whether a scenario is configured, i.e. whether a third-party platform needs to send a message notification, please refer to the above embodiments. This application will not repeat the details here.

[0137] If the scenario is configured, proceed to step S603 below; if the scenario is not configured, proceed to step S614 below.

[0138] S603, Configuration Acquisition Steps.

[0139] The configuration retrieval step can include retrieving the Kafka message from the current stage of the process and information such as which stage it is currently in.

[0140] S604. Determine whether the process is configured.

[0141] The determination of whether a process is configured, i.e. whether the current process needs to be notified, can be referred to the above embodiments, and will not be repeated here.

[0142] If the component is configured, proceed to step S605 below; if the component is not configured, proceed to step S614 below.

[0143] S605. Determine whether the outbound call transaction identity document (ID) is configured.

[0144] The outbound call transaction ID can be the transaction identifier described in the above embodiments.

[0145] Determining whether an outbound call transaction ID is configured, i.e., determining whether the corresponding outbound call transaction ID is stored in the electronic device at the current stage of the process, can be referred to the above embodiments, and will not be repeated here in the embodiments of this application.

[0146] If the electronic device stores the corresponding outbound call transaction ID, it means that an outbound call transaction ID has been configured, and the following step S607 is executed. If the electronic device does not store the corresponding outbound call transaction ID, it means that an outbound call transaction ID has not been configured, and the following step S614 is executed.

[0147] S606, Obtain the outbound call transaction ID.

[0148] S607. Determine if the transaction message is configured.

[0149] The transaction message configuration can be the message template described in the above embodiments. Determining whether a transaction message is configured, i.e., determining whether the electronic device stores the corresponding transaction message at the current stage of the process, can be found in the above embodiments; this application will not repeat the details here.

[0150] If the electronic device stores the corresponding transaction message, it indicates that the transaction message is configured, and the following step S609 is executed. If the electronic device does not store the corresponding transaction message, it indicates that the transaction message is not configured, and the following step S614 is executed.

[0151] S608, Obtain transaction message configuration.

[0152] S609. Determine if SQL is configured.

[0153] The SQL can be the SQL file in the data acquisition rules described in the above embodiments.

[0154] Determining whether SQL is configured, i.e., determining whether the corresponding SQL is stored in the electronic device at the current stage of the process, can be found in the above embodiments, and will not be repeated here.

[0155] If the electronic device stores the corresponding SQL, it means that the SQL is configured, and the following step S607 is executed. If the electronic device does not store the corresponding SQL, it means that the SQL is not configured, and the following step S614 is executed.

[0156] S610, Get Configuration SQL.

[0157] S611, Execute SQL to retrieve data.

[0158] This step corresponds to the process of obtaining message data according to the data acquisition rules described in the above embodiments, and will not be repeated here.

[0159] For example, the information obtained can be seen in Table 1 below:

[0160] Table 1

[0161]

[0162] S612, Copy data to the requesting entity.

[0163] This step corresponds to the process of filling message data into the message template as described in the above embodiments, and will not be repeated here.

[0164] S613, Read message configuration and send request.

[0165] The request can be the message described in the above embodiments.

[0166] This step corresponds to the process described in the above embodiments of sending a message carrying a notification message to a third-party platform.

[0167] The message reading configuration allows you to read the transaction identifier of the business application from the message, determine the interface to send the request based on the transaction identifier, and send the request to a third-party platform through the interface to display the notification message on the third-party platform.

[0168] S614, End.

[0169] In summary, the message notification method provided in this application can determine key issues such as whether data needs to be sent, what data needs to be sent, and how to obtain the data by reading the configuration, thus reducing code development. Only configuration is required to add or remove third-party platforms, with granularity down to each processing step and specific content to be sent. Subsequent configuration is all that's needed to achieve the effect of loading notifications from third-party platforms.

[0170] Figure 7 This is a schematic diagram of the structure of a message notification device provided in an embodiment of this application. Figure 7 As shown, the message notification device includes: an acquisition module 701, a processing module 702, a sending module 703, and a judgment module 704;

[0171] The acquisition module 701 is used to respond to the acquisition of the first Kafka message and acquire the pre-configured data acquisition rules corresponding to the current flow stage. The first Kafka message is generated when the data flows to a stage in response to the business application of the third-party platform. The first Kafka message indicates the current flow stage.

[0172] The acquisition module 701 is also used to acquire message data from the data generated by the notification service application according to the data acquisition rules.

[0173] The processing module 702 is used to fill message data into a configurable message template to generate a message carrying a notification message.

[0174] The sending module 703 is used to send message notification messages to a third-party platform so that the notification messages can be displayed on the third-party platform.

[0175] In some embodiments, the data acquisition rules include multiple SQL files, and the processing module 702 is specifically used to acquire message data from the data generated during the processing of business applications based on the query conditions of each of the multiple SQL files.

[0176] In some embodiments, the query conditions of the SQL file may include at least one of the following: order number, product code, or code of a third-party application.

[0177] In some embodiments, the message template includes a first message template and / or a second message template, wherein the first message template is used to generate a notification message of the progress of the service application, and the second message template is used to generate a notification message of the processing result of the service application.

[0178] In some embodiments, the sending module 703 is specifically used to send a first message to a third-party platform through an interface corresponding to the transaction identifier of the business application, so as to display a first notification message on the third-party platform. The first message is generated after filling the first message template with data. The first notification message is used to prompt the user that the business application has entered the current stage of the process.

[0179] In some embodiments, the sending module 703 is specifically used to send a second message to a third-party platform through an interface corresponding to the transaction identifier of the business application, so as to display a second notification message on the third-party platform. The second message is generated after filling data into the second message template. The second notification message is used to prompt the user that the business application has passed the review of the current stage of the process.

[0180] In some embodiments, the message notification device further includes a judgment module 704, which is used to determine whether the third-party platform needs to send a message notification in response to the obtained second Kafka message. The second Kafka message is generated upon receiving a business application from the third-party platform.

[0181] The judgment module 704 is also used to determine, based on the first Kafka message, whether the current flow stage is configured with data acquisition rules, business application transaction identifiers, and message templates.

[0182] The acquisition module 701 is specifically used to acquire the data acquisition rules, transaction identifier of business application, and message template of the currently flowing stage if the current stage is configured with data acquisition rules, transaction identifier of business application, and message template.

[0183] In some embodiments, the processing module 702 is further configured to generate a message transmission record, the transmission record including the message content, the message transmission time, and whether the message was successfully transmitted.

[0184] The processing module 702 is also used to send the failed transmission message to a third-party platform at a preset time, wherein the interval between the preset time and the transmission time of the failed transmission message is greater than or equal to a preset value.

[0185] In some embodiments, the processing module 702 is further configured to receive configuration information of a third-party platform input by the user. The configuration information includes data acquisition rules for each stage of the multiple stages of the business application, transaction identifiers of the business application, and message templates; the number of message templates is greater than or equal to the number of stages of the business application.

[0186] The message notification device provided in this application embodiment can be used to execute the technical solution of the message notification method in the above embodiment. Its implementation principle and technical effect are similar, and will not be described again here.

[0187] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware. For example, processing module 702 can be a separate processing element, or it can be integrated into a chip in the above device. Alternatively, it can be stored as program code in the memory of the above device, and its functions can be called and executed by a processing element of the device. The implementation of other modules is similar. Moreover, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed through the integrated logic circuits in the hardware of the processor element or through software instructions.

[0188] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 8 As shown, the electronic device may include: a transceiver 801, a processor 802, and a memory 803.

[0189] Processor 802 executes computer execution instructions stored in memory, causing processor 802 to perform the scheme in the above embodiments. Processor 802 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0190] The memory 803 is connected to the processor 802 via the system bus and completes communication between them. The memory 83 is used to store computer program instructions.

[0191] Transceiver 801 can be used to obtain the task to be run and its configuration information.

[0192] The system bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The system bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus. Transceivers are used to enable communication between database access devices and other computers (e.g., clients, read-write libraries, and read-only libraries). Memory may include random access memory (RAM) and may also include non-volatile memory.

[0193] The electronic device provided in this application embodiment can be the terminal device described in the above embodiments.

[0194] This application also provides a chip for executing instructions, which is used to execute the message notification method described in the above embodiments.

[0195] This application also provides a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to perform the message notification method described in the above embodiments.

[0196] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solution of the message notification method in the above embodiments.

[0197] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0198] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.

[0199] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.

[0200] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0201] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0202] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk or optical disc, etc.

[0203] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0204] The aforementioned storage medium can be implemented from any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium can be any available medium accessible to general-purpose or special-purpose computers.

[0205] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. The processor and storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic control unit or main control device.

[0206] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0207] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0208] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A message notification method, characterized in that, include: Receive business applications submitted from third-party platforms; Generate a second Kafka message; In response to the second Kafka message, check whether a configuration file for sending message notifications to the third-party platform is stored, and determine whether the third-party platform needs to send message notifications. If so, when the processing of the business application reaches a certain stage, a first Kafka message is generated, and the first Kafka message indicates the current stage to which the process has been completed. In response to the first Kafka message, determine whether the current flow stage is configured with data acquisition rules, the transaction identifier of the business application, and the message template; If configured, the pre-configured data acquisition rules corresponding to the current flow stage, the transaction identifier of the business application, and the message template are obtained. Based on the data acquisition rules, message data is obtained from the data generated during the processing of the business application. The message data is filled into a configurable message template to generate a message carrying a notification message; Based on the transaction identifier of the business application, the message is sent to the third-party platform through the interface corresponding to the transaction identifier, so as to display the notification message on the third-party platform.

2. The method according to claim 1, characterized in that, The data acquisition rules include multiple Structured Query Language (SQL) files. According to the data acquisition rules, message data is obtained from the data generated during the processing of the service application, including: Based on the query conditions of each of the multiple SQL files, the message data is obtained from the data generated during the processing of the business application.

3. The method according to claim 2, characterized in that, The query conditions of the SQL file may include at least one of the following: order number, product code, or code of a third-party application.

4. The method according to claim 2, characterized in that, The message template includes a first message template and / or a second message template. The first message template is used to generate a notification message about the progress of the service application, and the second message template is used to generate a notification message about the processing result of the service application.

5. The method according to claim 4, characterized in that, Sending the message to the third-party platform to display the notification message on the third-party platform includes: Based on the transaction identifier of the business application, the first message is sent to the third-party platform through the interface corresponding to the transaction identifier, so as to display a first notification message on the third-party platform. The first message is generated by filling data into the first message template. The first notification message is used to prompt the user that the business application has entered the current stage of the process.

6. The method according to claim 4, characterized in that, Sending the message to the third-party platform to display the notification message on the third-party platform includes: Based on the transaction identifier of the business application, the second message is sent to the third-party platform through the interface corresponding to the transaction identifier, so as to display a second notification message on the third-party platform. The second message is generated by filling data into the second message template. The second notification message is used to prompt the user that the business application has passed the review of the current stage.

7. The method according to claim 1, characterized in that, The method further includes: Generate a transmission record for the message, the transmission record including the content of the message, the transmission time of the message, and whether the message was successfully transmitted; For messages that fail to be sent, the message is sent to the third-party platform at a preset time, and the interval between the preset time and the time when the message was sent is greater than or equal to a preset value.

8. The method according to claim 1, characterized in that, The method further includes: The system receives configuration information from the third-party platform input by the user. The configuration information includes data acquisition rules for each stage of the business application, the transaction identifier of the business application, and message templates. The number of message templates is greater than or equal to the number of stages of the business application.

9. A message notification device, characterized in that, include: The judgment module, in response to the second Kafka message, checks whether a configuration file for sending message notifications to third-party platforms is stored, and determines whether the third-party platform needs to send message notifications. The second Kafka message is generated when the business application of the third-party platform is received. In response to the first Kafka message, determine whether the current flow stage is configured with data acquisition rules, transaction identifiers for business applications, and message templates. The first Kafka message is generated when the process of processing the business application of the third-party platform flows to a certain stage, and the first Kafka message indicates the current flow stage. The acquisition module is used to acquire the pre-configured data acquisition rules, the transaction identifier of the business application, and the message template corresponding to the current flow stage if the current flow stage is configured with data acquisition rules, the transaction identifier of the business application, and the message template. The acquisition module is also used to acquire message data from the data generated during the processing of the business application, according to the data acquisition rules. The processing module is used to fill the message data into a configurable message template to generate a message carrying a notification message; The sending module is used to send the message to the third-party platform through the interface corresponding to the transaction identifier of the business application, so as to display the notification message on the third-party platform.

10. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-8.

12. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-8.

Images