Intelligent industrial park integrated management and control system and method based on internet of things

Abstract

The application discloses an integrated management and control system and method for a smart industrial park based on the Internet of Things, and relates to the technical field of park management and control, which comprises the following steps: collecting park event data, equipment operation data and management and control resource state data, generating event trigger states and management and control resource available states; generating an event influence window according to the event trigger states and the equipment operation data; generating an event resource matching result and an event disposal path based on the event influence window and the management and control resource available states; generating an event disposal instruction according to the event disposal path, collecting corresponding event disposal feedback of the event disposal instruction, rewriting the event influence window and the management and control resource available states according to the event disposal feedback, and generating an integrated management and control result for the park; and the application improves the adaptation degree among event disposal, resource linkage and feedback rewriting under the condition that multiple types of events in the park continuously and concurrently trigger and management and control resources are scattered and occupied.

Description

Technical Field

[0001] This invention relates to the field of park management technology, specifically to an integrated management system and method for smart industrial parks based on the Internet of Things. Background Technology

[0002] With the continuous integration of IoT devices, park business platforms, and coordinated response resources into smart industrial parks, park management is gradually expanding from single-point equipment monitoring to comprehensive management across security, fire protection, access, energy consumption, environment, and equipment operation and maintenance. The relevant management and control platforms can typically complete the access of multi-source sensing data, the aggregation of alarm information, the display of equipment status, and the dispatch of basic work orders, providing good basic support for park operation monitoring and daily response coordination.

[0003] Currently, in the integrated management and control of smart industrial parks based on the Internet of Things, equipment failures, security anomalies, fire alarms, access anomalies, energy consumption anomalies, and environmental anomalies may be triggered continuously in adjacent time periods or the same area. The areas of action, associated equipment, and types of resources for handling different events vary. If the handling is assigned only according to the source of the alarm or the category of the event, it is easy to cause instability in the correspondence between the event object, the equipment object, and the resource object, making it difficult to keep the handling priority and resource call object consistent in the case of multiple concurrent events.

[0004] Secondly, security personnel, maintenance personnel, fire protection resources, access control resources, and equipment control resources within the park are typically distributed according to service areas, resource types, and time periods of occupation. Whether a resource is available for use depends not only on the resource type but also on the service area, current location, time period of occupation, and the outcome of the previous action. If the feedback from the action is not promptly reflected in the scope of the event's impact and the resource occupation status, issues such as duplicate resource occupation, unused idle resources not being utilized, and the order of event handling deviating from the actual impact period may arise. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides an integrated management and control system and method for smart industrial parks based on the Internet of Things.

[0006] An integrated management and control system for smart industrial parks based on the Internet of Things, comprising:

[0007] Status generation module S11: Collects park event data, equipment operation data and management resource status data, and generates event trigger status and management resource availability status;

[0008] Window generation module S12: Generates event-affected windows based on event triggering status and device operating data;

[0009] Linkage matching module S13: Based on the event impact window and the availability status of control resources, it generates event resource matching results and event handling paths;

[0010] Feedback Write-back Module S14: Generates event handling instructions based on the event handling path, collects event handling feedback corresponding to the event handling instructions, writes back the event impact window and the availability status of control resources based on the event handling feedback, and generates integrated park control results.

[0011] An integrated management and control method for smart industrial parks based on the Internet of Things (IoT), applicable to any of the aforementioned integrated management and control systems for smart industrial parks based on the IoT:

[0012] S21: Collect park event data, equipment operation data, and management resource status data, and generate event trigger status and management resource availability status;

[0013] S22: Generate an event impact window based on the event triggering status and device operating data;

[0014] S23: Based on the event impact window and the availability of control resources, generate event resource matching results and event handling paths;

[0015] S24: Generate event handling instructions based on the event handling path, collect event handling feedback corresponding to the event handling instructions, write back the event impact window and the availability status of control resources based on the event handling feedback, and generate integrated park control results.

[0016] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0017] This invention provides a unified representation of various events and dispersed management resources in a park by using event triggering status and management resource availability status. This enables a comparable management basis to be formed between the event's area of ​​effect, equipment operating status, resource type, service area, and occupation period. It reduces mismatches between event numbers, equipment numbers, and management resource numbers when multiple events are triggered concurrently, and improves the correspondence between event handling objects and resource linkage objects.

[0018] Furthermore, this invention also enables the event handling process to maintain a dynamic correspondence with the management resource occupation and release process by using a closed-loop write-back mechanism between the event impact window, event resource matching results, event handling path, and event handling feedback. After the handling status changes, the event impact window and the availability status of management resources are simultaneously corrected, reducing the situation of repeated occupation of management resources, unused idle resources, and event handling priority deviating from the actual impact period. This improves the adaptability of the integrated management results of the park to concurrent event handling and resource linkage changes.

[0019] In summary, this invention improves the adaptability between event handling, resource coordination, and feedback writing in the context of continuous concurrent triggering of multiple events in the park and the dispersed use of management resources. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this invention. For those skilled in the art, other drawings can be obtained based on these drawings.

[0021] Figure 1 This is a block diagram of an integrated management and control system for a smart industrial park based on the Internet of Things, provided in Embodiment 1 of the present invention.

[0022] Figure 2 The flowchart illustrates an integrated management and control method for smart industrial parks based on the Internet of Things, as provided in Embodiment 2 of the present invention. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0024] Example 1

[0025] Please see Figure 1 As shown in the figure, this embodiment discloses an integrated management and control system for smart industrial parks based on the Internet of Things. The system includes:

[0026] Status generation module S11: Collects park event data, equipment operation data and management resource status data, and generates event trigger status and management resource availability status;

[0027] Specifically, the park event data is collected from at least one of the following: park event management platform, security alarm system, fire alarm system, access control system, parking management system, energy consumption monitoring system, environmental monitoring system, or equipment alarm system;

[0028] The park's event data includes event number, event type, trigger time, and event area. Event types include at least one of the following: equipment failure events, security anomaly events, fire alarm events, access anomaly events, energy consumption anomaly events, and environmental anomaly events.

[0029] Equipment operation data is collected by IoT gateways, equipment controllers, sensor acquisition terminals or park equipment management platforms. The equipment operation data includes equipment number, equipment type, equipment location, operating time and equipment operation status.

[0030] The status data of controlled resources is collected by security dispatch system, operation and maintenance work order system, fire linkage system, property dispatch system or emergency response system. The status data of controlled resources includes the controlled resource number, resource type, service area, occupation time period and resource location.

[0031] It should be noted that the equipment operating status parameters adopt the corresponding status caliber according to the equipment type. For example, access control equipment corresponds to the open / closed status, camera equipment corresponds to the online status, fire protection equipment corresponds to the alarm status, energy consumption equipment corresponds to the application energy value, and environmental equipment corresponds to the environmental data collection value.

[0032] The operating status values ​​of different equipment types are not directly compared numerically; the difference in status values ​​of subsequent equipment is only calculated under the same equipment number and the same status caliber.

[0033] Specifically, the steps for generating event trigger states and managing resource availability states are as follows:

[0034] S111: Read the event number, event type, trigger time, and event area from the park event data, arrange the event numbers according to the trigger time, and generate event time arrangement data.

[0035] In one specific embodiment, the first The park event data corresponding to each event is represented as follows:

[0036]

[0037] in, For the first Park event data corresponding to each event Number the event. For event type, For the trigger time, This refers to the area where the event applies.

[0038] Event Scope The area boundary is represented by the spatial coordinate system of the park. The area boundary is the building number, floor number, room number, road section number, parking zone number, or a polygonal area composed of the coordinates of multiple boundary points.

[0039] When the event's scope is represented by a polygonal region, the event's scope is represented as follows:

[0040]

[0041] in, The first of the event's scope The coordinates of the boundary points.

[0042] According to the trigger time Event number Sort in ascending order;

[0043] If multiple event numbers have the same trigger time, they are arranged according to the order in which the event data enters the park event management platform, and event time arrangement data is generated.

[0044] The data arranged by event time is represented as follows:

[0045]

[0046] in, Arrange the data according to the event time. The order of event numbers after they are triggered, and satisfying the following conditions: .

[0047] S112: Based on the data arranged at the time of the event and the equipment operation data, match the equipment number and equipment operation status quantity within the area affected by the event to generate the corresponding data for the event equipment.

[0048] Specifically, the steps for generating data corresponding to the event device are as follows:

[0049] S112.1: By reading the equipment number, equipment type, equipment location, and equipment operating status data from the equipment operation data, the equipment space value data is generated.

[0050] In one specific embodiment, the first The device in the The device operation data corresponding to each running time point is represented as follows:

[0051]

[0052] in, For the first The device in the Device operation data corresponding to each running time. For equipment number, For equipment type, For equipment location, For runtime, This refers to the equipment's operating status.

[0053] Equipment location The location coordinates are represented using the spatial coordinate system of the park:

[0054]

[0055] in, and Let these be the coordinates of the device in planar space. This indicates the floor or height where the equipment is located.

[0056] The equipment number, equipment type, equipment location, and equipment operating status are written into the same data structure according to the operating time to generate equipment space value data:

[0057]

[0058] in, This is the data retrieved from the device space.

[0059] S112.2: Based on the device space value data and the event's effective area, filter the device numbers located within the event's effective area and generate regional device data.

[0060] In a specific embodiment, when the event action area is represented by a polygonal region, the ray intersection determination method is used to determine whether the device location is within the event action area.

[0061] For equipment location Read the corresponding plane coordinates ,from A ray is emitted horizontally, and the number of intersections between the ray and the boundary of the event's affected area is counted. .

[0062] The region inclusion determination result is expressed as follows:

[0063]

[0064] in, For the first The location of the device relative to the first The area within which an event applies includes the judgment result;

[0065] when At that time, equipment number Located in the area of ​​event effect Inside;

[0066] when At that time, equipment number Not located in the event's area of ​​effect Inside.

[0067] If the area affected by the event is represented by a building number, floor number, or room number, then the building number, floor number, or room number in the device location is compared with the area affected by the event.

[0068] If the device numbers match, retain the device number; if the device numbers do not match, discard the device number.

[0069] Write the device number, device type, device location, and device operating status within the event's affected area into the area's device data;

[0070] Regional equipment data is represented as follows:

[0071]

[0072] in, For the first The regional device data corresponding to each event number.

[0073] S112.3: By arranging data based on regional device data and event time, read the device operating status data according to the trigger time, and generate corresponding data for the event device.

[0074] In one specific embodiment, for event number Triggering time Read the same device number from the regional device data. Device operating status quantities before and after the trigger moment;

[0075] When there is a runtime At that time, This refers to the device operating status quantity corresponding to the triggering time.

[0076] When satisfied At that time, linear interpolation is used to read the device operating status variables corresponding to the trigger time:

[0077]

[0078] in, Number the event At the trigger time Corresponding device number The device's operating status.

[0079] It should be noted that if the device operating status quantity is a switch quantity, enumeration status, or alarm status, linear interpolation is not used; instead, the device operating status quantity that is closest to the trigger time and within the same sampling period is read.

[0080] If there are no device operating status quantities within the same sampling period before and after the triggering time, the corresponding device number will be marked as a missing device number and will not be written into the event device's corresponding data.

[0081] The data corresponding to the event device is represented as follows:

[0082]

[0083] in, Number the event The corresponding event device data.

[0084] S113: Based on the data corresponding to the event device, calibrate the device operating status quantity according to the event number and trigger time, and generate the event trigger status.

[0085] In one specific embodiment, the same event number The event type, trigger time, event scope, device number, device type, and device operating status corresponding to the trigger time are written into the same trigger status unit to generate the event trigger status.

[0086] The event trigger state is represented as follows:

[0087]

[0088] in, Number the event The corresponding event trigger state.

[0089] It should be noted that all device operating status quantities in the event-triggered state correspond to the same trigger time. This avoids inconsistencies in the state sampling times of different devices under the same event number.

[0090] S114: Based on the managed resource status data, break down the resource type, service area, occupation time period, and resource location to generate the managed resource availability status.

[0091] In one specific embodiment, the first The status data of each managed resource is represented as follows:

[0092]

[0093] in, For the first The status data of each managed resource. To manage resource numbering, For resource type, For the service area, For the time period occupied, For resource location.

[0094] The time period occupied is represented as:

[0095]

[0096] in, To occupy the start time, This is the end time of occupation.

[0097] When the controlled resource number is not occupied, the occupied period is recorded as an empty value;

[0098] When a managed resource number has multiple occupied time periods, the multiple occupied time periods are arranged according to the start time of occupation, and the available status of the managed resource is written to each of them.

[0099] The availability status of managed resources is represented as follows:

[0100]

[0101] in, Numbering of managed resources The corresponding availability status of managed resources.

[0102] It should be noted that the correspondence rules between resource types and event types are pre-set by the park management platform. For example, fire alarm events correspond to fire handling resources, security anomaly events correspond to security handling resources, equipment failure events correspond to equipment operation and maintenance resources, and access anomaly events correspond to access management resources.

[0103] The corresponding rules are the established contents of the park's operation and management system or emergency response plan.

[0104] It should be noted that this module converts park events, equipment status, and management resources from different sources into the same event number, trigger time, trigger status, and resource availability status under the event's area of ​​effect, thus avoiding the inability of cross-system data to be directly linked.

[0105] Window generation module S12: Generates event-affected windows based on event triggering status and device operation data.

[0106] Specifically, the steps to generate the event-affected window are as follows:

[0107] S121: Based on the event trigger status, read the event number, trigger time, event area, and corresponding event device data to generate event location data.

[0108] In one specific embodiment, from the event triggering state Read the event number Triggering time Area of ​​Event Scope Data corresponding to event devices Generate event location data.

[0109] Event location data is represented as follows:

[0110]

[0111] in, Number the event The corresponding event location data.

[0112] Event location data preserves the correspondence between event number, trigger time, event area, and corresponding data of the event device, so that the device operating status data under the same event number can be read forward and backward along the operating time.

[0113] S122: Based on the event location data, read the device operating status before and after the trigger time from the device operating data, and calculate the device status difference.

[0114] In one specific embodiment, for event location data Device number Read the running time before and after the trigger time from the device's operating data;

[0115] Let the runtime before the trigger time be . The runtime after the trigger time is The corresponding equipment operating status variables are as follows: and .

[0116] The equipment status difference is expressed as:

[0117]

[0118] in, Number the event Next device number The corresponding device status difference.

[0119] If the equipment operating status quantity is a multi-dimensional status quantity, then calculate the equipment status difference for each equipment operating status quantity of the same dimension.

[0120] Different dimensions of device operating status quantities are not added or subtracted together.

[0121] For switch quantities or enumerated states, first convert the state codes preset in the device operation data into numerical codes, and then calculate the device state difference.

[0122] The status codes are loaded by the park's equipment management platform. For example, the status code is 0 for off, 1 for on, 0 for offline, 1 for online, 0 for no alarm, and 1 for alarm.

[0123] S123: By filtering the device number and running time of consecutively oriented values ​​based on the device status difference and the event's area of ​​effect, a status continuation range is generated.

[0124] Specifically, the steps for generating the state continuation range are as follows:

[0125] S123.1: By reading the difference symbol of the same device number at adjacent operating times through the device status difference, a status difference symbol is generated.

[0126] In one specific embodiment, for the same device number Arrange the equipment operating status variables according to the operating time, and calculate the equipment status difference between adjacent operating times:

[0127]

[0128] in, Number the equipment In adjacent running time and The difference in device status between them.

[0129] The state difference symbol is represented as:

[0130]

[0131] in, Number the equipment The sign of the state difference between adjacent running times.

[0132] S123.2: Based on the sign of the status difference, filter the device numbers with the same sign of the difference between adjacent running times and generate the same-direction device data.

[0133] In one specific embodiment, if the same device number The sign of the difference between two adjacent states satisfies:

[0134]

[0135] Then the equipment number Running time Running time The status difference sign is written to the same-direction device data.

[0136] Data from devices moving in the same direction is represented as follows:

[0137]

[0138] in, Number the event The corresponding data from the same direction device.

[0139] It should be noted that when the status difference sign is 0, no data is written to the same-direction device;

[0140] If the same device number satisfies the same sign of the difference multiple times within a consecutive operating time, it will be retained consecutively according to the operating time.

[0141] S123.3: By arranging the running times of consecutively oriented values ​​through the data and event scope of the same-direction devices, a state continuation range is generated.

[0142] In one specific embodiment, data from the same-direction device Read the device number and runtime, and combine them with the event's scope. Remove device numbers that are not located within the event's affected area;

[0143] The running times that consecutively satisfy the same sign of the state difference under the same equipment number are arranged to obtain the start and end times of consecutive values ​​in the same direction.

[0144] The range of state continuation is represented as:

[0145]

[0146] in, Number the event The corresponding state duration range, The starting time for continuously taking values ​​in the same direction. The end time of continuous, same-direction value taking values. The sign represents the state difference corresponding to consecutive values ​​in the same direction.

[0147] S124: Based on the state continuation range and trigger time, determine the start time and end time of the event impact, and generate the event impact window.

[0148] In one specific embodiment, the same event number is used. Read the overwrite trigger time from the state continuation range. Or related to the triggering time The start and end times of adjacent consecutive values ​​in the same direction;

[0149] The start time of the event's impact is represented as:

[0150]

[0151] The end time of the event's impact is indicated as follows:

[0152]

[0153] in, Number the event The corresponding event affects the start time. Number the event The corresponding event affects the end time.

[0154] If the state continuation range does not cover the trigger time, but the start time of the state continuation range and the trigger time are within the same sampling period, then the state continuation range will be included in the event impact window.

[0155] If the status duration ranges corresponding to multiple device numbers overlap, the event impact window for the same event number is determined according to the earliest start time and the latest end time.

[0156] If the status duration ranges corresponding to multiple device numbers do not overlap, then multiple event impact windows are generated respectively, while retaining the same event number.

[0157] The event impact window is displayed as follows:

[0158]

[0159] in, Number the event The corresponding event-affected window, The device number that falls into the event-affected window.

[0160] It should be noted that the generation of the event impact window does not depend on a fixed event duration, but is determined by the equipment operating status quantities before and after the triggering time and the operating time of continuous unidirectional values. This allows fire alarm events, energy consumption abnormal events, equipment failure events, or access abnormal events to generate event impact windows according to the same processing logic.

[0161] This module determines the event impact window by measuring the device operating status before and after the trigger time and the continuous unidirectional values, thus avoiding scheduling resources based on the fixed duration of the event, which could result in a window that is too short, too long, or inconsistent with the actual changes in the device.

[0162] Linkage matching module S13: Based on the event impact window and the availability status of control resources, it generates event resource matching results and event handling paths.

[0163] Specifically, the steps for generating event resource matching results and event handling paths are as follows:

[0164] S131: By matching the event's impact window and the availability of control resources, match the event's affected area, service area, and resource type to generate candidate resources for disposal.

[0165] In one specific implementation, from the event impact window Read the event number Area of ​​Event Scope The start time of the event's impact and the end of the event's impact ;

[0166] From managing resource availability status Read the controlled resource number Resource types Service Area Occupied Time Period and resource location .

[0167] The correspondence between resource type and event type is represented as follows:

[0168]

[0169] in, Number the event With controlled resource number The type corresponds to the determination result. Event type The corresponding callable resource type.

[0170] When the event applies to the area Service Area When both regions are represented by polygonal areas, the overlap value between the event's active region and the service region is calculated:

[0171]

[0172] in, Area of ​​influence of the event and service area The overlapping values ​​of the regions, This represents a function for calculating the area of ​​a region.

[0173] When the event's affected area and service area are represented by building number, floor number, or room number, if the numbers are the same, the overlapping area value is recorded as 1; if the numbers are different, the overlapping area value is recorded as 0.

[0174] Candidate disposal resources are represented as follows:

[0175]

[0176] in, Number the event Corresponding candidate disposal resources.

[0177] It should be noted that: Candidate disposal resources only indicate that the managed resource number meets the disposal conditions in terms of resource type and service area, and do not indicate that the managed resource number is in a callable state within the event impact window.

[0178] S132: Based on the candidate disposal resources and the event impact window, calculate the avoidance time between the occupied period and the event impact window, and generate the event resource matching result.

[0179] Specifically, the steps for generating event resource matching results are as follows:

[0180] S132.1: By reading the control resource number, resource type, service area and occupation time period through the candidate disposal resources, generate regional type matching resources.

[0181] In one specific embodiment, from candidate disposal resources The system reads the control resource number that meets the conditions of resource type correspondence and regional overlap, and retains the corresponding resource type, service area and occupation time period to generate regional type matching resources.

[0182] Region type matching resources are represented as:

[0183]

[0184] in, Number the event The corresponding region type matches the resources.

[0185] S132.2: Match resources and event impact windows according to region type, remove control resource numbers that overlap with the time period of occupation and event impact window, and generate callable resources.

[0186] Specifically, the steps to generate callable resources are as follows:

[0187] S132.2.1: Match resources by region type, read the controlled resource number, service area and time period, and generate the resource occupation range.

[0188] In one specific embodiment, resources are matched from region type. Read the controlled resource number Service Area and the time period occupied Generate the resource usage range.

[0189] The scope of resource usage is represented as follows:

[0190]

[0191] in, Number the event With controlled resource number The corresponding resource usage range.

[0192] If the controlled resource number is not occupied, the occupancy start time is... and the end time of occupation Record it as a null value.

[0193] S132.2.2: Calculate the time period overlap duration based on the event impact window and resource usage range, and generate the resource avoidance duration.

[0194] In a specific embodiment, when neither the start time nor the end time of occupation is null, the time period overlap duration is expressed as follows:

[0195]

[0196] in, Number the event With controlled resource number The corresponding time period overlap duration.

[0197] When the start and end times of occupation are empty values, the time period overlap duration is... The value is 0.

[0198] The duration of time period overlap will be used as the resource avoidance duration.

[0199]

[0200] in, Duration for resource avoidance.

[0201] It should be noted that a resource avoidance duration of 0 indicates that the period during which the controlled resource number is occupied does not overlap with the event impact window;

[0202] A resource avoidance duration of not 0 indicates that the controlled resource number is in conflict within the event's impact window.

[0203] S132.2.3: Based on the resource avoidance duration and resource occupation range, filter the control resource numbers with a time period overlap of zero, and generate callable resources.

[0204] In one specific embodiment, the following will be satisfied The management resource number is retained, which will meet the requirements. Remove the controlled resource number and generate a callable resource.

[0205] Callable resources are represented as:

[0206]

[0207] in, Number the event The corresponding callable resources.

[0208] S132.3: By using callable resources and event numbers, write the control resource number according to the start time of the event's impact to generate event resource matching results.

[0209] In one specific embodiment, the event number is... The start time of the event's impact When will the impact of the event end? Area of ​​Event Scope and the control resource number in the callable resources Write to the same matching unit to generate event resource matching results.

[0210] The event resource matching result is represented as follows:

[0211]

[0212] in, Number the event The corresponding event resource matching results.

[0213] It should be noted that when the same controlled resource number simultaneously meets the event resource matching results of multiple event numbers, the resource is rearranged in step S134 according to the resource arrival distance value and the event impact start time.

[0214] S133: Calculate the distance from the controlled resource number to the area affected by the event based on the event resource matching results and resource location, and generate the resource arrival distance value.

[0215] In one specific embodiment, resource location The location coordinates are represented using the spatial coordinate system of the park:

[0216]

[0217] in, and Numbering of managed resources plane coordinates, Numbering of managed resources Floor or height indicator.

[0218] Event Scope The coordinates of the region center are represented as:

[0219]

[0220] in, , and The coordinates are the center coordinates of the area affected by the event.

[0221] When the area affected by an event is represented by a polygonal region, the coordinates of the region's center are calculated using the average coordinates of the boundary points of the event's area.

[0222] When the area affected by the event is represented by building number, floor number, or room number, the coordinates of the center of the area are read from the park's spatial base map.

[0223] The distance from the controlled resource number to the area affected by the event is represented as follows:

[0224]

[0225] in, Numbering of managed resources To the area of ​​effect of the event The distance to reach, This is the floor conversion factor.

[0226] It should be noted that the floor conversion factor is... The range of values ​​was determined based on experimental data of floor-to-floor passage distances within the park. layer layer.

[0227] If the travel path distance is already recorded in the park's spatial base map, then the travel path distance from the resource location to the event's area of ​​effect is directly read as the resource arrival distance value.

[0228] S134: Based on the resource arrival distance value, the start time of the event impact, and the control resource number, rearrange the control resource numbers corresponding to the same event number to generate the event handling path.

[0229] In one specific embodiment, the same event number is used. Corresponding event resource matching results According to the resource reach distance value The values ​​are sorted in ascending order for the controlled resource numbers;

[0230] When two controlled resource numbers correspond to the same resource arrival distance value, they are arranged according to the idle start time of the controlled resource number in the available state of the controlled resource.

[0231] When the same controlled resource number is matched by multiple event numbers simultaneously, the order is determined by the start time of the event's impact. The event numbers are arranged in chronological order.

[0232] The incident handling path is represented as follows:

[0233]

[0234] in, Number the event The corresponding event handling path, The number is the control resource number arranged according to the order of disposal.

[0235] It should be noted that the event handling path record shows the order in which controlled resource numbers are invoked under the same event number;

[0236] When an event number matches only one managed resource number, the event handling path contains only one handling priority.

[0237] This module uses resource type, service area, time period, and distance to constrain resource matching, avoiding resource conflicts, unreasonable cross-region calls, or chaotic processing order caused by calling only by area or resource type.

[0238] Feedback Write-back Module S14: Generates event handling instructions based on the event handling path, collects event handling feedback corresponding to the event handling instructions, writes back the event impact window and the availability status of control resources based on the event handling feedback, and generates integrated park control results.

[0239] Specifically, the steps for generating integrated management and control results for the park are as follows:

[0240] S141: Read the event number, control resource number, and handling priority through the event handling path, and generate the handling instruction content.

[0241] In one specific embodiment, from the event handling path Read the event number Controlled resource number The disposal priority corresponding to the controlled resource number Generate disposal instructions.

[0242] The content of the disposal instruction is expressed as follows:

[0243]

[0244] in, Number the event Next The content of the disposal instructions corresponding to each disposal priority.

[0245] The instructions for handling the incident include the incident number, the controlled resource number, the priority of handling, and the area of ​​impact of the incident.

[0246] When the response action corresponding to the event type is already defined by the park's emergency response plan, the response action code will be written into the response instruction content.

[0247] S142: Based on the content of the handling instruction and the event impact window, calculate the handling time for the corresponding controlled resource number and generate the event handling instruction.

[0248] In one specific embodiment, the time of disposal is calculated by combining the start time of the event's impact, the order of disposal, and the interval between adjacent disposals.

[0249] The time of disposal is indicated as follows:

[0250]

[0251] in, Number the event Next The processing time corresponding to each processing priority. This represents the interval between adjacent treatments.

[0252] It should be noted that: the interval between adjacent treatments Determined based on the park's emergency response plan or historical sample experimental data corresponding to the event type;

[0253] When an event type requires multiple control resource numbers to arrive simultaneously, the handling time corresponding to multiple handling priorities is taken as the start time of the event's impact.

[0254] Incident handling instructions are expressed as follows:

[0255]

[0256] in, Number the event Next Each processing order corresponds to an event processing instruction.

[0257] S143: Issue the incident handling instruction to the corresponding controlled resource number, collect the arrival time, completion time and handling status, and generate incident handling feedback.

[0258] In one specific embodiment, the integrated management and control platform of the park will handle incident instructions. Issued to the corresponding controlled resource number ;

[0259] Controlled Resource Number The corresponding terminal device, mobile terminal, controller, or linkage subsystem returns the arrival time, completion time, and handling status.

[0260] The incident handling feedback is as follows:

[0261]

[0262] in, Number the event Next The incident handling feedback corresponds to each handling priority. For the arrival time, To complete the time, The status is under control.

[0263] The status of the handling includes completed, incomplete, and reassigned;

[0264] When the managed resource number is a device control type resource, the arrival time is the time when the event handling instruction is received by the corresponding controller, and the completion time is the time when the corresponding controller returns the action completion signal.

[0265] When the managed resource number is a personnel resource, the arrival time is the time when the personnel's mobile terminal enters the event's area of ​​effect, and the completion time is the time when the personnel's mobile terminal submits the completion result.

[0266] S144: Based on the event handling feedback, correct the event impact window and the availability of control resources, and generate a control write-back status.

[0267] In a specific embodiment, if the handling status in the event handling feedback If it is already completed, then the completion time will be recorded. With the end of the event's impact Compare;

[0268] The event window correction value is represented as:

[0269]

[0270] in, This is the correction value for the event window.

[0271] when When the event ends, update the event's impact time to the completion time;

[0272] when At that time, the end time of the event's impact is preserved.

[0273] If the handling status in the incident handling feedback is incomplete or transferred, the incident impact window will be retained, and the time period occupied by the corresponding control resource number in the control resource availability status will be extended to the completion time or transfer time.

[0274] The write-back status is indicated as follows:

[0275]

[0276] in, To control the write-back status, For the corrected event impact window, This indicates the corrected availability status of control resources.

[0277] It should be noted that the corrected event impact window retains the event number, the area affected by the event, the start time of the event impact, and the end time of the event impact.

[0278] The corrected availability status of controlled resources retains the controlled resource number, resource type, service area, updated occupancy period, and resource location.

[0279] S145: Based on the control write-back status, filter the completed event numbers and the control resource numbers that can be released, and generate the integrated control results for the park.

[0280] In one specific embodiment, the event number with the status of "completed" is read from the control write-back status, and the control resource numbers that have been written into the control resource availability status at the time of completion are filtered to generate the completed event number and the control resource number that can be released.

[0281] If all event handling feedbacks under the same event number show the handling status as completed, then the event number will be written as the completed event number.

[0282] If the time period corresponding to the same controlled resource number has reached its completion time, then the controlled resource number will be written as the releaseable controlled resource number.

[0283] The results of the integrated management and control of the park are expressed as follows:

[0284]

[0285] in, As a result of the integrated management and control of the park, Number the completed events. For the release of controlled resource IDs, For the corrected event impact window, This indicates the corrected availability status of control resources.

[0286] It should be noted that when the handling status in the incident handling feedback is incomplete or transferred, the park's integrated management and control platform will return to step S13 to regenerate the incident resource matching result and incident handling path based on the corrected incident impact window and the corrected management and control resource availability status.

[0287] When the handling status in the incident handling feedback is "completed", the park integrated management and control platform releases the corresponding management and control resource number and writes the corrected incident impact window and the corrected management and control resource availability status into the park integrated management and control results.

[0288] This module writes back the event impact window and manages the availability status of resources through event handling feedback, so that incomplete, transferred and completed states can trigger rematching, occupation extension or resource release respectively, forming a continuously updated integrated management and control closed loop for the park.

[0289] Example 2

[0290] Please see Figure 2 As shown, based on a unified inventive concept, this embodiment discloses an integrated management and control method for smart industrial parks based on the Internet of Things, the method comprising:

[0291] S21: Collect park event data, equipment operation data, and management resource status data, and generate event trigger status and management resource availability status;

[0292] S22: Generate an event impact window based on the event triggering status and device operating data;

[0293] S23: Based on the event impact window and the availability of control resources, generate event resource matching results and event handling paths;

[0294] S24: Generate event handling instructions based on the event handling path, collect event handling feedback corresponding to the event handling instructions, write back the event impact window and the availability status of control resources based on the event handling feedback, and generate integrated park control results.

[0295] The above embodiments are only used to illustrate the technical methods of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical methods of the present invention without departing from the spirit and scope of the technical methods of the present invention.

Claims

1. An integrated management and control system for smart industrial parks based on the Internet of Things, characterized in that, The system includes: Status generation module S11: Collects park event data, equipment operation data and management resource status data, and generates event trigger status and management resource availability status; Window generation module S12: Generates event-affected windows based on event triggering status and device operating data; Linkage matching module S13: Based on the event impact window and the availability status of control resources, it generates event resource matching results and event handling paths; Feedback Write-back Module S14: Generates event handling instructions based on the event handling path, collects event handling feedback corresponding to the event handling instructions, writes back the event impact window and the availability status of control resources based on the event handling feedback, and generates integrated park control results.

2. The integrated management and control system for smart industrial parks based on the Internet of Things as described in claim 1, characterized in that, The steps for generating event triggering states and managing resource availability states are as follows: S111: By reading the event number, event type, trigger time, and event area of ​​effect from the park event data, the event numbers are arranged according to the trigger time, and event time arrangement data is generated. S112: Based on the data arranged at the time of the event and the equipment operation data, match the equipment number and equipment operation status quantity within the area of ​​the event's effect, and generate the corresponding data for the event equipment; S113: Based on the data corresponding to the event device, calibrate the device operating status according to the event number and trigger time, and generate the event trigger status; S114: Based on the managed resource status data, break down the resource type, service area, occupation time period, and resource location to generate the managed resource availability status.

3. The integrated management and control system for smart industrial parks based on the Internet of Things as described in claim 2, characterized in that, The steps for generating data corresponding to the event device are as follows: S112.1: By reading the equipment number, equipment type, equipment location, and equipment operating status data from the equipment operation data, generate equipment space value data; S112.2: Based on the device space value data and the event's effective area, filter the device numbers located within the event's effective area and generate regional device data; S112.3: By arranging data based on regional device data and event time, read the device operating status data according to the trigger time, and generate corresponding data for the event device.

4. The integrated management and control system for smart industrial parks based on the Internet of Things as described in claim 3, characterized in that, The steps to generate an event-affected window are as follows: S121: Based on the event trigger status, read the event number, trigger time, event area, and corresponding event device data to generate event location data; S122: Based on the event location data, read the device operating status before and after the trigger time from the device operation data, and calculate the device status difference; S123: By filtering the device number and running time of consecutively unidirectional values ​​through the device status difference and the event's area of ​​effect, a status continuation range is generated; S124: Based on the state continuation range and trigger time, determine the start time and end time of the event impact, and generate the event impact window.

5. The integrated management and control system for smart industrial parks based on the Internet of Things as described in claim 4, characterized in that, The steps for generating the state continuation range are as follows: S123.1: By reading the difference symbol of the same device number at adjacent operating times through the device status difference, a status difference symbol is generated; S123.2: Based on the sign of the status difference, filter the device numbers with the same sign of the difference between adjacent running times and generate data of devices in the same direction; S123.3: By arranging the running times of consecutively oriented values ​​through the data and event scope of the same-direction devices, a state continuation range is generated.

6. The integrated management and control system for smart industrial parks based on the Internet of Things as described in claim 5, characterized in that, The steps to generate event resource matching results and event handling paths are as follows: S131: By matching the event's impact window and the availability of control resources, match the event's affected area, service area, and resource type to generate candidate resources for disposal; S132: Based on the candidate disposal resources and the event impact window, calculate the avoidance time between the occupied period and the event impact window, and generate the event resource matching result; S133: Calculate the distance from the controlled resource number to the area affected by the event based on the event resource matching results and resource location, and generate the resource arrival distance value; S134: Based on the resource arrival distance value, the start time of the event impact, and the control resource number, rearrange the control resource numbers corresponding to the same event number to generate the event handling path.

7. The integrated management and control system for smart industrial parks based on the Internet of Things as described in claim 6, characterized in that, The steps to generate event resource matching results are as follows: S132.1: By reading the control resource number, resource type, service area and occupation time period through the candidate disposal resources, generate regional type matching resources; S132.2: Match resources and event impact windows according to region type, remove control resource numbers that overlap with the time period of occupation and event impact window, and generate callable resources; S132.3: By using callable resources and event numbers, write the control resource number according to the start time of the event's impact to generate event resource matching results.

8. The integrated management and control system for smart industrial parks based on the Internet of Things as described in claim 7, characterized in that, The steps to generate callable resources are as follows: S132.2.1: Match resources by region type, read the controlled resource number, service area and occupation time period, and generate the resource occupation range; S132.2.2: Calculate the time period overlap duration and generate the resource avoidance duration based on the event impact window and resource usage range; S132.2.3: Based on the resource avoidance duration and resource occupation range, filter the control resource numbers with a time period overlap of zero, and generate callable resources.

9. The integrated management and control system for smart industrial parks based on the Internet of Things as described in claim 8, characterized in that, The steps to generate integrated management and control results for the park are as follows: S141: Read the event number, control resource number, and handling priority through the event handling path, and generate the handling instruction content; S142: Based on the content of the handling instruction and the event impact window, calculate the handling time for the corresponding controlled resource number and generate the event handling instruction; S143: Issue the incident handling instruction to the corresponding controlled resource number, collect the arrival time, completion time and handling status, and generate incident handling feedback; S144: Based on the event handling feedback, correct the event impact window and the availability of control resources, and generate a control write-back status; S145: Based on the control write-back status, filter the completed event numbers and the control resource numbers that can be released, and generate the integrated control results for the park.

10. A method for integrated management and control of smart industrial parks based on the Internet of Things (IoT), applied to the integrated management and control system for smart industrial parks based on the IoT as described in any one of claims 1-9, characterized in that, The method includes: S21: Collect park event data, equipment operation data, and management resource status data, and generate event trigger status and management resource availability status; S22: Generate an event impact window based on the event triggering status and device operating data; S23: Based on the event impact window and the availability of control resources, generate event resource matching results and event handling paths; S24: Generate event handling instructions based on the event handling path, collect event handling feedback corresponding to the event handling instructions, write back the event impact window and the availability status of control resources based on the event handling feedback, and generate integrated park control results.

Images