Work order processing method, device and storage medium
By performing word segmentation and semantic analysis on the historical risk assessment information of account-reported work orders, priority processing conditions are automatically determined, solving the problems of low work order processing efficiency and operational risks, and achieving efficient and accurate work order processing.
Patent Information
- Application Number
- CN201910517409.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-06-14
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2039-07-08
Smart Images

Figure CN112085457B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a work order processing method, device and storage medium. Background Art
[0002] With the development of science and technology, Internet activities are becoming more frequent, which has spawned a large number of illegal online activities. Users can report illegal online activities through the reporting platform, and the reporting platform will assign manual processing.
[0003] At present, in the process of accepting reports through the reporting platform, first, the user initiates an online report through the reporting platform, and then the reporting platform generates a work order based on the received report, and assigns the work order to the staff for manual processing in the order of generation time. Since all reported work orders need to be queued for manual processing, a large amount of manpower is required when the number of reports is large, the work order processing efficiency is low, and for work orders with higher risks, the reporting platform usually faces certain risks caused by delayed processing of reports. Summary of the invention
[0004] The embodiments of the present application provide a work order processing method, device and storage medium, which can improve the efficiency of work order processing.
[0005] In a first aspect, an embodiment of the present application provides a work order processing method, including:
[0006] Get the account report ticket;
[0007] Extracting historical risk assessment information corresponding to the reported account in the account reporting work order;
[0008] Determining whether priority treatment conditions are met based on the historical risk assessment information;
[0009] When the historical risk assessment information does not meet the priority processing conditions, the account reporting work order is stored in the unprocessed work order database;
[0010] When the storage time of the account report work order in the unprocessed work order database reaches a preset time, the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order are merged for processing.
[0011] In some embodiments, determining whether a priority processing condition is met according to the historical risk assessment information includes:
[0012] Performing word segmentation processing on the historical risk assessment information according to a preset word segmentation rule to obtain segmented words;
[0013] Performing semantic analysis on the segmented words through a trained preset model to obtain semantic information;
[0014] Determine whether a priority processing condition is met according to the semantic information.
[0015] In some implementations, determining whether a priority processing condition is met according to the semantic information includes:
[0016] Determine, based on the semantic information, whether the reported account is a high-risk account, whether there are transaction features in the semantic information, and / or whether there is a risk description in the semantic information;
[0017] When the reported account is a high-risk account, there are transaction features in the semantic information, and / or there is a risk description in the semantic information, it is determined that the priority processing condition is met.
[0018] In some implementations, before performing semantic analysis on the segmented words using the trained preset model to obtain semantic information, the method further includes:
[0019] Acquire multiple training samples, perform word segmentation on each training sample according to the word segmentation rule, and obtain sample words after word segmentation;
[0020] Acquire the real semantics of the sample words, and identify the semantics of the sample words through a preset model to obtain predicted semantics;
[0021] The preset model is trained according to the real semantics and the predicted semantics to obtain a trained preset model.
[0022] In some implementations, obtaining an account reporting work order includes:
[0023] Receive a report request sent by a client, wherein the report request carries the reported account and attribute information;
[0024] Generate an account reporting ticket based on the reported account and attribute information.
[0025] In some implementations, when the historical risk assessment information does not meet the priority processing condition, storing the account reporting work order in the unprocessed work order database includes:
[0026] When the historical risk assessment information does not meet the priority processing conditions, obtaining the current status of the reported account in the account reporting work order;
[0027] If the current status of the reported account is an unpunished status, the account reporting work order is stored in the unprocessed work order database.
[0028] In some implementations, after obtaining the current status of the reported account in the account reporting work order, the method further includes:
[0029] If the current status of the reported account is a punished status, the processing result will be fed back to the client corresponding to the reporting account.
[0030] In some embodiments, after determining whether a priority processing condition is met according to the historical risk assessment information, the method further includes:
[0031] When the historical risk assessment information meets the priority processing condition, obtaining the priority of the historical risk assessment information;
[0032] The account reporting ticket is processed according to the priority.
[0033] In a second aspect, an embodiment of the present application further provides a work order processing device, including:
[0034] The first acquisition unit is used to acquire the account reporting ticket;
[0035] An extraction unit, configured to extract historical risk assessment information corresponding to the reported account in the account reporting work order;
[0036] A determination unit, configured to determine whether a priority processing condition is met according to the historical risk assessment information;
[0037] A storage unit, configured to store the account reporting work order in an unprocessed work order database when the historical risk assessment information does not meet the priority processing condition;
[0038] The first processing unit is used to merge and process the unprocessed work orders in the unprocessed work order database that have the same attributes as the account reporting work order when the storage time of the account reporting work order in the unprocessed work order database reaches a preset time.
[0039] In some embodiments, the determining unit includes:
[0040] A word segmentation module, used to perform word segmentation processing on the historical risk assessment information according to a preset word segmentation rule to obtain segmented words;
[0041] An analysis module is used to perform semantic analysis on the segmented words through a trained preset model to obtain semantic information;
[0042] A determination module is used to determine whether a priority processing condition is met according to the semantic information.
[0043] In some implementations, the determining module is specifically configured to:
[0044] Determine, based on the semantic information, whether the reported account is a high-risk account, whether there are transaction features in the semantic information, and / or whether there is a risk description in the semantic information;
[0045] When the reported account is a high-risk account, there are transaction features in the semantic information, and / or there is a risk description in the semantic information, it is determined that the priority processing condition is met.
[0046] In some implementations, the determining unit further includes:
[0047] A sample acquisition module is used to acquire multiple training samples, perform word segmentation on each training sample according to the word segmentation rule, and obtain sample words after word segmentation;
[0048] A recognition module is used to obtain the real semantics of the sample words and recognize the semantics of the sample words through a preset model to obtain predicted semantics;
[0049] The training module is used to train the preset model according to the real semantics and the predicted semantics to obtain the trained preset model.
[0050] In some implementations, the first acquisition unit is specifically configured to:
[0051] Receive a report request sent by a client, wherein the report request carries the reported account and attribute information;
[0052] Generate an account reporting ticket based on the reported account and attribute information.
[0053] In some embodiments, the storage unit comprises:
[0054] A status acquisition module, used for acquiring the current status of the reported account in the account reporting work order when the historical risk assessment information does not meet the priority processing condition;
[0055] The storage module is used to store the account reporting work order in the unprocessed work order database if the current status of the reported account is an unpunished status.
[0056] In some embodiments, the storage unit further includes:
[0057] The feedback module is used to feed back the processing result to the client corresponding to the reporting account if the current status of the reported account is a punished status.
[0058] In some implementations, the work order processing device further includes:
[0059] A second acquisition unit, configured to acquire the priority of the historical risk assessment information when the historical risk assessment information meets a priority processing condition;
[0060] The second processing unit is used to process the account reporting work order according to the priority.
[0061] In a third aspect, an embodiment of the present application further provides a server, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor calls the computer program in the memory, it executes any one of the work order processing methods provided in the embodiment of the present application.
[0062] In a fourth aspect, an embodiment of the present application further provides a storage medium, wherein the storage medium stores a plurality of instructions, wherein the instructions are suitable for loading by a processor to execute any one of the work order processing methods provided in the embodiment of the present application.
[0063] The embodiment of the present application can obtain the account report work order, and extract the historical risk assessment information corresponding to the reported account in the account report work order, and then determine whether the priority processing conditions are met based on the historical risk assessment information. When the historical risk assessment information does not meet the priority processing conditions, the account report work order is stored in the unprocessed work order database; and when the storage time of the account report work order in the unprocessed work order database reaches a preset time, the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order are merged for processing. This solution can automatically process the account report work order according to the priority processing conditions, and merge the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order, so that the work orders can be processed in a timely manner, and the unprocessed work orders with the same attributes can be batch processed, thereby improving the work order processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0064] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.
[0065] Figure 1 It is a flowchart of a work order processing method provided in an embodiment of the present application;
[0066] Figure 2 is another flowchart of the work order processing method provided in an embodiment of the present application;
[0067] Figure 3 is another flowchart of the work order processing method provided in an embodiment of the present application;
[0068] Figure 4 It is a schematic diagram of initiating a report provided in an embodiment of the present application;
[0069] Figure 5 It is a schematic diagram of work order processing provided in an embodiment of the present application;
[0070] Figure 6 is a schematic diagram of a work order processing result provided in an embodiment of the present application;
[0071] Figure 7 is another flowchart of the work order processing method provided in an embodiment of the present application;
[0072] Figure 8 It is a structural schematic diagram of a work order processing device provided in an embodiment of the present application;
[0073] Fig. 9 It is a schematic diagram of the structure of the server provided in the embodiment of the present application. DETAILED DESCRIPTION
[0074] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.
[0075] See also Figure 1 , Figure 1 : is a flowchart of a work order processing method provided by an embodiment of the present application. In this embodiment, it will be described from the perspective of a work order processing device. The work order processing device can be integrated in a network device such as a server or a gateway. The work order processing method may include:
[0076] S101. Obtain an account reporting ticket.
[0077] The account reporting work order may refer to a workflow for recording, processing and tracking the completion of account reporting, i.e., a work order generated by each online reporting through an account. The account may be an account registered on a payment network platform, a social network platform, a shopping network platform, or other network platforms.
[0078] In some implementations, obtaining an account reporting work order may include: receiving a reporting request sent by a client, the reporting request carrying the reported account and attribute information; and generating an account reporting work order according to the reported account and attribute information.
[0079] For example, the work order processing device may receive a report request sent by a client, which carries the reported account and attribute information, etc. The type of the reported account may be flexibly set according to actual needs, and the attribute information may include the report type, the amount of damage, the report description, and the identity information of the user corresponding to the reported account, etc. Then, an account report work order may be generated according to the reported account and attribute information.
[0080] S102. Extract historical risk assessment information corresponding to the reported account in the account reporting work order.
[0081] Among them, the historical risk assessment information can be used to evaluate the historical data of the risk of the reported account, for example, it can include the historical transaction information of the reported account, and the historical reported information, etc. The historical reported information can include the corpus of the report description, etc.
[0082] It should be noted that in order to facilitate the extraction and analysis of historical risk assessment information, the work order processing device can store the historical transaction information and historical reported information corresponding to each account in the database. When an account reporting work order is obtained, the reported account can be extracted from the account reporting work order, and the historical risk assessment information corresponding to the reported account can be searched from the database.
[0083] S103. Determine whether priority processing conditions are met based on historical risk assessment information.
[0084] In the field of online reporting, in the process of accepting account reporting tickets, there is usually a situation where effective reports are delayed in processing, which may cause operational risks. Therefore, account reporting tickets that meet the priority processing conditions can be given priority processing. Among them, the operational risk refers to the risk caused by the operator's improper management of the interactive behaviors and information generated between various users on the network, which may include: damage to user experience, the spread of bad social trends, and the infringement of normal users caused by illegal acts of lawbreakers during user interaction.
[0085] After obtaining the historical risk assessment information corresponding to the reported account, the work order processing device can determine whether the historical risk assessment information meets the priority processing conditions, wherein the priority processing conditions can be flexibly set according to actual needs. For example, it is determined whether there are transaction features or risk descriptions in the historical risk assessment information. If so, it is determined that the historical risk assessment information meets the priority processing conditions. If not, it is determined that the historical risk assessment information does not meet the priority processing conditions.
[0086] In some embodiments, determining whether priority processing conditions are met based on historical risk assessment information may include: performing word segmentation on the historical risk assessment information according to preset word segmentation rules to obtain segmented words; performing semantic analysis on the segmented words through a trained preset model to obtain semantic information; and determining whether priority processing conditions are met based on the semantic information.
[0087] For example, the work order processing device can perform word segmentation on the historical risk assessment information according to a preset word segmentation rule. The preset word segmentation rule can be word segmentation according to a preset number of words per interval, for example, one or more words per interval are cut into a word. The preset word segmentation rule can also be uniform word segmentation according to the total number of words in the historical risk assessment letter. For example, when the total number of words in the historical risk assessment letter is 15, every 5 words can be evenly divided into a word. The preset word segmentation rule can also be random word segmentation. For example, when the total number of words in the historical risk assessment letter is 15, only 3 groups of 2-word words are extracted therefrom. Alternatively, the historical risk assessment letter with a total number of 15 words is divided into a word consisting of 2 words, a word consisting of 1 word, a word consisting of 9 words, and a word consisting of 3 words; and so on.
[0088] It is understandable that the preset word segmentation rules can be flexibly set according to actual needs, for example, dictionary-based word segmentation, statistics-based word segmentation, or artificial intelligence-based word segmentation, etc. The specific content is not limited here.
[0089] After the historical risk assessment information is segmented to obtain the corresponding words, the segmented words can be semantically analyzed through the trained preset model to obtain semantic information. In order to improve the accuracy of the semantic analysis, the preset model can be trained in advance, and the semantic analysis can be performed through the trained preset model.
[0090] In some embodiments, before semantic analysis is performed on the segmented words through a trained preset model to obtain semantic information, the work order processing method may also include: obtaining multiple training samples, performing segmentation processing on each training sample according to the segmentation rules to obtain sample words after segmentation; obtaining the true semantics of the sample words, and identifying the semantics of the sample words through a preset model to obtain predicted semantics; training the preset model according to the true semantics and predicted semantics to obtain a trained preset model.
[0091] For example, in order to conduct targeted training, the work order processing device can obtain multiple training samples to train the preset model. The training samples can be text information related to historical risk assessment information. The method of obtaining multiple training samples can be to randomly extract the corresponding multiple training samples from the historical risk assessment information, or to extract multiple training samples from the historical risk assessment information of different network platforms, or to create multiple training samples corresponding to the risk assessment information according to different scenarios. It can be understood that the number of training samples and the method of obtaining them can be flexibly set according to actual needs, and the specific content is not limited here.
[0092] After obtaining multiple training samples, each training sample can be segmented according to the preset segmentation rules to obtain sample words after segmentation. In order to improve the reliability of processing historical risk assessment information, the preset segmentation rules are consistent with the aforementioned segmentation rules for segmenting historical risk assessment information, which will not be repeated here.
[0093] At this time, the real semantics of the sample words can be obtained, and the real semantics can be the real meaning of the sample words, and the semantics of the sample words can be identified by the preset model to obtain the predicted semantics, and the predicted semantics can be the meaning of the sample words identified by the preset model. Then, the difference between the real semantics and the predicted semantics can be obtained, and the preset model can be converged according to the difference between the real semantics and the predicted semantics to adjust the parameters of the preset model to appropriate values, and obtain the trained preset model.
[0094] After obtaining the trained preset model, the trained preset model can be used to perform semantic analysis on the segmented words to obtain semantic information, and then determine whether the priority processing conditions are met based on the semantic information.
[0095] In some embodiments, determining whether the priority processing conditions are met based on semantic information may include: judging based on the semantic information whether the reported account is a high-risk type of account, whether there are transaction characteristics in the semantic information, and / or whether there is a risk description in the semantic information; when the reported account is a high-risk type of account, there are transaction characteristics in the semantic information, and / or there is a risk description in the semantic information, determining that the priority processing conditions are met.
[0096] Among them, high-risk accounts can be paid accounts, high-value accounts, or high-risk complaint-prone accounts. Transaction features can be transaction behaviors between the reported party and the reporter, etc., which need to be quickly intercepted to prevent the reporter from being harmed. If they are not defined in time, it may cause economic damage and complaints to the reporter, thereby bringing operational risks to the network platform, such as the reporter transferring 10,000 yuan to the reported party. The risk description can be a text description of danger and strong complaint tendency contained in the semantic information corresponding to the risk assessment information of the report. If the report work order of the account containing such description is not handled in time, it will cause great harm to the normal operation of the network platform, for example, text descriptions such as "I want to commit suicide". Based on semantic information, it can be determined whether the reported account is a high-risk account, whether there are transaction features and / or whether there is a risk description.
[0097] For example, the work order processing device can determine whether the reported account is a high-risk account based on the semantic information. If the reported account is a high-risk account, it is determined that the priority processing condition is met, and the work order reporting the account is processed first; if the reported account is not a high-risk account, it is further determined whether there are transaction features in the semantic information. If there are transaction features in the semantic information, it is determined that the priority processing condition is met, and the work order reporting the account is processed first; if there are no transaction features in the semantic information, it is further determined whether there is a risk description in the semantic information. If there is a risk description in the semantic information, it is determined that the priority processing condition is met, and the work order reporting the account is processed first; if there is no risk description in the semantic information, it is determined that the priority processing condition is not met.
[0098] For another example, the work order processing device can determine whether there are transaction features in the semantic information. If there are transaction features in the semantic information, it is determined that the priority processing conditions are met and the work order reporting the account is processed first; if there are no transaction features in the semantic information, it is further determined whether there is a risk description in the semantic information. If there is a risk description in the semantic information, it is determined that the priority processing conditions are met and the work order reporting the account is processed first; if there is no risk description in the semantic information, it is further determined whether the reported account is a high-risk type account. If the reported account is a high-risk type account, it is determined that the priority processing conditions are met and the work order reporting the account is processed first; if the reported account is not a high-risk type account, it is determined that the priority processing conditions are not met.
[0099] For another example, the work order processing device can determine whether the reported account is a high-risk account, whether there are transaction features in the semantic information, and whether there is a risk description in the semantic information based on the semantic information. If the reported account is a high-risk account, there are transaction features in the semantic information, and there is a risk description in the semantic information, it is determined that the priority processing conditions are met, and the report work order for the account is processed first; if the reported account is not a high-risk account, there are no transaction features in the semantic information, and there is no risk description in the semantic information, it is determined that the priority processing conditions are not met.
[0100] It is understandable that the order of determining whether the priority processing conditions are met based on the semantic information can be flexibly set according to actual needs. For example, it is possible to first determine whether the reported account is a high-risk type of account, then determine whether there are transaction features in the semantic information, and finally determine whether there is a risk description in the semantic information. Alternatively, it is possible to first determine whether there is a risk description in the semantic information, then determine whether there are transaction features in the semantic information, and finally determine whether the reported account is a high-risk type of account. Alternatively, multiple parallel threads can be used to simultaneously determine whether the reported account is a high-risk type of account, determine whether there are transaction features in the semantic information, and determine whether there is a risk description in the semantic information, etc. The specific content is not limited here.
[0101] By automatically determining whether the priority processing conditions are met based on semantic information, the account report work order is processed first when the priority processing conditions are determined to be met. When the priority processing conditions are determined to be met, the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order are merged and processed, avoiding manual analysis of the risk level of the report, and the subjective judgment given may be omitted, avoiding potential operational risks to the network platform. By analyzing the risk level of the reported account in the account report work order, comparing the transaction characteristics between the reporting account and the reported account, and performing intelligent analysis on the semantic information corresponding to the corpus description content filled in by the reporter when reporting, high-risk account report work orders are automatically processed quickly, so as to achieve rapid processing of high-risk report work orders, protect the legitimate rights and interests of the reporter, reduce the operational risks of the network platform, and reduce the risk of economic losses to the reporter due to Internet fraud and other behaviors.
[0102] S104. When the historical risk assessment information does not meet the priority processing conditions, the account reporting work order is stored in the unprocessed work order database.
[0103] In order to facilitate the subsequent clustering of unprocessed account reporting work orders and improve the efficiency of work order processing, when the historical risk assessment information does not meet the priority processing conditions, the account reporting work order can be stored in the unprocessed work order database waiting for processing.
[0104] In some embodiments, when the historical risk assessment information does not meet the priority processing conditions, storing the account reporting work order in the unprocessed work order database may include: when the historical risk assessment information does not meet the priority processing conditions, obtaining the current status of the reported account in the account reporting work order; if the current status of the reported account is an unpunished status, storing the account reporting work order in the unprocessed work order database.
[0105] In order to improve the efficiency of processing work orders and avoid repeated processing of account reporting work orders corresponding to the same reported account, the work order processing device can obtain the current status of the reported account in the account reporting work order, which can include unpunished status, punished status, and being processed, etc. If the current status of the reported account is unpunished status, the account reporting work order is stored in the unprocessed work order database.
[0106] In some embodiments, after obtaining the current status of the reported account in the account reporting work order, the work order processing method may further include: if the current status of the reported account is a punished status, the processing result is fed back to the client corresponding to the reporting account to avoid the account reporting work order corresponding to the punished reported account being stored in the unprocessed work order database, and by verifying the current status of the reported account, the account reporting work order is automatically processed based on the current status, thereby greatly improving the work order processing efficiency.
[0107] S105. When the storage time of the account report work order in the unprocessed work order database reaches a preset time, the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order are merged for processing.
[0108] In order to improve the efficiency of work order processing, unprocessed work orders with the same attributes can be merged for processing. For example, after the account report work order is stored in the unprocessed work order database, it can be determined whether the storage time of the account report work order in the unprocessed work order database has reached the preset time, wherein the preset time can be flexibly set according to actual needs. When the storage time of the account report work order in the unprocessed work order database has reached the preset time, the unprocessed work orders with the same attributes as the account report work order in the unprocessed work order database are obtained. The same attributes can be the same reporting type or the same reported account, etc. Then the unprocessed work orders with the same attributes as the account report work order in the unprocessed work order database are merged for processing. At this time, after the processing is completed, the processing results can be fed back to the client corresponding to the reporting account.
[0109] In some embodiments, after determining whether the priority processing conditions are met based on the historical risk assessment information, the work order processing method may further include: when the historical risk assessment information meets the priority processing conditions, obtaining the priority of the historical risk assessment information; and processing the account reporting work order according to the priority.
[0110] Among them, historical risk assessment information that meets the priority processing conditions may include multiple types, for example, high-risk type accounts, transaction characteristics, and risk descriptions, etc. Different priorities can be set in advance for different types. For example, different weight values can be set for high-risk type accounts, transaction characteristics, and risk descriptions, respectively. The larger the weight value, the higher the corresponding priority. Conversely, the smaller the weight value, the lower the corresponding priority. The high-risk type account can be set with the highest priority, the transaction characteristics with the second priority, and the risk description with the lowest priority, etc. Of course, the priority can be flexibly set according to actual needs, and the specific content is not limited here.
[0111] When the historical risk assessment information meets the priority processing conditions, the priority of the historical risk assessment information can be obtained, and then the account reporting work order is processed according to the priority of the historical risk assessment information, and the processing results are fed back to the client corresponding to the reporting account, so that high-risk work orders can be quickly and accurately identified, and the overall work order processing efficiency can be improved. For example, if there are account reporting work orders A, account reporting work orders B, and account reporting work orders C that all meet the priority processing conditions, where account reporting work order A is a high-risk type account, account reporting work order B is a transaction feature, and account reporting work order C is a risk description, the priorities from high to low are high-risk type account, transaction features, and risk description. At this time, account reporting work orders A, account reporting work orders B, and account reporting work orders C can be processed in order from high to low priority.
[0112] The embodiment of the present application can obtain the account report work order, and extract the historical risk assessment information corresponding to the reported account in the account report work order, and then determine whether the priority processing conditions are met based on the historical risk assessment information. When the historical risk assessment information does not meet the priority processing conditions, the account report work order is stored in the unprocessed work order database; and when the storage time of the account report work order in the unprocessed work order database reaches a preset time, the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order are merged for processing. This solution can automatically process the account report work order according to the priority processing conditions, and merge the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order, so that the work orders can be processed in a timely manner, and the unprocessed work orders with the same attributes can be batch processed, thereby improving the work order processing efficiency.
[0113] The work order processing method described in the above embodiment will be further described in detail below.
[0114] Please refer to Figure 2 , Figure 2Another flowchart of the work order processing method provided in the embodiment of the present application is shown in FIG. Figure 2 As shown, the process of the work order processing method can be as follows:
[0115] S201. The client sends a report request to the server.
[0116] The report request may include the reported account and attribute information, etc. The type of the reported account may be flexibly set according to actual needs. The attribute information may include the amount of damage, the report description (i.e., the report description), and the identity information of the user corresponding to the reported account, etc. For example, Figure 3 As shown, the client can initiate a report through the network platform, generate a report request, and send the report request to the server.
[0117] For example, Figure 4 As shown, taking reporting online fraud as an example, the client can display a reporting interface and receive an activation command for the "I want to report" button in the reporting interface, and enter the information input interface for reporting online fraud according to the command. The information input interface can include attribute information such as the victim account, the amount of loss, the reporting object, the fraudulent behavior, the reporting description, and the evidence screenshot. The reporting description can enter the corresponding description content according to the needs of the reporter. At this time, a reporting request can be generated based on the attribute information and sent to the server.
[0118] S202. The server generates an account reporting ticket based on the received reporting request.
[0119] For example, an account reporting work order may be generated based on the reported account and attribute information carried in the reporting request.
[0120] S203. The server verifies whether the account reporting ticket meets the priority processing conditions. If the verification is successful, step S204 is executed. If the verification is not successful, step S208 is executed.
[0121] The server can extract the historical risk assessment information corresponding to the reported account in the account reporting work order from the database storing historical risk assessment information, and verify whether the priority processing conditions are met based on the historical risk assessment information. The historical risk assessment information can be used to evaluate the historical data of the reported account risk, for example, it can include the historical transaction information of the reported account, and the historical reported information, etc.
[0122] Among them, the priority processing conditions can be flexibly set according to actual needs. For example, the historical risk assessment information can be segmented according to the preset segmentation rules to obtain the segmented words. The preset segmentation rules can be flexibly set according to actual needs, and then the segmented words are semantically analyzed through the trained preset model to obtain semantic information. At this time, it can be determined whether the priority processing conditions are met based on the semantic information.
[0123] In some embodiments, determining whether the priority processing conditions are met based on semantic information may include: judging based on the semantic information whether the reported account is a high-risk type of account, whether there are transaction characteristics in the semantic information, and / or whether there is a risk description in the semantic information; when the reported account is a high-risk type of account, there are transaction characteristics in the semantic information, and / or there is a risk description in the semantic information, determining that the priority processing conditions are met.
[0124] For example, Figure 3 As shown, the server can determine whether the reported account is a high-risk account based on the semantic information. If the reported account is a high-risk account, it is determined that the priority processing condition is met, and the account report work order is processed first, and the processing result is fed back to the client corresponding to the reporter, and the work order is archived. The work order archiving can be after the account report work order is processed, the processed account report work order is automatically stored or manually stored in the database; if the reported account is not a high-risk account, it is further determined whether there are transaction features in the semantic information. If there are transaction features in the semantic information, it is determined that the priority processing condition is met, and the account report work order is processed first; if there are no transaction features in the semantic information, it is further determined whether there is a risk description in the semantic information. If there is a risk description in the semantic information, it is determined that the priority processing condition is met, and the account report work order is processed first; if there is no risk description in the semantic information, it is determined that the priority processing condition is not met.
[0125] It is understandable that the order of determining whether the priority processing conditions are met based on the semantic information can be flexibly set according to actual needs. For example, it is possible to first determine whether the reported account is a high-risk type of account, then determine whether there are transaction features in the semantic information, and finally determine whether there is a risk description in the semantic information. Alternatively, it is possible to first determine whether there is a risk description in the semantic information, then determine whether there are transaction features in the semantic information, and finally determine whether the reported account is a high-risk type of account. Alternatively, multiple parallel threads can be used to simultaneously determine whether the reported account is a high-risk type of account, determine whether there are transaction features in the semantic information, and determine whether there is a risk description in the semantic information, etc. The specific content is not limited here.
[0126] This embodiment automatically determines whether the priority processing conditions are met based on semantic information, so that when it is determined that the priority processing conditions are met, the account report work order is processed first. When it is determined that the priority processing conditions are met, the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order are merged for processing, avoiding manual analysis of the risk level of the report, and the subjective judgment given may be omitted, avoiding potential operational risks to the network platform. By analyzing the risk level of the reported account in the account report work order, comparing the transaction characteristics between the reporting account and the reported account, and performing intelligent analysis on the semantic information corresponding to the corpus description content filled in by the reporter when reporting, high-risk account report work orders are automatically processed quickly, thereby achieving rapid processing of high-risk report work orders, protecting the legitimate rights and interests of the reporter, reducing the operational risk of the network platform, and reducing the risk of economic losses to the reporter due to Internet fraud and other behaviors.
[0127] S204. The server sends the account reporting ticket to the review platform.
[0128] S205. The review platform reviews and processes the account reporting ticket.
[0129] S206: The audit platform sends the processing results to the server.
[0130] S207: The server sends the processing result to the client.
[0131] When the historical risk assessment information meets the priority processing conditions, the server can send the account report ticket to the review platform, and the review platform will promptly review the account report ticket in priority. For example, Figure 5 As shown, the basic information corresponding to the account report ticket, account basic information, asynchronous form, and forensic query and other related information can be manually reviewed. The asynchronous form can include form title, relevant screenshots, problem description, and transaction order number. After the review obtains the processing result, the processing result is fed back to the client corresponding to the reporting account. For example, Figure 6 As shown, the processing result may include whether the report is established or not established, and the processing details may be displayed, which may include the reported object, report type, report time, report description, processing result and processing time, etc. The processing result may also be evaluated as satisfactory or unsatisfactory, etc. This enables rapid and accurate identification of high-risk work orders and improves the overall processing efficiency of work orders.
[0132] It should be noted that when the historical risk assessment information meets the priority processing conditions, the priority of the historical risk assessment information is obtained, and the account reporting work order is processed according to the priority.
[0133] like Figure 7As shown, the process of the work order processing method can also be as follows:
[0134] S208. The server stores the account reporting work orders and merges the unprocessed work orders with the same attributes.
[0135] In order to improve the efficiency of work order processing, when the historical risk assessment information does not meet the priority processing conditions, the server can store the account reporting work order in the unprocessed work order database. After storing the account reporting work order in the unprocessed work order database, it can be determined whether the storage time of the account reporting work order in the unprocessed work order database reaches the preset time. The preset time can be flexibly set according to actual needs.
[0136] When the storage time of an account report work order in the unprocessed work order database reaches the preset time, the unprocessed work order in the unprocessed work order database with the same attribute as the account report work order is obtained. The same attribute can be the same report type or the same reported account, etc. Then the unprocessed work orders in the unprocessed work order database with the same attribute as the account report work order are merged, so that multiple unprocessed work orders with the same attributes can be merged into one, and assigned to the same reviewer for processing, so that the reviewer can process them in batches, thereby greatly improving the processing efficiency. When the storage time reaches the preset time, if there is no unprocessed work order with the same attribute as the account report work order in the database, it can be processed in the order in which the unprocessed work orders are stored.
[0137] It should be noted that in order to improve the efficiency of processing work orders and avoid repeated processing of account report work orders corresponding to the same reported account, the server can obtain the current status of the reported account in the account report work order, which can include unpunished status, punished status, and being processed. If the current status of the reported account is unpunished, the account report work order is stored in the unprocessed work order database. If the current status of the reported account is punished, the processing result is fed back to the client corresponding to the reporting account to avoid the account report work order corresponding to the punished reported account being stored in the unprocessed work order database. By verifying the current status of the reported account, the account report work order is automatically processed based on the current status, so that the account report work order for the punished account can be quickly identified. After determining that the report is established, it is promptly fed back to the client corresponding to the reporter, which greatly exerts the ability of automatic processing, reduces the workload of manual processing, and greatly improves the efficiency of work order processing.
[0138] S209. The server sends the merged unprocessed work orders to the review platform.
[0139] S210. The audit platform audits the merged unprocessed work orders.
[0140] S211. The audit platform sends the processing results to the server.
[0141] S212: The server sends the processing result to the client.
[0142] At this point, the server can send the merged unprocessed tickets to the review platform, for example Figure 5 As shown in the figure, the auditor can review the basic information corresponding to the account report ticket, account basic information, asynchronous form, and evidence query and other related information. After the review obtains the processing result, the processing result is fed back to the client corresponding to the reporting account. For example, Figure 6 As shown, the processing result may include whether the report is established or not established, etc., and the processing details may be displayed, and the processing details may include the reported object, report type, report time, report description, processing result and processing time, etc., and the processing result may also be evaluated as satisfactory or unsatisfactory, etc. When it is determined that the report is valid, the server may punish or not punish the reported party corresponding to the reported account according to the preset punishment strategy, and send the processing result to the client corresponding to the reporting account (i.e., the reporting party), so that the work orders can be processed in batches and the work order processing efficiency can be improved.
[0143] In the embodiment of the present application, after the client initiates a report request, the server can generate an account report work order based on the received report request, and determine whether the account report work order meets the priority processing conditions. When the priority processing conditions are met, the account report work order can be processed first; when the priority processing conditions are not met, the account report work order can be stored in the unprocessed work order database, and when the storage time of the account report work order in the unprocessed work order database reaches a preset time, the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order are merged for processing. This solution can quickly and accurately identify high-risk work orders when the account report work order is obtained, and automatically and quickly process the account report work order that meets the priority processing conditions, that is, quickly process high-risk work orders, reduce potential operational risks to the network platform; and merge the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order, so that the work orders can be processed in time, and the unprocessed work orders with the same attributes are processed in batches, which improves the efficiency of work order processing.
[0144] In order to facilitate better implementation of the work order processing method provided in the embodiment of the present application, the embodiment of the present application also provides a device based on the above work order processing method. The meanings of the terms are the same as those in the above work order processing method, and the specific implementation details can refer to the description in the method embodiment.
[0145] See also Figure 8 , Figure 8A structural diagram of a work order processing device provided in an embodiment of the present application, wherein the work order processing device 300 may include a first acquisition unit 301, an extraction unit 302, a determination unit 303, a storage unit 304, and a first processing unit 305, etc.
[0146] Among them, the first acquisition unit 301 is used to obtain the account reporting work order.
[0147] The extraction unit 302 is used to extract the historical risk assessment information corresponding to the reported account in the account reporting work order.
[0148] The determination unit 303 is used to determine whether a priority processing condition is met according to the historical risk assessment information.
[0149] The storage unit 304 is used to store the account reporting work order in the unprocessed work order database when the historical risk assessment information does not meet the priority processing conditions.
[0150] The first processing unit 305 is used to merge the unprocessed work orders in the unprocessed work order database with the same attributes as the account reporting work order when the storage time of the account reporting work order in the unprocessed work order database reaches a preset time.
[0151] In some implementations, the determination unit 303 includes a word segmentation module, an analysis module, and a determination module, etc., which may be specifically as follows:
[0152] The word segmentation module is used to perform word segmentation processing on the historical risk assessment information according to preset word segmentation rules to obtain segmented words.
[0153] The analysis module is used to perform semantic analysis on the segmented words through the trained preset model to obtain semantic information.
[0154] The determination module is used to determine whether the priority processing condition is met according to the semantic information.
[0155] In some embodiments, the determination module is specifically used to: determine whether the reported account is a high-risk type of account, whether there are transaction features in the semantic information, and / or whether there is a risk description in the semantic information based on the semantic information; when the reported account is a high-risk type of account, there are transaction features in the semantic information, and / or there is a risk description in the semantic information, determine that the priority processing conditions are met.
[0156] In some implementations, the determination unit 303 may further include a sample acquisition module, a recognition module, and a training module, etc., which may be specifically as follows:
[0157] The sample acquisition module is used to acquire multiple training samples, perform word segmentation on each training sample according to the word segmentation rules, and obtain sample words after word segmentation.
[0158] The recognition module is used to obtain the real semantics of the sample words and recognize the semantics of the sample words through a preset model to obtain the predicted semantics.
[0159] The training module is used to train the preset model according to the real semantics and the predicted semantics to obtain the trained preset model.
[0160] In some implementations, the first acquisition unit 301 is specifically used to: receive a reporting request sent by a client, the reporting request carrying the reported account and attribute information; and generate an account reporting work order according to the reported account and attribute information.
[0161] In some implementations, the storage unit 304 may include a state acquisition module and a storage module, etc., which may be specifically as follows:
[0162] The status acquisition module is used to obtain the current status of the reported account in the account reporting work order when the historical risk assessment information does not meet the priority processing conditions.
[0163] The storage module is used to store the account reporting work order in the unprocessed work order database if the current status of the reported account is an unpunished status.
[0164] In some implementations, the storage unit 304 may further include:
[0165] The feedback module is used to feed back the processing result to the client corresponding to the reporting account if the current status of the reported account is a punished status.
[0166] In some implementations, the work order processing device 300 may further include a second acquisition unit and a second processing unit, etc., which may be specifically as follows:
[0167] The second acquisition unit is used to acquire the priority of the historical risk assessment information when the historical risk assessment information meets the priority processing condition.
[0168] The second processing unit is used to process the account reporting ticket according to the priority.
[0169] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0170] In the embodiment of the present application, the first acquisition unit 301 can acquire the account report work order, and the extraction unit 302 can extract the historical risk assessment information corresponding to the reported account in the account report work order. Then, the determination unit 303 can determine whether the priority processing condition is met according to the historical risk assessment information. When the historical risk assessment information does not meet the priority processing condition, the storage unit 304 can store the account report work order in the unprocessed work order database; and when the storage time of the account report work order in the unprocessed work order database reaches a preset time, the first processing unit 305 can merge the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order. This solution can automatically process the account report work order according to the priority processing condition, and merge the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order, so that the work order can be processed in time, and the unprocessed work orders with the same attributes can be processed in batches, thereby improving the work order processing efficiency.
[0171] The present application also provides a server, such as Fig. 9 As shown, it shows a schematic diagram of the structure of the server involved in the embodiment of the present application, specifically:
[0172] The server may include one or more processing core processors 401, one or more computer-readable storage media memories 402, a power supply 403, an input unit 404 and other components. Those skilled in the art will appreciate that Fig. 9 The server structure shown in the figure does not constitute a limitation on the server, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Among them:
[0173] The processor 401 is the control center of the server, and uses various interfaces and lines to connect various parts of the entire server. By running or executing software programs and / or modules stored in the memory 402, and calling data stored in the memory 402, the processor 401 performs various functions of the server and processes data, thereby monitoring the server as a whole. Optionally, the processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 401.
[0174] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the server, etc. In addition, the memory 402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.
[0175] The server also includes a power supply 403 for supplying power to each component. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, so that the power management system can manage charging, discharging, power consumption and other functions. The power supply 403 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators and other arbitrary components.
[0176] The server may further include an input unit 404, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
[0177] Although not shown, the server may further include a display unit, etc., which will not be described in detail herein. Specifically in this embodiment, the processor 401 in the server will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402, thereby realizing various functions, as follows:
[0178] Obtain an account reporting work order; extract the historical risk assessment information corresponding to the reported account in the account reporting work order; determine whether the priority processing conditions are met based on the historical risk assessment information; when the historical risk assessment information does not meet the priority processing conditions, store the account reporting work order in the unprocessed work order database; when the storage time of the account reporting work order in the unprocessed work order database reaches a preset time, merge the unprocessed work orders in the unprocessed work order database with the same attributes as the account reporting work order.
[0179] In the above embodiments, the description of each embodiment has its own focus. For the part that is not described in detail in a certain embodiment, please refer to the detailed description of the work order processing method above, and will not be repeated here.
[0180] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.
[0181] To this end, an embodiment of the present application provides a storage medium in which a plurality of instructions are stored, and the instructions can be loaded by a processor to execute the steps in any work order processing method provided in the embodiment of the present application. For example, the instructions can execute the following steps:
[0182] Obtain an account reporting work order; extract the historical risk assessment information corresponding to the reported account in the account reporting work order; determine whether the priority processing conditions are met based on the historical risk assessment information; when the historical risk assessment information does not meet the priority processing conditions, store the account reporting work order in the unprocessed work order database; when the storage time of the account reporting work order in the unprocessed work order database reaches a preset time, merge the unprocessed work orders in the unprocessed work order database with the same attributes as the account reporting work order.
[0183] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.
[0184] The storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0185] Since the instructions stored in the storage medium can execute the steps in any work order processing method provided in the embodiments of the present application, the beneficial effects that can be achieved by any work order processing method provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.
[0186] The above is a detailed introduction to a work order processing method, device and storage medium provided in the embodiments of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A work order processing method, characterized in that: include: Get the account report ticket; Extracting historical risk assessment information corresponding to the reported account in the account reporting work order; Determine whether the priority treatment conditions are met based on the historical risk assessment information, including: Performing word segmentation processing on the historical risk assessment information according to a preset word segmentation rule to obtain segmented words; Performing semantic analysis on the segmented words through a trained preset model to obtain semantic information; Determine, based on the semantic information, whether the reported account is a high-risk account, whether there are transaction features in the semantic information, and / or whether there is a risk description in the semantic information; When the reported account is a high-risk account, the semantic information contains transaction features, and / or the semantic information contains risk descriptions, determining that the priority processing conditions are met; When the historical risk assessment information does not meet the priority processing conditions, the account reporting work order is stored in the unprocessed work order database; When the storage time of the account report work order in the unprocessed work order database reaches a preset time, the unprocessed work orders in the unprocessed work order database with the same attributes as the account report work order are merged for processing.
2. The work order processing method according to claim 1, characterized in that: Before performing semantic analysis on the segmented words by using the trained preset model to obtain semantic information, the method further includes: Acquire multiple training samples, perform word segmentation on each training sample according to the word segmentation rule, and obtain sample words after word segmentation; Acquire the real semantics of the sample words, and identify the semantics of the sample words through a preset model to obtain predicted semantics; The preset model is trained according to the real semantics and the predicted semantics to obtain a trained preset model.
3. The work order processing method according to claim 1, characterized in that: The account reporting work order includes: Receive a report request sent by a client, wherein the report request carries the reported account and attribute information; Generate an account reporting ticket based on the reported account and attribute information.
4. The work order processing method according to claim 1, characterized in that: When the historical risk assessment information does not meet the priority processing condition, storing the account reporting work order in the unprocessed work order database includes: When the historical risk assessment information does not meet the priority processing conditions, obtaining the current status of the reported account in the account reporting work order; If the current status of the reported account is an unpunished status, the account reporting work order is stored in the unprocessed work order database.
5. The work order processing method according to claim 4, characterized in that: After obtaining the current status of the reported account in the account reporting work order, the method further includes: If the current status of the reported account is a punished status, the processing result will be fed back to the client corresponding to the reporting account.
6. The work order processing method according to any one of claims 1 to 5, characterized in that: After determining whether the priority processing condition is met according to the historical risk assessment information, the method further includes: When the historical risk assessment information meets the priority processing condition, obtaining the priority of the historical risk assessment information; The account reporting ticket is processed according to the priority.
7. A work order processing device, characterized in that: include: The first acquisition unit is used to acquire the account reporting ticket; An extraction unit, configured to extract historical risk assessment information corresponding to the reported account in the account reporting work order; A determination unit, configured to determine whether a priority processing condition is met according to the historical risk assessment information, comprising: performing word segmentation processing on the historical risk assessment information according to a preset word segmentation rule to obtain words after word segmentation; Performing semantic analysis on the segmented words through a trained preset model to obtain semantic information; Determine, based on the semantic information, whether the reported account is a high-risk account, whether there are transaction features in the semantic information, and / or whether there is a risk description in the semantic information; When the reported account is a high-risk account, the semantic information contains transaction features, and / or the semantic information contains risk descriptions, determining that the priority processing conditions are met; A storage unit, configured to store the account reporting work order in an unprocessed work order database when the historical risk assessment information does not meet the priority processing condition; The first processing unit is used to merge and process the unprocessed work orders in the unprocessed work order database that have the same attributes as the account reporting work order when the storage time of the account reporting work order in the unprocessed work order database reaches a preset time.
8. A storage medium, characterized in that: The storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the work order processing method according to any one of claims 1 to 6.
