Service shortcut phrase message pushing method and related device

Through the background system querying business information and generating message messages in a unified format, the problem of inconvenient communication between business messages between different systems is solved, and efficient and secure cross-system communication is achieved.

CN119603258AActive Publication Date: 2025-03-11AGRICULTURAL BANK OF CHINA
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
CN202411743545.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-30
Publication Date
2025-03-11
Estimated Expiration
2044-11-30

AI Technical Summary

Technical Problem

The existing technology does not support business message communication between different systems, resulting in inconvenient communication across systems and low communication efficiency.

Method used

Through the backend system, we query and obtain business information for the tasks to be communicated, and query the message parameter configuration, message access rule configuration and element rule configuration based on the business information, generate a unified format message message, and push it to the front-end outlet system through the message interaction center.

Benefits of technology

It realizes the unification of message packet formats between different background systems, facilitates cross-system communication, improves communication efficiency, and ensures the security of communication through automatic checksum generation of message packets of shortcut phrases.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119603258A_ABST
    Figure CN119603258A_ABST
Patent Text Reader

Abstract

The invention discloses a service shortcut phrase message pushing method and a related device, and the method comprises the steps: querying and obtaining corresponding service information for a to-be-communicated task through a background system; the background system inquires corresponding message parameter configuration, message access rule configuration and element rule configuration according to the service information; the background system checks and generates information messages in a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, and the information messages generated by different background systems are unified into the first format; and the background system pushes the information message to a foreground website system through a message interaction center. Therefore, the format of the information message can be unified, cross-system communication among different systems is facilitated, the information message of the shortcut phrase can be automatically checked and generated, the communication efficiency is high, and the safety is high.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the financial field, and in particular to a business quick phrase message pushing method and related devices. Background Art

[0002] Generally, large commercial banks adopt a front-end and back-end separation operation mode, and usually establish one or more back-end systems to accept complex businesses that require manual processing submitted remotely by tellers at various branch outlets. A complex business will be divided into multiple links according to business rules, such as data entry, review and recording, print verification, business verification, data verification, accounting, etc. Each link will generate a task, which will be randomly assigned to operators of the back-end system with different operation authority roles for processing. When the operator of the back-end system processes payment-related businesses, he may encounter situations where the business information is questionable. For example, in the task of processing the review and recording link, the OCR input data is inconsistent with the image information; in the accounting task, if the receiving bank number of the inter-bank transfer is filled in incorrectly, if the business is returned directly, the work of each link in the early stage needs to be processed again, and the business processing efficiency is greatly reduced. Therefore, it is necessary for the operator of the back-end system to be able to work with the teller at the branch to address clear business element issues.

[0003] Existing instant messaging tools are developed and used by various companies. Users can send and receive information through video, voice, text, pictures, etc. Instant messaging technology is usually divided into message push, communication chat, real-time audio and video, live broadcast, etc. Message push refers to a technology that pushes information or notifications to user devices in real time. It establishes a connection with the user's device through a push service. When there is a new message or notification, the push service pushes the information to the user's device. For example, when a mobile banking APP notifies customers of consumption information or pushes marketing advertising information, it uses a message push service. However, the existing technology does not support business message communication between different systems, cross-system communication is inconvenient, and communication efficiency is low. Summary of the invention

[0004] In view of the above problems, the present invention provides a method and related devices for pushing business quick phrase messages that overcome the above problems or at least partially solve the above problems.

[0005] In a first aspect, a method for pushing a business quick phrase message includes:

[0006] The backend system queries and obtains corresponding business information for the task to be communicated, wherein the business information includes: business type, component and component link;

[0007] The backend system queries the corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, wherein the message parameter configuration uses the shortcut phrase and element information, the message access rule configuration is used to configure the access information of the message, and the element rule configuration is used to configure the rule verification information of the shortcut phrase;

[0008] The backend system verifies and generates a message message in a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message messages generated by different backend systems are unified into the first format;

[0009] The backend system pushes the message to the frontend network point system through the message interaction center.

[0010] Optionally, in some optional implementations, before the background system queries and obtains corresponding business information for the task to be communicated, the method further includes:

[0011] The front-end network point system initiates a service application to the back-end system;

[0012] After accepting the business application, the background system establishes a plurality of corresponding tasks, wherein different tasks are executed in sequence, and one business application corresponds to a plurality of businesses.

[0013] Optionally, in some optional implementations, the background system queries and obtains corresponding business information for the task to be communicated, including:

[0014] The backend system queries and obtains the channel request serial number, business serial number, business type, component link and branch teller number of the task to be communicated as the business information.

[0015] Optionally, in some optional implementations, the background system queries corresponding message parameter configuration, message access rule configuration, and element rule configuration according to the business information, including:

[0016] The backend system queries and obtains corresponding message parameter configuration according to the business type and component link in the business information, wherein the message parameter configuration involves: quick phrases and element information;

[0017] The backend system queries and obtains the corresponding message access rule configuration according to the business type and component link in the business information, wherein the message access rule configuration is pre-updated to redis when the backend system is started, and the message access rule configuration includes: message sending type, message phrase flag, jump flag, jump parameter and jump model;

[0018] The backend system queries and obtains the corresponding element rule configuration according to the business type and component link in the business information.

[0019] Optionally, in some optional implementations, the background system verifies and generates a message message in a first format based on the message parameter configuration, the message access rule configuration, and the element rule configuration, including:

[0020] The background system generates a message message in the first format based on the message parameter configuration and the message access rule configuration;

[0021] The backend system verifies whether the elements involved in the message are correct based on the element rule configuration;

[0022] If the elements involved in the message are correct, the message in the first format is obtained.

[0023] Optionally, in some optional implementations, after the background system pushes the message message to the front-end network point system through the message interaction center, the method further includes:

[0024] The front-end network point system parses the message message based on the set message parsing rules to obtain the corresponding shortcut phrase;

[0025] The front-end network point system selects the central interface of the back-end system or its own message push interface for the quick phrase, and replies a message to the back-end system, wherein the reply message is a verified message.

[0026] Optionally, in certain optional implementations, after the front-end network point system selects the central interface of the back-end system or its own message push interface for the shortcut phrase and replies a message to the back-end system, the method further includes:

[0027] The background system queries the current business processing status and assignee of the task according to the message.

[0028] In a second aspect, a business quick phrase message push device includes: a background system;

[0029] The backend system includes: a business information query unit, a configuration query unit, a message generation unit and a message push unit;

[0030] The business information query unit is used to query and obtain corresponding business information for the task to be communicated, wherein the business information includes: business type, component and component link;

[0031] The configuration query unit is used to query the corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, wherein the message parameter configuration uses the shortcut phrase and element information, the message access rule configuration is used to configure the access information of the message, and the element rule configuration is used to configure the rule verification information of the shortcut phrase;

[0032] The message generation unit is used to verify and generate a message message of a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message messages generated by different background systems are unified into the first format;

[0033] The message push unit is used to push the message message to the front-end network point system through the message interaction center.

[0034] In a third aspect, a computer-readable storage medium stores a program, and when the program is executed by a processor, the method for pushing a business shortcut phrase message described in any one of the above items is implemented.

[0035] In a fourth aspect, an electronic device comprises at least one processor, and at least one memory and a bus connected to the processor; wherein the processor and the memory communicate with each other through the bus; and the processor is used to call program instructions in the memory to execute any of the business shortcut phrase message push methods described above.

[0036] By means of the above technical scheme, a method and related device for pushing business quick phrase messages provided by the present invention can query and obtain corresponding business information for the task to be communicated through the background system, wherein the business information includes: business type, component and component link; the background system queries the corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, wherein the message parameter configuration uses the quick phrase and element information, the message access rule configuration is used to configure the access information of the message, and the element rule configuration is used to configure the rule verification information of the quick phrase; the background system verifies and generates a message message of the first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message messages generated by different background systems are unified into the first format; the background system pushes the message message to the front-end network point system through the message interaction center. It can be seen from this that the present invention can unify the format of the message message, facilitate cross-system communication between different systems, and the present invention can also automatically verify and generate the message message of the quick phrase, which is not only efficient but also safe.

[0037] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0039] Figure 1 A flowchart of a method for pushing a business quick phrase message provided by the present invention is shown;

[0040] Figure 2 A flowchart of another method for pushing a business quick phrase message provided by the present invention is shown;

[0041] Figure 3 A schematic diagram showing a first message interaction provided by the present invention is shown;

[0042] Figure 4 A schematic diagram showing a second message interaction provided by the present invention is shown;

[0043] Figure 5 A schematic diagram showing a third message interaction provided by the present invention is shown;

[0044] Figure 6 A schematic diagram showing a fourth message interaction provided by the present invention is shown;

[0045] Figure 7 A schematic diagram showing a fifth message interaction provided by the present invention is shown;

[0046] Figure 8 A structural schematic diagram of an electronic device provided by the present invention is shown. DETAILED DESCRIPTION

[0047] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.

[0048] like Figure 1As shown, the present invention provides a method for pushing a business quick phrase message, including: S100, S200, S300 and S400;

[0049] S100, the backend system queries and obtains corresponding business information for the task to be communicated, wherein the business information includes: business type, component and component link;

[0050] Optionally, the backend system mentioned in the present invention can be understood as the backend center of the head office in the banking field. The backend system uses new technical tools such as imaging and workflow to achieve front-end and back-end separation and remote collaborative operations, transfer part of the transaction labor and control functions of the branch to the backend center, and support multiple types of business processing. When a branch teller accepts a business that needs to be processed by the backend system, a channel serial number will be generated, and after entering the business elements, it will be submitted to the backend system for subsequent processing.

[0051] Optionally, take the general processing flow of a payment-related account transaction as an example: when the background system receives the transaction, it will generate a transaction serial number. At the same time, according to the preset business processing flow, the transaction is divided into multiple links, and a task serial number is generated for each link. That is, a transaction will generate a channel serial number, a business serial number, and multiple task serial numbers, and the present invention does not limit this.

[0052] Optionally, the present invention can be used for business communication between operators of the backend system and tellers at outlets. The basic process is: the outlet system initiates a business, and after the backend system accepts the business, multiple tasks are generated according to the preset process. Each task that needs to be manually processed requires the business operator to obtain the task serial number for processing, and then transfer to the next task after processing. If the operator needs to communicate with the teller at the outlet regarding the business details, he can click the contact with the acceptor button on the task details interface. The system will obtain the business information through the task details interface, and then automatically query the quick phrase and message access rule configuration according to the business information. According to the query results, a negotiated specific message format is formed, and then the message is pushed to the outlet system through the message interaction center. After the outlet system parses the message message, it replies to the quick phrase question in turn, and performs business rule verification on the quick phrase content of each reply, and pushes the message through the message interaction center after the verification passes. After receiving the quick phrase of the reply, the operator of the backend system performs different operations according to the latest task status of the message and the message rules of the task link. For example, check the reply quick phrase content, perform business jump, or automatically fill in the message content.

[0053] Optionally, the overall process of the present invention is as follows Figure 2 As shown, the present invention will not be explained in detail here. Figure 2 Please refer to the subsequent explanation for understanding the contents, and the present invention does not limit this.

[0054] Optionally, as mentioned above, a business needs to be split into multiple tasks for execution, some tasks require communication with branch tellers, while others do not. Tasks that require communication with branch tellers can be understood as tasks to be communicated as mentioned in the present invention, and the present invention does not impose any restrictions on this.

[0055] Optionally, concepts such as business types, components, and component links are well-known technical concepts in the art, and the present invention will not make any detailed descriptions of them. For details, please refer to the relevant descriptions in the art.

[0056] Optionally, in some optional embodiments, before S100, the method further includes: step 1.1 and step 1.2;

[0057] Step 1.1, the front-end network point system initiates a business application to the back-end system;

[0058] Step 1.2: After the background system accepts the business application, it establishes multiple corresponding tasks, wherein different tasks are executed in sequence, and one business application corresponds to multiple businesses.

[0059] Optionally, in some optional embodiments, the S100 includes: step 2.1;

[0060] Step 2.1: The backend system queries and obtains the channel request serial number, business serial number, business type, component link and branch teller number of the task to be communicated as the business information.

[0061] S200, the background system queries the corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, wherein the message parameter configuration uses the shortcut phrase and element information, the message access rule configuration is used to configure the access information of the message, and the element rule configuration is used to configure the rule verification information of the shortcut phrase;

[0062] For example, in some optional embodiments, the S200 includes: step 3.1, step 3.2 and step 3.3;

[0063] Step 3.1, the backend system queries and obtains corresponding message parameter configuration according to the business type and component link in the business information, wherein the message parameter configuration involves: quick phrases and element information;

[0064] Step 3.2, the backend system queries and obtains the corresponding message access rule configuration according to the business type and component link in the business information, wherein the message access rule configuration is pre-updated to redis when the backend system is started, and the message access rule configuration includes: message sending type, message phrase flag, jump flag, jump parameter and jump model;

[0065] Step 3.3: The backend system queries and obtains the corresponding element rule configuration according to the business type and component link in the business information.

[0066] Optionally, the present invention designs three message rules: message parameter configuration, message access control configuration, and element rule configuration. When the background system initiates message communication for any task process, the business type, component, and component link of the task can be obtained from the task details interface, and then based on this information, the message parameter configuration, message access control configuration, and element rule configuration can be queried, and then combined into the final message message, which is not limited by the present invention.

[0067] Optionally, when the background system pushes messages, the rules may be synchronized to an external system, or the message interface of the background system may be directly reused, which is not limited in the present invention.

[0068] Optionally, message parameter configuration is used to configure the shortcut phrases and element information used in the message. This configuration table configures multiple shortcut phrases and English elements required for the internal links of a business type, as shown in Table 1 below.

[0069] Table 1

[0070]

[0071] Message parameter type description: 0 is push message, 1 is session message, 2 is email, 3 is SMS. The present invention can be extended according to business needs, and different types can be configured to display corresponding interfaces, and the present invention does not limit this.

[0072] Optional, message access control configuration, used to configure message access information. The table is loaded into redis when the system starts, and Redis will be updated synchronously when the business is added, deleted, modified, or queried through the management menu. Query parameter information such as message sending type, message phrase flag, jump flag, jump parameter, jump model, etc. according to the three keys of business type, link, and message type. These parameter information are divided into two categories: sending and replying. For example, if the head office center interface is reused, the reply parameters will be queried when replying to the message, as shown in Table 2 below.

[0073] Table 2

[0074]

[0075] Optional, element rule configuration, used to configure the rule verification information of the quick phrase. The English element of the quick phrase must be named the same as the business page element to achieve automatic message backfill. If a component link has the verification rule enabled, when replying to the quick phrase question, the element verification rule of the reply content will be queried based on the English element of the quick phrase in the message content, and the reply content will be verified according to the rule. For example, the content of a message reply is a quick phrase, containing the datVch element, and the content is 20230101. The verification rule is enabled, then the rule of the element will be automatically found according to datVch and verified. For datVch, the field length will be verified to 8, and the configured regular expression will be used to verify the message content. If the format is wrong, the configured error prompt will be prompted. For namAcRecv, only the field length range is verified to be between 1 and 120, and there is no regular verification, as shown in Table 3 below.

[0076] Table 3

[0077]

[0078] S300, the background system verifies and generates a message message in a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message messages generated by different background systems are unified into the first format;

[0079] For example, in some optional embodiments, the S300 includes: step 4.1, step 4.2 and step 4.3;

[0080] Step 4.1, the background system generates a message message in the first format based on the message parameter configuration and the message access rule configuration;

[0081] Step 4.2, the background system verifies whether the elements involved in the message are correct based on the element rule configuration;

[0082] Step 4.3: If the elements involved in the message are correct, obtain the message in the first format.

[0083] Optionally, the first format mentioned in the present invention may be a JSON format. That is, the message content uses the JSON format, and the message sending and receiving use a unified format. As long as different systems use the same message message, message interaction can be achieved. The business notification message is as follows:

[0084]

[0085]

[0086] Note: sysId, system ID, indicates the system from which the message is sent.

[0087] Type: message type, trans is a transaction message, note is a notification message, and the shortcut phrase is a transaction message.

[0088] Idmsgbiz: message code, message access control table id.

[0089] CodTr: Jump menu, type is assigned the value of trans.

[0090] Msg: transaction message body.

[0091] isShort: Y is a quick phrase message, and N is a non-quick phrase message.

[0092] Short: A quick phrase.

[0093] numSeq: sequence number, used for quick phrase display sorting.

[0094] txtEleShort: English element, used for field rule verification and message backfilling. If backfilled, it must be consistent with the backfill field.

[0095] indRuleEnbl: Whether to enable rule verification.

[0096] txtParmMsg: Quick phrase question.

[0097] txtMsgCten: quick phrase reply content.

[0098] numBizJrn: business serial number.

[0099] numTaskSeq: task sequence number.

[0100] numBizReq: channel serial number.

[0101] S400: The backend system pushes the message to the frontend network point system through the message interaction center.

[0102] Optionally, in some optional implementations, after S400, the method further includes: step 5.1 and step 5.2;

[0103] Step 5.1, the front-end network point system parses the message message based on the set message parsing rules to obtain the corresponding shortcut phrase;

[0104] Step 5.2: The front-end network point system selects the central interface of the back-end system or its own message push interface for the shortcut phrase, and replies a message to the back-end system, wherein the reply message is a verified message.

[0105] Optionally, in certain optional embodiments, after step 5.2, the method further comprises: step 6.1;

[0106] Step 6.1: The background system queries the current business processing status and assignee of the task according to the message.

[0107] Optionally, the entire message communication process of the present invention is introduced below by taking the quick phrase business message communication process in the remittance element review stage of the payment business settlement account as an example.

[0108] 1. The teller at the branch initiates a remittance business for a settlement account and generates a channel serial number. The channel serial number and business information are sent to the backend system together.

[0109] 2. The operator of the back-end system accepts the business, which generates multiple tasks such as data entry, data rule verification, element review, element verification, business rule verification, seal verification, business verification, account processing, and account processing review according to the preset process. Element review, element review, business verification, account processing, and account processing review all require message communication, and the element review link also requires automatic message backfilling.

[0110] 3. From the task details interface of the element review, click Contact the acceptor to initiate a quick phrase communication. From the task processing page, obtain the channel request serial number, business serial number, business type 100001, link eleCheck, and branch teller number and other business information of this task. According to the business type 100001 and link eleCheck, query the message parameter configuration, obtain the message parameter type, quick phrase content, and the business rule check activation status of each item, and call up the quick phrase message push interface, such as Figure 3 shown.

[0111] 4. The operator selects the required quick phrase question and clicks the message send button. The message access control configuration will be queried based on the service type 100001 and the link eleCheck, and then the message will be synthesized:

[0112]

[0113]

[0114] 5. Push the message to the network point system A through the message server. After receiving the message, the network point system A parses the message according to the negotiated message format and displays it, such as Figure 4As shown, the display site system A receives the shortcut phrase.

[0115] 6. The system where the teller at the branch is located can use two methods to reply to the quick phrase. One is to call the background system interface, and the other is for the system to implement the message push interface itself. This mode requires synchronization of the three rule configuration tables mentioned above. The sample message sends three quick phrases: datVch, numVch, and txteleShort (other). Business rule verification is enabled for datVch and numVch. When replying to the message, the reply content is checked according to the rule verification parameters. After the check passes, the message reply is successful.

[0116] 7. When the backend system receives the reply message, it first queries the business processing status and assignee of the task according to the task number in the message content. There are three situations:

[0117] Case 1: If the task is not completed and is under the name of the person, and the business rule is configured to backfill, the backfill operation will be automatically performed after the message is received. If the task interface has opened the quick phrase content of the reply to automatically backfill into the elements consistent with the page, if the task page is not opened, clicking the received message can also automatically jump to the task page and backfill the elements. First, the backfill prompt is performed, such as Figure 5 shown.

[0118] After clicking the OK button, the content of the element variables datVch and numVch in the task processing interface will be automatically filled in, completing the automatic backfilling. Figure 6 As shown, the text boxes after the bill date and bill number are automatically filled in, and the message content is displayed in the right area to facilitate the operator to compare and confirm;

[0119] Case 2: If the task is not completed and is under the name of the person, and the business rule is configured for jump, for example, the message action flag in the message rule configuration is 1 jump, and the received message jump parameter is / prod / bizTrn, after clicking the received message, the URL will be spliced ​​according to the domain name, jump parameter and business information and jump will be performed.

[0120] Case 3: Other cases, such as when the task has been completed or the task is not in your name, you can only view the shortcut phrase content. Figure 7 shown.

[0121] In summary, the present invention implements quick phrase message push in a configurable manner, which has the following advantages:

[0122] (1) It can automatically match message parameters according to business information and quickly send quick phrase messages of different business types to improve communication efficiency.

[0123] (2) The content of the reply quick phrase can be checked according to business rules to meet the requirements of automatic backfilling of business information, reduce copying and pasting work, avoid manual filling errors, and improve the accuracy of information entry.

[0124] (3) Various message parameters can be flexibly set to form a message message in a specific format. The message contains message parameters and business information. The system can automatically fill in the message content, redirect business, view details, and other functions based on the received message message.

[0125] The present invention provides a business quick phrase message push device, comprising: a background system;

[0126] The backend system includes: a business information query unit, a configuration query unit, a message generation unit and a message push unit;

[0127] The business information query unit is used to query and obtain corresponding business information for the task to be communicated, wherein the business information includes: business type, component and component link;

[0128] The configuration query unit is used to query the corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, wherein the message parameter configuration uses the shortcut phrase and element information, the message access rule configuration is used to configure the access information of the message, and the element rule configuration is used to configure the rule verification information of the shortcut phrase;

[0129] The message generation unit is used to verify and generate a message message of a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message messages generated by different background systems are unified into the first format;

[0130] The message push unit is used to push the message message to the front-end network point system through the message interaction center.

[0131] Optionally, in certain optional embodiments, the device further comprises: a front-end outlet system;

[0132] The front-end network point system includes: a business application initiating unit;

[0133] The background system also includes: a task establishment unit;

[0134] The business application initiating unit is used to initiate a business application to the background system before the background system queries and obtains corresponding business information for the task to be communicated;

[0135] The task establishing unit is used to establish a plurality of corresponding tasks after accepting the service application, wherein different tasks are executed in sequence and one service application corresponds to a plurality of services.

[0136] Optionally, in certain optional implementations, the business information query unit includes: a business information query subunit;

[0137] The business information query subunit is used to query and obtain the channel request serial number, business serial number, business type, component link and branch teller number of the task to be communicated as the business information.

[0138] Optionally, in certain optional implementations, the configuration query unit includes: a message parameter configuration query subunit, a message access rule query subunit, and an element rule configuration query subunit;

[0139] The message parameter configuration query subunit is used to query and obtain the corresponding message parameter configuration according to the business type and component link in the business information, wherein the message parameter configuration involves: shortcut phrases and element information;

[0140] The message access rule query subunit is used to query and obtain the corresponding message access rule configuration according to the business type and component link in the business information, wherein the message access rule configuration is pre-updated to redis when the background system is started, and the message access rule configuration includes: message sending type, message phrase flag, jump flag, jump parameter and jump model;

[0141] The element rule configuration query subunit is used to query and obtain the corresponding element rule configuration according to the business type and component link in the business information.

[0142] Optionally, in some optional implementations, the message generation unit includes: a message message generation subunit, a message message verification subunit and a message message acquisition subunit;

[0143] The message packet generation subunit is used to generate a message packet in the first format based on the message parameter configuration and the message access rule configuration;

[0144] The message verification subunit is used to verify whether the elements involved in the message are correct based on the element rule configuration;

[0145] The message message acquisition subunit is used to obtain the message message in the first format if the elements involved in the message message are correct.

[0146] Optionally, in some optional implementations, the front-end network point system further includes: a message parsing unit and a message reply unit;

[0147] The message parsing unit is used to parse the message based on the set message parsing rules to obtain the corresponding shortcut phrase after the backend system pushes the message to the front-end network point system through the message interaction center;

[0148] The message reply unit is used to select the central interface of the background system or its own message push interface for the quick phrase, and reply a message to the background system, wherein the replied message is a verified message.

[0149] Optionally, in some optional implementations, the background system further includes: a business processing status query unit;

[0150] The business processing status query unit is used to select the central interface of the backend system or its own message push interface for the shortcut phrase in the front-end branch system, and after replying a message to the backend system, query the current business processing status and acceptor of the task according to the message.

[0151] The present invention provides a computer-readable storage medium on which a program is stored. When the program is executed by a processor, the method for pushing a business quick phrase message described in any one of the above is implemented.

[0152] like Figure 8 As shown, the present invention provides an electronic device 70, which includes at least one processor 701, and at least one memory 702 and a bus 703 connected to the processor 701; wherein the processor 701 and the memory 702 communicate with each other through the bus 703; the processor 701 is used to call the program instructions in the memory 702 to execute any of the business shortcut phrase message push methods described above.

[0153] In the present invention, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0154] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0155] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined in the present invention may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown in the present invention, but will conform to the widest scope consistent with the principles and novel features disclosed in the present invention.

[0156] The above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A method for pushing a business quick phrase message, characterized in that: include: The backend system queries and obtains corresponding business information for the task to be communicated, wherein the business information includes: business type, component and component link; The backend system queries the corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, wherein the message parameter configuration uses the shortcut phrase and element information, the message access rule configuration is used to configure the access information of the message, and the element rule configuration is used to configure the rule verification information of the shortcut phrase; The backend system verifies and generates a message message in a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message messages generated by different backend systems are unified into the first format; The backend system pushes the message to the frontend network point system through the message interaction center.

2. The method according to claim 1, characterized in that: Before the background system queries and obtains corresponding business information for the task to be communicated, the method further includes: The front-end network point system initiates a service application to the back-end system; After accepting the business application, the background system establishes a plurality of corresponding tasks, wherein different tasks are executed in sequence, and one business application corresponds to a plurality of businesses.

3. The method according to claim 1, characterized in that The backend system queries and obtains corresponding business information for the task to be communicated, including: The backend system queries and obtains the channel request serial number, business serial number, business type, component link and branch teller number of the task to be communicated as the business information.

4. The method according to claim 3, characterized in that: The backend system queries the corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, including: The backend system queries and obtains corresponding message parameter configuration according to the business type and component link in the business information, wherein the message parameter configuration involves: quick phrases and element information; The backend system queries and obtains the corresponding message access rule configuration according to the business type and component link in the business information, wherein the message access rule configuration is pre-updated to redis when the backend system is started, and the message access rule configuration includes: message sending type, message phrase flag, jump flag, jump parameter and jump model; The backend system queries and obtains the corresponding element rule configuration according to the business type and component link in the business information.

5. The method according to claim 3, characterized in that: The backend system verifies and generates a message message in a first format based on the message parameter configuration, the message access rule configuration, and the element rule configuration, including: The background system generates a message message in the first format based on the message parameter configuration and the message access rule configuration; The backend system verifies whether the elements involved in the message are correct based on the element rule configuration; If the elements involved in the message are correct, the message in the first format is obtained.

6. The method according to claim 1, characterized in that After the backend system pushes the message to the front-end network point system through the message interaction center, the method further includes: The front-end network point system parses the message message based on the set message parsing rules to obtain the corresponding shortcut phrase; The front-end network point system selects the central interface of the back-end system or its own message push interface for the quick phrase, and replies a message to the back-end system, wherein the reply message is a verified message.

7. The method according to claim 6, characterized in that After the front-end network point system selects the central interface of the back-end system or its own message push interface for the quick phrase and replies a message to the back-end system, the method further includes: The background system queries the current business processing status and assignee of the task according to the message.

8. A business quick phrase message push device, characterized in that: include: Backend system; The backend system includes: a business information query unit, a configuration query unit, a message generation unit and a message push unit; The business information query unit is used to query and obtain corresponding business information for the task to be communicated, wherein the business information includes: business type, component and component link; The configuration query unit is used to query the corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, wherein the message parameter configuration uses the shortcut phrase and element information, the message access rule configuration is used to configure the access information of the message, and the element rule configuration is used to configure the rule verification information of the shortcut phrase; The message generation unit is used to verify and generate a message message of a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message messages generated by different background systems are unified into the first format; The message push unit is used to push the message message to the front-end network point system through the message interaction center.

9. A computer-readable storage medium having a program stored thereon, characterized in that: When the program is executed by the processor, the service shortcut phrase message pushing method according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: The electronic device includes at least one processor, and at least one memory and a bus connected to the processor; wherein the processor and the memory communicate with each other through the bus; the processor is used to call the program instructions in the memory to execute the business shortcut phrase message push method as described in any one of claims 1 to 7.

Citation Information

Patent Citations

  • Early warning information short message sending device and publishing device and system against emergent event

    CN108269386A

  • Counter business processing system, method and device and storage medium

    CN111292179A

  • Service information pushing method and system and storage medium

    CN115208947A

  • Unified heterogeneous message pushing method and system

    CN116866427A

  • Data processing method and device and storage medium

    CN117251436A