Port operation scheduling system and method facing high-concurrency services

Abstract

The invention relates to the technical field of software systems, and particularly discloses a port operation scheduling system and method for high-concurrency businesses, and the scheduling system comprises a data processing module, a rule label field mapping module, a rule engine module and a scheduling module. The system has the beneficial effects that service rules can be created and modified according to real service management requirements through the rule engine module and stored in the rule base, the data processing module processes received data and matches corresponding rule labels, and the corresponding service rules can be quickly matched by identifying the rule labels; therefore, the corresponding scheduling instruction is generated, and the scheduling efficiency of the port facility equipment is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of software systems, and in particular to a port operation scheduling system and method facing high concurrent business. Background Art

[0002] The technology of high-concurrency business scheduling rules in port operation scenarios has undergone significant evolution. In the early days, ports mainly relied on manual experience and paper documents for scheduling, which was inefficient and difficult to deal with complex situations. With the development of computer technology, basic port management information systems began to be introduced, realizing the initial electronicization of business processing, but there are still problems such as information islands and poor real-time performance.

[0003] Subsequently, the introduction of automated equipment such as automated guided vehicles (AGVs) and automated rail cranes greatly improved the port's operating efficiency. This phase also saw the application of big data analysis and artificial intelligence technologies, which improved forecasting and decision-making capabilities. At the same time, the development of graphical rule engines made business rules more flexible and configurable, and able to quickly adapt to changing needs.

[0004] In recent years, in order to cope with the growing demand for concurrent processing, port dispatching systems have begun to adopt distributed architecture and cloud computing technology. The implementation of microservice architecture has greatly improved the concurrent processing capability and scalability of the system. The global scheduling algorithm is also being continuously optimized, from simple heuristic algorithms to more complex reinforcement learning and multi-objective optimization methods, making resource allocation more efficient and balanced.

[0005] Rule engine technology is the core of implementing flexible business logic. It allows for quick adjustment and optimization of scheduling rules without modifying the underlying code. Modern rule engines not only support complex conditional judgment and action execution, but also greatly improve the ability of business personnel to participate in rule formulation and adjustment.

[0006] The existing rule engine mainly uses Drools technology, which cannot be quickly associated with business logic, nor can it dynamically configure business rules based on real-time data. The execution call time for a single rule is too long, which cannot meet the needs of a large number of devices connected to the port at the same time and the rapid execution of business processes. It also affects the TCS port cloud control scheduling system to issue scheduling instructions in time according to high-concurrency business, affecting the efficiency of port operation scheduling. Summary of the invention

[0007] The present invention is to solve the above problems and propose a port operation scheduling system and method for high concurrent business.

[0008] The technical solution of the present invention is achieved in this way:

[0009] A port operation scheduling system for high-concurrency business, including a data processing module, a rule tag field mapping module, a rule engine module, and a scheduling module.

[0010] The data processing module is a data standardization processing module that interfaces with all internal devices in the port area. It can convert data of different types and protocols into a unified format and pass it to the TCS port cloud control scheduling system;

[0011] The rule tag field mapping module is used to route different processing requirements to different processing paths to form a rule tag with a specific pattern;

[0012] The rule engine module includes three internal modules: rule base, rule verification module and dynamic script executor. The data processing module performs logical operations on various data passed in according to the configured rule tags, and then inputs the passed in numerical parameters into the dynamic script interpreter for execution to obtain a final return value. The final scheduling or other job instruction results are obtained according to the return value and forwarded to the scheduling module.

[0013] The rule base is used to store supplemented rules and temporarily modified and saved rules. It supports adding, deleting, modifying, and querying rules, as well as rule classification, fuzzy and precise retrieval by rule name.

[0014] The rule verification module is used to verify the correctness of the dynamic script in real time and online for the newly created rules or the edited and modified rules. By inputting parameters, the running results of the dynamic script are obtained, and the results are compared with the expected results of the dynamic script to verify the correctness of the rule script.

[0015] The dynamic script executor is used to run the created rules;

[0016] The scheduling module dispatches scheduling tasks to the port facilities and equipment operating in the port through the identified scheduling instructions, so as to schedule the port facilities and equipment.

[0017] Furthermore, the port facilities and equipment connected to the dispatching module include various operating equipment, roadside equipment, monitoring equipment, and port machinery equipment within the port area.

[0018] Furthermore, the rule engine module also includes a rule display module, a rule design module and a rule update module.

[0019] The rule display module is used to display all configured rules, so that operation and maintenance personnel can configure, modify, edit or delete the rules;

[0020] The rule design module is used by operation and maintenance personnel to quickly and visually design new rules;

[0021] The rule update module is used to update newly created or modified rules to the system in a timely manner to facilitate the rapid application of new rules.

[0022] Furthermore, the rule tag field mapping module extracts keywords based on the data uploaded by the port facilities and equipment, and forms rule tags with specific patterns through a unified rule template. Each rule tag contains the following contents: rule tag code, rule classification, scenario type, equipment type, processing method, and rule serial number.

[0023] Furthermore, the content recorded by the rule design module when designing rule labels includes remarks description, number / name / type of parameters, and rule dynamic script list.

[0024] A port operation scheduling method for high concurrent business includes the following steps:

[0025] Step s1, reporting the data list through the network at a set frequency according to different types of equipment, different protocols, and data structures;

[0026] Step s2: The gateway layer receives and processes high-concurrency data and forwards it to the data processing module using a load balancing strategy;

[0027] Step s3: After receiving various types of data, the data processing module performs data cleaning and formatting, and then forwards it to the rule label field mapping module;

[0028] Step s4: Mapping is performed according to the tag field and scenario type carried in the reported data, a processor of the corresponding scenario is selected, and the scenario-oriented type of the rule tag is defined;

[0029] Step s5: Mapping is performed according to the tag field and device type carried in the reported data, a processor of the corresponding device type is selected, and the device type of the rule tag is defined;

[0030] Step s6: Mapping is performed according to the label field and concurrent processing mode carried by the reported data, and different processing modes are selected respectively, so as to define the processing mode of the rule label;

[0031] s6.1. If the data is marked as high concurrency or high frequency, the high concurrency processing method is selected for processing;

[0032] s6.2. If the data is marked as low frequency and high concurrency type, the message queue is selected for processing;

[0033] s6.3. If the data is marked as low concurrency and low frequency type, it is directly processed by code;

[0034] Step s7: directly match the rule in the memory according to the last 3 digits of the tag carried by the reported data;

[0035] Step s8: According to the label bit and rule type carried by the reported data, distinguish whether the rule corresponding to the data is a unit rule or a nested rule, thereby defining the rule classification of the rule label, thereby forming a dynamic script with a complete rule label;

[0036] s8.1. If the data is marked as a unit rule, all execution steps of the rule are read directly from the cache;

[0037] s8.2. If the data is marked as a nested rule, first read the list of all nested rule IDs under the rule, and then loop through the list of all business script execution steps for the ID and all nested rules;

[0038] Step s9, sequentially bringing the parameter list passed in step s1 into the dynamic script read in step s8 for interpretation and execution, completing the interpretation and execution of a unit rule or completing the interpretation and execution of a nested rule;

[0039] Step s10: If after step s9 is executed, the data does not conform to the rule judgment logic after verification by the rule verification module, the data is discarded without being processed, and the execution ends;

[0040] Step s11: If step s9 is completed and the rule verification module verifies that the rule judgment logic is met, the scheduling instruction is output;

[0041] Step s12: forwarding the scheduling instruction generated by the rule engine module to the scheduling module;

[0042] Step s13: The dispatching module encapsulates and formats the instructions according to the instruction requirements, and then directly sends them to the corresponding port facilities and equipment;

[0043] Step s14: the port facility equipment executes the business scheduling operation after receiving the scheduling instruction;

[0044] Step s15, the process ends.

[0045] By adopting the above technical scheme, the beneficial effects of the present invention are as follows: through the rule engine module, business rules can be created and modified according to actual business management needs and stored in the rule library; the data processing module matches the corresponding rule tags to the received data processing, and can quickly match the corresponding business rules by identifying the rule tags, thereby generating corresponding scheduling instructions, thereby improving the scheduling efficiency of port facilities and equipment; a rule engine based on a dynamic script method of field mapping is adopted to shorten the processing time of a single rule and improve the high concurrent processing capability of multiple rules; the rule engine module can be used to realize the rapid editing, creation and modification of business rules, so that maintenance personnel can quickly configure the business system without modifying the underlying code, thereby improving the deployment efficiency of new or improved business rules. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0047] Figure 1 It is a system architecture diagram of the present invention;

[0048] Figure 2 It is a bitwise parsing diagram of the rule labels of the present invention;

[0049] Figure 3 It is a schematic diagram of the steps of converting the rules of the present invention into executable business scripts;

[0050] Figure 4 is a diagram of the system deployment mode of the present invention;

[0051] Figure 5 This is a schematic diagram of the high-concurrency processing principle of the business of the present invention;

[0052] Figure 6 It is a schematic diagram of directly generating scheduling instructions according to the rules of the present invention;

[0053] Figure 7 It is a schematic diagram of rule updating of the present invention;

[0054] Figure 8 It is a schematic diagram of a dynamic script of the present invention;

[0055] Fig. 9 It is a flow chart of the working principle of the scheduling method of the present invention;

[0056] Fig.10 It is a diagram of the execution process of Case 1 of the present invention;

[0057] Fig.11 is a diagram of the execution process of Case 2 of the present invention;

[0058] Fig.12 This is a diagram of the execution process of Case 3 of the present invention. DETAILED DESCRIPTION

[0059] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0060] like Figure 1-Figure 3 , Figure 6-8 As shown, a port operation scheduling system facing high concurrent business includes a data processing module, a rule label field mapping module, a rule engine module, and a scheduling module.

[0061] The data processing module is a data standardization processing module that interfaces with all internal devices in the port area. It can convert data of different types and protocols into a unified format and pass it to the TCS port cloud control scheduling system;

[0062] The rule tag field mapping module is used to route different processing requirements to different processing paths to form a rule tag with a specific pattern;

[0063] The rule engine module includes three internal modules: rule base, rule verification module and dynamic script executor. The data processing module performs logical operations on various data passed in according to the configured rule tags, and then inputs the passed in numerical parameters into the dynamic script interpreter for execution to obtain a final return value. The final scheduling or other job instruction results are obtained according to the return value and forwarded to the scheduling module.

[0064] The rule base is used to store supplemented rules and temporarily modified and saved rules. It supports adding, deleting, modifying, and querying rules, as well as rule classification, fuzzy and precise retrieval by rule name.

[0065] The rule verification module is used to verify the correctness of the dynamic script of the newly created rules or the edited and modified rules in real time and online. By inputting parameters, the running results of the dynamic script are obtained, and the results are compared with the expected results of the dynamic script to verify the correctness of the rule script; for example: create a rule with the input of power, when the power is greater than or equal to 18, it returns "0", otherwise it returns "1", and then enter a value for verification. For example, after entering 17, the return value is "1", which is the same as the expected value "1", and after entering 18, the return value is "0", which is the same as the expected value "0", which means that the rule logic is reasonable and can be used. Otherwise, the rule code needs to be modified for re-verification. It can be published to the rule library only after the verification passes.

[0066] The dynamic script executor is used to run the created rules. The business script can be very flexible and can be long, short, simple or complex to freely control the business scheduling logic. It can be flexibly modified, adjusted and debugged without modifying the TCS infrastructure code, so as to cope with urgent and scattered needs, reduce the development workload, reduce the risk of service operation and maintenance, and allow operation and maintenance personnel to write simple logic to meet the needs without large-scale development, so as to adapt to the rapid iteration of port needs;

[0067] The dispatch module dispatches dispatch tasks to the port facilities and equipment operating in the port through the identified dispatch instructions, and dispatches the port facilities and equipment, such as issuing instructions to let the unmanned container trucks that are short of power charge at the charging position, issuing instructions to let the unmanned container trucks transport containers to the designated location, issuing instructions to let the bridge crane lift the containers on the unmanned container trucks to the designated bay, etc.

[0068] In this embodiment, the port facilities and equipment connected to the scheduling module include various operating equipment, roadside equipment, monitoring equipment, and port machinery equipment within the port area, including: gantry cranes, bridge cranes, forklifts, reach loaders, cameras, radars, manned container trucks, unmanned container trucks, and anemometers, etc.

[0069] In this embodiment, the rule engine module also includes a rule display module, a rule design module and a rule update module.

[0070] The rule display module is used to display all configured rules, which is convenient for operation and maintenance personnel to configure, modify, edit or delete the rules, and provide a management list for operation and maintenance personnel;

[0071] The rule design module is used by operation and maintenance personnel to quickly design new rules visually. After the business rules are designed through the rule design module, they are published. The logic and dynamic scripts contained in the rule are converted into executable business script step nodes (the flowchart is converted into executable business script step nodes), and pushed to the web application server cache. The execution process is as follows: Figure 3As shown in the figure, when the rule engine is compiled, it will compile the executable circuit into an executable program containing three paths, while the rule engine based on dynamic scripts will dynamically interpret and execute one of them according to the condition judgment, reducing the compilation link, thereby reducing the execution time and fundamentally improving the concurrent processing capability;

[0072] The rule update module is used to update newly created or modified rules to the system in a timely manner, facilitating the rapid application of new rules and enabling imperceptible hot updates without restarting the application when rule parameters or rule business logic change.

[0073] In this embodiment, the rule label field mapping module extracts data keywords uploaded by port facilities and equipment, and forms rule labels with specific patterns through unified rule templates. To create rule labels, the following contents need to be defined in sequence: rule label code, rule classification, scenario type, equipment type, processing method, rule serial number, remark description, number / name / type of parameters, and rule dynamic script list.

[0074] During the rule creation process, the rules are standardized. The following fields need to be defined when creating rules:

[0075] ①Rule number: such as: 001, 002, the length is unlimited;

[0076] ②Rule label: For example, it is represented by S, the value range is limited to letters, and the length is unlimited;

[0077] ③Rule classification: unit rule, nested combination rule, such as: represented by 0, 1, the value range is limited to 0-9, for example, "1" represents a unit rule, and "2" represents a nested combination rule composed of two unit rules;

[0078] ④ Scenario-oriented types: site rules, traffic rules, business rules (safety rules, efficiency rules), etc. For example, "1" represents site rules, "2" represents traffic rules, and "3" represents business rules. The value range is limited to 0-9;

[0079] ⑤ Equipment type: the equipment marking code, such as 1 for gantry crane, 2 for bridge crane, 3 for unmanned container truck, 4 for manned container truck (when the equipment type exceeds 10, AZ is used instead), the value range is limited to 0-9, AZ;

[0080] ⑤Processing method: high frequency, high concurrency; low frequency, high concurrency; low frequency, low concurrency. For example, "0" represents high frequency, high concurrency, "1" represents low frequency, high concurrency, and "2" represents low frequency, low concurrency. The value range is limited to 0-2;

[0081] ⑥ Input parameter number, name and type;

[0082] ⑦Remarks description;

[0083] ⑧Process editing;

[0084] ⑨Dynamic scripts of process nodes;

[0085] When creating this rule, a dedicated tag will be automatically created for it to distinguish and process data. When the device reports data, it only needs to carry this tag, and it can automatically match the rule and automatically select the processing method.

[0086] Rule classification:

[0087] Rules are divided into unit rules and nested combination rules. A unit rule is an independent rule that contains logical judgment conditions, dynamic scripts and other elements; a combination nested rule contains logical judgment conditions, dynamic scripts, and one or more nested unit rules. Rules can be nested and combined. If you choose to create a combination rule, you can select existing unit rules for combination and nesting. Combination rules cannot be nested in combination rules, and combination rules can only be combined and nested by unit rules.

[0088] Rule scenario classification:

[0089] Rule scenario classification includes: site rules, traffic rules, and business rules (safety rules, efficiency rules).

[0090] Site rules, including quay crane area rules, yard area rules, customs inspection area rules, transfer station rules, charging station area rules, etc.

[0091] Traffic rules, including speed limit rules, road turning rules, lane change rules, etc.

[0092] Business rules (safety rules), including the alarm rules for the unmanned container truck’s own equipment, etc.

[0093] Business rules (efficiency rules), including scheduling efficiency matching rules, job priority improvement rules, etc.

[0094] The system of the present invention is a subsystem of the TCS port cloud control dispatching system. It adopts multi-machine multi-node and distributed deployment, and the overall microservice architecture adopts a load balancing strategy to achieve high concurrent processing (such as Figure 4 , Figure 5 As shown in the figure). Applications on the Web application server can be deployed in a multi-machine, multi-node mode. For example, rule applications can be deployed on multiple application servers. Multiple applications can be deployed on web application server 1, including user center, Dispatcher scheduling application, rule application, and other applications. Both gateway and business scheduling applications can be deployed in a multi-machine, multi-node mode.

[0095] Business rules are a set that can be added, subtracted, modified, and arranged. The scheduling instructions generated based on the rules are directly issued by the scheduling module to the job set card or other job equipment.

[0096] like Fig. 9 As shown, a port operation scheduling method facing high concurrent business includes the following steps:

[0097] Step s1, according to different types of equipment, different protocols, and data structures, report the data list through the network at a set frequency (data sources include: various data reported by ships, containers, bridge cranes, gantry cranes, forklifts, unmanned container trucks, wind speed meters and other equipment);

[0098] Step s2: The gateway layer receives and processes high-concurrency data and forwards it to the data processing module using a load balancing strategy;

[0099] Step s3: After receiving various types of data, the data processing module performs data cleaning and formatting, and then forwards it to the rule label field mapping module;

[0100] Step s4: Mapping is performed according to the tag field and scenario type carried in the reported data, the processor of the scenario is selected, and the scenario-oriented type of the rule tag is defined as "S0[1]A0001";

[0101] Step s5: Mapping is performed according to the tag field and device type carried in the reported data, a processor of the corresponding device type is selected, and the device type of the rule tag is defined as "S01[A]0001";

[0102] Step s6: Mapping is performed according to the tag field and concurrent processing mode carried by the reported data, and different processing modes are selected respectively, thereby defining the processing mode of the rule tag "S01A[0]001";

[0103] s6.1. If the data is marked as high concurrency or high frequency, the high concurrency processing method is selected for processing;

[0104] s6.2. If the data is marked as low frequency and high concurrency type, the message queue is selected for processing;

[0105] s6.3. If the data is marked as low concurrency and low frequency type, it is directly processed by code;

[0106] Step s7: directly match the rule "S01A0

[001] " in the memory according to the last three digits of the tag carried by the reported data. The last three digits of the tag are the serial number code of the business rule in the rule base.

[0107] Step s8: According to the label bit and rule type carried by the reported data, the rule corresponding to the data is distinguished as a unit rule or a nested rule, so as to define the rule classification of the rule label "S[0]1A0001", thereby forming a dynamic script with a complete rule label;

[0108] s8.1. If the data is marked as a unit rule, all execution steps of the rule are read directly from the cache;

[0109] s8.2. If the data is marked as a nested rule, first read the list of all nested rule IDs under the rule, and then loop through the list of all business script execution steps for the ID and all nested rules;

[0110] Step s9, sequentially bringing the parameter list passed in step s1 into the dynamic script read in step s8 for interpretation and execution, completing the interpretation and execution of a unit rule or completing the interpretation and execution of a nested rule;

[0111] Step s10: If after step s9 is executed, the data does not conform to the rule judgment logic after verification by the rule verification module, the data is discarded without being processed, and the execution ends;

[0112] Step s11: If step s9 is completed and the rule verification module verifies that the rule judgment logic is met, the scheduling instruction is output;

[0113] Step s12: forwarding the scheduling instruction generated by the rule engine module to the scheduling module;

[0114] Step s13: The dispatching module encapsulates and formats the instructions according to the instruction requirements, and then directly sends them to the corresponding port facilities and equipment;

[0115] Step s14: the port facility equipment executes the business scheduling operation after receiving the scheduling instruction;

[0116] Step s15, the process ends.

[0117] Example of high-concurrency business scheduling method based on port operation scenario:

[0118] Case 1: When the battery level of the container truck is lower than 18%, the charging task is triggered.

[0119] Rule design execution steps:

[0120] 1-1. Design a rule in the rule design module and name it "Charging Threshold Judgment". When the battery level is lower than 18%, return to the charging station for charging.

[0121] 1-2. Publish the updated rules to all node servers to complete the rule update.

[0122] like Fig.10 As shown, the unmanned container truck T101 reports control data (including power data) at a cycle of every 100ms, which is processed by the data processing module and called by the rule module for calculation. A rule tag is generated for the data. The rule engine receives the power data and calls the rule corresponding to the rule tag to determine whether it is less than 18%. If the power is not less than 18%, the data is discarded. If it is less than 18%, the rule is triggered to generate a charging operation instruction and send it to the scheduling module. The scheduling module receives the instruction and assembles the data and sends it directly to the unmanned container truck T101. After receiving the scheduling instruction, the unmanned container truck T101 goes to the charging station for charging. This instruction is a unit rule. After a period of operation, the charging threshold can be changed and then updated through the rule update module. At the same time, when creating rules, nested combination rules can be created based on whether it is in an operating state, which can determine both the power level and whether it is in an operating state.

[0123] Case 2: The wind speed is greater than level 5, triggering the stop of job scheduling.

[0124] The rule design and execution steps are similar to those in Case 1. The specific execution process is as follows: Fig.11 As shown, the anemometer reports real-time data (including wind speed value) at intervals of 1 second, which is processed by the data processing module and called by the rule module for calculation, and a rule label is generated for the data. The rule engine receives the real-time data and calls the corresponding rule to determine whether the wind speed is greater than level 5. If the wind speed is not greater than level 5, the data is discarded. If it is not less than level 5, the rule is triggered, and an instruction to notify all equipment to stop working is generated and sent to the scheduling module. The scheduling module receives the instruction, generates an instruction and sends it to all port operation equipment. The port operation equipment receives the instruction and stops working.

[0125] Case 3: The idle time of the container truck is greater than 20 minutes, triggering priority scheduling.

[0126] The rule design and execution steps are similar to those in Case 1. The specific execution process is as follows: Fig.12 As shown, the unmanned container truck T101 reports control data (including a field indicating whether it is currently operating) at a period of every 100ms, which is processed by the data processing module and called by the rule module for calculation. A rule label is generated for the data. The rule engine receives the status data and calls the rule corresponding to the rule label to determine whether the idle time is greater than 20 minutes. If the idle time does not exceed 20 minutes, the data is discarded. If it is greater than 20 minutes, the rule is triggered to generate an instruction to increase the job priority and send it to the scheduling module. The scheduling module receives the instruction, adds it to the priority scheduling queue, and issues the job task to the unmanned container truck T101 as soon as there is a scheduling task.

[0127] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A port operation scheduling system for high concurrent business, characterized by: Including data processing module, rule label field mapping module, rule engine module, scheduling module, The data processing module is a data standardization processing module that interfaces with all internal devices in the port area. It can convert data of different types and protocols into a unified format and pass it to the TCS port cloud control scheduling system; The rule tag field mapping module is used to route different processing requirements to different processing paths to form a rule tag with a specific pattern; The rule engine module includes three internal modules: rule base, rule verification module and dynamic script executor. The data processing module performs logical operations on various data passed in according to the configured rule tags, and then inputs the passed in numerical parameters into the dynamic script interpreter for execution to obtain a final return value. The final scheduling or other job instruction results are obtained according to the return value and forwarded to the scheduling module. The rule base is used to store supplemented rules and temporarily modified and saved rules. It supports adding, deleting, modifying, and querying rules, as well as rule classification, fuzzy and precise retrieval by rule name. The rule verification module is used to verify the correctness of the dynamic script in real time and online for the newly created rules or the edited and modified rules. By inputting parameters, the running results of the dynamic script are obtained, and the results are compared with the expected results of the dynamic script to verify the correctness of the rule script. The dynamic script executor is used to run the created rules; The scheduling module dispatches scheduling tasks to the port facilities and equipment operating in the port through the identified scheduling instructions, so as to schedule the port facilities and equipment.

2. A port operation scheduling system for high concurrent business according to claim 1, characterized in that: The port facilities and equipment connected to the dispatching module include various operating equipment, roadside equipment, monitoring equipment, and port machinery equipment within the port area.

3. The port operation scheduling system facing high concurrent business according to claim 1 is characterized by: The rule engine module also includes a rule display module, a rule design module and a rule update module. The rule display module is used to display all configured rules, so that operation and maintenance personnel can configure, modify, edit or delete the rules; The rule design module is used by operation and maintenance personnel to quickly and visually design new rules; The rule update module is used to update newly created or modified rules to the system in a timely manner to facilitate the rapid application of new rules.

4. The port operation scheduling system facing high concurrent business according to claim 3 is characterized by: The rule tag field mapping module extracts data keywords uploaded by port facilities and equipment, and forms rule tags with specific patterns through a unified rule template. Each rule tag contains the following contents: rule tag code, rule classification, scenario type, equipment type, processing method, and rule serial number.

5. A port operation dispatching system for high concurrent business according to claim 4, characterized in that: The content recorded by the rule design module when designing the rule label includes a remark description.

6. A port operation scheduling method for high concurrent business, characterized by: The following steps are involved: Step s1, reporting the data list through the network at a set frequency according to different types of equipment, different protocols, and data structures; Step s2: The gateway layer receives and processes high-concurrency data and forwards it to the data processing module using a load balancing strategy; Step s3: After receiving various types of data, the data processing module performs data cleaning and formatting, and then forwards it to the rule label field mapping module; Step s4: Mapping is performed according to the tag field and scenario type carried in the reported data, a processor of the corresponding scenario is selected, and the scenario-oriented type of the rule tag is defined; Step s5: Mapping is performed according to the tag field and device type carried in the reported data, a processor of the corresponding device type is selected, and the device type of the rule tag is defined; Step s6: Mapping is performed according to the label field and concurrent processing mode carried by the reported data, and different processing modes are selected respectively, so as to define the processing mode of the rule label; s6.

1. If the data is marked as high concurrency or high frequency, the high concurrency processing method is selected for processing; s6.

2. If the data is marked as low frequency and high concurrency type, the message queue is selected for processing; s6.

3. If the data is marked as low concurrency and low frequency type, it is directly processed by code; Step s7: directly match the rule in the memory according to the last 3 digits of the tag carried by the reported data; Step s8: According to the label bit and rule type carried by the reported data, distinguish whether the rule corresponding to the data is a unit rule or a nested rule, thereby defining the rule classification of the rule label, thereby forming a dynamic script with a complete rule label; s8.

1. If the data is marked as a unit rule, all execution steps of the rule are read directly from the cache; s8.

2. If the data is marked as a nested rule, first read the list of all nested rule IDs under the rule, and then loop through the list of all business script execution steps for the ID and all nested rules; Step s9, sequentially bringing the parameter list passed in step s1 into the dynamic script read in step s8 for interpretation and execution, completing the interpretation and execution of a unit rule or completing the interpretation and execution of a nested rule; Step s10: If after step s9 is executed, the data does not conform to the rule judgment logic after verification by the rule verification module, the data is discarded without being processed, and the execution ends; Step s11: If step s9 is completed and the rule verification module verifies that the rule judgment logic is met, the scheduling instruction is output; Step s12: forwarding the scheduling instruction generated by the rule engine module to the scheduling module; Step s13: The dispatching module encapsulates and formats the instructions according to the instruction requirements, and then directly sends them to the corresponding port facilities and equipment; Step s14: the port facility equipment executes the business scheduling operation after receiving the scheduling instruction; Step s15, the process ends.

Images