Barrier gate dynamic aging application management system and method based on one-key linkage

Abstract

The invention provides a barrier gate dynamic aging application management system and method based on one-key linkage, and solves the problems of authorization rigidness, unsmooth linkage and low management efficiency of a traditional system through a dynamic aging authorization and multi-device one-key linkage mechanism. And through dynamic aging authorization and refined authority management, authorization abuse and illegal invasion are effectively prevented. And multi-device linkage verification ensures that the visitor can only move within an authorized range, so that the safety protection capability of the community is enhanced. The owner can complete visitor authorization through the mobile phone APP, and does not need to hand over an access control card or inform a password face to face; visitors can smoothly pass through a plurality of checkpoints within the authorization validity period, repeated verification is not needed, and the passing experience is improved. Property management personnel can manage all authorization records and equipment states in a centralized mode through the management platform, manual intervention is reduced through an automatic authorization process and an alarm mechanism, and the management cost is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of barrier gate, in particular to a barrier gate dynamic time limit application management system and method based on one-key linkage, an electronic device and a computer readable storage medium. BACKGROUND

[0002] The application mode of the existing barrier gate authorization system is: the authorization time limit is fixed (usually 24 hours or long-term effective), the barrier gate and the unit door and other devices are independently authorized and need to be operated respectively, the abnormal situation (such as authorization expiration, device failure) needs manual intervention for processing, and the permission management only distinguishes two levels of owners and visitors without fine control. It has the following defects:

[0003] 1. The fixed authorization time limit cannot be adjusted, which easily leads to expiration without use or illegal stay;

[0004] 2. Multiple device linkages need repeated authorization, which is tedious and low in security;

[0005] 3. Abnormal situation processing relies on manual intervention, with delayed response;

[0006] 4. The permission management has coarse granularity and cannot realize fine management and control. SUMMARY

[0007] In order to solve the technical problems existing in the prior art, the present application provides the following technical solutions:

[0008] On the one hand, a barrier gate dynamic time limit application management system based on one-key linkage is provided, which comprises a dynamic time limit control module, a linkage control terminal, a multi-device communication gateway, an owner APP and a property management platform, wherein:

[0009] The dynamic time limit control module is used for fine management and state transition control of authorization time, the linkage control terminal is used for executing a three-level event triggering and condition judgment mechanism, the multi-device communication gateway supports standardized protocol conversion for cross-system device linkage, the owner APP is used for one-key multi-device authorization and time limit setting, and the property management platform is used for device association configuration and abnormal situation processing.

[0010] On the other hand, a barrier gate dynamic time limit application management method based on one-key linkage is provided, which is implemented based on the barrier gate dynamic time limit application management system based on one-key linkage, and comprises the following steps:

[0011] (1) The visitor initiates a call through the barrier gate terminal, and the system collects the vehicle and information and pushes them to the owner APP;

[0012] (2) The owner selects the associated device and authorization time limit through the APP, generates an authorization instruction after verification is completed; and

[0013] (3) The authorization management platform uses a "broadcast-confirmation" mechanism to issue instructions to all associated devices, and the devices verify the validity of the instructions and return confirmation information;

[0014] (4) The visitor passes through the gate within the authorization validity period, and the system synchronously sends a linkage signal to the unit door, wherein the authorization validity period uses a "reference time + dynamic buffer" calculation mechanism, the reference time is a continuous time length set by the owner, and the dynamic buffer is the cumulative time consumed by the vehicle passing through each device, and the time synchronization uses the NTP protocol;

[0015] (5) The unit door remains in a pre-open state for the remaining authorization time, and the visitor automatically closes after passing through;

[0016] (6) If the visitor does not pass through in time, the system triggers a secondary verification process, and the owner generates a temporary authorization after verification;

[0017] (7) The state of all devices is synchronized in real time to the owner APP and the property management platform;

[0018] (8) When the authorization expires or the vehicle passes through all devices, the system automatically cancels the authorization and records the log;

[0019] (9) When an abnormal event occurs, a fault isolation mechanism is triggered and an alarm is sent to the property.

[0020] Preferably, the authorization process of the owner APP in step (2) includes: selecting the devices to be authorized on the map, setting the 15-minute-24-hour effective period by sliding the time axis, completing the secondary verification through fingerprint or facial recognition, and generating an authorization instruction containing the device list and validity information.

[0021] Preferably, the instruction issuing mechanism in step (3) uses ECC algorithm signature, and the device verifies the signature after receiving the instruction, checks whether the local time is within the authorization period, and returns ACK confirmation within 500ms, and fails to start 3 times of retransmission mechanism.

[0022] Preferably, the linkage signal in step (4) includes the license plate, the remaining validity period and the verification code, and the unit door verifies the signal validity after receiving it, starts the vehicle template preloading, keeps the pre-open state for 30 seconds and displays the remaining time.

[0023] Preferably, the secondary verification process in step (6) includes: pushing a notification containing a verification code to the owner APP, generating a 3-minute temporary authorization after verification, and synchronously updating the time slice state of all associated devices.

[0024] Preferably, the authorization cancellation conditions in step (8) include: authorization time expiration, authorization times exhausted, owner voluntary revocation, or vehicle passing through all associated devices, and the cancellation instruction is synchronized to all devices by broadcast.

[0025] Preferably, the abnormal event in step (9) includes device communication failure, authorization verification error and timeout non-passing, the processing mechanism includes fault isolation, manual intervention and alarm pushing, and the event priority follows "abnormal event>core event>auxiliary event".

[0026] In another aspect, an electronic device is provided, comprising: a processor; a memory having computer readable instructions stored thereon, the computer readable instructions, when executed by the processor, implement the one-key linkage based barrier gate dynamic time limit application management method described above.

[0027] In another aspect, a computer readable storage medium is provided, the storage medium having at least one instruction stored therein, the at least one instruction being loaded and executed by a processor to implement the one-key linkage based barrier gate dynamic time limit application management method described above.

[0028] The technical scheme provided by the embodiment of the application brings at least the following beneficial effects:

[0029] 1. High security: dynamic time limit authorization and fine-grained permission management effectively prevent authorization abuse and illegal intrusion. Multi-device linkage verification ensures that visitors can only move within the authorized range, enhancing the security protection capability of the community.

[0030] 2. Good convenience: owners can complete visitor authorization through a mobile phone APP without face-to-face handover of access control cards or password notification. Visitors can smoothly pass through multiple checkpoints within the authorized validity period without repeated verification, improving the passage experience.

[0031] 3. Efficient management: property personnel can centrally manage all authorization records and device states through the management platform, and the automated authorization process and alarm mechanism reduce manual intervention and reduce management costs. BRIEF DESCRIPTION OF DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiment description. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative labor.

[0033] Figure 1 is a component structure schematic diagram of a one-key linkage based barrier gate dynamic time limit application management system provided by the embodiment of the application;

[0034] Figure 2 is a flowchart of visitor calling and authorization provided by the embodiment of the application. DETAILED DESCRIPTION

[0035] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0036] In embodiments of the present invention, words such as "exemplarily," "for example," etc., are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" in the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present the concept in a concrete manner. Furthermore, in embodiments of the present invention, the meaning expressed by "and / or" can be both, or either one.

[0037] In the embodiments of this invention, the terms "image" and "picture" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning. Similarly, the terms "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning.

[0038] In this embodiment of the invention, sometimes a subscript such as W1 may be mistakenly written as a non-subscript form such as W1. When the difference is not emphasized, the meaning they express is the same.

[0039] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0040] This invention provides a dynamic time-sensitive application management system and method for barrier gates based on one-click linkage. The method can be implemented by an electronic device, which can be a terminal or a server.

[0041] In this embodiment, the hardware foundation of the barrier gate / access control system can be understood and applied in conjunction with existing barrier gate systems. The main innovation of this invention lies in solving the problems of rigid authorization, poor linkage, and inefficient management in traditional systems through dynamic time-limited authorization and a one-click linkage mechanism for multiple devices.

[0042] The specific technical content of the present invention will be described below.

[0043] 1. System Composition

[0044] 1.1 As Figure 1 As shown, hardware system

[0045] 1.1.1 Interlocking Control Terminal: Utilizing an industrial-grade PLC controller (model S7-1214C), it features 16 digital inputs and 16 relay outputs, supporting multiple industrial communication protocols such as Modbus TCP / IP and BACnet / IP. It can simultaneously connect to 8 barrier gates, 16 unit door access control systems, and 4 elevator control systems, enabling cross-system interlocking control. It has built-in dual Ethernet ports (supporting redundant communication) and a 4G module (full network compatibility), ensuring real-time data transmission between devices (latency <200ms). With an IP65 protection rating, it is suitable for operating environments from -30℃ to 70℃.

[0046] 1.1.2 Authorized terminal equipment: including the touch screen of the barrier gate control box, the owner's mobile APP, and the unit door station, etc. The barrier gate touch screen uses a 7-inch high-definition capacitive screen and supports multi-touch; the unit door station has vehicle recognition and password input functions.

[0047] 1.1.3 Timing Module: Employs a high-precision RTC clock chip, with a timing error ≤1 second / day. Supports network time synchronization to ensure time synchronization across all devices. Built-in backup battery allows the clock to operate for at least 72 hours after a power outage.

[0048] 1.1.4 Communication Gateway: An edge computing gateway (2TOPS computing power) is adopted to handle data forwarding and protocol conversion between subsystems. Supported protocols include: ONVIF (camera), WeChat / Alipay (payment interface), MQTT (IoT devices), and HTTP / HTTPS (cloud communication). A dual-redundant network (wired gigabit Ethernet + 5G industrial module) is configured, employing SD-WAN technology for automatic link switching (switching time < 1 second). A built-in data caching module (16GB storage) can locally cache 300,000 records during network interruption, automatically resuming transmission upon recovery.

[0049] 1.2 Software System

[0050] 1.2.1 Linked Authorization Management Platform: Developed based on the Java Spring Boot framework, it adopts a distributed microservice architecture. The core microservices include: ① Authorization rule engine service (responsible for relationship management and trigger condition configuration, using the Drools rule engine to parse 1:N association expressions), ② Time slice scheduling service (handles the generation and status update of 1-minute granular time slices, implemented based on the Quartz scheduled task framework), ③ Device status monitoring service (real-time collection of device operation data, sampling frequency 100ms / time, using Netty to implement TCP long connection communication), ④ Blockchain evidence storage service (interfacing with Hyperledger Fabric nodes, using the Kafka consensus mechanism to complete transaction endorsement), ⑤ User authentication service (unified identity verification, integrating OAuth2.0+JWT to achieve cross-service authorization), ⑥ Log auditing service (operation log aggregation and analysis, supporting multi-dimensional retrieval by device / time / person), ⑦ Configuration management service (dynamic parameter adjustment, based on the Apollo configuration center to achieve hot updates), and ⑧ Alarm notification service (abnormal event distribution, supporting multi-channel notifications such as SMS / APP push / audio-visual alarms). The core functions of the platform include: (1) Authorization rule engine: supports setting the 1:N relationship between the gate and the unit door (using a directed graph data structure to store the relationship, supporting many-to-many mapping), configuring linkage trigger conditions (defining the trigger logic through rule expressions, such as "gate opening event ∧ (current time ∈ authorized time slice) → unit door authorization activation"); (2) Time validity management: setting the authorization period on a visual time axis (the front end uses D3.js to draw the time axis, supports dragging and adjusting the start and end times, accurate to the minute), supporting single / multiple passage, and special rules for holidays (built-in database of Chinese statutory holidays, supporting custom special date rules); (3) Equipment status monitoring: real-time display of the gate / unit door opening and closing status (using WebSocket protocol to push status changes, the front end refreshes the status dashboard every 500ms), authorization synchronization status (green synchronized / red not synchronized), and automatically triggering property alarms when there are abnormalities (upgrading the alarm level if three consecutive synchronization failures occur); (4) Blockchain storage of operation logs: all authorization records (including equipment linkage logs, timestamps, and operators) are written to Hyperledger. Fabric consortium blockchain (each block contains 200 transaction records, the block generation interval is 10 seconds, and the SHA-256 hash algorithm is used to ensure that the data is tamper-proof) supports judicial-grade traceability (connects to notary office evidence storage nodes to provide on-chain data judicial appraisal reports).

[0051] 1.2.2 Dynamic Time-Effect Control Module: Adopts a dual control mechanism of time slicing + state machine: (1) Time Slice Management: The authorization period is divided into time slices with a granularity of 1 minute. Each time slice independently sets the permission status (allow / prohibit access) and stores it in a Redis ordered set (key is device ID + date, score is time slice number, value is permission status). It supports daily / weekly / monthly cycles (the cycle rules are defined by CRON expressions, such as "Monday to Friday 09:00-18:00"); (2) State Machine Control: Defines 5 states: "Unauthorized - Pending Verification - Authorized - Timeout - Expired". The state transition is realized through event-driven: ① Unauthorized → Pending Verification (received owner's authorization instruction) ; ② Pending verification → Authorized (secondary verification completed); ③ Authorized → Timeout (passage not completed after authorized time slice); ④ Timeout → Authorized (secondary verification passed); ⑤ Authorized / Timeout → Invalid (authorization attempts exhausted / actively revoked / time expired); (3) Secondary verification trigger: When a vehicle does not pass through the gate within the authorized time slice (timeout of 5 minutes), the secondary verification process is automatically triggered: ① Push a notification containing a time-sensitive verification code to the owner's APP (the verification code is generated based on the TOTP algorithm and is valid for 60 seconds); ② After verification, a new 3-minute temporary authorization is generated (the temporary authorization time slice covers the subsequent 3 slices of the original time slice); ③ Update the time slice status of all associated devices synchronously through the publish-subscribe mode (using the Redis Pub / Sub mechanism, the device subscribes to the corresponding channel to receive updates in real time).

[0052] 1.2.3 Terminal Application: The owner's APP (supports iOS 12.0+ / Android 7.0+) features: ① One-click multi-device authorization: Map-style selection of gates / unit doors to be authorized (based on Gaode Map SDK to render a 3D map of the community, supporting up to 5 devices; the shortest passage path is automatically calculated when devices are selected), and a sliding time axis to set the effective time period (15 minutes to 24 hours, slider increment of 5 minutes, real-time calculation and display of "estimated passage end time"); ② Dynamic status dashboard: Real-time display of the remaining authorization time for each device (using WebSocket long connection to push data, format "HH:MM:SS") and passage status (unused / passed / expired, distinguished by different colored progress bars); ③ Quick access for secondary verification: When passage is not completed within the time limit, the APP pops up a window displaying "Click to extend authorization by 10 minutes" (the pop-up uses a floating window for priority display), supporting fingerprint / facial recognition quick verification (integrating the system's biometric API, and encrypting the transmission of verification results). The property management client supports the configuration of: ① Device association (drag-and-drop interface for binding gates and unit doors, implemented based on Vue.js drag-and-drop components, with associations saved to the configuration management service in real time); ② Linkage rule templates (built-in 5 types of templates, including "Visitor Vehicle Linkage Template" [Gate + Unit Door] and "Owner Vehicle Linkage Template" [Gate + Basement + Unit Door], with support for custom template parameters); ③ Anomaly handling strategies (automatic exemption [e.g., identification of immediate family members of owners], manual review [first visit of new visitors], with configuration strategies synchronized to the authorization rule engine via API).

[0053] 1.2.4 Database System: Deployed using a MySQL cluster architecture consisting of 1 master, 2 slaves, and 3 nodes (the master node handles write operations, and the slave nodes handle read operations; high availability is achieved through MGR [MySQL Group Replication]). It features data redundancy (three copies of data are stored on each node using a RAID 5 disk array) and automatic failover (fault detection interval of 500ms, failover time <3 seconds). The database stores key data in real-time, including authorization records (using a partitioning strategy, partitioned quarterly), device status (using a Memory engine to store hot data, flushed to disk every 5 minutes), and operation logs (stored using archive tables, automatically compressing logs older than one year). Data retention is at least 3 years (historical data is archived monthly to object storage, supporting on-demand recovery).

[0054] 2. Functionality and Interaction Flow

[0055] 2.1 As Figure 2 The visitor call and authorization process shown

[0056] 2.1.1 Visitor Call: Upon arriving at the community entrance, visitors can initiate a call by entering the owner's apartment number (supporting fuzzy search using the first letter of the pinyin, e.g., entering "LYG" matches "Li owner") or scanning the gate's QR code on the touchscreen. The system automatically triggers: ① Dual-camera simultaneous data acquisition (the main camera captures a panoramic view of the vehicle [1080P resolution], and the secondary camera captures the driver's face [720P resolution], with images preprocessed for distortion correction and illumination compensation); ② Generation of a call interface with advertising space (the top 30% area rotates local merchant advertisements, with advertisement content matching nearby merchants within a 3km radius based on LBS location; clicking the advertisement redirects to the merchant's mini-program); ③ Pushing the call request to the owner's APP via APNs (iOS) / Firebase (Android), with the message priority set to "urgent," and the message bar displaying "Visitor [License Plate Number: XXXXX] requests entry." At the same time, the LED screen of the barrier gate displays "Calling the owner, please wait..." (red scrolling text, font size 48px), and the voice module plays a prompt tone (using TTS real-time synthesized voice, the volume is automatically adjusted according to the ambient noise, "Video call has been initiated, please wait for the owner's response").

[0057] 2.1.2 Owner Authorization: Upon receiving a call request, the owner's app displays a three-column linked authorization interface (using a Flexbox layout to achieve adaptive three-column design, with the left and right columns each 35% of the width and the middle column 30%): Left: Real-time video stream (using H.265 encoding to achieve 720P / 30fps transmission, with a dynamic bitrate adjustment range of 500kbps-2Mbps, supporting two-way voice intercom echo cancellation algorithm [based on NLMS adaptive filter, echo suppression >40dB]), Right: Visitor information verification area (integrating license plate recognition results [based on YOLOv5 object detection + CNN character recognition, displayed only with a confidence level >95%], vehicle feature values ​​[extracting 10-dimensional features such as body color / model / annual inspection sticker location], historical access record comparison list [sorted in descending order of access frequency]), Bottom: One-click linked authorization panel (including a quick selection box for frequently used device groups [default display of the 3 most recently used device combinations]). The system features a dynamic time-efficiency adjustment slider [baseline time 5-120 minutes, with real-time calculation of "estimated total time = baseline time + number of devices × 5-minute buffer"] + an emergency cancellation button [highlighted in red, clicking triggers a 10-second countdown confirmation]. The terminal page defaults to displaying "Common Linkage Combinations" (main entrance gate + corresponding unit door, intelligently recommended based on owner's historical authorization data). Owners can select or add devices with a single click (supports multi-selection across buildings, up to 5 devices, automatically optimizing the passage order when multiple selections are made). Dragging the slider sets the base authorization time, and the system automatically displays the dynamic buffer estimated time. Clicking the "Linkage Authorization" button triggers secondary verification (vehicle recognition uses the ArcFace algorithm [face recognition accuracy 99.8%], fingerprint verification supports the FIDO standard [anti-relay attack]), generating a chain authorization token upon successful verification. The core structure of the chained authorization token includes: ① a chained sequence of device UUIDs (unique identifiers of devices ordered by access sequence, such as ["D-001", "U-003"]), ② a UTC timestamp interval accurate to milliseconds (startTime: 1620000000000, endTime: 1620003600000), ③ a digital signature based on the ECC secp256r1 curve (the token content is encrypted with a SHA-256 hash value using the platform's private key, and the public key is pre-installed in each device), and ④ a dynamic buffer factor (an additional time-sensitive compensation value automatically calculated based on the number of devices, formula: buffer factor = number of devices × 5 minutes). This token uses a chained structure design; the access records (including timestamps and device signatures) of preceding devices automatically activate the authorization status of subsequent devices, achieving inter-device status linkage. The APP displays the device linkage status dashboard in real time (green √ indicates synchronization has been completed, yellow ○ indicates pending confirmation, and red × indicates synchronization failure. The synchronization status is refreshed every 200ms). It also pushes advertising revenue notifications ("Advertising revenue of 0.3 yuan for this call has been received." Revenue data comes from the advertising management service).

[0058] 2.1.3 Permission Issuance: The linkage authorization management platform adopts a distributed node synchronization mechanism (based on the Raft consensus algorithm to ensure data consistency among at least 3 nodes). It broadcasts authorization instructions to the associated device group through a 5G industrial communication gateway (EC-IoT-GW model supporting edge computing, locally caching the most recent 100 authorization instructions, and using the MQTT-SN protocol [QoS=1 to ensure message delivery at least once]). The instruction data packet structure is: {Authorization Code: UUID-128 bits, Validity Period: UTC timestamp interval, Device List: [{ID:xxx, Type: Barrier Gate, IP:192.168.1.xx}, {ID:yyy, Type: Unit Door, IP:192.168.1.yy}], Dynamic Buffering Rule: 5 minutes / device, Verification Code: HMAC-SHA256 (Authorization Code + Timestamp)}. Upon receiving the data, the device performs three layers of verification: ① ECC-256 signature verification (using the secp256r1 curve; the verification public key is stored in the device's security chip; if signature verification fails, the command is immediately discarded); ② NTP timestamp calibration (synchronizing to the Alibaba Cloud NTP server; deviation from the server must be <100ms; if the deviation exceeds the threshold, authorization is rejected); ③ Device whitelist matching (verifying both MAC address and device certificate; the whitelist is updated daily at 3 AM from the configuration management service). After successful verification, the local authorization state machine is updated (using a finite state machine model; state changes are recorded in the local log) and an ACK is returned (containing device ID + timestamp + execution result, in JSON format). If no response is received within 500ms, exponential backoff retransmission is initiated (3 retransmissions at intervals of 200ms / 400ms / 800ms to avoid network congestion). After all devices are confirmed, the data is synchronously written to the blockchain for storage (using the Hyperledger Fabric consortium blockchain, the block contains the device response timestamp, authorization record hash value, Merkle root hash, and the transaction is confirmed by the endorsement node [property server] signature). In case of abnormality, the property platform will trigger a graded alarm (red pop-up screen [emergency] + sound prompt [110dB beep] + SMS notification [property manager], with processing priority distinguished according to the abnormality level [level 1-5]).

[0059] 2.1.4 Visitor Access: When a visitor arrives at the first gate within the authorization period, the license plate recognition module completes license plate matching within 1 second (using image preprocessing [deblurring / denoising] → license plate localization → character segmentation → character recognition process, comparing the recognition result with the license plate number in the authorization token). Simultaneously, the gate opens and sends a linkage signal to the associated unit door (using lightweight transmission via the CoAP protocol; the signal content includes the license plate, remaining validity period, and the timestamp of the preceding device's passage). The unit door remains pre-open for 30 seconds (a countdown is displayed on the unit door's screen). Upon arrival, the visitor opens the door via vehicle recognition (compared in real-time with the authorized vehicle database) or by entering an authorization code (the authorization code is the last 6 digits of the UUID in the token, dynamically generated). If a visitor fails to pass through the gate within the authorized time limit, the system will immediately trigger secondary verification: ① Push a "Timeout Not Passing" reminder to the owner's APP (including a 30-second countdown, which will be automatically canceled if no action is taken after the countdown ends); ② The owner can choose to "Extend Authorization by 10 Minutes" (requires re-verification of identity and generation of a new timestamp interval) or "Cancel Authorization" (immediately broadcasts a permission expiration command); ③ If no action is taken within the time limit, all device authorizations will be automatically revoked (and the device's local authorization cache will be cleared simultaneously).

[0060] 2.1.5 Permission Expiration: The system triggers the permission expiration process when any of the following conditions are met: ① Authorization time expires (a "Authorization is about to expire" reminder is pushed to the owner's APP 1 minute in advance, triggered by a local scheduled task); ② Authorization attempts are exhausted (in multi-pass mode, the authorization expires automatically after the number of passes reaches a set threshold); ③ Owner actively revokes authorization (clicking "Revoke" on the "My Authorizations" page in the APP triggers the permission issuance process broadcast expiration command); ④ Vehicle has passed through all associated devices (the expiration process is triggered within 5 seconds after the last device passes through). The permission expiration command is broadcast to all devices (using the same transmission protocol and verification mechanism as the authorization command). The devices immediately update their authorization lists and return the execution result (the execution result includes status codes such as "Expiration successful" / "Device offline"). The management platform generates an "Authorization Lifecycle Report" (including the passage records of each device [passage time / time consumed], validity period usage [actual usage time / total authorization time], and abnormal events [such as the number of synchronization failures]).

[0061] 2.2 Multi-device linkage control process

[0062] 2.2.1 Gate and unit door linkage: When the gate system completes license plate recognition (using the YOLOv5+EasyOCR combined model to recognize the license plate, the recognition time <800ms, the character recognition accuracy rate ≥99.5%, and the inference is accelerated through TensorRT) and raises the pole, it immediately sends a pre-authorization signal to the unit door through a low-latency linkage channel (based on 5G slicing technology, the end-to-end latency <20ms, and the network slice ID is preset to 0x000A). The signal is transmitted through a TLS1.3 encrypted session channel: ① The clear text of the visiting vehicle license plate; ② The remaining authorization time (accurate to seconds, in the format YYYYMMDDHHMMSS, based on NTP calibrated time); ③ The dynamic verification code (the CRC32 value based on the license plate + timestamp + device key, where the device key is a 32-bit random number preset in the device security chip). The unit door access control system performs four-step verification: 1) Verification code timeliness (the timestamp deviation ≤5 seconds, and it will be rejected and the time synchronization exception log will be recorded if it times out); 2) License plate white list matching (supporting exact matching, such as "Beijing A88888" and "Beijing A8888 hanging" are judged as unmatched, and fuzzy matching needs to be enabled by the owner in the APP in advance); 3) Vehicle template pre-loading (retrieving the 1:1 comparison template stored during authorization from the local cache, the cache path is / opt / device / template / , using the LRU eviction policy, and caching up to 100 templates at most); 4) Device status self-check (camera focal length / door lock motor current / network connectivity, and it will enter the degraded mode if any of them is abnormal). After the verification passes: ① Keep the electromagnetic lock in a pre-sucked state (automatically released after 30 seconds of timeout, and the LED will flash for 5 seconds before release to remind); ② The vehicle recognition device enters the fast comparison mode (the threshold is set to 92 points, based on the ROC curve analysis, the misrecognition rate ≤0.1%, and the comparison time ≤300ms); ③ The terminal LED screen dynamically displays "The gate linkage is being authorized, and there are XX seconds remaining | License plate: Beijing A88888" (red digital countdown). If the verification fails (such as the timestamp exceeding the tolerance), it will immediately send the device linkage exception log (including the original signal packet, error code [such as 0x02 = verification code invalidation], and device status snapshot) to the property platform, and start the local audible and visual alarm (the red light flashes 2 times per second + 3 beeps of 110dB prompt sound).

[0063] The gate license plate recognition system adopts a two-stage "YOLOv5+EasyOCR combined model to recognize the license plate", and the specific principle is as follows:

[0064] 1). Image preprocessing and input optimization

[0065] Image acquisition and preprocessing: After the gate camera captures the vehicle image, it first performs preprocessing operations, including:

[0066] Distortion correction: Correct the lens distortion through the camera internal parameter matrix (obtained by pre-calibration) to ensure the accurate geometric shape of the license plate area;

[0067] Illumination compensation: The Retinex algorithm is used to enhance the image contrast under backlight / strong light conditions, and the brightness distribution is adjusted through gamma correction to avoid overexposure or underexposure that could cause character blurring.

[0068] Size normalization: The image is scaled to 640×640 pixels (YOLOv5 standard input size) and RGB channels are normalized (pixel values ​​are mapped to the [0,1] range) to reduce the computational cost of the model.

[0069] 2) License plate localization based on YOLOv5 (target detection stage)

[0070] Network architecture: Employs a lightweight YOLOv5s model (balancing speed and accuracy), the core of which includes:

[0071] Backbone: CSPDarknet53 network, which reduces redundant gradient computation through cross-stage local connectivity (CSP) structure and extracts image features at 5 scales (80×80, 40×40, 20×20, 10×10, 5×5).

[0072] Neck: The PANet structure integrates multi-scale features through bottom-up feature pyramids and top-down path aggregation, enhancing the detection capability of small targets (such as distant license plates);

[0073] Head: The detection head outputs the bounding box coordinates (x, y, w, h), confidence score (wh whether it is a license plate), and class probability (only for the "license plate" class).

[0074] Anchor mechanism: Based on the rectangular features of the license plate (width-to-height ratio of approximately 3:1), three sets of anchor boxes are preset (such as [10,20], [20,40], and [40,80]). The anchor size is optimized through the K-means clustering algorithm to improve the positioning accuracy.

[0075] Accelerated inference: Mosaic data augmentation (randomly stitching 4 images) is enabled during model training to improve generalization ability. During the inference stage, the PyTorch model is converted into TensorRT Engine through TensorRT to achieve layer fusion, precision quantization (FP16 mixed precision) and automatic kernel tuning, compressing the detection time of a single image to less than 300ms.

[0076] 3) Character recognition based on EasyOCR (OCR stage)

[0077] Character segmentation: Secondary processing is performed on the license plate area output by YOLOv5.

[0078] Skew correction: Detect the skew angle of the license plate (within ±15°) through the minimum bounding rectangle algorithm, and use affine transformation to correct it into a horizontal rectangle;

[0079] Character region extraction: Segment characters based on the projection method (accumulating pixel gray values in the vertical direction), remove interference regions such as borders and rivets, and obtain 7 character sub-images (standard format of Chinese license plates: 1 Chinese character + 1 letter + 5 characters).

[0080] Character recognition model: EasyOCR adopts the "CNN + RNN + CTC" architecture:

[0081] CNN feature extraction: Use ResNet-34 as the backbone network to extract 256-dimensional feature vectors from character sub-images;

[0082] RNN sequence modeling: Learn the character sequence dependency relationship through bidirectional LSTM (Bi-LSTM) (for example, after "Zhe A", it is more likely to be followed by numbers rather than letters);

[0083] CTC decoding: For the problem of character spacing variation, adopt the connectionist temporal classification (CTC) algorithm to realize the recognition of variable-length character sequences without manual alignment of labels, and output the final license plate string (such as "Zhe A88888").

[0084] Accuracy optimization: Ensure the character recognition accuracy ≥99.5% through the following mechanisms:

[0085] Dictionary constraint: Only retain character combinations that conform to Chinese license plate rules (for example, the first digit is the abbreviation of the province, the second digit is a letter, and the last five digits are letters / numbers);

[0086] Error correction: Based on the edit distance algorithm, compare the recognition result with the license plate character library, and automatically correct similar characters (such as "0" and "O", "8" and "B").

[0087] 4). Underlying optimization for TensorRT accelerated inference

[0088] Model conversion and optimization:

[0089] ONNX intermediate representation: Export the trained YOLOv5 and EasyOCR models to the ONNX format to unify the model structure description;

[0090] TensorRT Engine generation: Parse the ONNX model through TensorRT and perform:

[0091] Layer fusion: Combine convolution, activation function (ReLU), and batch normalization (BN) into a single computing unit to reduce the number of kernel calls;

[0092] Precision quantization: FP16 precision is used by default (FP32 is retained for some critical layers). Under the premise of precision loss <0.5%, memory usage is reduced by 50% and the calculation speed is increased by 2 times.

[0093] Dynamic Shape Optimization: For license plate images at different distances (size changes), enable Dynamic Shape inference to avoid recompiling the engine.

[0094] Hardware acceleration adaptation: The barrier gate control terminal is equipped with an NVIDIA Jetson TX2 embedded AI chip (1.3GHz Denver 2 CPU + 256-core Pascal GPU). TensorRT performs convolution and matrix operations in parallel through CUDA cores, keeping the end-to-end recognition time within 800ms (300ms for target detection + 500ms for character recognition), meeting the real-time passage requirements of the barrier gate.

[0095] 5) Coordination with the barrier gate linkage system

[0096] The recognition results (license plate string, confidence score, and location coordinates) are transmitted in real time to the linkage control terminal via the Modbus TCP protocol, serving as the core basis for subsequent authorization verification.

[0097] If the license plate matches the authorized list and the confidence level is ≥95%, the barrier gate will be raised directly.

[0098] If the confidence level is less than 95% (e.g., the license plate is damaged), a secondary verification will be automatically initiated (e.g., requiring a verification code to be entered) to ensure a balance between security and traffic efficiency.

[0099] Through the combination of the above technologies, the system achieves fast and accurate license plate recognition in complex scenarios, providing key technical support for dynamic time-sensitive authorization and multi-device linkage.

[0100] 2.2.2 Unit Door and Elevator Interlock: After the unit door opens (the door lock sensor detects the latch retraction signal), the access control system sends a floor authorization command to the elevator control system via the Modbus TCP protocol. The command format is [Device Address 0x01][Function Code 0x06][Register Address 0x0001][Authorized Floor Value], and the data field uses CRC16 verification. After receiving the command, the elevator controller: ① Immediately responds with ACK (response code 0x00 indicates successful reception); ② Cuts off the circuit path of unauthorized floor buttons through the relay module (only the authorized floor buttons are powered, and hardware-level locking prevents tampering); ③ The LED screen inside the car displays "Authorized Floor: Floor X" and plays a prompt tone "Elevator authorized, please press the floor button". After a visitor enters the elevator and presses the authorized floor button, the elevator starts running. Upon reaching the target floor: ① The weighing sensor detects a change in load (the person leaves the elevator); ② After 3 seconds, an authorization record clearing command is triggered (clearing the value of elevator controller register 0x0001 to 0x00); ③ The authorization record (including floor, time, and device ID) is saved to the elevator's local log (path / var / log / elevator / access.log) and simultaneously uploaded to the property management platform.

[0101] 2.2.3 Abnormal Situation Linkage: The system classifies abnormalities into three categories based on severity: 1) Physical intrusion (forced opening of the barrier gate, sensor damage, violent dismantling of equipment); 2) Status anomalies (unit door not closed for more than 30 seconds, equipment offline for more than 1 minute, authorization synchronization failure); 3) Data anomalies (license plate recognition error rate exceeding 5%, timestamp deviation exceeding 10 seconds). Anomaly detection mechanisms: ① Physical intrusion is detected through vibration sensors + infrared beams (sampling frequency 1kHz, trigger threshold 800mV); ② Status anomalies are monitored through device heartbeat packets (sent every 30 seconds, offline if not received within the timeout); ③ Data anomalies are analyzed in real time through edge nodes (error rate is statistically analyzed using a 5-minute sliding window). Emergency response priority: Physical intrusion > Data anomaly > Status anomaly. Specific measures include: ① Immediately lowering the barrier gate (motor reverses to the mechanical lock position, simultaneously cutting off the gate lifting control circuit); ② Unit door audible and visual alarm (110dB buzzer + red flashing light, continuously triggered until manual reset); ③ Activating local authorization cache when the device is offline (retaining the 10 most recent authorization records, automatically synchronizing upon network connection). Alarm information is pushed to the property management platform via the MQTT protocol, including: anomaly occurrence time (UTC accurate to milliseconds), device ID (e.g., D-001-U1), anomaly type code (0x01=physical intrusion, 0x02=status anomaly), and the URL of the captured image (stored on the local NVR, path rtsp: / / 192.168.1.100 / stream / anomaly ID).

[0102] 3. Summary of Technical Advantages: This system achieves efficient and secure linkage authorization management through the following technological innovations: 1) Dynamic timeliness control mechanism: Adopting dual management of time slicing and state machine, the authorization accuracy is improved to the minute level, resolving the contradiction between security and user experience caused by traditional fixed timeliness; 2) Chained authorization token design: Through the chained sequence of device UUIDs and ECC encrypted signature, the authorization instructions are tamper-proof and the linkage between devices is orderly; 3) Distributed microservice architecture: Eight core microservices are independently deployed and elastically expanded, supporting the processing of 300+ authorization requests per second; 4) Multi-dimensional security verification: Integrating ECC signature, NTP calibration, device whitelist and other multi-layer protection, the anti-relay attack capability reaches financial-grade standards; 5) Low-latency device linkage: Based on 5G slicing and edge computing, the signal transmission latency from the barrier gate to the unit door is <20ms, ensuring smooth passage; 6) Intelligent anomaly handling: The combination of hierarchical alarms and automatic emergency response improves anomaly handling efficiency by 80% and reduces manual intervention costs.

[0103] 3. Control Logic

[0104] 3.1 Dynamic Time-Based Control Logic

[0105] 3.1.1 Authorization Time Calculation: The system adopts a two-factor dynamic timeliness model: Baseline Time = Owner-set Value (5-120 minutes, step size 5 minutes), Dynamic Buffer = ∑(Equipment Access Time + Path Compensation Time). Equipment access time is defined as: 15 seconds / gate (including license plate recognition + gate lifting action), 10 seconds / unit door (vehicle recognition + door opening action), 5 seconds / floor elevator (stopping + door opening / closing); Path compensation time is calculated based on the community topology map (e.g., from the main entrance to the unit door of Building 3, the default compensation is 2 minutes). Formula: Total Authorization Timeliness = Baseline Time + ∑(Equipment Access Time × 1.5) + Path Compensation Time. Example: If the owner sets the baseline to 60 minutes, and the visitor passes through the main entrance gate (15 seconds) → the unit door of Building 2 (10 seconds) → the elevator (3 floors × 5 seconds = 15 seconds), with a path compensation of 2 minutes, then the total timeliness = 60 + [(15 + 10 + 15) / 60 × 1.5] + 2 ≈ 65 minutes. Time calculation is accurate to the second, and the clocks of all devices are synchronized using the NTPv4 protocol (synchronization period of 1 minute, deviation controlled within ±50ms). It supports automatic time zone calibration (including daylight saving time rule base) and leap second compensation mechanism.

[0106] 3.1.2 Time Validity Verification: When the device receives an authorization request, it first checks whether the current time is within the authorization validity period. If it is within the validity period, it performs the corresponding door opening / bar raising operation; if it has exceeded the validity period, it rejects the request and returns a "Authorization expired" message.

[0107] 3.1.3 Time Synchronization Mechanism: All devices synchronize their time with the time server periodically (by default, hourly) via the NTP protocol. If the time difference between the device and the server exceeds 5 minutes, the system will automatically issue a time anomaly alarm to remind property management personnel to check the network and device status.

[0108] 3.2 Linkage Control Logic

[0109] 3.2.1 Event-triggered linkage: A visual linkage configuration mechanism is adopted on the terminal page, which allows owners to customize the event-action mapping relationship in the "Linkage Rules" interface of the APP.

[0110] The system has a preset three-level event engine:

[0111] (1) Core events (gate opening / unit door authorization): trigger cross-system device cascading actions, such as the main entrance gate opening → synchronously pushing linkage signal to the unit door (including license plate, remaining time, vehicle template index) + elevator pre-stop instruction (specified floor), and the terminal page displays the progress bar "Linking in progress: gate → unit door → elevator" in real time;

[0112] (2) Auxiliary events (exceeding time limit / authorization about to expire): Trigger the tiered reminder process. If the vehicle does not pass through the gate within 10 minutes, a countdown dialog box will pop up on the terminal page (you can click "extend 10 minutes" or "cancel immediately" within 30 seconds), and a push notification (vibration + ringtone reminder) will be sent simultaneously.

[0113] (3) Abnormal events (device communication failure / authorization verification error): Execute fault isolation strategies, such as when the unit door goes offline → the gate system suspends linkage and displays "Unit door failure, switched to independent authorization mode" on the terminal page, and sends an alarm message containing the fault code to the property management. The event priority is dynamically adjusted through a weighted scoring algorithm (abnormal event weight 1.0 > core event 0.7 > auxiliary event 0.3) to ensure priority response to emergencies.

[0114] 3.2.2 Condition Judgment Mechanism: The execution of a linked action requires the following conditions to be met:

[0115] (1) Identity consistency: The license plate / vehicle identified by the barrier gate and the unit door must be completely matched (slight damage is allowed, similarity ≥95%).

[0116] (2) Time continuity: The time interval between the authorization time of the preceding device and the verification time of the current device shall be ≤30 minutes (to prevent authorization abuse);

[0117] (3) Status validity: All associated devices are in normal working condition (no faults, network is unobstructed);

[0118] (4) Completeness of permissions: Includes complete authorization chain information (authorization code, device list, remaining validity period). If any condition is not met, the linkage will be refused, an exception log will be recorded, and the property management will be notified.

[0119] 3.2.3 Fault Isolation Mechanism: When a subsystem fails, the linkage control terminal automatically isolates the faulty system to ensure that other systems are not affected. For example, if the unit door access control fails, the barrier gate system can still work normally, but it will stop sending linkage signals to the unit door.

[0120] Therefore, the above solution can solve the following corresponding technical problems:

[0121] (1) Authorization timeliness issue: Traditional access control authorizations are often valid for a long time, which poses a security risk. This solution uses a dynamic timeliness control module to achieve refined management of authorization time. Visitors can only pass within the authorization validity period, and the authorization will automatically expire after that, effectively reducing the risk of authorization abuse.

[0122] (2) Problem of poor linkage between multiple devices: Barrier gates, access control and elevator systems from different manufacturers often use proprietary communication protocols, making it difficult to achieve linkage control. This solution solves the problem of interconnection between devices across systems and manufacturers through communication gateways and standardized interfaces, and achieves a seamless experience of "one-time authorization, multiple access".

[0123] (3) Cumbersome authorization process: Traditional authorization methods require owners to remember complex passwords or carry access cards, which is inconvenient. This solution simplifies the authorization process through the "one-click authorization" function of the owner's APP. Owners do not need to remember passwords, but only need to set the authorization time and scope, which improves the user experience.

[0124] (4) Property management efficiency issues: Property management requires manual verification of visitor identities and registration of authorization information, which is labor-intensive and inefficient. This solution, through automated authorization processes and real-time monitoring, allows property staff to remotely view and manage all authorization records, with automatic alarms for abnormal situations, significantly improving management efficiency.

[0125] (5) System compatibility issues: Equipment built at different times within the community often comes from different manufacturers, and protocol incompatibility leads to the inability to link together. The communication gateway of this solution supports multiple industry standard protocols and mainstream manufacturer proprietary protocols, which can quickly connect to existing equipment, protect the community's existing investment, and reduce system upgrade costs.

[0126] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0127] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0128] In this invention, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be a single item or multiple items.

[0129] It should be understood that, in various embodiments of the present invention, the order of the above-mentioned process numbers does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0130] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0131] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the devices, apparatuses, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0132] In the several embodiments provided by this invention, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0133] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0134] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0135] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0136] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A dynamic time-based application management system for barrier gates based on one-click linkage, characterized in that, This includes a dynamic time-based control module, a linkage control terminal, a multi-device communication gateway, a homeowner's app, and a property management platform, among which: The dynamic timeliness control module is used for fine-grained management of authorization time and state transition control; the linkage control terminal is used to execute a three-level event triggering and condition judgment mechanism; the multi-device communication gateway supports standardized protocol conversion for cross-system device linkage; the owner APP is used for one-click multi-device authorization and timeliness settings; and the property management platform is used for device association configuration and anomaly handling.

2. A dynamic time-based application management method for a barrier gate based on one-key linkage, implemented based on the dynamic time-based application management system for a barrier gate based on one-key linkage as described in claim 1, characterized in that, Includes the following steps: (1) Visitors initiate a call through the gate terminal, and the system collects vehicle and information and pushes it to the owner's APP; (2) The owner selects the associated device and authorization period through the APP, and generates an authorization command after completing the verification; (3) The authorization management platform uses a "broadcast-confirmation" mechanism to send instructions to all associated devices, and the devices verify the validity of the instructions and return confirmation information; (4) When a visitor passes through the gate within the authorized time limit, the system synchronously sends a linkage signal to the unit door. The authorized time limit adopts the "base time + dynamic buffer" calculation mechanism. The base time is the duration set by the owner, the dynamic buffer is the cumulative time taken for the vehicle to pass through each device, and the time synchronization adopts the NTP protocol. (5) The unit door remains in a pre-open state for the remaining authorized time and closes automatically after the visitor passes through; (6) If passage is not granted within the time limit, the system will trigger a secondary verification process. After the owner verifies the information, a temporary authorization will be generated. (7) The status of all equipment is synchronized to the owner's APP and property management platform in real time; (8) When the authorization expires or the vehicle passes through all devices, the system will automatically cancel the authorization and record the log. (9) When an abnormal event occurs, the fault isolation mechanism is triggered and the property management is alerted.

3. The method according to claim 2, characterized in that, The authorization process of the owner's APP in step (2) includes: selecting the devices to be authorized on a map, setting the effective time period from 15 minutes to 24 hours by sliding the time axis, completing secondary verification through fingerprint or facial recognition, and generating an authorization instruction containing the device list and time information.

4. The method according to claim 2, characterized in that, The instruction delivery mechanism in step (3) uses ECC algorithm signature. After receiving the instruction, the device verifies the signature, checks whether the local time is within the authorized time period, and returns ACK confirmation within 500ms. If it fails, the 3-retransmission mechanism is started.

5. The method according to claim 2, characterized in that, The linkage signal in step (4) includes the license plate, remaining time limit and verification code. After receiving the signal, the unit door verifies the validity of the signal, starts the vehicle template preloading, maintains the pre-open state for 30 seconds and displays the remaining time.

6. The method according to claim 2, characterized in that, The secondary verification process in step (6) includes: pushing a notification containing a verification code to the owner's APP, generating a 3-minute temporary authorization after successful verification, and synchronously updating the time slice status of all associated devices.

7. The method according to claim 2, characterized in that, The conditions for canceling permissions in step (8) include: the authorization period expires, the number of authorizations is exhausted, the owner actively cancels the authorization, or the vehicle passes through all associated devices. The cancellation instruction is broadcast to all devices simultaneously.

8. The method according to claim 2, characterized in that, Abnormal events in step (9) include device communication failure, authorization verification error and timeout failure to pass. The handling mechanisms include fault isolation, manual intervention and alarm push. The event priority follows "abnormal events > core events > auxiliary events".

9. An electronic device, characterized in that, The electronic device includes: processor; A memory storing computer-readable instructions that, when executed by the processor, implement the method as described in any one of claims 2 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium contains program code that can be invoked by a processor to execute the method as described in any one of claims 2 to 8.

Images