CN108768953B - Control method, server and storage medium for scheduling process - Google Patents

Control method, server and storage medium for scheduling process Download PDF

Info

Publication number
CN108768953B
CN108768953B CN201810415634.1A CN201810415634A CN108768953B CN 108768953 B CN108768953 B CN 108768953B CN 201810415634 A CN201810415634 A CN 201810415634A CN 108768953 B CN108768953 B CN 108768953B
Authority
CN
China
Prior art keywords
scheduling
plan
target
scheduling information
information
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.)
Active
Application number
CN201810415634.1A
Other languages
Chinese (zh)
Other versions
CN108768953A (en
Inventor
夏科锋
刘建武
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Jagon Intelligent Technology Co ltd
Original Assignee
Shenzhen Jagon Intelligent Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Jagon Intelligent Technology Co ltd filed Critical Shenzhen Jagon Intelligent Technology Co ltd
Priority to CN201810415634.1A priority Critical patent/CN108768953B/en
Publication of CN108768953A publication Critical patent/CN108768953A/en
Application granted granted Critical
Publication of CN108768953B publication Critical patent/CN108768953B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63Routing a service request depending on the request content or context
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention discloses a control method, a server and a storage medium for a scheduling process, wherein the method comprises the following steps: receiving at least one piece of initial scheduling information input by a first user through a creation terminal; creating a scheduling plan according to each piece of initial scheduling information to obtain an unviewed plan list; sending an un-audited plan list to an audit terminal, and partially displaying initial scheduling information corresponding to each scheduling plan; acquiring a first scheduling plan selected by a second user through an audit terminal, and acquiring first scheduling information corresponding to the first scheduling plan; receiving second scheduling information input by a second user through the auditing terminal; judging whether the first scheduling information is consistent with the second scheduling information; and when the first scheduling information is consistent with the second scheduling information, sending prompt information that the first scheduling plan is approved to an auditing terminal. The invention audits whether the scheduling plan passes through by auditing the scheduling information input by different terminals, so as to avoid the error of the scheduling plan and improve the auditing efficiency.

Description

Control method, server and storage medium for scheduling process
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a method for controlling a scheduling process, a server, and a storage medium.
Background
At present, a railway is taken as a main domestic traffic main road, which plays an important role in the daily life process, and in order to ensure that the railway can work normally, the railway needs to be maintained regularly, so that accidents caused by running of the train on the railway are avoided, and therefore, a plurality of operation points are arranged on the railway. When the operation scheduling is carried out on the railway operation point, the operation time limit of the operation point is very strict, trains are likely to pass on the track in the non-operation period, and safety accidents are likely to happen when workers enter the operation point to carry out operation in the non-operation period.
Disclosure of Invention
The invention provides a control method, a server and a storage medium for a scheduling process, which aim to solve the problem of high error probability caused by manually realizing the control of the scheduling process by the conventional railway operation point.
In order to solve the above problems, the present invention provides a method for controlling a scheduling process, which is characterized in that the method is applied to a control system of the scheduling process, wherein the control system of the scheduling process comprises a server, a creation terminal and an audit terminal; the method comprises the following steps:
receiving at least one piece of initial scheduling information input by a first user through a creation terminal;
creating a scheduling plan according to each piece of initial scheduling information to obtain an unviewed plan list;
sending an un-audited plan list to an audit terminal, and partially displaying initial scheduling information corresponding to each scheduling plan;
acquiring a first scheduling plan selected by a second user through an audit terminal, and acquiring first scheduling information corresponding to the first scheduling plan;
receiving second scheduling information input by a second user through the auditing terminal;
judging whether the first scheduling information is consistent with the second scheduling information;
and when the first scheduling information is consistent with the second scheduling information, sending prompt information that the first scheduling plan is approved to an auditing terminal.
As a further improvement of the present invention, before the step of receiving at least one initial scheduling information input by the first user through the creation terminal, the method further includes:
receiving a first login request sent by a first user through a creation terminal, wherein the first login request comprises a first user account;
the method comprises the steps that a first user account is matched with a plurality of preset user accounts in a server to obtain a first target preset account matched with the first user account, and each preset user account corresponds to one authority type;
and associating the first user account with a target authority corresponding to the first target preset account.
As a further improvement of the present invention, before the step of receiving the second scheduling information input by the second user through the audit terminal, the method further includes:
receiving a second login request sent by a second user through an auditing terminal, wherein the second login request comprises a second user account;
the second user account is matched with a plurality of preset user accounts in the server to obtain a second target preset account matched with the second user account, and each preset user account corresponds to one authority type;
and associating the second user account with the target permission corresponding to the second target preset account.
As a further improvement of the present invention, the first scheduling information includes a first scheduling time and a first scheduling command number, and the second scheduling information includes a second scheduling time and a second scheduling command number; the step of judging whether the first scheduling information is consistent with the second scheduling information comprises the following steps:
judging whether the first scheduling time is matched with the second scheduling time and whether the first scheduling command number is matched with the second scheduling command number;
if the first scheduling time is matched with the second scheduling time and the first scheduling command number is matched with the second scheduling command number, the first scheduling information is confirmed to be consistent with the second scheduling information;
and if the first scheduling time is not matched with the second scheduling time or the first scheduling command number is not matched with the second scheduling command number, confirming that the first scheduling information is inconsistent with the second scheduling information.
As a further improvement of the present invention, after the step of determining whether the first scheduling information and the second scheduling information are consistent, the method further includes:
and when the first scheduling information is inconsistent with the second scheduling information, sending warning information that the first scheduling plan cannot be audited to the auditing terminal.
As a further improvement of the present invention, after the step of sending the prompt information that the first scheduling plan is approved to the auditing terminal, the method further includes:
and locking the first dispatching plan, and adding the first dispatching plan to a preset executable plan list.
As a further improvement of the invention, each scheduling plan corresponds to a scheduling interval, each scheduling interval comprises at least one electronic lock, and each electronic lock corresponds to a lock identification code; after the step of adding the first dispatch plan to the preset executable plan list, the method further comprises the following steps:
receiving a task application sent by a third user through an execution terminal, wherein the task application comprises at least one target electronic lock, and each target electronic lock corresponds to one task information;
acquiring a target lock identification code corresponding to each target electronic lock, confirming a target scheduling interval corresponding to each target electronic lock according to the target lock identification code, confirming a target scheduling plan corresponding to each target electronic lock according to the target scheduling interval, and confirming target scheduling information corresponding to each target electronic lock according to the target scheduling plan so as to acquire at least one piece of target scheduling information;
judging whether the task information corresponding to each target electronic lock is correct or not according to the target scheduling information corresponding to each target electronic lock;
if the task information is correct, sending prompt information that the task application is approved to the execution terminal;
and if the task information is incorrect, sending prompt information that the task application is not approved to the execution terminal.
As a further improvement of the present invention, before the step of receiving the task application sent by the execution terminal, the method further includes:
receiving a third login request sent by a third user through an execution terminal, wherein the third login request comprises a third user account;
matching the third user account with a plurality of preset user accounts in the server to obtain a third target preset account matched with the third user account, wherein each preset user account corresponds to one authority type;
and associating the third user account with the target permission corresponding to the third target preset account.
In order to solve the above problem, the present invention further provides a server, which includes a memory and a processor, wherein the processor is coupled to the memory, and the memory stores a computer program that can be executed on the processor;
the processor, when executing the computer program, implements the steps of any of the above-described methods of controlling a scheduling process.
In order to solve the above problem, the present invention further provides a storage medium having a computer program stored thereon, where the computer program is executed by a processor to implement the steps in any one of the control methods for scheduling processes.
Compared with the prior art, the scheduling plan is created according to the initial scheduling information input by the first user creation terminal, whether the scheduling plan passes the audit according to the first scheduling information input by the audit terminal of the second client, and when the audit result shows that the scheduling plan passes the audit, the scheduling plan audit passing message is sent to the audit terminal, so that the possibility of error of the created scheduling plan is effectively reduced, the probability of error in the scheduling process is reduced, the occurrence probability of accidents is further reduced, and meanwhile, the efficiency of auditing the scheduling plan is further improved through the separate creation and audit processes.
Drawings
FIG. 1 is a block diagram of a process control system according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a first exemplary embodiment of a method for controlling a scheduling process according to the present invention;
FIG. 3 is a flowchart illustrating a second embodiment of a method for controlling a scheduling process according to the present invention;
FIG. 4 is a flowchart illustrating a control method for scheduling process according to a third embodiment of the present invention;
FIG. 5 is a flowchart illustrating a control method for scheduling process according to a fourth embodiment of the present invention;
FIG. 6 is a flowchart illustrating a fifth exemplary embodiment of a method for controlling a scheduling process according to the present invention;
FIG. 7 is a flowchart illustrating a sixth embodiment of a method for controlling a scheduling process according to the present invention;
FIG. 8 is a flowchart illustrating a seventh exemplary embodiment of a method for controlling a scheduling process according to the present invention;
FIG. 9 is a flowchart illustrating a control method for scheduling process according to an eighth embodiment of the present invention;
FIG. 10 is a functional block diagram of a first embodiment of a server according to the present invention;
FIG. 11 is a functional block diagram of a server according to a second embodiment of the present invention;
FIG. 12 is a functional block diagram of a server according to a third embodiment of the present invention;
FIG. 13 is a functional block diagram of a server according to a fourth embodiment of the present invention;
FIG. 14 is a functional block diagram of a server according to a fifth embodiment of the present invention;
FIG. 15 is a functional block diagram of a server according to a sixth embodiment of the present invention;
FIG. 16 is a functional block diagram of a seventh embodiment of the server of the present invention;
FIG. 17 is a functional block diagram of an eighth embodiment of a server according to the present invention;
fig. 18 is a schematic diagram of a framework of an embodiment of the server of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
FIG. 1 is an embodiment of a process control system for scheduling in accordance with the present invention. In this embodiment, the scheduling process control system includes a server 1, a creation terminal 2, an audit terminal 3, and an execution terminal 4, where the server 1 is respectively in communication connection with the creation terminal 2, the audit terminal 3, and the execution terminal 4, and the creation terminal 2, the audit terminal 3, and the execution terminal 4 respectively correspond to different users, where the creation terminal 2 is configured to input initial scheduling information to the server 1, and the server 1 creates a scheduling plan according to the initial scheduling information after receiving the initial scheduling information, so as to obtain an unchecked plan list, and sends the unchecked plan list to the audit terminal 2. The auditing terminal 2 is used for outputting and displaying an unchecked plan list so that a second user can select a first scheduling plan through the auditing terminal 2, each scheduling plan in the unchecked plan list displays part of scheduling information corresponding to the scheduling plan, and the second user inputs second scheduling information into the auditing terminal 2 according to the part of displayed scheduling information; the server 1 obtains first scheduling information corresponding to a first scheduling plan after receiving the first scheduling plan selected by a second user through the auditing terminal 2, and confirms whether the first scheduling plan is approved or not by judging whether the first scheduling information is consistent with the second scheduling information or not. The execution terminal 4 is used for a third user to send a task application to the server 1, the task application comprises a target electronic lock and task information, after receiving the task application, the server 1 obtains a target scheduling interval corresponding to the target electronic lock to confirm a target scheduling plan and obtain target scheduling information of the target scheduling plan, and whether the task application passes the audit is judged by comparing the target scheduling information with the task information.
Fig. 2 is a flowchart illustrating a control method of a scheduling process according to a first embodiment of the present invention. In this embodiment, the control method of the scheduling process is applied to a server. Specifically, the control method of the scheduling process includes the following steps:
at step S1, at least one initial scheduling information input by the first user through the creation terminal is received.
Specifically, the server receives initial scheduling information input by the first user through the creation terminal, and the server may simultaneously receive a plurality of initial scheduling information input by the first user creation terminal.
In step S2, a scheduling plan is created according to each piece of initial scheduling information to obtain an unchecked plan list.
In particular, the list of unaudited plans includes at least one dispatch plan.
And step S3, sending the list of the non-audit plans to the audit terminal, and partially displaying the initial scheduling information corresponding to each scheduling plan.
It should be noted that the initial scheduling information includes scheduling time, scheduling interval, and scheduling command number information, after the non-audit plan list is sent to the audit terminal, each scheduling plan only displays a part of the initial scheduling information, and after the second user obtains the scheduling information displayed in the part through the audit terminal, the second user can input other scheduling information not displayed through the audit terminal according to the scheduling information displayed in the part. Preferably, the scheduling information displayed in the part is a scheduling interval.
Step S4, a first scheduling plan selected by the second user through the audit terminal is obtained, and first scheduling information corresponding to the first scheduling plan is obtained.
Specifically, a first scheduling plan in an unchecked plan list selected by a second user through a check terminal is obtained, and first scheduling information corresponding to the first scheduling plan is obtained.
And step S5, receiving second scheduling information input by the second user through the audit terminal.
Specifically, after the second user selects the first scheduling plan, the scheduling information portion of the first scheduling plan is displayed, for example, only the scheduling interval of the first scheduling plan is displayed, and the scheduling time, the scheduling command number, and the like are not displayed, after the second user reconfirms the scheduling interval, the second user can input the second scheduling information, that is, the other scheduling information except the scheduling interval, through the auditing terminal according to the scheduling interval.
In step S6, it is determined whether the first scheduling information and the second scheduling information match. When the first schedule information coincides with the second schedule information, step S7 is performed.
Specifically, the first scheduling information and the second scheduling information are compared to determine whether they are consistent, and when the first scheduling information and the second scheduling information are consistent, step S7 is executed.
And step S7, sending the prompt information that the first scheduling plan passes the audit to the audit terminal.
Specifically, after the first scheduling information and the second scheduling information are confirmed to be consistent, prompt information that the first scheduling plan is approved is sent to the auditing terminal, so that the second user is prompted that the first scheduling plan is approved.
According to the method and the device, the scheduling plan is created according to the initial scheduling information input by the first user creation terminal, the second client is used for auditing whether the scheduling plan passes or not according to the first scheduling information input by the auditing terminal, and when the auditing result is that the scheduling plan passes, a message that the scheduling plan is approved is sent to the auditing terminal, so that the possibility of error of the created scheduling plan is effectively reduced, the probability of error in the scheduling process is reduced, the occurrence probability of accidents is further reduced, and meanwhile, the efficiency of auditing the scheduling plan is further improved through the separate creation and auditing processes.
Fig. 3 is a flowchart illustrating a control method for scheduling process according to a second embodiment of the present invention. Referring to fig. 3, the method for controlling the scheduling process includes the following steps:
in step S10, a first login request sent by a first user through a creation terminal is received.
It should be noted that the first login request includes a first user account.
Specifically, before a first user inputs initial scheduling information to a server through a creation terminal, a first login request is sent to the server through the creation terminal.
In step S11, the first user account is matched with a plurality of preset user accounts in the server, so as to obtain a first target preset account matched with the first user account.
It should be noted that a plurality of preset user accounts are stored in the server, each preset user account corresponds to one permission type and different permission types, and the permissions exercised by the preset user accounts are different from each other, for example, the permission types may include a scheduling plan permission creation permission and a scheduling plan permission review permission.
Specifically, a first user account is matched with a plurality of preset user accounts in a server to determine that the first user account corresponds to a first permission, where the first permission is a permission for creating a scheduling plan in this embodiment.
Step S12, associate the first user account with a target permission corresponding to the first target preset account.
Specifically, a target authority corresponding to a first target preset account is given to the first user account.
At step S13, at least one initial scheduling information input by the first user through the creation terminal is received.
The step is similar to step S1, and reference may be made to the description of step S1, which is not repeated here.
In step S14, a scheduling plan is created according to each piece of initial scheduling information to obtain an unchecked plan list.
The step is similar to step S2, and reference may be made to the description of step S2, which is not repeated here.
And step S15, sending the list of the non-audit plans to the audit terminal, and partially displaying the initial scheduling information corresponding to each scheduling plan.
The step is similar to step S3, and reference may be made to the description of step S3, which is not repeated here.
Step S16, a first scheduling plan selected by the second user through the audit terminal is obtained, and first scheduling information corresponding to the first scheduling plan is obtained.
The step is similar to step S4, and reference may be made to the description of step S4, which is not repeated here.
And step S17, receiving second scheduling information input by the second user through the audit terminal.
The step is similar to step S5, and reference may be made to the description of step S5, which is not repeated here.
In step S18, it is determined whether the first scheduling information and the second scheduling information match. When the first schedule information coincides with the second schedule information, step S19 is performed.
The step is similar to step S6, and reference may be made to the description of step S6, which is not repeated here.
And step S19, sending the prompt information that the first scheduling plan passes the audit to the audit terminal.
The step is similar to step S7, and reference may be made to the description of step S7, which is not repeated here.
In the embodiment, the authority type of the first user account sending the login request at the creation terminal can be confirmed through the login request sent by the creation terminal, and then how to process the data information input by the first user account is judged according to the authority type, wherein the authority type of the first user account is the authority of creating the scheduling plan, and then the server creates the scheduling plan according to the initial scheduling information input by the first user through the creation terminal, so that the functions of automatically identifying the user account type and automatically performing corresponding data processing according to the account type are realized.
Fig. 4 is a flowchart illustrating a control method for scheduling process according to a third embodiment of the present invention. Referring to fig. 4, the method for controlling the scheduling process includes the following steps:
at step S20, at least one initial scheduling information input by the first user through the creation terminal is received.
The step is similar to step S1, and reference may be made to the description of step S1, which is not repeated here.
In step S21, a scheduling plan is created according to each piece of initial scheduling information to obtain an unchecked plan list.
The step is similar to step S2, and reference may be made to the description of step S2, which is not repeated here.
Step S22, a second login request sent by the second user through the audit terminal is received.
It should be noted that the second login request includes a second user account.
Specifically, before the second user inputs the second scheduling information and the target command number to the server through the auditing terminal, the second login request is sent to the server through the auditing terminal.
In step S23, the second user account is matched with a plurality of preset user accounts in the server, so as to obtain a second target preset account matched with the second user account.
It should be noted that each preset user account corresponds to one permission type.
Specifically, a second permission of the second user account is confirmed according to the matching condition of the second user account and a plurality of preset user accounts in the server, and the second permission is a permission for checking the scheduling plan.
And step S24, associating the second user account with a target authority corresponding to the second target preset account.
Specifically, a target authority corresponding to a second target preset account is given to the second user account.
And step S25, sending the list of the non-audit plans to the audit terminal, and partially displaying the initial scheduling information corresponding to each scheduling plan.
The step is similar to step S3, and reference may be made to the description of step S3, which is not repeated here.
Step S26, a first scheduling plan selected by the second user through the audit terminal is obtained, and first scheduling information corresponding to the first scheduling plan is obtained.
The step is similar to step S4, and reference may be made to the description of step S4, which is not repeated here.
And step S27, receiving second scheduling information input by the second user through the audit terminal.
The step is similar to step S5, and reference may be made to the description of step S5, which is not repeated here.
In step S28, it is determined whether the first scheduling information and the second scheduling information match. When the first schedule information coincides with the second schedule information, step S29 is performed.
The step is similar to step S6, and reference may be made to the description of step S6, which is not repeated here.
And step S29, sending the prompt information that the first scheduling plan passes the audit to the audit terminal.
The step is similar to step S7, and reference may be made to the description of step S7, which is not repeated here.
In this embodiment, the authority type of the second user account sending the login request at the audit terminal can be confirmed through the login request sent by the audit terminal, and then how to process the data information input by the second user account is judged according to the authority type, where the authority type corresponding to the second user account is the authority of auditing the scheduling plan, and then the server audits the scheduling plan according to the second scheduling information input by the second user through the audit terminal.
Fig. 5 is a flowchart illustrating a control method of a scheduling process according to a fourth embodiment of the present invention. Referring to fig. 5, the method for controlling the scheduling process includes the following steps:
at step S30, at least one initial scheduling information input by the first user through the creation terminal is received.
The step is similar to step S1, and reference may be made to the description of step S1, which is not repeated here.
In step S31, a scheduling plan is created according to each piece of initial scheduling information to obtain an unchecked plan list.
The step is similar to step S2, and reference may be made to the description of step S2, which is not repeated here.
And step S32, sending the list of the non-audit plans to the audit terminal, and partially displaying the initial scheduling information corresponding to each scheduling plan.
It should be noted that the scheduling information displayed in this part is a scheduling interval for the second user to confirm the scheduling plan.
The step is similar to step S3, and reference may be made to the description of step S3, which is not repeated here.
Step S33, a first scheduling plan selected by the second user through the audit terminal is obtained, and first scheduling information corresponding to the first scheduling plan is obtained.
It should be noted that the first scheduling information includes a first scheduling time and a first scheduling command number, and the scheduling interval information in the initial scheduling information is the displayed scheduling information, so that after the first scheduling plan selected by the second user through the audit terminal is obtained, only the first scheduling time and the first scheduling command number corresponding to the first scheduling plan need to be obtained again.
The step is similar to step S4, and reference may be made to the description of step S4, which is not repeated here.
And step S34, receiving second scheduling information input by the second user through the audit terminal.
The step is similar to step S5, and reference may be made to the description of step S5, which is not repeated here.
Step S35, it is determined whether the first scheduling time matches the second scheduling time and the first scheduling command number matches the second scheduling command number. If the first scheduling time matches the second scheduling time and the first scheduling command number matches the second scheduling command number, go to step S36; if the first scheduling time does not match the second scheduling time or the first scheduling command number does not match the second scheduling command number, step S38 is executed.
It should be noted that the second scheduling information includes a second scheduling time and a second scheduling command number, and the scheduling interval information is already displayed and does not need to be input again. Step S36 is performed if and only if the first scheduled time matches the second scheduled time and the first scheduled command number matches the second scheduled command number.
Step S36 confirms that the first scheduling information matches the second scheduling information.
And step S37, sending the prompt information that the first scheduling plan passes the audit to the audit terminal.
The step is similar to step S7, and reference may be made to the description of step S7, which is not repeated here.
In step S38, it is confirmed that the first scheduling information does not match the second scheduling information.
In this embodiment, whether the scheduling information corresponding to the first scheduling plan is correct is determined according to the second scheduling time and the second scheduling command number input by the second user through the auditing terminal, so that the auditing process for the first scheduling plan is completed.
Fig. 6 is a flowchart illustrating a fifth embodiment of a method for controlling a scheduling process according to the present invention. Referring to fig. 6, the method for controlling the scheduling process includes the following steps:
at step S40, at least one initial scheduling information input by the first user through the creation terminal is received.
The step is similar to step S1, and reference may be made to the description of step S1, which is not repeated here.
In step S41, a scheduling plan is created according to each piece of initial scheduling information to obtain an unchecked plan list.
The step is similar to step S2, and reference may be made to the description of step S2, which is not repeated here.
And step S42, sending the list of the non-audit plans to the audit terminal, and partially displaying the initial scheduling information corresponding to each scheduling plan.
The step is similar to step S3, and reference may be made to the description of step S3, which is not repeated here.
Step S43, a first scheduling plan selected by the second user through the audit terminal is obtained, and first scheduling information corresponding to the first scheduling plan is obtained.
The step is similar to step S4, and reference may be made to the description of step S4, which is not repeated here.
And step S44, receiving second scheduling information input by the second user through the audit terminal.
The step is similar to step S5, and reference may be made to the description of step S5, which is not repeated here.
In step S45, it is determined whether the first scheduling information and the second scheduling information match. When the first schedule information coincides with the second schedule information, step S46 is performed. When the first schedule information does not coincide with the second schedule information, step S47 is performed.
The step is similar to step S6, and reference may be made to the description of step S6, which is not repeated here.
And step S46, sending the prompt information that the first scheduling plan passes the audit to the audit terminal.
The step is similar to step S7, and reference may be made to the description of step S7, which is not repeated here.
And step S47, sending warning information that the first dispatch plan fails to be audited to the audit terminal.
Specifically, when the first scheduling information is inconsistent with the second scheduling information, it is indicated that the first user has a problem through creating initial scheduling information input by the terminal or the second scheduling information input by the second user through the auditing terminal, and the second user is reminded to re-audit the first scheduling plan by sending warning information that the auditing is not passed to the auditing terminal.
Further, when the first scheduling plan is not checked for a plurality of times, for example, 3 times, a reminding message for communication confirmation with the user who created the scheduling plan is sent to the checking terminal.
In the embodiment, when the first scheduling information is determined to be consistent with the second scheduling information, the warning information that the first scheduling plan cannot be audited is sent to the auditing terminal, so that a second user of the auditing terminal is reminded to audit the first scheduling plan again, and the probability of errors of the scheduling plan is reduced.
Fig. 7 is a flowchart illustrating a control method for scheduling process according to a sixth embodiment of the present invention. Referring to fig. 7, the method for controlling the scheduling process includes the following steps:
at step S50, at least one initial scheduling information input by the first user through the creation terminal is received.
The step is similar to step S1, and reference may be made to the description of step S1, which is not repeated here.
In step S51, a scheduling plan is created according to each piece of initial scheduling information to obtain an unchecked plan list.
The step is similar to step S2, and reference may be made to the description of step S2, which is not repeated here.
And step S52, sending the list of the non-audit plans to the audit terminal, and partially displaying the initial scheduling information corresponding to each scheduling plan.
The step is similar to step S3, and reference may be made to the description of step S3, which is not repeated here.
Step S53, a first scheduling plan selected by the second user through the audit terminal is obtained, and first scheduling information corresponding to the first scheduling plan is obtained.
The step is similar to step S4, and reference may be made to the description of step S4, which is not repeated here.
And step S54, receiving second scheduling information input by the second user through the audit terminal.
The step is similar to step S5, and reference may be made to the description of step S5, which is not repeated here.
In step S55, it is determined whether the first scheduling information and the second scheduling information match. When the first schedule information coincides with the second schedule information, step S56 is performed.
The step is similar to step S6, and reference may be made to the description of step S6, which is not repeated here.
And step S56, sending the prompt information that the first scheduling plan passes the audit to the audit terminal.
The step is similar to step S7, and reference may be made to the description of step S7, which is not repeated here.
Step S57, locking the first dispatch plan, and adding the first dispatch plan to the list of the preset executable plans.
It should be noted that, all the scheduling plans allowed to be executed are listed in the preset executable plan list, and through the list, the user can quickly query the scheduling plan and the scheduling information thereof currently required to be executed.
Specifically, after the first dispatch plan is approved, the first dispatch plan is locked so that the first dispatch plan cannot be modified, and the first dispatch plan is added to a preset executable plan list.
According to the embodiment, the first dispatching plan is locked, so that the first dispatching plan cannot be modified after being audited, and the risk that the first dispatching plan is tampered is reduced.
Fig. 8 is a flowchart illustrating a seventh embodiment of the method for controlling a scheduling process according to the present invention. Referring to fig. 8, the method for controlling the scheduling process includes the following steps:
step S600, at least one initial scheduling information input by the first user through the creation terminal is received.
The step is similar to step S1, and reference may be made to the description of step S1, which is not repeated here.
Step S601, creating a scheduling plan according to each piece of initial scheduling information to obtain an unchecked plan list.
The step is similar to step S2, and reference may be made to the description of step S2, which is not repeated here.
Step S602, sending the list of the non-audit plans to the audit terminal, and partially displaying the initial scheduling information corresponding to each scheduling plan.
The step is similar to step S3, and reference may be made to the description of step S3, which is not repeated here.
Step S603, a first scheduling plan selected by the second user through the audit terminal is obtained, and first scheduling information corresponding to the first scheduling plan is obtained.
The step is similar to step S4, and reference may be made to the description of step S4, which is not repeated here.
Step S604, receiving second scheduling information input by the second user through the audit terminal.
The step is similar to step S5, and reference may be made to the description of step S5, which is not repeated here.
Step S605 determines whether the first scheduling information and the second scheduling information are consistent. When the first scheduling information coincides with the second scheduling information, step S506 is performed.
The step is similar to step S6, and reference may be made to the description of step S6, which is not repeated here.
And step S606, sending the prompt information that the first scheduling plan is approved to the auditing terminal.
The step is similar to step S7, and reference may be made to the description of step S7, which is not repeated here.
Step S607, locking the first dispatch plan, and adding the first dispatch plan to the preset executable plan list.
The step is similar to step S57, and reference may be made to the description of step S57, which is not repeated here.
Step S608, a task application sent by the third user through the execution terminal is received.
It should be noted that the task application includes at least one target electronic lock, and each target electronic lock corresponds to one task information.
Step S609, a target lock identification code corresponding to each target electronic lock is obtained, a target scheduling interval corresponding to each target electronic lock is confirmed according to the target lock identification code, a target scheduling plan corresponding to each target electronic lock is confirmed according to the target scheduling interval, and target scheduling information corresponding to each target electronic lock is confirmed according to the target scheduling plan so as to obtain at least one piece of target scheduling information.
It should be noted that, in this embodiment, each scheduling plan corresponds to one scheduling interval, each scheduling interval includes at least one electronic lock, each electronic lock corresponds to one lock identification code, the lock identification code is generated when the electronic lock is recorded in the server, and the electronic lock and the lock identification code correspond to each other one by one.
Specifically, as illustrated by an electronic lock, after acquiring a target lock identification code of the target electronic lock, the server may determine a scheduling interval, i.e., a target scheduling interval, where the target electronic lock is located through the target lock identification code, then determine a target scheduling plan corresponding to the scheduling interval according to the target scheduling interval, where each scheduling interval corresponds to at least one scheduling plan, and after determining the target scheduling plan, acquire target scheduling information corresponding to each target scheduling plan.
Step S610, determining whether the task information corresponding to each target electronic lock is correct according to the target scheduling information corresponding to each target electronic lock. If the task information is correct, execute step S611; if the task information is not correct, step S612 is executed.
Specifically, a target electronic lock is taken as an example, after target scheduling information is obtained, task information corresponding to the target electronic lock is compared and judged with the target scheduling information corresponding to the target electronic lock, and when a plurality of target scheduling information exist, only the task information meets the requirement of one of the target scheduling information, that is, the task information corresponding to the target electronic lock is considered to be approved. Checking whether the task information corresponding to each target electronic lock is correct or not in sequence according to the mode, and executing the step S611 only when the task information corresponding to each target electronic lock is correct; otherwise, step S612 is performed.
Step S611, sending a prompt message that the task application is approved to the execution terminal.
Specifically, when the task information is correct, prompt information that the task application is approved is sent to the execution terminal, so that a third user is reminded to allow the task to be executed.
And step S612, sending prompt information that the task application audit is not passed to the execution terminal.
Specifically, when the task information is incorrect, prompt information that the task application audit is failed is sent to the execution terminal, so that a third user is reminded that the task is not allowed to be executed, and the task application is required to be resubmitted.
In the embodiment, whether the task application meets the requirement of one scheduling plan in a preset executable plan list is confirmed by auditing the task information of the task application input by a third user through the execution terminal, and the task is allowed to be executed only when the audit is passed, so that the accuracy of task execution in the whole scheduling process is further ensured, the condition that the task is inconsistent with the scheduling plan is avoided, manual audit is not needed, and the task auditing efficiency is improved.
Fig. 9 is a flowchart illustrating a control method for scheduling process according to an eighth embodiment of the present invention. Referring to fig. 9, the method for controlling the scheduling process includes the steps of:
step S700, at least one initial scheduling information input by the first user through the creation terminal is received.
The step is similar to step S1, and reference may be made to the description of step S1, which is not repeated here.
Step S701, creating a scheduling plan according to each piece of initial scheduling information to obtain an unchecked plan list.
The step is similar to step S2, and reference may be made to the description of step S2, which is not repeated here.
Step S702, sending the list of the non-audit plans to the audit terminal, and partially displaying the initial scheduling information corresponding to each scheduling plan.
The step is similar to step S3, and reference may be made to the description of step S3, which is not repeated here.
Step S703 is to obtain a first scheduling plan selected by the second user through the audit terminal, and obtain first scheduling information corresponding to the first scheduling plan.
The step is similar to step S4, and reference may be made to the description of step S4, which is not repeated here.
Step S704, receiving second scheduling information input by the second user through the audit terminal.
The step is similar to step S5, and reference may be made to the description of step S5, which is not repeated here.
Step S705, determining whether the first scheduling information and the second scheduling information are consistent. When the first scheduling information coincides with the second scheduling information, step S706 is performed.
The step is similar to step S6, and reference may be made to the description of step S6, which is not repeated here.
Step S706, sending the prompt information that the first scheduling plan is approved to the auditing terminal.
The step is similar to step S7, and reference may be made to the description of step S7, which is not repeated here.
Step S707, lock the first dispatch plan, and add the first dispatch plan to a preset executable plan list.
The step is similar to step S56, and reference may be made to the description of step S56, which is not repeated here.
In step S708, a third login request sent by the third user through the execution terminal is received.
It should be noted that the third login request includes a third user account.
Specifically, a third login request is sent to the server before a third user applies for a task by executing the terminal input to the server.
In step S709, the third user account is matched with a plurality of preset user accounts in the server to obtain a third target preset account matched with the third user account, where each preset user account corresponds to one permission type.
It should be noted that a plurality of preset user accounts are stored in the server, each preset user account corresponds to one permission type and different permission types, and the authorities exercised by the preset user accounts are different.
Specifically, the third user account is matched with a plurality of preset user accounts in the server to confirm that the third user account corresponds to a third permission, and in this embodiment, the third permission is a task application permission.
Step S710, associating the third user account with a target permission corresponding to a third target preset account.
Specifically, a target authority corresponding to a third target preset account is given to the third user account.
Step S711 receives a task application sent by the third user through the execution terminal.
The step is similar to the step S608, and the description of the step S608 may be specifically referred to, and is not repeated herein.
Step S712, obtaining a target lock identification code corresponding to each target electronic lock, determining a target dispatching interval corresponding to each target electronic lock according to the target lock identification code, determining a target dispatching plan corresponding to each target electronic lock according to the target dispatching interval, and determining target dispatching information corresponding to each target electronic lock according to the target dispatching plan to obtain at least one target dispatching information.
The step is similar to step S609, and reference may be specifically made to the description of step S609, which is not described herein again.
Step S713, determining whether the task information corresponding to each target electronic lock is correct according to the target scheduling information corresponding to each target electronic lock. If the task information is correct, go to step S714; if the task information is not correct, step S715 is performed.
The step is similar to step S610, and reference may be specifically made to the description of step S610, which is not described herein again.
And step S714, sending the prompt information that the task application is approved to the execution terminal.
The step is similar to step S611, and reference may be specifically made to the description of step S611, which is not described herein again.
And step S715, sending prompt information that the task application audit is not passed to the execution terminal.
The step is similar to step S612, and reference may be specifically made to the description of step S612, which is not described herein again.
In the embodiment, the authority type of the third user account sending the login request at the execution terminal can be confirmed by executing the login request sent by the terminal, and then, how to process the data information input by the third user account is judged according to the authority type, the authority type of the third user account is the task application authority, and then the server verifies whether the task application input by the third user through the execution terminal meets the requirement of one scheduling plan in a preset executable plan list, so that the function of automatically identifying the user account type and automatically performing corresponding data processing according to the account type is realized.
Fig. 10 is a functional block diagram of a server according to a first embodiment of the present invention. Referring to fig. 10, the server includes a first receiving module 10, a creating module 11, a sending module 12, a first obtaining module 13, a second receiving module 14, a first determining module 15, and a first prompting module 16.
The first receiving module 10 is configured to receive at least one piece of initial scheduling information input by a first user through a creation terminal; a creating module 11, configured to create a scheduling plan according to each piece of initial scheduling information, so as to obtain an unchecked plan list; a sending module 12, configured to send an unchecked plan list to a checking terminal, and partially display initial scheduling information corresponding to each scheduling plan; the first obtaining module 13 is configured to obtain a first scheduling plan selected by a second user through an audit terminal, and obtain first scheduling information corresponding to the first scheduling plan; the second receiving module 14 is configured to receive second scheduling information input by the second user through the audit terminal; a first judging module 15, configured to judge whether the first scheduling information is consistent with the second scheduling information; and the first prompting module 16 is configured to send a prompting message that the first scheduling plan is approved to the auditing terminal when the first scheduling information is consistent with the second scheduling information.
Fig. 11 is a functional block diagram of a server according to a second embodiment of the present invention. Referring to fig. 11, the server further includes a third receiving module 20, a first matching module 21, and a first associating module 22.
The third receiving module 20 is configured to receive a first login request sent by a first user through a creation terminal, where the first login request includes a first user account; the first matching module 21 is configured to match the first user account with a plurality of preset user accounts in the server, so as to obtain a first target preset account matched with the first user account, where each preset user account corresponds to one permission type; the first association module 22 is configured to associate the first user account with a target permission corresponding to the first target preset account.
Fig. 12 is a functional block diagram of a server according to a third embodiment of the present invention. Referring to fig. 12, the server further includes a fourth receiving module 30, a second matching module 31, and a second associating module 32.
The fourth receiving module 30 is configured to receive a second login request sent by a second user through an audit terminal, where the second login request includes a second user account; the second matching module 31 is configured to match the second user account with a plurality of preset user accounts in the server, so as to obtain a second target preset account matched with the second user account, where each preset user account corresponds to one permission type; and the second association module 32 is configured to associate the second user account with a target permission corresponding to the second target preset account.
Fig. 13 is a functional block diagram of a server according to a fourth embodiment of the present invention. Referring to fig. 13, the first determining module 15 includes a determining unit 150, a first confirming unit 151, and a second confirming unit 152.
The determining unit 150 is configured to determine whether the first scheduling time matches the second scheduling time and whether the first scheduling command number matches the second scheduling command number; a first confirming unit 151, configured to confirm that the first scheduling information is consistent with the second scheduling information if the first scheduling time matches with the second scheduling time and the first scheduling command number matches with the second scheduling command number; a second confirming unit 152, configured to confirm that the first scheduling information is inconsistent with the second scheduling information if the first scheduling time does not match with the second scheduling time or the first scheduling command number does not match with the second scheduling command number.
Fig. 14 is a functional block diagram of a server according to a fifth embodiment of the present invention. Referring to fig. 14, the server further includes a second prompt module 40.
The second prompting module 40 is configured to, by the second prompting module 40, send warning information that the first scheduling plan fails to be audited to the auditing terminal when the first scheduling information is inconsistent with the second scheduling information.
Fig. 15 is a functional block diagram of a server according to a sixth embodiment of the present invention. Referring to fig. 15, the server further includes a locking module 50.
The locking module 50 is configured to lock the first dispatch plan and add the first dispatch plan to the preset executable plan list.
Fig. 16 is a functional block diagram of a seventh embodiment of the server according to the present invention. Referring to fig. 16, the server further includes a fifth receiving module 60, a second obtaining module 61, a second determining module 62, a third prompting module 63, and a fourth prompting module 64.
The fifth receiving module 60 is configured to receive a task application sent by a third user through an execution terminal, where the task application includes at least one target electronic lock, and each target electronic lock corresponds to one piece of task information; the second obtaining module 61 is configured to obtain a target lock identification code corresponding to each target electronic lock, confirm a target scheduling interval corresponding to each target electronic lock according to the target lock identification code, confirm a target scheduling plan corresponding to each target electronic lock according to the target scheduling interval, and confirm target scheduling information corresponding to each target electronic lock according to the target scheduling plan to obtain at least one piece of target scheduling information; the second judging module 62 is configured to judge whether task information corresponding to each target electronic lock is correct according to target scheduling information corresponding to each target electronic lock; the third prompting module 63 is configured to send a prompting message that the task application is approved to the execution terminal if the task information is correct; and a fourth prompt module 64, configured to send a prompt message that the task application audit is not passed to the execution terminal if the task information is incorrect.
Fig. 17 is a functional block diagram of a seventh embodiment of the server according to the present invention. Referring to fig. 17, the server further includes a sixth receiving module 70, a third matching module 71 and a third associating module 72.
The sixth receiving module 70 is configured to receive a third login request sent by a third user through the execution terminal, where the third login request includes a third user account; a third matching module 71, configured to match a third user account with multiple preset user accounts in the server, so as to obtain a third target preset account matched with the third user account, where each preset user account corresponds to one permission type; and the third association module 72 is configured to associate the third user account with a target permission corresponding to a third target preset account.
It will be apparent to those skilled in the art that, for convenience and simplicity of description, the foregoing functional units and modules are merely illustrated in terms of division, and in practical applications, the foregoing functional allocation may be performed by different functional units and modules as needed, that is, the internal structure of the server is divided into different functional units or modules to perform all or part of the above described functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the above-mentioned apparatus may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
Fig. 18 shows a schematic block diagram of a server according to another embodiment of the present invention, and referring to fig. 18, the server in this embodiment includes: one or at least two processors 80 and a memory 81, and a computer program 810 stored in the memory 81 and executable on the processor 80. The processor 80, when executing the computer program 810, implements the steps in the control method of the scheduling process described in the above embodiments, such as: step S1-step S6 shown in fig. 2. Alternatively, the processor 80, when executing the computer program 810, implements the functions of the modules/units in the server embodiment described above, such as: the functions of the modules 10-15 shown in fig. 10.
The computer program 810 may be divided into one or more modules/units, which are stored in the memory 81 and executed by the processor 80 to accomplish the present application. One or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 810 in the server.
The server includes, but is not limited to, a processor 80, a memory 81. Those skilled in the art will appreciate that fig. 18 is merely one example of a server and is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or different components, e.g., a server may also include input devices, output devices, network access devices, buses, etc.
The Processor 80 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 81 may be a read-only memory, a static storage device that may store static information and instructions, a random access memory, or a dynamic storage device that may store information and instructions, or may be an electrically erasable programmable read-only memory, a read-only optical disk, or other optical disk storage, magnetic disk storage media, or other magnetic storage devices. The memory 81 may be connected to the processor 80 via a communication bus or may be integrated with the processor 80.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed server and method may be implemented in other ways. For example, the above-described server embodiments are merely illustrative, and for example, a module or a unit may be divided into only one logical function, and may be implemented in other ways, for example, multiple 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.
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 embodiment of the present application further provides a storage medium for storing a computer program, which contains program data designed to execute the control method embodiment of the scheduling process described above. By executing the computer program stored in the storage medium, the offline unlocking method of the lockset provided by the application can be realized.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by the computer program 810, and the computer program 810 can be stored in a computer-readable storage medium, where the computer program 810 can implement the steps of the methods described above when being executed by the processor 80. The computer program 810 comprises, inter alia, computer program code, which may be in the form of source code, object code, an executable file or some intermediate form. The computer readable medium may include: any entity or device capable of carrying computer program code, recording medium, U.S. disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution media, and the like. It should be noted that the computer readable medium may include any suitable increase or decrease as required by legislation and patent practice in the jurisdiction, for example, in some jurisdictions, computer readable media may not include electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
The embodiments of the present invention have been described in detail, but the present invention is only exemplary and is not limited to the embodiments described above. It will be apparent to those skilled in the art that any equivalent modifications or substitutions can be made within the scope of the present invention, and thus, equivalent changes and modifications, improvements, etc. made without departing from the spirit and scope of the present invention should be included in the scope of the present invention.

Claims (10)

1. A control method of a scheduling process is characterized in that the method is applied to a server; the method comprises the following steps:
receiving at least one piece of initial scheduling information input by a first user through a creation terminal;
creating a scheduling plan according to each piece of initial scheduling information to obtain an unviewed plan list;
sending the list of the non-audit plans to an audit terminal, and partially displaying the initial scheduling information corresponding to each scheduling plan; the initial scheduling information comprises scheduling time, scheduling interval and scheduling command number information;
acquiring a first scheduling plan selected by a second user through an audit terminal, and acquiring first scheduling information corresponding to the first scheduling plan;
receiving second scheduling information input by the second user through the auditing terminal;
judging whether the first scheduling information is consistent with the second scheduling information;
and when the first scheduling information is consistent with the second scheduling information, sending prompt information that the first scheduling plan is approved to the auditing terminal.
2. The method for controlling scheduling process of claim 1, wherein before the step of receiving at least one initial scheduling information input by the first user through the creation terminal, further comprising:
receiving a first login request sent by a first user through the creation terminal, wherein the first login request comprises a first user account;
the first user account is matched with a plurality of preset user accounts in the server to obtain a first target preset account matched with the first user account, and each preset user account corresponds to one authority type;
and associating the first user account with the target permission corresponding to the first target preset account.
3. The method for controlling a scheduling process according to claim 1, wherein the step of receiving the second scheduling information input by the second user through the audit terminal is preceded by:
receiving a second login request sent by the second user through the auditing terminal, wherein the second login request comprises a second user account;
the second user account is matched with a plurality of preset user accounts in the server to obtain a second target preset account matched with the second user account, and each preset user account corresponds to one authority type;
and associating the second user account with the target permission corresponding to the second target preset account.
4. The method of claim 1, wherein the first scheduling information includes a first scheduling time and a first scheduling command number, and the second scheduling information includes a second scheduling time and a second scheduling command number; the step of judging whether the first scheduling information is consistent with the second scheduling information includes:
judging whether the first scheduling time is matched with the second scheduling time and whether the first scheduling command number is matched with the second scheduling command number;
if the first scheduling time is matched with the second scheduling time and the first scheduling command number is matched with the second scheduling command number, confirming that the first scheduling information is consistent with the second scheduling information;
and if the first scheduling time is not matched with the second scheduling time or the first scheduling command number is not matched with the second scheduling command number, confirming that the first scheduling information is inconsistent with the second scheduling information.
5. The method for controlling a scheduling process according to claim 1, wherein after the step of determining whether the first scheduling information and the second scheduling information are consistent, the method further comprises:
and when the first scheduling information is inconsistent with the second scheduling information, sending warning information that the first scheduling plan cannot be audited to the auditing terminal.
6. The method for controlling a scheduling process according to claim 1, wherein after the step of sending the prompt message that the first scheduling plan audit is passed to the audit terminal, the method further comprises:
and locking the first dispatching plan, and adding the first dispatching plan to a preset executable plan list.
7. The method of claim 6, wherein each dispatch plan corresponds to a dispatch interval, each dispatch interval including at least one electronic lockset, each electronic lockset corresponding to a lockset identification code; after the step of adding the first dispatch plan to a preset executable plan list, the method further includes:
receiving a task application sent by a third user through an execution terminal, wherein the task application comprises at least one target electronic lock, and each target electronic lock corresponds to one task information;
acquiring a target lock identification code corresponding to each target electronic lock, confirming a target scheduling interval corresponding to each target electronic lock according to the target lock identification code, confirming a target scheduling plan corresponding to each target electronic lock according to the target scheduling interval, and confirming target scheduling information corresponding to each target electronic lock according to the target scheduling plan so as to acquire at least one piece of target scheduling information;
judging whether the task information corresponding to each target electronic lock is correct or not according to the target scheduling information corresponding to each target electronic lock;
if the task information is correct, sending prompt information that the task application is approved to the execution terminal;
and if the task information is incorrect, sending prompt information that the task application is not approved to the execution terminal.
8. The method for controlling a scheduling process according to claim 7, wherein before the step of receiving the task application sent by the execution terminal, the method further comprises:
receiving a third login request sent by the third user through the execution terminal, wherein the third login request comprises a third user account;
the third user account is matched with a plurality of preset user accounts in the server to obtain a third target preset account matched with the third user account, and each preset user account corresponds to one authority type;
and associating the third user account with the target permission corresponding to the third target preset account.
9. A server comprising a memory and a processor coupled to the memory, the memory having stored thereon a computer program operable on the processor;
the processor, when executing the computer program, implements the steps in the method of controlling a scheduling process of any of claims 1-8.
10. A storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the steps in the method of controlling a scheduling process of any one of claims 1 to 8.
CN201810415634.1A 2018-05-03 2018-05-03 Control method, server and storage medium for scheduling process Active CN108768953B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810415634.1A CN108768953B (en) 2018-05-03 2018-05-03 Control method, server and storage medium for scheduling process

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810415634.1A CN108768953B (en) 2018-05-03 2018-05-03 Control method, server and storage medium for scheduling process

Publications (2)

Publication Number Publication Date
CN108768953A CN108768953A (en) 2018-11-06
CN108768953B true CN108768953B (en) 2020-12-18

Family

ID=64009104

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810415634.1A Active CN108768953B (en) 2018-05-03 2018-05-03 Control method, server and storage medium for scheduling process

Country Status (1)

Country Link
CN (1) CN108768953B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020124292A1 (en) * 2018-12-16 2020-06-25 吉安市井冈山开发区金庐陵经济发展有限公司 Method for preparing business plan
CN110231812B (en) * 2019-06-19 2021-06-08 深圳市简工智能科技有限公司 Industrial Internet of things linkage and execution method and device, intelligent equipment and system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103440549A (en) * 2013-08-20 2013-12-11 国家电网公司 Power failure dispatching control system and control method thereof
CN107070945A (en) * 2013-06-19 2017-08-18 华为技术有限公司 Identity logs method and apparatus
CN107450445A (en) * 2017-09-05 2017-12-08 国网山东省电力公司 A kind of unified check of electric power supervisory control signal multistation and acceptance method
CN107580009A (en) * 2016-07-04 2018-01-12 北京新岸线网络技术有限公司 A kind of verifying video content method and system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130282600A1 (en) * 2012-04-23 2013-10-24 Sap Ag Pattern Based Audit Issue Reporting

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107070945A (en) * 2013-06-19 2017-08-18 华为技术有限公司 Identity logs method and apparatus
CN103440549A (en) * 2013-08-20 2013-12-11 国家电网公司 Power failure dispatching control system and control method thereof
CN107580009A (en) * 2016-07-04 2018-01-12 北京新岸线网络技术有限公司 A kind of verifying video content method and system
CN107450445A (en) * 2017-09-05 2017-12-08 国网山东省电力公司 A kind of unified check of electric power supervisory control signal multistation and acceptance method

Also Published As

Publication number Publication date
CN108768953A (en) 2018-11-06

Similar Documents

Publication Publication Date Title
US10679439B2 (en) Method and device for controlling code lock
US20210165869A1 (en) Management system, vehicle, and information processing method
US9430882B2 (en) Computerized vehicle maintenance management system with embedded stochastic modelling
CN110175822B (en) Equipment standing book management method and system
CN110619208B (en) User authentication method, server, user equipment and system
CN108768953B (en) Control method, server and storage medium for scheduling process
CN110599355A (en) Block chain-based vehicle insurance information system, insurance policy registration method and claim settlement method
CN114116508A (en) External platform docking test method and system, forwarding system and vehicle software system
CN110570277A (en) order dispatching method and device
CN108540335B (en) Management method and management device for equipment analysis report
CN111338869B (en) Configuration parameter management method, device, equipment and storage medium
US11863689B1 (en) Security settlement using group signatures
CN111340635A (en) Data checking method, equipment, server and readable storage medium
CN111045725A (en) Control method, device and storage medium of code management system
US11477027B1 (en) Apparatus and methods for management of controlled objects
EP3699802B1 (en) Security data processing device
CN115240298A (en) Vehicle digital key acquisition method and device, computer equipment and storage medium
CN114331661A (en) Data verification method and device, electronic equipment and storage medium
CN111784262A (en) Data management method, device and storage medium for drivers and vehicles on logistics platform
CN111754239A (en) Payment password evaluation method and component integrating data, information and knowledge
CN117710068B (en) Temporary supplier verification method, device and equipment based on artificial intelligence
CN116664081B (en) Case data fixed certificate processing method, device and equipment based on quick-handling identification
CN115086065B (en) Block chain-based data synchronization method and device, electronic equipment and medium
US11095658B2 (en) Enhanced system access controls
CN116341797B (en) Case management method, device and system

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
GR01 Patent grant
GR01 Patent grant