Private parking space time-sharing entry control methods and systems

Abstract

The unmanned gate systems installed in community parking lots pose a challenge to controlling the entry and exit of external vehicles when private parking spaces are shared on a time-sharing basis. This invention discloses a method and system for controlling the entry of private parking spaces shared on a time-sharing basis. By accessing the access permission table and access record table of the gate system through a synchronization module, the temporary identities of tenant vehicles and owner vehicles are replaced, achieving entry and exit control of tenant vehicles without modifying the existing gate system software. Three methods for compliant access to the access permission table and access record table by the synchronization module are provided, applicable to various common gate systems. A low-cost installation method for the synchronization module is given for both networked and offline gate system hosts. By compensating third parties, it supports scenarios such as tenant vehicles not leaving on time or owner vehicles entering early.

Description

Technical Field

[0001] This invention belongs to the field of information technology, and specifically relates to a method and system for controlling the entry of private parking spaces on a time-sharing basis. Background Technology

[0002] Parking difficulties are a common problem in large cities. Many private parking spaces within communities remain idle after vehicles leave the area. Time-sharing parking could alleviate this problem and generate income for residents. For example, the Ministry of Housing and Urban-Rural Development's "Notice on Strengthening the Management of Urban Parking Facilities" explicitly states: "Individuals are allowed to use internet information technology to rent or lend their privately owned parking facilities on a time-sharing or short-term basis and obtain corresponding income." The "Beijing Municipal Regulations on Motor Vehicle Parking" also clearly states: "The city promotes paid time-sharing of parking spaces by units or individuals. Parking facility management units should provide support and cooperation, and offer convenience."

[0003] Using online platforms is a common method for time-sharing of private parking spaces in communities. For example, Chinese patent application CN201610288467.X discloses a community parking space sharing method and its server. The lessee needs to show an order to the community management. However, most community parking lots in cities use unmanned gate systems. Chinese patent application CN202110448695.X discloses a shared parking space system based on community services, including a community management platform, a parking space sharing platform, a vehicle access control device, and a parking space monitoring device. The vehicle access control device needs to send vehicle information to the parking space sharing platform for verification; after successful verification, the access control device opens. This patent requires the development of a dedicated vehicle access control device to support the entry of external vehicles, which is too costly. Chinese patent application CN202010736892.7 discloses a shared parking space service system and method for residential areas. The method mainly includes: after a shared parking space is successfully reserved, the terminal platform system marks the shared parking space and simultaneously sends the relevant information to the community parking management system; upon entering the community, the community parking management system identifies the vehicle information entering the community and raises the barrier to allow passage, while simultaneously feeding back the relevant information to the terminal platform system; upon leaving the community, the community parking management system identifies the vehicle information leaving the community, automatically controls whether to raise the barrier to allow passage, and feeds back the departure information to the terminal platform system, while the terminal platform system cancels the mark. This patent does not explain how the reserved parking space information is sent to the community parking management system. Furthermore, the community parking management system needs to feed back departure information to the terminal platform system, indicating that the implementation of this method requires software functional modifications to the existing community parking management system.

[0004] Most urban communities have installed unattended gate systems in their parking lots, but these systems vary in manufacturer and version. Modifying the gate system's software to enable time-sharing parking spaces is technically difficult because manufacturers typically don't provide source code for third-party modification. Unauthorized modification or replacement of the original software raises legal issues and can lead to after-sales and maintenance problems. While direct system management by property management is theoretically feasible, modifying access permissions would significantly increase their workload, reducing their incentive. This approach is practically only suitable for long-term (monthly or yearly) time-sharing rentals, not short-term or temporary situations. Existing methods lack specific technical solutions for sending parking space time-sharing reservation information to the community parking lot's gate system without modifying its existing software, thus enabling tenants' vehicles to enter and exit. Furthermore, the existing method does not take into account situations where the owner's vehicle is also in the parking lot when the owner's parking space is shared with others on a time-sharing basis (such as tenant vehicles not leaving in time or owner vehicles entering the parking lot in advance). Such situations may infringe on the legitimate rights and interests of third parties (such as other owners or property management companies). Summary of the Invention

[0005] To overcome the shortcomings of the prior art, the present invention aims to provide a method and system for controlling entry into private parking spaces shared on a time-sharing basis. This method temporarily treats tenant vehicles as owner vehicles when owners share parking spaces, utilizing the functionality of the existing parking lot gate system to achieve this temporary replacement of vehicle identity and entry / exit control. Without modifying the existing gate system software, the present invention provides a technical solution for implementing the above method and system. In particular, it eliminates the need for software operation by property management units, making it suitable not only for long-term rentals but also for short-term, single-use rentals. The present invention also provides a method for calculating supplementary fees to address the problem of infringing on the legitimate rights of third parties when tenant vehicles and owner vehicles are simultaneously in the parking lot.

[0006] To achieve the above objectives, the technical solution adopted by the present invention is as follows: The method for controlling entry to private parking spaces through time-sharing includes the following steps: Step 1: The owner connects to the server through the owner's client and publishes the time-sharing information of their parking space. The parking lot where the parking space is located has a barrier gate system. The barrier gate system includes a host, an access permission table, and an access record table. The host is a control device for controlling vehicle entry and exit. The access permission table stores the license plate numbers allowed by the barrier gate system. The access record table stores vehicle access information, including license plate number, entry time, and exit time. The access permission table and access record table can be accessed through the host. The host is connected to a synchronizer, and the synchronizer is connected to the server. The synchronizer is equipped with a synchronization module. The synchronization module is a software module and is independent of the barrier gate system. Step 2: The tenant connects to the server through the tenant client, selects the time-sharing information, and enters their reserved license plate number to reserve a parking space; Step 3: The synchronization module communicates with the server to obtain the reserved license plate number, and communicates with the host to add it to the access permission table; Step 4: The barrier gate system controls the entry and exit of the vehicle corresponding to the reserved license plate number and records the vehicle passage information; Step 5: The synchronization module communicates with the host to access the access record table and determines whether the vehicle corresponding to the reserved license plate number has left the venue; if so, the reserved license plate number is deleted from the access permission table.

[0007] The private parking space time-sharing entry control method of the present invention can be further replaced in steps 1 and 2 as follows: Step 1: The tenant connects to the server through a tenant client and publishes time-sharing demand information. This time-sharing demand information includes parking spaces and reserved license plate numbers. The parking space has a barrier gate system. The barrier gate system includes a host, an access permission table, and a access record table. The host is the controller for the barrier gate system to control vehicle entry and exit. The access permission table stores the license plate numbers allowed by the barrier gate system. The access record table stores vehicle access information, including license plate number, entry time, and exit time. The access permission table and access record table can be accessed through the host. The host is connected to a synchronizer, and the synchronizer is connected to the server. The synchronizer is equipped with a synchronization module. The synchronization module is a software module and is independent of the barrier gate system. Step 2: The homeowner connects to the server through the homeowner client, selects and confirms the time-sharing requirement information; the homeowner has a parking space in the corresponding parking lot.

[0008] The private parking space time-sharing entry control method of the present invention can be further replaced in steps 1 and 2 as follows: Step 1: The owner connects to the server through the owner's client and publishes the time-sharing information of their parking space. The parking lot where the parking space is located has a barrier gate system. The barrier gate system includes a host, an access permission table, and an access record table. The host is the controller of the barrier gate system to control vehicle entry and exit. The access permission table stores the license plate numbers allowed by the barrier gate system. The access record table stores vehicle access information, including license plate number, entry time, and exit time. The access permission table and access record table can be accessed through the host. The host is connected to a synchronizer, and the synchronizer is connected to the server. The synchronizer is equipped with a synchronization module. The synchronization module is a software module and is independent of the barrier gate system. Tenants connect to the server through a tenant client to publish time-sharing demand information; the time-sharing demand information includes the reserved license plate number and parking lot; Step 2: The server matches the time-sharing information with the time-sharing demand information. If the match is successful, proceed to step 3.

[0009] In one embodiment, the method by which the synchronization module of the present invention accesses the access permission table and / or the access record table is as follows: Method 1: The access permission table and / or the access record table are stored in the host, and the synchronization module directly accesses the file storing the access permission table and / or the access record table; Alternatively, method 2: The host is equipped with interface calling software, which provides an interface for accessing the access permission table and / or the access record table. The synchronization module calls this interface to access the access permission table and / or the access record table. Alternatively, Method 3: The barrier gate system further includes barrier gate management software, which includes a front-end interface and a back-end program. The front-end interface is used for maintaining license plate numbers and / or querying vehicle passage information, and generates corresponding data packets to be sent to the back-end program. The back-end program is used to receive the data packets sent by the front-end interface, and to maintain the corresponding license plate number in the access permission table and / or read and return the corresponding vehicle passage information. The synchronization module simulates the front-end interface operation to generate corresponding data packets and sends them to the back-end program, accessing the access permission table and / or the passage record table. For example, in Method 3, before simulating the front-end interface operation to generate the corresponding data packets, the synchronization module needs to first log in to the barrier gate management software using a relevant account to establish a session; the generated data packets include session identifier information.

[0010] In one embodiment, step 3 of the present invention, in which the synchronization module communicates with the server to obtain the reserved license plate number and communicates with the host to add it to the access permission table, is implemented as follows: Method A: The host is not connected to the Internet, the synchronizer is connected to the host via a dedicated line, and the synchronizer and the server are connected to the Internet; the synchronization module accesses the server through the Internet to obtain the corresponding reserved license plate number, and then accesses the host through the dedicated line to add it to the access permission table; Alternatively, method B: The host, synchronizer, and server are all connected to the Internet; the synchronization module communicates with the server through the Internet to obtain the corresponding reserved license plate number, and then accesses the host through the Internet to add it to the access permission table.

[0011] In one embodiment, step 5 of the present invention, the method for the synchronization module to communicate with the host to access the access record table, is as follows: Method a: The host is not connected to the Internet, and the synchronizer is connected to the host via a dedicated line; the synchronization module communicates with the host via the dedicated line to access the access record table; Alternatively, method b: both the host and the synchronizer are connected to the Internet; the synchronization module communicates with the host through the Internet to access the access record table.

[0012] In one embodiment, the parking space of the present invention corresponds to the owner's license plate number, and the records in the access permission table include the owner's license plate number; The method for controlling entry into the time-sharing private parking space also includes steps to disable the owner's license plate number and steps to enable the owner's license plate number. The specific steps for disabling the owner's vehicle license plate number are as follows: The synchronization module determines whether the car corresponding to the reserved license plate number has entered the venue; if so, it deletes the corresponding owner's license plate number from the access permission table. The specific steps for enabling the owner's vehicle license plate number are as follows: When deleting the reserved license plate number from the access permission table in step 5, the corresponding owner's license plate number is added to the access permission table.

[0013] In one embodiment, the parking space of the present invention corresponds to the owner's license plate number, and the records in the access permission table include the owner's license plate number; Step 4 is followed by a step to calculate the additional fees, specifically: Determine whether the car corresponding to the reserved license plate number and the corresponding owner's car entered the parking lot at the same time; if so, calculate the supplementary fee based on the duration of simultaneous entry into the parking lot and the parking fee standard.

[0014] In one embodiment, the server of the present invention stores the parking space information of the owners in advance; only after the parking space information is approved can the corresponding owner share the parking space for a period of time; the approval is the responsibility of the management of the corresponding parking lot or the operator of the server.

[0015] In one embodiment, the communication strategy between the synchronization module and the server is real-time access or timed access; the relevant permissions required for communication between the synchronization module and the server are pre-configured; and the correspondence between the synchronization module and the parking lot is pre-configured.

[0016] This invention also provides a private parking space time-sharing entry control system, including a server and a synchronization module. The parking lot where the parking space is located has a gate system, which includes a host, an access permission table, and an access record table. The host is a control device for controlling vehicle entry and exit. The access permission table stores license plate numbers allowed by the gate system, and the access record table stores vehicle access information, including license plate number, entry time, and exit time. The access permission table and access record table can be accessed through the host. The host is connected to the synchronizer, and the synchronizer is connected to the server; the synchronizer is equipped with the synchronization module; the synchronization module is a software module and is independent of the barrier gate system. The server includes an information publishing module and a reservation generation module. These two modules are used for: owners publishing time-sharing information and tenants selecting time-sharing information and entering a reserved license plate number to reserve a parking space; or, tenants publishing time-sharing demand information and owners selecting time-sharing demand information to share a parking space; or, owners publishing time-sharing information and tenants publishing time-sharing demand information and matching and confirming the time-sharing information and the time-sharing demand information. The time-sharing information includes parking space information, and the time-sharing demand information includes parking lot and reserved license plate number. The synchronization module includes an enable module for reserving license plate numbers and a disable module for reserving license plate numbers. The enabled license plate number module is used to communicate with the server to obtain the reserved license plate number, and to communicate with the host to add it to the access permission table. The module for disabling reserved license plate numbers is used to communicate with the host to access the access record table and determine whether the vehicle corresponding to the reserved license plate number has left the venue; if so, the reserved license plate number is deleted from the access permission table.

[0017] In one embodiment, the synchronization module of the present invention includes a table access module for accessing the access permission table and / or the access record table, wherein the access method is: Directly access the access permission table and / or access record table files stored in the host; Alternatively, the interface installed on the host can be used to call the access permission table and / or access record table provided by the software. Alternatively, the front-end interface of the simulated barrier gate management software generates corresponding data packets, which are sent to the back-end program of the barrier gate management software to access the access permission table and / or access record table; the barrier gate management software belongs to the barrier gate system.

[0018] In one embodiment, the parking space of the present invention corresponds to the owner's license plate number, and the records in the access permission table include the owner's license plate number; The synchronization module also includes a module for disabling the owner's license plate number and a module for enabling the owner's license plate number. The module for disabling owner's license plate number is used to determine whether the car corresponding to the reserved license plate number has entered the venue; if so, the corresponding owner's license plate number is deleted from the access permission table. The enabled owner license plate number module is used to add the corresponding owner license plate number to the access permission table when the disabled reservation license plate number module deletes the reservation license plate number from the access permission table.

[0019] In one embodiment, the parking space of the present invention corresponds to the owner's license plate number, and the records in the access permission table include the owner's license plate number; The server or synchronization module also includes a supplementary fee calculation module, which is used to determine whether the car corresponding to the reserved license plate number and the corresponding owner's car enter the parking lot at the same time; if so, the supplementary fee is calculated based on the duration of simultaneous entry into the parking lot and the parking fee standard.

[0020] Compared with the prior art, the beneficial effects of the present invention are: 1. The designed synchronization module can add the reserved license plate number to the access permission table before entering the site and delete the reserved license plate number from the access permission table after leaving the site. Without modifying the existing gate system software functions, it realizes the control of tenant vehicles entering and leaving the site, and is suitable for time-sharing of owner parking spaces under unattended gate system conditions.

[0021] 2. Three specific methods are provided for the synchronization module to access the access permission table and / or access record table: these include directly accessing the file storing the access permission table and / or access record table, calling the access permission table and / or access record table interface provided by the barrier gate management software, and simulating the operation of the barrier gate system's front-end interface to generate corresponding data packets and send them to the barrier gate system's back-end program to access the access permission table and / or access record table. These methods are applicable to various common barrier gate systems and do not raise compliance issues regarding unauthorized access or tampering with the barrier gate management software. Furthermore, none of the above three methods require operation from the property management unit; they are implemented automatically by the software, without increasing the burden on the property management unit, thus demonstrating practicality.

[0022] 3. The synchronizer can be implemented using an embedded system, with direct hardware costs of only a few hundred yuan. The synchronizer can connect to the gate system host via a dedicated line, enabling the synchronization module to access the access permission table and access record table. This achieves time-sharing sharing of parking spaces for owners even when the gate system host is not connected to the internet, at extremely low cost. If the gate system host is connected to the internet, the synchronizer can be replaced by a server, significantly reducing hardware investment.

[0023] 4. By providing methods (or modules) for disabling and enabling owner's license plate numbers, the existing parking lot gate system's functions are utilized to temporarily replace the identities of tenant vehicles and owner vehicles and control their entry and exit, ensuring that the legitimate rights and interests of third parties (such as other owners or property management companies) are not infringed.

[0024] 5. Allow tenants to enter the premises with their cars first and pay parking fees before leaving, which can effectively prevent payment evasion.

[0025] 6. When a tenant's vehicle fails to leave the premises on time or a property owner's vehicle enters the premises early, the third party will be compensated by charging for the time period when both the tenant's and property owner's vehicles enter the premises at the same time. This also benefits both the property owner and the tenant.

[0026] 7. Only after the parking space information has been verified and approved can the corresponding owner participate in time-sharing parking space sharing, thus ensuring the authenticity of the time-sharing parking space information. Attached Figure Description

[0027] Figure 1 This is a schematic diagram of a private parking space time-sharing entry control system in an embodiment of the present invention. Detailed Implementation

[0028] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings and examples.

[0029] Example 1 This embodiment is a basic embodiment of a time-sharing access control method for private parking spaces, and may include: S101, owners connect to the server through the owner's client to publish their parking space's time-sharing information.

[0030] An owner refers to someone who owns or has the right to use a parking space. This can be the purchaser of the parking space (ownership) or a long-term tenant (such as a parking space included with a rental agreement, who has the right to use it). The owner's client can be a mobile phone, computer, tablet, or other internet-connected computer device. It can be used to log in to the server, enter parking space information, publish time-sharing information, query parking space sharing records, and check sharing revenue. The server can be a dedicated server or cloud server, or other internet-connected computer device. It can include functions such as basic information management for users (e.g., owners, tenants, property management), time-sharing information management and / or time-sharing demand information management, time-sharing confirmation, synchronization module API calls (e.g., providing the synchronization module with the corresponding reserved license plate number), parking space sharing record management, and billing management (these functions can be implemented through relevant software installed on the server). Time-sharing information includes corresponding parking space information (including parking lot information), available time periods for time-sharing parking, and may also include parking prices. Parking prices can be set by the owner or by the parking lot's regulations. Time-sharing information is usually stored on the server side so that tenants can log in to the server to query and reserve parking spaces.

[0031] The parking lot where the parking space is located in this application has a barrier gate system. Most parking lots in cities have barrier gate systems to restrict vehicle entry and exit. Barrier gate systems have control devices for controlling vehicle entry and exit, referred to as the host in this application, which are typically computer devices such as dedicated servers, industrial control computers, or embedded systems. Barrier gate systems usually also include license plate recognition devices and barrier gates, all of which are connected to the host to control vehicle entry and exit. For example, the host will check if the license plate number recognized by the license plate recognition device is included in the access permission table. If so, it will control the barrier gate to open and record the vehicle passage information. Barrier gate systems support the entry and exit of vehicles owned by parking space owners, generally by registering the owner's license plate number. The barrier gate system also records vehicle entry and exit information. Owner license plate numbers and vehicle passage information are usually stored on the host, specifically in the form of a database form or a dedicated file (such as an Excel file). Some barrier gate systems implemented using cloud platform technology may store database forms such as vehicle access information in the cloud (usually servers on the internet), but they still need to transmit relevant information to the cloud via a host computer. The cloud can be seen as an extended storage space for the host computer. The access permission table and access record table in this application refer to the database forms or dedicated files used by the barrier gate system to store owners' license plate numbers and vehicle access information. The access permission table stores the license plate numbers allowed by the barrier gate system, and the access record table stores vehicle access information, including license plate number, entry time, and exit time. The host computer needs to access the access permission table when controlling vehicle entry and exit, and it needs to access the access record table when recording vehicle access information. Therefore, both the access permission table and the access record table can be accessed by the host computer.

[0032] To achieve a time-sharing entry control method for private parking spaces without modifying the existing barrier gate system software, this application creatively designs a synchronization module. The synchronization module is a software module independent of the barrier gate system and is installed in the synchronizer. The synchronizer can be a computer device such as an industrial control computer or an embedded system (e.g., ARM, microcontroller, etc.). The synchronizer needs to connect to a host computer, which generally has corresponding connection interfaces (e.g., Ethernet interface, RS-485 interface, etc.). The synchronizer can connect to the relevant interfaces of the host computer via a dedicated line. If the host computer is connected to the Internet, the synchronizer can also be connected to the Internet. The synchronizer also needs to connect to a server, since the server is connected to the Internet, and the synchronizer can be connected to the Internet via wireless means (e.g., 5G, WIFI, etc.) or wired means (e.g., Ethernet cable).

[0033] Owners typically need to register their information on the server first for easy login. Table 1 illustrates one way owner information is implemented. The owner ID field is the keyword for owner information, used to distinguish different owners. Table 1 also includes fields for name, password (password for logging into the server), and contact information (for contacting the owner). In addition, owner information may also include payment account information (such as bank card number, Alipay account, WeChat account, etc.) to facilitate payment of parking revenue to owners.

[0034] Table 1 Owner Information Owner ID Name password Contact information E01 Zhang San abc 13900000000 E02 Li Si 123 13811111111 E03 Wang Wu 666 13322222222 Table 2 illustrates one implementation method for parking space information. The Parking Space ID field is the keyword for the parking space information. The Owner ID field is used to describe the ownership of the parking space. If each owner has only one parking space, Tables 1 and 2 can be merged. In this invention, the parking spaces are located within a parking lot, and the parking space information necessarily includes the parking lot. The Parking Lot field describes the parking lot where the parking space is located, facilitating tenant filtering. The Owner License Plate Number field describes the license plate number of the owner's car corresponding to the parking space. Table 2 also includes a Parking Space Number field, which is the number of the parking space in the corresponding parking lot (usually marked on the ground or on a tag above the parking space), to facilitate tenants in finding the parking space. To ensure the authenticity of the time-sharing information, it can be required that the parking space information be approved before the corresponding owner can share the parking space for time. The approval can be handled by the management of the corresponding parking lot or by the server operator. The Approval No field in Table 2 indicates whether the corresponding parking space information has been approved.

[0035] Table 2 Parking Space Information Parking space ID Owner ID PARKING LOT Owner's license plate number Parking space number No review S01 E01 Parking lot in Community A A11111 005 yes S02 E02 Parking lot in Community A A22222 007 yes S03 E03 B Community Parking Lot A33333 005 yes Table 3 illustrates one implementation method for time-sharing information. The serial number field is a keyword used to distinguish different time-sharing information. The parking space ID field indicates the parking space corresponding to the time-sharing information. The sharing start time and sharing end time indicate the time period during which the corresponding parking space can be shared. The parking price is the corresponding parking fee standard, which can be the price set by the owner or the parking lot price. The parking fee can belong to the owner, or it can be distributed among the owner, the platform provider (the service provider of the time-sharing parking function), and the property management company (parking lot management company) according to the agreement.

[0036] Table 3 Time-sharing information serial number Parking space ID Shared start time Shared end time Parking prices F001 S01 2025-11-26 8:00 2025-11-26 18:00 3 yuan / hour F002 S02 2025-11-26 9:00 2025-11-26 16:00 2 yuan / hour F003 S03 2025-11-26 8:00 2025-11-26 20:00 2 yuan / hour Table 4 illustrates the access permission table for the parking lot gate system in Community A, as shown in Table 2. The license plate number field indicates the license plate numbers allowed to pass through the parking lot gate system in Community A, which are usually the license plate numbers of resident vehicles. Residents typically pay the relevant fees to the property management company for direct access.

[0037] Table 4A Community Parking Lot Barrier System Access Control Table license plate number A11111 A22222 Some gate systems may also include other fields in their access permission tables, as shown in Table 5. The status field includes two categories: valid and invalid (or normal and abnormal). The gate system allows license plates with a valid (or normal) status to pass, while license plates with an invalid (or abnormal) status are not allowed to pass (such as license plates that have not paid management fees on time).

[0038] Table 5 contains access permission tables with status fields. license plate number state A11111 efficient A22222 invalid Table 6 illustrates the access records of the parking lot gate system in Community A from Table 2, including fields for license plate number, entry time, and exit time. From the records in Table 6, we can see that: vehicle with license plate number A11111 entered the parking lot at 19:00 on November 25, 2025, and left at 7:00 on November 26, 2025, indicating that this vehicle was not in the parking lot; vehicle with license plate number R11111 entered the parking lot at 9:00 on November 26, 2025, and its exit time is blank, indicating that this vehicle is still in the parking lot and has not yet left.

[0039] Table 6A Community Parking Lot Barrier System Access Record Sheet license plate number Entry time Departure time A11111 2025-11-25 19:00 2025-11-26 7:00 R11111 2025-11-26 9:00 Some gate systems may record entry and exit separately in their access logs, as shown in Table 7. Table 7 is essentially the same as Table 6, and the implementation method of Table 6 will be used for explanation below.

[0040] Table 7. Separate Passage Records license plate number Passage time Passage type A11111 2025-11-25 19:00 Entrance A11111 2025-11-26 7:00 leaving R11111 2025-11-26 9:00 Entrance S102, the tenant connects to the server through the tenant client, selects time-sharing information and enters their reserved license plate number to reserve a parking space.

[0041] A tenant refers to a user who intends to rent a time-sharing parking space. The tenant's client can be a mobile phone, computer, tablet, or other internet-connected computer device, used to log in to the server, query time-sharing information, reserve parking spaces, check parking records, and pay parking fees. When selecting time-sharing information, tenants should consider the intended parking time period to avoid time conflicts. When the server provides time-sharing information to the tenant's client, the corresponding shareable time period should be valid. For example, in Table 3, if the current time is 19:00 on November 26, 2025, only the time-sharing information for parking space S03 is valid, and the shareable time period is from 19:00 to 20:00 on November 26, 2025. When reserving a parking space, tenants should typically enter the reserved license plate number (i.e., the license plate number of the car intending to park in the corresponding space), which the server records. Tenants can also modify the reserved license plate number before entering the parking space (e.g., if the original vehicle breaks down and a new vehicle is used). Tenants can choose not to enter the license plate number when reserving a parking space (for example, if a tenant is reserving a parking space for someone else and the license plate number is not yet known), but they must enter the license plate number before entering the premises.

[0042] Tenants typically need to register their tenant information first to facilitate server login. Table 8 illustrates one implementation method for tenant information. The Tenant ID field is the keyword for tenant information, used to distinguish different tenants. The reserved license plate number field is the default value for the reserved license plate number when reserving a parking space (i.e., this reserved license plate number will be automatically filled in when reserving a parking space).

[0043] Table 8 Tenant Information Tenant ID Name password Contact information Reserved license plate number R01 Zhao Liu xyz 13922222222 R11111 R02 Sun Qi 987 13855555555 R22222 Table 9 illustrates one implementation method for server-side information recording when reserving a parking space. The reservation number field is the key used to distinguish different reserved parking spaces. The parking space ID field describes the corresponding time-sharing parking space. The tenant ID and reserved license plate number fields represent the corresponding tenant and the license plate number of the vehicle to be parked. The proposed start time and proposed end time fields are used by the tenant to input the proposed parking time period, facilitating subsequent rental of the corresponding parking space during other available time periods. The actual start time and actual end time fields record the actual entry and exit times of the tenant's vehicle (obtainable from the access record table). The parking fee field stores the corresponding parking fee payable by the tenant.

[0044] Table 9 Parking Space Reservation Information Appointment number Parking space ID Tenant ID Reserved license plate number Proposed start time Proposed end time Actual start time Actual end time Parking Fee B001 S01 R01 R11111 2025-11-26 8:00 2025-11-26 12:00 B002 S03 R02 R22222 If a time-sharing information entry allows only one tenant to book, Table 9 can be merged with Table 3. If multiple tenants are allowed to book (e.g., booking different time slots), then previously booked time slots cannot be booked by subsequent tenants. That is, the time-sharing information provided by the server to subsequent tenant clients should remove previously booked time slots to avoid conflicts.

[0045] As shown in Table 9, parking spaces S01 and S03 in Table 3 were both reserved, while S02 was not. Specifically, parking space S01 was reserved by tenant R01 with license plate number R11111, with a planned start time of 9:00 AM and a planned end time of 12:00 PM on November 26, 2025. Based on the planned start and end times entered by tenant R01, parking space S01 can still be shared between 12:00 PM and 6:00 PM on November 26, 2025. Parking space S03 was reserved by tenant R02 with license plate number R22222. Since tenant R02 did not enter a planned start and end time, to prevent conflicts, this time-sharing information for parking space S03 should generally not be reserved by other tenants. Of course, multiple tenants can also be allowed to reserve the same parking space on a time-sharing basis, on a first-come, first-served basis. That is, once one tenant enters, the reservations of other tenants simultaneously become invalid (or, after the tenant who entered leaves, the remaining tenants continue to enter on a first-come, first-served basis). Multiple tenants reserving the same parking space can also use other strategies for entry. For example, tenants who pay a deposit in advance can lock their parking rights; if a tenant fails to enter within the designated time, the deposit will not be refunded, preventing tenants from defaulting and causing losses to the property owner. If multiple tenants are allowed to reserve the same parking space simultaneously, they should be able to see the reservation information of other relevant tenants to facilitate their decision-making (such as canceling the reservation or continuing to wait).

[0046] S103, the synchronization module communicates with the server to obtain the reserved license plate number, and communicates with the host to add it to the access permission table.

[0047] If the host is not connected to the internet, the synchronizer can only connect to the host via a dedicated line. In this case, the synchronizer is usually installed on the host side, with a one-to-one correspondence between the synchronizer and the host. Although the synchronizer connects to the internet and the server, its address is usually a dynamic address (similar to an internet terminal), but the server usually has a fixed access address or domain name. Therefore, the synchronization module installed in the synchronizer usually needs to actively initiate a request to communicate with the server. If the synchronizer has a fixed access address, the server can also actively initiate a communication request.

[0048] If the host is connected to the Internet, the synchronizer can also connect to the host via the Internet. In this case, the synchronizer can also be installed on the server side. In this case, the synchronizer can correspond to multiple hosts (each host must be connected to the Internet). If the synchronizer does not have a fixed access address, the synchronization module needs to actively initiate a request to communicate with the server; if it has a fixed access address, the server can also actively initiate a communication request. To save costs, the synchronizer can also be integrated with the server (i.e., the synchronization module can be directly installed on the server).

[0049] The communication strategy between the synchronization module and the server can be real-time access or timed access (e.g., access once per minute). The permissions required for communication between the synchronization module and the server (such as login accounts) can be configured in advance, and will not be elaborated here. The correspondence between the synchronization module and the parking lot (gate system) can also be configured in advance; Table 10 illustrates one configuration method. The synchronization module ID field is a keyword used to distinguish different synchronization modules, the corresponding parking lot is the parking lot associated with that synchronization module, and the installation location is the installation location of the synchronization module. For example, synchronization module TB01 is installed on the host side, corresponding to parking lot A in community A; synchronization module TB02 is installed on the server side, corresponding to parking lots B and C in community C.

[0050] Table 10 Synchronization Module Configuration Information Synchronization Module ID Corresponding parking lot Installation location TB01 Parking lot in Community A Host side TB02 B Community Parking Lot server side TB02 C Community Parking Lot server side After the synchronization module establishes communication with the server, it can obtain the corresponding reserved license plate number based on the mapping between the synchronization module and the parking lot. For example, the server can pre-deploy a software call interface that provides the corresponding reserved license plate number to the synchronization module. The synchronization module calls this interface with the synchronization module ID as a parameter. This interface can then send the reserved license plate number associated with the corresponding parking lot to the synchronization module based on the pre-configured mapping between the synchronization module and the parking lot. Taking Table 10 as an example, the synchronization module TB01 calls the relevant interface of the server with TB01 as a parameter (i.e., the interface that provides the corresponding reserved license plate number to the synchronization module). This interface queries the synchronization module configuration information in Table 10 and finds that the corresponding parking lot is the A Community Parking Lot. By querying Tables 2 and 9, it can be found that only parking space S01 in the A Community Parking Lot has reserved parking space information, and the corresponding reserved license plate number is R11111. This is returned as the return value to the synchronization module TB01. If a synchronization module has multiple corresponding parking lots (for example, when the synchronization module is installed on the server side), the above return value should also include the corresponding parking lot to facilitate the synchronization module's access to the corresponding host. For example, the synchronization module TB02 calls the relevant interface of the server with TB02 as the parameter, and the corresponding return value is the parking lot of Community B and the reserved license plate number R22222. If the server actively initiates the communication request (in which case the synchronizer has a fixed access address), the server can also send the reserved license plate number associated with the corresponding parking lot to the corresponding synchronization module according to the synchronization module configuration information. If the synchronization module is directly installed on the server, the synchronization module can directly read the corresponding reserved license plate number stored in the server.

[0051] After obtaining the reserved license plate number, the synchronization module communicates with the host and adds it to the access permission table. In subsequent steps, the synchronization module also needs to access the access record table. The synchronization module can choose from the following three methods to access the access permission table and / or access record table through the host: Method 1: The access permission table and / or access record table are stored in the host, and the synchronization module directly accesses the file containing the access permission table and / or access record table.

[0052] The synchronization module communicates with the host computer, directly accessing the files on the host computer that store the access permission table and / or access record table. Taking the reserved license plate number R11111 obtained by the synchronization module TB01 as an example, if the access permission table of the parking lot host computer in Community A is in the form of Table 4, the synchronization module can directly access Table 4 and add R11111 to that table. Method 1 requires that the access permission table and / or access record table (contents) cannot be encrypted. If encryption is required, Method 2 or Method 3 can be used.

[0053] Method 2: The host has interface calling software installed. The interface calling software provides an interface for accessing the access permission table and / or access record table. The synchronization module calls this interface to access the access permission table and / or access record table.

[0054] For example, the synchronization module TB01 uses the reserved license plate number R11111 as a parameter to call the relevant interface provided by the host software (such as the interface for adding license plate numbers) to add it to the access permission table. If there is no relevant interface, method 3 can be used.

[0055] Method 3: The barrier gate system also includes barrier gate management software, which consists of a front-end interface and a back-end program. The front-end interface is used for maintaining license plate numbers and / or querying vehicle passage information, and generates corresponding data packets to send to the back-end program. The back-end program receives data packets sent by the front-end interface, and maintains the corresponding license plate number in the access permission table and / or reads and returns the corresponding vehicle passage information. The synchronization module simulates the front-end interface operations, generates corresponding data packets, sends them to the back-end program, and accesses the access permission table and / or the passage record table.

[0056] To facilitate parking lot management in maintaining vehicle license plate numbers, the barrier gate system will provide corresponding barrier gate management software, typically including a front-end interface and a back-end program. The front-end interface is used for license plate number maintenance operations (such as adding / deleting) and / or vehicle access information queries, generating corresponding data packets to send to the back-end program. The back-end program receives the data packets sent by the front-end interface, maintaining the corresponding license plate number in the access permission table and / or reading and returning the corresponding vehicle access information. The front-end interface runs on a front-end device and is connected to the host (wired or wireless), while the back-end program runs on the host. The front-end device is usually a computer device (such as a front-end interface APP or WEB interface). If the host is connected to the internet, the front-end device can also be a mobile device such as a smartphone. If the front-end device can connect to the internet and can install a synchronization module, it can also be used instead of a synchronizer to save costs.

[0057] Specifically, in this embodiment, the front-end interface includes an operation interface for maintaining the owner's vehicle license plate number and is responsible for generating license plate number maintenance command data packets and sending them to the back-end program. The synchronization module can generate license plate number maintenance command data packets by simulating the front-end interface operation and send them to the back-end program. The back-end program receives the license plate number maintenance command data packets (sent by the simulated operation) and maintains the corresponding license plate number in the access permission table. Even if the access permission table and / or access record table are encrypted, they are usually handled by the back-end program (the encryption of the front-end interface is easily cracked), which does not affect the synchronization module's ability to simulate the front-end interface operation and generate the corresponding data packets to send to the back-end program.

[0058] For example, after adding the license plate number "R55555" to the owner's vehicle license plate number maintenance interface on the front-end interface of a certain gate management software and confirming it, the front-end interface generates a license plate number maintenance command data packet and sends it to the back-end program via HTTP protocol. The specific data packet (using XML encoding as an example) is as follows: <?xml version="1.0" encoding="UTF-8"?> <operationinfo> <operationtype> addPlate< / operationtype> <platenumber> R55555< / platenumber> < / operationinfo> In the above encoding, the first line is the XML declaration header (XML version 1.0, encoding format UTF-8); <operationinfo>As the root node of the XML, it is used to wrap all relevant information (here only the operation type and license plate number are included). <operationtype>It is a child node of the storage operation type, and the text value inside the node is "addPlate" (i.e., add license plate). <platenumber>It is a child node that stores the license plate number, and the text value inside the node is "R55555".

[0059] After receiving the aforementioned data packet, the backend program running on the host machine parses it. Based on the parsed data... <operationtype>The child node value "addPlate" and <platenumber>The child node value "R55555" adds the license plate number "R55555" to the access permission table.

[0060] The synchronization module generates a license plate number maintenance command data packet by simulating front-end interface operations and sends it to the back-end program, thereby achieving the purpose of accessing the access permission table. Taking the reserved license plate number R11111 obtained by the synchronization module TB01 as an example, the synchronization module TB01 simulates front-end interface operations to generate a license plate number maintenance command data packet and sends it to the back-end program via the HTTP protocol. The simulated data packet is as follows: <?xml version="1.0" encoding="UTF-8"?> <operationinfo> <operationtype> addPlate< / operationtype> <platenumber> R11111< / platenumber> < / operationinfo> After receiving the above data packet, the backend program running on the host adds the license plate number "R11111" to the access permission table, and the contents of Table 4 are updated to those shown in Table 11.

[0061] Table 11 includes a list of access rights for reserved license plate numbers. license plate number A11111 A22222 R11111 The process of generating data packets described above is commonly known as serialization, which is the process of converting object (variable) information into a form that can be stored or transmitted. Common serialization methods include XML, JSON, and Protobuf. Since the front-end interface of the gate management software typically interacts with the back-end program based on typical serialization methods and standard communication protocols, the synchronization module can simulate the serialization method corresponding to the front-end interface to generate data packets and send them to the back-end program via relevant communication protocols to access the access permission table. This process usually requires relevant account information (such as an account that can add license plate numbers) or a session identifier (such as a session ID); otherwise, the back-end program may consider it unauthorized access. That is, the synchronization module must first log in to the gate management software using the relevant account to establish a session; the generated data packets include session identifier information (or account information). In parking lots with gate systems, if time-sharing of parking spaces is to be implemented, the parking lot management (property management company) must provide support; therefore, relevant account information or session identifiers are obtainable. The synchronization module's operation of accessing the access permission table based on relevant account information or session identifiers can be considered an operation by the parking lot management, and there is no compliance issue regarding unauthorized access or tampering with the gate management software. While the above operations can be performed manually, they suffer from low efficiency, high cost, and poor user experience. It can be argued that, in the implementation of time-sharing parking space sharing for owners, the synchronization module, under the premise of compliance, achieves automated replacement of manual operation of the gate management software.

[0062] The synchronization module can add the reserved license plate number to the corresponding access permission table at an appropriate time. For example, according to Table 3, the sharing start time for parking space S01 corresponding to reserved license plate number R11111 (at which time the owner's parking space should be in a shareable vacant state) is 8:00 on November 26, 2025. The reserved license plate number can be added to the corresponding access permission table at that time. As another example, according to Table 9, the tenant corresponding to license plate number R11111 intends to start parking at 8:00 on November 26, 2025. The reserved license plate number can be added to the corresponding access permission table at that time. The reserved license plate number can also be added to the corresponding access permission table before the tenant's car is actually ready to enter the parking space. In this case, the tenant can request entry through the tenant client by connecting to the server. The corresponding synchronization module communicates with the server to obtain this request before adding the corresponding reserved license plate number to the access permission table.

[0063] S104, the barrier gate system controls the entry and exit of vehicles corresponding to the reserved license plate numbers, and records vehicle passage information.

[0064] Barrier gate systems all have the function of controlling vehicle entry and exit and recording vehicle passage information. Therefore, when a vehicle with a reserved license plate number wants to enter, the main unit of the barrier gate system will determine whether the license plate number is included in the access permission table based on the license plate number recognized by the license plate recognition device. If so, it will control the barrier gate to open and record the vehicle passage information (such as license plate number and entry time). Taking the reserved license plate number R11111, which has been added to the access permission table in Table 11, as an example, when the corresponding vehicle wants to enter, the license plate recognition device recognizes the license plate number as "R11111". The main unit determines that the access permission table already contains the license plate number, controls the barrier gate to open, and records the corresponding vehicle passage information. When recording vehicle passage information, if the passage record table adopts the format of Table 6, a new record is added, recording the corresponding license plate number and entry time (the exit time is temporarily empty and will be recorded when leaving); if the format of Table 7 is adopted, a new record is added, recording the corresponding license plate number and entry time.

[0065] The process of controlling vehicle entry described above is a standard function of the barrier gate system. The process of controlling vehicle exit is similar to the entry process and is also a standard function of the barrier gate system, so it will not be described again. During the entry and exit process of the vehicle corresponding to the reserved license plate number, the vehicle will be regarded as the owner's vehicle and allowed to pass. Therefore, the entry and exit control of tenant vehicles in time-sharing parking spaces can be realized by using the standard function of the barrier gate system.

[0066] S105, the synchronization module communicates with the host to access the access record table and determines whether the car corresponding to the reserved license plate number has left the site; if so, the reserved license plate number is deleted from the access permission table.

[0067] Similar to step S103, if the host is not connected to the Internet, the synchronizer can only communicate with the host via a dedicated line to access the access record table (one synchronizer corresponds to one host); if the host is connected to the Internet, the synchronizer can also communicate with the host via the Internet to access the access record table (if the synchronizer is installed on the server side, it can correspond to multiple hosts). Regardless of the connection method, the synchronization module installed in the synchronizer needs to actively initiate a request when communicating with the host. The strategy for the synchronization module to communicate with the host can be real-time access or timed access.

[0068] The method for the synchronization module to communicate with the host and access the access record table through the host has been described in step S103 and will not be repeated here. Since methods 1 and 2 are relatively simple, this step will be explained in conjunction with method 3 below.

[0069] For example, on the vehicle passage information query interface of a certain gate management software, after querying and confirming the passage information for "A11111", the front-end interface generates a vehicle passage information query command data packet and sends it to the back-end program via HTTP protocol. The specific data packet (using XML encoding as an example) is as follows: <?xml version="1.0" encoding="UTF-8"?> <queryrecord> <platenumber> A11111< / platenumber> < / queryrecord> In the above encoding, <queryrecord>As the root node of the XML, it is used to wrap all relevant information (here, only the license plate number is included). <platenumber>It is a child node that stores the license plate number, and the text value inside the node is "A11111".

[0070] After receiving the aforementioned data packet, the backend program running on the host machine parses it. Assuming the access record table is shown in Table 6, based on the parsed data... <platenumber>The child node value is "A11111". The backend program generates a vehicle passage record data packet and returns it (to the frontend interface). The specific data packet is as follows: <?xml version="1.0" encoding="UTF-8"?> <returnrecord> <platenumber> A11111< / platenumber> <starttime> 2025-11-25 19:00< / starttime> <endtime> 2025-11-26 7:00< / endtime> < / returnrecord> In the above encoding, <returnrecord>As the root node of the XML, it is used to wrap all relevant information; <platenumber>This is a child node that stores the license plate number; the text value within the node is "A11111". <starttime>This is a child node that stores the entry time; the text value within the node is "2025-11-25 19:00". <endtime>This is a child node that stores the departure time, and the text value within the node is "2025-11-26 7:00".

[0071] After receiving the aforementioned data packet from the backend program, the front-end interface displays the relevant vehicle traffic information on the interface.

[0072] The synchronization module generates a vehicle access information query command data packet by simulating front-end interface operations and sends it to the back-end program. It then receives the vehicle access record data packet from the back-end program (simulating the front-end interface) to access the access record table. Taking Table 6 as an example, assuming the corresponding synchronization module TB01 wants to query the access information for license plate number "R11111", it first simulates front-end interface operations to generate a vehicle access information query command data packet, and then sends it to the back-end program via HTTP protocol. The simulated data packet is as follows: <?xml version="1.0" encoding="UTF-8"?> <queryrecord> <platenumber> R11111< / platenumber> < / queryrecord> After receiving the above data packet, the backend program running on the host machine parses it, queries the passage records of license plate number "R11111", generates a vehicle passage record data packet, and sends it to the frontend interface. The specific data packet is as follows: <?xml version="1.0" encoding="UTF-8"?> <returnrecord> <platenumber> R11111< / platenumber> <starttime> 2025-11-26 9:00< / starttime> <endtime>< / endtime> < / returnrecord> The synchronization module TB01 receives the aforementioned data packets sent by the backend program, parses them, and thus achieves the purpose of accessing the access record table.

[0073] The aforementioned gate system's front-end interface for querying vehicle passage information is based on the license plate number field. Some interfaces may also offer queries based on other fields, such as entry time, exit time, or combinations thereof; the principles are similar and will not be elaborated further.

[0074] After accessing the access record table, the synchronization module determines whether the vehicle corresponding to the reserved license plate number has already left the venue. If so, it deletes the reserved license plate number from the access permission table. Taking the access information of the reserved license plate number "R11111" queried by the synchronization module TB01 as an example, the entry time is "2025-11-26 9:00", and the departure time is empty, indicating that the corresponding vehicle has not yet left the venue. If the departure time is "2025-11-26 15:00", it means that the corresponding vehicle has already left the venue. In this case, the synchronization module TB01 needs to communicate with the host to delete the reserved license plate number from the access permission table. After deletion, the corresponding vehicle will not be allowed to enter the venue. The method of the synchronization module communicating with the host to delete the license plate number from the access permission table is similar to the method of the synchronization module communicating with the host to add the reserved license plate number to the access permission table in step S103. The difference is that the operation type changes from addition to deletion, which will not be described in detail here.

[0075] Tenants who have reserved parking spaces may no longer need to park due to changes in their schedules. If the corresponding license plate number has been added to the access permission table, it can be removed from the access permission table after the shared end time shown in Table 3 arrives, to prevent tenants from entering during non-shared hours. For example, the synchronization module can communicate with the host to access the access record table to determine if the shared end time has arrived and the corresponding tenant's car has not yet entered; if so, the corresponding reserved license plate number will be removed from the access permission table. Tenants can also request to cancel their entry through the tenant client connection to the server. After the synchronization module receives the cancellation request from the server, it communicates with the host to remove the corresponding reserved license plate number from the access permission table. If the reserved parking space information includes the proposed end time as shown in Table 9, the synchronization module can also determine if the proposed end time has arrived and the corresponding tenant's car has not yet entered; if so, the corresponding reserved license plate number will be removed from the access permission table. If a tenant who reserved a parking space does not ultimately enter the parking space, the owner usually needs to be compensated, such as the deposit (or down payment) being non-refundable.

[0076] After the tenant's car leaves, the server can bill the tenant and collect relevant fees according to the billing rules. Fees may include parking fees, reservation fees, property management fees, etc. These fees can be deducted from the tenant's prepaid fees. If there is no prepaid fee and there are concerns that the tenant may refuse to pay after leaving, the following steps can be performed after the gate system controls the car corresponding to the reserved license plate number to enter the premises in step S104: The synchronization module communicates with the host to access the access record table and determines whether the car corresponding to the reserved license plate number has entered the venue; if so, the reserved license plate number is deleted from the access permission table. Before the barrier gate system controls the vehicle corresponding to the reserved license plate number to leave in step S104, the following steps are performed: Tenants pay parking fees by connecting to the server through the tenant client. After the synchronization module confirms successful payment with the server, it communicates with the host to add the corresponding reserved license plate number to the access permission table.

[0077] Example 2 In steps S101 and S102 of Example 1, the property owner publishes time-sharing parking space information, and the tenant selects the time-sharing information to reserve a parking space. Example 2 differs from Example 1 in that steps S101 and S102 are different; in Example 2, the tenant publishes time-sharing demand information, and the property owner selects the time-sharing demand information to rent a parking space, as detailed below: S101, tenants connect to the server through the tenant client and publish time-sharing demand information.

[0078] Tenants typically need to register their information on the server first; this embodiment continues to use the tenant information illustrated in Table 8. Table 12 illustrates one implementation method for time-sharing demand information. The serial number field is a keyword used to distinguish different time-sharing demand information. The tenant ID field describes the tenant who posted the time-sharing demand information. The parking lot is the parking lot where the tenant intends to park. If tenants are allowed to select multiple parking lots, the parking lot can be designed as a secondary form corresponding to the time-sharing demand information. The proposed start time and proposed end time fields describe the time period the tenant intends to park. The reserved license plate number describes the license plate number of the vehicle the tenant intends to park in. If the parking price is set by the owner, an expected price field can also be included, i.e., the parking price acceptable to the tenant.

[0079] Table 12 Time-Sharing Demand Information serial number Tenant ID PARKING LOT Proposed start time Proposed end time Reserved license plate number Expected Price FR001 R01 Parking lot in Community A 2025-11-26 8:00 2025-11-26 12:00 R11111 3 yuan / hour FR002 R02 B Community Parking Lot 2025-11-26 9:00 2025-11-26 16:00 R22222 2 yuan / hour The time-sharing demand information posted by the tenant includes parking space and reserved license plate number. Similar to Example 1, the parking lot has a gate system, which includes a host, an access permission table, and an access record table. The access permission table and access record table can be accessed through the host. The host is connected to a synchronizer, which is connected to a server. The synchronizer is equipped with a synchronization module, which is a software module independent of the gate system. The reserved license plate number can be entered when the time-sharing demand information is posted, or it can be entered after the owner responds to the time-sharing demand information (e.g., when a tenant urgently reserves a parking space for someone else, but the license plate number is not yet specified), but it must be entered before the corresponding vehicle enters the parking lot.

[0080] S102, the owner connects to the server through the owner's client, selects and confirms the time-sharing requirement information.

[0081] Since homeowners typically register their information and corresponding parking space information in advance on the server, and the parking space information includes the parking lot, when a homeowner connects to the server through their homeowner client, the server can send relevant time-sharing request information to the homeowner client based on the parking lot field (this can be done by the homeowner actively querying or by the server actively pushing the request). For example, when homeowners E01 or E02 in Table 1 connect to the server through their homeowner client, they can query the time-sharing request information with serial number FR001 in Table 12. This is because homeowners E01 or E02's parking space is in the parking lot of Community A, and the parking request for time-sharing information with serial number FR001 is also in the parking lot of Community A.

[0082] When a property owner selects and confirms their time-sharing request, they must ensure that the available time slots for their parking space match the tenant's intended parking period. Table 13 illustrates one implementation method for the server to record information after a property owner selects and confirms their time-sharing request. The serial number field corresponds to the serial number field in Table 12, the property owner ID field corresponds to the property owner ID field in Table 1 (this field can be omitted since parking space information includes a property owner ID field, but it is retained here for ease of explanation), the parking space ID field corresponds to the parking space ID field in Table 2, and the parking price field represents the parking fee standard entered by the property owner. In this implementation, multiple property owners are allowed to select the same time-sharing request. The time-sharing request with serial number FR001 is selected by property owners E01 and E02 respectively. A tenant can respond to one of the selections based on their own needs. For example, tenant R01 responds to property owner E02's parking space S02 (parking space S02 is cheaper) based on the parking price information. After the tenant responds, the server modifies the corresponding validity flag field to "Yes," and other corresponding records simultaneously become invalid (i.e., the validity flag is modified to "No"). Tenant R02 has not yet responded to owner E03's request for parking space S03, so the corresponding activation flag field is empty. Similarly, owners can select multiple time-sharing request information and confirm them, with the principle of "first come, first served" for each tenant. That is, once a tenant responds, the corresponding records of other tenants become invalid. If a time-sharing request information can only be selected by one owner (usually on a first-come, first-served basis), then Table 13 can also be merged with Table 12.

[0083] Table 13 Time-Sharing Demand Confirmation Information serial number Owner ID Parking space ID Parking prices Effective mark FR001 E01 S01 3 yuan / hour no FR001 E02 S02 2 yuan / hour yes FR002 E03 S03 2 yuan / hour The subsequent steps are the same as in Example 1. Taking step S103 as an example, the synchronization module corresponding to the parking lot in Community A communicates with the server and obtains the corresponding reserved license plate number "R11111" based on the information in Tables 2, 12, and 13. It then communicates with the host to add the reserved license plate number to the access permission table. The subsequent steps S104 and S105 will not be described in detail.

[0084] Example 3 The difference between this embodiment and the previous two embodiments lies in the fact that steps S101 and S102 are different. The owner publishes parking space time-sharing information, and the tenant publishes time-sharing demand information. The server matches these two types of information. If the match is successful, steps S103-S105 are executed, as follows: S101: Owners connect to the server through the owner's client to publish their parking space time-sharing information; tenants connect to the server through the tenant's client to publish their time-sharing demand information.

[0085] For simplicity, the owner information, parking space information, and time-sharing information in this embodiment still use the data from Tables 1, 2, and 3, while the tenant information and time-sharing demand information still use the data from Tables 8 and 12. Similar to the previous two embodiments, the parking lot has a gate system, which includes a host, an access permission table, and an access record table. The access permission table and access record table can be accessed through the host. The host is connected to a synchronizer, which is connected to a server. The synchronizer is equipped with a synchronization module; the synchronization module is a software module, independent of the gate system. The time-sharing demand information published by the tenant includes the parking lot and the reserved license plate number.

[0086] S102, the server matches the time-sharing information with the time-sharing demand information. If the match is successful, steps S103-S105 are executed.

[0087] Table 14 illustrates one implementation method for the server to match time-sharing information with time-sharing demand information. The shared serial number field corresponds to the serial number field in Table 3, and the demand serial number field corresponds to the serial number field in Table 12. When matching the information shown in Tables 3 and 12, the server must ensure that the parking lots are consistent and that the tenant's intended parking time is within the time period when the owner's parking space can be shared. If there is price information, the owner's parking price cannot be greater than the tenant's expected price. This embodiment supports matching one piece of time-sharing information with multiple pieces of time-sharing demand information, and also supports matching one piece of time-sharing demand information with multiple pieces of time-sharing information. Table 14 lists the matching records. Among them, the record corresponding to the demand serial number FR001 matches both the shared serial numbers F001 and F002. The corresponding tenant can respond to one of the matching records according to its own needs. For example, if tenant R01 responds to the record with the shared serial number F002 (corresponding to parking space S02), the server modifies the effective flag field of the corresponding record to "yes", the record is successfully matched, and other corresponding records become invalid simultaneously. If one time-sharing information item matches multiple time-sharing demand items, the owner's response method is similar. If multiple time-sharing information items match multiple time-sharing demand items, the first record where both the owner and tenant respond is considered a successful match (relevant fields need to be designed to record the responses from both parties), and other corresponding records become invalid simultaneously. If time-sharing serial number F003 matches demand serial number FR002, but the corresponding owner and tenant have not yet responded, the corresponding activation flag is empty.

[0088] Table 14 Matching Information Shared serial number Request serial number Effective mark F001 FR001 no F002 FR001 yes F003 FR002 The implementation method in Table 14 requires the owner and / or tenant to respond to the matching record before a successful match is considered. The server can also perform a unique match between time-sharing information and time-sharing demand information according to preset rules; this match result is directly considered a successful match. For example, if the server's preset rule prioritizes matching those with lower parking prices, the matching information from Tables 3 and 12 is shown in Table 15. Table 15 no longer requires an activation flag field, simplifying the matching process.

[0089] Table 15 shows the unique matching information in the results. Shared serial number Request serial number F002 FR001 F003 FR002 The server can match time-sharing information with time-sharing demand information in real time or at scheduled intervals. If the match is successful, steps S103-S105 are executed. Subsequent steps are the same as in Example 1. Taking step S103 as an example, assuming Table 15 is the matching result, the synchronization module corresponding to the parking lot in Community A communicates with the server and obtains the corresponding reserved license plate number "R11111" based on the information in Tables 2, 3, 12, and 15, and then communicates with the corresponding host to add it to the corresponding access permission table. Similarly, the synchronization module corresponding to the parking lot in Community B communicates with the server and obtains the corresponding reserved license plate number "R22222", and then communicates with the corresponding host to add it to the corresponding access permission table. Subsequent steps S104 and S105 will not be described in detail.

[0090] Example 4 The time-sharing of owner parking spaces is usually a profit-making activity. If an owner's parking space is shared with others during a time period, and the owner's own vehicle is also in the parking lot (e.g., temporarily moved to another parking space), it infringes on the rights of other parties. Example 4 is used to solve this problem. Example 4 differs from the previous three examples in that: there is a correspondence between parking spaces and owner license plate numbers; the access permission table includes records of owner license plate numbers, as well as steps to disable and enable owner license plate numbers.

[0091] The specific steps to disable a homeowner's license plate number are as follows: The synchronization module determines whether the car corresponding to the reserved license plate number has entered the venue; if so, the corresponding homeowner's license plate number is deleted from the access permission table.

[0092] The specific steps to enable the owner's license plate number are as follows: When deleting the reserved license plate number from the access permission table in step S105, add the corresponding owner's license plate number to the access permission table.

[0093] Table 2 illustrates the correspondence between parking spaces and owner license plate numbers, while Tables 4 and 5 illustrate cases where the access permission table includes owner license plate numbers. Since parking spaces and owner license plate numbers are correlated, reserved license plate numbers are also correlated with owner license plate numbers; that is, the parking space rented by the tenant is also the parking space where the owner's car is parked. The synchronization module can communicate with the host to access the access record table and determine whether the car corresponding to the reserved license plate number has entered the parking area. The synchronization module can also determine whether the car corresponding to the reserved license plate number has entered the parking area based on other conditions. For example, the scenario described in Example 1, S103, where a tenant requests entry through a tenant client connection to the server.

[0094] The method for deleting the corresponding owner's license plate number from the access permission table depends on the specific implementation of the access permission table. If the access permission table is as shown in Table 4, then the owner's license plate number needs to be directly deleted from the access permission table. Before deletion, the synchronization module can back up the correspondence between the reserved license plate number and the owner's vehicle license plate number (backup is optional; the correspondence can be queried from the server later). The backup can be sent to the synchronizer or the server for later enabling of the owner's license plate number. If the access permission table is as shown in Table 5, the status field corresponding to the owner's license plate number needs to be changed to invalid.

[0095] The specific method for adding the corresponding owner's license plate number to the access permission table during the process of enabling the owner's license plate number depends on the specific implementation of the access permission table. If the access permission table is as shown in Table 4, simply add the owner's vehicle license plate number corresponding to the reserved license plate number to the access permission table. If the access permission table is as shown in Table 5, the status field corresponding to the owner's vehicle license plate number needs to be changed to "valid".

[0096] Example 5 Example 4 addresses the issue of tenant vehicles and owner vehicles simultaneously entering the parking lot during time-sharing of private parking spaces by disabling and enabling owner license plate numbers. However, tenant vehicles may not leave on time, or owner vehicles may enter early. In this case, disallowing owner vehicles may affect owners' enthusiasm for time-sharing parking spaces. Example 5 addresses this problem. Example 5 differs from Examples 1, 2, and 3 in that: there is a correspondence between parking spaces and owner license plate numbers, and the access permission table includes owner license plate numbers; after step S104, a fee calculation step is also included, specifically: Determine whether the car corresponding to the reserved license plate number and the car of the corresponding owner entered the corresponding parking lot at the same time; if so, calculate the supplementary fee based on the duration of simultaneous entry into the parking lot and the parking fee standard.

[0097] The synchronization module or server can determine whether a car corresponding to a reserved license plate number and a car belonging to a specific owner simultaneously entered the corresponding parking lot based on vehicle traffic information. Vehicle traffic information includes the license plate number, entry time, and exit time, which can be used to determine if a car with the reserved license plate number and a car belonging to a specific owner entered the parking lot simultaneously. For example, a reserved license plate number R11111 corresponds to a car with license plate number A11111, and the vehicle traffic information is shown in Table 16. Based on the entry and exit times, it can be determined that between 18:00 on November 27, 2025, and 20:00 on November 27, 2025, cars with license plate numbers R11111 and A11111 entered the parking lot simultaneously. Assuming the parking fee (which could be the parking lot's standard fee or a fee set by the platform) is 3 yuan / hour, the additional fee would be 3 yuan / hour × 2 hours = 6 yuan. This fee can be used as compensation to third parties (such as other owners or the property management company).

[0098] Table 16 Access Record - Owner's and Tenant's Cars Entering Simultaneously license plate number Entry time Departure time A11111 2025-11-26 18:00 2025-11-27 8:00 R11111 2025-11-27 9:00 2025-11-27 20:00 A11111 2025-11-27 18:00 2025-11-28 8:00 Furthermore, regardless of whether tenant cars and owner cars enter the parking lot simultaneously, an additional management fee can be charged as needed because frequent entry of tenant cars may incur management costs for the property management company. For example, a management fee of 1 yuan per instance can be charged for tenant cars.

[0099] Figure 1 This illustration shows an embodiment of a time-sharing access control system for private parking spaces according to the present invention, including a server 1 and a synchronization module 10. The objects in its application scenario include owner client 2, tenant client 3, owner 4, tenant 5, tenant car 6, parking space 7, parking lot 8, network 9, host 12, barrier gate 13, and license plate recognition device 14. Server 1 is connected to network 9. Owner client 2 and tenant client 3 can be mobile phones, laptops, tablets, etc., and are also connected to network 9. Parking space 7 corresponds to owner 4 (indicated by an arrow pointing from parking space 7 to owner 4). Owner 4 and owner client 2 are enclosed in an ellipse, indicating that owner 4 uses owner client 2 to access server 1 via network 9. Tenant 5, tenant client 3, and tenant car 6 are enclosed in an ellipse, indicating that tenant 5 uses tenant client 3 to access server 1 via network 9 and rents parking space 7 to park tenant car 6 (indicated by an arrow pointing from parking space 7 to tenant car 6). Parking space 7 is located within parking lot 8. Parking lot 8 has a barrier gate system 15 to restrict vehicle entry and exit from parking lot 8. The barrier gate system 15 includes a main unit 12, a barrier gate 13, a license plate recognition device 14, an access permission table 16, and an access record table 17. The main unit 12 is a control device for controlling the entry and exit of vehicles. The main unit 12 is connected to the barrier gate 13 (indicated by a dashed connection line), and the entry and exit control of vehicles is realized by controlling the opening and closing of the barrier gate 13. Figure 1 The barrier gate system 15 has two barrier gates 13 and two license plate recognition devices 14, installed at the entrance and exit of the parking lot 8, respectively. The license plate recognition devices 14 are used to identify vehicle license plate numbers. The access permission table 16 stores the license plate numbers allowed by the barrier gate system 15; corresponding vehicles can enter and exit the parking lot 8 through the barrier gates 13. The access record table 17 stores vehicle access information, including license plate number, entry time, and exit time. The access permission table 16 and access record table 17 can be database forms or dedicated files, accessible through the host 12 (indicated by an arrow pointing to the host 12). The synchronizer 11 is connected to the host 12 (indicated by a dashed connection line). The synchronizer 11 is equipped with a synchronization module 10 (indicated by an arrow pointing to the synchronizer 11). The synchronization module 10 is a software module, independent of the barrier gate system 15. The synchronization module 10 can access the access permission table 16 and access record table 17 through the host 12. Synchronizer 11 is connected to network 9 and communicates with server 1 through network 9.

[0100] Server 1 includes an information publishing module and a reservation generation module.

[0101] The information publishing module and the appointment generation module are used for: Owner 4 publishes time-sharing information and tenant 5 selects time-sharing information and enters the reserved license plate number to reserve parking space 7; or, tenant 5 publishes time-sharing demand information and owner 4 selects time-sharing demand information to share parking space 7; or, owner 4 publishes time-sharing information and tenant 5 publishes time-sharing demand information, and the time-sharing information and time-sharing demand information are matched and confirmed.

[0102] Time-sharing information includes parking space information and parking lot 8; time-sharing demand information includes parking lot 8 and reserved license plate number.

[0103] Synchronization module 10 includes an enable / disable module for reserved license plate numbers and a disable module for reserved license plate numbers. These modules are used to generate the operations performed on reserved license plate numbers after the parking space time-sharing confirmation is completed by the reservation module. Specifically: The enabled license plate number reservation module is used to communicate with server 1 to obtain the reserved license plate number and to communicate with host 12 to add it to the access permission table 16. The module for disabling the reserved license plate number is used to communicate with the host 12 to access the access record table 17 and determine whether the car corresponding to the reserved license plate number has left the site; if so, the reserved license plate number is deleted from the access permission table 16.

[0104] The synchronization module 10 also includes a table access module for accessing the access permission table 16 and / or the access record table 17. Access methods include: directly accessing the access permission table 16 and / or the access record table 17 files stored in the host 12; or calling the interface provided by the software to access the access permission table 16 and / or the access record table 17 via the interface installed on the host 12; or simulating the operation of the front-end interface of the barrier gate management software to generate corresponding data packets and sending them to the back-end program of the barrier gate management software to access the access permission table 16 and / or the access record table 17. The barrier gate management software belongs to the barrier gate system 15 and includes a front-end interface and a back-end program, with the back-end program installed in the host 12.

[0105] Synchronization module 10 also includes a post-entry deletion module and a pre-departure recovery module.

[0106] The "delete upon entry" module is used to determine whether the vehicle corresponding to the reserved license plate number has already entered the venue; if so, the reserved license plate number is deleted from the access permission table 16. The pre-departure recovery module is used to add the corresponding reserved license plate number to the access permission table 16 after tenant 5 pays the parking fee.

[0107] If the owner 4 corresponding to parking space 7 owns a car, then parking space 7 is associated with the owner's license plate number, and the records in access permission table 16 include the owner's license plate number.

[0108] Synchronization module 10 also includes a module for disabling owner's license plate number and a module for enabling owner's license plate number, or server 1 or synchronization module 10 also includes a module for calculating supplementary fees.

[0109] The "Disable Owner's License Plate Number" module is used to determine whether a vehicle corresponding to a reserved license plate number has entered the area; if so, the corresponding owner's license plate number will be deleted from the access permission table 16.

[0110] The Enable Owner License Plate Number module is used to add the corresponding owner license plate number to the access permission table 16 when the Disable Reservation License Plate Number module deletes the reserved license plate number from the access permission table 16.

[0111] The supplementary fee calculation module is used to determine whether the car corresponding to the reserved license plate number and the corresponding owner's car entered the corresponding parking lot 8 at the same time; if so, it calculates the supplementary fee based on the duration of simultaneous entry into parking lot 8 and the parking fee standard. The supplementary fee can be used as compensation to third parties (such as other owners or property management companies).< / endtime> < / starttime> < / platenumber> < / returnrecord> < / platenumber> < / platenumber> < / queryrecord> < / platenumber> < / operationtype> < / platenumber> < / operationtype> < / operationinfo>

Claims

1. A method for controlling entry to private parking spaces on a time-sharing basis, characterized in that: Includes the following steps, Step 1: The owner connects to the server through the owner's client and publishes the time-sharing information of their parking space. The parking lot where the parking space is located has a barrier gate system. The barrier gate system includes a host, an access permission table, and an access record table. The host is a control device for controlling vehicle entry and exit. The access permission table stores the license plate numbers allowed by the barrier gate system. The access record table stores vehicle access information, including license plate number, entry time, and exit time. The access permission table and access record table can be accessed through the host. The host is connected to a synchronizer, and the synchronizer is connected to the server. The synchronizer is equipped with a synchronization module. The synchronization module is a software module and is independent of the barrier gate system. Step 2: The tenant connects to the server through the tenant client, selects the time-sharing information, and enters their reserved license plate number to reserve a parking space; Step 3: The synchronization module communicates with the server to obtain the reserved license plate number, and communicates with the host to add it to the access permission table; Step 4: The barrier gate system controls the entry and exit of the vehicle corresponding to the reserved license plate number and records the vehicle passage information; Step 5: The synchronization module communicates with the host to access the access record table and determines whether the vehicle corresponding to the reserved license plate number has left the venue; if so, the reserved license plate number is deleted from the access permission table.

2. The private parking space time-sharing entry control method according to claim 1, characterized in that: Step 1 and Step 2 are either: Step 1: The tenant connects to the server through a tenant client and publishes time-sharing demand information. This time-sharing demand information includes parking spaces and reserved license plate numbers. The parking space has a barrier gate system. The barrier gate system includes a host, an access permission table, and a access record table. The host is a control device for controlling vehicle entry and exit. The access permission table stores the license plate numbers allowed by the barrier gate system. The access record table stores vehicle access information, including license plate number, entry time, and exit time. The access permission table and access record table can be accessed through the host. The host is connected to a synchronizer, which is connected to the server. The synchronizer is equipped with a synchronization module. This synchronization module is a software module and is independent of the barrier gate system. Step 2: The homeowner connects to the server through the homeowner client, selects and confirms the time-sharing requirement information; the homeowner has a parking space in the corresponding parking lot.

3. The private parking space time-sharing entry control method according to claim 1, characterized in that: Step 1 and Step 2 are either: Step 1: The owner connects to the server through the owner's client and publishes the time-sharing information of their parking space. The parking lot where the parking space is located has a barrier gate system. The barrier gate system includes a host, an access permission table, and an access record table. The host is a control device for controlling vehicle entry and exit. The access permission table stores the license plate numbers allowed by the barrier gate system. The access record table stores vehicle access information, including license plate number, entry time, and exit time. The access permission table and access record table can be accessed through the host. The host is connected to a synchronizer, and the synchronizer is connected to the server. The synchronizer is equipped with a synchronization module. The synchronization module is a software module and is independent of the barrier gate system. Tenants connect to the server through a tenant client to publish time-sharing demand information; the time-sharing demand information includes parking spaces and reserved license plate numbers. Step 2: The server matches the time-sharing information with the time-sharing demand information. If the match is successful, proceed to step 3.

4. The private parking space time-sharing entry control method according to claim 1, 2, or 3, characterized in that: Step 4, after the barrier gate system controls the vehicle corresponding to the reserved license plate number to enter the gate, also includes the following steps: The synchronization module communicates with the host to access the access record table and determines whether the car corresponding to the reserved license plate number has entered the venue; if so, the reserved license plate number is deleted from the access permission table. Step 4, before the barrier gate system controls the vehicle corresponding to the reserved license plate number to leave, also includes the following steps: Tenants pay parking fees by connecting to the server through a tenant client. After the synchronization module communicates with the server to confirm successful payment, it communicates with the host to add the corresponding reserved license plate number to the access permission table.

5. The private parking space time-sharing entry control method according to claim 1, 2, 3, or 4, characterized in that: The method by which the synchronization module communicates with the host to access the access permission table and / or the access record table is as follows: Method 1: The access permission table and / or the access record table are stored in the host, and the synchronization module directly accesses the file storing the access permission table and / or the access record table; Alternatively, method 2: The host is equipped with interface calling software, which provides an interface for accessing the access permission table and / or the access record table. The synchronization module calls this interface to access the access permission table and / or the access record table. Alternatively, method 3: The barrier gate system further includes barrier gate management software, which includes a front-end interface and a back-end program; the front-end interface is used for maintaining license plate numbers and / or querying vehicle passage information, and generates corresponding data packets to send to the back-end program; the back-end program is used to receive data packets sent by the front-end interface, and realize the maintenance of the corresponding license plate number in the access permission table and / or the reading and return of the corresponding vehicle passage information; the synchronization module simulates the operation of the front-end interface to generate corresponding data packets and sends them to the back-end program, accessing the access permission table and / or the passage record table.

6. The private parking space time-sharing entry control method according to claim 1, 2, 3, or 4, characterized in that: Both the synchronizer and the server are connected to the Internet, and the synchronization module communicates with the server through the Internet. The synchronizer is connected to the host via a dedicated line, and the synchronization module communicates with the host via the dedicated line; or, the host is connected to the Internet, and the synchronization module communicates with the host via the Internet.

7. The private parking space time-sharing entry control method according to claim 1, 2, 3, or 4, characterized in that: The parking spaces are associated with the owners' license plate numbers, and the records in the access permission table include the owners' license plate numbers; The private parking space time-sharing entry control method also includes steps to disable the owner's license plate number and steps to enable the owner's license plate number, or the private parking space time-sharing entry control method also includes steps to calculate the supplementary fee. The specific steps for disabling the owner's vehicle license plate number are as follows: The synchronization module determines whether the car corresponding to the reserved license plate number has entered the venue; if so, it deletes the corresponding owner's license plate number from the access permission table. The specific steps for enabling the owner's vehicle license plate number are as follows: When deleting the reserved license plate number from the access permission table in step 5, the corresponding owner's license plate number is added to the access permission table; The specific steps for calculating the supplementary payment are as follows: Determine whether the car corresponding to the reserved license plate number and the car of the corresponding owner enter the corresponding parking lot at the same time; if so, calculate the supplementary fee based on the duration of simultaneous entry into the parking lot and the parking fee standard.

8. A time-sharing entry control system for private parking spaces, comprising a server and a synchronization module, wherein the parking lot where the parking space is located has a barrier gate system, the barrier gate system comprising a host, an access permission table, and an access record table; the host is a control device for controlling vehicle entry and exit, the access permission table stores license plate numbers allowed to pass through the barrier gate system, and the access record table stores vehicle access information, including license plate number, entry time, and exit time; the access permission table and the access record table can be accessed through the host; characterized in that: The host is connected to the synchronizer, and the synchronizer is connected to the server; the synchronizer is equipped with the synchronization module; the synchronization module is a software module and is independent of the barrier gate system. The server includes an information publishing module and a reservation generation module. These two modules are used for: owners publishing time-sharing information and tenants selecting time-sharing information and entering a reserved license plate number to reserve a parking space; or, tenants publishing time-sharing demand information and owners selecting time-sharing demand information to share a parking space; or, owners publishing time-sharing information and tenants publishing time-sharing demand information and matching and confirming the time-sharing information and the time-sharing demand information. The time-sharing information includes parking space information and parking lot information, and the time-sharing demand information includes parking lot information and a reserved license plate number. The synchronization module includes an enable / disable module for reserving license plate numbers and a disable module for reserving license plate numbers. These modules are used to process the reserved license plate numbers after the parking space time-sharing confirmation is obtained from the reservation generation module. Specifically: The enabled license plate number reservation module is used to communicate with the server to obtain the reserved license plate number, and to communicate with the host to add it to the access permission table. The module for disabling reserved license plate numbers is used to communicate with the host to access the access record table and determine whether the vehicle corresponding to the reserved license plate number has left the venue; if so, the reserved license plate number is deleted from the access permission table.

9. The private parking space time-sharing entry control system according to claim 8, characterized in that: The synchronization module further includes a table access module for accessing the access permission table and / or the access record table. The access method is as follows: Directly access the access permission table and / or access record table files stored in the host; Alternatively, the interface installed on the host can be used to call the access permission table and / or access record table provided by the software. Alternatively, the front-end interface of the simulated barrier gate management software generates corresponding data packets, which are sent to the back-end program of the barrier gate management software to access the access permission table and / or access record table; the barrier gate management software belongs to the barrier gate system.

10. The private parking space time-sharing entry control system according to claim 8, characterized in that: The synchronization module also includes a post-entry deletion module and a pre-departure recovery module; The post-entry deletion module is used to determine whether the vehicle corresponding to the reserved license plate number has already entered the venue; if so, the reserved license plate number is deleted from the access permission table. The pre-departure recovery module is used to add the corresponding reserved license plate number to the access permission table after the tenant pays the parking fee; The parking spaces are associated with the owners' license plate numbers, and the records in the access permission table include the owners' license plate numbers; The synchronization module also includes a module for disabling the owner's license plate number and a module for enabling the owner's license plate number; or, the server or synchronization module also includes a module for calculating supplementary fees. The module for disabling owner's license plate number is used to determine whether the car corresponding to the reserved license plate number has entered the venue; if so, the corresponding owner's license plate number is deleted from the access permission table. The enabled owner license plate number module is used to add the corresponding owner license plate number to the access permission table when the disabled reservation license plate number module deletes the reservation license plate number from the access permission table; The supplementary fee calculation module is used to determine whether the car corresponding to the reserved license plate number and the car of the corresponding owner enter the corresponding parking lot at the same time; if so, it calculates the supplementary fee based on the duration of simultaneous entry into the parking lot and the parking fee standard.

Images