Declaration-free processing method and apparatus for application cases, electronic device and computer-readable storage medium

Abstract

Disclosed in the embodiments of the present specification are a declaration-free processing method and apparatus for application cases and an electronic device. The declaration-free processing method for application cases comprises: when a case application request has been received, acquiring user material information of a target user, and performing comparison on the user material information and declaration information corresponding to a current case of the target user; then, when the user material information does not match the declaration information, omitting a declaration information confirmation process of the current case, extracting keyword information from current application materials of the current case, and adding the keyword information into the user material information; and when the user material information matches the declaration information, sending the declaration information to the target user.

Description

Method, device, electronic device, and computer-readable storage medium for handling application cases without notification Technical Field

[0001] The embodiments of this specification belong to the field of data processing technology, and in particular, relate to a method, device, and electronic device for processing application cases without notification. Background Art

[0002] When processing some applications (e.g., insurance applications, employment applications, and admissions applications), the applicant may issue a notice based on the applicant's specific circumstances. This notice contains a disclaimer regarding specific circumstances. The applicant must confirm and sign this notice based on their specific circumstances before their application can be approved.

[0003] However, some applicants may submit multiple applications for a certain category of applicants based on their actual circumstances and needs. Having to confirm the same notification letter each time will not only affect application efficiency but also the applicant's application experience.

[0004] Summary of the Invention

[0005] The embodiments of this specification provide a method, device, and electronic device for handling application cases without notification, and the technical solution is as follows.

[0006] In the first aspect, an embodiment of the present specification provides a method for processing application cases without notification, including: when receiving a case application request, obtaining user material information of a target user, and comparing the notification information corresponding to the current case of the target user based on the user material information, the user material information includes historical keyword information extracted from a first historical application material, and the first historical application material includes the application materials of the target user in historical cases; when the user material information does not match the notification information, the notification information confirmation process of the current case is waived, and keyword information is extracted from the current application materials of the current case, and the keyword information is added to the user material information; when the user material information matches the notification information, the notification information is sent to the target user.

[0007] On the second aspect, an embodiment of the present specification provides a notification-free processing device for application cases, including: an acquisition module, used to obtain user material information of a target user when receiving a case application request, and compare the notification information corresponding to the current case of the target user based on the user material information, the user material information including historical keyword information extracted from a first historical application material, and the first historical application material including the application materials of the target user in the historical case; a first judgment module, used to exempt the notification information confirmation process of the current case when the user material information does not match the notification information, and extract keyword information from the current application material of the current case, and add the keyword information to the user material information; a second judgment module, used to send the notification information to the target user when the user material information matches the notification information.

[0008] On the third aspect, the embodiments of this specification also provide an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the steps of the above-mentioned method for handling the application case without notification.

[0009] Fourthly, an embodiment of this specification provides a computer storage medium, which stores a plurality of instructions suitable for being loaded by a processor and executing the steps of the above-mentioned method for handling the application case without notification.

[0010] The beneficial effects of the technical solutions provided by some embodiments of this specification include at least the following: In one or more embodiments of this specification, when a user applies for medical insurance, for example, the user's application materials, obtained by summarizing keyword information from the user's previous application materials, can be compared with the user's current application information to determine whether the user can be exempted from disclosure. If the user can be exempted from disclosure, the disclosure information confirmation process is eliminated, thereby improving application efficiency and the user's application experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of this specification, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0012] FIG1 is a schematic diagram of the system architecture of a method for handling application cases without notification provided in an embodiment of this specification.

[0013] FIG2 is a flow chart of a method for handling an application case without notification provided in an embodiment of this specification.

[0014] FIG3 is a flowchart of another method for handling an application case without notification provided in an embodiment of this specification.

[0015] FIG4 is a flowchart of another method for handling an application case without notification provided in an embodiment of this specification.

[0016] FIG5 is a schematic diagram of the structure of a device for processing an application case without notification provided in an embodiment of this specification.

[0017] FIG6 is a schematic structural diagram of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0018] The technical solutions in the embodiments of this specification will be described clearly and completely below in conjunction with the drawings in the embodiments of this specification.

[0019] Throughout this specification, the claims, and the accompanying drawings, the terms "first," "second," "third," and the like are used to distinguish between different items, not to describe a particular order. Furthermore, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements but may optionally include steps or elements not listed, or may include other steps or elements inherent to the process, method, product, or apparatus.

[0020] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements described without departing from the scope of this specification. Various examples may appropriately omit, replace, or add various processes or components. For example, the described methods may be performed in an order different from the order described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in other examples.

[0021] First, some of the embodiments of the present application will be explained below to facilitate understanding by those skilled in the art.

[0022] Health declaration form: refers to the health declaration form that insurance companies require customers to fill out when accepting their insurance applications, which is a description of their health conditions.

[0023] The Graph Health Initiative transforms healthcare data into interoperable, semantically consistent data that can be shared and understood by diverse systems and applications. By building a unified data graph, healthcare providers, research institutions, technology developers, and others can better utilize and analyze data to improve healthcare quality, reduce costs, and foster innovation.

[0024] Named Entity Recognition (NER): It is a task in natural language processing that aims to identify and classify named entities from text, such as names of people, places, organizations, dates, times, etc.

[0025] Optical Character Recognition (OCR) is a technology that converts printed or handwritten text into machine-processable text.

[0026] Please refer to FIG1 , which shows a schematic diagram of the system architecture of a method for handling application cases without notification provided in an embodiment of this specification.

[0027] As shown in FIG1 , the system architecture of the notification-free processing method of the application case may include at least a terminal 100 , a server 200 and a network 300 .

[0028] Terminal 100 includes, but is not limited to, electronic devices such as smartphones, desktop computers, tablet computers, laptops, smart speakers, digital assistants, and smart wearable devices. It may also be software running on these electronic devices, such as an application. Optionally, the operating system running on the electronic device may include, but is not limited to, Android, iOS, Linux, and Windows. Optionally, terminal 100 provides users with a service for processing case applications without notification. Terminal 100 may obtain operating instructions from an application program interface and send a case application request to server 200.

[0029] Server 200 can provide backend services for Terminal 100. Based on the case application request sent by Terminal 100, it compares the notification information with the target user's user material information, determines whether the target user can be exempted from the notification information confirmation process, and if so, extracts keyword information from the current application materials. Specifically, Server 200 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0030] The network 300 is used to provide a medium for a communication link between the terminal 100 and the server 200. The network 300 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0031] In addition, it should be noted that what is shown in FIG1 is only a system provided by the present disclosure. In practical applications, other systems may also be included, for example, more terminals may be included.

[0032] In the embodiments of this specification, the terminal 100 and the server 200 may be directly or indirectly connected via wired or wireless communication, which is not limited in this disclosure.

[0033] Next, please refer to Figure 2, which shows an overall flow chart of a method for processing an application case without notification provided in an embodiment of this specification. The method for processing an application case without notification can be used in a server.

[0034] As shown in FIG2 , the method for handling the application case without notification may include at least the following steps.

[0035] Step 201: upon receiving a case application request, obtaining user material information of a target user, and comparing notification information corresponding to the current case of the target user based on the user material information.

[0036] The user material information includes historical keyword information extracted from first historical application materials, and the first historical application materials include application materials of the target user in historical cases.

[0037] Specifically, when the target user wants to apply for a case, he or she can generate a case application request by operating in the corresponding program window interface of the terminal. After the server receives the case application request, it can determine the user information of the target user who sent the case application request in the database, and query the user material information of the target user based on the user information. The user material information can be historical keyword information extracted from the first historical application material submitted by the target user in the application process of the historical case. The historical keyword information may include health information, disease information, educational information, grade information, etc. in the application materials. These historical keyword information can be used to characterize the actual situation of the target user himself or herself. The server will obtain the notification information of the current case that the target user is applying for, that is, the case application request, and compare the notification information with the user material information, and then determine whether the target user can be exempted from confirming the notification information during the application process of the current case.

[0038] As an example, for insurance application cases, the corresponding notification information may be the health notification information corresponding to the health notification form. The health notification information may specifically include an explanation and exemption of the health conditions that the user needs to protect himself in this insurance. When the user attempts to make an insurance claim due to the health conditions exempted in the health notification information, the claim will not be made.

[0039] In the case of insurance applications, the user's profile information can specifically be Tupu Health Facts. The user's profile information may include information on surgeries performed by the target user at various hospitals, disease consultation information, and so on. The health disclosure information may include information on surgeries and diseases that are not covered by this type of insurance. If the user's profile information matches the health disclosure information, it means that the user's profile information contains information on surgeries, diseases, etc. that are not covered by this type of insurance. In this case, the disclosure information confirmation process cannot be waived, and the target user must personally confirm whether they still want to apply for this type of insurance despite knowing this. If the user's profile information does not match the health disclosure information, it means that the user's profile information does not contain information on surgeries, diseases, etc. that are not covered by this type of insurance, and the disclosure information confirmation process can be waived.

[0040] As another example, for a job application, the corresponding notification information may specifically include some work experience, work ability and other requirements that need to be met to complete the job normally. When the user's own ability information corresponding to the user's material information cannot match the requirements, the user will need to personally confirm the notification information and confirm whether he or she still wants to apply.

[0041] As another example, for an application for admission, the corresponding notification information may specifically include test scores for designated subjects, subjects already studied, and other requirements. When a user's own abilities in the user's material information cannot match the requirements, the user will be required to personally confirm the notification information and confirm whether he or she still wants to apply.

[0042] In addition, other types of applications, such as employment applications and enrollment applications, can also be classified as insurance applications, such as enrollment insurance applications and employment insurance applications, depending on the actual situation. In other embodiments, other types of applications can also be classified, and this is not limited here.

[0043] Step 203: When the user material information does not match the notification information, the notification information confirmation process of the current case is omitted, and keyword information is extracted from the current application materials of the current case and added to the user material information.

[0044] Specifically, when the server compares the user material information with the notification information and confirms that the user material information does not match the notification information, it is considered that the corresponding personal information in the target user's previous application materials does not fall within the scope of non-protection of the current case. At this time, the server will exempt the notification information confirmation process of the current case, so that the target user does not need to confirm the notification information in the actual application operation process of the current case, thereby improving the application efficiency. In addition, in order to enrich the user material information and improve the accuracy of the process of whether the notification information is exempted in subsequent case applications, the server can also obtain the current application materials submitted by the target user to apply for the current case, perform keyword extraction on the current application materials, extract the keyword information in the current application materials, and add it to the user material information.

[0045] Keyword extraction can be performed using frequency-based methods such as TF-IDF (Term Frequency-Inverse Document Frequency) and word frequency statistics. Alternatively, a machine learning algorithm, such as support vector machines (SVM) or Naive Bayes, can be used to train models to predict keywords. Other keyword extraction methods are also possible and are not limited here.

[0046] Step 205: When the user profile information matches the notification information, the notification information is sent to the target user.

[0047] Specifically, if the server compares the user's materials with the notification information and confirms a match, it will deem the target user's previous application materials to be exempt from the current case. This means that certain circumstances of the target user fall within the exemption scope of the notification information. In this case, the server will send the target user a notification during the application process, allowing the target user to personally confirm the information and decide whether to continue applying for the case.

[0048] As an optional embodiment of this specification, the method also includes: allocating a reminder time for each keyword information in the user material information based on the keyword category; when the continuous cumulative storage time of any target keyword information in the user material information exceeds the storage time, sending an update reminder information to the target user based on the target keyword information.

[0049] Specifically, the server may pre-store a keyword category table, in which reminder durations corresponding to different keyword information are pre-set based on human experience. The server may assign a reminder duration to each keyword information in the user's profile information based on this table. If the cumulative duration of a target keyword information stored in the user's profile information exceeds this reminder duration, the server will generate an update reminder message and send it to the target user, prompting the target user to submit the latest corresponding materials to update the keyword information.

[0050] For example, in the case of an insurance application, the notification information is health information. Certain types of diseases have a greater likelihood of worsening over time. Therefore, after the reminder period expires, the target user needs to submit the latest physical examination report / interview report and other information to update the keyword information corresponding to the disease category in the user's material information. Otherwise, the keyword information will stop being used for the notification exemption process before the update to avoid misjudgment.

[0051] In an embodiment of this specification, when a user applies for medical insurance, for example, the server can compare the user's application materials, obtained by summarizing keyword information from the user's previous application materials, with the user's disclosure information for the current case, and then determine whether the user can be exempted from disclosure. If the user is eligible to be exempted from disclosure, the disclosure information confirmation process is waived, thereby improving application efficiency and the user's application experience.

[0052] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0053] As another optional embodiment of this specification, please refer to Figure 3, which shows an overall flow chart of another method for processing application cases without notification provided by the embodiment of this specification. The method for processing application cases without notification can be used in the server.

[0054] As shown in FIG3 , the method for handling the application case without notification may include at least the following steps.

[0055] Step 301: upon receiving a case application request, obtaining user material information of a target user, and comparing notification information corresponding to the current case of the target user based on the user material information.

[0056] The user material information includes historical keyword information extracted from the first historical application material, and the first historical application material includes the application material of the target user in the historical case.

[0057] Specifically, step 301 may refer to step 201 and will not be described in detail here.

[0058] Step 303: When the user material information does not match the notification information, the notification information confirmation process of the current case is omitted.

[0059] Specifically, step 303 may refer to step 203 and will not be described in detail here.

[0060] Step 305: Perform optical character recognition on the current application materials of the current case to obtain text information.

[0061] Specifically, the application materials submitted by the user can be image information obtained by scanning or taking a photo of a paper document. After receiving the application materials, the server first needs to perform optical character recognition on the current application materials to extract text information from the image information.

[0062] The specific process of optical character recognition may include the following processing.

[0063] Image preprocessing: Preprocess the input image, including denoising, binarization, image resizing, etc., to improve the accuracy of subsequent character recognition.

[0064] Text localization: Detecting and locating text regions in an image. Commonly used text localization methods include edge detection, connected region analysis, and deep learning.

[0065] Character segmentation: Segment the characters in a text region into individual characters. Character segmentation methods can be based on connected component analysis, vertical projection, deep learning-based methods, etc.

[0066] Character recognition: Recognizes individual characters after segmentation. Common character recognition methods include template matching, feature extraction (such as HOG and SIFT), and deep learning methods (such as convolutional neural networks).

[0067] Post-processing: Post-process the recognition results, such as removing erroneous recognition results, correcting recognition results, etc.

[0068] Result output: The recognition results are output in text form, which can be plain text or structured text results.

[0069] Step 307: Perform entity recognition on the text information to obtain field information.

[0070] Specifically, after the server obtains the text information, since not all text information is required by the server, it is also necessary to perform entity recognition on the text information to extract key field information from the text information.

[0071] The specific process of entity recognition may include the following processing.

[0072] Data preprocessing: Clean and tokenize the text, remove useless characters and punctuation, and divide the text into sentences or words.

[0073] Feature extraction: Based on the task requirements, appropriate features are extracted to represent the text. Common features include part of speech, word form, context, etc.

[0074] Entity candidate recognition: Use machine learning or deep learning models to identify and label entities in text. Common models include conditional random fields (CRFs), recurrent neural networks (RNNs), and sequence labeling models (such as BERT and LSTM-CRF).

[0075] Entity classification: Classify the labeled entities into different entity types, such as names of people, places, and organizations. Methods such as rule matching, dictionary matching, or model classification can be used.

[0076] Post-processing and evaluation: Perform post-processing on the recognition results, such as merging adjacent entities, removing duplicate entities, etc. Then evaluate the performance of the model, such as calculating indicators such as accuracy, recall rate, and F1 value.

[0077] Step 309: Normalize the field information to obtain keyword information.

[0078] Specifically, the field information extracted from different application materials may differ in format. To unify the obtained field information, the server can also normalize each field information to finally obtain each keyword information.

[0079] As an example, the keyword information may include the campus name of a certain hospital, the names of the departments visited, the disease diagnosis results of the departments, the surgical result information, etc.

[0080] Among them, the specific method of normalization may include the following processes.

[0081] Case conversion: Convert all letters to uppercase or lowercase to eliminate differences caused by case.

[0082] Remove punctuation marks: Remove punctuation marks in the text, such as full stops, commas, question marks, etc., to avoid the impact of punctuation marks on the text.

[0083] Remove special characters: In addition to punctuation marks, other special characters can also be removed, such as @, #, $, etc., to ensure the purity of the text.

[0084] Remove stop words: Stop words refer to words that frequently appear in the text but often lack actual meaning, such as "of", "is", "in", etc. By using a stop word library, these common stop words can be removed from the text to reduce noise and redundancy.

[0085] Stem extraction or lemmatization: By reducing words to their original forms, different word forms can be normalized to the same form. For example, convert "running" and "runs" to "run", or convert "cats" and "cat" to "cat".

[0086] Number normalization: For text containing numbers, the numbers can be uniformly converted to specific symbols or markers to abstract the specific values of the numbers.

[0087] Abbreviation expansion: For abbreviations, they can be expanded into their full forms to better understand and process the text.

[0088] Step 311: Add the keyword information to the user material information.

[0089] Specifically, for Step 311, reference can be made to Step 203, which will not be elaborated here.

[0090] Step 313: When the user profile information matches the notification information, the notification information is sent to the target user.

[0091] Specifically, step 313 may refer to step 205 and will not be described in detail here.

[0092] Step 315: When the user material information partially matches the notification information, the notification information is regenerated based on the matching part in the notification information, the regenerated notification information is sent to the target user, and keyword information is extracted from the current application materials of the current case and added to the user material information.

[0093] Specifically, in some cases, the user's application materials may partially match the notification information, meaning that the user's application materials only correspond to part of the disclaimer in the notification information. In this case, the server can regenerate a notification based on the matching portion, i.e., the portion that requires notification confirmation. This regenerated notification information is then used as the notification information that requires the target user's personal confirmation and processing in the current case processing process. In addition, the server also extracts keyword information from the current application materials for the current case to enrich the user's application materials and improve the accuracy of the next comparison.

[0094] In an embodiment of this specification, when a user applies for medical insurance, for example, the server can extract keyword information from the application materials through methods such as optical character recognition, entity recognition, and normalization. The server then compares the aggregated user information with the user's case disclosure information to determine whether the user can be exempted from disclosure. If there is only a partial match between the user's information and the disclosure information, the server will regenerate a new disclosure information based on the matching portion. This eliminates confusion among users about the inclusion of previously confirmed and signed content in the disclosure information, improving the user's application experience.

[0095] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0096] As another optional embodiment of this specification, please refer to Figure 4, which shows an overall flow chart of another method for processing application cases without notification provided by the embodiment of this specification. The method for processing application cases without notification can be used in the server.

[0097] As shown in FIG4 , the method for handling the application case without notification may include at least the following steps.

[0098] Step 401: After a preset retrieval time period, retrieve the second historical application materials newly added by the target user from the return flow data of the target platform, and query whether the second historical application materials have extracted the keyword information on the case date.

[0099] Specifically, in addition to extracting keyword information from the application materials each time the target user applies for a new case, the server will also regularly retrieve newly added second historical application materials from the reflux data from the target platform that processes the user's case application according to the preset retrieval time. It can be seen from the aforementioned process of new user application cases that the server will not necessarily extract keyword information for every new case application. In addition, for target users who have not used this system before, their historical application materials may not have keyword information extracted. Therefore, after the server retrieves the second historical application materials, it will query whether keyword information has been extracted from each second historical application material on the day the case application was made, that is, on the case date.

[0100] The second historical application materials may be the same as or different from the first historical application materials, depending on the actual situation. The target platform can be a big data computing platform (Open Data Processing Service, ODPS) or other platforms, which are not limited here.

[0101] As an optional embodiment of this specification, the query in step 401 as to whether the second historical application material has extracted the keyword information before the case date also includes: judging whether the target user can be exempted from the notification information confirmation process based on the user material information; when the target user can be exempted from the notification information confirmation process, executing the next step; when the target user cannot be exempted from the notification information confirmation process, ending the step.

[0102] Specifically, for risk control purposes, during the insurance application process, if a user has a serious illness (such as cancer), they should not be exempted from the information confirmation process to prevent unexpected situations. Therefore, the server will also determine whether the target user can be exempted from the information confirmation process based on the user's profile information. If not, the keyword information extraction is meaningless and the process will be terminated directly.

[0103] The specific method for determining whether the target user can be exempted from the notification information confirmation process can be to preset some diagnostic information as the basis for determining whether the information cannot be exempted, such as a specified disease or surgery. The server only needs to determine whether the user's material information includes diagnostic information. If diagnostic information is present, it is considered that the target user cannot be exempted from the notification information confirmation process. In addition, the specific method for determining whether the target user can be exempted from the notification information confirmation process can also be to import the target user into a preset list library as long as the user has been diagnosed with a certain disease. The target users on the list are users who cannot be exempted from the notification information confirmation process.

[0104] As an optional embodiment of this specification, step 401 queries whether the second historical application material has extracted the keyword information on the case date, including: querying whether the target user has a historical processing record of reflow data; when the target user has a historical processing record of reflow data, querying whether the second historical application material has extracted the keyword information on the case date; when the target user does not have a historical processing record of reflow data, determining the target application object corresponding to the second historical application material, and extracting the keyword information from all third historical application materials of the target user, where the third historical application material includes the historical application materials of the target user under the category corresponding to the target application object.

[0105] Specifically, the server can also query whether the target user has historically processed reflow data. If the target user has historically processed reflow data, the server only needs to extract keyword information from the second historical application materials retrieved this time. If the target user has never processed reflow data, the server can determine the target applicant based on the second historical application materials. Based on the target applicant, the specific case category of the application case corresponding to the second historical application materials can be determined. The server can then query all third historical application materials under this category and extract keyword information from all third historical application materials to enrich the user material information of the target user.

[0106] As an optional embodiment of this specification, the extracting the keyword information from all third historical application materials of the target user includes: sequentially querying all third historical application materials of the target user, and extracting the keyword information from the target third historical application materials from which the keyword information has not been extracted.

[0107] Specifically, keyword information may have already been extracted from some of the third historical application materials. Therefore, the server can sequentially query the third historical application materials to identify target third historical application materials from which keyword information has not been extracted, and then extract keyword information from the target third historical application materials.

[0108] Step 403: For the target historical application materials from which the keyword information has not been extracted, extract the keyword information from the target historical application materials and add the keyword information to the user material information.

[0109] Specifically, similarly, the second historical application materials may contain some materials from which keyword information has been extracted. Therefore, the server may query the second historical application materials in sequence, identify target historical application materials from which keyword information has not been extracted, and extract keyword information from the target historical application materials.

[0110] Step 405: For the target historical application materials from which the keyword information has been extracted, the steps are ended.

[0111] Specifically, for target historical application materials whose keyword information has been extracted, the server will directly end the step without extracting the keyword information.

[0112] In the embodiment of this specification, in addition to the passive processing method of judging whether the case can be exempted from notification when receiving a new application case from the target user, the server will also actively retrieve the target user's newly added second historical application materials and extract keywords from the second historical application materials to further improve and enrich the user material information of the target user and ensure the accuracy of each exemption judgment process.

[0113] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0114] Next, please refer to Figure 5, which shows a schematic diagram of the structure of a notification-free processing device for an application case provided in an embodiment of this specification. It should be noted that the notification-free processing device for an application case shown in Figure 5 is used to execute the method of the embodiment shown in Figure 2 of this application. For ease of explanation, only the portion relevant to the embodiment of this application is shown. For specific technical details not disclosed, please refer to the embodiment shown in Figure 2 of this application.

[0115] As shown in Figure 5, the notification-free processing device for the application case may at least include: an acquisition module 501, which is used to obtain the user material information of the target user when receiving a case application request, and compare the notification information corresponding to the current case of the target user based on the user material information, the user material information includes historical keyword information extracted from the first historical application material, and the first historical application material includes the application materials of the target user in the historical case; a first judgment module 502, which is used to exempt the notification information confirmation process of the current case when the user material information does not match the notification information, and extract keyword information from the current application material of the current case, and add the keyword information to the user material information; a second judgment module 503, which is used to send the notification information to the target user when the user material information matches the notification information.

[0116] As an optional embodiment of this specification, the first judgment module 502 is specifically used to: perform optical character recognition on the current application materials of the current case to obtain text information; perform entity recognition on the text information to obtain field information; and perform normalization processing on the field information to obtain keyword information.

[0117] As an optional embodiment of this specification, the device also includes: a third judgment module, which is used to regenerate the notification information based on the matching part in the notification information when the user material information partially matches the notification information, send the regenerated notification information to the target user, and extract keyword information from the current application materials of the current case, and add the keyword information to the user material information.

[0118] As an optional embodiment of this specification, the device also includes: an retrieval module, which is used to retrieve the second historical application materials newly added by the target user from the reflux data of the target platform every time a preset retrieval time period passes, and query whether the second historical application materials have extracted the keyword information on the case date; a first processing module, which is used to extract the keyword information from the target historical application materials that have not extracted the keyword information, and add the keyword information to the user material information; a second processing module, which is used to end the step for the target historical application materials from which the keyword information has been extracted.

[0119] As an optional embodiment of this specification, the retrieval module is specifically used to: determine whether the target user can be exempted from the notification information confirmation process based on the user material information; when the target user can be exempted from the notification information confirmation process, execute the next step; when the target user cannot be exempted from the notification information confirmation process, end the step.

[0120] As an optional embodiment of this specification, the retrieval module is further specifically used to: query whether the target user has a historical processing record of reflux data; when the target user has a historical processing record of reflux data, query whether the second historical application material has extracted the keyword information on the case date; when the target user does not have a historical processing record of reflux data, determine the target application object corresponding to the second historical application material, and extract the keyword information from all third historical application materials of the target user, where the third historical application material includes the historical application materials of the target user under the category corresponding to the target application object.

[0121] As an option in the embodiment of this specification, the retrieval module is further configured to sequentially query all third historical application materials of the target user, and extract the keyword information from the target third historical application materials from which the keyword information has not been extracted.

[0122] As an optional embodiment of this specification, the device also includes: an allocation module for allocating reminder durations to each of the keyword information in the user material information based on keyword categories; a deletion module for sending update reminder information to the target user based on the target keyword information when the continuous cumulative storage duration of any target keyword information in the user material information exceeds the storage duration.

[0123] Those skilled in the art will clearly understand that the technical solutions of the embodiments of the present application can be implemented with the help of software and / or hardware. "Unit" and "module" in this specification refer to software and / or hardware that can independently perform or cooperate with other components to perform specific functions, where the hardware can be, for example, a field programmable gate array (FPGA), an integrated circuit (IC), etc.

[0124] Each processing unit and / or module in the embodiments of the present application may be implemented by an analog circuit that implements the functions described in the embodiments of the present application, or may be implemented by software that executes the functions described in the embodiments of the present application.

[0125] Next, please refer to FIG6 , which shows a schematic structural diagram of an electronic device provided in an embodiment of this specification.

[0126] As shown in FIG. 6 , the electronic device 600 may include: at least one processor 601 , at least one network interface 604 , a user interface 603 , a memory 605 , and at least one communication bus 602 .

[0127] The communication bus 602 may be used to implement connection and communication among the above components.

[0128] The user interface 603 may include buttons, and the optional user interface may also include a standard wired interface or a wireless interface.

[0129] The network interface 604 may include, but is not limited to, a Bluetooth module, an NFC module, a Wi-Fi module, and the like.

[0130] The processor 601 may include one or more processing cores. The processor 601 utilizes various interfaces and lines to connect the various components within the entire electronic device 600. By running or executing instructions, programs, code sets, or instruction sets stored in the memory 605, and calling data stored in the memory 605, the processor 601 performs various functions of the electronic device 600 and processes data. Optionally, the processor 601 may be implemented in at least one hardware form selected from DSP, FPGA, and PLA. The processor 601 may integrate one or a combination of a CPU, a GPU, and a modem. The CPU primarily processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; and the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 601 and may be implemented separately on a single chip.

[0131] Among them, the memory 605 may include RAM and may also include ROM. Optionally, the memory 605 includes a non-transitory computer-readable medium. The memory 605 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 605 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 605 may also be at least one storage device located away from the aforementioned processor 601. As shown in Figure 6, the memory 605 as a computer storage medium may include an operating system, a network communication module, a user interface module and program instructions.

[0132] Specifically, the processor 601 can be used to call the notification-free processing application for application cases stored in the memory 605, and perform the following operations: when receiving a case application request, obtain the user material information of the target user, and compare the notification information corresponding to the current case of the target user based on the user material information, the user material information includes historical keyword information extracted from the first historical application material, and the first historical application material includes the application materials of the target user in the historical case; when the user material information does not match the notification information, the notification information confirmation process of the current case is waived, and keyword information is extracted from the current application material of the current case, and the keyword information is added to the user material information; when the user material information matches the notification information, the notification information is sent to the target user.

[0133] As an optional embodiment of this specification, the extracting keyword information from the current application materials of the current case includes: performing optical character recognition on the current application materials of the current case to obtain text information; performing entity recognition on the text information to obtain field information; and normalizing the field information to obtain keyword information.

[0134] As an optional embodiment of this specification, the method also includes: when the user material information partially matches the notification information, regenerating the notification information based on the matching part in the notification information, sending the regenerated notification information to the target user, and extracting keyword information from the current application materials of the current case, and adding the keyword information to the user material information.

[0135] As an optional embodiment of this specification, the method also includes: after each preset retrieval time, retrieving the second historical application materials newly added by the target user from the reflux data of the target platform, and querying whether the second historical application materials have extracted the keyword information on the case date; for the target historical application materials from which the keyword information has not been extracted, extracting the keyword information from the target historical application materials, and adding the keyword information to the user material information; for the target historical application materials from which the keyword information has been extracted, ending the step.

[0136] As an optional embodiment of this specification, the query of whether the second historical application material has extracted the keyword information before the case date also includes: judging whether the target user can be exempted from the notification information confirmation process based on the user material information; when the target user can be exempted from the notification information confirmation process, executing the next step; when the target user cannot be exempted from the notification information confirmation process, ending the step.

[0137] As an optional embodiment of this specification, the querying whether the second historical application material has extracted the keyword information on the case date includes: querying whether the target user has a historical processing record of reflow data; when the target user has a historical processing record of reflow data, querying whether the second historical application material has extracted the keyword information on the case date; when the target user does not have a historical processing record of reflow data, determining the target application object corresponding to the second historical application material, and extracting the keyword information from all third historical application materials of the target user, the third historical application material including the historical application materials of the target user under the category corresponding to the target application object.

[0138] As an optional embodiment of this specification, the extracting the keyword information from all third historical application materials of the target user includes: sequentially querying all third historical application materials of the target user, and extracting the keyword information from the target third historical application materials from which the keyword information has not been extracted.

[0139] As an optional embodiment of this specification, the method also includes: allocating a reminder duration for each keyword information in the user material information based on the keyword category; when the continuous cumulative storage time of any target keyword information in the user material information exceeds the storage time, sending update reminder information to the target user based on the target keyword information.

[0140] The embodiments of this specification also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above method. The computer-readable storage medium may include, but is not limited to, any type of disk, including a floppy disk, an optical disk, a DVD, a CD-ROM, a microdrive, a magneto-optical disk, a ROM, a RAM, an EPROM, an EEPROM, a DRAM, a VRAM, a flash memory device, a magnetic or optical card, a nanosystem (including a molecular memory IC), or any type of medium or device suitable for storing instructions and / or data.

[0141] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0142] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0143] In the several embodiments provided in this application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interface, and the indirect coupling or communication connection of the device or unit can be electrical or other forms.

[0144] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0145] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0146] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory, including a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned memory includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0147] Those skilled in the art will appreciate that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable memory, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0148] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

Claims

1. A method for handling application cases without notification, including: Upon receiving a case application request, obtaining user material information of a target user, and comparing notification information corresponding to a current case of the target user based on the user material information, wherein the user material information includes historical keyword information extracted from a first historical application material, and the first historical application material includes application materials of the target user in historical cases; When the user material information does not match the notification information, the notification information confirmation process of the current case is waived, and keyword information is extracted from the current application materials of the current case, and the keyword information is added to the user material information; When the user material information matches the notification information, the notification information is sent to the target user.

2. According to the method of claim 1, extracting keyword information from the current application materials of the current case comprises: Performing optical character recognition on the current application materials of the current case to obtain text information; Performing entity recognition on the text information to obtain field information; The field information is normalized to obtain keyword information.

3. The method according to claim 1, further comprising: When the user material information partially matches the notification information, the notification information is regenerated based on the matching part of the notification information, the regenerated notification information is sent to the target user, and keyword information is extracted from the current application materials of the current case and added to the user material information.

4. The method according to claim 1, further comprising: After each preset extraction time, extract the second historical application materials newly added by the target user from the return flow data of the target platform, and query whether the second historical application materials have extracted the keyword information on the case date; For a target historical application material from which the keyword information has not been extracted, extract the keyword information from the target historical application material and add the keyword information to the user material information; For the target historical application materials from which the keyword information has been extracted, the steps are ended.

5. The method according to claim 4, wherein the querying of whether the second historical application material has been used before the case date to extract the keyword information further comprises: Determining whether the target user can be exempted from the notification information confirmation process based on the user profile information; When the target user can be exempted from the notification information confirmation process, executing the next step; When the target user cannot be exempted from the notification information confirmation process, the step ends.

6. According to the method of claim 4, the querying whether the second historical application material has extracted the keyword information on the case date comprises: Query whether the target user has a historical processing record of backflow data; When the target user has a historical processing record of the return data, query whether the second historical application material has extracted the keyword information on the case date; When there is no historical processing record of the return data for the target user, determine the target application object corresponding to the second historical application material, and extract the keyword information from all third historical application materials of the target user, where the third historical application materials include the historical application materials of the target user under the category corresponding to the target application object.

7. The method according to claim 6, wherein extracting the keyword information from all third historical application materials of the target user comprises: All third historical application materials of the target user are queried in sequence, and the keyword information is extracted from the target third historical application materials from which the keyword information has not been extracted.

8. The method according to claim 1, further comprising: Based on the keyword category, each of the keyword information in the user material information is assigned a reminder duration; When the continuous cumulative storage time of any target keyword information in the user material information exceeds the storage time, update reminder information is sent to the target user based on the target keyword information.

9. A device for processing application cases without notification, comprising: an acquisition module, configured to acquire user material information of a target user upon receiving a case application request, and compare the notification information corresponding to the current case of the target user based on the user material information, wherein the user material information includes historical keyword information extracted from a first historical application material, and the first historical application material includes application materials of the target user in historical cases; A first judgment module is used to, when the user material information does not match the notification information, waive the notification information confirmation process of the current case, extract keyword information from the current application materials of the current case, and add the keyword information to the user material information; The second judgment module is used to send the notification information to the target user when the user material information matches the notification information.

10. The device according to claim 9, wherein the first determination module is specifically configured to: Performing optical character recognition on the current application materials of the current case to obtain text information; Performing entity recognition on the text information to obtain field information; The field information is normalized to obtain keyword information.

11. The device according to claim 9, further comprising: The third judgment module is used to regenerate the notification information based on the matching part of the notification information when the user material information partially matches the notification information, send the regenerated notification information to the target user, extract keyword information from the current application materials of the current case, and add the keyword information to the user material information.

12. The device according to claim 9, further comprising: The extraction module is used to extract the second historical application materials newly added by the target user from the return data of the target platform every time a preset extraction time passes, and query whether the second historical application materials have extracted the keyword information on the case date; A first processing module is used to extract the keyword information from the target historical application materials from which the keyword information has not been extracted, and add the keyword information to the user material information; The second processing module is used to end the step for the target historical application materials from which the keyword information has been extracted.

13. The device according to claim 12, wherein the scooping module is specifically used for: Determining whether the target user can be exempted from the notification information confirmation process based on the user profile information; When the target user can be exempted from the notification information confirmation process, executing the next step; When the target user cannot be exempted from the notification information confirmation process, the step ends.

14. The device according to claim 12, wherein the scooping module is further used for: Query whether the target user has a historical processing record of backflow data; When the target user has a historical processing record of the return data, query whether the second historical application material has extracted the keyword information on the case date; When there is no historical processing record of the return data for the target user, determine the target application object corresponding to the second historical application material, and extract the keyword information from all third historical application materials of the target user, where the third historical application materials include the historical application materials of the target user under the category corresponding to the target application object.

15. The device according to claim 14, wherein the scooping module is further used for: All third historical application materials of the target user are queried in sequence, and the keyword information is extracted from the target third historical application materials from which the keyword information has not been extracted.

16. The apparatus according to claim 9, further comprising: An allocating module, configured to allocate a reminder duration to each of the keyword information in the user material information based on the keyword category; The deletion module is used to send update reminder information to the target user based on the target keyword information when the continuous cumulative storage time of any target keyword information in the user material information exceeds the storage time.

17. An electronic device comprising a processor and a memory; The processor is connected to the memory; The memory is used to store executable program code; The processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to execute the method according to any one of claims 1 to 8.

18. A computer-readable storage medium having a computer program stored thereon, wherein the computer-readable storage medium has instructions stored therein, and when the instructions are executed on a computer or a processor, the computer or the processor executes the steps of the method according to any one of claims 1 to 8.

Images