Java-based intelligent emergency cabinet integrated management system and method

Abstract

The present application relates to the technical field of intelligent management and control of Internet of Things devices and intelligent management and control of emergency supplies, in particular to a wisdom emergency cabinet integrated management system and method based on Java, comprising: a situation element collection module: input information from the emergency cabinet is acquired, and the input information is packaged as a situation element, wherein the situation element contains a source identifier, an information type and data payload; a comprehensive situation synthesis module: based on the situation element, a comprehensive situation describing the current operating condition of the emergency cabinet is generated; a dispatch module: according to the comprehensive situation, a disposal process chain is determined, wherein the disposal process chain is sequentially linked by at least one response node; by establishing a unified situation element and fusing and evaluating multi-source information based on the situation dimension, a comprehensive situation reflecting the composite risks of fire, water immersion and illegal intrusion can be generated.

Description

Technical Field

[0001] This invention relates to the field of intelligent management and control of IoT devices and intelligent management and control of emergency supplies, specifically to an integrated management system and method for a smart emergency cabinet based on Java. Background Technology

[0002] As intelligent emergency supply storage and retrieval nodes deployed in public places, the core value of smart emergency cabinets lies in realizing the transformation from passive storage to proactive response, and from isolated devices to networked services. However, existing systems mostly adopt a hard-coded model of specific sensors + fixed control logic. Each functional module (such as environmental monitoring, access control, and material management) is developed independently, and the data formats and interface protocols are not unified. When a new sensor is added or a new scenario is required, the code of multiple modules must be modified, integrated, and tested. The development cycle is long, and the system is difficult to quickly adapt to diverse deployment scenarios and business needs. Furthermore, the existing solutions have limitations in processing... Actions are often discrete; for example, an alarm may trigger the event and the event may be considered complete once a control command is sent. It is impossible to perceive whether the action was actually executed successfully (e.g., whether the lock was actually opened or the alarm message was delivered). Furthermore, it is impossible to dynamically trigger subsequent coordinated actions based on the outcome (e.g., starting a material retrieval timer after the door is opened or switching channels to retry after a message sending failure). There is a lack of effective coordination mechanisms between various hardware devices and business modules. When a certain step fails (e.g., a network interruption prevents the command from being issued or an actuator malfunctions), it is often only possible to record logs and wait for manual intervention, causing the entire emergency process to be interrupted and losing responsiveness at critical moments. Summary of the Invention

[0003] This invention addresses the technical problems existing in the prior art by providing an integrated management system and method for intelligent emergency cabinets based on Java.

[0004] The technical solution of this invention to solve the above-mentioned technical problems is as follows: A Java-based integrated management system for smart emergency cabinets, comprising: Situational data acquisition module: Acquires input information from the emergency cabinet and encapsulates the input information into situational data, which includes source identifier, information type and data payload; Comprehensive Situation Synthesis Module: Based on situational elements, it generates a comprehensive situational description of the current operating status of the emergency cabinet; Scheduling module: Based on the overall situation, determine a handling process chain, wherein the handling process chain is composed of at least one response node linked in sequence; Node execution module: Drives the response nodes in the handling process chain to perform handling actions. After the current response node performs the handling action, if output information is generated, the output information is encapsulated into a new situation element, and the operation of comprehensive situation generation is re-executed.

[0005] In a preferred embodiment, the situational awareness acquisition module acquires input information from different source components in the smart emergency cabinet through a preset data interface; The input information is encapsulated according to a predefined metadata structure to generate situational elements, which include: Source identifier, used to uniquely identify the source component that provides input information; Information type identifier, used to declare the predefined category to which the input information belongs; Data payload is used to carry the original content of input information or the content after preliminary transformation. The input information can be one or more of the following: Physical environmental parameter data collected by environmental sensors deployed on the smart emergency cabinet; Image or video data acquired by image acquisition devices deployed on smart emergency cabinets; Equipment status data fed back by the lock controller or door status detector of the smart emergency cabinet; Access requests or control commands sent from external user terminals to the smart emergency cabinet.

[0006] In a preferred embodiment, the integrated situation synthesis module assigns each situation element to a predefined situation dimension based on the source identifier and the information type identifier, wherein each predefined situation dimension corresponds to a specific combination of a set of source identifiers and information type identifiers; Acquire the data payloads of all situation elements belonging to the situation dimension. For each acquired data payload, compare the information type identifier with the preset threshold corresponding to the information type identifier based on the information type identifier of the situation element to which the data payload belongs. If the comparison result meets the predefined abnormal conditions, generate a preliminary state judgment indicating an abnormality; otherwise, generate a preliminary state judgment indicating normality. Based on the preliminary state determination of all data load levels within the situation dimension, and in accordance with the predetermined state merging rules within the situation dimension, a situation evaluation value representing the overall state level of the situation dimension is generated. The situation evaluation values ​​for each situation dimension are weighted and summed to obtain a weighted evaluation value. All weighted evaluation values ​​are summed to obtain a comprehensive evaluation value. Two preset comprehensive status thresholds are obtained, including a first threshold and a second threshold, wherein the first threshold is less than the second threshold. The comprehensive evaluation value is compared with the first threshold and the second threshold. If the comprehensive evaluation value is less than or equal to the first threshold, the overall operating status level is determined to be the first level. If the comprehensive evaluation value is greater than the first threshold and less than or equal to the second threshold, the overall operating status level is determined to be the second level. If the comprehensive evaluation value is greater than the second threshold, the overall operating status level is determined to be the third level. A comprehensive situation description containing the overall operating status level and situation evaluation values ​​of all situation dimensions is generated.

[0007] In a preferred embodiment, the scheduling module compares the situation evaluation value with a preset dimension threshold in each situation dimension included in the overall situation. If the situation evaluation value of the situation dimension is greater than or equal to the corresponding dimension threshold, the situation dimension is identified as a key dimension. Each identified key dimension is classified into a first type of key dimension or a second type of key dimension according to its predefined business attributes. The first key dimension indicates that if the situation assessment value exceeds the standard, it indicates the existence of direct physical risks related to environmental safety. The second key dimension is that when the situation assessment value exceeds the standard, it indicates that there is an anomaly related to equipment status, security control, or business processes. If the key dimension contains only the first type of key dimension, then the first handling process chain is determined; if the key dimension contains both the first type of key dimension and the second type of key dimension, then the second handling process chain is determined. If the key dimension only includes the second type of key dimension and the situation assessment value of the second type of key dimension reaches the preset specified level, then the third handling process chain is determined.

[0008] In a preferred embodiment, the node execution module sequentially drives each response node in the processing flow chain to execute its corresponding processing action, wherein the response node is a predefined functional unit for execution operations, and its execution action includes at least one of the following types: Send specific control commands to the hardware actuators of the emergency cabinet; Generate processing notifications or log information, and execute sending actions over the network to achieve information reporting; Update the status indicators representing the emergency cabinet and its related services; After the current response node performs a handling action, if the handling action produces explicit output information, then the following steps are executed: Based on the identity and operation type of the response node, a source identifier and an information type identifier are determined. The output information is used as the data payload and encapsulated together with the source identifier and information type identifier to generate a new situation element. The new situation element is used as input and returned to execute the operation of generating a comprehensive situation. If the current response node fails to execute the action, a situation element representing the failure is generated. Its data payload contains the reason for the failure. The failed situation element and other real-time situation elements are used as input to regenerate the comprehensive situation. Based on the regenerated comprehensive situation, an alternative action process chain is determined and executed. A Java-based integrated management system for smart emergency cabinets also includes a response node actuator cluster. The response node actuator cluster is connected to the scheduling module and the node execution module to execute response nodes in the handling process chain. The response node actuator cluster is deployed both locally on the emergency cabinet and in the cloud, while the response nodes used to control the emergency cabinet hardware are deployed locally.

[0009] The present invention also provides an integrated management method for a smart emergency cabinet based on Java, comprising the following steps: S1, acquiring input information from the emergency cabinet and encapsulating the input information into a situation element, wherein the situation element includes a source identifier, information type and data payload; S2. Based on the situational data, generate a comprehensive situational data describing the current operating status of the emergency cabinet; S3. Based on the overall situation, determine a response process chain, wherein the response process chain consists of at least one response node linked in sequence; S4. Drive the response nodes in the response process chain to perform response actions. After the current response node performs a response action, if output information is generated, the output information is encapsulated into a new situation element, and the operation of generating the comprehensive situation is re-executed. The beneficial effects of this invention are as follows: This invention transforms business logic into configuration information that can be dynamically loaded, enabling remote updates. When the system needs to add sensors, new emergency scenarios, or process optimization requirements, there is no need to modify the core code; only configuration adjustments are required for a rapid response, improving the system's business maintainability. By establishing a unified situational awareness element and fusing and evaluating multi-source information based on the situational awareness dimension, a comprehensive situational awareness reflecting the composite risks of fire, water immersion, and illegal intrusion can be generated. Furthermore, by matching the response process chain according to the situational awareness dimension, the execution effect of response actions can be perceived in real time. Combined with the design of automatically activating backup process chains when nodes fail, the high completion rate of the processing flow in complex environments is ensured. Attached Figure Description

[0010] Figure 1 This is a system block diagram of the present invention; Figure 2 This is a flowchart of the present invention. Detailed Implementation

[0011] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0012] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0013] In the description of this application, the term "for example" is used to mean "used as an example, illustration, or description." Any embodiment described as "for example" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use the invention. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that the invention can be made without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid obscuring the description of the invention with unnecessary detail. Therefore, the invention is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.

[0014] like Figure 1 This embodiment provides: a Java-based integrated management system for smart emergency cabinets, including: Situational data acquisition module: Acquires input information from the emergency cabinet and encapsulates the input information into situational data, which includes source identifier, information type and data payload; In this embodiment of the invention, the situation element acquisition module needs to be specifically described. The situation element acquisition module obtains input information from different source components in the smart emergency cabinet through a preset data interface. The input information is encapsulated according to a predefined metadata structure to generate situational elements, which include: Source identifier, used to uniquely identify the source component that provides input information; Information type identifier, used to declare the predefined category to which the input information belongs; Data payload is used to carry the original content of input information or the content after preliminary transformation. The input information can be one or more of the following: Physical environmental parameter data collected by environmental sensors deployed on the smart emergency cabinet; Image or video data acquired by image acquisition devices deployed on smart emergency cabinets; Equipment status data fed back by the lock controller or door status detector of the smart emergency cabinet; Access requests or control commands sent from external user terminals to the smart emergency cabinet.

[0015] It should be noted that the situational awareness module unifies and structures the various raw and heterogeneous data generated by the smart emergency cabinet. Through predefined interfaces or communication protocols, it acquires raw input information from various components of the smart emergency cabinet, performs encapsulation operations, and constructs each piece of input information into a standardized data structure, namely, a situational element. The encapsulation process adds specific metadata to the raw data. The source identifier uniquely identifies which physical device or logical component of the emergency cabinet the information originates from; the information type identifier declares the abstract category to which the data belongs (such as environmental parameters, image frames, status signals, control commands); and the data payload records the specific content of the raw information (such as temperature values). The data includes binary image data and door lock open / close status codes. Data collected by environmental sensors originates from various environmental sensors installed on the emergency cabinet, such as temperature, humidity, smoke, and water immersion sensors. The raw output values ​​(such as voltage, resistance, or digital codes) of these sensors are read periodically or event-triggered through the sensor interface. When encapsulated as a situational element, this data is assigned a source identifier indicating the specific physical location of the sensor, and an information type identifier declaring it as environmental monitoring data. The data payload contains the specific physical quantity values ​​after necessary conversions (such as analog-to-digital conversion and unit conversion). The data acquired by the image acquisition device and the lock characterization are also included. The data on cabinet door status corresponds to visual perception and equipment status perception, respectively. Unstructured image information and discrete status signals are incorporated into a unified situational awareness unit. For image data, image frames or video streams are acquired from image acquisition devices such as cameras integrated into the emergency cabinet. During encapsulation, the source identifier points to the specific camera device, the information type identifier indicates image data, and the data payload is compressed or encoded raw image binary data, or image feature descriptions containing timestamps. For lock or cabinet door status data, real-time status signals from components such as electric locks and magnetic door switches are acquired through digital input interfaces or specific status query protocols. During encapsulation, the source identifier is the specific actuator or sensor. The type identifier indicates that it is device status data, while the data payload records the specific status value. Request data from the user terminal represents the interaction intent between the external system or personnel and the emergency cabinet. It transforms various forms of user instructions or queries into standardized events that can be parsed and responded to internally. This type of data comes from operations initiated by users through mobile applications, management platform web pages, or field terminals, such as door opening authorization requests, material query requests, one-click alarm triggers, etc. These request data packets are received through network interfaces or local communication interfaces. When encapsulated into status elements, the source identifier is used to distinguish the identity of the request initiating terminal or user, the information type identifier is used to declare the business type of the request, and the data payload carries the specific parameters of the request.

[0016] Comprehensive Situation Synthesis Module: Based on situational elements, it generates a comprehensive situational description of the current operating status of the emergency cabinet; In this embodiment of the invention, the integrated situation synthesis module needs to be specifically described. For each situation element, the integrated situation synthesis module assigns the situation element to a predefined situation dimension based on the source identifier and the information type identifier. Each predefined situation dimension corresponds to a specific combination of a set of source identifiers and information type identifiers. Acquire the data payloads of all situation elements belonging to the situation dimension. For each acquired data payload, compare the information type identifier with the preset threshold corresponding to the information type identifier based on the information type identifier of the situation element to which the data payload belongs. If the comparison result meets the predefined abnormal conditions, generate a preliminary state judgment indicating an abnormality; otherwise, generate a preliminary state judgment indicating normality. Based on the preliminary state determination of all data load levels within the situation dimension, and in accordance with the predetermined state merging rules within the situation dimension, a situation evaluation value representing the overall state level of the situation dimension is generated. The situation evaluation values ​​for each situation dimension are weighted and summed to obtain a weighted evaluation value. All weighted evaluation values ​​are summed to obtain a comprehensive evaluation value. Two preset comprehensive status thresholds are obtained, including a first threshold and a second threshold, wherein the first threshold is less than the second threshold. The comprehensive evaluation value is compared with the first threshold and the second threshold. If the comprehensive evaluation value is less than or equal to the first threshold, the overall operating status level is determined to be the first level. If the comprehensive evaluation value is greater than the first threshold and less than or equal to the second threshold, the overall operating status level is determined to be the second level. If the comprehensive evaluation value is greater than the second threshold, the overall operating status level is determined to be the third level. A comprehensive situation description containing the overall operating status level and situation evaluation values ​​of all situation dimensions is generated.

[0017] The predefined situational dimensions are used to logically classify and group the generated discrete situational elements of different sources and types according to their business. Each situational dimension is defined by a specific combination of its corresponding source identifier and information type identifier. For example, the environmental safety dimension may specify that it only accepts situational elements with source identifiers such as temperature sensor 01, smoke sensor 01, etc., and type information identifiers such as temperature data and smoke concentration data. The predefined situational dimensions are based on the deployment scenarios of smart emergency cabinets, such as communities, campuses, and factories, and core functions such as the storage and retrieval of emergency supplies and security monitoring. It analyzes the core business status and potential risk points that need to be focused on. For example, it is found that continuous monitoring of fire risk, equipment failure risk, illegal intrusion risk, and material loss risk is required. The risk points and business status are abstracted into different situational dimensions, and each dimension is given a clear business name.

[0018] The predefined anomaly conditions are clearly defined under what circumstances a given data load should be judged as abnormal and under what circumstances it should be normal. Since the definitions of anomalies are very different for different information types (such as temperature, smoke concentration, and door lock status), the predefined anomaly conditions configure different judgment logics for different information types. The predefined anomaly conditions are pre-set for specific information types to determine whether the data load deviates from the normal or safe range. The predefined anomaly conditions can determine the normal operating range or state of each sensor device based on its technical specifications, industry safety standards, or product design requirements. For example, the safe upper limit of the cabinet temperature can be determined according to the fire extinguisher storage environment standard.

[0019] The preset comprehensive status threshold serves as a quantitative boundary for hierarchical decision-making, mapping the calculated continuous comprehensive evaluation values ​​to an overall operational status level with a clear business orientation. The first threshold and the second threshold define the critical points between different levels. The first threshold represents the critical point for transitioning from a normal state to a state of attention. When the comprehensive evaluation value is less than or equal to the first threshold, the overall operational status is determined to be at the first level, indicating that the weighted evaluation results of each dimension are within an acceptable ideal or safe range. The second threshold represents the critical point for escalating from the attention state to the alarm state. When the comprehensive evaluation value is greater than the second threshold, the overall operating status is judged to be level three, indicating that at least one or more key dimensions have experienced serious anomalies, and the weighted fusion has reached a risk level that requires immediate response. The preset comprehensive status threshold uses historical comprehensive value data, combined with historical actual events and handling records, to analyze which evaluation value ranges the system is actually in a stable operating state, which ranges begin to show minor anomalies but have not caused consequences, and which ranges are accompanied by real security events or serious failures.

[0020] It should be noted that the integrated situation synthesis module reads the source identifier and information type identifier contained within each situation element. Based on a predefined classification mapping relationship, and according to a specific combination of these two identifiers, the situation element is assigned to one or more predefined situation dimensions. These predefined situation dimensions are analytical perspectives or thematic categories abstracted from the emergency cabinet's business scenario, used to characterize its operational status from different angles. Examples include environmental safety dimensions and physical state dimensions. Each dimension clearly defines which sources and types of data it accepts. The data payload of each situation element assigned to a situation dimension is independently evaluated, and the situation is determined based on the situation to which the data payload belongs. The information type identifier of the element is identified, and the corresponding preset threshold is found. The value or state of the data payload is compared with the preset threshold to generate a preliminary state judgment for each data payload. The preliminary state judgments generated by all data payloads in the situation dimension are used as input and processed by the predetermined state merging rules in the situation dimension. The state merging rules define how to integrate discrete judgments into a whole conclusion. For example, if any abnormal judgment exists, the situation dimension evaluation value is high risk, or the risk level is calculated according to the proportion of abnormal judgments. The output risk level result is quantified into the situation evaluation value of the situation dimension. The situation evaluation value is a quantitative output that represents the current state level. A weighting factor is preset for each situation dimension, reflecting the relative importance of the situation dimension in the overall evaluation. The situation evaluation value of each dimension is multiplied by its corresponding weighting factor to obtain a weighted evaluation value. Then, the weighted evaluation values ​​of all dimensions are summed to obtain a comprehensive evaluation value. Two comprehensive status thresholds are preset. The obtained comprehensive evaluation value is compared with the comprehensive status thresholds sequentially. If the comprehensive evaluation value is less than or equal to the first threshold, the overall operating status level is determined to be Level 1, representing normal or low risk. If the comprehensive evaluation value is greater than the first threshold but less than or equal to the second threshold, it is determined to be Level 2, representing attention or medium risk. If the comprehensive evaluation value is greater than the second threshold, it is determined to be Level 3, representing alarm or high risk. Finally, a structured comprehensive situation description is generated. The comprehensive situation description includes the overall operating status level and the situation evaluation values ​​of each dimension. The comprehensive situation description expresses the current operating status of the emergency cabinet.

[0021] The weighted evaluation values ​​for all dimensions are summed, specifically including the following steps: Acquire the data payloads of all situation elements within the situation dimension and classify them according to the information type identifier. For each type of data payload, perform normalization processing. For numerical data, use maximum and minimum value normalization. The normalized value = (original value - preset minimum value) / (preset maximum value - preset minimum value). The result range is [0,1]. For state data, normal is mapped to 0 and abnormal is mapped to 1. For each type of normalized data, a preset weight factor is applied. The weight factor is preset according to the importance of the data in the dimensional evaluation, and the value range is [0,1]. The sum of the weight factors of all categories within the same dimension is 1. The weighted contribution value of the data of that type is calculated as: normalized value × weight factor of that type. The weighted contribution values ​​of all categories within the situation dimension are summed to obtain the original weighted sum of that situation dimension; The original weighted sum is mapped twice, and the original weighted sum is multiplied by a dimension scaling factor to obtain the final situation evaluation value of the situation dimension. The value range is [0,1], and the larger the value, the higher the degree of anomaly. After obtaining the final situation evaluation value for each situation dimension, a predefined weight factor needs to be configured for each dimension. The weight factor reflects the relative importance of the situation dimension in the overall evaluation. It is determined in advance by business rules, and the sum of the weight factors of all dimensions is 1. Then, the situation evaluation value of each dimension is multiplied by its corresponding weight factor to obtain the weighted evaluation value of that dimension. Then, the weighted evaluation values ​​of all dimensions are summed to calculate the comprehensive evaluation value. The value ranges from 0 to 1. The larger the value, the higher the overall abnormality. Then, the comprehensive evaluation value is compared with two preset thresholds. The first threshold is less than the second threshold. If the comprehensive evaluation value is less than or equal to the first threshold, the overall operating status level is determined to be Level 1 (normal). If the comprehensive evaluation value is greater than the first threshold and less than or equal to the second threshold, it is determined to be Level 2 (attention). If the comprehensive evaluation value is greater than the second threshold, it is determined to be Level 3 (alarm). Finally, a comprehensive situation description containing the comprehensive evaluation value, the overall operating status level, and the situation evaluation values ​​of all dimensions is generated. After obtaining the final situation evaluation value for each situation dimension, a predefined weight factor needs to be configured for each dimension. This weight factor reflects the relative importance of the dimension in the overall evaluation and is determined in advance by business rules. The sum of the weight factors of all dimensions is 1. The situation evaluation value of each dimension is multiplied by its corresponding weight factor to obtain the weighted evaluation value of that dimension. Then, the weighted evaluation values ​​of all dimensions are summed to calculate the comprehensive evaluation value. The value ranges from 0 to 1. The larger the value, the higher the overall abnormality. Subsequently, the comprehensive evaluation value is compared with two preset thresholds, where the first threshold is less than the second threshold. If the comprehensive evaluation value is less than or equal to the first threshold, the overall operating status level is determined to be Level 1 (normal). If the comprehensive evaluation value is greater than the first threshold and less than or equal to the second threshold, it is determined to be Level 2 (attention). If the comprehensive evaluation value is greater than the second threshold, it is determined to be Level 3 (alarm). A comprehensive situation description containing the comprehensive evaluation value, the overall operating status level, and the situation evaluation values ​​of all dimensions is generated.

[0022] Scheduling module: Based on the overall situation, determine a handling process chain, wherein the handling process chain is composed of at least one response node linked in sequence; In this embodiment of the invention, the scheduling module needs to be specifically described. For each situation dimension included in the comprehensive situation, the scheduling module compares the situation evaluation value with the preset dimension threshold in the situation dimension. If the situation evaluation value of the situation dimension is greater than or equal to the corresponding dimension threshold, the situation dimension is identified as a key dimension. Each identified key dimension is classified into a first type of key dimension or a second type of key dimension according to its predefined business attributes. The first key dimension indicates that if the situation assessment value exceeds the standard, it indicates the existence of direct physical risks related to environmental safety. The second key dimension is that when the situation assessment value exceeds the standard, it indicates that there is an anomaly related to equipment status, security control, or business processes. If the key dimension contains only the first type of key dimension, then the first handling process chain is determined; if the key dimension contains both the first type of key dimension and the second type of key dimension, then the second handling process chain is determined. If the key dimension only includes the second type of key dimension and the situation assessment value of the second type of key dimension reaches the preset specified level, then the third handling process chain is determined.

[0023] Based on a comprehensive situational awareness reflecting the overall status of the emergency cabinet, the scheduling module intelligently selects and determines a targeted automated response plan. It matches a handling process chain to the currently identified operational status. This handling process chain is a predefined sequence of operations linked together by multiple response nodes in a specific logical order. Each node encapsulates an operation (such as controlling specific hardware or sending a notification). It reads the evaluation values ​​of various status dimensions contained in the comprehensive situational awareness. These evaluation values ​​quantify the current status level of each dimension (such as environmental safety and equipment status). The evaluation values ​​are then judged to identify dimensions with abnormal status, prominent risks, or requiring priority attention, and these are marked as critical dimensions. Preset conditions are pre-defined rules used to define what evaluation value characteristics constitute criticality; for example, an evaluation value exceeding a preset risk level for that dimension... The system identifies risk thresholds, rankings among the top N in all dimensions, or values ​​that have been continuously deteriorating recently. Based on the types of all key dimensions (e.g., environmental safety or physical intrusion) and their specific evaluation values, this information is used as input to apply process chain selection logic. This logic is a pre-configured set of decision rules or mapping tables that defines the correspondence between different combinations of key dimension types and their evaluation value ranges and different handling process chains. For example, if the key dimension is only environmental safety and its evaluation value falls within the high-temperature warning range, then the ventilation and high-temperature warning process chain is activated. If the key dimension includes both environmental safety (smoke alarm) and equipment status (abnormal door opening), then the fire emergency linkage and security alarm process chain is activated.

[0024] After identifying the set of key dimensions, the situation assessment value of each key dimension is first binarized by comparing it with a preset high threshold. If the situation assessment value is greater than or equal to the threshold, it is judged as high risk; otherwise, it is considered medium risk or ignored according to preset rules. Based on the type combination and risk level of the key dimensions, matching is performed according to the predefined rule priority order. Each rule contains a conditional expression and a corresponding handling process chain identifier. For example, if there is an environmental safety dimension with a high risk level, a fire emergency linkage chain is matched; if there is only an equipment status dimension with a high risk, an equipment fault alarm chain is matched; if there are both environmental safety and equipment status dimensions with high risk, a composite anomaly handling chain is matched. The rules are checked one by one according to priority order, and the handling process chain corresponding to the first rule that meets the conditions is selected as the current process chain to be executed. If no rule matches, the recording and notification chain is selected as the fallback solution by default.

[0025] Node execution module: Drives the response nodes in the handling process chain to perform handling actions. After the current response node performs the handling action, if output information is generated, the output information is encapsulated into a new situation element, and the operation of comprehensive situation generation is re-executed. In this embodiment of the invention, the node execution module needs to be specifically described. The node execution module drives each response node in the processing flow chain to execute the corresponding processing action in sequence. The response node is a predefined functional unit for execution operations, and its execution action includes at least one of the following types: Send specific control commands to the hardware actuators of the emergency cabinet; Generate processing notifications or log information, and execute sending actions over the network to achieve information reporting; Update the status indicators representing the emergency cabinet and its related services; After the current response node performs a handling action, if the handling action produces explicit output information, then the following steps are executed: Based on the identity and operation type of the response node, a source identifier and an information type identifier are determined. The output information is used as the data payload and encapsulated together with the source identifier and information type identifier to generate a new situation element. The new situation element is used as input and returned to execute the operation of generating a comprehensive situation. If the current response node fails to execute a handling action, a situational element representing the failure is generated. Its data payload includes the reason for the failure. The failed situational element is used as input along with other real-time situational elements, and a comprehensive situation is regenerated. Based on the regenerated comprehensive situation, a backup handling procedure chain is determined and executed.

[0026] Each response node in the node execution module is a single-function execution unit. When a node finishes execution, its result is encapsulated into a new situation element. The new situation element is then returned to the input of the integrated situation operation, triggering a new round of situation synthesis, evaluation, and decision-making. Response nodes generate specific control commands through composite hardware communication protocols (e.g., sending unlocking pulses to electric locks, sending start information to audible and visual alarms). Nodes that generate and send messages execute sending actions through hardware interfaces, directly changing the physical state of the emergency cabinet. Nodes that generate and send information generate structured early warning, notification, or log information (e.g., SMS, APP push, platform alarms) and execute sending actions through the communication network to achieve information reporting and personnel reach. Nodes that call data processing trigger a preset data processing algorithm (e.g., using image analysis to confirm whether personnel have left, performing secondary analysis of historical sensor data). The output of nodes that call data processing is processed state variables or database records (e.g., changing the emergency cabinet status from in use to idle, deducting the quantity of material inventory) to maintain consistency between the internal state of the system and the actual situation. After the current response node performs its action, if it generates output information (e.g., confirmation receipt of control command sent, message delivery receipt, new results from data processing, or new values ​​of status identifiers after modification), the system will immediately initiate an encapsulation process. This process combines the output information with source identifiers and information type identifiers that identify the response node and its operation type to construct a new situational element. This new situational element carries information about the action performed and its results. This new situational element, along with other real-time data that may exist in the system, is then returned as input for a new situational synthesis and evaluation operation. This may drive the system to determine the next action chain (e.g., the material retrieval monitoring process after successful door opening, or the process after message transmission failure). The retry process involves the following steps: When a failure is detected in the current response node (e.g., hardware unresponsiveness, network interruption, data processing anomaly), the system generates a situational element representing the failure. Its data payload includes the specific reason for the failure (e.g., network timeout, device offline). Based on all situational elements at this moment (including new failure information), a comprehensive situation is regenerated. This comprehensive situation reflects the new condition that a certain action is blocked. Based on the updated situation, the system redefines a new action chain. This new action chain is a predefined backup action chain for the specific scenario of action failure. Its goal may be to try alternative solutions, report higher-level faults, or perform a safe recovery operation. Finally, the system executes this backup action chain.

[0027] A Java-based integrated management system for smart emergency cabinets also includes a response node actuator cluster. The response node actuator cluster is connected to the scheduling module and the node execution module to execute response nodes in the handling process chain. The response node actuator cluster is deployed both locally on the emergency cabinet and in the cloud, while the response nodes used to control the emergency cabinet hardware are deployed locally.

[0028] After the current response node completes its action and generates clear output information, it first organizes the output information according to a predefined data structure, such as using key-value pairs to record the execution result, success status, return code, or specific data. Then, it determines the source identifier for the newly generated situation element. This identifier is fixed as a unique identifier for the current response node, such as LOCK_CONTROL_NODE or MESSAGE_SEND_NODE. At the same time, based on the nature of the output information, it selects an appropriate information type identifier from a predefined set of types, such as EXEC_RESULT for execution result, DATA_PROCESSED for processed data, and STATE_CHANGED for state change. The source identifier, information type identifier, and organized data payload are combined to form a complete new situation element. This situation element will serve as the input for the subsequent step S2 and participate in a new round of situation synthesis. When a failure to execute a response action is detected at the current response node, a situation element representing the failure is first generated. The data payload records the reasons for the failure in detail, such as hardware unresponsiveness, network timeout, or data format error. The failed situation element is added to the current situation element set. A new comprehensive situation is generated based on all the updated situation elements. Due to the addition of the failed situation element, the evaluation values ​​of the relevant situation dimensions will change accordingly. For example, the evaluation value of the device status dimension may increase due to the failure. Based on the new comprehensive situation, a response process chain is determined again according to the same process chain selection logic as before. Since the situation has changed, the matched process chain may be different from the previous failed process chain, thus obtaining a backup response process chain. If the newly matched process chain is exactly the same as the process chain before the failure, in order to avoid infinite loop, the system will forcibly select a preset fallback process chain (such as "manual takeover chain") and then switch to executing the fallback or backup process chain. It should be noted that the preset threshold of the present invention is obtained by collecting multiple sets of sample data by those skilled in the art and setting a corresponding preset ratio coefficient for each set of sample data; substituting the set preset ratio coefficient and the collected sample data into the formula, any two formulas constitute a system of two first equations, and the calculated coefficients are filtered and averaged to obtain the value. The size of the coefficient is a specific value obtained by quantifying each parameter to facilitate subsequent comparison. The size of the coefficient depends on the amount of sample data and the preset proportional coefficient initially set by those skilled in the art for each set of sample data; as long as it does not affect the proportional relationship between the parameter and the quantified value.

[0029] like Figure 2 This implementation also provides a Java-based integrated management method for smart emergency cabinets, including the following steps: S1, obtaining input information from the emergency cabinet and encapsulating the input information into a situation element, wherein the situation element includes a source identifier, information type, and data payload; S2. Based on the situational data, generate a comprehensive situational data describing the current operating status of the emergency cabinet; S3. Based on the overall situation, determine a response process chain, wherein the response process chain consists of at least one response node linked in sequence; S4. Drive the response nodes in the response process chain to perform response actions. After the current response node performs a response action, if output information is generated, the output information is encapsulated into a new situation element, and the operation of generating the comprehensive situation is re-executed.

[0030] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0031] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

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

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

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

[0036] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A Java-based integrated management system for smart emergency cabinets, characterized in that, include: Situational data acquisition module: Acquires input information from the emergency cabinet and encapsulates the input information into situational data, which includes source identifier, information type and data payload; Comprehensive Situation Synthesis Module: Based on situational elements, it generates a comprehensive situational description of the current operating status of the emergency cabinet; Scheduling module: Based on the overall situation, determine a handling process chain, wherein the handling process chain is composed of at least one response node linked in sequence; Node execution module: Drives the response nodes in the handling process chain to perform handling actions. After the current response node performs the handling action, if output information is generated, the output information is encapsulated into a new situation element, and the operation of comprehensive situation generation is re-executed.

2. The integrated management system for a Java-based smart emergency cabinet according to claim 1, characterized in that, The situational awareness acquisition module obtains input information from different source components in the smart emergency cabinet through a preset data interface; The input information is encapsulated according to a predefined metadata structure to generate situational elements, which include: Source identifier, used to uniquely identify the source component that provides input information; Information type identifier, used to declare the predefined category to which the input information belongs; Data payload is used to carry the original content of input information or the content after preliminary transformation. The input information can be one or more of the following: Physical environmental parameter data collected by environmental sensors deployed on the smart emergency cabinet; Image or video data acquired by image acquisition devices deployed on smart emergency cabinets; Equipment status data fed back by the lock controller or door status detector of the smart emergency cabinet; Access requests or control commands sent from external user terminals to the smart emergency cabinet.

3. The integrated management system for a Java-based smart emergency cabinet according to claim 1, characterized in that, For each situation element, the integrated situation synthesis module assigns the situation element to a predefined situation dimension based on the source identifier and information type identifier. Each predefined situation dimension corresponds to a specific combination of a set of source identifiers and information type identifiers. Acquire the data payloads of all situation elements belonging to the situation dimension. For each acquired data payload, compare the information type identifier with the preset threshold corresponding to the information type identifier based on the information type identifier of the situation element to which the data payload belongs. If the comparison result meets the predefined abnormal conditions, a preliminary state judgment indicating an abnormality is generated; otherwise, a preliminary state judgment indicating normality is generated.

4. The integrated management system for a Java-based smart emergency cabinet according to claim 3, characterized in that, Based on the preliminary state determination of all data load levels within the situation dimension, and in accordance with the predetermined state merging rules within the situation dimension, a situation evaluation value representing the overall state level of the situation dimension is generated. The situation evaluation values ​​for each situation dimension are weighted and summed to obtain a weighted evaluation value. All weighted evaluation values ​​are summed to obtain a comprehensive evaluation value. Two preset comprehensive status thresholds are obtained, including a first threshold and a second threshold, wherein the first threshold is less than the second threshold. The comprehensive evaluation value is compared with the first threshold and the second threshold. If the comprehensive evaluation value is less than or equal to the first threshold, the overall operating status level is determined to be the first level. If the comprehensive evaluation value is greater than the first threshold and less than or equal to the second threshold, the overall operating status level is determined to be the second level. If the comprehensive evaluation value is greater than the second threshold, the overall operating status level is determined to be the third level. A comprehensive situation description containing the overall operating status level and situation evaluation values ​​of all situation dimensions is generated.

5. The integrated management system for a Java-based smart emergency cabinet according to claim 1, characterized in that, For each situation dimension included in the comprehensive situation, the scheduling module compares the situation evaluation value with the preset dimension threshold in the situation dimension. If the situation evaluation value of the situation dimension is greater than or equal to the corresponding dimension threshold, the situation dimension is identified as a key dimension. Each identified key dimension is classified into a first type of key dimension or a second type of key dimension according to its predefined business attributes. The first key dimension indicates that if the situation assessment value exceeds the standard, it indicates the existence of direct physical risks related to environmental safety. The second key dimension indicates an anomaly related to equipment status, security control, or business processes when the situation assessment value exceeds the standard.

6. The integrated management system for a Java-based smart emergency cabinet according to claim 5, characterized in that, If the key dimension contains only the first type of key dimension, then the first handling process chain is determined; if the key dimension contains both the first type of key dimension and the second type of key dimension, then the second handling process chain is determined. If the key dimension only includes the second type of key dimension and the situation assessment value of the second type of key dimension reaches the preset specified level, then the third handling process chain is determined.

7. The integrated management system for a Java-based intelligent emergency cabinet according to claim 1, characterized in that, The node execution module sequentially drives each response node in the processing flow chain to execute its corresponding processing action. A response node is a predefined functional unit for execution operations, and its execution actions include at least one of the following types: Send specific control commands to the hardware actuators of the emergency cabinet; Generate processing notifications or log information, and execute sending actions over the network to achieve information reporting; Update the status identifiers representing the emergency cabinet and its related services.

8. The integrated management system for a Java-based smart emergency cabinet according to claim 7, characterized in that, After the current response node performs a handling action, if the handling action produces explicit output information, then the following steps are executed: Based on the identity and operation type of the response node, a source identifier and an information type identifier are determined. The output information is used as the data payload and encapsulated together with the source identifier and information type identifier to generate a new situation element. The new situation element is used as input and returned to execute the operation of generating a comprehensive situation. If the current response node fails to execute a handling action, a situational element representing the failure is generated. Its data payload includes the reason for the failure. The failed situational element is used as input along with other real-time situational elements, and a comprehensive situation is regenerated. Based on the regenerated comprehensive situation, a backup handling procedure chain is determined and executed.

9. The integrated management system for a Java-based intelligent emergency cabinet according to claim 1, characterized in that, The system also includes a response node executor cluster, which is connected to the scheduling module and the node execution module to execute response nodes in the handling process chain. The response node executor cluster is deployed locally on the emergency cabinet and in the cloud, and the response nodes used to control the emergency cabinet hardware are deployed locally.

10. A Java-based integrated management method for smart emergency cabinets is applied to the Java-based integrated management system for smart emergency cabinets as described in any one of claims 1-9, characterized in that, Includes the following steps: S1. Obtain input information from the emergency cabinet and encapsulate the input information into a situational element, wherein the situational element includes source identifier, information type and data payload; S2. Based on the situational data, generate a comprehensive situational data describing the current operating status of the emergency cabinet; S3. Based on the overall situation, determine a response process chain, wherein the response process chain consists of at least one response node linked in sequence; S4. Drive the response nodes in the response process chain to perform response actions. After the current response node performs a response action, if output information is generated, the output information is encapsulated into a new situation element, and the operation of generating the comprehensive situation is re-executed.

Images