Hospital ward emergency lighting method and equipment based on power management and medium

Abstract

The invention discloses a hospital ward emergency lighting method and device based on power management and a medium, and relates to the technical field of emergency lighting, and the method comprises the steps: receiving and solidifying ward emergency lighting configuration parameters, generating a configuration version identifier, and constructing a baseline configuration packet containing lighting partitions and lamp control parameters; according to the executable strategy set and a corresponding strategy certificate, determining a target strategy, generating and issuing a control instruction, and outputting an execution read-back acquisition demand; and acquiring lamp read-back data and regional illumination feedback according to a read-back acquisition execution demand, performing time alignment, forming an alignment evidence record, writing back and updating the available energy estimation and credibility state of the power management context, and outputting an operation record attached with a configuration version identifier. According to the method, the predicted power consumption, the sustainable execution duration and the credibility state are subjected to unified judgment, so that the output strategy has verifiable performability under energy and duration constraints.

Description

Technical Field

[0001] This invention relates to the field of emergency lighting technology, and in particular to a method, equipment and medium for emergency lighting in hospital wards based on power management. Background Technology

[0002] Hospital ward emergency lighting technology is evolving from individual emergency lighting fixtures towards integration and networking, gradually forming a collaborative architecture with UPS / energy storage devices as the power supply core, lighting control equipment as the execution node, zoned illuminance detection as the feedback source, and operation and maintenance management terminal as the configuration and audit entry point. Differentiated illuminance is ensured through zoned start / stop and dimming control, and the standardized deployment and refined management of emergency lighting are supported by operation data recording and versioned configuration management.

[0003] In scenarios of power supply anomalies or switching, the main shortcomings of existing technologies are that emergency lighting strategies are usually triggered directly by fixed plans or single energy estimates, lacking quantitative characterization and constraints on the reliability of energy estimates. This makes it difficult to maintain verifiable consistency in strategy selection under conditions of acquisition noise, state drift, or reading jitter, and easily leads to problems such as repeated strategy switching or mismatch between the strategy and power supply capacity after execution, thereby weakening the determinism of emergency control. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a power management-based emergency lighting method for hospital wards to solve the problem that emergency lighting strategies are difficult to operate stably and verify execution due to insufficient reliability of energy estimation and lack of quantitative constraints in the event of power supply abnormalities.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] In a first aspect, the present invention provides a method for emergency lighting in hospital wards based on power management, which includes receiving and fixing emergency lighting configuration parameters for wards, generating a configuration version identifier, and constructing a baseline configuration package containing lighting zones and luminaire control parameters;

[0008] Continuously collect and integrate the ward's power supply and lighting status to generate a power management context that includes an estimate of available energy and a confidence level.

[0009] A candidate emergency lighting strategy library is generated based on the baseline configuration package. The executableness of each candidate strategy in the candidate emergency lighting strategy library is marked using the power management context, forming a strategy certificate library.

[0010] When a power supply anomaly or switching event is detected, a power supply capacity boundary is generated based on the current power management context, online access verification is performed on the policy certificate library, and a set of executable policies and corresponding policy certificates are output.

[0011] Based on the set of executable policies and the corresponding policy certificates, determine the target policy, generate and issue control commands, and output the execution readback collection requirements.

[0012] Based on the requirements for execution readback data collection, the system collects lamp readback data and area illuminance feedback, performs time alignment, forms an alignment evidence record, writes back and updates the available energy estimate and confidence status of the power management context, and outputs an operation record with a configuration version identifier.

[0013] As a preferred embodiment of the hospital ward emergency lighting method based on power management described in this invention, the specific steps for constructing a baseline configuration package containing lighting zones and luminaire control parameters are as follows:

[0014] Receive ward emergency lighting configuration parameters, which include lighting zone information, luminaire control parameters and target illuminance threshold;

[0015] The lighting zone information is processed by normalizing the zone boundary point sequence and prioritizing it to generate a zone geometric boundary description and determine the zone priority of each zone.

[0016] Based on the geometric boundary description of the zones and the corresponding zone priorities, combined with the target illuminance threshold, the minimum guaranteed illuminance and the maximum permissible illuminance of each lighting zone are determined.

[0017] By using the luminaire control parameters and the geometric boundary description of the zones, the luminaire zone affiliation is determined, the controllable luminaires are grouped, and the start / stop permissions and dimming step size constraints of each group are determined.

[0018] The system establishes and stores the association between the zonal geometric boundary description, minimum guaranteed illuminance and maximum allowable illuminance, start / stop permissions, dimming step size constraints, ward emergency lighting configuration parameters and configuration version identifier, and outputs a baseline configuration package.

[0019] As a preferred embodiment of the hospital ward emergency lighting method based on power management described in this invention, the specific steps for generating a power management context containing available energy estimates and confidence status are as follows:

[0020] Real-time data collection of power supply and lighting status; assessment of remaining available energy based on power supply status; and calculation of total power consumption of current lighting load based on lighting status.

[0021] Based on the total available energy reserves and total load power consumption, predict the duration of sustainable power supply, and use the duration of sustainable power supply and the corresponding remaining available energy as an estimate of available energy.

[0022] Assess the inter-source consistency of power supply status and the stability of lighting status readings, generate a quantified confidence status, and output a power management context that includes an estimate of available energy and the confidence status.

[0023] As a preferred embodiment of the hospital ward emergency lighting method based on power management described in this invention, the specific steps for generating the candidate emergency lighting strategy library are as follows:

[0024] Based on the lighting zone information and luminaire control parameters in the baseline configuration package, a preset degradation level set is constructed according to the zone priority, and a zone combination state set is generated.

[0025] Configure target dimming parameters and start / stop status for each zone combination state, and generate initial candidate strategy entries;

[0026] Perform illuminance compliance checks on the initial candidate policy entries based on the minimum guaranteed illuminance and the maximum permissible illuminance, and output the policy entries that pass the checks;

[0027] Based on dimming step size constraints and start / stop permissions, the feasibility of the validated strategy entries is controlled and trimmed to obtain a candidate emergency lighting strategy library.

[0028] As a preferred embodiment of the hospital ward emergency lighting method based on power management described in this invention, the specific steps for forming the strategy certificate library are as follows:

[0029] For each candidate emergency lighting strategy in the candidate emergency lighting strategy library, calculate the expected power consumption based on the start / stop status, target dimming parameters, and luminaire control parameters.

[0030] Based on the expected power consumption, the available energy estimate in the power management context is converted into a duration, and the sustainable execution duration of the candidate strategy is output.

[0031] Based on the minimum continuous lighting duration of emergency lighting in the ward emergency lighting configuration parameters, as a preset minimum duration threshold, candidate emergency lighting strategies whose continuous execution duration exceeds the minimum duration threshold are assigned an executability label;

[0032] The executability label, expected power consumption, sustainable execution duration, and trust status in the power management context are used as additional trust identifiers for policy certificates and associated with corresponding candidate policies, thus generating a policy certificate library.

[0033] As a preferred embodiment of the hospital ward emergency lighting method based on power management described in this invention, the specific steps for outputting the set of executable strategies and corresponding strategy certificates are as follows:

[0034] Based on the available energy estimate and real-time power supply status in the power management context, the remaining available energy and the expected continuous power supply duration are calculated. The confidence correction method is determined according to the confidence status, and the remaining available energy and the expected continuous power supply duration are corrected to generate a power supply capacity boundary that includes the corrected upper limit of energy and the corrected lower limit of duration.

[0035] The feasibility of the emergency lighting strategies in the strategy certificate library is determined by using the revised upper limit of energy and the revised lower limit of duration, and the set of executable strategies and their corresponding strategy certificates are selected.

[0036] As a preferred embodiment of the hospital ward emergency lighting method based on power management described in this invention, the specific steps of determining the target strategy, generating control commands and issuing them for execution, and outputting execution readback acquisition requirements are as follows.

[0037] Based on the expected power consumption, sustainable execution duration and additional trustworthiness identifier in the policy certificate, the executable policies are sorted by multiple objectives to determine the target policy. When there are multiple equivalent target policies, the policy with the lowest expected power consumption is selected as the target policy.

[0038] The target strategy is mapped to a set of control actions for each lighting fixture group, and control commands are generated and sent to the lighting control equipment to execute the target strategy.

[0039] Based on the additional trustworthiness identifier in the policy certificate corresponding to the target policy, the execution readback collection requirement is output.

[0040] As a preferred embodiment of the hospital ward emergency lighting method based on power management described in this invention, the specific steps for collecting and updating the luminaire readback data and regional illuminance feedback are as follows:

[0041] Based on the execution readback acquisition requirements corresponding to the target strategy, the actual current, actual voltage, and switch status of the specified lamps are collected to form lamp readback data; at the same time, the illuminance data of the lighting zones involved in the target strategy are collected to form area illuminance feedback.

[0042] Based on the time of issuance of control commands, the luminaire readback data and the area illuminance feedback are time-aligned to form an alignment evidence record;

[0043] Based on the aligned evidence records, the actual power consumption is calculated and the illuminance deviation is obtained, and the available energy estimate in the power management context is corrected.

[0044] Assess the consistency between luminaire readback data and area illuminance feedback, update the confidence status, associate the updated power management context with the configuration version identifier and store it, and output the operation log.

[0045] In a second aspect, the present invention provides a computer device including a memory and a processor, wherein the memory stores a computer program, wherein when the computer program is executed by the processor, it implements any step of the emergency lighting method for hospital wards based on power management as described in the first aspect of the present invention.

[0046] Thirdly, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein: when the computer program is executed by a processor, it implements any step of the emergency lighting method for hospital wards based on power management as described in the first aspect of the present invention.

[0047] The beneficial effects of this invention are as follows: When power supply anomalies or switching events occur, power supply capacity boundaries are generated based on the power management context, and online access verification is performed on the policy certificate library, so that the policy output in emergency situations has clear power supply constraint boundaries and maintains decision stability; at the same time, the expected power consumption, sustainable execution duration and credibility status are incorporated into the unified judgment, so that the output policy has verifiable executability under energy and duration constraints, and the screening process is solidified into a reproducible path, suppressing frequent policy switching caused by acquisition noise, state drift or reading jitter, reducing the risk of execution interruption, and improving the determinism and continuity of emergency lighting control. Attached Figure Description

[0048] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0049] Figure 1 This is a flowchart of a power management-based emergency lighting method for hospital wards.

[0050] Figure 2 A flowchart for creating a policy certificate library.

[0051] Figure 3 This is a flowchart for online access verification.

[0052] Figure 4 A flowchart for determining the target strategy. Detailed Implementation

[0053] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0054] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0055] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0056] Reference Figures 1-4 As one embodiment of the present invention, this embodiment provides a method for emergency lighting in hospital wards based on power management, comprising the following steps:

[0057] S1: Receive and solidify the ward emergency lighting configuration parameters, generate a configuration version identifier, and build a baseline configuration package containing lighting zone and luminaire control parameters.

[0058] S1.1: Receive ward emergency lighting configuration parameters, which include lighting zone information, luminaire control parameters and target illuminance threshold.

[0059] The configuration input interface is configured to receive ward emergency lighting configuration parameters, which include lighting zone information, luminaire control parameters, and target illuminance threshold.

[0060] Perform a field integrity check on the emergency lighting configuration parameters in the ward to determine if they are complete:

[0061] The configuration parameters for emergency lighting in the ward include lighting zone information, luminaire control parameters, and target illuminance threshold. The lighting zone information includes at least one lighting zone, and each lighting zone includes a zone identifier, zone priority, and a sequence of zone boundary points. The zone identifiers are unique.

[0062] The lighting control parameters include at least one lighting record. The lighting record includes the lighting fixture identifier, the coordinates of the lighting fixture installation location, the lighting fixture controllability indicator, start / stop permissions, dimming step size constraints, the lighting fixture control address, the lighting fixture rated power, and the lighting fixture controllability type (including switch type and dimming type). The lighting fixture identifier is unique.

[0063] All zone identifiers included in the target illuminance threshold are completely consistent with all zone identifiers included in the lighting zone information, and each zone identifier includes both the lower illuminance threshold and the upper illuminance threshold, and satisfies that the lower illuminance threshold is less than or equal to the upper illuminance threshold.

[0064] If any check fails, output the field integrity check failure result and end the receiving process.

[0065] Perform a format consistency check on the emergency lighting configuration parameters for the wards:

[0066] The sequence of boundary points in the lighting zone information can all be parsed into pairs of two-dimensional numerical coordinates. All zone boundary point sequences use the same separator and the same coordinate unit, and the coordinate unit is consistent with that of the luminaire installation location coordinates.

[0067] The lighting control addresses in the lighting control parameters are all non-empty numeric strings; the lighting installation location coordinates are two-dimensional numerical coordinate point pairs and the unit is meters; the rated power of the lighting fixture is a positive value and the unit is watts; the controllable type of the lighting fixture is a preset enumeration value; and the dimming step size constraint is an integer from 1 to 100.

[0068] Both the lower and upper limits of illuminance in the target illuminance threshold expression carry a unit string, and the unit string is lux.

[0069] If any rule of the format conformance check is not met, output a format conformance check failure result and end the receiving process.

[0070] The ward emergency lighting configuration parameters that have passed the field integrity check and format consistency check are written to the local persistent configuration storage location; the ward emergency lighting configuration parameters are serialized according to a fixed field order (lighting zone information, lamp control parameters and target illuminance threshold) and converted into a byte sequence according to UTF-8 encoding.

[0071] Perform SHA-256 digest calculation on the byte sequence to obtain a fixed-length digest value, and convert it into a fixed-length hexadecimal string as the configuration version identifier; establish and store an association record between the configuration version identifier and the ward emergency lighting configuration parameters, with the configuration version identifier as the index key of the association record.

[0072] S1.2: Perform normalization and priority sorting on the lighting zone boundary point sequence to generate a zone geometric boundary description and determine the zone priority corresponding to each zone.

[0073] Read the lighting zone information from the emergency lighting configuration parameters of the ward, perform zone boundary point sequence normalization on each zone record, add the first point to form a closed boundary when the first point and the last point are inconsistent, merge consecutive repeated points, delete redundant points that cause zero-length edges, and output the normalized zone boundary point sequence.

[0074] Perform a valid polygon check on the normalized partition boundary point sequence (example: at least 3 non-collinear vertices, area greater than 0, no self-intersections); if it fails, output a failure result and end the partition boundary processing flow.

[0075] The normalized point sequence is converted into a partitioned geometric boundary description by using closed polygon boundary representation, and the correspondence between partition identifier and partitioned geometric boundary description is established.

[0076] Read the partition priority, establish the correspondence between partition identifier and partition priority, use the correspondence as the partition priority of each partition, and generate a deterministic partition identifier sequence: sorted from high to low partition priority; when partition priorities are the same, if the partition identifier can be parsed as an integer, sorted in ascending numerical order; otherwise, sorted in ascending lexicographical order of the partition identifier string.

[0077] S1.3: Based on the geometric boundary description of the zone and the corresponding zone priority, combined with the target illuminance threshold, determine the minimum guaranteed illuminance and the maximum permissible illuminance for each lighting zone.

[0078] Read the target illuminance threshold from the emergency lighting configuration parameters of the ward, and read the lower illuminance threshold, upper illuminance threshold, zonal geometric boundary description and zonal priority line by zonal identifier.

[0079] The lower limit threshold for illuminance is determined as the minimum guaranteed illuminance, and the upper limit threshold for illuminance is determined as the maximum permissible illuminance.

[0080] The partition identifier, partition geometric boundary description, partition priority, minimum guaranteed illuminance, and maximum allowable illuminance are formed into a partition constraint record and written to the local persistent configuration storage location, and associated with the same record as the configuration version identifier.

[0081] It should be noted that the illuminance threshold is based on the working surface at a preset height above the ward floor (0.8m in the example). The illuminance threshold is configured by the hospital management terminal according to the emergency lighting management specifications (example: 15lx~100lx for the bed and patient activity area, 30lx~200lx for the bedside work area, and 5lx~30lx for the passage / entrance buffer zone inside the ward door). The illuminance threshold is fixed with the configuration version identifier.

[0082] S1.4: Using the luminaire control parameters and zone geometric boundary description, determine the luminaire zone affiliation relationship, group the controllable luminaires, and determine the start / stop permissions and dimming step size constraints of each group.

[0083] The luminaire control parameters are read from the ward emergency lighting configuration parameters. The luminaire control parameters include luminaire identification, luminaire installation location coordinates, luminaire controllability indicator, start / stop permissions, dimming step size constraints, luminaire control address, luminaire rated power and luminaire controllability type.

[0084] The coordinates of the lighting fixture installation location and the sequence of boundary points in the description of the zone geometry both use the same two-dimensional plane coordinate system (unit: meters).

[0085] For example: Configure boundary judgment tolerance (unit: meters) through the hospital management terminal and fix it with the configuration version identifier (example: 0.05 meters); perform judgment within the polygon for the installation position coordinates of each lamp:

[0086] When the coordinates of the luminaire's installation location are located within the closed area enclosed by the geometric boundary description of a certain lighting zone, it is determined that the luminaire's identification falls into the lighting zone corresponding to the lighting zone identification.

[0087] When the coordinates of the luminaire installation location are not located inside the closed area of ​​any lighting zone, calculate the minimum distance from the coordinates of the luminaire installation location to the geometric boundary description of each lighting zone.

[0088] When the minimum distance is not greater than the boundary judgment tolerance, the luminaire mark is determined to be located on the boundary line of the corresponding lighting zone, and the luminaire mark is regarded as falling into the lighting zone of the corresponding lighting zone mark.

[0089] When the installation location of a lighting fixture meets the criteria for multiple zones, the zone with the higher priority is selected first; if they are still the same, the zone with the earlier priority is selected based on the deterministic ranking of the zone identifier.

[0090] Based on the judgment result, a one-to-one correspondence between the lamp identifier and the zone identifier is generated as the lamp zone affiliation relationship; if any lamp is not mapped to a zone, the coverage check failure result is output and the process ends.

[0091] Lighting fixtures are selected as controllable based on their control parameters, and then grouped into controllable fixture sets according to their zone identifiers. Each controllable fixture set corresponding to a zone is defined as a controllable fixture group, and the group identifier adopts the zone identifier.

[0092] For each controllable lighting fixture group, the start / stop permission is taken as the most stringent restriction of the start / stop permission of the lighting fixtures in the group (prohibiting start / stop takes precedence over allowing start / stop), and the dimming step size constraint is taken as the maximum step size value of the dimming step size constraint of the lighting fixtures in the group (the larger the step size, the stricter the constraint).

[0093] Write the luminaire partition affiliation, controllable luminaire grouping, start / stop permissions, and dimming step size constraints to the local persistent configuration storage location, and establish the same record association with the configuration version identifier.

[0094] It should be noted that the dimming step size constraint is in percentage form, and the dimming parameter is allowed to be an integer from 0 to 100; the step size is an integer from 1 to 100, and the larger the step size, the stricter the constraint. The step size is preferably an integer that can be divided by 100; the start / stop permission is (allow start / stop, prohibit start / stop).

[0095] S1.5: Establish and store the association between the zonal geometric boundary description, minimum guaranteed illuminance and maximum allowable illuminance, start / stop permissions, dimming step size constraints, ward emergency lighting configuration parameters and configuration version identifier, and output the baseline configuration package.

[0096] The configuration version identifier is used as the main index, the ward emergency lighting configuration parameters are used as the original configuration segment, the zoning geometric boundary description, zoning priority, minimum guaranteed illuminance and maximum allowable illuminance are used as the zoning constraint segment, and the luminaire zoning affiliation, controllable luminaire grouping, group start and stop permissions, group dimming step size constraints, luminaire rated power and luminaire controllable type are used as the luminaire control segment. The baseline configuration package is then compiled and stored.

[0097] S2: Continuously collect and merge the ward's power supply status and lighting status to generate a power management context that includes an estimate of available energy and a confidence level.

[0098] S2.1: Real-time acquisition of power supply status and lighting status, assessment of remaining available energy using power supply status, and calculation of total load power consumption of current lighting using lighting status.

[0099] Set the data collection period to a fixed period, generate a data collection timestamp at the beginning of each data collection period, and synchronously collect the power supply status and lighting status at the corresponding time of the data collection timestamp.

[0100] The power supply status includes the power input status, the remaining capacity percentage of the energy storage device, the rated energy of the energy storage device, the output voltage and output current of the energy storage device, and carries the data collection timestamp.

[0101] The lighting status includes the on / off status and dimming percentage corresponding to each luminaire's identifier, along with a timestamp of the data collection.

[0102] The remaining available energy is calculated based on the power supply status. The rated power and controllable type of the luminaires are read from the baseline configuration package, and the current total load power consumption is calculated in combination with the lighting status.

[0103] The remaining usable energy is represented as:

[0104] ;

[0105] In the formula, Remaining available energy (unit: watt-hours). This represents the percentage of remaining capacity of the energy storage device. Rated energy of the energy storage device (unit: watt-hour).

[0106] The total load power consumption is expressed as:

[0107] ;

[0108] In the formula, This represents the current total load power consumption (in watts). For the first Rated power of a lamp (unit: watts). For lighting fixture index, This represents the power usage.

[0109] It should be noted that when the lamp is in the off state, the power consumption of the lamp is zero; when the lamp is a switch type and in the on state, the power consumption of the lamp is one; when the lamp is a dimming type and in the on state, the power consumption of the lamp is the ratio of the dimming percentage to 100; where the dimming percentage is an integer from 0 to 100.

[0110] S2.2: Based on the total available energy reserves and total load power consumption, predict the duration of sustainable power supply, and use the duration of sustainable power supply and the corresponding remaining available energy as an estimate of available energy.

[0111] The remaining available energy is used as the energy portion of the available energy estimate.

[0112] A low-power consumption determination is performed on the current total load power consumption by setting a preset low-power consumption threshold:

[0113] When the current total load power consumption is not greater than the low power consumption threshold, the continuous power supply duration will be set as the upper limit and the low power consumption flag will be recorded.

[0114] When the current total load power consumption is greater than the minimum power consumption threshold, the sustainable power supply duration is calculated based on the energy and power consumption conversion.

[0115] The duration of sustainable power supply is expressed as follows:

[0116] ;

[0117] In the formula, Duration of sustainable power supply (unit: hours).

[0118] The remaining available energy is combined with the duration of sustainable power supply to form an estimate of available energy.

[0119] It should be noted that the low power consumption threshold is set by the hospital management terminal during the configuration phase and is fixed with the configuration version identifier. When setting it, the total load power consumption sequence is continuously collected under the condition that no control commands are issued and the on / off status of the lamps and the dimming percentage remain unchanged. The upper limit of power consumption fluctuation is statistically analyzed and determined as the low power consumption threshold (the example value is an integer from 5W to 20W).

[0120] For example, when the upper limit of power consumption fluctuation is 6.8W, the low power consumption threshold is 7W; when the upper limit of power consumption fluctuation is 12.3W, it is 13W; in applications, integers from 5W to 20W can be used.

[0121] S2.3: Assess the inter-source consistency of power supply status and the stability of lighting status readings, generate a quantified confidence status, and output a power management context that includes an estimate of available energy and the confidence status.

[0122] The change in energy along the capacity path is obtained based on the change in remaining available energy between two adjacent acquisition cycles.

[0123] The energy change along the capacity path is expressed as:

[0124] ;

[0125] In the formula, This represents the change in energy along the capacity path (unit: watt-hours). The remaining available energy (in watt-hours) for the next acquisition cycle.

[0126] Based on the output voltage, output current and acquisition cycle length of this acquisition cycle, the energy output of the discharge path within the acquisition cycle is determined.

[0127] The energy output of the discharge path is expressed as:

[0128] ;

[0129] In the formula, Energy output through the discharge path (unit: watt-hour). This is the output voltage for this acquisition cycle. This is the output current for this acquisition cycle. This refers to the duration of the data collection cycle.

[0130] The energy closure difference is obtained by calculating the absolute value of the difference between the energy change in the capacity path and the energy output in the discharge path.

[0131] The energy closure difference is expressed as:

[0132] ;

[0133] In the formula, Energy closure difference (unit: watt-hour).

[0134] When no control command is issued and the lighting status remains unchanged, the system enters the stable statistics window. Within the stable statistics window, the energy closure difference is calculated once for each acquisition cycle and recorded in the order of acquisition timestamps to form an energy closure difference sequence. When the number of samples in the energy closure difference sequence is not less than the minimum number of statistical times (30 in the example), its fluctuation upper bound is calculated and determined as the energy closure tolerance.

[0135] When a control command is issued, a power supply abnormality occurs, or a switching event occurs, the stability statistics window ends, and the energy closure tolerance determined most recently remains unchanged.

[0136] The energy closure difference is compared with the energy closure tolerance to generate an inter-source consistency score for energy supply status; when a stable statistical window has not been formed or the sample is insufficient, the median score of the inter-source consistency score for energy supply status is taken.

[0137] The load change is obtained based on the change in total load power consumption between adjacent acquisition cycles.

[0138] Within a stable statistical window, load changes are recorded synchronously to form a load change sequence. The upper limit of fluctuation is statistically determined and defined as the load change tolerance. The load change tolerance is used as the basis for judging the range of small fluctuations.

[0139] When the load change remains within a small fluctuation range, the highest score is taken for the stability rating of the lighting status reading.

[0140] When the load change is within a small fluctuation range in one period and exceeds the small fluctuation range in another period, take the middle part.

[0141] When the load change continuously exceeds the small fluctuation range, a low score is taken; when the load change in the previous cycle does not exist, a medium score is taken; the credibility status is the lowest of the inter-source consistency score and the reading stability score; when the recorded low power consumption flag is true, the credibility status is downgraded by one level.

[0142] The power management context is formed by combining the data collection timestamp, available energy estimate, and credibility status and output. The power management context includes the data collection timestamp, remaining available energy, current total load power consumption, sustainable power supply duration, low power consumption flag, and credibility status, and is stored in association with the configuration version identifier.

[0143] S3: Generate a candidate emergency lighting strategy library based on the baseline configuration package, and use the power management context to mark the executability of each candidate strategy in the candidate emergency lighting strategy library to form a strategy certificate library.

[0144] S3.1: Based on the lighting zone information and luminaire control parameters in the baseline configuration package, construct a preset degradation level set according to the zone priority, and generate a zone combination state set.

[0145] Read the partition identifier, partition priority, and deterministic partition identifier sequence from the baseline configuration package.

[0146] A set of degrade levels is constructed according to the partition priority corresponding to the deterministic partition identifier sequence from high to low. Each degrade level corresponds to an enabled partition set and a disabled partition set.

[0147] The set of enabled partitions is formed by the union of the partition identifiers of the first few priority groups, and the set of disabled partitions is the difference between the set of all partition identifiers and the set of enabled partitions.

[0148] For each downgrade level, a partition combination status record is generated according to the deterministic partition identifier sequence. The partition combination status record includes the downgrade level identifier, the partition identifier, and the partition start / stop status. The partition combination status records of all downgrade levels are summarized to generate a partition combination status set.

[0149] S3.2: Configure target dimming parameters and start / stop status for each partition combination state, and generate initial candidate strategy entries.

[0150] For each partition combination state record in the partition combination state set, generate the partition target dimming parameters according to the partition start / stop state:

[0151] When the partition start / stop status is off, the partition target dimming parameter is zero;

[0152] When the zone's start / stop status is enabled, the zone's target dimming parameter takes the minimum allowable value within the permitted range of dimming parameter values, ensuring that the zone's expected illuminance meets the minimum guaranteed illuminance and does not exceed the maximum allowable illuminance. The zone's expected illuminance is determined based on the obtained data.

[0153] By reading the area illuminance feedback from the most recently stored operation record under the same configuration version identifier, and reading the current dimming percentage of the zone in the lighting status corresponding to the operation record; assuming that the illuminance changes monotonically with the dimming percentage,

[0154] The regional illuminance feedback is proportionally converted according to the target dimming percentage of the zone to obtain the zone's expected illuminance.

[0155] When the running record is missing, or the current dimming percentage of the partition is zero, making the proportional conversion unavailable, the expected illuminance of the partition is calculated from the partition full brightness illuminance baseline value according to the partition target dimming percentage;

[0156] The full-brightness reference value of the zone is collected during the installation and commissioning phase under the condition that all lamps are lit and the lighting status is stable, and is stored in association with the configuration version identifier.

[0157] When the full brightness illuminance baseline value of a zone is missing and the emergency strategy is not triggered, full brightness control is issued to the zone, and the illuminance feedback of the area is collected after the lighting status stabilizes. The collected results are written into the full brightness illuminance baseline value of the zone and stored in association with the configuration version identifier.

[0158] When the baseline value of full brightness illuminance for a zone is missing and the zone is in an emergency state and the baseline data collection conditions are not met, the expected illuminance for the zone is conservatively estimated based on the minimum guaranteed illuminance and the confidence level is downgraded by one level.

[0159] The partition identifier, partition start / stop status, and partition target dimming parameters corresponding to the same downgrade level identifier are summarized to form the initial candidate strategy entries.

[0160] S3.3: Perform illuminance compliance verification on the initial candidate strategy entries based on the minimum guaranteed illuminance and the maximum permissible illuminance, and output the strategy entries that pass the verification.

[0161] Based on the minimum guaranteed illuminance and maximum permissible illuminance in the partition constraint record, perform illuminance compliance verification on the enabled partitions in the initial candidate policy entries to confirm that the partition's expected illuminance is not lower than the minimum guaranteed illuminance and not higher than the maximum permissible illuminance; the partition's expected illuminance for the disabled partition is zero and it does not participate in the minimum guaranteed illuminance constraint.

[0162] The initial candidate policy entries that pass the illuminance compliance check are aggregated to form a set of policy entries that have passed the check.

[0163] S3.4: By controlling the feasibility of the validated strategy entries through dimming step size constraints and start / stop permissions, a candidate emergency lighting strategy library is obtained.

[0164] For policy entries that pass the verification, the partition actions are mapped to controllable lighting group actions according to the lighting luminaire partition affiliation relationship, so as to obtain the group start / stop status and group target dimming parameters of each controllable lighting luminaire group.

[0165] Lock the lighting status used for permission verification to the lighting status with the same acquisition timestamp as the power management context.

[0166] Perform start / stop permission verification for each controllable lighting fixture group: when the group's start / stop permission is prohibited, the start / stop permission verification is only passed if the group's start / stop status is consistent with the current lighting status; otherwise, the current policy entry is removed.

[0167] For policy entries that pass the start / stop permission verification, dimming step size constraint processing is performed to adjust the group target dimming parameters to the minimum allowable value that satisfies the group dimming step size constraint, and keep them within the allowable range of dimming parameter values.

[0168] The group start / stop status and the adjusted group dimming parameters are summarized to form candidate emergency lighting strategies, which are then compiled into a candidate emergency lighting strategy library and stored in association with the configuration version identifier.

[0169] S3.5: For each candidate emergency lighting strategy in the candidate emergency lighting strategy library, calculate the expected power consumption based on the start / stop status, target dimming parameters, and luminaire control parameters.

[0170] For each candidate emergency lighting strategy in the candidate emergency lighting strategy library, the luminaire identifiers are traversed by controllable luminaire group. The rated power and controllable type of the luminaire are read from the baseline configuration package. The expected power consumption of each luminaire is determined and summarized according to the group start / stop status and group dimming parameters of the candidate strategy to obtain the expected power consumption of the candidate strategy.

[0171] It should be noted that the expected power consumption is zero when the luminaire is in the off state; the expected power consumption is the rated power of the luminaire when the luminaire is in the on state and is a switch type; and the expected power consumption is determined by the rated power of the luminaire and the dimming percentage when the luminaire is in the on state and is a dimming type.

[0172] S3.6: Based on the expected power consumption, perform a duration conversion on the available energy estimate in the power management context and output the sustainable execution duration of the candidate strategy.

[0173] Read the remaining available energy in the power management context, and combine it with the expected power consumption of the candidate strategy to calculate the sustainable execution time of the candidate strategy.

[0174] When the expected power consumption of a candidate strategy is not positive, the duration of continuous execution of the candidate strategy is set to zero and the expected power consumption anomaly is recorded.

[0175] When the expected power consumption of a candidate strategy is not greater than the low power consumption threshold, the candidate strategy is determined to meet the low power consumption condition. The maximum duration of the candidate strategy can be taken as the duration, and the low power consumption condition is recorded in the corresponding strategy certificate.

[0176] When the expected power consumption of a candidate strategy is greater than the low power consumption threshold, the duration of sustainable execution of the candidate strategy is determined based on the conversion result.

[0177] S3.7: Based on the ward emergency lighting configuration parameters, a minimum duration threshold is preset, and candidate emergency lighting strategies whose continuous execution duration exceeds the minimum duration threshold are marked as executable.

[0178] Based on the ward emergency lighting configuration parameters, the minimum continuous lighting duration requirement for emergency lighting is read as the preset minimum duration threshold (example range: 30 minutes to 120 minutes), and the minimum continuous lighting duration requirement is permanently stored along with the configuration version identifier.

[0179] Read the duration of each candidate emergency lighting strategy and generate executability annotations:

[0180] If a candidate emergency lighting strategy can be executed for a duration not less than a preset minimum duration threshold, it is marked as executable.

[0181] If the duration of execution of a candidate emergency lighting strategy is less than the preset minimum duration threshold, the executability label is determined to be unexecutable.

[0182] For example, the minimum continuous lighting duration for emergency lighting in general wards is 60 minutes, and the minimum continuous lighting duration for emergency lighting in wards requiring emergency or treatment procedures is 90 minutes.

[0183] S3.8: Use the executability label, expected power consumption, sustainable execution duration, and trust status in the power management context as additional trust identifiers for the policy certificate and associate them with the corresponding candidate policies to generate a policy certificate library.

[0184] Candidate emergency lighting strategies are serialized according to a fixed field order and converted into byte sequences using UTF-8 encoding. The byte sequences are then subjected to SHA-256 digest calculation to obtain a fixed-length digest value, which is then converted into a fixed-length hexadecimal string as the candidate emergency lighting strategy identifier.

[0185] The fixed field order includes configuration version identifier, group identifier, lamp control address, start / stop action and dimming target value, and is arranged according to the group identifier order corresponding to the deterministic partition identifier sequence. The lamp control addresses within the group are ordered in ascending order of value.

[0186] Write the configuration version identifier, candidate emergency lighting strategy identifier, executability label, expected power consumption, sustainable execution duration, and trust status in the power management context into the strategy certificate, where the trust status serves as an additional trust identifier for the strategy certificate; aggregate all strategy certificates to form a strategy certificate repository, and store it in association with the configuration version identifier.

[0187] S4: When a power supply anomaly or switching event is detected, generate a power supply capacity boundary based on the current power management context, perform online access verification on the policy certificate library, and output an executable policy set and corresponding policy certificate.

[0188] S4.1: Based on the available energy estimate and real-time power supply status in the power management context, calculate the remaining available energy and the expected continuous power supply duration, and determine the confidence correction method according to the confidence status to perform confidence correction on the remaining available energy and the expected continuous power supply duration, generating a power supply capacity boundary that includes the corrected upper limit of energy and the corrected lower limit of duration.

[0189] When a power supply anomaly or switching event is detected, the power management context corresponding to the latest acquisition timestamp is read, the remaining available energy, the duration of sustainable power supply and the reliability status are extracted, and the energy closure difference corresponding to the acquisition timestamp is read.

[0190] Determine the confidence correction rule and generate the correction amount based on the confidence level:

[0191] When the confidence level is at its highest score, the correction is zero; when the confidence level is at its middle score, the energy correction is the maximum of the energy closure difference and the energy closure tolerance, and the duration correction is the duration of one acquisition cycle; when the confidence level is at its low score, the energy correction is the maximum of the energy closure difference and the energy closure tolerance of the two most recent acquisition cycles, and the duration correction is the duration of two acquisition cycles.

[0192] The corrected upper limit of energy is obtained by subtracting the energy correction amount from the remaining available energy, and the corrected lower limit of duration is obtained by subtracting the duration correction amount from the sustainable power supply duration; when the subtraction result is less than zero, it is taken as zero respectively.

[0193] The latest data collection timestamp, the corrected upper limit of energy, and the corrected lower limit of duration are combined to form a power supply capacity boundary record output.

[0194] S4.2: Use the revised upper limit of energy and the revised lower limit of duration to determine the feasibility of the policy certificates for each candidate emergency lighting policy in the policy certificate library, and select the set of executable policies and their corresponding policy certificates.

[0195] Read policy certificates one by one from the policy certificate library, and read the candidate emergency lighting policy identifier, executability label and expected power consumption.

[0196] When the executability flag is marked as non-executable, the policy certificate is deemed to have failed the online access verification.

[0197] If the expected power consumption is not positive, the policy certificate is deemed to have failed the online access verification.

[0198] For the remaining policy certificates, read the corrected upper limit of energy and the corrected lower limit of duration from the power supply capacity boundary.

[0199] The duration of continuous operation is calculated based on the revised energy limit and the expected power consumption to convert the power supply capacity boundary.

[0200] The duration of sustainable execution of the power supply capacity boundary is expressed as follows:

[0201] ;

[0202] In the formula, The duration of sustainable execution for the power supply capacity boundary. This is the revised energy limit. This represents the estimated power consumption.

[0203] When the expected power consumption is not greater than the low power consumption threshold, the duration of continuous execution of the power supply capability boundary is taken as the upper limit of the duration.

[0204] The sustainable execution time of the power supply capacity boundary is compared with the lower limit of the revised duration: when the sustainable execution time of the power supply capacity boundary is not less than the lower limit of the revised duration, the policy certificate is deemed to have passed the online access verification, and the corresponding candidate emergency lighting policy identifier is added to the executable policy set, and the policy certificate is added to the corresponding policy certificate set; otherwise, it is deemed to have failed.

[0205] After completing the traversal, output the set of executable policies and the corresponding set of policy certificates.

[0206] It should be noted that the feasibility determination simultaneously meets the following conditions: the executability of the strategy certificate is marked as executable, the expected power consumption is positive, and the boundary sustainable execution time calculated by converting the modified energy upper limit and the expected power consumption is not less than the modified duration lower limit.

[0207] S5: Based on the set of executable policies and the corresponding policy certificates, determine the target policy, generate and issue control commands, and output the execution readback collection requirements.

[0208] S5.1: Based on the expected power consumption, continuous execution duration, and additional trustworthiness identifier in the policy certificate, perform multi-objective ranking of executable policies to determine the target policy. When there are multiple equivalent target policies, select the policy with the lowest expected power consumption as the target policy.

[0209] Read the set of executable policies and the corresponding set of policy certificates, and establish a one-to-one correspondence between candidate emergency lighting policy identifiers and policy certificates.

[0210] Read the candidate emergency lighting strategy identifier for each executable strategy set, and read the sustainable execution duration, expected power consumption and trust status from the corresponding strategy certificate.

[0211] Use the credibility status as an additional credibility identifier; convert the additional credibility identifier into a credibility level value, with the highest score corresponding to 3, the medium score corresponding to 2, and the low score corresponding to 1.

[0212] Prioritize the candidate emergency lighting strategy with the longest sustainable execution time; when the sustainable execution time is the same, prioritize the candidate emergency lighting strategy with the higher confidence level value; when the confidence level value is still the same, select the candidate emergency lighting strategy with the lower expected power consumption.

[0213] When multiple equivalent candidate emergency lighting strategies are obtained according to the above sorting rules, the smallest one is selected as the target strategy in ascending lexicographical order of the candidate emergency lighting strategy identifiers, and the target strategy and its corresponding strategy certificate are output.

[0214] The target strategy is expressed as:

[0215] ;

[0216] In the formula, For the target strategy, For any candidate emergency lighting strategy in the set of executable strategies, Candidate emergency lighting strategies Sustainable execution duration, Candidate emergency lighting strategies The expected power consumption, Candidate emergency lighting strategies Credibility rating (dimensionless, highest score 3, medium score 2, low score 1).

[0217] S5.2: Map the target strategy to a set of control actions for each lighting fixture group, generate and issue control commands to the lighting control equipment to execute the target strategy.

[0218] A group control action record is generated for each group identifier. The group control action record includes the group identifier, the set of lamp control addresses, the start / stop action and the dimming target value. The start / stop action is determined by the group start / stop status and the dimming target value is determined by the group dimming parameters.

[0219] When the lighting control address can be resolved to a numerical value, it is arranged in ascending order of numerical value; when it cannot be resolved to a numerical value, it is arranged in ascending order of lexicographical order; all grouped control action records are summarized in a fixed order according to the group identifier to form a control action set.

[0220] Control commands are generated based on a set of control actions. Each control command includes at least a configuration version identifier, a candidate emergency lighting strategy identifier, a group identifier, a luminaire control address, a start / stop action, and a dimming target value. The control commands are then sent to the lighting control equipment for execution, and the time of command issuance is recorded.

[0221] S5.3: Output the readback collection requirements based on the additional trustworthiness identifier in the policy certificate corresponding to the target policy.

[0222] Read the additional trust identifier in the policy certificate corresponding to the target policy, and read the group identifier set and partition identifier set involved in the target policy.

[0223] Based on the baseline configuration package, read the luminaire identifier and luminaire control address corresponding to the group identifier to generate a luminaire readback collection list; generate a regional illuminance feedback collection list based on the partition identifier set.

[0224] Based on the additional confidence level, the data collection scope of the lighting fixture readback collection list is pruned, and the readback collection requirements are output:

[0225] When the additional credibility identifier is the highest score, only one lamp identifier is retained for each group identifier for readback. When the lamp identifier can be parsed into a numerical value, the smallest one is selected in ascending numerical order; when it cannot be parsed into a numerical value, the smallest one is selected in ascending lexicographical order.

[0226] When the additional credibility identifier is split in the middle, all lamp identifiers corresponding to the group identifier are retained for readback.

[0227] When the additional credibility score is low, all lamp identifiers corresponding to the group identifier are retained for readback.

[0228] The acquisition of luminaire readback data and the acquisition of area illuminance feedback data are performed within two consecutive acquisition cycles starting from the moment the self-control command is issued.

[0229] The final list of lamp readings and the list of area illuminance feedback collections are combined to form the execution reading and collection requirements.

[0230] The requirements for performing readback data acquisition include the luminaire readback data acquisition field and the area illuminance feedback acquisition field. The luminaire readback data acquisition field includes the actual voltage, actual current and switch status, while the area illuminance feedback acquisition field includes at least illuminance data.

[0231] S6: Based on the execution readback acquisition requirements, collect lamp readback data and area illuminance feedback, perform time alignment, form an alignment evidence record, write back and update the available energy estimate and confidence status of the power management context, and output an operation record with a configuration version identifier.

[0232] S6.1: Based on the execution readback acquisition requirements corresponding to the target strategy, collect the actual current, actual voltage and switching status of the specified lamps to form lamp readback data; at the same time, collect the illuminance data of the lighting zones involved in the target strategy to form regional illuminance feedback.

[0233] Based on the requirement of execution readback collection, the final list of lamp readback collection is extracted; a readback request is initiated for each lamp control address in the list, and the readback timestamp is recorded when the readback response arrives.

[0234] The actual voltage, actual current, and switch status are analyzed from the readback response to generate a luminaire readback data record.

[0235] The data log for luminaire readback should include at least the configuration version identifier, luminaire identifier, luminaire control address, readback timestamp, actual voltage, actual current, and switch status.

[0236] All lighting fixture readback data records are aggregated to generate a lighting fixture readback data set.

[0237] Based on the requirement of execution readback collection, extract the regional illuminance feedback collection list; initiate an illuminance collection request for each partition identifier in the list, and record the illuminance collection timestamp when the illuminance results are generated.

[0238] The zoning identifier, illuminance data, and illuminance collection timestamp are combined to generate regional illuminance feedback records; all regional illuminance feedback records are then aggregated to form a regional illuminance feedback set.

[0239] S6.2: Based on the time of issuance of the control command, the luminaire readback data and the area illuminance feedback are time-aligned to form an alignment evidence record.

[0240] The data set of lamp readback is evaluated one by one according to the time of the control command issuance: if the readback timestamp falls within the time alignment window calculated from the time of the control command issuance, it is recorded as alignment successful; otherwise, it is recorded as alignment failure.

[0241] Each illuminance feedback set in the area is evaluated: if the illuminance collection timestamp falls within the time alignment window calculated from the time the self-control command is issued, it is considered that the alignment is successful; otherwise, it is considered that the alignment is unsuccessful.

[0242] The time alignment window starts from the moment the control command is issued, and the window length is one acquisition cycle duration; the acquisition cycle duration is a fixed cycle length of the acquisition cycle and is fixed with the configuration version identifier.

[0243] The successfully aligned luminaire readback data records and the successfully aligned area illuminance feedback records are summarized at the same time the control command is issued to form an alignment evidence record.

[0244] The alignment evidence record includes the configuration version identifier, the candidate emergency lighting strategy identifier, the time when the control command was issued, the list of successfully aligned luminaire readback data records, and the list of successfully aligned area illuminance feedback records.

[0245] Furthermore, when the list of successfully aligned luminaire readback data records is empty or the list of successfully aligned area illuminance feedback records is empty, the alignment evidence record is marked as incomplete alignment.

[0246] S6.3: Based on the aligned evidence record, calculate the actual power consumption and obtain the illuminance deviation, and correct the available energy estimate in the power management context.

[0247] When the alignment evidence record is complete, calculate the current actual total load power consumption based on the list of successfully aligned lamp readback data records, and write the current actual total load power consumption into the alignment evidence record.

[0248] The current actual total load power consumption is expressed as:

[0249] ;

[0250] In the formula, This represents the current actual total load power consumption. To determine the number of readback records that were successfully aligned and included in the calculation, For the first The actual voltage recorded in the readback record. For the first The actual current of each readback record.

[0251] Read and align the evidence records to the corresponding collection timestamps in the power management context, and extract the remaining available energy.

[0252] The remaining available energy is used to calculate the updated sustainable power supply duration by converting it into the current actual total load power consumption. The remaining available energy and the updated sustainable power supply duration are then combined to generate an updated available energy estimate, which is written back to replace the available energy estimate in the power management context.

[0253] Based on the partition constraint records in the baseline configuration package, the minimum guaranteed illuminance and the maximum permissible illuminance are extracted; for each successfully aligned area illuminance feedback record, the illuminance data is compared with the minimum guaranteed illuminance and the maximum permissible illuminance, and illuminance deviation markers are generated and written into the alignment evidence record.

[0254] S6.4: Evaluate the consistency between luminaire readback data and area illuminance feedback, update the confidence status, associate the updated power management context with the configuration version identifier and store it, and output the operation record.

[0255] Read the set of partition identifiers corresponding to the target strategy, establish the correspondence between the lamp reading data records and the partition identifiers through the lamp partition affiliation relationship; merge them according to the partition identifier to form a partition lamp reading summary; merge the successfully aligned area illuminance feedback records according to the partition identifier to form a partition illuminance feedback summary.

[0256] For each partition identifier set corresponding to the target strategy, a consistency score is generated, with the consistency score limited to the highest, medium, and low scores:

[0257] When a partition identifier has both successfully aligned luminaire readback data records and successfully aligned area illuminance feedback records, and the illuminance deviation of the partition identifier is marked as meeting the partition constraints, the consistency score is the highest score.

[0258] When the partition identifier contains successfully aligned data and the illuminance deviation is marked as not meeting the partition constraints, or when the partition identifier lacks successfully aligned luminaire readback data records or lacks successfully aligned area illuminance feedback records, the consistency score is the median.

[0259] When both the successfully aligned luminaire readback data record and the successfully aligned area illuminance feedback record are missing from the partition identifier, the consistency score is lower.

[0260] The lowest consistency score among all partitions is taken as the consistency score for this run.

[0261] The credibility status in the power management context is updated to the lowest of the original credibility status and the consistency score. When the aligned evidence record is marked as incompletely aligned, if the updated credibility status is the highest score, it is downgraded to a medium score; if the updated credibility status is a medium score, it is downgraded to a low score; if the updated credibility status is a low score, it remains unchanged.

[0262] The updated power management context is associated with the configuration version identifier and stored. The configuration version identifier, candidate emergency lighting strategy identifier, control command issuance time, alignment evidence record and updated power management context are summarized to form the operation record output.

[0263] This embodiment also provides a computer device applicable to the emergency lighting method for hospital wards based on power management, comprising: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement the emergency lighting method for hospital wards based on power management as proposed in the above embodiment.

[0264] The computer device can be a terminal, comprising a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0265] This embodiment also provides a storage medium storing a computer program that, when executed by a processor, implements the method for implementing power management-based emergency lighting in hospital wards as proposed in the above embodiments. The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Red-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0266] In summary, this invention achieves the following: when power supply anomalies or switching events occur, it generates power supply capacity boundaries based on the power management context and performs online access verification on the policy certificate library, ensuring that policy outputs in emergency situations have clear power supply constraints and maintain decision stability; simultaneously, it incorporates expected power consumption, sustainable execution duration, and credibility status into a unified judgment, ensuring that the output policy has verifiable executability under energy and duration constraints, and solidifies the screening process into a reproducible path, suppressing frequent policy switching caused by acquisition noise, state drift, or reading jitter, reducing the risk of execution interruption, and improving the determinism and continuity of emergency lighting control.

[0267] It should be noted that the above embodiments are only used to illustrate the technical solutions 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 solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for emergency lighting in hospital wards based on power management, characterized in that: include, Receive and solidify the configuration parameters for emergency lighting in the ward, generate a configuration version identifier, and construct a baseline configuration package containing lighting zone and luminaire control parameters; Continuously collect and integrate the ward's power supply and lighting status to generate a power management context that includes an estimate of available energy and a confidence level. A candidate emergency lighting strategy library is generated based on the baseline configuration package. The executableness of each candidate strategy in the candidate emergency lighting strategy library is marked using the power management context, forming a strategy certificate library. When a power supply anomaly or switching event is detected, a power supply capacity boundary is generated based on the current power management context, online access verification is performed on the policy certificate library, and a set of executable policies and corresponding policy certificates are output. Based on the set of executable policies and the corresponding policy certificates, determine the target policy, generate and issue control commands, and output the execution readback collection requirements. Based on the requirements for execution readback data collection, the system collects lamp readback data and area illuminance feedback, performs time alignment, forms an alignment evidence record, writes back and updates the available energy estimate and confidence status of the power management context, and outputs an operation record with a configuration version identifier.

2. The emergency lighting method for hospital wards based on power management as described in claim 1, characterized in that: The specific steps for constructing the baseline configuration package, which includes lighting zones and luminaire control parameters, are as follows: Receive ward emergency lighting configuration parameters, which include lighting zone information, luminaire control parameters and target illuminance threshold; The lighting zone information is processed by normalizing the zone boundary point sequence and prioritizing it to generate a zone geometric boundary description and determine the zone priority of each zone. Based on the geometric boundary description of the zones and the corresponding zone priorities, combined with the target illuminance threshold, the minimum guaranteed illuminance and the maximum permissible illuminance of each lighting zone are determined. By using the luminaire control parameters and the geometric boundary description of the zones, the luminaire zone affiliation is determined, the controllable luminaires are grouped, and the start / stop permissions and dimming step size constraints of each group are determined. The system establishes and stores the association between the zonal geometric boundary description, minimum guaranteed illuminance and maximum allowable illuminance, start / stop permissions, dimming step size constraints, ward emergency lighting configuration parameters and configuration version identifier, and outputs a baseline configuration package.

3. The emergency lighting method for hospital wards based on power management as described in claim 1, characterized in that: The specific steps for generating the power management context, which includes an estimate of available energy and a confidence level, are as follows: Real-time data collection of power supply and lighting status; assessment of remaining available energy based on power supply status; and calculation of total power consumption of current lighting load based on lighting status. Based on the total available energy reserves and total load power consumption, predict the duration of sustainable power supply, and use the duration of sustainable power supply and the corresponding remaining available energy as an estimate of available energy. Assess the inter-source consistency of power supply status and the stability of lighting status readings, generate a quantified confidence status, and output a power management context that includes an estimate of available energy and the confidence status.

4. The emergency lighting method for hospital wards based on power management as described in claim 1, characterized in that: The specific steps for generating the candidate emergency lighting strategy library are as follows: Based on the lighting zone information and luminaire control parameters in the baseline configuration package, a preset degradation level set is constructed according to the zone priority, and a zone combination state set is generated. Configure target dimming parameters and start / stop status for each zone combination state, and generate initial candidate strategy entries; Perform illuminance compliance checks on the initial candidate policy entries based on the minimum guaranteed illuminance and the maximum permissible illuminance, and output the policy entries that pass the checks; Based on dimming step size constraints and start / stop permissions, the feasibility of the validated strategy entries is controlled and trimmed to obtain a candidate emergency lighting strategy library.

5. The emergency lighting method for hospital wards based on power management as described in claim 1, characterized in that: The specific steps for forming the policy certificate library are as follows: For each candidate emergency lighting strategy in the candidate emergency lighting strategy library, calculate the expected power consumption based on the start / stop status, target dimming parameters, and luminaire control parameters. Based on the expected power consumption, the available energy estimate in the power management context is converted into a duration, and the sustainable execution duration of the candidate strategy is output. Based on the minimum continuous lighting duration of emergency lighting in the ward emergency lighting configuration parameters, as a preset minimum duration threshold, candidate emergency lighting strategies whose continuous execution duration exceeds the minimum duration threshold are assigned an executability label; The executability label, expected power consumption, sustainable execution duration, and trust status in the power management context are used as additional trust identifiers for policy certificates and associated with corresponding candidate policies, thus generating a policy certificate library.

6. The emergency lighting method for hospital wards based on power management as described in claim 1, characterized in that: The specific steps for outputting the set of executable policies and corresponding policy certificates are as follows. Based on the available energy estimate and real-time power supply status in the power management context, the remaining available energy and the expected continuous power supply duration are calculated. The confidence correction method is determined according to the confidence status, and the remaining available energy and the expected continuous power supply duration are corrected to generate a power supply capacity boundary that includes the corrected upper limit of energy and the corrected lower limit of duration. The feasibility of the emergency lighting strategies in the strategy certificate library is determined by using the revised upper limit of energy and the revised lower limit of duration, and the set of executable strategies and their corresponding strategy certificates are selected.

7. The emergency lighting method for hospital wards based on power management as described in claim 1, characterized in that: The specific steps for determining the target strategy, generating control commands and issuing them for execution, and outputting the execution readback collection requirements are as follows. Based on the expected power consumption, sustainable execution duration and additional trustworthiness identifier in the policy certificate, the executable policies are sorted by multiple objectives to determine the target policy. When there are multiple equivalent target policies, the policy with the lowest expected power consumption is selected as the target policy. The target strategy is mapped to a set of control actions for each lighting fixture group, and control commands are generated and sent to the lighting control equipment to execute the target strategy. Based on the additional trustworthiness identifier in the policy certificate corresponding to the target policy, the execution readback collection requirement is output.

8. The emergency lighting method for hospital wards based on power management as described in claim 1, characterized in that: The specific steps for collecting and updating the luminaire data and regional illuminance feedback are as follows: Based on the execution readback acquisition requirements corresponding to the target strategy, the actual current, actual voltage, and switch status of the specified lamps are collected to form lamp readback data; at the same time, the illuminance data of the lighting zones involved in the target strategy are collected to form area illuminance feedback. Based on the timing of the control command issuance, the luminaire readback data and the area illuminance feedback are time-aligned. Form an aligned record of evidence; Based on the aligned evidence records, the actual power consumption is calculated and the illuminance deviation is obtained, and the available energy estimate in the power management context is corrected. Assess the consistency between luminaire readback data and area illuminance feedback, update the confidence status, associate the updated power management context with the configuration version identifier and store it, and output the operation log.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, it implements the steps of the emergency lighting method for hospital wards based on power management as described in any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by the processor, it implements the steps of the emergency lighting method for hospital wards based on power management as described in any one of claims 1 to 8.

Images