A method for managing event processing, a method and apparatus for handling tasks.

By acquiring the attribute information of managed events, matching the target template with the preset event processing template, and executing the task processing sequence, the problem of low event processing efficiency in the existing technology is solved, and efficient and refined event processing is achieved.

CN115480886BActive Publication Date: 2026-11-17ALIBABA INNOVATION PRIVATE LIMITED
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202110661835.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-06-15
Publication Date
2026-11-17
Estimated Expiration
2041-06-15

AI Technical Summary

Technical Problem

The existing event allocation method is simple, which leads to low event processing efficiency and easy errors, and cannot meet the needs of efficient and refined processing.

Method used

By acquiring the attribute information of managed events, matching the target event processing template with the preset event processing template, and executing the event processing tasks in sequence according to the task processing order, including matching and mapping of tag information, content information, location information, time information, etc., combined with the determination of the event execution agency, the standardization and refinement of the event processing process can be achieved.

Benefits of technology

It improves the efficiency and quality of incident handling, ensures that the incident handling process complies with standards, enables refined handling based on specific circumstances, and reduces the occurrence of errors.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115480886B_ABST
    Figure CN115480886B_ABST
Patent Text Reader

Abstract

This application provides a management event processing method, a task processing method, and an apparatus. The management event processing method includes: acquiring a management event; matching a target event processing template from a preset event processing template based on the attribute information of the management event; and sequentially executing at least one event processing task for the management event in the target event processing template according to the task processing order in the target event processing template. This allows management events to be processed according to the standardized processing flow set by the target event processing template, improving event processing efficiency. Simultaneously, by decomposing the event processing flow into multiple event processing tasks through the event processing template, the event processing flow can be made more refined, facilitating the maintenance of high processing quality for the management events.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for managing event processing, a method for managing tasks, a device for managing event processing, and a device for managing tasks. Background Technology

[0002] In existing technologies, when an event requiring processing is detected, it is typically assigned to the appropriate event execution mechanism. However, current event assignment methods often simply delegate tasks to the corresponding event execution mechanism for independent processing, resulting in low event processing efficiency. Furthermore, there is a possibility of incorrect assignment, which could further reduce event processing efficiency. Summary of the Invention

[0003] In view of the above problems, embodiments of this application are proposed to provide a management event processing method, a task processing method, a management event processing apparatus, and a task processing apparatus that overcome or at least partially solve the above problems.

[0004] To address the aforementioned problems, this application discloses a method for managing event handling, including:

[0005] Get management events;

[0006] Based on the attribute information of the managed event, match the target event processing template in the preset event processing templates;

[0007] The task processing order in the target event processing template is adopted to sequentially execute at least one event processing task in the target event processing template for the managed event.

[0008] Optionally, the attribute information includes at least one of tag information, content information, location information, and time information;

[0009] The step of matching a target event processing template in a preset event processing template based on the attribute information of the managed event includes:

[0010] Input at least one of the tag information, content information, location information, and time information of the managed event into a preset event allocation model;

[0011] Based on the template information output by the event allocation model, the target event processing template is matched among the preset event processing templates.

[0012] Optionally, the attribute information includes category information;

[0013] The step of matching a target event processing template in a preset event processing template based on the attribute information of the managed event includes:

[0014] Check whether there is a preset template mapping relationship between the category information of the managed events and the event handling template;

[0015] If there is a preset template mapping relationship between the category information of the managed event and the event processing template, the event processing template corresponding to the category information of the managed event shall be used as the target event processing template.

[0016] Optionally, the step of matching a target event handling template in a preset event handling template based on the attribute information of the managed event further includes:

[0017] If there is no preset template mapping relationship between the category information of the management event and the event processing template, the event execution agency corresponding to the management event is searched in the preset event allocation list;

[0018] Use the event processing template corresponding to the event execution mechanism as the target event processing template.

[0019] Optionally, the step of matching a target event handling template in a preset event handling template based on the attribute information of the managed event includes:

[0020] Based on the attribute information of the management event, identify whether the management event meets the preset scenario management conditions;

[0021] If the management event meets the preset scenario management conditions, the event processing template corresponding to the scenario management conditions will be used as the target event processing template.

[0022] Optionally, the step of identifying whether the management event meets the preset scenario management conditions based on the attribute information of the management event includes:

[0023] Based on the attribute information of the managed event, identify whether the event time of the managed event is within a preset time period, and / or whether the event location of the managed event is within a preset area;

[0024] If the event time of the management event is within a preset time period, and / or the event location of the management event is within a preset area, then the management event is determined to meet the preset scenario management conditions.

[0025] Optionally, the step of sequentially executing at least one event processing task for the management event in the target event processing template according to the task processing order in the target event processing template includes:

[0026] Based on the task processing order in the target event processing template, create a task object corresponding to the event processing task to be processed in the preset task database;

[0027] The task object is processed by calling a preset task processing resource.

[0028] After the task object is processed, according to the task processing order, the next task object to be processed for the event processing task is created in the preset task database, and the step of calling the preset task processing resources to process the task object is repeated until the event processing task at the end of the task processing order in the target event processing template is processed.

[0029] Optionally, the method further includes:

[0030] In response to the template arrangement operation, at least one event handling task of a preset type is created in the blank template, and the task processing order between the event handling tasks is determined to obtain the event handling template.

[0031] This application also provides a task processing method, including:

[0032] Get the target event;

[0033] Based on the attribute information of the target event, match the target event processing template in the preset event processing template;

[0034] The task processing order in the target event processing template is adopted to sequentially execute at least one event processing task for the target event in the target event processing template.

[0035] This application also provides a management event handling apparatus, including:

[0036] The acquisition module is used to acquire management events;

[0037] The matching module is used to match a target event processing template in a preset event processing template based on the attribute information of the managed event;

[0038] An execution module is used to sequentially execute at least one event processing task for the managed event in the target event processing template, according to the task processing order in the target event processing template.

[0039] Optionally, the attribute information includes at least one of tag information, content information, location information, and time information;

[0040] The matching module includes:

[0041] The model input submodule is used to input at least one of the tag information, content information, location information, and time information of the managed event into a preset event allocation model;

[0042] The first matching submodule is used to match the target event processing template in the preset event processing templates based on the template information output by the event allocation model.

[0043] Optionally, the attribute information includes category information;

[0044] The matching module includes:

[0045] The relationship lookup submodule is used to look up whether there is a preset template mapping relationship between the category information of the managed event and the event processing template;

[0046] The second matching submodule is used to use the event processing template corresponding to the category information of the managed event as the target event processing template if there is a preset template mapping relationship between the category information of the managed event and the event processing template.

[0047] Optionally, the matching module further includes:

[0048] The organization lookup submodule is used to find the event execution organization corresponding to the management event in a preset event allocation list if there is no preset template mapping relationship between the category information of the management event and the event processing template.

[0049] The third matching submodule is used to use the event processing template corresponding to the event execution mechanism as the target event processing template.

[0050] Optionally, the matching module includes:

[0051] The scene recognition submodule is used to identify whether the management event meets the preset scene management conditions based on the attribute information of the management event;

[0052] The fourth matching submodule is used to use the event processing template corresponding to the preset scenario management conditions as the target event processing template if the management event meets the preset scenario management conditions.

[0053] Optionally, the scene recognition submodule includes:

[0054] The time period area identification unit is used to identify whether the event time of the management event is within a preset time period and / or whether the event location of the management event is within a preset area based on the attribute information of the management event;

[0055] The scene recognition unit is used to determine whether the management event meets the preset scene management conditions if the event time of the management event is within a preset time period and / or the event location of the management event is within a preset area.

[0056] Optionally, the execution module includes:

[0057] The object creation submodule is used to create a task object corresponding to the event processing task to be processed in a preset task database according to the task processing order in the target event processing template.

[0058] The submodule is invoked to call preset task processing resources to process the task object;

[0059] The repeat submodule is used to create a task object for the next pending event processing task in a preset task database according to the task processing order after the task object is processed, and repeatedly execute the step of calling the preset task processing resources to process the task object until the event processing task at the end of the task processing order in the target event processing template is completed.

[0060] Optionally, the device further includes:

[0061] The module generation module is used to respond to template arrangement operations, create at least one preset type of event processing task in a blank template, determine the task processing order between the event processing tasks, and obtain an event processing template.

[0062] This application embodiment also provides a task processing device, including:

[0063] The event acquisition module is used to acquire target events;

[0064] The template matching module is used to match a target event processing template in a preset event processing template based on the attribute information of the target event.

[0065] The template execution module is used to execute at least one event processing task for the target event in the target event processing template in sequence, according to the task processing order in the target event processing template.

[0066] This application also discloses an electronic device, including:

[0067] One or more processors; and

[0068] One or more machine-readable media having instructions stored thereon, which, when executed by the one or more processors, cause the electronic device to perform one or more methods as described in the embodiments of this application.

[0069] This application also discloses one or more machine-readable media storing instructions that, when executed by one or more processors, cause the processors to perform one or more methods as described in this application.

[0070] This application also discloses a software product, including a computer program / instructions, wherein when the computer program / instructions are executed, they implement one or more methods as described in the embodiments of this application.

[0071] The embodiments of this application have the following advantages:

[0072] The management event processing method of this application embodiment obtains management events; matches a target event processing template in a preset event processing template according to the attribute information of the management events; and sequentially executes at least one event processing task for the management event in the target event processing template according to the task processing order in the target event processing template. This allows management events to be processed according to the standardized processing flow set by the target event processing template, improving event processing efficiency. Simultaneously, by decomposing the event processing flow into multiple event processing tasks through the event processing template, the event processing flow can be made more refined, facilitating the maintenance of high processing quality for the management events. Attached Figure Description

[0073] Figure 1 This is a flowchart illustrating the steps of an embodiment of a management event handling method according to this application.

[0074] Figure 2 This is a flowchart illustrating the steps of another embodiment of the management event handling method of this application;

[0075] Figure 3 This is a schematic diagram of a template arrangement interface according to an embodiment of this application;

[0076] Figure 4 This is a schematic diagram of a task processing system according to an embodiment of this application;

[0077] Figure 5 This is a schematic diagram of an intelligent operation center according to an embodiment of this application;

[0078] Figure 6 This is a flowchart illustrating the steps of one embodiment of a task processing method according to this application.

[0079] Figure 7 This is a structural block diagram of an embodiment of a management event processing device according to this application.

[0080] Figure 8 This is a structural block diagram of one embodiment of a task processing device according to this application. Detailed Implementation

[0081] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0082] In this embodiment of the application, when a management event requiring the intervention of a management department occurs within a jurisdictional area such as a city or town, the event is typically handed over to the relevant management department for handling. Depending on the primary management department, management events can include traffic management events, urban environmental management events, public security management events, industrial and commercial management events, tax management events, customs management events, community management events, emergency management events, and so on. For example, if a vehicle collision occurs within the jurisdictional area, it can be considered a traffic management event requiring the handling of the traffic management department. If a merchant is found selling substandard products within the jurisdictional area, it can be considered an industrial and commercial management event requiring the handling of the industrial and commercial administration department. If a dispute occurs among residents of a community within the jurisdictional area, it can be considered a community management event requiring the handling of the neighborhood committee or other community management departments. In some cases, management events may require the collaborative handling of multiple management departments. For example, if it is necessary to verify the business operations of merchants within the jurisdiction, the event can be handled jointly by the industrial and commercial administration department and the tax administration department.

[0083] This application embodiment manages the aforementioned management events using an Intelligent Operations Center (IOC), and pre-sets at least one event processing template within the IOC, enabling the standardization and refinement of processing flows for different types of management events. After acquiring a management event, a target event processing template can be accurately matched among the preset event processing templates based on the event's attribute information. This provides a standardized processing flow for the management event. Subsequently, the target event processing template can be used to process the management event according to the processing flow set in the target event processing template, effectively improving event processing efficiency.

[0084] Reference Figure 1 The diagram illustrates a flowchart of an embodiment of a management event handling method according to this application, which may specifically include the following steps:

[0085] Step 101, Obtain management events;

[0086] In this embodiment of the application, the intelligent operation center can communicate with at least one event acquisition device, thereby acquiring management events sent by the event acquisition device.

[0087] The event acquisition device may be a multimedia acquisition device, a telephone, an intelligent electronic device with event reporting function, an Internet information acquisition device, a device with the function of receiving information actively submitted by users, etc., and this application does not limit it.

[0088] In practice, the information sent by the event acquisition device to the intelligent operation center may be unstandardized. Unstandardized information may be difficult for the intelligent operation center to identify as valid and to process further. Therefore, it is necessary to further process the information collected by the event acquisition device to generate standardized management events.

[0089] Specifically, after obtaining the information sent by the event acquisition device, the intelligent operation center can convert the information sent by the event acquisition device into standardized management events by mapping non-standard fields in the information sent by the event acquisition device to standard fields, extracting key fields in the information sent by the event acquisition device and recombining or disassembling the key fields, and filling the key fields in the information sent by the event acquisition device into a standard template.

[0090] In practical implementation, since there are many types of event acquisition devices, different types of event acquisition devices can collect the same event simultaneously, which may result in identical or partially identical management events. Therefore, the management events can be deduplicated or merged.

[0091] Specifically, the intelligent operation center can identify whether the management events are identical or partially identical based on fields such as title, description, type, time, and location. If identical management events exist, deduplication can be performed, retaining only one of the multiple identical management events. If partially identical management events exist, they can be merged, combining multiple management events and deleting duplicate content.

[0092] Step 102: Match the target event processing template in the preset event processing templates according to the attribute information of the managed event;

[0093] In this embodiment, the management event may have attribute information. The attribute information can be determined based on fields in the management event. For example, if the management event contains fields related to illegal parking, then the management event may have the attribute information "illegal parking". If the management event contains fields related to location A, then the management event may have the attribute information "location A".

[0094] In this embodiment, the intelligent operation center may have at least one preset event processing template. The event processing template may include at least one event processing task required for handling management events, and the task processing order of the event processing tasks. Thus, the intelligent operation center can standardize the processing flow of management events and decompose the event processing flow into multiple event processing tasks, making the event processing flow more refined and facilitating the maintenance of high processing quality for the management events.

[0095] In this embodiment, the management events can have many different types. Furthermore, even when the management event types are the same, the processing flow of the management event can differ depending on the actual situation of the management event. Therefore, the intelligent operation center can store a large number of event processing templates. After acquiring the management event, a suitable target event processing template can be matched from the preset event processing templates based on the attribute information of the management event.

[0096] In specific implementations, depending on actual needs, a mapping relationship between attribute information and event processing templates can be preset to determine the target event processing template corresponding to the managed event based on the mapping relationship; alternatively, a preset algorithm model can be used to recommend the target event processing template based on the attribute information; or the event execution mechanism corresponding to the managed event can be determined based on the attribute information, and the event processing template preset by the event execution mechanism can be used as the target event processing template.

[0097] Step 103: Using the task processing order in the target event processing template, execute at least one event processing task for the management event in the target event processing template in sequence.

[0098] In this embodiment, after determining the target event processing template, the management event can be processed according to the target event processing template. Therefore, the task processing order in the target event processing template can be used to sequentially execute at least one event processing task for the management event in the target event processing template, thereby completing the processing of the management event.

[0099] In a specific implementation, the target event processing template may also include execution conditions, thus the processing flow within the target event processing template may have branching flows. Therefore, depending on whether the execution conditions are met, the target event processing template may have different task processing sequences and event processing tasks. Specifically, during the process of the intelligent operation center executing event processing tasks sequentially according to the task processing sequence, the task processing sequence may point to an execution condition, and subsequent corresponding task processing sequences and event processing tasks can be executed based on whether the execution condition is met.

[0100] In a practical implementation, the execution of the event processing task can be performed by the intelligent operation center itself, or by at least one electronic device communicatively connected to the intelligent operation center. Examples include controlling road inspection equipment to collect images of specific locations, sending notification information to the mobile terminals of specific personnel, and acquiring rainfall data collected by road environment monitoring equipment.

[0101] As an example of this application, the management event is a vehicle illegally parked on road A. The management event may have the attribute information "illegal parking". Based on the attribute information "illegal parking" of the management event, a target event processing template "illegal parking enforcement" can be matched from a preset event processing template. In the target event processing template "illegal parking enforcement", the event processing tasks, in the order of task processing, can be "find traffic police", "notify traffic police of the iron bars", "determine if the vehicle has been moved", and the execution condition "vehicle moved". If the execution condition "vehicle moved" is met, the subsequent event processing task, in the order of task processing, is "end process". If the execution condition "vehicle moved" is not met, the subsequent event processing tasks, in the order of task processing, are "obtain towing company contact information" and "notify towing company to move vehicle".

[0102] The management event processing method of this application embodiment obtains management events; matches a target event processing template in a preset event processing template according to the attribute information of the management event; and sequentially executes at least one event processing task for the management event in the target event processing template according to the task processing order in the target event processing template. This allows management events to be processed according to a preset standardized processing flow, improving event processing efficiency. Simultaneously, by decomposing the event processing flow into multiple event processing tasks through the event processing template, the event processing flow can be made more refined, facilitating the maintenance of high processing quality for the management events.

[0103] Reference Figure 2 The diagram illustrates a flowchart of an embodiment of a management event handling method according to this application, which may specifically include the following steps:

[0104] Step 201, obtain management events;

[0105] In this embodiment of the application, the intelligent operation center can communicate with at least one event acquisition device, thereby acquiring management events sent by the event acquisition device.

[0106] The event acquisition device may be a multimedia acquisition device, a telephone, an intelligent electronic device with event reporting function, an Internet information acquisition device, a device with the function of receiving information actively submitted by users, etc., and this application does not limit it.

[0107] Step 202: Match the target event processing template in the preset event processing templates according to the attribute information of the managed event;

[0108] In this embodiment, the management event may have attribute information. The attribute information can be determined based on fields in the management event.

[0109] In this embodiment, the intelligent operation center may have at least one preset event processing template. The event processing template may include at least one event processing task required for handling management events, and the task processing order of the event processing tasks. Thus, the intelligent operation center can standardize the processing flow of management events and decompose the event processing flow into multiple event processing tasks, making the event processing flow more refined and facilitating the maintenance of high processing quality for the management events.

[0110] In this embodiment, the management events can have many different types. Furthermore, even when the management event types are the same, the processing flow of the management event can differ depending on the actual situation of the management event. Therefore, the intelligent operation center can store a large number of event processing templates. After acquiring the management event, a suitable target event processing template can be matched from the preset event processing templates based on the attribute information of the management event.

[0111] In one embodiment of this application, the attribute information includes at least one of tag information, content information, location information, and time information.

[0112] Specifically, the tag information may contain information that reflects the characteristics of the management event. For example, if the management event is that a vehicle is illegally parked on road A, the management event may have the tag information "illegal parking".

[0113] The tag information can be added during the process of collecting and managing events using the event acquisition device. For example, a customer service representative can record the management event and add tag information to it while answering a phone call.

[0114] The tag information can also be added to the management event by the intelligent operation center. Specifically, the intelligent operation center can store a number of preset tag information. After acquiring the management event, the intelligent operation center analyzes the content of the management event, selects tag information related to the content of the management event from the preset tag information, and adds tag information related to its content to the management event.

[0115] Specifically, the content information can be the specific descriptive information contained in the management event. The location information can be information related to the location where the management event occurred. The time information can be information related to the time when the management event occurred. The location information and the time information can be preset or extracted from the content information of the management event.

[0116] In one embodiment of this application, the step of matching a target event processing template in a preset event processing template based on the attribute information of the managed event includes:

[0117] S11, input at least one of the tag information, content information, location information, and time information of the managed event into a preset event allocation model;

[0118] In this embodiment, a preset event allocation model can be used to determine the target event processing template corresponding to the management event. The event allocation model can be a convolutional neural network model, a multilayer perceptron model, a decision tree model, etc., and this application does not impose any restrictions on it.

[0119] In this embodiment of the application, the tag information, content information, location information, and time information of the management event can better reflect the characteristics of the management event, making it easier to assign a suitable target event processing template to the management event according to the specific circumstances of the management event.

[0120] For example, regarding management events like illegal parking, there are various handling methods depending on the time period, weather conditions, and road conditions, such as notifying the owner to move the vehicle, issuing a ticket by the traffic police, having the vehicle moved by a tow truck, or not taking any action. Therefore, there can be a variety of event handling templates for this type of management event. In this case, it is necessary to comprehensively consider information such as the event's tag information, content information, location information, and time information to assign an appropriate target event handling template based on the specific circumstances of the event, so that the handling method better meets the user's actual needs.

[0121] Therefore, at least one of the tag information, content information, location information, and time information of the managed event can be used as model input, and template information indicating the target event processing template can be used as output to train the preset model, thereby obtaining the event allocation model. This enables the event allocation model to recommend target event processing templates based on the tag information, content information, location information, and time information of the managed event.

[0122] Since the content information may contain a lot of irrelevant information, key fields can be extracted from the content information according to actual needs, and then used as model input to improve the model's processing effect.

[0123] Subsequently, when it is necessary to determine the target event processing template corresponding to the managed event, at least one of the tag information, content information, location information, and time information of the managed event can be input into a preset event allocation model to determine the target event processing template.

[0124] S12, based on the template information output by the event allocation model, match the target event processing template in the preset event processing templates.

[0125] In this embodiment, after inputting at least one of the tag information, content information, location information, and time information of the managed event, the event allocation model can output template information to indicate the target event processing template. Thus, based on the template information, the target event processing template can be matched among preset event processing templates.

[0126] Specifically, the template information can be information related to the event handling template, such as the name and numerical labels associated with the event handling template. Therefore, based on the template information, the corresponding target event handling template can be directly determined from the preset event handling templates.

[0127] In one embodiment of this application, the attribute information further includes category information.

[0128] Specifically, the intelligent operation center may have several categories of information pre-set. These categories can be divided according to the event execution agency corresponding to the management event, the event scenario corresponding to the management event, the location where the management event occurs, etc. This application does not impose any restrictions on this.

[0129] The category information of the management event can be added by the tag information during the process of collecting management events by the event collection device, or it can be added by the intelligent operation center based on factors such as the content, source, and occurrence time of the management event.

[0130] In one embodiment of this application, the step of matching a target event processing template in a preset event processing template based on the attribute information of the managed event includes:

[0131] S21, Check whether there is a preset template mapping relationship between the category information of the managed event and the event processing template;

[0132] In this embodiment, a relatively fixed event processing flow can be established for at least one category of management events. In this case, the intelligent operation center can be pre-configured with event processing templates for that category of management events to efficiently process such events. Therefore, the intelligent operation center can pre-store a template mapping relationship between the category information of the management events and the event processing templates.

[0133] Therefore, after obtaining the management event, it is possible to check whether there is a preset template mapping relationship between the category information of the management event and the event processing template, so as to determine whether the management event of that category has a corresponding event processing template.

[0134] S22, if there is a preset template mapping relationship between the category information of the managed event and the event processing template, the event processing template corresponding to the category information of the managed event is used as the target event processing template.

[0135] In this embodiment of the application, if there is a preset template mapping relationship between the category information of the management event and the event processing template, the event processing template corresponding to the category of management event can be directly used as the target event processing template to achieve rapid matching between management events and event processing templates.

[0136] In one embodiment of this application, the step of matching a target event processing template in a preset event processing template based on the attribute information of the managed event further includes:

[0137] S31, if there is no preset template mapping relationship between the category information of the management event and the event processing template, the event execution agency corresponding to the management event is searched in the preset event allocation list;

[0138] In this embodiment, if there is no preset template mapping relationship between the category information of the management event and the event processing template, then a corresponding event processing template may not be assigned for that category of management event. In this case, a general event processing template can be used to process the management event.

[0139] Generally, a management event can have a corresponding event execution agency. This agency is responsible for managing and executing specific types of management events. Different agencies may have different event handling procedures, thus a common event handling template can typically correspond to a city-level execution agency. Therefore, to determine the common event handling template for a management event, it is necessary to determine the corresponding event execution agency.

[0140] Generally, the event execution mechanism can have a corresponding preset event allocation list. The event allocation list can be used to define the management events that the event execution mechanism needs to manage and execute. Therefore, the event execution mechanism corresponding to the management event can be found in the preset event allocation list.

[0141] In a specific implementation, the event allocation list can record descriptive information about the management events that the event execution agency needs to manage and execute. Information such as the type, content, tag, time, and location of the management events can be compared with the descriptive information in the event allocation list. The event execution agency corresponding to the descriptive information with the highest similarity is selected as the event execution agency for that management event. The event allocation list can also record the type information of the management events that the event execution agency needs to manage and execute. Therefore, the corresponding event execution agency can be directly determined based on the category information of the management events.

[0142] S32, the event processing template corresponding to the event execution mechanism is used as the target event processing template.

[0143] In this embodiment of the application, after determining the event execution mechanism, the general event processing template corresponding to the event execution mechanism can be used as the target event processing template, thereby completing the matching between the management event and the event processing template.

[0144] In one embodiment of this application, the step of matching a target event processing template in a preset event processing template based on the attribute information of the managed event includes:

[0145] S41, Based on the attribute information of the management event, identify whether the management event meets the preset scenario management conditions;

[0146] In this embodiment of the application, during urban management, there may be management needs under specific circumstances. For example, during holidays, stricter management of illegal parking around tourist attractions is required. During weekdays, stricter checks on road traffic accidents are needed to prevent traffic congestion. During peak pedestrian traffic, stricter management of illegal street vending is required. Therefore, at least one scenario management function can be set up to address these specific management needs. The scenario management function can be used to check for management events that meet the requirements of the specific circumstances, and at least one event processing template applicable to the specific circumstances can be set up to process the management events under those specific circumstances.

[0147] Therefore, at least one scenario management condition can be preset for the specific situations that the scenario management function needs to manage. Subsequently, based on the attribute information of the management event, it can be identified whether the management event meets the preset scenario management condition, thereby determining whether the management event is a management event under a specific situation.

[0148] In one embodiment of this application, the step of identifying whether the management event meets preset scenario management conditions based on the attribute information of the management event;

[0149] S411, Based on the attribute information of the management event, identify whether the event time of the management event is within a preset time period, and / or whether the event location of the management event is within a preset area;

[0150] In this application embodiment, management needs under specific circumstances can typically be associated with a specific time period and a specific area. For example, during holidays, stricter management of illegal parking around tourist attractions is required. The time period corresponding to this specific management need can be from the beginning to the end of the holiday. The corresponding area can be a pre-defined area around the tourist attraction.

[0151] Therefore, the preset scenario management conditions can be set to include a preset time period and / or a preset area, so as to determine whether the management event is a management event under a specific situation based on whether the management event meets the conditions of the preset time period and / or the preset area.

[0152] In this case, after obtaining the management event, the occurrence time of the management event can be identified based on the attribute information of the management event, such as whether the occurrence time of the management event is within a preset time period, and / or whether the occurrence location of the management event is within a preset area, so as to determine whether the management event is a management event under a specific situation.

[0153] The preset time period and preset area can be configured according to actual needs, and this application does not impose any restrictions on them.

[0154] Specifically, the attribute information of the management event may include time information and location information, thereby enabling the determination of the occurrence time and location of the management event, and identifying whether the occurrence time of the management event falls within a preset time period, and / or whether the occurrence location of the management event falls within a preset area.

[0155] S412, if the event time of the management event is within a preset time period, and / or the event location of the management event is within a preset area, determine that the management event meets the preset scenario management conditions.

[0156] In this application embodiment, if the event time of the management event is within a preset time period, and / or the event location of the management event is within a preset area, it can be considered that the attribute information of the management event matches the preset scenario management conditions, and the management event satisfies the preset scenario management conditions.

[0157] S42, if the management event meets the preset scenario management conditions, the event processing template corresponding to the scenario management conditions is used as the target event processing template.

[0158] In this embodiment of the application, if the management event meets the preset scenario management conditions, the management event can be considered as a management event under a specific situation, and the event processing template corresponding to the scenario management conditions can be used as the target event processing template.

[0159] In practical implementation, the scene management function may need to manage multiple types of management events under specific circumstances, thus the event processing templates corresponding to the scene management conditions may also be multiple. In this case, depending on actual needs, a mapping relationship between attribute information and event processing templates can be preset to determine the target event processing template corresponding to the management event based on the mapping relationship; alternatively, a preset algorithm model can be used to recommend the target event processing template based on the attribute information; or the event execution mechanism corresponding to the management event can be determined based on the attribute information, and the event processing template preset by the event execution mechanism can be used as the target event processing template.

[0160] In one embodiment of this application, the method further includes:

[0161] S51, responding to the template arrangement operation, create at least one preset type of event processing task in the blank template, and determine the task processing order between the event processing tasks to obtain the event processing template.

[0162] In this embodiment, the event processing template can be manually arranged or generated by a computer by recognizing the descriptive information of the event flow. When the event processing template is manually arranged, it can respond to user input of a template arrangement operation, create at least one preset type of event processing task in a blank template, and determine the task processing order between the event processing tasks based on the user's template arrangement operation to obtain the event processing template.

[0163] The type of event handling task may include notification type, action type, task type, etc., and this application does not limit it.

[0164] In a practical implementation, a template arrangement interface can be displayed to the user. This interface can show first schematic icons for at least one preset type of event handling task and a blank template. Subsequently, in response to the user's template arrangement operation, second schematic icons for visible event handling tasks can be added to the blank template. Furthermore, in response to the user's template arrangement operation, the second schematic icons for event handling tasks can be sequentially connected within the template. This allows the determination of the event handling tasks included in the event handling template and their processing order based on the displayed second schematic icons and the connections between them.

[0165] As an example of this application, Figure 3 This is a schematic diagram of a template arrangement interface according to an embodiment of this application. It may include a schematic icon 301 for event handling tasks, a first schematic icon 302 for routing conditions, and a blank template 303. Subsequently, in response to a user's template arrangement operation, a second schematic icon 304 for visible event handling tasks and a second schematic icon 305 for routing conditions can be added to the blank template. The user can click on the second schematic icon 304 for event handling tasks to set the specific actions to be performed by the event handling task. Furthermore, in response to a user's template arrangement operation, the second schematic icons 304 for event handling tasks and the second schematic icons 305 for routing conditions can be sequentially connected in the template. Therefore, based on the second schematic icons 304 for event handling tasks and the second schematic icons 305 for routing conditions displayed in the template, and their interconnections, the event handling tasks included in the event handling template and their processing order can be determined.

[0166] Step 203: Based on the task processing order in the target event processing template, create a task object corresponding to the event processing task to be processed in the preset task database;

[0167] In this embodiment of the application, the intelligent operation center typically needs to handle a massive number of management events. In processing these events, it is necessary to minimize processing latency to improve efficiency.

[0168] Therefore, the intelligent operation center can execute multiple management events simultaneously using a concurrent execution method. If the intelligent operation center needs to execute a management event, it can write the event processing task in the target event processing template corresponding to the management event into a preset task database, thereby creating at least one task object.

[0169] However, during event management, tasks need to be processed sequentially, which may introduce waiting time. If all event processing tasks in the target event template corresponding to the managed event are written to the task database, the database may accumulate temporarily unprocessable tasks. Therefore, instead of writing all event processing tasks in the target event template, a task object corresponding to the currently pending event processing task can be created in a preset task database according to the task processing order in the target event template. After the task object is processed, subsequent event processing tasks are written sequentially. This ensures that all task objects in the task database represent the currently pending event processing tasks, further improving data processing efficiency.

[0170] Step 204: Invoke the preset task processing resources to process the task object;

[0171] In this embodiment of the application, the task objects in the database can be processed by calling human resources, service platforms that communicate with the database, electronic devices that communicate with the database, and other task processing resources.

[0172] In a specific implementation, the task objects in the task database can record information such as the name of their corresponding event processing task and the execution method. Therefore, the intelligent operation center can invoke the corresponding task processing resources to process the task object based on the execution method recorded in the task object.

[0173] Step 205: After the task object is processed, according to the task processing order, create the next task object of the event processing task to be processed in the preset task database, and repeat the step of calling the preset task processing resources to process the task object until the event processing task at the end of the task processing order in the target event processing template is processed.

[0174] In this embodiment, once the task object is processed, the current event processing task can be considered complete. At this point, according to the task processing order, the next pending event processing task following the currently completed task needs to be processed. This can be achieved by creating a task object for the next pending event processing task in a preset task database and repeatedly executing the step of calling preset task processing resources to process the task object, thus completing the next event processing task. Therefore, the event processing tasks can be processed sequentially through the task database until the event processing task at the end of the task processing order in the target event processing template is completed. At this point, the management event processing can be considered complete.

[0175] In this application, the task object that has been processed can be moved to the historical task list by the task database or deleted.

[0176] As a specific example of this application, Figure 4 This is a schematic diagram of a task processing system according to an embodiment of this application. The task processing system may include a task allocation service layer 401, a task writing layer 402, and a database layer 403. The database layer 403 may include several task databases. The task database includes a primary database and a backup database corresponding to the primary database. Data in the primary database can be backed up to the backup database, so that if the primary database is damaged, the data can be stored in the backup database in a timely manner.

[0177] When it is necessary to execute the target event processing template corresponding to the managed event, a template instance can be created in the task allocation service layer 401. The template instance can contain at least one event processing task. The task allocation service layer 401 can call the task writing layer 402 to create a task object corresponding to the event processing task in the database of the database layer 403. The intelligent operation center can call preset task processing resources to process the task object. After the task object is processed, the task allocation service layer 401 can call the task writing layer 402 to create the next task object to be processed in the database of the database layer 403 according to the task processing order, and repeat the step of calling preset task processing resources to process the task object until the event processing task at the end of the task processing order in the target event processing template is processed.

[0178] The task writing layer 402 can modify the bytecode of the Java SDK data storage code to enable simultaneous writing to multiple databases, further improving task processing capabilities. Simultaneously, the task writing layer 402 can also determine the database to which the task object is to be written. Specifically, it can perform a modulo-weighted calculation based on the task object's task identifier information and determine the database to be written based on the calculation result. Depending on actual needs, the task writing layer 402 can also horizontally partition the data tables in the database based on the task identifier information.

[0179] As an example of this application, Figure 5 This is a schematic diagram of an intelligent operation center according to an embodiment of this application. The intelligent operation center may include an event standardization module 501, an event deduplication / fusion module 502, an event monitoring module 503, a task execution engine 504, a task list module 505, a task processing resource service module 506, an open platform service module 507, a scene management module 508, a tag management module 509, an evaluation service module 510, a database 511, an intelligent operation center operation entry point 512, and an application access interface 513. An artificial intelligence processing platform 514 and an event acquisition device 515 are communicatively connected to the intelligent operation center.

[0180] After the event acquisition device 515 collects management events, it can send the management events to the event standardization module 501.

[0181] The event standardization module 501 standardizes the management events, and then the event deduplication / fusion module 502 performs deduplication or fusion of the management events.

[0182] The event listening module 503 can monitor whether the event deduplication / fusion module 502 has acquired a new management event, and, through the computing power provided by the artificial intelligence processing platform 514, determine the management event's attribute information.

[0183] Meanwhile, the scene management module 508 can also monitor whether the event deduplication / fusion module 502 has obtained a new management event and whether the management event meets the preset scene management conditions. If the scene management conditions are met, the scene management module 508 will match the target event processing template.

[0184] Subsequently, the task execution engine 504 executes at least one event processing task for the managed event in the target event processing template sequentially, following the task processing order in the target event processing template. During task execution, the task list module 505 can display the status of the currently executing event processing task, and the task processing resources required to execute the event processing task can be obtained through the task processing resource service module 506 or the open platform service module 507. Furthermore, the open platform service module 507 can also provide functions such as custom editing of event processing tasks and registration of algorithm models.

[0185] The tag management module 509 can add tag information to the managed events during the standardization process of the event standardization module 501, or during the matching of target event processing templates by the event listening module 503 or the scene management module 508. This allows for matching of target event processing templates based on the tag information. Subsequently, the task list module 505 can also categorize and display the status of currently executing event processing tasks based on the tag information provided by the tag management module 509.

[0186] Database 511 can provide data storage functions for various modules in the intelligent operation center, as well as storage functions for management events.

[0187] The evaluation service module 510 provides users with service evaluation functionality. The intelligent operation center operation entry point 512 provides users with a way to access the intelligent operation center. The intelligent operation center and application access interface 513 provides users with a way to access the intelligent operation center through applications.

[0188] The management event processing method of this application embodiment obtains management events; matches a target event processing template in a preset event processing template according to the attribute information of the management event; creates a task object corresponding to the event processing task to be processed in a preset task database according to the task processing order in the target event processing template; calls preset task processing resources to process the task object; after the task object is processed, creates the next task object to be processed in the preset task database according to the task processing order, and repeats the step of calling preset task processing resources to process the task object until the event processing task at the end of the task processing order in the target event processing template is processed. This allows management events to be processed according to a preset standardized processing flow, improving event processing efficiency. Simultaneously, by decomposing the event processing flow into multiple event processing tasks through the event processing template, the event processing flow can be made more refined, facilitating the maintenance of high processing quality for the management events. Furthermore, by processing the event processing tasks sequentially through the task database, efficient processing of massive amounts of management events is achieved.

[0189] Reference Figure 6 The diagram illustrates a flowchart of a task processing method embodiment according to this application, which may specifically include the following steps:

[0190] Step 601, obtain the target event;

[0191] In this embodiment, events that can be processed using a process-oriented approach can be generated in various fields such as internet operations and maintenance, streamlined industrial production, and personal schedule management. An intelligent operation center can be used to process these process-oriented events. Thus, the intelligent operation center can acquire the target event.

[0192] Specifically, the target event can be an event actively sent by the user to the intelligent operation center, or an event obtained by the intelligent operation center using event acquisition equipment; this application does not impose any restrictions on this.

[0193] In practice, the information sent by the event acquisition device to the intelligent operation center may be unstandardized. Unstandardized information may be difficult for the intelligent operation center to identify as valid and to process further. Therefore, it is necessary to further process the information collected by the event acquisition device to generate standardized target events.

[0194] Specifically, after obtaining the information sent by the event acquisition device, the intelligent operation center can convert the information sent by the event acquisition device into a standardized target event by mapping non-standard fields in the information sent by the event acquisition device to standard fields, extracting key fields in the information sent by the event acquisition device and recombining or disassembling the key fields, and filling the key fields in the information sent by the event acquisition device into a standard template.

[0195] In practical implementation, since there are many types of event acquisition devices, different types of event acquisition devices can simultaneously acquire the same event, which may result in identical or partially identical target events. Therefore, the target events can also be deduplicated or merged.

[0196] Specifically, the intelligent operation center can identify whether target events are identical or partially identical based on fields such as title, description, type, time, and location contained in the target events. If identical target events exist, deduplication can be performed, retaining only one of the multiple identical target events. If partially identical target events exist, they can be merged, combining multiple target events and deleting duplicate content.

[0197] Step 602: Match the target event processing template in the preset event processing templates according to the attribute information of the target event;

[0198] In this embodiment, the target event may have attribute information. The attribute information can be determined based on fields in the target event. For example, if the target event contains fields related to "product A" and "production," then the target event may have the attribute information "produce product A." If the target event contains fields related to "system A" and "fault," then the target event may have the attribute information "repair system A."

[0199] In this embodiment, the intelligent operation center may have at least one preset event processing template. The event processing template may include at least one event processing task required to process the target event, and the task processing order of the event processing tasks. Thus, the intelligent operation center can standardize the processing flow of the target event and decompose the event processing flow into multiple event processing tasks, making the event processing flow more refined and facilitating the maintenance of high processing quality for the target event.

[0200] In this embodiment, the target event can have many different types. Furthermore, even when the target event types are the same, the processing flow of the target event can differ depending on the actual situation of the target event. Therefore, the intelligent operation center can store a large number of event processing templates. After acquiring the target event, a suitable target event processing template can be matched from the preset event processing templates based on the attribute information of the target event.

[0201] In specific implementations, depending on actual needs, a mapping relationship between attribute information and event processing templates can be preset to determine the target event processing template corresponding to the target event based on the mapping relationship; alternatively, a preset algorithm model can be used to recommend the target event processing template based on the attribute information; or the event execution mechanism corresponding to the target event can be determined based on the attribute information, and the event processing template preset by the event execution mechanism can be used as the target event processing template.

[0202] Step 603: Using the task processing order in the target event processing template, execute at least one event processing task for the target event in the target event processing template in sequence.

[0203] In this embodiment of the application, after determining the target event processing template, the target event can be processed according to the target event processing template. Therefore, the task processing order in the target event processing template can be used to sequentially execute at least one event processing task for the target event in the target event processing template, thereby completing the processing of the target event.

[0204] In a specific implementation, the target event processing template may also include execution conditions, thus the processing flow within the target event processing template may have branching flows. Therefore, depending on whether the execution conditions are met, the target event processing template may have different task processing sequences and event processing tasks. Specifically, during the process of the intelligent operation center executing event processing tasks sequentially according to the task processing sequence, the task processing sequence may point to an execution condition, and subsequent corresponding task processing sequences and event processing tasks can be executed based on whether the execution condition is met.

[0205] In a practical implementation, the event processing task can be executed by the intelligent operation center itself, or by at least one electronic device communicatively connected to the intelligent operation center. Examples include controlling production equipment to initiate fault detection procedures or sending notification information to the mobile terminals of specific personnel.

[0206] As an example of this application, the target event is the production of product A on [date]. The target event may have the attribute information "Production of product A". Based on the attribute information "Production of product A", a target event processing template "Product A Production Process" can be matched from a preset event processing template. In the target event processing template "Product A Production Process", the event processing tasks, in the order of task processing, can be "Add raw material a", "Add raw material b after a preset time a", "Inspect product quality", and the execution condition "Product quality meets condition x". If the execution condition "Product quality meets condition x" is met, the subsequent event processing task, in the order of task processing, is "Production completed". If the execution condition "Product quality meets condition x" is not met, the subsequent event processing tasks, in the order of task processing, are "Obtain contact information for technical personnel" and "Notify technical personnel to process product A".

[0207] The target event processing method of this application embodiment obtains a target event; matches a target event processing template in a preset event processing template according to the attribute information of the target event; and sequentially executes at least one event processing task for the target event in the target event processing template according to the task processing order in the target event processing template. This allows the target event to be processed according to a preset standardized processing flow, improving event processing efficiency. Simultaneously, by decomposing the event processing flow into multiple event processing tasks through the event processing template, the event processing flow can be made more refined, facilitating the maintenance of high processing quality for the target event.

[0208] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of this application are not limited to the described order of actions, because according to the embodiments of this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of this application.

[0209] Reference Figure 7 The diagram illustrates a structural block diagram of an embodiment of a management event processing device according to this application, which may specifically include the following modules:

[0210] Module 701 is used to acquire management events;

[0211] The matching module 702 is used to match a target event processing template in a preset event processing template according to the attribute information of the managed event;

[0212] The execution module 703 is used to execute at least one event processing task for the management event in the target event processing template in sequence according to the task processing order in the target event processing template.

[0213] In one embodiment of this application, the attribute information includes at least one of tag information, content information, location information, and time information;

[0214] The matching module includes:

[0215] The model input submodule is used to input at least one of the tag information, content information, location information, and time information of the managed event into a preset event allocation model;

[0216] The first matching submodule is used to match the target event processing template in the preset event processing templates based on the template information output by the event allocation model.

[0217] In one embodiment of this application, the attribute information includes category information;

[0218] The matching module includes:

[0219] The relationship lookup submodule is used to look up whether there is a preset template mapping relationship between the category information of the managed event and the event processing template;

[0220] The second matching submodule is used to use the event processing template corresponding to the category information of the managed event as the target event processing template if there is a preset template mapping relationship between the category information of the managed event and the event processing template.

[0221] In one embodiment of this application, the matching module further includes:

[0222] The organization lookup submodule is used to find the event execution organization corresponding to the management event in a preset event allocation list if there is no preset template mapping relationship between the category information of the management event and the event processing template.

[0223] The third matching submodule is used to use the event processing template corresponding to the event execution mechanism as the target event processing template.

[0224] In one embodiment of this application, the matching module includes:

[0225] The scene recognition submodule is used to identify whether the management event meets the preset scene management conditions based on the attribute information of the management event;

[0226] The fourth matching submodule is used to use the event processing template corresponding to the preset scenario management conditions as the target event processing template if the management event meets the preset scenario management conditions.

[0227] In one embodiment of this application, the scene recognition submodule includes:

[0228] The time period area identification unit is used to identify whether the event time of the management event is within a preset time period and / or whether the event location of the management event is within a preset area based on the attribute information of the management event;

[0229] The scene recognition unit is used to determine whether the management event meets the preset scene management conditions if the event time of the management event is within a preset time period and / or the event location of the management event is within a preset area.

[0230] In one embodiment of this application, the execution module includes:

[0231] The object creation submodule is used to create a task object corresponding to the event processing task to be processed in a preset task database according to the task processing order in the target event processing template.

[0232] The submodule is invoked to call preset task processing resources to process the task object;

[0233] The repeat submodule is used to create a task object for the next pending event processing task in a preset task database according to the task processing order after the task object is processed, and repeatedly execute the step of calling the preset task processing resources to process the task object until the event processing task at the end of the task processing order in the target event processing template is completed.

[0234] In one embodiment of this application, the apparatus further includes:

[0235] The module generation module is used to respond to template arrangement operations, create at least one preset type of event processing task in a blank template, determine the task processing order between the event processing tasks, and obtain an event processing template.

[0236] Reference Figure 8 The diagram illustrates a structural block diagram of an embodiment of a management event processing device according to this application, which may specifically include the following modules:

[0237] Event acquisition module 801 is used to acquire target events;

[0238] The template matching module 802 is used to match a target event processing template in a preset event processing template according to the attribute information of the target event;

[0239] The template execution module 803 is used to execute at least one event processing task for the target event in the target event processing template in sequence, according to the task processing order in the target event processing template.

[0240] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0241] This application also provides an electronic device, including:

[0242] One or more processors; and

[0243] One or more machine-readable media having instructions stored thereon, which, when executed by the one or more processors, cause the electronic device to perform the methods described in the embodiments of this application.

[0244] This application also provides one or more machine-readable media storing instructions that, when executed by one or more processors, cause the processors to perform the methods described in this application.

[0245] This application also discloses a software product, including a computer program / instructions, wherein when the computer program / instructions are executed, they implement one or more methods as described in the embodiments of this application.

[0246] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0247] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus, or computer program products. Therefore, embodiments of this application can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of this application can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0248] This application describes embodiments with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0249] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0250] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0251] Although preferred embodiments of the present application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present application.

[0252] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0253] The above provides a detailed description of a management event processing method, a task processing method, a management event processing device, and a task processing device provided by this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method of managing event processing, the method comprising: Applied to an intelligent operation center, the intelligent operation center is communicatively connected to at least one event acquisition device, including: Acquiring management events includes: acquiring information sent by the event acquisition device; extracting key fields from the information, and recombining or disassembling the key fields and filling them into a standard template to generate standardized management events; Based on the title, description, type, time, and location fields contained in the management events, identify management events that are identical or partially identical; The same management events are deduplicated. Merge the management events that are partially identical. Based on the attribute information of the managed event, a target event processing template is matched in a preset event processing template; the attribute information includes at least one of tag information, content information, location information, time information, and category information; the category information is divided according to the event execution agency, event scenario, or location corresponding to the managed event; the target event processing template contains execution conditions, which are used to determine the task processing order and event processing tasks; Using the task processing order in the target event processing template, at least one event processing task for the management event in the target event processing template is executed sequentially according to whether the execution conditions are met; The step of matching a target event processing template in a preset event processing template based on the attribute information of the managed event includes: inputting at least one of the tag information, content information, location information, and time information of the managed event into a preset event allocation model; and matching a target event processing template in a preset event processing template based on the template information output by the event allocation model. The step of matching a target event processing template in a preset event processing template based on the attribute information of the managed event further includes: checking whether there is a preset template mapping relationship between the category information of the managed event and the event processing template; if there is a preset template mapping relationship between the category information of the managed event and the event processing template, the event processing template corresponding to the category information of the managed event is used as the target event processing template. The step of matching a target event processing template in a preset event processing template based on the attribute information of the managed event further includes: identifying whether the managed event meets preset scenario management conditions based on the attribute information of the managed event; if the managed event meets the preset scenario management conditions, using the event processing template corresponding to the scenario management conditions as the target event processing template.

2. The method according to claim 1, characterized in that, The step of matching a target event handling template in a preset event handling template based on the attribute information of the managed event further includes: If there is no preset template mapping relationship between the category information of the management event and the event processing template, the event execution agency corresponding to the management event is searched in the preset event allocation list; Use the event processing template corresponding to the event execution mechanism as the target event processing template.

3. The method according to claim 1, characterized in that, The step of identifying whether a management event meets preset scenario management conditions based on the attribute information of the management event includes: Based on the attribute information of the managed event, identify whether the event time of the managed event is within a preset time period, and / or whether the event location of the managed event is within a preset area; If the event time of the management event falls within a preset time period, and / or the event location of the management event falls within a preset area, the management event is determined to meet the preset scenario management conditions.

4. The method according to claim 1, characterized in that, The step of sequentially executing at least one event processing task for the managed event in the target event processing template according to the task processing order in the target event processing template includes: Based on the task processing order in the target event processing template, create a task object corresponding to the event processing task to be processed in the preset task database; The task object is processed by calling a preset task processing resource. After the task object is processed, according to the task processing order, the next task object to be processed for the event processing task is created in the preset task database, and the step of calling the preset task processing resources to process the task object is repeated until the event processing task at the end of the task processing order in the target event processing template is processed.

5. The method according to claim 1, characterized in that, The method further includes: In response to the template arrangement operation, at least one event handling task of a preset type is created in the blank template, and the task processing order between the event handling tasks is determined to obtain the event handling template.

6. A management event processing device, characterized in that, Applied to an intelligent operation center, the intelligent operation center is communicatively connected to at least one event acquisition device, including: The acquisition module is used to acquire management events; determine identical or partially identical management events based on the title, description, type, time, and location fields contained in the management events; perform deduplication on identical management events; and perform fusion on partially identical management events; wherein, acquiring management events includes: acquiring information sent by the event acquisition device; extracting key fields from the information, and recombining or decomposing the key fields and filling them into a standard template to generate standardized management events; The matching module is used to match a target event processing template in a preset event processing template according to the attribute information of the managed event; the attribute information includes at least one of tag information, content information, location information, time information, and category information; the category information is divided according to the event execution agency, event scenario, or location corresponding to the managed event; the target event processing template contains execution conditions, which are used to determine the task processing order and event processing tasks; An execution module is used to execute at least one event processing task for the management event in the target event processing template in sequence, according to whether the execution conditions are met, based on the task processing order in the target event processing template. The matching module includes: a model input submodule, used to input at least one of the tag information, content information, location information, and time information of the managed event into a preset event allocation model; and a first matching submodule, used to match a target event processing template in a preset event processing template according to the template information output by the event allocation model. The matching module further includes: a relationship lookup submodule, used to look up whether there is a preset template mapping relationship between the category information of the managed event and the event processing template; and a second matching submodule, used to take the event processing template corresponding to the category information of the managed event as the target event processing template if there is a preset template mapping relationship between the category information of the managed event and the event processing template. The matching module further includes: a scene recognition submodule, used to identify whether the management event meets preset scene management conditions based on the attribute information of the management event; and a fourth matching submodule, used to use the event processing template corresponding to the scene management conditions as the target event processing template if the management event meets the preset scene management conditions.

7. An electronic device, characterized in that, include: One or more processors; and One or more machine-readable media having instructions stored thereon, which, when executed by the one or more processors, cause the electronic device to perform one or more methods as described in claims 1-5.

8. One or more machine-readable media having instructions stored thereon that, when executed by one or more processors, cause the processors to perform one or more methods as described in claims 1-5.

9. A software product comprising a computer program / instructions, wherein, When the computer program / instructions are executed, the method described in one or more of claims 1-5 is performed.

Citation Information

Patent Citations

  • Event processing method, device and equipment and computer storage medium

    CN109684047A

  • Event flow processing method and device, storage medium and program product

    CN112784199A

  • Asynchronous processing method and device, electronic equipment, storage medium and roadside equipment

    CN112905314A