Message reminding method and device, equipment and storage medium

Abstract

The application discloses a message reminding method and device, equipment and storage medium, belong to computer communication technical field. The method comprises: obtaining a plurality of label data; according to the list identification, determine the associated label data associated with the target list in the preset database; according to the label information corresponding to the associated label data, determine the candidate label of the target list, and determine the label meeting the preset condition in the candidate label as the target label; in the case where the target label meets the reminding trigger condition, send the reminding message to the front end. In this way, when the label information of the list is changed, the label data can be associated with the target list, and when the target label meets the reminding trigger condition, the reminding message is sent to the front end, so that the front end can follow up the target list in time, thereby improving the timeliness of important label reminding, avoiding the situation that important urgent matters are missed due to the untimely message reminding, and improving the service quality.

Description

Technical Field

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

[0002] With the development and popularization of computer communication technology, call center systems have become a unified and efficient service platform. They bring together various functional departments within an enterprise into a unified external contact window, centrally arrange agent seats, and adopt a unified standard service model to provide users with systematic, intelligent, and humanized services.

[0003] In real-world applications, each agent is typically assigned a large number of contacts and is required to conduct follow-up calls and satisfaction surveys with those contacts within the contact's validity period. However, the various tags associated with these contacts often change due to policy adjustments, user behavior, or risk control system assessments. For example, changes in account credit scores, loan limits, registration information, and business processing status can alter the importance of the contact list. Currently, changes in these tags are only visible when the contact list is queried, and the front-end is not promptly notified when tags change, leading to missed updates. Summary of the Invention

[0004] This application provides a message notification method, apparatus, device, and storage medium to solve the problem in the prior art that notifications cannot be sent in a timely manner when the tag information of a list changes.

[0005] To solve the above-mentioned technical problems, this application is implemented as follows:

[0006] In a first aspect, embodiments of this application provide a message notification method, including:

[0007] Acquire multiple tag data, the tag data including list identifiers and tag information, the tag data being used to indicate that the tag information of the list indicated by the list identifier has changed;

[0008] Based on the list identifier, identify the associated tag data among multiple tag data that is related to the target list in the preset database;

[0009] Based on the tag information corresponding to the associated tag data, at least one candidate tag of the target list is determined, and the tag that meets the preset conditions among the at least one candidate tag is determined as the target tag of the target list;

[0010] If the target tag meets the reminder triggering conditions, a reminder message is sent to the front end.

[0011] Secondly, embodiments of this application provide a message notification device, including:

[0012] The data acquisition module is used to acquire multiple tag data, the tag data including list identifiers and tag information, and the tag data is used to indicate that the tag information of the list indicated by the list identifier has changed;

[0013] The association determination module is used to determine, based on the list identifier, the associated tag data among multiple tag data that is associated with the target list in the preset database;

[0014] The tag determination module is used to determine at least one candidate tag of the target list based on the tag information corresponding to the associated tag data, and to determine the tag that meets the preset conditions among the at least one candidate tag as the target tag of the target list;

[0015] The message notification module is used to send a notification message to the front end when the target tag meets the notification triggering conditions.

[0016] Thirdly, embodiments of this application provide an electronic device, which includes a processor and a memory. The memory stores programs or instructions that can run on the processor, and when the program or instructions are executed by the processor, they implement the steps of the above-described message notification method.

[0017] Fourthly, embodiments of this application provide a computer-readable storage medium storing a program or instructions, which, when executed by a processor, implement the steps of the aforementioned message notification method.

[0018] As can be seen from the technical solutions provided by the above embodiments of this application, the embodiments of this application acquire multiple tag data, wherein the tag data includes list identifiers and tag information, and the tag data is used to indicate that the tag information of the list indicated by the list identifier has changed; based on the list identifier, associated tag data that is related to the target list in the multiple tag data is determined; based on the tag information corresponding to the associated tag data, at least one candidate tag of the target list is determined, and the tag that meets the preset conditions among the at least one candidate tag is determined as the target tag; when the target tag meets the reminder triggering conditions, a reminder message is sent to the front end. In this way, when the tag information of the list (such as credit rating, registration information, business processing status, etc.) changes, the tag data can be associated with the target list, and when the target tag corresponding to the target list meets the reminder triggering conditions, a reminder message is sent to the front end, so that the front end can follow up on the target list in a timely manner, thereby improving the timeliness of important tag reminders, avoiding the situation of missing important and urgent matters due to untimely message reminders, and improving service quality. Attached Figure Description

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

[0020] Figure 1 A flowchart illustrating a message notification method provided in an embodiment of this application is shown;

[0021] Figure 2 A flowchart illustrating the method for determining the correspondence between tags and scores provided in an embodiment of this application is shown.

[0022] Figure 3 Another flowchart of the message notification method provided in this application embodiment is shown;

[0023] Figure 4 This illustration shows one of the structural schematic diagrams of the message notification device provided in an embodiment of this application;

[0024] Figure 5 A second schematic diagram of the structure of the message notification device provided in this application embodiment is shown;

[0025] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

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

[0027] Figure 1 This illustration shows a flowchart of a message notification method provided in an embodiment of this application. The execution subject of this method can be a workstation robot, a terminal device, or a server. The terminal device can be a personal computer, a mobile terminal device such as a mobile phone or tablet, or a user-used terminal device. The server can be a standalone server or a server cluster composed of multiple servers. Furthermore, the server can be a backend server for a specific business function or a backend server for a system (such as a call center system). This embodiment uses a server as the execution subject for illustration. For the case of a terminal device, the following related content can be used, and will not be elaborated further here. As shown in the figure, the message notification method 100 may include the following steps:

[0028] S101: Obtain multiple label data.

[0029] The tag data includes list identifiers and tag information. Tag data is used to indicate changes in the tag information of the list indicated by the list identifier. Specifically, tag data can be data describing changes in some attribute information or behavioral events corresponding to the list. For example, event data related to the business processing stage of the list, such as "application completed," "registered," or "real-name verified," or login tag data such as login time, mobile phone number, or user ID. It can also be data describing changes in the tags configured for the list, such as assigning tags like "Credit Rating A" or "Star User" to certain lists. Changes in this tag data can affect the importance of the list. For example, when a service recipient completes real-name registration, outbound services such as telephone follow-ups and questionnaires can be provided to the service recipient.

[0030] In practice, when a change in tag data is detected, the changed tag data is obtained in real time. The tag data includes list identifiers and tag information. The list identifiers can be used to associate the tag information with the corresponding target list, so as to update the tag information corresponding to the target list. Here, the tag information is used to represent the tag corresponding to the change in list information. It can be a text tag such as "star-rated user" or "real-name authenticated", or a tag code such as mobile phone number, user ID, login time, etc.

[0031] S102: Based on the list identifier, determine the associated tag data among multiple tag data that is related to the target list in the preset database;

[0032] In specific implementation, based on the list identifier in the tag data obtained in S101 above, the tag data is associated with the target list in the preset database and stored. If there is no target list in the preset database corresponding to the list identifier, the tag data is ignored; if there is a target list in the preset database corresponding to the list identifier, the tag data is associated with the target list and stored, so that the associated tag data associated with the target list can be queried based on the target list.

[0033] S103: Based on the tag information corresponding to the associated tag data, determine at least one candidate tag of the target list, and determine the tag that meets the preset conditions among the at least one candidate tag as the target tag of the target list.

[0034] In practical implementation, there are many types of tag information. If all tag information is reminded on the front end, it will affect the processing progress of the current front end. To this end, this application embodiment determines at least one candidate tag of the target list based on the tag information corresponding to the associated tag data, determines the target tag of the target list from the candidate tags, and then sends a front end message reminder to the target tag. Specifically, it can determine whether the tag corresponding to the tag information is a target tag based on the category of the tag information. For example, the tag configured for the list is determined as the target tag, while other tags besides those configured for the list (such as "user login time") are not considered target tags. Alternatively, it can determine the score corresponding to the tag information; when the score is higher than a set threshold, the tag corresponding to the tag information is determined as the target tag. In this way, target tags representing changes in important and urgent matters can be sent to the front end without affecting the processing progress of front end matters, thereby avoiding the omission of important and urgent matters.

[0035] S104: If the target tag meets the reminder triggering conditions, send a reminder message to the front end.

[0036] In practice, after identifying the target tags corresponding to the target list, considering various influencing factors such as the target list may have already been followed up, the target list may have reached its recent call frequency limit, or other target tags corresponding to the target list may have just been alerted, it is also necessary to determine whether the target tag meets the alert triggering conditions. If the target tag meets the alert triggering conditions, an alert message is sent to the front end to make the message alert time more flexible and reasonable.

[0037] Through the above steps, when the tag information (such as credit rating, registration information, business processing status, etc.) of the list changes, the tag data is associated with the target list. When the target tag corresponding to the target list meets the reminder trigger condition, a reminder message is sent to the front end, so that the front end can follow up and process the target list in a timely manner. In this way, important tag information is reminded without affecting the current processing of the front end, avoiding the omission of important and urgent matters due to untimely message reminders, and improving service quality.

[0038] In this embodiment of the application, as an optional implementation, in S101, multiple tag data are acquired, including:

[0039] Receive raw tag data sent by the upstream system in real time;

[0040] According to the preset data cleaning rules, the original label data is cleaned, and the data format of the target field in the cleaned original label data is converted into the preset format to obtain the label data.

[0041] In practice, the raw tag data sent by the upstream system typically contains attribute information across multiple fields, such as list identifier ID, tag code, tagging time, and tag source. The raw tag data is cleaned using preset data cleaning rules. For example, attribute information such as tagging time and tag source is filtered out, while attribute information such as list identifier ID and tag code is retained. Here, the data of the corresponding fields in the raw tag data can be retained according to actual needs. Furthermore, the data format of the target field is converted to a preset format. Taking the list identifier ID as an example, if the obtained list identifier ID is of type String, but the database stores it as type Integer, its format can be converted to match the target list in the database. In this way, the obtained tag data matches the storage type of the database, which is beneficial for subsequent association and storage with the target list, and for the front end to obtain the tag data corresponding to the target list.

[0042] In this embodiment of the application, as an optional implementation, in S103, determining the tags that meet the preset conditions among the at least one candidate tags as target tags of the target list includes:

[0043] Obtain the pre-stored correspondence between tags and scores, and the tag threshold; the score is used to characterize the importance of the tag; determine the target score corresponding to the at least one candidate tag according to the correspondence between the tag and the score; and determine the tags among the at least one candidate tags whose target scores are higher than the tag threshold as the target tags of the target list.

[0044] In specific implementation, this application embodiment first obtains the pre-stored correspondence between tags and scores, and the tag threshold. Target tags are configured using a data dictionary approach, i.e., the pre-stored correspondence between tags and scores, with each tag corresponding to a score. Tags and their corresponding scores are stored in the data dictionary. Candidate tags corresponding to the target list are then matched with the tags in the data dictionary. Based on the correspondence between tags and scores, the target score corresponding to the candidate tag is determined. If the target score is higher than the tag threshold, the candidate tag is determined as the target tag. The tag threshold is a value determined based on the pre-stored scores corresponding to the tags. For example, it can be the average of the pre-stored scores corresponding to the tags, or it can be the score corresponding to the percentile value (e.g., 40%) selected from the pre-stored scores corresponding to the tags in sequence as the tag threshold.

[0045] Since the score corresponding to the candidate tag is determined by matching the candidate tag with the pre-stored tags, the score corresponding to the candidate tag can be adjusted accordingly by dynamically adjusting the pre-stored tags, which helps to improve the timeliness of the determined target tag.

[0046] To dynamically adjust target labels according to actual application scenarios, embodiments of this application provide the following correspondence between labels and scores, as well as a method for determining label thresholds, such as... Figure 2 As shown, the method may include the following steps:

[0047] S103a: Obtain multiple historical lists within a preset time period, as well as the tag data corresponding to each historical list.

[0048] In practice, a scheduled task for the target label is set at a preset time each day. The preset time can be a specific time such as 1:00 AM or 2:00 AM every day, or any time during the free time period. For example, the scheduled task can be set to start on the weekend, or it can be set to start two hours after the task ends. The start time of the scheduled task can be set according to specific needs, and there are no specific limitations here.

[0049] The scheduled task will retrieve multiple historical lists within a preset time period, as well as the tag data corresponding to each historical list. The preset time period can be set according to the actual application scenario, such as retrieving historical lists within the last 7 days, historical lists within the last month or year, or historical lists from January or February, along with the tag data corresponding to each historical list.

[0050] S103b: Sort the multiple historical lists according to the preset sorting rules and divide them into multiple segments. Determine the frequency of occurrence of each tag in each segment based on the tag data corresponding to the historical lists in each segment.

[0051] In practice, historical lists can be sorted sequentially or in reverse order based on attribute information in the tag data, such as "loan amount" or "credit rating," and divided into multiple segments. For example, the first 30% of the historical list can be designated as segment 1, the first 20%-60% as segment 2, and the last 60%-100% as segment 3. Based on the tag data corresponding to the historical lists within each segment, the frequency of each tag within that segment is determined. Typically, each historical list corresponds to multiple tags, as shown in the table below.

[0052] Table 1. Frequency of each label in different sections

[0053] Section 1 30 times 10 times 60 times … Section 2 20 times 90 times 40 times … Section 3 50 times 40 times 15 times …

[0054] S103c: For each tag, determine the score corresponding to the tag based on the frequency ratio of the tag in its segment and the weight of the segment; determine the correspondence between the tag and the score and the tag threshold based on each tag and the score corresponding to the tag.

[0055] The frequency percentage is the ratio of the frequency of the label in its segment to the total frequency of all labels in the segment.

[0056] In a specific implementation, corresponding weights can be assigned to the tag scores of different segments. For example, the weight for segment 1 is 0.45; the weight for segment 2 is 0.35; and the weight for segment 3 is 0.20. The score for each tag is determined based on the proportion of each tag's frequency of occurrence within its target segment relative to the total frequency of all tags within that target segment, and the weight corresponding to the target segment. The calculation formula is as follows:

[0057]

[0058] Among them, V m p is the score for label m; k Let L be the weight of segment k, and the weights for the three segments are 0.45, 0.35, and 0.20, respectively; mk X represents the frequency of label m within segment k; ik Let n be the frequency of label i in segment k, and n be the total number of segments.

[0059] Taking label A as an example, its corresponding score is (30 / (30+10+60)*0.45)+(20 / (20+90+40)*0.35)+(50 / (50+40+15)*0.20)=0.277. The score for each label is calculated and updated in the data dictionary. The labels are then sorted according to their scores, and the 40th percentile is used as the label threshold. Taking 10 labels as an example, the correspondence between the labels and their scores is shown in the table below:

[0060] Table 2. Correspondence between labels and scores

[0061] Tag 1 0.522 Tag 2 0.500 Tag 3 0.411 Tag 4 0.348 Tag 5 0.323 Tag 6 0.229 Tag 7 0.223 Tag 8 0.126 Tag 9 0.123 Tag 10 0.113

[0062] As shown in the table, the label threshold is its 40th percentile, which is 0.348. Candidate labels with a score greater than 0.348 are identified as target labels.

[0063] In this embodiment of the application, as an optional implementation, the target tag can be determined to meet the reminder triggering conditions in the following ways:

[0064] The first determination method is to obtain the call record information of the target list corresponding to the target tag; if the call record information meets the pre-set call frequency control rules, determine that the target tag meets the reminder triggering conditions.

[0065] For example, if the pre-set call frequency control rule is 3 times in 1 day and 4 times in 2 days; if the call record information of this list shows that it has already been dialed 2 times on the current day and 2 times the previous day, then it has dialed a total of 4 times in two days. If it calls again, it will exceed the call frequency control rule of 4 times in 2 days, and the target tag does not meet the reminder triggering condition. However, if it has already been dialed 1 time on the current day and 2 times the previous day, it has dialed a total of 3 times in two days. If it calls again, it will still meet the call frequency control rule of 4 times in 2 days, and the target tag meets the reminder triggering condition.

[0066] The second determination method is to obtain the follow-up status of the historical tags in the target list corresponding to the target tag; if the follow-up status of the historical tags is "followed up", then determine that the target tag meets the reminder triggering conditions.

[0067] In practice, the same target list often corresponds to multiple target tags. If a reminder is sent for each target tag, it will affect the processing progress of the current task on the front end. Therefore, in order to improve the effectiveness of message reminders, if there is a historical tag that has already been reminded and is in an unfollowed state, then subsequent target tags do not need to be reminded again; if the historical tag is in a followed state, then the target tag is determined to meet the reminder triggering condition, and a reminder message is sent to the front end.

[0068] The third determination method is to obtain the follow-up status of the target follow-up list, wherein the tag corresponding to the target follow-up list belongs to the same tag category as the target tag; if the follow-up status of the target follow-up list is "followed up", then the target tag is determined to meet the reminder triggering condition.

[0069] In practice, the front end will correspond to multiple lists to be followed up. If a reminder is given for every tag on a target list that arrives, it will frequently disrupt the processing progress of the current task. To address this, the tag category of the target tag is determined. If two target lists have the same tag category, only the first target list meets the reminder trigger condition. When the second target list arrives, if the first target list that has already been reminded has not yet been followed up, it will not be reminded again, but will be stored in the list to be followed up. Such lists can be queried and followed up through the front end page. If the first list is already followed up, the target tag meets the reminder trigger condition, and a reminder message is sent to the front end.

[0070] The fourth determination method: if the reminder trigger time of the target list corresponding to the target tag is within the preset target time period, and the follow-up status of the target list is not followed up, then the target tag is determined to meet the reminder trigger condition.

[0071] In practice, for a specific target list, if it has just been followed up recently (this time threshold can be configured as needed, such as within 1 hour), then the front-end can be notified to follow up again after a certain period of time. For example, if the target tag arrives in the system at night, a delayed reminder can be set up to send a message the next morning. For such messages, they can be sent to a delayed queue for later notification.

[0072] In this embodiment of the application, as an optional implementation, in S104, sending the reminder message to the front end includes:

[0073] Save the target list corresponding to the target tag and identify the reminder record of the target list; send the tag information corresponding to the target list to the Kafka message queue so that the front end can retrieve reminder messages from the Kafka message queue for consumption.

[0074] In practice, the target list corresponding to the target tag is first stored in a follow-up table to facilitate subsequent tracking and recording of the processing status information of the target list. A reminder record for the target list is also created to indicate that the target tag has been reminded to the front end. If the front end is an agent robot, the agent robot to which the target tag belongs is queried based on the list tag to obtain its email address and other relevant information. The number of follow-up lists for each agent robot in the follow-up table is then checked, and the target tag and list information are notified to that agent robot. Next, the tag information corresponding to the target list is sent to the Kafka message queue. Each agent robot's logged-in web application instance server consumes the messages from Kafka, queries the instance's WebSocket cache information, and if it exists, obtains the corresponding WebSocket connection based on the agent's email address and notifies the front end page, displaying a pop-up notification at a designated location on the front end page; if it does not exist, the message is ignored.

[0075] In this embodiment of the application, as an optional implementation, after sending the reminder message to the front end in S104, the method further includes:

[0076] Based on the currently executing list of follow-up requests, determine the follow-up status of the target list corresponding to the reminder message; control the front end to perform the corresponding operation according to the follow-up status.

[0077] The follow-up status includes ignore, immediate execution, and follow-up later. In specific implementation, when the follow-up status is ignore, the control frontend deletes the reminder message corresponding to the target tag and does not send the target list to the follow-up list. When the follow-up status is immediate follow-up, the control frontend jumps to the workbench panel and executes the call operation based on the information in the target list. Alternatively, when the follow-up status is follow-up later, the control frontend hides the display box corresponding to the reminder message and displays the number of the list to be followed in a designated area of ​​the frontend (such as the upper right corner). In response to the frontend's query operation on the target list in the follow-up list, the target list corresponding to the target list is displayed and the follow-up operation is executed.

[0078] In specific implementation, such as Figure 3 As shown, the message notification method provided in this application embodiment may include the following steps:

[0079] Step 1: Consume tag data pushed from the upstream system of Kafka. This tag data is used to indicate that the tag information of the list indicated by the list identifier has changed;

[0080] Step 2: Perform data cleaning, format conversion, and other standard verification on the label data to obtain label data that meets the standard requirements;

[0081] Step 3: Tag data includes list identifier ID and tag information. Based on the list identifier ID, query the preset database to see if there is a target list associated with the tag data. If there is a target list associated with the tag data in the database, the tag data is written to the database and stored in the tag table corresponding to the target list; if there is no target list associated with the tag data in the database, the tag data is ignored.

[0082] Step 4: After storing the tag data in the tag table corresponding to the target list, determine whether the tag corresponding to the target list is a high-value tag (target tag). If the tag corresponding to the target list is a high-value tag, send a reminder message to the front end; if the tag corresponding to the target list is not a high-value tag, only store it in the database. If the front end actively queries the target list, display the tag corresponding to the target list for reference.

[0083] Step 5: If the tag corresponding to the target list is determined to be a high-value tag, the alert triggering conditions can be determined by checking whether the high-value tag meets the alert triggering conditions (such as whether the call record information of the target list complies with the call frequency control rules, whether the database already contains a similar alert for the target list, and whether the follow-up table contains a similar alert). If the high-value tag meets the alert triggering conditions, an alert message is sent to the front end; if the high-value tag requires a delayed alert, the alert message corresponding to the high-value tag is stored in the delayed alert queue.

[0084] Step 6: For high-value tags that meet the alert trigger conditions, implement the real-time notification process for the front end. First, store the target list and corresponding high-value tags in the agent alert follow-up table for easy tracking and recording of agent follow-up on the list. Then, save an agent alert record to indicate that the list tag has been alerted to an agent. Further, query the agent to which the follow-up list ID belongs to obtain the agent's email address and other relevant information. Query the number of lists to be followed up by agents in the follow-up table, assemble the tag and list information to be notified to the agents, and push this information to Kafka. Further still, the web application instance server logged into by each agent consumes the message from Kafka, queries the WebSocket cache information in the instance, and if it exists, obtains the corresponding WebSocket connection based on the agent's email address and notifies the front end page; if it does not exist, ignore the message and change the status of each related table (such as the agent alert follow-up table and agent alert record table).

[0085] Step 7: After receiving the reminder message, the front-end page can determine the follow-up strategy and follow-up status (such as ignore status, immediate execution status, or follow-up later status) of the target list corresponding to the reminder message based on the currently executing follow-up list, and control the front-end to perform the corresponding operation according to the follow-up strategy and follow-up status.

[0086] By employing the above method, when the tag information of the list changes, the tag data can be linked to the target list. Furthermore, when the target tag corresponding to the target list meets the alert trigger conditions, an alert message is sent to the front end. This allows the front end to promptly follow up on the target list, improving the timeliness of important tag alerts and preventing the omission of important and urgent matters due to untimely message alerts. Additionally, the front end can flexibly select the follow-up status of the target list based on the currently executing list follow-up list, ensuring orderly processing of list follow-up matters and thus improving list processing efficiency.

[0087] Figure 4 This illustration shows one of the structural schematic diagrams of a message notification device provided in an embodiment of this application. This motion state recognition device can achieve, for example... Figure 1 , Figure 2 , Figure 3 In any of the embodiments shown, the message notification device 400 includes all or part of the following:

[0088] The data acquisition module 410 is used to acquire multiple tag data, the tag data including list identifiers and tag information, and the tag data is used to indicate that the tag information of the list indicated by the list identifier has changed;

[0089] The association determination module 420 is used to determine, based on the list identifier, the associated tag data among multiple tag data that is associated with the target list in the preset database;

[0090] The tag determination module 430 is used to determine at least one candidate tag of the target list based on the tag information corresponding to the associated tag data, and to determine the tag that meets the preset conditions among the at least one candidate tag as the target tag of the target list;

[0091] The message notification module 440 is used to send a notification message to the front end when the target tag meets the notification triggering conditions.

[0092] As an optional implementation, the data acquisition module 410 includes:

[0093] The receiving unit is used to receive raw tag data sent by the upstream system in real time;

[0094] The processing unit is used to perform data cleaning on the original label data according to preset data cleaning rules, and to convert the data format of the target field in the original label data after data cleaning into a preset format to obtain the label data.

[0095] As an optional implementation, the tag determination module 430 includes:

[0096] An acquisition unit is used to acquire the pre-stored correspondence between tags and scores, and tag thresholds; the scores are used to characterize the importance of the tags.

[0097] The first determining unit is used to determine the target score corresponding to the at least one candidate label based on the correspondence between the label and the score.

[0098] The second determining unit is used to determine the tags whose target scores are higher than the tag threshold among the at least one candidate tags as target tags in the target list.

[0099] As an optional implementation, when the acquisition unit is used to acquire the pre-stored correspondence between tags and scores and the tag threshold, it is specifically used for:

[0100] Obtain multiple historical lists within a preset time period, along with tag data corresponding to each historical list; sort the multiple historical lists according to a preset sorting rule and divide them into multiple segments; determine the frequency of occurrence of each tag within each segment based on the tag data corresponding to the historical lists within each segment; for each tag, determine the score corresponding to the tag based on the proportion of the tag's frequency of occurrence within its segment and the weight corresponding to its segment; the proportion of the frequency of occurrence is the ratio of the frequency of occurrence of the tag within its segment to the sum of the frequencies of occurrence of all tags within its segment; determine the correspondence between tags and scores and the tag threshold based on each tag and its corresponding score.

[0101] As an optional implementation, when determining that the target tag meets the reminder triggering conditions, the message notification module 440 is specifically used for:

[0102] Obtain the call record information of the target list corresponding to the target tag;

[0103] If the call record information conforms to the pre-set call frequency control rules, the target tag is determined to meet the reminder triggering conditions.

[0104] As an optional implementation, when determining that the target tag meets the reminder triggering conditions, the message notification module 440 is specifically used for:

[0105] Obtain the tracking status of historical tags in the target list corresponding to the target tag;

[0106] If the historical tag is in the "followed" state, the target tag is determined to meet the reminder triggering conditions.

[0107] As an optional implementation, when determining that the target tag meets the reminder triggering conditions, the message notification module 440 is specifically used for:

[0108] Obtain the follow-up status of the target follow-up list, wherein the tags corresponding to the target follow-up list belong to the same tag category as the target tag;

[0109] If the follow-up status of the target follow-up list is "followed up", then the target tag is determined to meet the reminder triggering condition.

[0110] As an optional implementation, when determining that the target tag meets the reminder triggering conditions, the message notification module 440 is specifically used for:

[0111] If the reminder trigger time of the target list corresponding to the target tag is within the preset target time period, and the follow-up status of the target list is in the non-follow-up status, then the target tag is determined to meet the reminder trigger condition.

[0112] As an optional implementation, when the message notification module 440 is used to send a notification message to the front end, it is specifically used for:

[0113] Save the target list corresponding to the target tag, and mark the reminder record of the target list;

[0114] The tag information corresponding to the target list is sent to the Kafka message queue so that the front end can retrieve the reminder message from the Kafka message queue for consumption.

[0115] This application provides a message reminder device, including a data acquisition module, an association determination module, a tag determination module, and a message reminder module. When the tag information (such as credit rating, registration information, business processing status, etc.) of a list changes, the data acquisition module acquires tag data, which includes a list identifier and tag information. The association determination module determines the associated tag data among multiple tag data that is associated with a target list in a preset database based on the list identifier. The tag determination module determines at least one candidate tag of the target list based on the tag information corresponding to the associated tag data, and determines the tag that meets the preset conditions among the at least one candidate tag as the target tag of the target list. Then, when the target tag meets the reminder triggering conditions, the message reminder module sends a reminder message to the front end so that the front end can promptly follow up on the target list. In this way, the timeliness of important tag reminders can be improved, avoiding the omission of important and urgent matters due to untimely message reminders, and improving service quality.

[0116] Figure 5 The second schematic diagram of the message notification device provided in this application embodiment is shown. This motion state recognition device can achieve the following: Figure 1 , Figure 2 , Figure 3 In any of the embodiments shown, the message notification device 500 includes all or part of the following:

[0117] The data acquisition module 510 is used to acquire multiple tag data, the tag data including list identifiers and tag information, and the tag data is used to indicate that the tag information of the list indicated by the list identifier has changed;

[0118] The association determination module 520 is used to determine, based on the list identifier, the associated tag data among multiple tag data that is associated with the target list in the preset database;

[0119] The tag determination module 530 is used to determine at least one candidate tag of the target list based on the tag information corresponding to the associated tag data, and to determine the tag that meets the preset conditions among the at least one candidate tag as the target tag of the target list;

[0120] The message notification module 540 is used to send a notification message to the front end when the target tag meets the notification triggering conditions;

[0121] The operation control module 550 is used to determine the follow-up status of the target list corresponding to the reminder message based on the currently executing list follow-up list; the control front end executes the corresponding follow-up operation according to the follow-up status.

[0122] The follow-up status includes ignore, immediate follow-up, and follow-up later status. When the follow-up status is ignore, the control frontend deletes the reminder message corresponding to the target tag. When the follow-up status is immediate follow-up, the control frontend jumps to the workbench panel and performs a call operation based on the information in the target list. Alternatively, when the follow-up status is follow-up later, the control frontend hides the display box corresponding to the reminder message and displays the number of the list to be followed in a specified area of ​​the frontend (such as the upper right corner). In response to the frontend's query operation on the target list in the list to be followed, the target list corresponding to the target list is displayed and the follow-up operation is performed.

[0123] This application provides a message notification device, including a data acquisition module, an association determination module, a tag determination module, a message notification module, and an operation control module. When the tag information (such as credit rating, registration information, business processing status, etc.) of a list changes, the data acquisition module acquires multiple tag data, which include a list identifier and tag information. The association determination module determines, based on the list identifier, associated tag data among the multiple tag data that is related to a target list in a preset database. The tag determination module determines at least one candidate tag for the target list based on the tag information corresponding to the associated tag data, and identifies the tag among the candidate tags that meets preset conditions as the target. The target tag of the list; when the target tag meets the reminder trigger condition, the message reminder module sends a reminder message to the front end. The operation control module determines the follow-up strategy of the target list corresponding to the reminder message based on the currently executing list follow-up list; and controls the front end to execute the corresponding operation according to the follow-up strategy. In this way, the timeliness of important tag reminders can be improved, avoiding the omission of important and urgent matters due to untimely message reminders. At the same time, the front end can flexibly select the follow-up strategy of the target list according to the currently executing list follow-up list, ensuring the orderly processing of list follow-up matters, thereby improving the efficiency of list processing.

[0124] Figure 6The diagram illustrates the hardware structure of a computer device implementing the embodiments of this application. Referring to the diagram, at the hardware level, the electronic device includes a processor and optionally, an internal bus, a network interface, and memory. The memory may include RAM, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk storage device. Of course, the computer device may also include other hardware required for other business operations.

[0125] The processor, network interface, and memory can be interconnected via an internal bus, which can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only a single bidirectional arrow is used in this diagram, but this does not imply that there is only one bus or one type of bus.

[0126] The memory stores the message notification device, which includes one or more programs. Specifically, the program may include program code, which includes computer operation instructions. The memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0127] The processor reads the corresponding computer program from non-volatile memory into main memory and then runs it, logically forming a device that locates the target user. The processor executes the program stored in memory and specifically performs the following: Figure 1 , Figure 2 or Figure 3 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0128] The above is as stated in this application. Figure 1 , Figure 2 or Figure 3The methods disclosed in the illustrated embodiments can be implemented in or by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0129] The computer device can also execute the methods described in the preceding method embodiments and achieve the functions and beneficial effects of the methods described in the preceding method embodiments, which will not be repeated here.

[0130] Of course, in addition to software implementation, the electronic device of this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0131] This application also proposes a computer-readable storage medium that stores one or more programs, which, when executed by an electronic device including multiple applications, cause the electronic device to perform... Figure 1 , Figure 2 or Figure 3 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0132] The computer-readable storage medium includes read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc.

[0133] Furthermore, embodiments of this application also provide a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, which, when executed by a computer, implement the following process: Figure 1 , Figure 2 or Figure 3 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods described in the preceding method embodiments, and will not be repeated here.

[0134] In summary, the above description is merely a preferred embodiment of this application and does not limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

[0135] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0136] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can store information accessible to a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0137] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0138] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

Claims

1. A message notification method, characterized in that, include: Acquire multiple tag data, the tag data including list identifiers and tag information, the tag data being used to indicate that the tag information of the list indicated by the list identifier has changed; Based on the list identifier, identify the associated tag data among multiple tag data that is related to the target list in the preset database; Based on the tag information corresponding to the associated tag data, at least one candidate tag of the target list is determined, and tags among the at least one candidate tags that meet preset conditions are determined as target tags of the target list; wherein, determining tags among the at least one candidate tags that meet preset conditions as target tags of the target list includes: obtaining a pre-stored correspondence between tags and scores and a tag threshold; the score is used to characterize the importance of the tag; determining the target score corresponding to the at least one candidate tag based on the correspondence between the tag and the score; and determining tags among the at least one candidate tags whose target scores are higher than the tag threshold as target tags of the target list; If the target tag meets the reminder triggering conditions, a reminder message is sent to the front end.

2. The method according to claim 1, characterized in that, The process of obtaining the pre-stored correspondence between tags and scores, and the tag threshold, includes: Retrieve multiple historical lists within a preset time period, as well as the tag data corresponding to each historical list; The historical lists are sorted according to a preset sorting rule and divided into multiple segments. The frequency of occurrence of each tag in each segment is determined based on the tag data corresponding to the historical lists in each segment. For each tag, the score corresponding to the tag is determined based on the proportion of the frequency of the tag in its segment and the weight of the segment; the proportion of the frequency of the tag is the ratio of the frequency of the tag in its segment to the sum of the frequencies of all tags in the segment. Based on each label and its corresponding score, determine the correspondence between the label and the score, and the label threshold.

3. The method according to claim 1, characterized in that, The target tag meets the alert triggering conditions, including: Obtain the call record information of the target list corresponding to the target tag; If the call record information conforms to the pre-set call frequency control rules, the target tag is determined to meet the reminder triggering conditions.

4. The method according to claim 1, characterized in that, The target tag meets the alert triggering conditions, including: Obtain the tracking status of historical tags in the target list corresponding to the target tag; If the historical tag is in the "followed" state, the target tag is determined to meet the reminder triggering conditions.

5. The method according to claim 1, characterized in that, The target tag meets the alert triggering conditions, including: Obtain the follow-up status of the target follow-up list, wherein the tags corresponding to the target follow-up list belong to the same tag category as the target tag; If the follow-up status of the target follow-up list is "followed up", then the target tag is determined to meet the reminder triggering condition.

6. The method according to claim 1, characterized in that, The target tag meets the alert triggering conditions, including: If the reminder trigger time of the target list corresponding to the target tag is within the preset target time period, and the follow-up status of the target list is in the non-follow-up status, then the target tag is determined to meet the reminder trigger condition.

7. The method according to claim 1, characterized in that, Sending the reminder message to the front end includes: Save the target list corresponding to the target tag, and mark the reminder record of the target list; The tag information corresponding to the target list is sent to the Kafka message queue so that the front end can retrieve the reminder message from the Kafka message queue for consumption.

8. A message notification device, characterized in that, include: The data acquisition module is used to acquire multiple tag data, the tag data including list identifiers and tag information, and the tag data is used to indicate that the tag information of the list indicated by the list identifier has changed; The association determination module is used to determine, based on the list identifier, the associated tag data among multiple tag data that is associated with the target list in the preset database; A tag determination module is used to determine at least one candidate tag of the target list based on tag information corresponding to the associated tag data, and to determine the tags among the at least one candidate tags that meet preset conditions as target tags of the target list; wherein, the tag determination module is specifically used to: obtain a pre-stored correspondence between tags and scores and a tag threshold; the score is used to characterize the importance of the tag; determine the target score corresponding to the at least one candidate tag based on the correspondence between the tag and the score; and determine the tags among the at least one candidate tags whose target scores are higher than the tag threshold as target tags of the target list; The message notification module is used to send a notification message to the front end when the target tag meets the notification triggering conditions.

9. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1 to 7.

10. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 7.

Images