CN112668854A - Multi-organization-based efficient event dispatching method and related device - Google Patents
Multi-organization-based efficient event dispatching method and related device Download PDFInfo
- Publication number
- CN112668854A CN112668854A CN202011537205.5A CN202011537205A CN112668854A CN 112668854 A CN112668854 A CN 112668854A CN 202011537205 A CN202011537205 A CN 202011537205A CN 112668854 A CN112668854 A CN 112668854A
- Authority
- CN
- China
- Prior art keywords
- event
- distributed
- target
- state
- personnel
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 230000008520 organization Effects 0.000 claims abstract description 69
- 238000012216 screening Methods 0.000 claims abstract description 12
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 230000004888 barrier function Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Abstract
The application discloses an event dispatching method and a related device based on multi-organization high efficiency, which are used for optimizing parking lot services, improving user experience and guaranteeing smooth popularization of an unattended scheme. The method comprises the following steps: randomly acquiring an event to be distributed from a real-time table; acquiring organization information of the project according to the project identifier; acquiring an organization personnel list according to the organization information; screening a staff list to be distributed according to the organization staff list, wherein the staff list to be distributed comprises staff in an online and non-working state; acquiring a preset event dispatching priority rule and a preset personnel dispatching priority rule according to the organization information; determining a handler of the event to be distributed according to a preset personnel allocation priority rule and a list of the personnel to be distributed, and setting the status of the handler as a status to be processed; setting the priority of the event to be distributed according to a preset event dispatching priority rule, and setting the state of the event to be distributed as a state to be processed.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to an event dispatching method and related apparatus based on multi-organization high efficiency.
Background
In the current society, the competition of various industries is quite intense, and the parking lot industry is no exception. When the number of the accessed business circles is increased, the number of the projects is increased, the problems encountered in the parking lot are inevitable, and some problems are more or less encountered. For example, in sudden heavy rain weather, light becomes dark, raindrops are too dense, the identification effect of a camera is affected, a license plate cannot be correctly identified, and vehicles cannot enter or exit; the problem of the photosensitive angle of the entrance and the exit of the parking lot causes light reflection to influence the identification of the license plate; the access is influenced by sudden power failure and network disconnection in part of areas; software failure, failure of a server to cause the failure of the yard service, and the like.
In the prior art, although most of yards in the market currently propose unattended schemes in order to save manpower and material resource costs, many problems still cannot be solved by the unattended schemes, and generally problem events need to be uploaded to wait for processing personnel to go to the yard for processing. In the process, if the problem event is accurately, reasonably and quickly dispatched and cannot be quickly uploaded at the current terminal parking lot, the normal operation of the parking lot is influenced, and the smooth trip of the vehicle owner is influenced, so that the user experience of the vehicle owner is poor.
Disclosure of Invention
The application provides an event dispatching method and a related device based on multi-organization high efficiency, which are used for optimizing parking lot services, improving user experience and guaranteeing smooth popularization of an unattended scheme.
The application provides a multi-organization-based efficient event dispatching method in a first aspect, which comprises the following steps:
randomly acquiring an event to be distributed from a real-time table, wherein the real-time table stores a plurality of events to be distributed, and the events to be distributed carry item identifiers of items in which the events are located;
acquiring organization information of the project according to the project identifier;
acquiring an organization personnel list according to the organization information;
screening a staff list to be distributed according to the organization staff list, wherein the staff list to be distributed comprises staff in an online and non-working state;
acquiring a preset event dispatching priority rule and a preset personnel dispatching priority rule according to the organization information;
determining a handler of the event to be distributed according to the preset personnel allocation priority rule and the list of the personnel to be distributed, and setting the status of the handler as a status to be processed;
setting the priority of the event to be distributed according to the preset event dispatching priority rule, and setting the state of the event to be distributed as a state to be processed.
Optionally, before the obtaining of the preset event assignment priority rule and the preset staff assignment priority rule according to the organization information, the method further includes:
locking the event to be distributed;
after the setting the priority of the event to be distributed according to the preset event dispatch priority rule and the setting the state of the event to be distributed as a state to be processed, the method further comprises the following steps:
and unlocking the event to be distributed.
Optionally, after the setting the priority of the event to be distributed according to the preset event dispatch priority rule, and setting the state of the event to be distributed as a state to be processed, the method further includes:
acquiring a target event with the highest priority from the real-time table;
determining whether the target event has been dispatched;
if not, judging whether the state of a target person is a to-be-processed state, wherein the target person is a processing person of the target event;
if yes, dispatching the target event to the target personnel, and setting the target event and the state of the target personnel to be a processing state.
Optionally, the obtaining of the target event with the highest priority from the real-time table includes:
acquiring a to-be-processed event with the highest priority from the real-time table;
when the number of the events to be processed with the highest priority is 1, determining that the events to be processed are target events;
and when the number of the events to be processed with the highest priority is greater than or equal to 2, determining the events to be processed with the highest priority and the longest access time as target events.
Optionally, after obtaining the target event with the highest priority from the real-time table and before determining whether the target event has been dispatched, the method further includes:
locking the target event;
after the determining whether the target event has been dispatched, the method further comprises:
and if so, unlocking the target event.
Optionally, after the determining whether the target event has been dispatched and before the determining whether the state of the target person is a pending state, the method further includes:
locking the target person;
after the determining whether the state of the target person is a pending state, the method further includes:
and if not, unlocking the target personnel.
Optionally, after the dispatching the target event to the target person, the method further comprises:
storing the target event into a history table, wherein the history table is used for storing the event which is processed completely;
and deleting the target event from the real-time table.
A second aspect of the present application provides a multi-organization based efficient event dispatching system, comprising:
the system comprises a first acquisition unit, a second acquisition unit and a processing unit, wherein the first acquisition unit is used for randomly acquiring an event to be distributed from a real-time table, the real-time table stores a plurality of events to be distributed, and the events to be distributed carry item identifiers of items in which the events are located;
the second acquisition unit is used for acquiring the organization information of the project according to the project identifier;
the third acquisition unit is used for acquiring an organization personnel list according to the organization information;
the screening unit is used for screening a to-be-distributed personnel list according to the organization personnel list, and the to-be-distributed personnel list comprises personnel in an online and non-working state;
the fourth acquisition unit is used for acquiring a preset event dispatching priority rule and a preset personnel dispatching priority rule according to the organization information;
the determining unit is used for determining the processing personnel of the event to be distributed according to the preset personnel dispatching priority rule and the list of the personnel to be distributed and setting the state of the processing personnel as a state to be processed;
the setting unit is used for setting the priority of the event to be distributed according to the preset event dispatching priority rule and setting the state of the event to be distributed as a state to be processed;
a fifth obtaining unit, configured to obtain a target event with a highest priority from the real-time table;
a first judging unit, configured to judge whether the target event has been dispatched;
a second judging unit, configured to, when the first judging unit judges that the result is negative, judge whether a state of a target person is a to-be-processed state, where the target person is a processing person of the target event;
and the dispatching unit is used for dispatching the target event to the target person and setting the target event and the state of the target person as a processing state when the judgment result of the second judgment unit is yes.
Optionally, the system further comprises:
the first locking unit is used for locking the event to be distributed;
the first unlocking unit is used for unlocking the event to be distributed after the setting unit sets the priority of the event to be distributed according to the preset event dispatching priority rule and sets the state of the event to be distributed as the state to be processed.
Optionally, the system further comprises:
the second locking unit is used for locking the target event;
and the second unlocking unit is used for unlocking the target event when the judgment result of the first judgment unit is yes.
Optionally, the system further comprises:
the third locking unit is used for locking the target person;
and the third unlocking unit is used for unlocking the target person when the judgment result of the second judgment unit is negative.
Optionally, the system further comprises:
the storage unit is used for storing the target event into a history table, and the history table is used for storing the processed event;
and the deleting unit is used for deleting the target event from the real-time table.
A third aspect of the present application provides an event dispatching device based on multi-organization efficiency, the device comprising:
the device comprises a processor, a memory, an input and output unit and a bus;
the processor is connected with the memory, the input and output unit and the bus;
the memory holds a program that the processor calls to perform the first aspect and the event dispatching method optional of any of the first aspects.
A fourth aspect of the present application provides a computer-readable storage medium having a program stored thereon, where the program is executed on a computer to perform the event dispatching method selected from any one of the first aspect and the first aspect.
According to the technical scheme, the method has the following advantages:
by the method, the problem event can be rapidly, accurately and efficiently dispatched to the hands of the processing personnel, so that the processing personnel can rapidly go to the site or solve the problem event at the background, and the smooth trip of the vehicle owner is guaranteed. By the method, the parking lot service can be optimized, the user experience is improved, and the smooth popularization of the unattended scheme is guaranteed.
Drawings
FIG. 1 is a flowchart illustrating an embodiment of a multi-organization-based efficient event dispatching method provided by the present application;
FIG. 2 is a schematic flow chart of another embodiment of an efficient event dispatching method based on multiple organizations according to the present application;
FIG. 3 is a schematic structural diagram of an embodiment of a multi-organization-based efficient event dispatching system provided in the present application;
FIG. 4 is a schematic structural diagram of another embodiment of the multi-organization based efficient event dispatching system provided in the present application;
fig. 5 is a schematic structural diagram of an embodiment of an event dispatching device based on multi-organization efficiency provided by the present application.
Detailed Description
The application provides an event dispatching method and a related device based on multi-organization high efficiency, which are used for optimizing parking lot services, improving user experience and guaranteeing smooth popularization of an unattended scheme.
It should be noted that the multi-organization-based efficient event dispatching method provided by the present application may be applied to a terminal, a system, or a server, for example, the terminal may be a fixed terminal such as a smart phone or a computer, a tablet computer, a smart television, a smart watch, a portable computer terminal, or a desktop computer. For convenience of explanation, the terminal is taken as an execution subject for illustration in the present application.
Referring to fig. 1, fig. 1 is a block diagram illustrating an embodiment of a multi-organization based efficient event dispatching method provided by the present application, the method including:
101. randomly acquiring an event to be distributed from a real-time table, wherein the real-time table stores a plurality of events to be distributed, and the events to be distributed carry item identifications of items;
in the application, the terminal uses the relational database MySQL to establish a real-time table, the real-time table is used for storing events to be distributed on the project, and in addition, the terminal uses Redis as a caching tool to further reduce the time consumption of event dispatching.
In the application, a management unit is composed of a plurality of organizations, and one organization can be responsible for managing a plurality of projects, for example, in a parking lot management unit, a certain organization a is responsible for managing a plurality of parking lot projects, wherein a problem event needing to be solved by a processing person occurs in a certain parking lot project B, after the problem event is generated, a terminal stores the problem event in a to-be-distributed state in the real-time table, and the problem event carries a project identifier of the parking lot project B where the problem event is located, so that the terminal can distinguish the problem event of each project.
After the problem event is generated, the terminal needs to dispatch the problem event, and first, the terminal randomly obtains a problem event (an event to be distributed) from the real-time table to a memory.
102. Acquiring organization information of the project according to the project identifier;
the terminal can obtain organization information of an organization where the project is located, that is, information of an organization a in charge of managing the parking lot project B, through the project identifier carried by the problem event (to-be-distributed event).
It should be noted that the terminal may directly obtain the cache of the organization information from the cache tool, and request http to obtain the organization information and write the organization information into the cache if the cache is expired, that is, request the server to obtain the organization information and write the organization information into the cache, thereby ensuring that the request is not repeated during multi-service deployment, reducing the number of http requests, and reducing the time consumed by time allocation.
103. Acquiring an organization personnel list according to the organization information;
after acquiring the information of the organization a responsible for managing the problem event (event to be distributed), the terminal may acquire the staff list of the organization a, that is, the staff list working in the organization a, through the information of the organization a. In the organization personnel list, the status of the personnel includes an online status/offline status and an operating status/non-operating status, and the like.
In the same step 102, the terminal may directly obtain the cache of the organization personnel list from the cache tool, and request http to obtain and store in the cache if the cache is expired.
104. Screening a staff list to be distributed according to the organization staff list, wherein the staff list to be distributed comprises staff in an online and non-working state;
after the terminal acquires the organization personnel list, the processing personnel (to-be-allocated personnel) capable of processing the problem event at present can be screened according to the organization personnel list.
Specifically, the terminal marks the organizer list acquired in step 103 as userList 1; then acquiring a list of people currently in an online state in all organizations connected with the terminal, and marking the list as userList 2; the intersection of userList1 and userList2 is marked as userList3, userList3 is the personnel list currently in the online state in the organization, at this time, the terminal uses userList3 to query the personnel list in the online and non-working state, marked as userList4, and userList4 is the personnel list to be allocated in the application, and the personnel screening is completed.
105. Acquiring a preset event dispatching priority rule and a preset personnel dispatching priority rule according to the organization information;
there are different event assignment priority rules and people assignment priority rules in different projects and organizations. For example, the event dispatch priority rule may be: taking the problem event of the parking lot barrier as the highest priority, taking the problem event of the payment as the priority of the next level, or taking the problem event from a certain project A as the highest priority, and taking the problem event from another project B as the priority of the next level, and the like; the personnel assignment priority rule may be: the supervisor level personnel are the dispatching personnel with the highest priority, the assistant level personnel are the dispatching personnel with the next-level priority, the specific event and the dispatching rule of the personnel can be distinguished according to different projects and organizations, the specific event and the dispatching rule of the personnel need to be determined by combining with the actual situation, and the specific situation is not limited here.
The terminal can acquire the event assignment priority rule and the personnel assignment priority rule preset by the organization according to the acquired organization information, and maintain the event assignment priority rule to the cache tool. It should be noted that, since there is a problem that the priority of the staff assignment priority rule is changing due to the online or offline state of the staff, the terminal may not need to maintain the staff assignment priority rule in the caching tool.
106. Determining a handler of the event to be distributed according to the preset personnel allocation priority rule and the list of the personnel to be distributed, and setting the status of the handler as a status to be processed;
the terminal determines corresponding processing personnel for the problem event (event to be distributed) according to the obtained personnel assignment priority rule, and the terminal needs to determine from the list of personnel to be distributed screened in the step 104, namely, from the personnel in the online and non-working state in the current project according to the personnel assignment priority rule.
After determining a processing person of the problem event (event to be distributed), the terminal sets the processing person to be in a state to be processed. It should be noted that the pending state refers to a state in which the processing person currently has a problem event that needs to be processed.
107. And setting the priority of the event to be distributed according to the preset event dispatching priority rule, and setting the state of the event to be distributed as a state to be processed.
After determining the handler of the problem event (event to be distributed), the pre-distribution of the problem event is actually completed, and the terminal needs to set the priority of the problem event according to an event distribution priority rule, for example, if the problem event is that a barrier cannot be opened normally, the problem event belongs to a problem of a parking lot barrier, and if the problem event is the event with the highest priority in the event distribution priority rule, the terminal gives the highest priority to the problem event.
The terminal then also needs to set the problem event (event to be assigned) to a pending state, i.e., a state in which the assigned processing person is waiting to be processed. The pre-allocation of the problem event is completed, and the event to be allocated is changed into an event to be processed, namely the event to be processed is waited for processing by a processing person.
In the embodiment, information such as project information, organization personnel information and assignment rules is cached in Redis by reasonably utilizing a cache tool, so that the information can be conveniently shared during multi-service deployment, the efficiency is improved, and the assignment time is shortened.
In the embodiment, the method can reasonably, quickly and efficiently distribute corresponding processing personnel for the problem event, so that the processing personnel can quickly go to the scene or solve the problem event at the background, and the smooth trip of the vehicle owner is guaranteed. By the method, the parking lot service can be optimized, the user experience is improved, and the smooth popularization of the unattended scheme is guaranteed.
The above is a description of an embodiment of an event dispatching method based on multi-organization in this application, by which event pre-dispatching can be realized, suitable handlers can be determined for the event, and after the event is pre-dispatched, the event needs to be actually dispatched to the handlers, which is described in detail below.
Referring to fig. 2, fig. 2 is a diagram illustrating another embodiment of a multi-organization based efficient event dispatching method provided by the present application, the method including:
201. randomly acquiring an event to be distributed from a real-time table, wherein the real-time table stores a plurality of events to be distributed, and the events to be distributed carry item identifications of items;
202. acquiring organization information of the project according to the project identifier;
203. acquiring an organization personnel list according to the organization information;
204. screening a staff list to be distributed according to the organization staff list, wherein the staff list to be distributed comprises staff in an online and non-working state;
in this embodiment, steps 201 to 204 are similar to steps 101 to 104 of the previous embodiment, and are not described herein again.
205. Locking the event to be distributed;
in this embodiment, before processing the event to be distributed, a locking operation needs to be performed on the event to be distributed, so as to prevent the event to be distributed from being tampered or from being concurrently and repeatedly operated.
206. Acquiring a preset event dispatching priority rule and a preset personnel dispatching priority rule according to the organization information;
207. determining a handler of the event to be distributed according to the preset personnel allocation priority rule and the list of the personnel to be distributed, and setting the status of the handler as a status to be processed;
208. setting the priority of the event to be distributed according to the preset event dispatching priority rule, setting the state of the event to be distributed as a state to be processed, and unlocking the event to be distributed;
in this embodiment, steps 206 to 208 are similar to steps 105 to 107 of the previous embodiment, and are not repeated herein.
It should be noted that, after the terminal completes processing of the event to be distributed, that is, after the event to be distributed is changed into the event to be processed, the event to be processed may be unlocked, so that the terminal executes the subsequent steps to complete the assignment of the event to be processed.
209. Acquiring a target event with the highest priority from the real-time table;
when the terminal dispatches the event, the terminal firstly obtains a pending event with the highest priority at present, namely a target event in the application from the real-time table.
Optionally, the terminal may obtain the event to be processed with the highest priority from the real-time table;
when the number of the events to be processed with the highest priority is 1, determining that the events to be processed are target events;
and when the number of the events to be processed with the highest priority is greater than or equal to 2, determining the events to be processed with the highest priority and the longest access time as target events.
It should be noted that there may be 2 or more than 2 problem events with the same priority in the real-time table, and if the priority is the same and the priority is the current highest priority, the event with the longest access time is taken, so as to ensure reasonable allocation of the events.
210. Determining whether the target event has been dispatched, if not, executing step 211, if yes, returning to step 209;
the terminal determines whether the target event has been dispatched, and if not dispatched and the event status is correct (pending status), step 211 is executed.
It should be noted that before the terminal determines whether the target event has been dispatched, a locking operation needs to be performed on the high target event, so as to prevent a target event from being dispatched multiple times due to concurrent repeated operations. If the terminal determines that the target event has been dispatched, the lock is relinquished and the process returns to step 209.
211. Judging whether the state of the target person is a pending state, if so, executing step 212, otherwise, returning to step 209;
because the target person is occupied by other events, after determining that the target event is not dispatched and the status is correct, the terminal needs to determine whether the current status of the pre-assigned processing person of the target event is correct, that is, whether the current status is a pending status rather than an ongoing status, and if the status is correct, execute step 212.
It should be noted that, before the terminal determines whether the state of the target person is correct, a locking operation needs to be performed on the target person, so as to prevent a target person from being assigned to multiple target events due to concurrent repeated operations. If the terminal determines that the status of the target person is incorrect, the lock is abandoned and the process returns to step 209.
212. Dispatching the target event to the target person, and setting the target event and the state of the target person to be a processing state;
when the terminal determines that the target event and the state of the target person are both correct, the terminal can dispatch the target event to the target person, submit the target person to process the target event, set the target event and the state of the target person to be a processing state, and finish dispatching the event.
Specifically, the terminal may assign an event to a corresponding agent submission event through the websocket.
213. Storing the target event into a history table, wherein the history table is used for storing the event which is processed completely;
in this embodiment, the problem events may be stored in separate tables, with a real-time table for storing unprocessed or processing events and a history table for storing events that have been processed. Specifically, after the problem event processing of the real-time table is completed, the target event is stored in the history table. The history table can be convenient for the later record inquiry and various report statistics functions.
214. The target event is deleted from the real-time table.
After the event processing of the real-time table is finished, the real-time table is deleted from the real-time table, so that the data volume of the real-time table is not large, and the efficiency of data operation is improved.
Referring to fig. 3, fig. 3 is a diagram illustrating an embodiment of a multi-organization based efficient event dispatching system provided by the present application, the system comprising:
a first obtaining unit 301, configured to randomly obtain an event to be distributed from a real-time table, where the real-time table stores a plurality of events to be distributed, and the event to be distributed carries an item identifier of an item where the event is located;
a second obtaining unit 302, configured to obtain organization information where the item is located according to the item identifier;
a third acquiring unit 303, configured to acquire an organization personnel list according to the organization information;
a screening unit 304, configured to screen a to-be-distributed staff list according to the organization staff list, where the to-be-distributed staff list includes staff in an online and non-working state;
a fourth obtaining unit 305, configured to obtain a preset event assignment priority rule and a preset staff assignment priority rule according to the organization information;
a determining unit 306, configured to determine a processing staff of the event to be distributed according to the preset staff dispatching priority rule and the list of staff to be distributed, and set a state of the processing staff as a state to be processed;
a setting unit 307, configured to set a priority of the event to be distributed according to the preset event dispatch priority rule, and set a state of the event to be distributed as a to-be-processed state;
a fifth obtaining unit 308, configured to obtain a target event with a highest priority from the real-time table;
a first judging unit 309, configured to judge whether the target event has been dispatched;
a second judging unit 310, configured to, if the first judging unit judges that the result is negative, judge whether the state of the target person is a to-be-processed state, where the target person is a processing person of the target event;
the assigning unit 311 is configured to assign the target event to the target person and set the state of the target event and the target person as the processing state when the second determination unit determines that the result is yes.
In the embodiment, the system can rapidly, accurately and efficiently dispatch the problem event to the hands of the processing personnel, so that the processing personnel can rapidly go to the scene or solve the problem event at the background, and the smooth trip of the vehicle owner is guaranteed. By the method, the parking lot service can be optimized, the user experience is improved, and the smooth popularization of the unattended scheme is guaranteed.
Referring to fig. 4, fig. 4 is a schematic diagram illustrating an embodiment of a multi-organization-based efficient event dispatching system provided in the present application, the system includes:
a first obtaining unit 401, configured to randomly obtain an event to be distributed from a real-time table, where the real-time table stores a plurality of events to be distributed, and the event to be distributed carries an item identifier of an item where the event is located;
a second obtaining unit 402, configured to obtain organization information where the item is located according to the item identifier;
a third acquiring unit 403 for acquiring an organization personnel list according to the organization information;
a screening unit 404, configured to screen a to-be-distributed staff list according to the organization staff list, where the to-be-distributed staff list includes staff in an online and non-working state;
a fourth obtaining unit 405, configured to obtain a preset event assignment priority rule and a preset staff assignment priority rule according to the organization information;
a determining unit 406, configured to determine a processing staff of the event to be distributed according to the preset staff dispatching priority rule and the list of staff to be distributed, and set a state of the processing staff as a state to be processed;
a setting unit 407, configured to set a priority of the event to be distributed according to the preset event dispatch priority rule, and set a state of the event to be distributed as a to-be-processed state;
a fifth obtaining unit 408, configured to obtain a target event with a highest priority from the real-time table;
a first judging unit 409, configured to judge whether the target event has been dispatched;
a second judging unit 410, configured to, when the first judging unit 409 judges that the result is negative, judge whether the state of the target person is a to-be-processed state, where the target person is a processing person of the target event;
a dispatching unit 411, configured to dispatch the target event to the target person and set the status of the target event and the target person as a processing status when the second determining unit 410 determines that the result is yes.
In this embodiment, the system further includes:
a first locking unit 412, configured to lock the event to be distributed;
a first unlocking unit 413, configured to unlock the event to be distributed after the setting unit sets the priority of the event to be distributed according to the preset event dispatch priority rule, and sets the state of the event to be distributed as a state to be processed.
Optionally, in the system of this embodiment, the system further includes:
a second locking unit 414, configured to lock the target event;
a second unlocking unit 415, configured to unlock the target event when the determination result of the first determining unit 409 is yes.
Optionally, in the system of this embodiment, the system further includes:
a third locking unit 416 for locking the target person;
a third unlocking unit 417, configured to unlock the target person if the determination result of the second determining unit 410 is negative.
In the system of this embodiment, the system further includes:
a storage unit 418, configured to store the target event into a history table, where the history table is used to store the event that has been processed;
a deleting unit 419, configured to delete the target event from the real-time table.
In the system of this embodiment, the functions of each unit correspond to the steps in the method embodiment shown in fig. 2, and are not described herein again.
The present application also provides an event dispatching device based on multi-organization efficiency, please refer to fig. 5, fig. 5 is an embodiment of the event dispatching device based on multi-organization efficiency provided by the present application, the device includes:
a processor 501, a memory 502, an input/output unit 503, and a bus 504;
the processor 501 is connected with the memory 502, the input/output unit 503 and the bus 504;
the memory 502 holds a program that the processor 501 calls to perform any of the above multi-organization based efficient event dispatching methods.
The present application also relates to a computer-readable storage medium having a program stored thereon, wherein the program, when executed on a computer, causes the computer to perform any of the above multi-organization based efficient event dispatching methods.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like.
Claims (10)
1. An efficient multi-organization based event dispatching method, the method comprising:
randomly acquiring an event to be distributed from a real-time table, wherein the real-time table stores a plurality of events to be distributed, and the events to be distributed carry item identifiers of items in which the events are located;
acquiring organization information of the project according to the project identifier;
acquiring an organization personnel list according to the organization information;
screening a staff list to be distributed according to the organization staff list, wherein the staff list to be distributed comprises staff in an online and non-working state;
acquiring a preset event dispatching priority rule and a preset personnel dispatching priority rule according to the organization information;
determining a handler of the event to be distributed according to the preset personnel allocation priority rule and the list of the personnel to be distributed, and setting the status of the handler as a status to be processed;
setting the priority of the event to be distributed according to the preset event dispatching priority rule, and setting the state of the event to be distributed as a state to be processed.
2. The method of claim 1, wherein prior to said obtaining a preset event dispatch priority rule and a preset personnel dispatch priority rule based on said organization information, said method further comprises:
locking the event to be distributed;
after the setting the priority of the event to be distributed according to the preset event dispatch priority rule and the setting the state of the event to be distributed as a state to be processed, the method further comprises the following steps:
and unlocking the event to be distributed.
3. The method according to claim 1, wherein after the setting the priority of the event to be distributed according to the preset event dispatch priority rule and the setting the state of the event to be distributed to a pending state, the method further comprises:
acquiring a target event with the highest priority from the real-time table;
determining whether the target event has been dispatched;
if not, judging whether the state of a target person is a to-be-processed state, wherein the target person is a processing person of the target event;
if yes, dispatching the target event to the target personnel, and setting the target event and the state of the target personnel to be a processing state.
4. The method of claim 3, wherein the obtaining the highest priority target event from the real-time table comprises:
acquiring a to-be-processed event with the highest priority from the real-time table;
when the number of the events to be processed with the highest priority is 1, determining that the events to be processed are target events;
and when the number of the events to be processed with the highest priority is greater than or equal to 2, determining the events to be processed with the highest priority and the longest access time as target events.
5. The method of claim 3, wherein after said retrieving a highest priority target event from said real-time table and before said determining whether said target event has been dispatched, said method further comprises:
locking the target event;
after the determining whether the target event has been dispatched, the method further comprises:
and if so, unlocking the target event.
6. The method of claim 3, wherein after the determining whether the target event has been dispatched and before the determining whether the status of the target person is pending, the method further comprises:
locking the target person;
after the determining whether the state of the target person is a pending state, the method further includes:
and if not, unlocking the target personnel.
7. The method of any one of claims 3 to 6, wherein after said dispatching said target event to said target person, said method further comprises:
storing the target event into a history table, wherein the history table is used for storing the event which is processed completely;
and deleting the target event from the real-time table.
8. An efficient multi-organization based event dispatch system, the system comprising:
the system comprises a first acquisition unit, a second acquisition unit and a processing unit, wherein the first acquisition unit is used for randomly acquiring an event to be distributed from a real-time table, the real-time table stores a plurality of events to be distributed, and the events to be distributed carry item identifiers of items in which the events are located;
the second acquisition unit is used for acquiring the organization information of the project according to the project identifier;
the third acquisition unit is used for acquiring an organization personnel list according to the organization information;
the screening unit is used for screening a to-be-distributed personnel list according to the organization personnel list, and the to-be-distributed personnel list comprises personnel in an online and non-working state;
the fourth acquisition unit is used for acquiring a preset event dispatching priority rule and a preset personnel dispatching priority rule according to the organization information;
the determining unit is used for determining the processing personnel of the event to be distributed according to the preset personnel dispatching priority rule and the list of the personnel to be distributed and setting the state of the processing personnel as a state to be processed;
the setting unit is used for setting the priority of the event to be distributed according to the preset event dispatching priority rule and setting the state of the event to be distributed as a state to be processed;
a fifth obtaining unit, configured to obtain a target event with a highest priority from the real-time table;
a first judging unit, configured to judge whether the target event has been dispatched;
a second judging unit, configured to, when the first judging unit judges that the result is negative, judge whether a state of a target person is a to-be-processed state, where the target person is a processing person of the target event;
and the dispatching unit is used for dispatching the target event to the target person and setting the target event and the state of the target person as a processing state when the judgment result of the second judgment unit is yes.
9. An event dispatching device based on multi-organization high efficiency, characterized in that the device comprises:
the device comprises a processor, a memory, an input and output unit and a bus;
the processor is connected with the memory, the input and output unit and the bus;
the memory holds a program that the processor calls to perform the method of any one of claims 1 to 7.
10. A computer-readable storage medium having a program stored thereon, the program, when executed on a computer, performing the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011537205.5A CN112668854A (en) | 2020-12-23 | 2020-12-23 | Multi-organization-based efficient event dispatching method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011537205.5A CN112668854A (en) | 2020-12-23 | 2020-12-23 | Multi-organization-based efficient event dispatching method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112668854A true CN112668854A (en) | 2021-04-16 |
Family
ID=75408163
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011537205.5A Pending CN112668854A (en) | 2020-12-23 | 2020-12-23 | Multi-organization-based efficient event dispatching method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112668854A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4503499A (en) * | 1982-09-14 | 1985-03-05 | Eaton Corporation | Controlled work flow system |
| GB201310378D0 (en) * | 2013-06-11 | 2013-07-24 | Ibm | Prioritising event processing based on system workload |
| US20140278641A1 (en) * | 2013-03-15 | 2014-09-18 | Fiserv, Inc. | Systems and methods for incident queue assignment and prioritization |
| CN105426236A (en) * | 2015-11-11 | 2016-03-23 | 上海斐讯数据通信技术有限公司 | Realization method and device of high-concurrence state machine as well as system |
| CN109377187A (en) * | 2018-11-19 | 2019-02-22 | 中国银行股份有限公司 | A kind of outsourcing human resource distribution method and device |
| CN111008069A (en) * | 2019-12-02 | 2020-04-14 | 浙江大搜车软件技术有限公司 | Service processing method, device, computer equipment and storage medium |
| CN111260253A (en) * | 2019-11-29 | 2020-06-09 | 平安银行股份有限公司 | Information sending method and device, computer equipment and storage medium |
| CN111539598A (en) * | 2020-04-03 | 2020-08-14 | 联宝(合肥)电子科技有限公司 | Test task allocation method, device and storage medium |
| CN111680914A (en) * | 2020-06-08 | 2020-09-18 | 西安京迅递供应链科技有限公司 | Event distribution method, event distribution device, storage medium, and electronic apparatus |
-
2020
- 2020-12-23 CN CN202011537205.5A patent/CN112668854A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4503499A (en) * | 1982-09-14 | 1985-03-05 | Eaton Corporation | Controlled work flow system |
| US20140278641A1 (en) * | 2013-03-15 | 2014-09-18 | Fiserv, Inc. | Systems and methods for incident queue assignment and prioritization |
| GB201310378D0 (en) * | 2013-06-11 | 2013-07-24 | Ibm | Prioritising event processing based on system workload |
| CN105426236A (en) * | 2015-11-11 | 2016-03-23 | 上海斐讯数据通信技术有限公司 | Realization method and device of high-concurrence state machine as well as system |
| CN109377187A (en) * | 2018-11-19 | 2019-02-22 | 中国银行股份有限公司 | A kind of outsourcing human resource distribution method and device |
| CN111260253A (en) * | 2019-11-29 | 2020-06-09 | 平安银行股份有限公司 | Information sending method and device, computer equipment and storage medium |
| CN111008069A (en) * | 2019-12-02 | 2020-04-14 | 浙江大搜车软件技术有限公司 | Service processing method, device, computer equipment and storage medium |
| CN111539598A (en) * | 2020-04-03 | 2020-08-14 | 联宝(合肥)电子科技有限公司 | Test task allocation method, device and storage medium |
| CN111680914A (en) * | 2020-06-08 | 2020-09-18 | 西安京迅递供应链科技有限公司 | Event distribution method, event distribution device, storage medium, and electronic apparatus |
Non-Patent Citations (1)
| Title |
|---|
| 徐洁磐主编: "数据库技术实用教程", vol. 1, 中国铁道出版社, pages: 59 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP2006524381A5 (en) | ||
| CN111815288B (en) | Intelligent community property management system | |
| CN109035441A (en) | A kind of parking lot management and statistical system based on Internet of Things | |
| CN110738479A (en) | Order management method and system based on multi-person ordering | |
| CN111667348A (en) | Order splicing method and device | |
| CN110288774A (en) | A kind of vehicle sharing method, device, server and readable storage medium storing program for executing | |
| CN111178952A (en) | System, method and medium for sales lead follow-up and processing for the automotive industry | |
| CN116453519A (en) | Voice vehicle access method, device, system and storage medium | |
| CN108416852A (en) | Parking lot management method, multi-field model management server and readable storage medium storing program for executing | |
| CN112668854A (en) | Multi-organization-based efficient event dispatching method and related device | |
| CN112001510A (en) | Information processing method and device for automobile repair | |
| CN111245864A (en) | Method and system for effectively managing customer information | |
| CN107678856B (en) | Method and device for processing incremental information in business entity | |
| CN110060503A (en) | Vehicle parking management system, method, apparatus, computer equipment and storage medium | |
| CN115640457A (en) | Information management method, apparatus, device, medium, and program product | |
| CN110223017B (en) | Part logistics management system, method, electronic device and storage medium | |
| CN111292061A (en) | Method and device for managing resources in active triggering mode | |
| CN112132425A (en) | Performance distribution processing method, device, medium and terminal equipment | |
| CN111915039A (en) | Station reservation method and device, computer equipment and storage medium | |
| CN111429222A (en) | Article management method, system and storage medium | |
| CN111193620A (en) | Mobile work order processing method and system based on call center | |
| CN111026962A (en) | Hierarchical relation query response time reduction method, server and user front end | |
| CN111598466A (en) | Method and system for cloud management and configuration of instrument resources | |
| CN107609740B (en) | Method and device for distributing and managing mobile equipment based on internal application | |
| CN113792051B (en) | Data processing method, system, equipment and storage medium based on multi-mode lock |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |