Business quick phrase message pushing method and related device
By generating standardized message messages in the back-end systems of large commercial banks and pushing them to the front-end branch systems, the problem of low efficiency in cross-system communication was solved, enabling efficient business message push and automatic verification, and improving the accuracy and efficiency of information processing.
Patent Information
- Application Number
- CN202411743545.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-30
- Publication Date
- 2025-11-25
- Estimated Expiration
- 2044-11-30
AI Technical Summary
Existing technologies have failed to effectively support business message communication between different systems, resulting in low efficiency in cross-system communication. This is especially true in the front- and back-office separation operation mode of large commercial banks, where complex business processes require re-processing of issues at each stage.
Business information is retrieved through the backend system, a unified format message message is generated, and it is pushed to the front-end branch system through the message interaction center to realize cross-system message communication and automatically verify and generate quick phrase messages.
It achieves unified message format across different systems, facilitating cross-system communication, improving communication efficiency, and reduces repetitive work and errors by automatically verifying and generating quick phrase messages, thereby improving the accuracy of information entry.
Smart Images

Figure CN119603258B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the field of finance, in particular to a business shortcut phrase message pushing method and related device. BACKGROUND
[0002] Generally, large commercial banks adopt a back-end separation operation mode, and usually establish one or more back-end systems to accept remote submission of complex businesses by branch counters, which need to be manually processed. A complex business will be divided into multiple links according to business rules, such as input, review, verification, business verification, data verification, and accounting links. Each link will generate a task, which is randomly assigned to an operator of the back-end system with different operation permissions to process. When the operator of the back-end system processes a payment business, he or she may encounter a situation where the business information is doubtful. For example, when processing the review task, the OCR input data does not match the image information; when processing the accounting task, the receiving bank number is filled in incorrectly in the cross-bank transfer. If the business is directly returned, the work of each link in the early stage needs to be processed again, which greatly reduces the efficiency of business processing. Therefore, the operator of the back-end system needs to be able to communicate with the branch counter on the specific business element problem.
[0003] The existing instant messaging tool is a variety of communication tools developed and used by various enterprises. Users can send and receive information through video, voice, text, pictures, etc. Instant messaging technology is usually divided into message pushing, communication chatting, real-time audio and video, live broadcast, etc. Message pushing refers to a technology that pushes information or notifications to user devices in real time. It establishes a connection with the user device through a push service, and when there is a new message or notification, the push service pushes the information to the user device. For example, when the mobile banking APP notifies the customer of consumption information or pushes marketing advertising information, the message pushing service is used. However, the existing technology does not support business message communication between different systems, and cross-system communication is not convenient, which is low in communication efficiency. SUMMARY
[0004] In view of the above problems, the present application provides a business shortcut phrase message pushing method and related device which can overcome the above problems or at least partially solve the above problems.
[0005] In a first aspect, a business shortcut phrase message pushing method comprises:
[0006] The back-end system queries and obtains corresponding business information for the task to be communicated, wherein the business information includes business type, components, and component links.
[0007] The background system queries corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, wherein the message parameter configuration uses shortcut phrases and element information, the message access rule configuration is used for configuring access information of the message, and the element rule configuration is used for configuring rule check information of the shortcut phrases;
[0008] The background system checks and generates a message report in a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message reports generated by different background systems are all unified into the first format;
[0009] The background system pushes the message report to the foreground network point system through a message interaction center.
[0010] Optionally, in some optional embodiments, before the background system queries and obtains corresponding business information for a task to be communicated, the method further comprises:
[0011] The foreground network point system initiates a business application to the background system;
[0012] After the background system accepts 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 embodiments, the background system queries and obtains corresponding business information for a task to be communicated, comprising:
[0014] The background system queries and obtains a channel request serial number, a business serial number, a business type, a component link and a network point clerk number of the task to be communicated as the business information.
[0015] Optionally, in some optional embodiments, the background system queries corresponding message parameter configuration, message access rule configuration and element rule configuration according to the business information, comprising:
[0016] The background system queries and obtains corresponding message parameter configuration according to the business type and the component link in the business information, wherein the message parameter configuration involves shortcut phrases and element information;
[0017] The background system queries and obtains corresponding message access rule configuration according to the business type and the component link in the business information, wherein the message access rule configuration is updated to redis in advance 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;
[0018] The background system queries and acquires corresponding element rule configurations according to the business category and component links in the business information.
[0019] Optionally, in some optional embodiments, the background system verifies and generates the message in the first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, including:
[0020] The background system generates the message in the first format based on the message parameter configuration and the message access rule configuration;
[0021] The background 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 embodiments, after the background system pushes the message to the front-end point system through the message interaction center, the method further includes:
[0024] The front-end point system analyzes the message based on the set message analysis rule to obtain the corresponding shortcut phrase;
[0025] The front-end point system selects the central interface of the background system or the message push interface of itself to reply to the background system for the shortcut phrase, wherein the replied message is a verified message.
[0026] Optionally, in some optional embodiments, after the front-end point system selects the central interface of the background system or the message push interface of itself to reply to the background system for the shortcut phrase, the method further includes:
[0027] The background system queries the current business processing state and the handling person of the task according to the message.
[0028] In a second aspect, a business shortcut phrase message push device includes a background system.
[0029] The background 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 configured to query and acquire corresponding business information for a task to be communicated, wherein the business information includes a business category, components and component links.
[0031] The configuration query unit is configured to query corresponding message parameter configuration, message access rule configuration and element rule configuration according to the service information, wherein the message parameter configuration uses shortcut phrases and element information, the message access rule configuration is used for configuring access information of the message, and the element rule configuration is used for configuring rule check information of the shortcut phrases.
[0032] The message generation unit is configured to check and generate a message report in a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message reports generated by different background systems are all unified into the first format.
[0033] The message pushing unit is configured to push the message report to a foreground network point system through a message interaction center.
[0034] In a third aspect, a computer readable storage medium has a program stored thereon, and the program is executed by a processor to implement the service shortcut phrase message pushing method.
[0035] In a fourth aspect, an electronic device includes at least one processor and at least one memory connected to the processor via a bus; the processor and the memory communicate with each other through the bus; the processor is configured to call program instructions in the memory to execute the service shortcut phrase message pushing method.
[0036] According to the technical solution, the service shortcut phrase message pushing method and related device can query and obtain corresponding service information for a task to be communicated by a background system, wherein the service information includes service type, components and component links; the background system queries corresponding message parameter configuration, message access rule configuration and element rule configuration according to the service information, wherein the message parameter configuration uses shortcut phrases and element information, the message access rule configuration is used for configuring access information of the message, and the element rule configuration is used for configuring rule check information of the shortcut phrases; the background system checks and generates a message report in a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message reports generated by different background systems are all unified into the first format; and the background system pushes the message report to a foreground network point system through a message interaction center. Thus, the application can unify the format of the message report, facilitate cross-system communication between different systems, and automatically check and generate the message report of the shortcut phrases, which is not only efficient but also safe.
[0037] The above description is only a summary of the technical solutions of the present application. In order to enable one skilled in the art to better understand the technical means of the present application and implement the same according to the contents of the description, and in order to enable the above and other purposes, characteristics and advantages of the present application to be more apparent and easy to understand, the specific embodiments of the present application are described below. BRIEF DESCRIPTION OF DRAWINGS
[0038] Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The accompanying drawings are included to provide a better understanding of the preferred embodiments, and are not to be considered limitations of the present application. Moreover, in the drawings, like reference numerals refer to similar components throughout the several views. In the drawings:
[0039] Figure 1 A flow chart of a service shortcut phrase message pushing method provided by the present application is shown;
[0040] Figure 2 A flow chart of another service shortcut phrase message pushing method provided by the present application is shown;
[0041] Figure 3 A schematic diagram of a first message interaction provided by the present application is shown;
[0042] Figure 4 A schematic diagram of a second message interaction provided by the present application is shown;
[0043] Figure 5 A schematic diagram of a third message interaction provided by the present application is shown;
[0044] Figure 6 A schematic diagram of a fourth message interaction provided by the present application is shown;
[0045] Figure 7 A schematic diagram of a fifth message interaction provided by the present application is shown;
[0046] Figure 8 A schematic diagram of an electronic device provided by the present application is shown. DETAILED DESCRIPTION
[0047] Exemplary embodiments of the present application will be described hereinafter with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application can be embodied in various forms without being limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.
[0048] As Figure 1As shown, the present application provides a business quick phrase message pushing method, comprising: S100, S200, S300 and S400;
[0049] S100, the background system queries and acquires corresponding business information for the task to be communicated, wherein the business information comprises: business category, component and component link;
[0050] Optionally, the background system of the present application can be understood as a head office background center in the banking field. The background system realizes separation of front and back offices and off-site collaborative work by means of new technical tools such as images and workflows, transfers part of transaction labor and control functions of the network point to the background center, and supports multiple business processing. The network teller receives a business that needs to be processed by the background system, generates a channel serial number, enters business elements, and then submits to the background system for subsequent processing.
[0051] Optionally, taking the general processing flow of a payment type credit transfer business as an example: when the background system receives the business, it will generate a business serial number. At the same time, according to the preset business processing flow, the business is split into multiple links, and a task serial number is generated for each link. That is, one business will generate a channel serial number, a business serial number and multiple task serial numbers, which are not limited by the present application.
[0052] Optionally, the present application can be used for business communication between operators of the background system and network tellers. The basic process is: the network system initiates a business, and the background system receives the business and generates multiple tasks according to the preset flow. Each task that needs to be processed manually requires a business operator to obtain a task serial number for processing, and after processing, it is transferred to the next task. If the operator needs to communicate with the network teller on business details, he can click the contact button in the task details interface. The system will obtain the business information through the task details interface, then automatically query the quick phrase and message access rules configuration according to the business information. According to the query result, a specific message report format is composed, and then the message is pushed to the network system through the message interaction center. The network system parses the message report, replies to the quick phrase question in turn, and performs business rule verification on the content of each reply quick phrase. After verification, the message is pushed through the message interaction center. After receiving the reply quick phrase, the background system operator performs different operations according to the latest task state of the message and the message rules of the task link, such as viewing the reply quick phrase content, performing business jump or automatically filling in the message content, etc.
[0053] Optionally, the overall flow of the present application is as shown in Figure 2 As shown, the present application here will not be explained too much, Figure 2 The content in the following explanation should be understood, and the present application does not limit it.
[0054] Optionally, as mentioned above, one service needs to be split into multiple tasks for execution, some of which need to communicate with the branch teller, and some of which do not. The task that needs to communicate with the branch teller can be understood as the task to be communicated in the present application, and the present application does not limit this.
[0055] Optionally, the concepts of service type, component and component link are technical concepts known in the art, and the present application does not make too much description, please refer to the relevant description in the art.
[0056] Optionally, in some optional embodiments, before S100, the method further comprises steps 1.1 and 1.2.
[0057] Step 1.1, the front-end branch system initiates a service application to the back-end system;
[0058] Step 1.2, after the back-end system accepts the service application, a plurality of corresponding tasks are established, wherein different tasks are executed in sequence, and one service application corresponds to multiple services.
[0059] Optionally, in some optional embodiments, S100 comprises step 2.1.
[0060] Step 2.1, the back-end system queries and obtains the channel request serial number, service serial number, service type, component link and branch teller number of the task to be communicated as the service information.
[0061] S200, the back-end system queries the corresponding message parameter configuration, message access rule configuration and element rule configuration according to the service information, wherein the shortcut phrase and element information used by the message parameter configuration, 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, S200 comprises steps 3.1, 3.2 and 3.3.
[0063] Step 3.1, the back-end system queries and obtains the corresponding message parameter configuration according to the service type and component link in the service information, wherein the message parameter configuration involves shortcut phrase and element information;
[0064] Step 3.2, the background system acquires corresponding message access rule configuration according to the business category and component link in the business information, wherein the message access rule configuration is pre-updated to redis when the background system starts, and the message access rule configuration comprises: message sending type, message phrase flag, jump flag, jump parameter and jump model;
[0065] Step 3.3, the background system acquires corresponding element rule configuration according to the business category and component link in the business information.
[0066] Optionally, the application 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 category, component and component link of the task can be acquired from the task detail interface, and then the message parameter configuration, message access control configuration and element rule configuration can be queried according to the information, and finally the message report is combined, which is not limited by the application.
[0067] Optionally, the background system can synchronize the rules to the external system when pushing the message, or directly reuse the message interface of the background system, which is not limited by the application.
[0068] Optionally, the message parameter configuration is used to configure the shortcut phrase and element information used by the message. The configuration table configures multiple shortcut phrases and English elements required by the internal link of a business category, as shown in Table 1.
[0069] Table 1
[0070]
[0071] Message parameter type description: 0 is a push message, 1 is a conversation message, 2 is an email, and 3 is a short message. The application can be extended according to business needs, and different types can display corresponding interfaces, which are not limited by the application.
[0072] Optionally, the message access control configuration is used to configure the access information of the message. The table is loaded into redis when the system starts, and the Redis is updated synchronously when the business is added, deleted, modified or inquired through the management menu. According to the business category, link and message type 3 keys, the message sending type, message phrase flag, jump flag, jump parameter, jump model and other parameter information are queried. These parameter information is divided into two categories: sending and replying, such as reusing the central interface of the general line, and querying the reply parameter when replying the message, as shown in Table 2.
[0073] Table 2
[0074]
[0075] Optionally, the element rule configuration is configured to configure the rule check information of the shortcut phrase. The shortcut phrase English element must be the same as the business page element name to realize automatic backfill of the message. If a component link enables the check rule, when the shortcut phrase question is replied, the shortcut phrase English element in the message content is queried to check the reply content element check rule, and the reply content is checked according to the rule. For example, the content of a message reply is a shortcut phrase, which contains a datVch element, the content is 20230101, and the check rule is enabled. Then, the datVch element is automatically searched according to the rule, and the rule is checked. For the datVch, the length of the field is checked to be 8, and the message content is checked using the configured regular expression. If the format is incorrect, the configured error prompt is prompted. For the namAcRecv, only the length of the field is checked to be between 1 and 120, and there is no regular check. The details are shown in Table 3.
[0076] Table 3
[0077]
[0078] S300, the background system checks and generates a message report in a first format based on the message parameter configuration, the message access rule configuration and the element rule configuration, wherein the message reports generated by different background systems are all unified into the first format;
[0079] For example, in some optional embodiments, the S300 includes steps 4.1, 4.2 and 4.3.
[0080] Step 4.1, the background system generates the message report in the first format based on the message parameter configuration and the message access rule configuration;
[0081] Step 4.2, the background system checks whether the elements involved in the message report are correct based on the element rule configuration;
[0082] Step 4.3, if the elements involved in the message report are correct, the message report in the first format is obtained.
[0083] Optionally, the first format of the present application can be a JSON format. That is, the message content uses the JSON format, and the message sending and receiving use a unified format. Different systems can realize message interaction as long as the same message report is used. The business class notification report is as follows:
[0084]
[0085]
[0086] Description: sysId, system ID, represents the message from which system.
[0087] Type: message type, trans transaction class message, note notification class message, shortcut phrase is transaction class message.
[0088] Idmsgbiz: message encoding, message access control table id.
[0089] CodTr: jump menu, type is assigned to trans.
[0090] Msg: transaction class message body.
[0091] isShort: Y for shortcut phrase message, N for non-shortcut phrase message.
[0092] Short: shortcut phrase.
[0093] numSeq: serial number, used for shortcut phrase display sorting.
[0094] txtEleShort: English element, field rule check and message backfill are used, if backfilled, it needs to be consistent with the backfilled field.
[0095] indRuleEnbl: whether to enable rule check.
[0096] txtParmMsg: shortcut phrase question.
[0097] txtMsgCten: shortcut phrase reply content.
[0098] numBizJrn: business serial number.
[0099] numTaskSeq: task serial number.
[0100] numBizReq: channel serial number.
[0101] S400, the background system pushes the message packet to the front-end network point system through the message interaction center.
[0102] Optionally, in some optional embodiments, after the S400, the method further comprises steps 5.1 and 5.2;
[0103] Step 5.1, the front-end network point system parses the message packet based on the set message parsing rule to obtain the corresponding shortcut phrase;
[0104] Step 5.2, the front-end network point system selects a central interface of the back-end system or a message push interface of itself, and replies a message to the back-end system according to the shortcut phrase, wherein the replied message is a verified message.
[0105] Optionally, after the step 5.2, the method further comprises a step 6.1 in some optional embodiments.
[0106] Step 6.1, the back-end system queries the current service processing state and the service taker according to the message.
[0107] Optionally, the following takes the shortcut phrase business class message communication process of the payment class business settlement account remittance element audit link as an example to introduce the whole message communication process of the present application.
[0108] 1. A network point clerk initiates a settlement account remittance business, and generates a channel serial number. The channel serial number and the business information are sent to the back-end system.
[0109] 2. An operator of the back-end system receives the business, and generates a plurality of link tasks such as input, data rule verification, element audit, element re-audit, business rule verification, verification, business verification, account processing, and account processing re-audit according to a preset process. The element audit, element re-audit, business verification, account processing, and account processing re-audit links all need to be communicated by messages, and the element audit link also needs to be automatically backfilled by messages.
[0110] 3. Clicking on the contact with the service taker from the element audit task detail interface initiates the shortcut phrase communication. The channel request serial number, the business serial number, the business type 100001, the link eleCheck, and the network point clerk number of the business information are obtained from the task processing page. The message parameter type, the shortcut phrase content, and the business rule verification enabled state of each item are obtained by querying the message parameter configuration according to the business type 100001 and the link eleCheck, and the shortcut phrase message push interface is called, as shown in Figure 3 .
[0111] 4. The operator selects the required shortcut phrase question, and clicks the message send button to query the message access control configuration according to the business type 100001 and the link eleCheck, and then synthesize the message report:
[0112]
[0113]
[0114] 5. The message is pushed 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 report format and displays it, as shown in Figure 4As shown, the display point system A receives the shortcut phrase.
[0115] 6. The net point teller system can reply to the shortcut phrase in two ways. One is to call the background system interface, and the other is to implement the message push interface by the system itself, which needs to synchronize the three rule configuration tables mentioned above. In the example message, three shortcut phrases datVch, numVch and txteleShort (other) are sent, and datVch and numVch enable business rule verification. When replying to the message, the reply content is checked according to the rule verification parameters, and the message is successfully replied after the check is passed.
[0116] 7. The background system receives the reply message, and first queries the business processing state and the person in charge of the task according to the task number in the message content, and divides into three cases:
[0117] Case one, if the task is not completed and is under the name of the person, and the business rule is configured to be backfilled, the message is received and automatically backfilled. If the task interface is opened, the shortcut phrase content is automatically backfilled into the elements consistent with the page, such as clicking the received message to automatically jump to the task page and backfill the elements, first backfill the prompt, such as Figure 5 As shown.
[0118] After clicking the OK button, the element variable in the task processing interface is automatically filled with the content of datVch and numVch, and the automatic backfilling is completed, such as Figure 6 As shown, the text box after the bill date and bill number is automatically backfilled, and the message content is displayed in the right area, which is convenient for the operator to compare and confirm;
[0119] Case two, if the task is not completed and is under the name of the person, and the business rule is configured to 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 is spliced according to the domain name, jump parameter and business information and jumped.
[0120] Case three, other cases, such as the task is completed, the task is not under the name of the person, etc. can only view the shortcut phrase content, such as Figure 7 As shown.
[0121] In summary, the present application realizes the push of shortcut phrase messages through configuration, and has the following advantages:
[0122] (1) It can automatically match message parameters according to business information, quickly send shortcut phrase messages of different business types, and improve communication efficiency.
[0123] (2) The reply shortcut phrase content can be subjected to business rule check, the business information automatic backfill requirement can be met, the copy and paste work is reduced, the manual filling error is avoided, and the information entry accuracy is improved.
[0124] (3) Various message parameters can be flexibly set, and a message report is combined into a specific format. The report has message parameters and business information, and the system can realize message content automatic backfill, business jump, detail viewing and other functions according to the received message report.
[0125] The application provides a business shortcut phrase message pushing device, comprising: a background system;
[0126] The background system comprises a business information query unit, a configuration query unit, a report generation unit and a message pushing unit.
[0127] The business information query unit is used for querying and obtaining corresponding business information for a task to be communicated, wherein the business information comprises a business type, components and component links.
[0128] The configuration query unit is used for querying corresponding message parameter configurations, message access rule configurations and element rule configurations according to the business information, wherein the shortcut phrase and element information used by the message parameter configurations, the message access rule configurations are used for configuring access information of the message, and the element rule configurations are used for configuring rule check information of the shortcut phrase.
[0129] The report generation unit is used for checking and generating a first format message report based on the message parameter configurations, the message access rule configurations and the element rule configurations, wherein the message reports generated by different background systems are all unified into the first format.
[0130] The message pushing unit is used for pushing the message report to a foreground network point system through a message interaction center.
[0131] Optionally, in some optional embodiments, the device further comprises: a foreground network point system.
[0132] The foreground network point system comprises a business application initiation unit.
[0133] The background system further comprises a task establishment unit.
[0134] The business application initiation unit is used for initiating a business application to the background system before the background system queries and obtains corresponding business information for a task to be communicated.
[0135] The task establishing unit is configured to establish a plurality of tasks corresponding to the service application after receiving the service application, wherein different tasks are executed in sequence, and one service application corresponds to a plurality of services.
[0136] Optionally, in some optional embodiments, the service information querying unit comprises a service information querying subunit.
[0137] The service information querying subunit is configured to query and obtain a channel request serial number, a service serial number, a service type, a component link, and a branch teller number of the task to be communicated as the service information.
[0138] Optionally, in some optional embodiments, the configuration querying unit comprises a message parameter configuration querying subunit, a message access rule querying subunit, and an element rule configuration querying subunit.
[0139] The message parameter configuration querying subunit is configured to query and obtain corresponding message parameter configurations according to the service type and the component link in the service information, wherein the message parameter configurations involve shortcut phrases and element information.
[0140] The message access rule querying subunit is configured to query and obtain corresponding message access rule configurations according to the service type and the component link in the service information, wherein the message access rule configurations are updated to redis in advance when the background system is started, and the message access rule configurations include a message sending type, a message phrase flag, a jump flag, a jump parameter, and a jump model.
[0141] The element rule configuration querying subunit is configured to query and obtain corresponding element rule configurations according to the service type and the component link in the service information.
[0142] Optionally, in some optional embodiments, the message generating unit comprises a message message generating subunit, a message message checking subunit, and a message message obtaining subunit.
[0143] The message message generating subunit is configured to generate the message message of the first format based on the message parameter configurations and the message access rule configurations.
[0144] The message message checking subunit is configured to check whether the elements involved in the message message are correct based on the element rule configurations.
[0145] The message message obtaining subunit is configured to obtain the message message of the first format if the elements involved in the message message are correct.
[0146] Optionally, in some optional embodiments, the front-end point system further comprises a message packet parsing unit and a message reply unit.
[0147] The message packet parsing unit is configured to, after the background system pushes the message packet to the front-end point system through the message interaction center, parse the message packet based on a set packet parsing rule to obtain a corresponding shortcut phrase.
[0148] The message reply unit is configured to, for the shortcut phrase, select a central interface of the background system or a message pushing interface of the front-end point system to reply to the background system with a message, wherein the replied message is a verified message.
[0149] Optionally, in some optional embodiments, the background system further comprises a business processing state query unit.
[0150] The business processing state query unit is configured to, after the front-end point system selects the central interface of the background system or the message pushing interface of the front-end point system to reply to the background system with a message, query the current business processing state and a handling person of the task according to the message.
[0151] The application provides a computer readable storage medium, which stores a program, and the program is executed by a processor to implement the business shortcut phrase message pushing method.
[0152] As shown in Figure 8 The application provides an electronic device 70, which comprises at least one processor 701 and at least one memory 702 connected with the processor 701, and a bus 703; wherein the processor 701 and the memory 702 complete mutual communication through the bus 703; the processor 701 is used to call program instructions in the memory 702 to execute the business shortcut phrase message pushing method.
[0153] In this disclosure, relational terms such as first and second and the like can be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises", "comprising", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
[0154] Each of the embodiments in the present specification is described in a related manner, and the same or similar parts among the embodiments can be referred to each other. Each of the embodiments mainly explains the difference from other embodiments. In particular, the system embodiments are described simply because they are basically similar to the method embodiments, and the related parts can be referred to the description of the method embodiments.
[0155] The above description of disclosed embodiments provides enabling disclosure sufficient for one of ordinary skill in the art to practice or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and generic principles defined herein can be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
[0156] The above description is only preferred embodiments of the present application, not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims
1. A method for pushing business quick phrase messages, characterized in that, The method comprises the following steps: The background system queries and obtains corresponding business information for a task to be communicated, wherein the business information comprises a business type, a component, and a component link; The background system queries corresponding message parameter configurations, message access rule configurations, and element rule configurations according to the business information, wherein the message parameter configurations are used for configuring shortcut phrases and element information used by a message, the message access rule configurations are used for configuring access information of the message, the access information comprises a message sending type, a message phrase flag, a jump flag, a jump parameter, and a jump model, and the element rule configurations are used for configuring rule check information of the shortcut phrases; The background system checks and generates a message report in a first format based on the message parameter configurations, the message access rule configurations, and the element rule configurations, wherein the message reports generated by different background systems are all unified into the first format; The background system checks and generates a message report in a first format based on the message parameter configurations, the message access rule configurations, and the element rule configurations, wherein the background system checks and generates the message report in the first format based on the message parameter configurations, the message access rule configurations, and the element rule configurations, comprising: The background system generates the message report in the first format based on the message parameter configurations and the message access rule configurations; The background system checks whether elements involved in the message report are correct based on the element rule configurations; If the elements involved in the message report are correct, the message report in the first format is obtained; The background system pushes the message report to a front-end network point system through a message interaction center; The front-end network point system analyzes the message report based on a set report analysis rule to obtain a corresponding shortcut phrase; The front-end network point system selects a central interface of the background system or a message push interface of itself to reply a message to the background system for the shortcut phrase, wherein the replied message is a checked message.
2. The method of claim 1, wherein, Before the background system queries and obtains corresponding business information for a task to be communicated, the method further comprises: The front-end network point system initiates a business application to the background system; After the background system accepts 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 of claim 1, wherein, The background system queries and obtains corresponding business information for a task to be communicated, comprising: The background system queries and obtains a channel request serial number, a business serial number, a business type, a component link, and a network point clerk number of the task as the business information for the task to be communicated.
4. The method of claim 3, wherein, The background system queries corresponding message parameter configurations, message access rule configurations, and element rule configurations according to the business information, comprising: The background system queries and obtains corresponding message parameter configurations according to a business type and a component link in the business information, wherein the message parameter configurations involve shortcut phrases and element information. The background system acquires corresponding message access rule configurations according to the business category and component links in the business information, wherein the message access rule configurations are pre-updated into redis when the background system starts, and the message access rule configurations include message sending types, message phrase flags, jump flags, jump parameters, and jump models. The background system acquires corresponding element rule configurations according to the business category and component links in the business information.
5. The method of claim 1, wherein, After the foreground site system selects the central interface of the background system or the message push interface of itself to reply to the background system for the shortcut phrase, the method further includes: The background system queries the current business processing state and the handling person of the task according to the message.
6. A service quick phrase message pushing apparatus, characterized by, It includes: A background system; The background 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 configured to acquire corresponding business information for a task to be communicated, wherein the business information includes a business category, components, and component links. The configuration query unit is configured to acquire corresponding message parameter configurations, message access rule configurations, and element rule configurations according to the business information, wherein the message parameter configurations are used to configure shortcut phrases and element information used by messages, the message access rule configurations are used to configure access information of messages, the access information includes message sending types, message phrase flags, jump flags, jump parameters, and jump models, and the element rule configurations are used to configure rule verification information of shortcut phrases. The message generation unit is configured to verify and generate a message report in a first format based on the message parameter configurations, the message access rule configurations, and the element rule configurations, wherein message reports generated by different background systems are all unified into the first format. The background system verifies and generates a message report in a first format based on the message parameter configurations, the message access rule configurations, and the element rule configurations, including: The background system generates the message report in the first format based on the message parameter configurations and the message access rule configurations. The background system verifies whether elements involved in the message report are correct based on the element rule configurations. If the elements involved in the message report are correct, the message report in the first format is obtained. The message push unit is configured to push the message report to a foreground site system through a message interaction center. The foreground site system analyzes the message report based on a set message analysis rule to obtain a corresponding shortcut phrase. The foreground site system selects the central interface of the background system or the message push interface of itself to reply to the background system for the shortcut phrase, wherein the replied message is a verified message.
7. A computer-readable storage medium having stored thereon a program, characterized in that, The program is executed by a processor to implement the business shortcut phrase message push method according to any one of claims 1 to 5.
8. An electronic device, comprising: The electronic device comprises at least one processor, at least one memory connected with the processor, and a bus; wherein the processor, the memory and the bus complete mutual communication; the processor is used to call program instructions in the memory, so as to execute the service shortcut phrase message pushing method in any one of claims 1 to 5.
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