A multi-channel remote lighting control system

Abstract

This invention discloses a multi-channel remote lighting control system, relating to the field of lighting control technology in the preservation of cultural relics and archives. In this invention, lighting is first recorded as pending execution within the authorized time period, and then an execution confirmation frame is used to determine if execution has been successful. Simultaneously, the remaining exposure time is limited by the minimum of the daily cumulative exposure value, weekly cumulative exposure value, and single cumulative exposure value, and the actual execution time is limited by the smaller of the current remaining exposure time and the hold time. Lighting, holding, and exiting are all controlled by both authorization and exposure constraints, compressing unplanned exposure into authorized time periods with remaining allowance. When a cancellation frame arrives, authorization expires, hold time expires, exposure is exhausted, or the prohibition flag becomes valid, the system directly exits to a safe rollback scenario, preventing the lights from remaining in the previous state.

Description

Technical Field

[0001] This invention relates to the field of lighting control technology in the preservation environment of cultural relics and archives, and in particular to a multi-channel remote lighting control system. Background Technology

[0002] Lighting control in artifact display cases and archives differs from that in ordinary buildings. These scenarios require remote lighting, scene switching, and brightness adjustment during inspection, inventory, maintenance, and display. Simultaneously, it's necessary to control the duration of illumination and cumulative exposure of the artifacts within a specific statistical period. For paper, textiles, photographs, and pigments, whether lighting is implemented, for how long it is maintained, and when it is removed all directly impact the actual exposure process.

[0003] In existing technologies, common remote lighting control methods mainly include network control based on cloud platforms or mobile terminals, and remote control based on wired buses and gateways. These methods typically use remotely issued lighting or scene commands directly as the basis for execution, or superimpose on-site triggering information as supplementary conditions in addition to the remote commands. However, in the low-light, enclosed, and low-frequency operating environments of artifact display cases and archives, whether remote lighting should be implemented depends not only on the command itself, but also on whether the on-site operation is valid, the cumulative exposure status of the target object, and the current remaining lighting duration. Existing control methods lack a unified approach to these constraints, easily leading to situations where remote commands are delivered but not suitable for execution, the duration of execution becomes uncontrollable, or the timing of exit is unclear.

[0004] On the other hand, existing remote control processes often focus on command delivery itself, neglecting the continuous correspondence between authorization establishment, execution maintenance, expiration exit, and status recording. When remote control links switch, commands arrive repeatedly, or command cancellation overlaps with the execution status, situations can easily arise where lights remain in the previous state, exit actions are not completed in a timely manner, and control records do not match the actual light status. Once these situations occur, they not only increase the risk of unplanned exposure but also make it difficult to accurately pinpoint the specific target, time, and execution process during post-event verification.

[0005] Therefore, how to ensure that remote lighting is simultaneously constrained by authorization conditions, exposure conditions, and remote control confirmation in low-light lighting scenarios such as artifact display cases or archives, and how to form a continuous control closed loop that can be exited, recorded, and verified during the execution process, has become a technical problem that needs to be solved. Summary of the Invention

[0006] This application provides a multi-channel remote lighting control system to solve the problem of difficulty in achieving closed-loop consistency between authorization, exposure, and remote control status in low-illuminance lighting of cultural relic display cases or archives.

[0007] This invention provides a multi-channel remote lighting control system, including a remote management terminal, a first remote communication channel and a second remote communication channel that are independent of each other, a near-field confirmation channel, a local lighting controller, and a light source driving unit; The remote management terminal generates an authorized lighting record that includes at least a target identifier, scene code, brightness limit, authorized time period, duration, execution sequence number and operator identifier. The record is sent to the local lighting controller via the first remote communication channel. The second remote communication channel sends at least one of a confirmation frame and a cancellation frame corresponding to the authorized lighting record. The near-field confirmation channel sends a field confirmation frame. At least one of the confirmation frame and the field confirmation frame serves as the execution confirmation frame. The local lighting controller stores a scene code table, an exposure constraint table, and an execution log table. The exposure constraint table stores the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, the corresponding remaining exposure time, and the prohibition flag according to the target identifier. After receiving the authorized lighting record within the authorized time period, the local lighting controller generates a record to be executed. When the record to be executed and the execution confirmation frame meet the requirements of the target identifier and execution sequence number and the prohibition execution flag is invalid, the minimum value of the remaining exposure time corresponding to each statistical caliber is used as the current remaining exposure time. The lighting control command with a brightness limit not exceeding the scene code table is generated according to the scene code table. The light source driving unit is controlled to execute the lighting control command according to the execution time corresponding to the smaller value between the current remaining exposure time and the holding time. During execution, the local lighting controller updates the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, and current remaining exposure time according to the sampling time slice. When it receives a cancellation frame, the hold time expires, the authorized time period expires, the current remaining exposure time is reduced to zero, or the prohibition execution flag becomes valid, it outputs the lighting control command corresponding to the safety rollback scenario, writes the status flag of the corresponding execution sequence number and the termination reason into the execution log table, and sends a status receipt to the remote management terminal.

[0008] In some embodiments, the first remote communication path includes a first communication interface and a first gateway, and the second remote communication path includes a second communication interface and a second gateway, wherein the second communication interface and the second gateway are respectively set independently of the first communication interface and the first gateway. The local lighting controller associates the authorized lighting record, the confirmation frame, and the revocation frame with the execution sequence number and writes them into the execution log table.

[0009] In some embodiments, the scene code table pre-stores low-light display scenes, inspection scenes, maintenance scenes, inventory scenes, and safety rollback scenes corresponding to the target display case or target storage location, and stores the target channel, target brightness value, and transition duration for each scene code; the local lighting controller reads the corresponding control item according to the scene code and generates the lighting control instruction.

[0010] In some embodiments, the local lighting controller establishes a pending state, an executing state, and a terminated state for each execution sequence number; When an execution confirmation frame matching the record to be executed is received, the corresponding record is changed from the pending execution state to the executing state; When at least one of the confirmation frame, the on-site confirmation frame, and the cancellation frame with the same execution sequence number is received again, only the path source or end marker in the execution log table is updated, and the light control command is not output repeatedly.

[0011] In some embodiments, the near-field confirmation path includes a credential reading unit located near the target display case or target storage location, and the credential reading unit is connected to the local lighting controller; After the voucher reading unit reads the on-site voucher, it generates the on-site confirmation frame. The local lighting controller verifies the on-site voucher identifier in the on-site confirmation frame against the operator identifier in the authorized lighting record. If the verification matches, the record to be executed remains valid. If the verification does not match, the lighting control command corresponding to the safe rollback scenario is output and written to the execution log table.

[0012] In some embodiments, the scene code table stores an entry segment and an exit segment corresponding to each scene code; When the local lighting controller transitions from the pending state to the executing state, it outputs the lighting control instruction according to the entry segment of the corresponding scene code; when it receives the cancellation frame, the hold duration expires, the authorized time period expires, or the current remaining exposure time is reduced to zero, it outputs the lighting control instruction corresponding to the safe rollback scene according to the exit segment of the corresponding scene code.

[0013] In some embodiments, the local lighting controller generates a start receipt frame and an end receipt frame when entering the execution state and the end state, respectively; Both the start receipt frame and the end receipt frame include at least a target identifier, execution sequence number, current scene code, and status flag. The local lighting controller prioritizes sending the start receipt frame and the end receipt frame through the remote communication channel where the most recently received confirmation frame or cancellation frame is located. When the current execution sequence number only receives a field confirmation frame, it is sent through a preset default remote communication channel. If the sending fails, it is sent through the other remote communication channel.

[0014] In some embodiments, the local operation inputs generated by the local operation input unit include at least scene switching input, brightness adjustment input, emergency rollback input, and end input; The local lighting controller establishes a record item for the local operation input, which includes the input category, input time, target identifier, corresponding scene code and processing result, and writes the record item into the execution log table; When the local operation input is an emergency rollback input or an end input, the lighting control command corresponding to the safe rollback scenario is immediately output, and the current execution sequence number is switched to the end state.

[0015] In some embodiments, when the local operation input is a scene switching input or a brightness adjustment input and there is currently an execution state, the local lighting controller will retain the local operation input until the current execution sequence number ends before processing; When there is no current execution state, when the execution prohibition mark is invalid and the current remaining exposure time is greater than zero, the corresponding light control command is output according to the local operation input; for multiple local operation inputs generated consecutively within the preset queuing time window for the same target identifier, the latest input of the same type is retained as a valid input according to the input time order, and the processing result corresponding to the earlier input is updated to the queuing failure mark and then written to the execution log table.

[0016] In some embodiments, after each execution sequence number ends, the local lighting controller updates the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, and their respective remaining exposure time in the exposure constraint table according to the actual brightness value and the actual execution duration, and writes the update result into the execution log table in association with the execution sequence number.

[0017] Through the above technical solution, the present invention can achieve at least the following beneficial effects: This invention integrates authorized lighting records, independently configured first and second remote communication channels, near-field confirmation, exposure constraint table, execution duration limit, expiration exit, status receipt, and execution log table into a single control chain. Light activation is no longer directly triggered by detecting a person, terminal, or a single remote command. Instead, an execution record is first created within the authorized time period, and an execution confirmation frame confirms successful execution. Simultaneously, the remaining exposure time is limited by the minimum of the remaining exposure time corresponding to the daily cumulative exposure value, weekly cumulative exposure value, and single cumulative exposure value. The actual execution time is limited by the smaller of the current remaining exposure time and the hold time. This process ensures that lighting, hold, and exit are jointly controlled by authorization and exposure constraints, compressing unplanned exposure into authorized time periods with remaining allowance. When a cancellation frame arrives, authorization expires, hold time expires, exposure is exhausted, or the prohibition flag becomes valid, the system directly exits to a safe rollback scenario, preventing the lights from remaining in the previous state.

[0018] The independent first and second remote communication paths ensure that authorized lighting records, confirmations, and revocation controls no longer rely entirely on a single path. After the local lighting controller associates the path source of authorized lighting records, confirmation frames, and revocation frames with the execution sequence number in the execution log table, both the remote and local sides can trace back the control chain source by execution sequence number. This way, even in the event of gateway switching, single-path jitter, or duplicate transmissions, it is still possible to distinguish which path the authorization originated from, which path the confirmation originated from, and which path triggered the revocation. This allows for a direct correlation between actual light status changes and control sources, reducing situations where logs record changes but cannot explain why the light status changed.

[0019] An exposure constraint table established based on target identifiers extends exposure control from static thresholds to continuous constraints during execution. Instead of simply determining whether to allow lighting before execution, the system accumulates actual brightness values ​​and durations based on sampling time slices during execution to form exposure increments, and simultaneously updates daily, weekly, and single-time cumulative exposure values, as well as the current remaining exposure time. Therefore, when actual brightness increases, execution time lengthens, or previous exposures approach the limit, the system triggers exit conditions earlier; when the current remaining exposure time decreases to zero, the system immediately exits to a safe rollback scenario. This process ensures that exposure constraints are no longer merely a post-event verification measure but directly participate in in-process control, making it suitable for situations where paper, textiles, photographs, and pigment artifacts are more sensitive to cumulative illumination.

[0020] Near-field confirmation, state switching, entry and exit segments, status feedback, and local operation input processing further integrate on-site operations and remote control into a unified closed loop. After on-site credential identification and operator identification are verified, execution confirmation corresponds to on-site personnel, preventing erroneous activation in cases of absence or inconsistent credentials. The pending, in-process, and ended states ensure that repeated confirmations and cancellations only update records without repeatedly outputting control commands, reducing frequent switching. The entry and exit segments ensure that scene switching and rollback actions are executed according to predetermined control segments, reducing abrupt output during operation interruptions. Status feedback returns the start, end, and results of execution to the remote management terminal, allowing the remote side to verify whether commands were truly executed and when exit was initiated. Local operation input in the in-process state is processed after completion or immediately rolled back, preventing remote control and on-site control from overlapping. Overall, the system forms a continuous closed loop encompassing authorization establishment, execution confirmation, exposure restriction, expiration exit, remote feedback, and local logging. Attached Figure Description

[0021] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation on the scope of this application.

[0022] Figure 1 This is a framework diagram of a multi-channel remote lighting control system in one embodiment. Detailed Implementation

[0023] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0024] All terms used in this application (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0025] Furthermore, the relevant terms and concepts involved in this embodiment will be introduced below: A remote management terminal refers to a computing device used to generate authorized lighting records and send remote control data; a first remote communication path refers to a first communication link used to transmit authorized lighting records; a second remote communication path refers to a second communication link used to transmit confirmation frames and cancellation frames; a near-field confirmation path refers to a short-range communication link used to transmit on-site confirmation frames near the target display case or target storage location; a local lighting controller refers to a control device used to perform authorization judgment, exposure judgment, state switching, and lighting control output; a light source drive unit refers to a drive device used to drive the target light source according to lighting control instructions; a target identifier refers to a data identifier used to uniquely identify the target display case or target storage location; and a scene code refers to a data code used to uniquely indicate a set of preset lighting control items.

[0026] The local operation input unit refers to the input component used to receive on-site scene switching input, brightness adjustment input, emergency rollback input, and end input.

[0027] Authorized lighting records refer to data records generated by remote management terminals around a single target identifier and used to constrain the execution process of a single lighting event. Authorized time periods refer to the time interval during which authorized lighting records are allowed to enter the execution judgment process; authorized time periods include the authorization start time and authorization end time. Hold duration refers to the duration for which the current scene code output is maintained after the local lighting controller switches the corresponding record to the execution state. Execution sequence number refers to a unique sequence identifier used to identify the execution process of a single lighting event and establish a correspondence between authorized lighting records, confirmation frames, cancellation frames, on-site confirmation frames, start receipt frames, end receipt frames, and the execution log table. Scene code table refers to a data table that stores the correspondence between scene codes and lighting control items according to the target identifier. Exposure constraint table refers to a data table that stores the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, their respective remaining exposure time, and prohibition execution flags according to the target identifier. Execution log table refers to a data table that records the frame reception status, state switching status, control output status, and termination reason for each channel according to the execution sequence number. Safe fallback scene refers to a restricted lighting scene or off-light scene output by the local lighting controller according to the exit segment and fallback transition time when revocation, authorization end, exposure is limited, or verification fails. The local lighting controller reads the corresponding lighting control item based on the target identifier and scene code, generates one or more lighting control instructions according to the target channel, and controls the brightness switching process according to the transition duration. For target identifiers that are more sensitive to changes in light and heat, the fallback brightness value corresponding to the safe fallback scene can be configured as a non-zero restricted brightness, and the fallback transition duration corresponding to the exit segment is longer than the fallback transition duration of ordinary target identifiers, so that the current scene drops to the fallback brightness value at a preset slope and then maintains or turns off the lights. Thus, the safe fallback scene is not only used to end execution, but also to limit output abrupt changes during the fallback process.

[0028] In some embodiments, the authorized lighting record includes at least a target identifier, scene code, brightness limit, authorized time period, hold duration, execution sequence number, operator identifier, and record generation time; the confirmation frame includes at least a target identifier, scene code, execution sequence number, frame transmission time, and confirmation flag; the cancellation frame includes at least a target identifier, execution sequence number, frame transmission time, and cancellation flag; and the on-site confirmation frame includes at least a target identifier, execution sequence number, on-site credential identifier, and frame acquisition time. At least one of the confirmation frame and the on-site confirmation frame serves as an execution confirmation frame, used to trigger the execution judgment of the record to be executed. After receiving the authorized lighting record, the local lighting controller first checks whether the target identifier exists in the scene code table and exposure constraint table, and then checks whether the current time falls within the authorized time period; when the current time falls within the authorized time period, the authorized lighting record is written into the record to be executed; when the current time is earlier than the authorization start time, the record to be executed is held and enters the matching judgment after the authorization start time is reached; when the current time is later than the authorization end time, the corresponding record is written into the execution log table and the execution sequence number is terminated. The local lighting controller uses the target identifier and execution sequence number as the matching key for confirmation frames, cancellation frames, and on-site confirmation frames, and verifies the consistency of scene codes and the validity of frame times under the same execution sequence number. When the matching key and scene code are consistent, the subsequent control process is entered. When the matching key is consistent but the scene code is inconsistent, the inconsistent scene code is marked in the execution log table and the scene is safely rolled back.

[0029] Specifically, in this embodiment, authorized lighting records, confirmation frames, cancellation frames, and on-site confirmation frames are uniformly written into a time reference field. The time reference field refers to the same timing caliber used to compare the authorization start time, authorization end time, frame transmission time, and frame acquisition time, prioritizing the use of the local clock of the local lighting controller and correcting it with the most recent valid synchronization result. In addition to the fields written in the authorized lighting record, the record to be executed also includes the record status, first reception time, most recent matching time, and most recent valid frame time. The record status is used to distinguish between the pending execution status, the executing status, and the terminated status. The target identifier uses a unique code consistent across the scene code table, exposure constraint table, and execution log table. The scene code uses a code that uniquely corresponds to a set of lighting control items in the scene code table. The current remaining exposure time refers to the minimum value among the remaining exposure time calculated based on the daily cumulative exposure value, weekly cumulative exposure value, and single cumulative exposure value at the current execution judgment time. For duplicate confirmation frames, cancellation frames, and on-site confirmation frames arriving under the same execution sequence number, the local lighting controller performs deduplication based on the time of the most recent valid frame. The deduplication time window is an implementation parameter, with a default value of 1 second and an adjustable range of 0.2 to 5 seconds. Duplicate frames that fall within the deduplication time window and whose content has not changed only update the receiving record and do not trigger a state switch. Frames whose transmission time or acquisition time is more than 300 seconds before the authorization start time, more than 300 seconds after the authorization end time, or earlier than the time of the most recent valid frame under the same execution sequence number are recorded as having invalid timing and written to the execution log table.

[0030] In some embodiments, the local lighting controller reads the target channel, target brightness value, and transition duration according to the scene code table, and compares the target brightness value with the upper limit of brightness, taking the result that is not higher than the upper limit of brightness as the actual output brightness value; when the execution confirmation frame meets the execution conditions and the current remaining exposure time of the corresponding target identifier in the exposure constraint table is greater than zero, a lighting control instruction is generated and sent to the light source driving unit according to the actual output brightness value and transition duration; when the cancellation frame arrives, the hold duration expires, the authorized period expires, or the current remaining exposure time is reduced to zero, the lighting control instruction corresponding to the safe rollback scene is output, and the termination reason, termination time, and current scene code at the end are written to the execution log table.

[0031] Example 1: This embodiment presents a multi-channel remote lighting control system suitable for low-illuminance authorized lighting in artifact display cases or archives. The system uses authorized lighting records, execution confirmation frames, and exposure constraint tables as the common execution basis, and controls the lighting to maintain and exit based on the current remaining exposure time during execution.

[0032] like Figure 1As shown, this embodiment proposes a multi-channel remote lighting control system, including a remote management terminal, a first remote communication channel and a second remote communication channel that are set independently of each other, a near-field confirmation channel, a local lighting controller, and a light source driving unit; The remote management terminal generates an authorized lighting record that includes at least a target identifier, scene code, brightness limit, authorized time period, hold duration, execution sequence number, and operator identifier. This record is sent to the local lighting controller via a first remote communication channel. A second remote communication channel sends at least one of a confirmation frame and a cancellation frame corresponding to the authorized lighting record. A near-field confirmation channel sends a field confirmation frame. At least one of the confirmation frame and the field confirmation frame serves as the execution confirmation frame. The local lighting controller stores a scene code table, an exposure constraint table, and an execution log table. The exposure constraint table stores daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, corresponding remaining exposure time, and a prohibition flag based on the target identifier. Upon receiving the authorized lighting record within the authorized time period, the local lighting controller generates a record to be executed. When the record to be executed and the execution confirmation frame satisfy the target... When the identifier and execution sequence number are consistent and the prohibition flag is invalid, the minimum value among the remaining exposure time corresponding to each statistical caliber is taken as the current remaining exposure time. A light control command not exceeding the brightness limit is generated according to the scene code table, and the light source driving unit is controlled to execute the light control command according to the execution time corresponding to the smaller value between the current remaining exposure time and the hold time. During the execution process, the local light controller accumulates the actual brightness value and the corresponding duration according to the sampling time slice to form the exposure increment, and updates the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value and the current remaining exposure time accordingly. When a cancellation frame is received, the hold time expires, the authorized period expires, the current remaining exposure time is reduced to zero, or the prohibition flag becomes valid, the light control command corresponding to the safe rollback scene is output and written to the execution log table. In this embodiment, the cumulative exposure value includes the daily cumulative exposure value, weekly cumulative exposure value, and single cumulative exposure value corresponding to the target identifier, representing the actual cumulative illumination received by the target identifier under the corresponding statistical caliber; the remaining exposure time refers to the remaining time allowed to continue illumination after being converted according to the current actual brightness value under the current statistical caliber; the prohibited execution flag refers to the control flag given by the exposure constraint table that prohibits entering the execution state. The data sources in the exposure constraint table include one or more of the following: manually entered protection thresholds, historical execution log conversion results, and measured data from the illumination acquisition device.

[0033] When the local lighting controller enters the execution judgment, it first reads the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, remaining exposure time under each statistical metric, and the prohibition flag for the corresponding target identifier. The minimum of the remaining exposure time across the daily, weekly, and single-time levels is used as the current remaining exposure time. If the prohibition flag is valid, the scene is safely rolled back; if the prohibition flag is invalid and the current remaining exposure time is less than the hold time, the execution time is limited to the current remaining exposure time; if the prohibition flag is invalid and the current remaining exposure time is greater than or equal to the hold time, the execution time is limited to the hold time.

[0034] During execution, the local lighting controller accumulates the exposure increment by adding the actual brightness value and the corresponding duration according to the sampling time slice, and updates the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value and the corresponding remaining exposure time accordingly. When the current remaining exposure time decreases to zero during execution, a safe rollback scene is immediately output and the exposure expiration mark is written to the execution log table.

[0035] Abnormal operating conditions include at least the following: missing target identifier in the exposure constraint table; missing daily cumulative exposure value; missing weekly cumulative exposure value; missing single cumulative exposure value; missing remaining exposure time; failure to acquire actual brightness value; unavailable boundary moments; and time synchronization anomalies. When an abnormal operating condition occurs, the local lighting controller maintains a safe rollback scene and writes the abnormal operating condition marker to the execution log table. Daily boundary switching or weekly window boundary switching is not treated as an abnormal operating condition; instead, the exposure increment is split and updated according to the corresponding boundary moment.

[0036] For example, the cumulative exposure value, quota, and exposure increment use a consistent internal accounting unit. This internal accounting unit is used to maintain the comparability between the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, and their corresponding quotas. The update cycle is the time step of the local lighting controller recalculating the equivalent exposure consumption rate, cumulative exposure value, and current remaining exposure time. The default value is 1 second, and the adjustable range is 0.5~10 seconds. When the sampling time slice is less than the update cycle, the exposure increments of each sampling time slice within the same update cycle are accumulated before being written into the exposure constraint table. The daily quota, weekly quota, and single quota are written according to the protection scope of the cultural relic material category or archival carrier category corresponding to the target identifier. By default, the weekly quota does not exceed the cumulative daily quota limit of 7 consecutive natural days, and the single quota does not exceed the daily quota. The accounting method employs either zeroing or rolling merging. When zeroing is used, the daily cumulative exposure value is reset to zero after updating the natural day boundary, and the weekly cumulative exposure value is reset to zero after updating the preset weekly window boundary. When rolling merging is used, the daily and weekly cumulative exposure values ​​are accumulated by sliding based on the exposure increments within the most recent 24 hours and 7 days, respectively. The single cumulative exposure value is accumulated from the time the corresponding execution sequence number enters the execution state and is reset to zero after that execution sequence number enters the termination state. The remaining available exposure time is recalculated at least once per update cycle, and the recalculation result is the minimum value among the daily, weekly, and single-time remaining available exposure times. When any of the remaining available exposure times at any level is 0, a safe rollback scenario is maintained.

[0037] In an optional embodiment of Example 1, the first remote communication path includes a first communication interface and a first gateway, and the second remote communication path includes a second communication interface and a second gateway, wherein the second communication interface and the second gateway are respectively set independently of the first communication interface and the first gateway. The local lighting controller associates the path source of authorized lighting records, confirmation frames, and revocation frames with the execution sequence number and writes them into the execution log table; The independent configuration of the first and second remote communication paths means that the transmission paths for authorized lighting records and confirmation / cancellation frames are set separately on the communication interface and gateway entity, forming independent path source identifiers. The path source identifier includes at least the path number, interface number, gateway number, reception time, and reception result. When the local lighting controller receives authorized lighting records, confirmation frames, and cancellation frames, it records the corresponding path source identifiers and associates them with the execution sequence number, target identifier, frame type, and state transition result, writing them to the execution log table. For the same execution sequence number, if the confirmation and cancellation frames arrive from different remote communication paths, independent log records are formed in the execution log table; if the same frame arrives repeatedly on the same remote communication path, only the number of repeated receptions and the most recent reception time of the corresponding record for that frame are updated, without repeatedly triggering the lighting control output.

[0038] Specifically, in addition to the path number, interface number, gateway number, reception time, and reception result, the path source identifier also includes a frame sequence check value. The frame sequence check value is a comparison field used to determine the order of frames under the same execution sequence number. For the same execution sequence number, the local lighting controller prioritizes receiving frames with newer times and valid frame transmission times as the most recent valid frames. Frames with reversed reception times, missing frame transmission times, or frame transmission times deviating from the local time by more than a preset time difference threshold are recorded as abnormal frames and written to the execution log table. The preset time difference threshold is an implementation parameter, defaulting to 30 seconds, with an adjustable range of 5~300 seconds. The value is determined based on the maximum transmission jitter of the first and second remote communication paths and the gateway time synchronization accuracy. For duplicate arrivals of authorized lighting records, confirmation frames, and cancellation frames with identical content but different path sources, the local lighting controller retains the earliest valid reception record as the basis for state switching, while retaining other reception records as log information.

[0039] In one optional embodiment of Example 1, the scene code table pre-stores low-light display scenes, inspection scenes, maintenance scenes, inventory scenes, and safety rollback scenes corresponding to the target display case or target storage location, and stores the target channel, target brightness value, and transition duration for each scene code; the local lighting controller reads the corresponding control item according to the scene code and generates lighting control instructions; The scene code table is configured according to target identifiers. Each target identifier includes at least the scene code and its lighting control items corresponding to low-light display scene, inspection scene, maintenance scene, inventory scene, and safety fallback scene. The lighting control items include at least the target channel, target brightness value, transition duration, entry segment, and exit segment. The entry segment refers to the gradual brightening or channel-by-channel lighting control segment called by the local lighting controller when recording the transition from the pending state to the executing state; the exit segment refers to the gradual dimming, brightness reduction, or channel-by-channel shutdown control segment called by the local lighting controller when recording the transition from the executing state to the terminated state. The lighting control items corresponding to the safety fallback scene include at least the fallback target channel, fallback brightness value, and fallback transition duration. The safety fallback scene can be configured as an off-light scene or a restricted lighting scene under different target identifiers. After reading the corresponding lighting control items according to the target identifier and scene code, the local lighting controller generates one or more lighting control instructions according to the target channel and controls the brightness switching process according to the transition duration.

[0040] Furthermore, the equivalent illuminance coefficient refers to the conversion coefficient of the illumination intensity of the target identifier under the calibrated position, reference brightness, and corresponding scene code. It is written into the scene code table using stable measurement results from the illumination acquisition device. The calibrated position refers to the sensitive illumination location or representative storage location of the artifact corresponding to the target identifier; when the same target identifier has multiple illumination locations, the measurement result corresponding to the higher illumination location is used as the entry point. The reference brightness uses the same brightness scale as the target brightness value, defaulting to 100%, with an adjustable range of 30%~100%; the minimum measurement brightness is an implementation parameter used to limit the amplification of extremely low brightness, defaulting to 5%, with an adjustable range of 1%~15%. The calibrated brightness range refers to the brightness range allowed to use linear conversion under the corresponding scene code, defaulting to 20%~100%, and can be specifically adjusted based on the consistency between the drive readback value and the measured value from the illumination acquisition device. The actual brightness value is preferentially taken from the drive readback value of the light source driver unit. If the drive readback value is missing, the dimming output value sent by the local lighting controller is taken. If both are missing, the most recent valid illumination acquisition result is taken. If all three are missing, the most recent valid actual brightness value from the previous update cycle is used, and the minimum remaining exposure time is maintained without extending the execution time. The actual brightness value within the transition time is continuously recorded according to the sampling time slice. The sampling time slice is an implementation parameter, with a default value of 0.5 s and an adjustable range of 0.1~2 s.

[0041] In an optional embodiment of Example 1, the local lighting controller establishes a pending state, an executing state, and an ending state for each execution sequence number; When an execution confirmation frame matching the record to be executed is received, the corresponding record is changed from the pending execution state to the execution state; When at least one of the confirmation frame, on-site confirmation frame and cancellation frame with the same execution sequence number is received again, only the path source or end marker in the execution log table is updated, and the light control command is not repeatedly output. In an optional embodiment of Example 1, the near-field confirmation path includes a voucher reading unit located near the target display case or target storage location, and the voucher reading unit is connected to a local lighting controller. After the voucher reading unit reads the on-site voucher, it generates an on-site confirmation frame. The local lighting controller verifies the on-site voucher identifier in the on-site confirmation frame against the operator identifier in the authorized lighting record. If the verification matches, the record to be executed remains valid. If the verification does not match, the lighting control command corresponding to the safe rollback scenario is output and written to the execution log table. The on-site credential identifier refers to the data identifier read from the on-site credentials by the credential reading unit and used to identify the on-site operator. On-site credentials include one or more of the following: RFID cards, near-field communication tags, barcode identifiers, QR code identifiers, and electronic employee ID credentials. The correspondence between the operator identifier and the on-site credential identifier is written by the remote management terminal when generating the authorized lighting record, or verified by the local lighting controller based on a pre-stored correspondence table. The correspondence table includes at least the operator identifier, the on-site credential identifier, the valid start time, and the valid end time. After receiving the on-site confirmation frame, the local lighting controller first matches the record to be executed based on the execution sequence number and the target identifier, and then verifies the operator identifier and the on-site credential identifier based on the correspondence. When the correspondence is true, the on-site confirmation frame is allowed to participate in the execution condition judgment; when the correspondence is false, the on-site credential exceeds its validity period, or the on-site credential identifier is missing, the corresponding record is written to the execution log table and a safe rollback scenario is maintained. When the near-field confirmation path is abnormal, the local lighting controller records the abnormality. For pending records that have received a valid confirmation frame and whose authorized time period, target identifier, execution sequence number, and prohibition execution flag all meet the execution conditions, the confirmation frame is still allowed to be used as the execution confirmation frame to enter the execution judgment. For pending records that have not received a valid confirmation frame, the safe rollback scenario is maintained and the near-field confirmation path abnormality flag is written to the execution log table.

[0042] In one optional embodiment of Example 1, the scene code table stores an entry segment and an exit segment corresponding to each scene code; When the local lighting controller transitions from the pending state to the executing state, it outputs lighting control instructions according to the entry segment of the corresponding scene code; when it receives a cancellation frame, the hold duration expires, the authorized time period expires, or the current remaining exposure time is reduced to zero, it outputs the lighting control instructions corresponding to the safe fallback scene according to the exit segment of the corresponding scene code. When the local lighting controller enters the execution state and the termination state, it generates a start receipt frame and an end receipt frame, respectively. Both the start and end receipt frames include at least the target identifier, execution sequence number, current scene code, and status flag. The local lighting controller prioritizes sending the start and end receipt frames via the remote communication channel where the most recently received confirmation or cancellation frame is located. When the current execution sequence number only receives a field confirmation frame, the preferred sending channel is the preset default remote communication channel. If sending fails, it is sent via the other remote communication channel. In an optional implementation of Example 1, the start receipt frame refers to the status receipt generated and sent by the local lighting controller when the corresponding execution sequence number enters the execution state; the end receipt frame refers to the status receipt generated and sent by the local lighting controller when the corresponding execution sequence number enters the end state. Both the start and end receipt frames include at least the corresponding fields of target identifier, execution sequence number, current scene code, status flag, receipt generation time, path source identifier, and end reason. The local lighting controller synchronously writes the receipt sending result into the execution log table. The sending result includes at least the preferred sending path, the fallback sending path, the sending time, the number of sending times, and the sending status. When the current execution sequence number only receives a field confirmation frame, the preferred sending path is the preset default remote communication path; after the preferred sending path fails to send, the local lighting controller switches to the other remote communication path to send the same receipt content, and retains two sending records under the same execution sequence number in the execution log table. After receiving the start receipt frame and the end receipt frame, the remote management terminal establishes an association with the authorized lighting record according to the execution sequence number, and uses the status mark, current scene code and end reason in the receipt as the basis for remote status display and post-event verification.

[0043] For example, the start receipt frame and end receipt frame correspond to the receipt status field and receipt retransmission count field, respectively, within the local lighting controller. The receipt status field records one of the following results: not sent, sent successfully, sent successfully after the first path failed, or sent successfully through both paths. The receipt retransmission count field records the cumulative number of times the same receipt content has been sent. When both paths fail to send, the local lighting controller retains the corresponding receipt content along with the execution sequence number, target identifier, current scene code, status flag, and termination reason in the execution log table, and retransmits it in the order of reception time after either remote communication path becomes available again; the retransmission process does not change the already output lighting control status. The receipt content and the execution log table are associated through a double key of execution sequence number and target identifier. A double key refers to two related fields used simultaneously to index the same lighting execution process. The execution log table establishes a query scope at least by execution sequence number, target identifier, frame type, status flag, reception time, and termination reason, so that the remote management terminal can perform same-sequence number verification on authorized lighting records, receipt results, and exposure update results.

[0044] In an optional embodiment of Example 1, after each execution sequence number ends, the local lighting controller updates the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value and their respective remaining exposure time in the exposure constraint table according to the actual brightness value and the actual execution duration, and writes the update result into the execution log table in association with the execution sequence number. The actual brightness value refers to the current output brightness result determined by the local lighting controller during execution based on driver readback information, dimming output value, or light acquisition results. The actual execution duration refers to the cumulative duration during which the corresponding execution sequence number is in the execution state. After each execution sequence number ends, the local lighting controller calculates the exposure increment based on the actual brightness value and actual execution duration recorded during the execution process. This exposure increment is then added to the daily cumulative exposure value, weekly cumulative exposure value, and single cumulative exposure value in the exposure constraint table, while simultaneously deducting the corresponding remaining exposure time. The updated result includes at least the target identifier, execution sequence number, execution start time, execution end time, actual brightness value trajectory, exposure increment, updated daily cumulative exposure value, updated weekly cumulative exposure value, updated single cumulative exposure value, and the corresponding remaining exposure time and termination reason. The evidence storage structure in the execution log table includes at least the authorization record field area, frame reception field area, state switching field area, control output field area, exposure update field area, and receipt sending field area. Each field area is associated with the execution sequence number and target identifier to ensure that the log records, exposure update results, and remote receipt results of the same lighting execution process correspond to each other.

[0045] In a preferred embodiment of Example 1, the exposure constraint table, in addition to storing the prohibition flag for each target identifier, further subdivides the cumulative exposure value into daily cumulative exposure value, weekly cumulative exposure value, and single cumulative exposure value, which correspond to the daily quota, weekly quota, and single quota, respectively.

[0046] When authorized lighting begins, scene code changes, or the actual brightness value changes during execution, the local lighting controller recalculates the equivalent exposure consumption rate according to the update cycle. When the prohibition execution flag is valid, the duration conversion is not performed; instead, the lighting control command corresponding to the safe rollback scene is directly output and written to the execution log table.

[0047] At the start of each update cycle, the local lighting controller first reads the latest valid actual brightness value and the prohibition flag. The latest valid actual brightness value is taken from a brightness sample whose sampling time is no earlier than the end time of the previous update cycle. If no latest valid actual brightness sample is obtained in the current update cycle, the most recent valid brightness sample from the previous update cycle is used for calculation, and the currently obtained minimum remaining exposure time is maintained without extending the actual execution time. The prohibition flag is reread in each update cycle. When it changes from invalid to valid, the local lighting controller immediately terminates the current execution sequence number and outputs the lighting control command corresponding to the safety rollback scene; if the prohibition flag is abnormal or the timestamp is missing, it is treated as valid.

[0048] For records marked as invalid but meeting the authorized time period constraints, the equivalent exposure consumption rate is determined by the following formula: , in, Indicates the first Equivalent exposure consumption rate per update cycle; This represents the equivalent illuminance coefficient corresponding to the current scene code that is greater than zero. This coefficient is pre-written into the scene code table according to the illuminance measurement results of the target identifier at the calibrated position and the reference brightness. Indicates the first The actual brightness value for each update cycle; This represents a reference brightness greater than zero used for calibration. Switches according to the scene code, corresponding to the inspection scene and the maintenance scene. Higher than low-light display scenarios; when the actual brightness value increases... Synchronous increase, when the actual brightness value decreases, Synchronous reduction. To avoid amplifying the remaining exposure time when dimming to extremely low brightness, the minimum measured brightness is used instead when the actual brightness value is lower than the minimum measured brightness. participate The calculation; the minimum measured brightness is a preset brightness lower limit greater than zero, used to limit the conversion amplification when the actual brightness value is too low.

[0049] The linear conversion of the equivalent exposure consumption rate only applies to the calibrated brightness range corresponding to the current scene code. The calibrated brightness range is the effective brightness conversion range pre-stored in the scene code table for that scene code. When the actual brightness value is higher than the upper limit of the calibrated brightness range, the upper limit value is used to replace the actual brightness value in the calculation of the equivalent exposure consumption rate. When the actual brightness value is lower than the lower limit of the calibrated brightness range, the larger of the minimum metered brightness and the lower limit value is used to replace the actual brightness value in the calculation of the equivalent exposure consumption rate. When the current scene code lacks an effective equivalent illuminance coefficient or lacks a corresponding calibrated brightness range, the local lighting controller does not extend the remaining exposure time accordingly, but instead outputs the lighting control command corresponding to the safe fallback scene and writes it to the execution log table.

[0050] During execution, the local lighting controller synchronously recursively calculates the cumulative exposure values ​​for the three layers according to the update cycle: , in, and They represent the first Daily cumulative exposure value before and after each update cycle; and They represent the first Weekly cumulative exposure value before and after each update cycle; and They represent the first The cumulative exposure value of a single update cycle before and after each update cycle; This indicates the update cycle duration. Both daily and weekly cumulative exposure values ​​are updated according to a preset accounting method, which is either a pre-defined zeroing or rolling merging. The same target identifier remains unchanged within the same parameter configuration retention period. The parameter configuration retention period is the continuous operating cycle in which the local lighting controller has not rewritten the accounting method configuration for that target identifier. The single-time cumulative exposure value is zeroed at the end of the current execution sequence, thus ensuring that the same target identifier is simultaneously constrained by daily, weekly, and single-time metrics.

[0051] When a single update cycle crosses both the natural day boundary and the weekly window boundary, the local lighting controller splits the update cycle into a pre-boundary period and a post-boundary period according to the boundary time, and updates the corresponding daily or weekly cumulative exposure value respectively. If the boundary time is unavailable or time synchronization is abnormal, the exposure increment corresponding to the update cycle is included in the side with the smaller remaining amount between the front and back sides, and the remaining exposure time calculated according to the smaller side is maintained, without increasing the actual execution time.

[0052] After obtaining the updated cumulative exposure value, the remaining quota will be converted into the remaining exposure time based on the current consumption rate: , , , in, This indicates the remaining exposure time corresponding to the daily quota; This indicates the remaining exposure time corresponding to the weekly quota; This indicates the remaining exposure time corresponding to a single transaction limit; Indicates the daily limit; Indicates the weekly limit; This indicates the single-use limit. The daily limit, weekly limit, and single-use limit are determined by the tolerance level of the cultural relic material or archival carrier category corresponding to the target identifier. The weekly limit does not exceed the cumulative upper limit of multiple adjacent natural day limits, and the single-use limit does not exceed the daily limit. If any conversion result is zero, it means that the corresponding level of limit has been exhausted. The local lighting controller uses the minimum value among the three as the source of the current remaining exposure time to avoid excessively long execution time due to relying on only a single caliber.

[0053] Based on this, the actual execution time is determined by the minimum of the authorized retention time and the remaining exposure time of the three layers: , in, Indicates the actual execution time; This indicates the duration of the lighting in the authorized lighting record. The calculation is repeated in each update cycle. Therefore, when dimming, scene code switching, or brightness feedback changes occur during execution, the remaining exposure time will be dynamically shortened or extended accordingly, but the extension will not exceed [a certain value]. The upper bound defined by the limit does not exceed the boundary corresponding to the remaining value of each quota. When communication is interrupted, brightness feedback is abnormal, or data is missing within the update cycle, the local lighting controller adopts a conservative strategy, […]. The duration will be maintained based on the minimum remaining exposure time currently available, without extending the execution time based on missing data.

[0054] When the actual execution time approaches the threshold, instead of ending the lighting directly, it enters the critical dimming stage, compressing the current scene target brightness value proportionally: , in, This indicates the output brightness value during the critical brightness reduction phase; Indicates the minimum sustained brightness value; This indicates the target brightness value corresponding to the current scene code in the scene code table; Indicates the upper limit of brightness in the authorized lighting record; This represents the threshold duration for triggering a brightness reduction that is greater than zero. The critical brightness reduction occurs at... Effective at that time, and Not higher than Not lower than ;when When the brightness continues to decrease to zero, the critical dimming stage is exited and the corresponding lighting control command for the safety fallback scenario is output. Within the same execution sequence number, once the critical dimming stage is entered, the output brightness value is updated in a non-incremental manner; even if the remaining exposure time recovers to a value not less than the critical dimming trigger time threshold due to the actual decrease in brightness value in subsequent update cycles, the local lighting controller will maintain the currently output brightness value or continue to output at a lower brightness value, without restoring to the higher brightness value before entering the critical dimming stage; the target brightness value is only re-determined according to the new execution sequence number after a new execution sequence number is established.

[0055] When generating a record to be executed, the local lighting controller writes a configuration version identifier to the record. The configuration version identifier is used to bind the scene code table, equivalent illuminance coefficient, quota configuration, and accounting method corresponding to the execution sequence number. During the existence of the execution sequence number and its associated local queue item, the local lighting controller performs calculations, filtering, and conflict determination according to the configuration content corresponding to the configuration version identifier. When the configuration is modified during operation, the new configuration only takes effect on the newly generated execution sequence number and does not modify the execution sequence number and its associated local queue item that have been bound to the configuration version identifier.

[0056] Therefore, the exposure constraint table is no longer used only for static interception, but also links the cumulative exposure value, remaining exposure time, and execution prohibition flag to the entire process control of execution time and output brightness.

[0057] Example 2: Building upon Example 1, this example further provides a method for handling the interleaving of consecutive local inputs and remote undoes when the local operation input does not correspond to a safe rollback scenario, after the current execution sequence number ends. This method processes the local operation queue, conflict matrix, silent observation, and secondary filtering sequentially to maintain the temporal continuity between subsequent local inputs and the current execution chain.

[0058] The local operation input generated by the local operation input unit includes at least scene switching input, brightness adjustment input, emergency rollback input, and end input; the local lighting controller establishes a record item for the local operation input, which includes the input type, input time, target identifier, corresponding scene code, and processing result, and writes the record item to the execution log table; when the local operation input is an emergency rollback input or an end input, it immediately outputs the lighting control command corresponding to the safe rollback scene and switches the current execution sequence number to the end state; In this embodiment, when the local operation input is a scene switching input or a brightness adjustment input and there is currently an execution state, the local light controller will retain the local operation input until the current execution sequence number ends before processing; when there is currently no execution state, when the prohibition execution flag is invalid and the current remaining exposure time is greater than zero, the corresponding light control command is output according to the local operation input; for multiple local operation inputs generated consecutively within the preset queuing time window for the same target identifier, the latest input of the same type is retained as a valid input according to the input time order, and the processing result corresponding to the earlier input is updated to the queuing failure flag and then written to the execution log table; When the local operation input is a scene switching input or a brightness adjustment input and is currently in an execution state, the local lighting controller writes the local operation input into the local operation queue and retains it until the current execution sequence number ends before processing. When there is no current execution state, the local lighting controller first checks the current remaining exposure time and the prohibition flag of the corresponding target identifier in the exposure constraint table; if the prohibition flag is invalid and the current remaining exposure time is greater than zero, the corresponding lighting control command is output according to the local operation input; if the prohibition flag is valid or the remaining exposure time is equal to zero, the scene is safely rolled back and the local operation input is recorded as an unexecuted result and written to the execution log table.

[0059] For multiple local operation inputs generated consecutively within a preset queuing time window for the same target identifier, the local lighting controller processes them in queuing order according to their input time. Within the queuing time window, for multiple local operation inputs with the same input category and corresponding scene code, the latest one is retained as a valid queue item, and the processing result of the earlier recorded item is updated to indicate queuing failure. For local operation inputs with different input categories or corresponding scene codes, they are retained as different queue items. The local lighting controller does not directly delete the earlier input record, but retains it in the execution log table to maintain the traceability of local operation inputs.

[0060] In a preferred embodiment of Example 2, the local lighting controller maintains a local operation queue for local operation inputs generated by the same target identifier in the execution state that do not correspond to a safe rollback scenario. Each queue item in the local operation queue includes at least a local scene code, a priority code, an enqueue time, a retention deadline time, a queue validity flag, and a merging count.

[0061] When consecutive local inputs arrive, they are not enqueued indiscriminately. Instead, they are first merged based on scene consistency and temporal proximity. The first local input is then directly added to a new queue item. ;when hour, Determine using the following formula: , in, Indicates the first The project creation judgment value is entered locally next time; Indicates the first The local scene code corresponding to the next local input; This indicates the local scene code corresponding to the previous local input; Indicates the first The enqueue time of the next local input; Indicates the enqueue time of the previous local input; This indicates the time window for queuing.

[0062] The value is calibrated according to the continuous trigger interval and scene transition duration of the local operation input section, and is not less than the key debouncing cycle and not greater than the duration of the corresponding scene exit segment; when When this happens, the local lighting controller does not create new queue entries, but instead updates the queue count, enqueue time, and retention deadline for existing queue entries; when When a new local input reaches its capacity limit, if the priority code of the new local input is lower than or equal to the lowest priority code in the current queue, the new local input is discarded and the reason for discarding is recorded in the execution log table; if the priority code is higher than the lowest priority code in the current queue, the most recently enqueued queue entry with a priority code equal to the lowest priority code in the current queue is replaced, thereby compressing continuous inputs into a finite number of traceable queue entries.

[0063] Priority codes are pre-defined by the local lighting controller as discrete even-numbered levels based on scene risk level and task urgency. Maintenance scenes have higher priority codes than inspection scenes, inspection scenes have higher priority codes than inventory scenes, and low-light display scenes have the lowest priority. Safety rollback scenes are executed immediately without entering the local operation queue. With this setting, even if consecutive local inputs arrive intermittently, they will not directly overwrite the remote authorized execution chain before the current execution sequence number ends; instead, they will all enter the candidate set. The retention deadline is calculated based on the allowed waiting time corresponding to the local scene code. The allowed waiting time for maintenance scenes is longer than that for inventory scenes, and the allowed waiting time for low-light display scenes is shorter than that for inspection scenes. Queue items exceeding the retention deadline are no longer transferred to the execution stage; only log records are retained. For abnormal local inputs with out-of-order timestamps, missing scene codes, or out-of-bounds priority codes, the local lighting controller adopts a conservative strategy, marking the input as invalid and maintaining the current lighting control state without relaxing the execution conditions of the local queue.

[0064] In one example, the queue validity flag for the local operation queue uses two states: valid and invalid. The retention deadline refers to the latest time at which a queue item is allowed to enter subsequent filtering. The queuing time window is an implementation parameter, defaulting to 2 seconds, with an adjustable range of 0.5~10 seconds; the waiting compensation time window is an implementation parameter, defaulting to 30 seconds, with an adjustable range of 5~120 seconds; the silent observation duration is an implementation parameter, defaulting to 5 seconds, with an adjustable range of 1~30 seconds, and not less than the maximum retransmission interval of the second remote communication path. The priority code uses a discrete even-number level, defaulting to 0, 2, 4, and 6 for low-light display scenarios, inventory scenarios, inspection scenarios, and maintenance scenarios, respectively; when two queue items with the same target identifier have different priority codes but similar waiting durations, the queue item with the higher priority code is given priority. The queuing count refers to the number of consecutive local operation inputs merged within the queuing time window for the same queue item, used to determine the order when the selection value and enqueue time are the same. The maximum queue capacity is an implementation parameter, with a default value of 8 queues and an adjustable range of 4 to 32 queues. When the maximum capacity is reached, the queue is replaced according to the original priority and the most recently enqueued rule, and the processing result of the replaced queue item is updated to "Queue replacement failed".

[0065] When a remote undo frame arrives during the execution of the current execution sequence number, the local lighting controller immediately outputs the lighting control command corresponding to the safe rollback scene and writes the current execution sequence number into the end status; based on this, it calls the preset conflict matrix to process the local operation queue item by item.

[0066] The comparison of target brightness values ​​is only applicable to the first... The local scene code of the queue item corresponds to the same main lighting target channel in the scene code table as the main lighting target channel of the canceled scene, and both are bound to the same configuration version identifier; when the configuration version identifiers of the two are different, or the main lighting target channels are inconsistent and the target brightness values ​​cannot be directly compared, the local lighting controller will handle the overlapping target channel set with the target channel set of the canceled scene in the scene code table. Each queue item is processed as a cleared result, and this situation is written to the execution log table as a marker of inconsistent conflict comparison criteria.

[0067] The conflict matrix is ​​established in two dimensions: local scenario code and termination reason. When local operation queue filtering and conflict handling are involved, the configuration version identifier is also used to bind the priority code configuration and conflict matrix version, so that the same execution sequence number and its associated queue item use consistent filtering and conflict handling criteria during their lifetime. In the remote revocation corresponding column, for the first... Queue entries whose target channel set does not overlap with the target channel set of the cancelled scene in the scene code table are assigned retention results; A queue item whose target channel set includes the main lighting target channel corresponding to the canceled scene, and which satisfies any of the following conditions, is assigned a clear result: The local scene code of the queue item is the same as the scene code corresponding to the cancelled scene; or, under the premise of applying the comparison of target brightness values, the first queue item... The target brightness value corresponding to the local scene code of the queue item in the scene code table is not lower than the target brightness value corresponding to the canceled scene in the scene code table; for the queue item... The set of target channels corresponding to each queue item includes the main lighting target channel corresponding to the canceled scene, and under the premise of applying the comparison of target brightness values, the first queue item... If the target brightness value of the local scene code in the scene code table for a queue item is lower than the target brightness value of the canceled scene in the scene code table and does not trigger the prohibition flag, then a delayed result is assigned.

[0068] Among them, the canceled scene is the scene corresponding to the current execution sequence number before the arrival of the remote cancellation frame; the main lighting target channel is the target channel in the scene code table that corresponds to the canceled scene and is responsible for the main body illuminance output.

[0069] The queue validity flag is updated using the following formula: , in, Indicates the date after remote cancellation arrives. The queue validity flag is updated for each queue item; Indicates the first The processing results of each queue item in the remote cancellation column of the conflict matrix; Indicates the number of remote cancellations before arrival. The queue validity flag for each queue item; This column indicates the end reason for remote cancellation; Indicates the arrival time of the remote cancellation frame corresponding to this queue processing; Indicates the first The retention deadline for each queue item. A value of 0 indicates retention, a value of 1 indicates postponement, and a value of 2 indicates clearing. Therefore, after a remote cancellation, the queue state will only shrink or remain the same; the cancellation action will not amplify the execution scope of the local operation. The clearing, postponement, and retention results of each queue item, as well as changes in queue length, queue head scene code, and conflict matrix hit results, are all written to the execution log table along with the current execution sequence number.

[0070] Retaining, clearing, and delaying results are determined in a mutually exclusive manner, with only one processing result corresponding to the same queue item in the same termination reason column. It can be understood that the conflict matrix corresponds to at least the local scene code field, termination reason field, processing result field, and hit time field in the execution log table, with the processing result field taking one of the retain, delay, or clear options. The determination of overlapping target channel sets is based on the target channels written in the scene code table; if a target channel is missing, the configuration version identifier is inconsistent, and the target brightness value cannot be compared, or the main lighting target channel of the canceled scene is missing, the local light controller performs a clear operation and writes the conflict comparison inconsistency marker to the execution log table. For queue items that are delayed, the local light controller maintains the original enqueue time, original priority code, and original retain deadline, and does not automatically extend the retain time due to remote cancellation.

[0071] After the current execution sequence number ends, the head queue item is not directly output. Instead, the queue items that are still valid are filtered a second time according to priority and waiting time. Before filtering, the following criteria must be met simultaneously: the remaining exposure time of the corresponding target identifier in the exposure constraint table is greater than zero, the prohibited execution mark is invalid, and there is no pending remote authorization record with the same target identifier and an execution sequence number greater than the current execution sequence number. If there is remote cancellation, the preset silent observation time since the arrival time of the most recent remote cancellation frame participating in the current queue processing has expired. If there is no remote cancellation, this silent observation criterion is considered satisfied. The silent observation time is a preset waiting time used to shield short-term repeated control fluctuations after remote cancellation. Its value is not less than the maximum retransmission interval of the second remote communication path and not greater than the duration of the exit segment of the currently output scene.

[0072] After the above criteria are met, the local lighting controller will control the first... Calculate the selection value for each valid queue item: , in, Indicates the first The selection value for each valid queue item; Indicates the first Priority codes of each valid queue item; Indicates the end time of the current execution sequence number; Indicates the first The enqueue time of each valid queue item; This indicates the waiting compensation time window. The waiting compensation time window is a preset time window greater than zero and is bound according to the configuration version identifier. After entering the silent observation phase, the compensation portion formed by the waiting duration in the selected value is frozen according to the value at the beginning of the silent observation, and the deadline is retained so as not to be postponed due to the silent observation, thereby avoiding the continuous increase of the selected value of the delayed queue item due to repeated remote cancellation or repeated waiting.

[0073] Priority codes are incremented by even numbers, with a fixed difference of 2 between adjacent priority levels. The maximum number of waiting compensation items is 1. This ensures that waiting time can only improve the order of items in the same priority queue, and cannot override higher priority queue items across priority levels. Local lighting controller selection. The largest queue item is selected for subsequent execution. When multiple queue items have the same selection value, priority is given to the one with the earlier enqueue time. If the enqueue times are still the same, priority is given to the one with the larger queue count, in order to reduce repeated switching caused by continuous local input. When there are no valid queue items in the local operation queue, the selection value calculation process is not initiated, and the output state corresponding to the currently output scenario is maintained until a new valid input arrives. If a remote cancellation frame or a new remote authorization record is received again within the silent observation period, queue release is paused, and the selection value is recalculated while maintaining the freeze rule for the waiting time compensation portion, until there are no new remote control conflicts before proceeding to the execution phase.

[0074] When a selected local queue item enters the execution phase, the local lighting controller generates a subsequent execution record with a new internal sequence number and establishes a source association with the previous execution sequence number to prevent local delayed inputs from being misidentified as a continuation of the previous remote authorization record. Upon completion of execution, revocation, clearing, or exceeding the retention deadline, the execution log table is written back. Furthermore, each field of the execution log table is appended in the order it is written, and at least one valid record is retained for the same execution sequence number from the authorization record field, frame reception field, state switching field, control output field, exposure update field, and receipt sending field. When the execution log table reaches the preset record capacity limit, the local lighting controller performs a rolling overwrite of completed records according to the end time corresponding to the execution sequence number, prioritizing the overwriting of the oldest completed record that has exceeded the preset retention time. Records in the pending or executing state are not overwritten, and records with abnormal operating condition markers, exposure expiration markers, revocation markers, verification failure markers, or receipt not sent successfully markers are not overwritten before exceeding the preset retention time. The preset retention period is the implementation parameter, with a default value of 30 days and an adjustable range of 7 to 180 days. During rolling overwrite, the local light controller writes the start execution sequence number, end execution sequence number, and overwrite time of the overwritten record to the execution log table. If a field write fails, the local light controller first maintains the current light control state and then retryes writing; if consecutive retries fail, the unwritten field content is temporarily stored as a record to be written and written in chronological order after writing capability is restored. The minimum retention period for records to be written is 24 hours, with an adjustable range of 1 to 168 hours. All time fields in the execution log table are recorded using a time base field to maintain the alignment of authorized lighting records, receipts, and exposure updates. With this processing, when continuous local input and remote undo are interleaved, local input will neither reverse the bright scene upon arrival of remote undo nor be discarded entirely due to a single undo. Instead, it is transformed into a traceable and replayable delayed execution chain according to the order of queuing, conflict filtering, silent observation, and secondary filtering.

[0075] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0076] Furthermore, those skilled in the art will understand that although some embodiments herein include certain features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of this application and form different embodiments. For example, all the embodiments above can be used in any combination. The information disclosed in this background section is intended only to enhance the understanding of the general background of this application and should not be construed as an admission or in any way implying that such information constitutes prior art known to those skilled in the art.

Claims

1. A multi-channel remote lighting control system, characterized in that, It includes a remote management terminal, two independent remote communication channels, a near-field confirmation channel, a local lighting controller, and a light source driving unit; The remote management terminal generates an authorized lighting record that includes at least a target identifier, scene code, brightness limit, authorized time period, duration, execution sequence number and operator identifier. The record is sent to the local lighting controller via the first remote communication channel. The second remote communication channel sends at least one of a confirmation frame and a cancellation frame corresponding to the authorized lighting record. The near-field confirmation channel sends a field confirmation frame. At least one of the confirmation frame and the field confirmation frame serves as the execution confirmation frame. The local lighting controller stores a scene code table, an exposure constraint table, and an execution log table. The exposure constraint table stores the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, the corresponding remaining exposure time, and the prohibition flag according to the target identifier. After receiving the authorized lighting record within the authorized time period, the local lighting controller generates a record to be executed. When the record to be executed and the execution confirmation frame meet the requirements of the target identifier and execution sequence number and the prohibition execution flag is invalid, the minimum value of the remaining exposure time corresponding to each statistical caliber is used as the current remaining exposure time. The lighting control command with a brightness limit not exceeding the scene code table is generated according to the scene code table. The light source driving unit is controlled to execute the lighting control command according to the execution time corresponding to the smaller value between the current remaining exposure time and the holding time. During execution, the local lighting controller updates the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, and current remaining exposure time according to the sampling time slice. When it receives a cancellation frame, the hold time expires, the authorized time period expires, the current remaining exposure time is reduced to zero, or the prohibition execution flag becomes valid, it outputs the lighting control command corresponding to the safety rollback scenario, writes the status flag of the corresponding execution sequence number and the termination reason into the execution log table, and sends a status receipt to the remote management terminal.

2. The multi-channel remote lighting control system according to claim 1, characterized in that, The first remote communication path includes a first communication interface and a first gateway, and the second remote communication path includes a second communication interface and a second gateway, wherein the second communication interface and the second gateway are respectively set independently of the first communication interface and the first gateway; The local lighting controller associates the authorized lighting record, the confirmation frame, and the revocation frame with the execution sequence number and writes them into the execution log table.

3. The multi-channel remote lighting control system according to claim 1, characterized in that, The scene code table pre-stores low-light display scenes, inspection scenes, maintenance scenes, inventory scenes, and safety rollback scenes corresponding to the target display case or target storage location, and stores the target channel, target brightness value, and transition duration for each scene code; the local lighting controller reads the corresponding control item according to the scene code and generates the lighting control command.

4. The multi-channel remote lighting control system according to claim 1, characterized in that, The local lighting controller establishes a pending execution state, an execution in progress state, and a termination state for each execution sequence number; When an execution confirmation frame matching the record to be executed is received, the corresponding record is changed from the pending execution state to the executing state; When at least one of the confirmation frame, the on-site confirmation frame, and the cancellation frame with the same execution sequence number is received again, only the path source or end marker in the execution log table is updated, and the light control command is not output repeatedly.

5. The multi-channel remote lighting control system according to claim 1, characterized in that, The near-field confirmation path includes a voucher reading unit located near the target display case or target storage location, and the voucher reading unit is connected to the local lighting controller; After the voucher reading unit reads the on-site voucher, it generates the on-site confirmation frame. The local lighting controller verifies the on-site voucher identifier in the on-site confirmation frame against the operator identifier in the authorized lighting record. If the verification matches, the record to be executed remains valid. If the verification does not match, the lighting control command corresponding to the safe rollback scenario is output and written to the execution log table.

6. The multi-channel remote lighting control system according to claim 4, characterized in that, The scene code table stores an entry segment and an exit segment corresponding to each scene code; When the local lighting controller transitions from the pending state to the executing state, it outputs the lighting control instruction according to the entry segment of the corresponding scene code; when it receives the cancellation frame, the hold duration expires, the authorized time period expires, or the current remaining exposure time is reduced to zero, it outputs the lighting control instruction corresponding to the safe rollback scene according to the exit segment of the corresponding scene code.

7. The multi-channel remote lighting control system according to claim 6, characterized in that, When the local lighting controller enters the execution state and the termination state, it generates a start receipt frame and an end receipt frame, respectively. Both the start receipt frame and the end receipt frame include at least a target identifier, execution sequence number, current scene code, and status flag. The local lighting controller prioritizes sending the start receipt frame and the end receipt frame through the remote communication channel where the most recently received confirmation frame or cancellation frame is located. When the current execution sequence number only receives a field confirmation frame, it is sent through a preset default remote communication channel. If the sending fails, it is sent through the other remote communication channel.

8. The multi-channel remote lighting control system according to claim 1, characterized in that, The local operation inputs generated by the local operation input unit include at least scene switching input, brightness adjustment input, emergency rollback input, and end input; The local lighting controller establishes a record item for the local operation input, which includes the input category, input time, target identifier, corresponding scene code and processing result, and writes the record item into the execution log table; When the local operation input is an emergency rollback input or an end input, the lighting control command corresponding to the safe rollback scenario is immediately output, and the current execution sequence number is switched to the end state.

9. The multi-channel remote lighting control system according to claim 8, characterized in that, When the local operation input is a scene switching input or a brightness adjustment input and is currently in execution, the local lighting controller will retain the local operation input until the current execution sequence number ends before processing it. When there is no current execution state, when the execution prohibition mark is invalid and the current remaining exposure time is greater than zero, the corresponding light control command is output according to the local operation input; For multiple local operation inputs generated consecutively within a preset queuing time window for the same target identifier, the latest input of the same category is retained as a valid input according to the input time order, and the processing result corresponding to the earlier input is updated as the queuing failure flag and then written to the execution log table.

10. The multi-channel remote lighting control system according to claim 1, characterized in that, After each execution sequence number ends, the local lighting controller updates the daily cumulative exposure value, weekly cumulative exposure value, single cumulative exposure value, and corresponding remaining exposure time in the exposure constraint table according to the actual brightness value and actual execution duration, and writes the update result into the execution log table in association with the execution sequence number.

Images