Off-line multi-scene cooperation and data synchronization mechanism and system based on light guide film

Abstract

The invention discloses an off-line multi-scene collaboration and data synchronization mechanism and system based on a light guide film. State data of a user in multiple application scenes such as health monitoring, safety protection, social service, virtual world and smart home are subjected to local temporary storage, priority ranking and intelligent synchronization after network disconnection recovery through a unified identity authentication center. The unique identity feature code is locally cached after the user registers for the first time, and the user does not need to depend on online authentication in an offline state. The system comprises an off-line data temporary storage module, a priority ranking module, an off-network recovery synchronization module, a conflict arbitration module, a storage space management module and a manager off-line response module. When the network is interrupted, state change is temporarily stored in a local circular queue according to the priority (the highest life safety class), sequencing is carried out in real time during writing, and low-priority data is preferentially discarded when the space is full (coverage operation is executed at the head of the queue). And after the network is recovered, reporting according to a priority sequence, and reporting overtime retry by adopting a fragment transmission and breakpoint resume mechanism. The multi-device offline conflict is automatically arbitrated according to a version number, a timestamp and a device priority rule, and a conflict log retention period can be set. And when the supervisor is offline, automatically electing a temporary supervisor, and synchronizing data after recovery. According to the method, the problems that multi-scene state data are lost when the network is interrupted, off-line operation cannot be coordinated, and data conflicts are generated after recovery are solved, and a complete closed loop of online real-time synchronization, off-line temporary storage and supplementary transmission and high availability of a manager is realized.

Description

Technical Field

[0001] This invention relates to the fields of distributed systems, offline data processing, data synchronization, and human-computer interaction. Specifically, it relates to an offline multi-scenario collaboration and data synchronization mechanism and system based on photoconductive film. Through a unified identity authentication center, it temporarily stores, prioritizes, and intelligently synchronizes user status data in multiple application scenarios such as health monitoring, security protection, social services, virtual world, and smart home after network outages. This solves the problems of data loss in multiple scenarios, inability to coordinate offline operations, and data conflicts after recovery in the prior art when the network is interrupted. Citation of prior application

[0002] This application is based on the applicant's previously filed patent technology, specifically cited as follows: 1. Prior patent application (application number 2026103505829, application date 2026-03-20, invention title: A method and system for unique identification of human optical spectral features based on photoconductive film) This patent discloses a method for uniquely identifying human optical spectral features. It uses a photoconductive film to collect human optical spectral features and generate a unique feature code for identity verification. The unified identity authentication center in this application uses the spectral feature acquisition and comparison technology of this patent as the identity basis for offline data synchronization. Users complete identity authentication upon initial registration; in offline mode, identity verification is performed using a locally cached unique identity feature code, eliminating the need for online authentication.

[0003] 2. Prior patent application (application number 2026103373270, application date 2026-03-19, invention title: A distributed housekeeping system and method based on multi-terminal collaboration) This patent discloses a distributed butler system based on multi-terminal collaboration, including a main butler unit and sub-butler units, used to aggregate information from various smart terminal devices and present it to the user. The multi-terminal offline collaboration mechanism in this application is implemented based on the butler system architecture of this patent.

[0004] 3. Prior patent application (application number 2026103511336, application date 2026-03-21, invention title: A full-scene state synchronization and priority scheduling system and method based on photoconductive film) This patent discloses a cross-scenario state synchronization and priority scheduling mechanism, including priority level division rules and a state synchronization framework. The priority sorting rules and state synchronization framework in this application reuse the technical solutions of this patent.

[0005] 4. Patents for various application scenarios submitted by the applicant. This application provides offline collaboration and data synchronization services for patents in various application scenarios, including health monitoring patents (such as blood pressure monitoring patent 2026103509995), security protection patents (such as anti-fraud patent 2026103476031), social service patents (such as family tracing patent 2026103505068), and intelligent interaction patents (such as eye tracking patent 2026103269949). The various health monitoring, security protection, social service, and intelligent interaction technologies referenced in the specific embodiments of this application all originate from the corresponding patents previously filed by the applicant (see the various embodiments in the "Specific Embodiments" section of this application for details). The application dates of the aforementioned prior basic patents are all earlier than this application, and they were not published before the filing date of this application, and therefore do not constitute prior art for this application. Background Technology

[0006] With the development of smart terminals and IoT technologies, users generate a large amount of status data in multiple scenarios (health monitoring, security protection, social services, virtual world, smart home). However, existing technologies have the following shortcomings: Offline data loss: When the network is interrupted, the status data generated in various scenarios cannot be reported, and the inconsistent local temporary storage strategies lead to data loss. Offline operations cannot be synchronized: Operations performed by users while offline (such as health monitoring and virtual world interaction) cannot be synchronized with other scenarios, and the status is inconsistent after the network is restored; Data conflicts after recovery: Multiple devices undergo state changes during offline periods, and the lack of a unified conflict arbitration mechanism after network recovery leads to data overwriting errors; Missing priorities: Offline temporarily stored data lacks priority distinction, and urgent data (such as car accident detection and physiological abnormalities) is treated the same as non-urgent data, which may delay the reporting of critical information; Low synchronization efficiency: After the network is restored, all offline data is fully synchronized, which consumes a lot of bandwidth and takes a long time to synchronize. No response when the supervisor is offline: Current technology does not consider the data processing mechanism when the supervisor device is offline or disconnected from the network.

[0007] The applicant has previously filed patents for a distributed housekeeper system (2026103373270) and a full-scene status synchronization and priority scheduling patent, which can achieve real-time online status synchronization. Building on this, the present invention further constructs an offline multi-scene collaboration and data synchronization mechanism to achieve local temporary storage, priority sorting, intelligent synchronization and conflict arbitration after network interruption, and designs a solution for handling offline housekeeper issues. Summary of the Invention

[0008] (a) Purpose of the invention The purpose of this invention is to provide an offline multi-scenario collaboration and data synchronization mechanism and system based on photoconductive film. By using a unified identity authentication center, the system can temporarily store, prioritize, and intelligently synchronize user status data in multiple application scenarios such as health monitoring, security protection, social services, virtual world, and smart home. This solves the problems of data loss in multiple scenarios when the network is interrupted, inability to coordinate offline operations, and data conflicts after recovery in the prior art.

[0009] (II) Technical Solution 1. An offline multi-scenario collaborative and data synchronization system based on a photoconductive film, characterized in that it comprises: The unified identity authentication center is used to collect the optical spectral characteristics of the user's human body through the optical guide film and generate a unique identity feature code, which serves as the identity basis for offline data synchronization. When a user registers for the first time, identity authentication is completed, and the unique identity feature code cached locally is used for identity recognition in offline mode. The offline data storage module is used to temporarily store the status change events generated by each application scenario in the local storage of the sub-manager when the communication between the sub-manager and the main manager is interrupted. Each record includes the status change event ID, scenario identifier, status type, status value, timestamp, version number, and priority level. The priority sorting module is used to sort the temporary data according to the priority level of the state change event, and high-priority data is retained and uploaded first; the sorting is performed in real time when the data is written to the temporary queue to ensure that the queue always maintains the priority order. The network outage recovery synchronization module is used to automatically report temporarily stored offline data to the main manager when the network is restored. The main manager processes the data according to priority and synchronizes it to all relevant scenarios. The reporting adopts a segmented transmission mechanism, in which each record is transmitted in segments of a fixed size. The sub-manager records the transmitted segment sequence number and the current record ID as the breakpoint. When the network is interrupted, the breakpoint is saved and the reporting continues from the breakpoint after the network is restored. The conflict arbitration module is used to determine the final state according to preset arbitration rules when multiple devices make conflicting changes to the same state while offline. The arbitration result is pushed to all relevant devices and a conflict log is recorded for users to view. Inconsistent states are allowed among devices during offline periods, and conflict arbitration is only executed by the administrator after the network is restored. The storage space management module is used to manage the local temporary storage space of the sub-manager. When the temporary storage space is insufficient, it will automatically clean up low-priority or expired data. The offline supervisor handling module is used to automatically elect the highest priority sub-supervisor among online devices as a temporary supervisor when the original supervisor device goes offline. The temporary supervisor is responsible for receiving offline data from other sub-supervisors, temporarily storing it, and arbitrating conflicts. When the original supervisor comes back online, the temporary supervisor will synchronize the temporarily stored data to the original supervisor and resume the original supervisor's responsibilities.

[0010] 2. The system according to claim 1, wherein the priority ranking module assigns priority levels to state change events that are consistent with scenario priorities: life safety scenarios are the highest priority; property safety scenarios are the second highest; social service scenarios are the third highest; health monitoring scenarios are the fourth highest; and daily interaction scenarios are the lowest. Within the same priority level, events are ranked by urgency; and within the same priority level and urgency level, events are ranked by timestamp.

[0011] 3. The system according to claim 1, characterized in that, in the offline data temporary storage module, each sub-manager uses a circular queue to store offline data, and the queue capacity is preset by the system; CRC32 checksum is used when writing data to prevent data corruption.

[0012] 4. The system according to claim 1, characterized in that, in the storage space management module, when the temporary storage space utilization rate reaches the system preset threshold, the system automatically cleans up the record with the lowest priority and the earliest timestamp, and records the cleanup log; when the space is full, newly generated low-priority data is directly discarded, and high-priority data overwrites the record with the lowest priority and the earliest timestamp in the queue (the overwrite operation is performed at the head of the queue and does not affect the writing of new data at the tail of the queue); the cleanup operation does not affect the higher-priority data that has already been written.

[0013] 5. The system according to claim 1, characterized in that, in the network recovery synchronization module, after network recovery, each sub-manager reports offline data in the following order: first, the highest priority data is reported in timestamp order; second, the next highest priority data is reported; and finally, the remaining priority data is reported in sequence. After receiving the data, the supervisor returns an acknowledgment signal, and after receiving the acknowledgment, the sub-manager deletes the reported data. If the network is interrupted again during the reporting process, the sub-manager saves the current breakpoint (current record ID and transmitted fragment sequence number), and after the network is restored, sends a resume request to the supervisor, carrying the current record ID and transmitted fragment sequence number. The supervisor returns the untransmitted data fragments, and the sub-manager continues reporting from the breakpoint. If the reporting times out, the sub-manager retryes the system's preset number of times, and after the timeout, the data is retained for reporting after the next recovery.

[0014] 6. The system according to claim 1, characterized in that, in the conflict arbitration module, when multiple devices generate conflicting changes to the same state during offline periods, arbitration is carried out according to the following rules: the state with the highest version number is given priority; if the version numbers are the same, the state with the latest timestamp is given priority; if the timestamps are the same, the device priority rule is used; the device priority rule is preset by the user in the unified identity authentication center and stored locally in the unified identity authentication center; since the device priority rule is only queried and used by the supervisor after the network is restored, it does not need to be synchronized during offline periods, thus avoiding the problem of offline synchronization being unavailable; the arbitration result is pushed to all relevant devices, and a conflict log is recorded for the user to view, the retention period of the conflict log is set by the user.

[0015] 7. The system according to claim 1, wherein the election rule for the temporary supervisor in the offline supervisor response module is as follows: the online sub-supervisor with the highest device priority is selected first; when the device priorities are the same, the device with the largest storage capacity is selected; when the storage capacity is the same, the device that has communicated with the supervisor the most recently is selected; the temporary supervisor's offline data storage adopts the same circular queue and priority sorting mechanism as the sub-supervisors.

[0016] 8. A method for offline multi-scenario collaboration and data synchronization based on photoconductive film, characterized by comprising the following steps: S1: Users complete identity authentication through the light guide film, establishing a unified identity across scenarios. In offline mode, identity recognition is performed through a unique identity feature code cached locally. S2: The sub-manager monitors the communication status with the main manager in real time; at the same time, the system monitors whether the main manager's device is online in real time, and if the main manager is offline, it executes the main manager offline response procedure. S3: When a network interruption is detected, the administrator will temporarily store the state change events generated by each application scenario in local storage and sort them by priority; the sorting is performed in real time when the data is written to the temporary storage queue to ensure that the queue always maintains the priority order. S4: The administrator continuously monitors the network status and retryes the connection at preset system intervals (e.g., 30 seconds). S5: When network recovery is detected, the sub-manager reports the temporarily stored offline data to the main manager in priority order; the reporting adopts a fragmented transmission mechanism, with each record being transmitted in fragments of a fixed size. The sub-manager records the transmitted fragment sequence number and the current record ID as a breakpoint. When the network is interrupted, the breakpoint is saved, and the reporting continues from the breakpoint after recovery; the system will retry a preset number of times when the reporting times out. S6: After receiving the data, the supervisor processes it according to priority and synchronizes it to all relevant scenarios; S7: When a conflict is detected, the conflict arbitration module determines the final state according to preset rules and synchronizes it to all devices; S8: After receiving confirmation from the supervisor, the sub-supervisor deletes the locally stored temporary data that has been reported.

[0017] 9. The method according to claim 8, wherein the offline response process of the supervisor includes: the system automatically elects the supervisor with the highest priority among the online devices as the temporary supervisor; the temporary supervisor is responsible for receiving offline data from other supervisors for temporary storage and conflict arbitration; when the original supervisor returns to online, the temporary supervisor synchronizes the temporary data to the original supervisor and resumes the original supervisor's responsibilities.

[0018] 10. A computer-readable storage medium having a computer program stored thereon, characterized in that, when the program is executed by a processor, it implements the method according to any one of claims 8-9. Detailed Implementation

[0019] System architecture and data flow The core innovation of this system lies in combining a distributed steward system with offline data storage, priority sorting, and network outage recovery synchronization. This enables local collaboration of multiple scenarios during network interruption and intelligent synchronization after recovery. Furthermore, a solution for steward offline situations has been designed.

[0020] The system architecture is as follows: Unified Identity Authentication Center: Deployed on the user's designated home device (default mobile phone), it uses unique identification based on a photoconductor film (referenced in prior application 2026103505829) as the identity foundation for offline data synchronization. User identity authentication is completed upon initial registration; offline identification is performed using a locally cached unique identity feature code, eliminating the need for online authentication.

[0021] The main supervisor unit is responsible for receiving offline data reported by sub-supervisors, processing it according to priority, synchronizing it to all relevant scenarios, and arbitrating conflicts. When a main supervisor device goes offline, the system automatically elects a temporary main supervisor.

[0022] Sub-Manager Unit: A lightweight software module installed on various smart terminal devices. Users are guided through the installation process via the Sub-Manager APP upon first use. Each Sub-Manager corresponds to an application scenario (e.g., blood pressure sub-Manager, blood oxygen sub-Manager, vehicle rescue sub-Manager, etc.), responsible for collecting status data for that scenario, detecting network status, temporarily storing offline data, reporting according to priority, and receiving confirmation. Sub-Managers connect to the Sub-Manager via an encrypted communication link.

[0023] Data flow path: Users complete identity authentication through the optical guide film, establishing a unified identity. The sub-manager monitors the communication status with the manager in real time; at the same time, the system monitors whether the manager's devices are online. If the supervisor is offline, the offline supervisor response procedure is executed (see Example 5 for details), and the system automatically elects a temporary supervisor according to the election rules. When the network is interrupted, the administrator will temporarily store the status changes locally and sort them by priority; The administrator continuously monitors the network and retryes the connection every 30 seconds. After the network is restored, the data manager reports offline data according to priority, using a segmented transmission and breakpoint resume mechanism, and retrying 3 times for reporting timeouts; The administrator receives, processes, and synchronizes the data. The conflict arbitration module handles conflicts between multiple devices, and conflict logs are retained for 30 days. After receiving confirmation, the administrator deletes the reported data.

[0024] The following provides a detailed description of each module: Example 1: Temporary storage of health monitoring data in offline mode User Zhang entered the underground parking garage, but his mobile phone had no network signal. Zhang used the blood pressure monitoring app to measure his blood pressure, but the data could not be reported to the monitoring system. The monitoring system detected a network interruption and temporarily stored the blood pressure measurement data (priority: level four) in a local circular queue. Each record includes an event ID, scene identifier (blood pressure), status type, status value, timestamp, version number, and priority level. A CRC32 checksum is used during data writing to prevent data corruption. Subsequently, Zhang used the blood oxygen monitoring app to measure his blood oxygen, and the data was also temporarily stored. Zhang measured his blood pressure 5 times and his blood oxygen 3 times consecutively, resulting in 8 records in the temporary queue. The storage space management module monitors usage; if the threshold is not reached, all records are retained.

[0025] Example 2: Offline Data Prioritization and Space Management User Li triggered the following events in an offline environment: The vehicle rescue app detected a minor collision (life safety category, level 1 priority). The health monitoring app detected elevated blood pressure (health monitoring category, level 4 priority). The anti-fraud app detected a suspicious call (property security category, level 2 priority). Virtual world applications record location changes (daily interaction type, priority level 5). Sleep monitoring app records sleep quality (health monitoring category, level 4 priority). The system prioritizes and temporarily stores data: highest priority (collision events) first, followed by (fraud prevention), then (blood pressure, sleep), and finally (virtual world). Sorting is performed in real-time as data is written to the temporary storage queue, ensuring the queue always maintains its priority order. When the temporary storage space usage reaches a system-preset threshold, the system automatically cleans up the lowest priority record with the earliest timestamp (virtual world position changes) and records the cleanup. When the space is full, newly generated low-priority data is discarded, and high-priority data overwrites the lowest priority record with the earliest timestamp in the queue (the overwrite operation is performed at the head of the queue and does not affect the writing of new data at the tail of the queue).

[0026] Example 3: Intelligent synchronization and resume download after network outage Mr. Li drove his car out of the underground parking garage, and the network was restored. Each data administrator detected the network restoration and reported the offline data in priority order: First, report incidents related to life safety: vehicle-mounted rescue collisions. Secondly, report matters related to property security: suspicious calls and fraud prevention. Finally, report health monitoring items: elevated blood pressure, sleep quality. The reporting process employs a fragmented transmission mechanism: the sub-administrator divides each record into fixed-size fragments for transmission. Upon successful transmission of a fragment, the local system records the fragment sequence number. If the network is interrupted again during the reporting process, the sub-administrator saves the current breakpoint (current record ID and transmitted fragment sequence number). After network recovery, the sub-administrator sends a resume request to the supervising administrator (carrying the current record ID and transmitted fragment sequence number). The supervising administrator returns the untransmitted data fragments, and the sub-administrator resumes reporting from the breakpoint. After all fragments of the same record have been transmitted, the supervising administrator returns confirmation, and the sub-administrator deletes the record. Reporting timeouts are retried three times; after a timeout, the data is retained for resuming reporting upon the next network recovery.

[0027] After receiving the data, the administrator processes it according to priority: first, collision events are processed and synchronized to all relevant scenarios (such as emergency contacts and vehicle systems); then, anti-fraud events are processed and synchronized to the anti-fraud application; finally, health monitoring data is processed and health trend reports are updated.

[0028] Example 4: Offline Conflict Arbitration and Device Prioritization for Multiple Devices Mr. Zhang used his mobile phone to measure his blood pressure at home, while a health monitoring app on his tablet was also measuring his blood pressure (offline). After the network was restored, both the phone and tablet simultaneously reported blood pressure data. Mobile phone data: timestamp 14:30:15, version number V3, blood pressure 135 / 85 Tablet data: Timestamp 14:30:20, Version V2, Blood pressure 128 / 80 The conflict arbitration module detects conflicting changes in the same state (blood pressure) and arbitrates according to the rules: Prioritize the highest version number: Mobile phone V3 is higher than Tablet V2, and mobile phone data will be used. If the version numbers are the same, the state with the latest timestamp will be used (this was not triggered in this example). When timestamps are the same, the device priority rule applies. Device priority rules are preset by users in the unified identity authentication center (e.g., mobile phone > tablet > computer > vehicle), and stored locally in the unified identity authentication center. Since device priority rules are only queried and used by the administrator after network recovery, they do not need to be synchronized during offline periods, avoiding the problem of offline synchronization being unavailable. Arbitration result: The blood pressure status is finally determined to be 135 / 85. The arbitration result is pushed to all relevant devices (mobile phone, tablet, vehicle, etc.) and a conflict log is recorded for users to view. The conflict log is retained for 30 days, and users can view the conflict record in the unified identity authentication center: "Blood pressure data conflict: Data from mobile phone (14:30:15) and tablet (14:30:20) are inconsistent; mobile phone data has been used." Example 5: Offline response by the supervisor Mr. Wang's mobile phone (the default supervisor) was out of battery and turned off. The blood pressure monitoring system on his tablet detected that the supervisor was offline, and the system automatically elected the highest-priority supervisor among the online devices as the temporary supervisor. The election rules were as follows: the highest-priority online supervisor was selected first; if the device priorities were the same, the device with the largest storage capacity was selected; if the storage capacity was the same, the device that had communicated with the supervisor most recently was selected. Mr. Wang's tablet was elected as the temporary supervisor.

[0029] The temporary supervisor is responsible for receiving offline data from other supervisors, storing it temporarily, and resolving conflicts. Mr. Wang uses the blood pressure supervisor's app to measure his blood pressure, and the data is reported to the temporary supervisor for storage. Once Mr. Wang's phone is charging and back online, the temporary supervisor synchronizes the stored data to the original supervisor and resumes the original supervisor's responsibilities. Exception handling mechanism

[0030] When the temporary storage space is full, the system automatically cleans up the record with the lowest priority and the earliest timestamp when the temporary storage space usage reaches the system's preset threshold, and records the cleanup log. When the space is full, newly generated low-priority data is directly discarded, and high-priority data overwrites the record with the lowest priority and the earliest timestamp in the queue (the overwrite operation is performed at the head of the queue and does not affect the writing of new data at the tail of the queue). The cleanup operation does not affect the higher-priority data that has already been written.

[0031] Data corruption handling: CRC32 checksum is calculated when each record is written and verified when it is read; corrupted records are automatically discarded and an error log is recorded when data corruption is detected.

[0032] Handling of reporting timeout: After the sub-administrator reports the data, they wait for the supervising administrator to confirm. If no confirmation is received within 10 seconds, the system will retry 3 times. If the system still fails, the data will be retained and reported again when the network is restored.

[0033] Conflict Log Management: Conflict logs are retained for 30 days by default, but users can set the retention period; users can view, export, and delete conflict logs.

[0034] Offline Manager Handling: When the manager device goes offline, the system automatically elects a temporary manager; the temporary manager temporarily stores data and synchronizes it after the original manager is restored; the election rules are as described above. Beneficial effects

[0035] Zero offline data loss: When the network is interrupted, all status changes are temporarily stored locally and automatically reported after recovery to ensure that no data is lost; Intelligent priority sorting: Life safety data is prioritized for retention and uploading, and emergency data is not discarded due to insufficient space; Resumable interruption: When the network is unstable, the report continues from the point of interruption. The data is transmitted in segments and the interruption point is recorded. The reported data is not transmitted repeatedly, saving bandwidth. The reporting timeout retry mechanism ensures reliability. Intelligent Conflict Arbitration: Offline conflicts between multiple devices are automatically arbitrated based on version number, timestamp, and device priority rules to avoid data overwriting errors; inconsistent states are allowed during offline periods, and conflicts are only arbitrated after recovery, creating a closed-loop logic; Fine-grained storage management: circular queue + priority cleanup, high-priority data is not overwritten by low-priority data; overwrite operations are performed at the head of the queue, without affecting the writing of new data; Data integrity guarantee: CRC32 checksum mechanism prevents data corruption, and corrupted data is automatically discarded; User traceability: The conflict log records all arbitration processes, which users can view and export, and the retention period can be set; Offline identity authentication: After a user registers for the first time, a unique identity feature code is cached locally, eliminating the need for online authentication when offline; Offline Supervisor Handling: Automatically elects a temporary supervisor, temporarily stores data, and synchronizes it after recovery to ensure continuous system operation; Technological synergy: This system integrates a distributed housekeeping system and a patented full-scenario status synchronization system, forming a complete closed loop of "online real-time synchronization + offline temporary storage and retransmission + high availability of housekeeping".

Claims

1. An offline multi-scenario collaborative and data synchronization system based on a photoconductive film, characterized in that, include: The unified identity authentication center is used to collect the optical spectral characteristics of the user's human body through the optical guide film and generate a unique identity feature code, which serves as the identity basis for offline data synchronization. Users complete identity verification upon initial registration, and their identity is identified offline using a unique identity feature code cached locally. The offline data storage module is used to temporarily store the status change events generated by each application scenario in the local storage of the sub-manager when the communication between the sub-manager and the main manager is interrupted. Each record includes the status change event ID, scenario identifier, status type, status value, timestamp, version number, and priority level. The priority sorting module is used to sort the temporary data according to the priority level of the state change event, and high-priority data is retained and uploaded first; the sorting is performed in real time when the data is written to the temporary queue to ensure that the queue always maintains the priority order. The network recovery synchronization module is used to automatically report temporarily stored offline data to the main manager when the network is restored. The main manager processes the data according to priority and synchronizes it to all relevant scenarios. The reporting adopts a fragmented transmission mechanism. Each record is transmitted in fragments of a fixed size. The fragment sequence number and the current record ID of the sub-manager record are used as breakpoints. When the network is interrupted, the breakpoint is saved and the reporting continues from the breakpoint after the network is restored. The conflict arbitration module is used to determine the final state according to preset arbitration rules when multiple devices make conflicting changes to the same state while offline. The arbitration result is pushed to all relevant devices and a conflict log is recorded for users to view. Inconsistent states are allowed among devices during offline periods, and conflict arbitration is only executed by the administrator after the network is restored. The storage space management module is used to manage the local temporary storage space of the sub-manager. When the temporary storage space is insufficient, it will automatically clean up low-priority or expired data. The offline manager response module is used to automatically elect the highest priority sub-manager among online devices as a temporary manager when the manager device goes offline. The temporary manager is responsible for receiving offline data from other sub-managers, temporarily storing it, and arbitrating conflicts. Once the original manager returns to online, the temporary manager will synchronize the temporary data to the original manager and resume the original manager's duties.

2. The system according to claim 1, characterized in that, In the priority sorting module, the priority level of state change events is consistent with the scenario priority: life safety scenarios have the highest priority; property safety scenarios are second; social service scenarios are third; health monitoring scenarios are fourth; and daily interaction scenarios have the lowest priority. Within the same priority level, sort by urgency; within the same priority level and urgency, sort by timestamp.

3. The system according to claim 1, characterized in that, In the offline data temporary storage module, each sub-manager uses a circular queue to store offline data, and the queue capacity is preset by the system; CRC32 checksum is used when writing data to prevent data corruption.

4. The system according to claim 1, characterized in that, In the storage space management module, when the temporary storage space utilization rate reaches the system's preset threshold, the system automatically cleans up the record with the lowest priority and the earliest timestamp, and records the cleanup log; when the space is full, newly generated low-priority data is directly discarded, and high-priority data overwrites the record with the lowest priority and the earliest timestamp in the queue; the cleanup operation does not affect the higher-priority data that has already been written.

5. The system according to claim 1, characterized in that, In the network recovery synchronization module, after network recovery, each sub-manager reports offline data in the following order: first, the highest priority data is reported in timestamp order; second, the next highest priority data is reported; and finally, the remaining priority data is reported in sequence. After receiving the data, the supervisor returns an acknowledgment signal, and the sub-manager deletes the reported data upon receiving the acknowledgment. If the network is interrupted again during the reporting process, the sub-manager saves the current breakpoint (current record ID and transmitted fragment sequence number), and sends a resume request to the supervisor after network recovery, carrying the current record ID and transmitted fragment sequence number. The supervisor returns the untransmitted data fragments, and the sub-manager continues reporting from the breakpoint. If the reporting times out, the sub-manager retryes the system's preset number of times. After the timeout, the data is retained for reporting after the next recovery.

6. The system according to claim 1, characterized in that, In the conflict arbitration module, when multiple devices make conflicting changes to the same state while offline, arbitration is conducted according to the following rules: The state with the highest version number will be used first; When version numbers are the same, the version with the latest timestamp is used; When timestamps are the same, the device priority rule is used; the device priority rule is preset by the user in the unified identity authentication center and stored locally in the unified identity authentication center; since the device priority rule is only queried and used by the administrator after the network is restored, it does not need to be synchronized during offline periods, thus avoiding the problem of offline synchronization being unavailable; The arbitration result is pushed to all relevant devices and a conflict log is recorded for users to view. The retention period of the conflict log is set by the user.

7. The system according to claim 1, characterized in that, In the offline response module for the supervisor, the election rules for the temporary supervisor are as follows: the online sub-supervisor with the highest device priority is selected first; if the device priorities are the same, the device with the largest storage capacity is selected; if the storage capacity is the same, the device that has communicated with the supervisor most recently is selected. The temporary manager's offline data storage uses the same circular queue and priority sorting mechanism as the sub-manager.

8. A method for offline multi-scenario collaboration and data synchronization based on photoconductive film, characterized in that, Includes the following steps: S1: Users complete identity authentication through the light guide film, establishing a unified identity across scenarios. In offline mode, identity recognition is performed through a unique identity feature code cached locally. S2: The sub-manager monitors the communication status with the main manager in real time; at the same time, the system monitors whether the main manager's device is online in real time, and if the main manager is offline, it executes the main manager offline response procedure. S3: When a network interruption is detected, the administrator will temporarily store the state change events generated by each application scenario in local storage and sort them by priority; the sorting is performed in real time when the data is written to the temporary storage queue to ensure that the queue always maintains the priority order. S4: The administrator continuously monitors the network status and retryes the connection at preset system intervals (e.g., 30 seconds). S5: When network recovery is detected, the sub-manager reports the temporarily stored offline data to the main manager in priority order; the reporting adopts a fragmented transmission mechanism, with each record being transmitted in fragments of a fixed size. The sub-manager records the transmitted fragment sequence number and the current record ID as a breakpoint. When the network is interrupted, the breakpoint is saved, and the reporting continues from the breakpoint after recovery; the system will retry a preset number of times when the reporting times out. S6: After receiving the data, the supervisor processes it according to priority and synchronizes it to all relevant scenarios; S7: When a conflict is detected, the conflict arbitration module determines the final state according to preset rules and synchronizes it to all devices; S8: After receiving confirmation from the supervisor, the sub-supervisor deletes the locally stored temporary data that has been reported.

9. The method according to claim 8, characterized in that, The offline handling process for the supervisor includes: the system automatically elects the supervisor with the highest priority among the online devices as the temporary supervisor; the temporary supervisor is responsible for receiving offline data from other supervisors, temporarily storing it, and arbitrating conflicts; when the original supervisor returns to online, the temporary supervisor synchronizes the temporarily stored data to the original supervisor and resumes the original supervisor's responsibilities.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method described in any one of claims 8-9.