Release management method, device, equipment, storage medium and system

Abstract

The application provides a release management method, device, equipment, storage medium and system, relates to the vehicle identification release field of parking lot, and the method comprises the following steps: obtaining access request data; in the case that the access request data is the license plate number of the current motor vehicle to be passed, obtaining identity verification data, if the identity verification data is Bluetooth card data, and the license plate number of the current motor vehicle to be passed and the identity verification data are matched with each other, then the barrier gate is controlled to release; in the case that the access request data is identity data, and the identity data is IC card data, obtaining license plate verification data, if the identity data of the current motor vehicle to be passed and the license plate verification data are matched with each other, then the barrier gate is controlled to release. The method uses the combination of the identity data and the license plate number to perform double verification on the motor vehicle to be passed, and improves the security of the release management.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of parking lot vehicle identification and release, and in particular to a release management method, device, equipment, storage medium and system. BACKGROUND

[0002] The conventional release management system of the parking lot is generally based on the license plate number for management. When the vehicle enters or exits the parking lot, the release management is performed by identifying the license plate number of the vehicle.

[0003] However, this management system has a security risk. For example, a fake license plate can be used to impersonate other vehicles to authenticate the gate opening. SUMMARY

[0004] Based on the above technical problems, the present application provides a release management method, device, equipment, storage medium and system, which can use the combination of identity data and license plate number to double-check the motor vehicle to be passed, so as to solve the problem of opening the gate with a fake license plate.

[0005] In a first aspect, the present application provides a release management method, which comprises: obtaining passage request data; the passage request data is the license plate number or identity data of the current motor vehicle to be passed; in the case that the passage request data is the license plate number of the current motor vehicle to be passed, obtaining the identity data to be verified, if the identity data to be verified is the Bluetooth card data, and the license plate number of the current motor vehicle to be passed and the identity data to be verified match each other, then controlling the gate release of the gate through which the current motor vehicle to be passed; in the case that the passage request data is the identity data, and the identity data is the IC card data, obtaining the license plate data to be verified, if the identity data of the current motor vehicle to be passed and the license plate data to be verified match each other, then controlling the gate release of the gate through which the current motor vehicle to be passed.

[0006] The release management method provided by the present application can use the license plate number to check the passage right of the motor vehicle to be passed, and use the identity data to check the consistency of the recognized license plate number and the motor vehicle to be passed, so as to realize the double-check of the motor vehicle to be passed, improve the security of the release management, and provide a solution for the release management in the high security requirement scene which needs to judge the consistency of the vehicle and the card.

[0007] In addition, the identity data can also use the contact type IC card data and the long-distance induction type Bluetooth card data respectively, which can meet the individual needs of different users.

[0008] Optionally, if the passage request data is the license plate number of the vehicle to be passed, the identity identification data to be verified is obtained, including: if the passage request data is the license plate number of the vehicle to be passed and Bluetooth card data exists in the Bluetooth card cache queue, the Bluetooth card data in the Bluetooth card cache queue is used as the identity identification data to be verified; if the identity identification data to be verified is Bluetooth card data and the license plate number of the vehicle to be passed matches the identity identification data to be verified, the gate at the gate where the vehicle to be passed is located is controlled to allow passage, including: if the license plate number of the vehicle to be passed matches the Bluetooth card data in the Bluetooth card cache queue, the gate at the gate where the vehicle to be passed is located is controlled to allow passage.

[0009] It should be understood that Bluetooth card data has a relatively long recognition range, reaching approximately 5 to 15 meters, while license plate recognition requires the vehicle to approach the barrier gate. If the acquired Bluetooth card data is directly matched, there may be cases where the license plate number is empty (not yet recognized). The release management method provided in this application utilizes a Bluetooth card cache queue to cache the acquired Bluetooth card data first, and then performs matching only when the license plate number is recognized. This provides a release control scheme for scenarios where Bluetooth card data is reported earlier than the license plate number.

[0010] Optionally, the method further includes: when the passage request data is identity data, and the identity data is Bluetooth card data, if there is no Bluetooth card data in the Bluetooth card cache queue, then the identity data of the current vehicle to be passed is used as candidate Bluetooth card data; if the candidate Bluetooth card data is different from the Bluetooth card data corresponding to one or more historical vehicles in the first period, or the time interval between the acquisition time of the candidate Bluetooth card data and the acquisition time of the target Bluetooth card data is greater than a preset time threshold, then the candidate Bluetooth card data is added to the Bluetooth card cache queue; the target Bluetooth card data is the Bluetooth card data corresponding to the last historical vehicle among one or more historical vehicles; if the candidate Bluetooth card data is the same as the Bluetooth card data corresponding to any one of the historical vehicles among one or more historical vehicles, or the time interval between the acquisition time of the candidate Bluetooth card data and the acquisition time of the target Bluetooth card data is less than a preset time threshold, then the Bluetooth card cache queue is not updated.

[0011] It should be understood that Bluetooth card data has a relatively long recognition range, reaching approximately 5 to 15 meters. Furthermore, Bluetooth cards are typically placed in the driver's seat or on the windshield. After a vehicle has been allowed to pass through the gate, it may continue to report Bluetooth card data to the Bluetooth card reader, thus interfering with the recognition of vehicles that have not yet been released. The release management method provided in this application can filter out Bluetooth card data reported by vehicles that have already passed through the gate by using two conditions: the Bluetooth card data is different from that of previously passed vehicles, and the interval between the Bluetooth card data of the previously passed vehicle and the last previously passed vehicle's Bluetooth card data exceeds a preset time threshold. This prevents the Bluetooth card data reported by vehicles that have already passed through the gate from interfering with the recognition of vehicles that have not yet been released.

[0012] Optionally, when the passage request data is identity data and the identity data is IC card data, obtaining the license plate data to be verified includes: when the passage request data is identity data and the identity data is IC card data, obtaining the license plate numbers of motor vehicles that have not been released within a preset time period as the license plate data to be verified.

[0013] It should be understood that Bluetooth card data has a longer recognition range, reaching approximately 5 to 15 meters, while IC card data requires the IC card to contact the IC card reader. Therefore, in actual traffic scenarios, a situation may arise where a motorcycle is in front and a car is behind. In this case, the motorcycle's license plate number has already been reported, while the car is still queuing behind the motorcycle and its license plate number has not yet been reported. However, due to the longer recognition range of Bluetooth card data, the car's Bluetooth card data is reported first, followed by the motorcycle's IC card data. The release management method provided in this application, after obtaining IC card data, can match the IC card data with the license plate numbers of vehicles waiting to pass within a preset time period, thereby verifying and releasing the motorcycles queuing ahead. This achieves a release management scheme that uses a hybrid approach of contact IC cards and long-range sensing Bluetooth cards.

[0014] Optionally, before controlling the gate to release the vehicle, the method further includes: determining whether the vehicle waiting to pass is a temporary vehicle or a fixed vehicle based on the license plate number of the vehicle waiting to pass; and issuing a prompt message to indicate whether the vehicle waiting to pass is a temporary vehicle or a fixed vehicle.

[0015] Optionally, the motor vehicle currently waiting to pass includes motorcycles or cars; the identification data for motorcycles is IC card data; and the identification data for cars is Bluetooth card data.

[0016] Secondly, this application provides a release management device, which includes various functional modules for the method described in the first aspect above.

[0017] Thirdly, this application provides a release management device, which includes a processor and a memory; the memory stores processor-executable instructions; when the processor is configured to execute the instructions, the release management device performs the method described in the first aspect above.

[0018] Fourthly, this application provides a computer program product that, when run on a release management device, causes the release management device to perform the steps of the related method described in the first aspect, so as to implement the method described in the first aspect.

[0019] Fifthly, this application provides a readable storage medium comprising: software instructions; when the software instructions are executed in a release management device, they cause the release management device to implement the method described in the first aspect above.

[0020] The beneficial effects of the second to fifth aspects mentioned above can be referred to the first aspect, and will not be repeated here. Attached Figure Description

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

[0022] Figure 1 A schematic diagram illustrating the composition of the release management system provided in this application embodiment;

[0023] Figure 2 A schematic diagram illustrating the composition of the release management device 400 provided in this embodiment of the application;

[0024] Figure 3 A flowchart illustrating the release management method provided in this application embodiment;

[0025] Figure 4 Another flowchart illustrating the release management method provided in this application embodiment;

[0026] Figure 5 This is another flowchart illustrating the release management method provided in an embodiment of this application;

[0027] Figure 6 This is another flowchart illustrating the release management method provided in an embodiment of this application;

[0028] Figure 7 This is another flowchart illustrating the release management method provided in an embodiment of this application;

[0029] Figure 8This is a schematic diagram of the composition of the release management device provided in the embodiments of this application. Detailed Implementation

[0030] Hereinafter, the terms "first," "second," and "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first," "second," or "third," etc., may explicitly or implicitly include one or more of that feature.

[0031] As described in the background section above, traditional parking lot access control systems typically rely on license plate numbers for management. When a vehicle enters or exits the parking lot, its license plate number is identified for access control.

[0032] However, this management system has security vulnerabilities. For example, it could be used to impersonate other vehicles by using fake license plates to authenticate and open the gate.

[0033] Based on this, embodiments of this application provide a release management method, device, equipment, storage medium, and system that can use identity data to perform dual verification of motor vehicles to be passed, in order to solve the problem of opening the gate with counterfeit license plates.

[0034] The following description is provided in conjunction with the accompanying drawings.

[0035] Figure 1 This is a schematic diagram illustrating the composition of the release management system provided in an embodiment of this application. Figure 1 As shown, the access control system may include: an integrated circuit (IC) card reader 100, a Bluetooth card reader 200, an automatic number plate recognition (ANPR) camera 300, an access control device 400, and a barrier gate 500. The IC card reader 100, Bluetooth card reader 200, ANPR camera 300, and barrier gate 500 are connected to the access control device 400.

[0036] For example, IC card reader 100, Bluetooth card reader 200, ANPR camera 300, and barrier gate 500 can be connected to access control device 400 via wired communication lines or wireless networks.

[0037] Optionally, the wired communication line can be a control area network (CAN) bus.

[0038] Among them, the IC card reader 100 is used to collect IC card data.

[0039] Optionally, the IC card data may specifically include the IC card number or the IC card's identification identifier. For example, before the IC card reader 100 collects the card number or identification identifier of an IC card, an IC card writer can be used to write the card number or identification identifier into the IC card.

[0040] The IC card reader 100 can be installed at the parking position of the gate channel (i.e., Figure 1 The location shown is near the gate passage, making it convenient for drivers of vehicles waiting to pass to swipe their cards.

[0041] Bluetooth card reader 200 is used to collect data from Bluetooth cards.

[0042] Similarly, Bluetooth card data can specifically include the Bluetooth card number or the Bluetooth card's identification identifier. For example, before the Bluetooth card 200 collects the card number or identification identifier of a Bluetooth card, a Bluetooth card writer can be used to write the card number or identification identifier into the Bluetooth card.

[0043] The Bluetooth card reader 200 can be installed on one side of the gate channel.

[0044] The ANPR camera 300 is used to capture the license plate numbers of vehicles currently waiting to pass.

[0045] For example, the ANPR camera 300 can first acquire an image of the vehicle waiting to pass, and then use optical character recognition technology to read the image of the vehicle waiting to pass and obtain the license plate number of the vehicle waiting to pass.

[0046] Optionally, the motor vehicle currently waiting to pass can specifically include motorcycles or cars. Cars have license plates displayed at both the front and rear, allowing for frontal recognition. Motorcycles, however, typically have their license plates only displayed at the rear or mounted sideways on the front, making them unrecognizable from the front. In this case, the ANPR camera 300 can be specifically positioned at the gate's barrier, facing the gate passage; alternatively, the ANPR camera 300 can be specifically positioned inside the gate passage, facing the gate's barrier; or, the ANPR camera 300 can include two ANPR cameras, one positioned at the gate's barrier, facing the gate passage, and the other positioned inside the gate passage, facing the gate's barrier.

[0047] The passage management device 400 is used to control the gate 500 to allow (or open) or not allow (or close) passage according to the following passage management method.

[0048] The passage management device 400 can be a controller installed at the gate; or it can be a computer or server installed at the gate; or it can be a remote server installed at the rear, etc. The embodiments of this application do not limit this.

[0049] The server can be a single server or a server cluster consisting of multiple servers. In some embodiments, the server cluster can also be a distributed cluster. Optionally, the server can also be implemented on a cloud platform, such as a private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, inter-cloud, and multi-cloud, or any combination thereof. This application does not limit this aspect.

[0050] It should be noted that the above Figure 1 Taking a single-sided barrier gate as an example, the passage management system can also be a double-sided barrier gate, which can be described in the above-mentioned manner. Figure 1 The composition of the single-sided barrier gate is obtained, and the embodiments of this application do not limit this.

[0051] The execution entity of the release management method provided in this application embodiment may be the release management device 400, or the processor in the release management device 400; or an application (APP) with release management function installed in the release management device 400; or a functional module in the release management device 400 for performing the release management function, etc. This application embodiment does not limit this.

[0052] For simplicity, the release management device 400 will be used as an example to describe the release management method provided in this application embodiment.

[0053] Figure 2 This is a schematic diagram illustrating the composition of the release management device 400 provided in an embodiment of this application. Figure 2 As shown, the device includes: a processor 10, a memory 20, a communication line 30, and a communication interface 40.

[0054] The processor 10, memory 20, and communication interface 40 can be connected via communication line 30.

[0055] The processor 10 is used to execute instructions stored in the memory 20 to implement the release management method provided in the following embodiments of this application. The processor 10 may be a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller (MCU) / single-chip microcomputer, a programmable logic device (PLD), or any combination thereof. The processor 10 may also be any other device with processing capabilities, such as a circuit, device, or software module; this application embodiment does not limit this. In one example, the processor 10 may include one or more CPUs, for example... Figure 2 CPU0 and CPU1 are included. As an optional implementation, the release management device 400 may include multiple processors; for example, in addition to processor 10, it may also include processor 50. Figure 2 (The example shown is a dashed line).

[0056] The memory 20 is used to store instructions. For example, the instructions may be computer programs. Optionally, the memory 20 may be a read-only memory (ROM) or other types of static storage devices that can store static information and / or instructions; it may also be a random access memory (RAM) or other types of dynamic storage devices that can store information and / or instructions; it may also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, etc. The embodiments of this application do not limit this.

[0057] It should be noted that the memory 20 can exist independently of the processor 10 or can be integrated with the processor 10. The memory 20 can be located inside or outside the release management device 400, and this application embodiment does not impose any restrictions on this.

[0058] Communication line 30 is used to transmit information between the various components included in the release management device 400.

[0059] The communication interface 40 is used to communicate with other devices (such as the aforementioned IC card reader 100, Bluetooth card reader 200, ANPR camera 300, or barrier gate 500, etc.) or other networks. This other communication network can be Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. The communication interface 40 can be a module, circuit, transceiver, or any device capable of communication.

[0060] It should be noted that, Figure 2 The structure shown does not constitute a limitation on the release management device 400, except Figure 2 In addition to the components shown, the release management device 400 may include more or fewer components than shown, or combinations of certain components, or different component arrangements.

[0061] The release management method provided in the embodiments of this application is described below.

[0062] Figure 3 This is a flowchart illustrating the release management method provided in an embodiment of this application. Figure 3 As shown, the method includes steps S101 to S105.

[0063] S101, the release management device 400 obtains the passage request data.

[0064] The passage request data can be the license plate number or identification data of the vehicle currently waiting to pass. As described in the aforementioned traffic management system, the vehicle currently waiting to pass can be a motorcycle or a car. The identification data can be IC card data or Bluetooth card data. Motorcycles correspond to IC card data. Cars correspond to Bluetooth card data.

[0065] Optionally, vehicles waiting to pass can be further divided into fixed vehicles and temporary vehicles. Fixed vehicles can be understood as vehicles that are permanently parked (or long-term parked) in parking lots managed by the traffic control system. Temporary vehicles can be understood as vehicles that are temporarily parked in parking lots managed by the traffic control system.

[0066] Based on the above understanding, the motor vehicles waiting to pass can be divided into the following four categories: fixed motorcycles, temporary motorcycles, fixed cars, and temporary cars. Optionally, the identification data for fixed motorcycles, temporary motorcycles, and temporary cars is IC card data, while the identification data for fixed cars is Bluetooth card data.

[0067] It should be noted that the above classification of identity data types is merely an example, and other classification methods are also possible, such as using IC card data or Bluetooth card data for all four types of vehicles waiting to pass. This application does not impose any limitations on this.

[0068] S102. When the passage request data is the license plate number of the motor vehicle currently waiting to pass, the passage management device 400 obtains the identity identification data to be verified.

[0069] S102 can be described with reference to the following embodiments, and will not be repeated here.

[0070] S103. If the identity identification data to be verified is Bluetooth card data, and the license plate number of the vehicle to be passed matches the identity identification data to be verified, then the release management device 400 controls the gate of the gate where the vehicle to be passed is located to release the vehicle.

[0071] For example, the release management device 400 may have a preset correspondence between license plate numbers and identity identification data. The release management device 400 can determine whether to release the vehicle based on the correspondence between license plate numbers and identity identification data, as well as the license plate number of the vehicle currently waiting to pass.

[0072] For example, the correspondence between license plate numbers and identity data can be shown in Table 1 below:

[0073] Table 1

[0074]

[0075]

[0076] As shown in Table 1, the correspondence between license plate numbers and identity data can specifically include a license plate number item and an identity data item. The identity data item can specifically include an IC card data item and a Bluetooth card data item. Specifically, the license plate number item can include license plate number 1 (motorcycle), license plate number 2 (motorcycle), license plate number 3 (car), and license plate number 4 (car). The IC card data item can specifically include IC card 1 and IC card 2. The Bluetooth card data item can specifically include Bluetooth card 1 and Bluetooth card 2. There is a correspondence between license plate number 1 (motorcycle) and IC card 1. There is a correspondence between license plate number 2 (motorcycle) and IC card 2. There is a correspondence between license plate number 3 (car) and Bluetooth card 1. There is a correspondence between license plate number 4 (car) and Bluetooth card 1.

[0077] S104. When the passage request data is identity identification data and the identity identification data is IC card data, the passage management device 400 obtains the license plate data to be verified.

[0078] S104 can be described with reference to the following embodiments, and will not be repeated here.

[0079] S105. If the identification data of the motor vehicle waiting to pass matches the license plate data to be verified, the release management device 400 controls the gate of the gate where the motor vehicle is located to release it.

[0080] S105 can be referred to in S103 above, and will not be repeated here.

[0081] Optionally, prior to S101, the current scenario can also be configured in software. For example, the release management device 400 can receive parking lot-related information, including adding lanes, adding ANPR cameras in lanes, adding IC card readers in lanes, adding Bluetooth card readers in lanes, setting the release rule to vehicle-card consistency, entering fixed vehicle license plates, and entering temporary card numbers.

[0082] In the release management method provided in this application embodiment, the release management device 400 can use the license plate number to verify the passage permission of the motor vehicle to be passed, and use the identity identification data to verify the consistency between the identified license plate and the motor vehicle to be passed, thereby realizing dual verification of the motor vehicle to be passed, improving the security of release management, and providing a solution for release management in high security scenarios that require vehicle-card consistency judgment.

[0083] In addition, identity data can be obtained using contact-based IC card data and long-range sensing Bluetooth card data, respectively, to meet the personalized needs of different users.

[0084] The following is a description of S102 and S103.

[0085] In some possible embodiments, the IC card reader, Bluetooth card reader, and ANPR camera can trigger license plate events and card swipe events, respectively. For the Bluetooth card data obtained during the card swipe event, the release management device 400 can match it with the license plate according to the Bluetooth card cache queue. In this case, Figure 4 This is another flowchart illustrating the release management method provided in an embodiment of this application. Figure 4 As shown, S102 can specifically include S1021, and S103 can be specifically implemented as S1031.

[0086] S1021. If the passage request data is the license plate number of the motor vehicle currently waiting to pass, and there is Bluetooth card data in the Bluetooth card cache queue, the release management device 400 uses the Bluetooth card data in the Bluetooth card cache queue as the identity identification data to be verified.

[0087] S1031. If the license plate number of the vehicle waiting to pass matches the Bluetooth card data in the Bluetooth card cache queue, the release management device 400 controls the gate of the gate where the vehicle waiting to pass is located to release the vehicle.

[0088] Optionally, if the license plate number of the motor vehicle waiting to pass is a temporary vehicle license plate number, the release management device 400 can control the gate not to release the vehicle.

[0089] Optionally, if there is no Bluetooth card data in the Bluetooth card cache queue, the access control device 400 can control the barrier gate not to allow passage.

[0090] Optionally, after S1031 above, the direction management device 400 may also clear the Bluetooth card cache queue.

[0091] It should be understood that Bluetooth card data has a relatively long recognition range, reaching approximately 5 to 15 meters, while license plate recognition requires the vehicle to approach the barrier gate. If the acquired Bluetooth card data is directly matched, there may be cases where the license plate number is empty (not yet recognized). In the release management method provided in this application embodiment, the release management device 400 can utilize a Bluetooth card cache queue to cache the acquired Bluetooth card data first, and then perform matching only when the license plate number is recognized. This provides a release control scheme for scenarios where Bluetooth card data is reported earlier than the license plate number.

[0092] In some possible embodiments, prior to S1021 described above, the release management device 400 may also acquire the Bluetooth buffer queue. In this case, Figure 5 This is another flowchart illustrating the release management method provided in an embodiment of this application. Figure 5 As shown, before S1021 above, the method may also include S201 to S202.

[0093] S201. If the passage request data is identity data and the identity data is Bluetooth card data, and there is no Bluetooth card data in the Bluetooth card cache queue, the release management device 400 will use the identity data of the current motor vehicle to be passed as the candidate Bluetooth card data.

[0094] Optionally, if Bluetooth card data exists in the Bluetooth card cache queue, that is, if there is already identified Bluetooth card data ahead, it can be assumed that there is a fixed car ahead that has not yet been released. In this case, the release management device 400 may not perform any operation.

[0095] S202. If the candidate Bluetooth card data is different from the Bluetooth card data corresponding to one or more historically passed motor vehicles in the first cycle, or if the time interval between the acquisition time of the candidate Bluetooth card data and the acquisition time of the target Bluetooth card data is greater than a preset time threshold, then the release management device 400 will add the candidate Bluetooth card data to the Bluetooth card cache queue.

[0096] The first cycle can be preset by the administrator in the release management device 400. For example, the first cycle can be 2 minutes or 3 minutes. This embodiment does not limit the specific duration of the first cycle. The target Bluetooth card data is the Bluetooth card data corresponding to the last historically passed vehicle among one or more historically passed vehicles. The preset duration threshold can be preset by the administrator in the release management device 400. For example, the preset duration threshold can be 10 seconds or 15 seconds. This embodiment does not limit the specific duration of the preset duration threshold.

[0097] Optionally, if the candidate Bluetooth card data is the same as the Bluetooth card data corresponding to any one of the historically passed motor vehicles, or if the acquisition time of the candidate Bluetooth card data and the acquisition time of the target Bluetooth card data are less than a preset time threshold, then the release management device 400 may not update the Bluetooth card cache queue.

[0098] It should be understood that Bluetooth card data has a relatively long recognition range, reaching approximately 5 to 15 meters. Furthermore, Bluetooth cards are typically placed in the driver's seat or on the windshield. After a vehicle is allowed to pass through the gate, it may continue to report Bluetooth card data to the Bluetooth card reader, thus interfering with the recognition of vehicles that have not yet been released. In the release management method provided in this application embodiment, the release management device 400 can filter out Bluetooth card data reported by vehicles that have already passed through the gate based on two conditions: the Bluetooth card data is different from that of historically passed vehicles, and the interval between the Bluetooth card data of the last historically passed vehicle and the data of the last passed vehicle is greater than a preset time threshold. This prevents the Bluetooth card data reported by vehicles that have already passed through the gate from interfering with the recognition of vehicles that have not yet been released.

[0099] The following is a description of S104.

[0100] In some possible embodiments, the access request data can also be IC card data. In this case, Figure 6 This is another flowchart illustrating the release management method provided in an embodiment of this application. Figure 6 As shown, the above S104 can specifically include S1041.

[0101] S1041. When the passage request data is identity identification data and the identity identification data is IC card data, the release management device 400 obtains the license plate number of the motor vehicle waiting to pass that has not been released within a preset time period as the license plate data to be verified.

[0102] The preset duration can be pre-set by the administrator in the release management device 400. For example, the preset duration could be 3 minutes or 5 minutes. This application embodiment does not limit the specific value of the preset duration. Vehicles waiting to pass that have not been released within the preset duration include currently waiting vehicles.

[0103] It should be understood that Bluetooth card data has a longer recognition range, reaching approximately 5 to 15 meters, while IC card data requires the IC card reader to deactivate the IC card. Therefore, in actual traffic scenarios, a situation may arise where a motorcycle is in front and a car is behind. In this case, the motorcycle's license plate number has already been reported, while the car is still queuing behind the motorcycle and has not yet reported its license plate number. However, due to the longer recognition range of Bluetooth card data, the car's Bluetooth card data is reported first, followed by the motorcycle's IC card data. In the release management method provided in this application embodiment, after obtaining IC card data, the release management device 400 can match the IC card data with the license plate numbers of motor vehicles waiting to pass within a preset time period, thereby verifying and releasing the motorcycles queuing in front. This achieves a release management scheme that uses a combination of contact IC cards and long-range inductive Bluetooth cards.

[0104] Optionally, before controlling the gate to release the vehicle, the method may further include: the release management device 400 determining whether the vehicle to be released is a temporary vehicle or a fixed vehicle based on the license plate number of the vehicle to be released; and the release management device 400 issuing a prompt message to indicate whether the vehicle to be released is a temporary vehicle or a fixed vehicle.

[0105] For example, the release management device 400 may also include an input / output interface. This input / output interface may be a display screen or a speaker, etc. The aforementioned prompt information may be text information displayed on the display screen or voice information emitted by the speaker, etc. This application embodiment does not impose any limitations on this.

[0106] Based on the understanding of the above embodiments, the release management method provided in this application embodiment will be described below using the data processing flow as an example. Figure 7 This is another flowchart illustrating the release management method provided in this application embodiment. Optionally, this method can be executed by the aforementioned release management device 400, such as... Figure 7 As shown, the method includes steps S301 to S317.

[0107] S301, obtain passage request data multiple times.

[0108] S301 can be referred to as described in S1011 above, and will not be repeated here.

[0109] S302. Determine whether the passage request data is a license plate number.

[0110] If yes, then execute S303; otherwise, execute S304.

[0111] S303. Determine whether the license plate number belongs to a fixed vehicle.

[0112] If yes, then execute S305; otherwise, execute S306.

[0113] S304. Determine whether the passage request data is IC card data.

[0114] If yes, then execute S309; ​​otherwise, determine that the access request data is Bluetooth card data and execute S310.

[0115] S305. Determine if there is Bluetooth card data in the Bluetooth card cache queue.

[0116] If yes, then execute S307; otherwise, execute S306.

[0117] S305 can be referred to in S1021 above, and will not be repeated here.

[0118] S306, Not allowed.

[0119] S307. Determine if the vehicle and card match.

[0120] If yes, then execute S308; otherwise, execute S306.

[0121] S307 can be referred to in S103 or S104 above, and will not be repeated here.

[0122] S308, Released.

[0123] S309. Determine whether the IC card data is the IC card data that has already been entered.

[0124] If yes, then execute S311; if no, then determine that it is an invalid card and execute S306.

[0125] S310. Determine whether Bluetooth card data exists in the Bluetooth card buffer queue.

[0126] If yes, then execute S313; otherwise, execute S314.

[0127] S311: Match license plates that have not been released within the last 3 minutes.

[0128] S312. Determine whether the matched license plate belongs to a fixed vehicle.

[0129] If yes, then execute S307; otherwise, determine that the matched license plate is a temporary vehicle and execute S308.

[0130] S309, S311, and S312 can be referred to in S1041 above, and will not be repeated here.

[0131] S313. Determine whether the acquired Bluetooth card data is the same as the Bluetooth card processed in the previous step and whether the interval does not exceed 10 seconds.

[0132] If yes, then execute S315; otherwise, execute S316.

[0133] S314. If it is determined that the preceding stationary vehicle has not yet been released, no action will be taken.

[0134] S315. If the gate crossing is confirmed to be a false alarm, no action will be taken.

[0135] S316. Cache the acquired Bluetooth card data into the Bluetooth card cache queue.

[0136] S313 to S316 can be referred to as described in S201 to S202 above, and will not be repeated here.

[0137] S317, Clear Bluetooth card cache queue.

[0138] The foregoing primarily describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the aforementioned functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0139] In an exemplary embodiment, this application also provides a release management device. Figure 8 This is a schematic diagram illustrating the composition of the release management device provided in an embodiment of this application. Figure 8 As shown, the device includes an acquisition module 801 and a processing module 802.

[0140] The acquisition module 801 is used to acquire passage request data; the passage request data is the license plate number or identity identification data of the motor vehicle currently waiting to pass; if the passage request data is the license plate number of the motor vehicle currently waiting to pass, the identity identification data to be verified is acquired.

[0141] The processing module 802 is used to control the gate of the current vehicle to be passed to release the vehicle if the identity identification data to be verified is Bluetooth card data and the license plate number of the vehicle to be passed matches the identity identification data to be verified.

[0142] The acquisition module 801 is also used to acquire the license plate data to be verified when the passage request data is identity identification data and the identity identification data is IC card data.

[0143] The processing module 802 is also used to control the gate of the gate where the vehicle to be passed is located to allow passage if the identity data of the vehicle to be passed matches the license plate data to be verified.

[0144] In some possible embodiments, the acquisition module 801 is specifically used to use the Bluetooth card data in the Bluetooth card cache queue as the identity identification data to be verified when the passage request data is the license plate number of the motor vehicle to be passed and there is Bluetooth card data in the Bluetooth card cache queue; the processing module 802 is specifically used to control the gate of the gate where the motor vehicle to be passed is located to release the vehicle if the license plate number of the motor vehicle to be passed matches the Bluetooth card data in the Bluetooth card cache queue.

[0145] In other possible embodiments, the processing module 802 is further configured to: if the passage request data is identity data and the identity data is Bluetooth card data, and there is no Bluetooth card data in the Bluetooth card cache queue, then use the identity data of the current vehicle to be passed as candidate Bluetooth card data; if the candidate Bluetooth card data is different from the Bluetooth card data corresponding to one or more historical vehicles that have passed in the first period, or if the time interval between the acquisition time of the candidate Bluetooth card data and the acquisition time of the target Bluetooth card data is greater than a preset time threshold, then add the candidate Bluetooth card data to the Bluetooth card cache queue; the target Bluetooth card data is the Bluetooth card data corresponding to the last historical vehicle that has passed in one or more historical vehicles; if the candidate Bluetooth card data is the same as the Bluetooth card data corresponding to any one of the historical vehicles that have passed in one or more historical vehicles, or if the time interval between the acquisition time of the candidate Bluetooth card data and the acquisition time of the target Bluetooth card data is less than a preset time threshold, then do not update the Bluetooth card cache queue.

[0146] In some other possible embodiments, the acquisition module 801 is specifically used to acquire the license plate number of a motor vehicle that has not been released within a preset time period as the license plate data to be verified when the passage request data is identity identification data and the identity identification data is IC card data.

[0147] In some other possible embodiments, before controlling the gate to allow passage, the processing module 802 is also used to determine whether the vehicle waiting to pass is a temporary vehicle or a fixed vehicle based on the license plate number of the vehicle waiting to pass; and to issue a prompt message to indicate whether the vehicle waiting to pass is a temporary vehicle or a fixed vehicle.

[0148] In some other possible embodiments, the motor vehicle currently waiting to pass includes a motorcycle or a car; the identification data corresponding to the motorcycle is IC card data; and the identification data corresponding to the car is Bluetooth card data.

[0149] It should be noted that, Figure 8 The module division shown is illustrative and represents only one logical functional division; in actual implementation, other division methods are possible. For example, two or more functions can be integrated into a single processing module. These integrated modules can be implemented in hardware or as software functional units.

[0150] In an exemplary embodiment, this application also provides a readable storage medium including software instructions that, when run on a release management device, cause the release management device to perform any of the methods provided in the above embodiments.

[0151] In an exemplary embodiment, this application also provides a computer program product containing computer execution instructions, which, when run on a release management device, causes the release management device to perform any of the methods provided in the above embodiments.

[0152] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer-executable instructions. When these computer-executable instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer-executable instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer-executable instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), etc.

[0153] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple components. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0154] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

[0155] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of release management, characterized by, The application relates to a release management scheme applied to a mixed use of a contact type IC card and a long-distance induction type Bluetooth card, and the method comprises the following steps: acquiring passage request data; the passage request data is a license plate number or identity data of a current motor vehicle to be passed; the identity data comprises Bluetooth card data or IC card data, and the identifiable range of the Bluetooth card data is larger than that of the IC card data; in the case that the passage request data is the license plate number of the current motor vehicle to be passed and Bluetooth card data exists in a Bluetooth card cache queue, taking the Bluetooth card data in the Bluetooth card cache queue as the identity data to be verified; the Bluetooth card data stored in the Bluetooth card cache queue is different from Bluetooth card data corresponding to one or more historical motor vehicles to be passed in a first period, or the time interval between the acquisition time of the Bluetooth card data stored in the Bluetooth card cache queue and the acquisition time of target Bluetooth card data is greater than a preset time threshold, and the target Bluetooth card data is Bluetooth card data corresponding to the last historical motor vehicle to be passed in the one or more historical motor vehicles to be passed; if the identity data to be verified is Bluetooth card data and the license plate number of the current motor vehicle to be passed matches the identity data to be verified, controlling a barrier gate of a gate through which the current motor vehicle to be passed passes to be released; in the case that the passage request data is identity data and the identity data is IC card data, acquiring a license plate number of a motor vehicle to be passed, which has a recognized license plate number but has not been released in a preset time, as license plate data to be verified, and if the identity data of the current motor vehicle to be passed matches the license plate data to be verified, controlling the barrier gate of the gate through which the current motor vehicle to be passed passes to be released.

2. The method according to claim 1, wherein if the identity data to be verified is Bluetooth card data and the license plate number of the current motor vehicle to be passed matches the identity data to be verified, controlling the barrier gate of the gate through which the current motor vehicle to be passed passes to be released, comprises: if the license plate number of the current motor vehicle to be passed matches the Bluetooth card data in the Bluetooth card cache queue, controlling the barrier gate of the gate through which the current motor vehicle to be passed passes to be released.

3. The method of claim 2, wherein, The method further comprises: in the case that the passage request data is identity data and the identity data is Bluetooth card data, if no Bluetooth card data exists in the Bluetooth card cache queue, taking the identity data of the current motor vehicle to be passed as candidate Bluetooth card data; if the candidate Bluetooth card data is different from Bluetooth card data corresponding to one or more historical motor vehicles to be passed in a first period or the time interval between the acquisition time of the candidate Bluetooth card data and the acquisition time of target Bluetooth card data is greater than a preset time threshold, adding the candidate Bluetooth card data to the Bluetooth card cache queue. If the candidate Bluetooth card data is identical to the Bluetooth card data corresponding to any one of the one or more historical passing motor vehicles, or the acquisition time of the candidate Bluetooth card data is less than the acquisition time of the target Bluetooth card data by the preset time threshold, the Bluetooth card cache queue is not updated.

4. The method of claim 1, wherein, Before controlling the barrier to release, the method further comprises: determining, according to the license plate number of the current motor vehicle to be passed, whether the current motor vehicle to be passed is a temporary vehicle or a fixed vehicle; issuing prompt information to prompt that the current motor vehicle to be passed is a temporary vehicle or a fixed vehicle.

5. The method according to any one of claims 1 to 4, characterized in that, The current motor vehicle to be passed includes a motorcycle or a car; the identity data corresponding to the motorcycle is IC card data; and the identity data corresponding to the car is Bluetooth card data.

6. A release management apparatus characterized by comprising: The application is applied to a release management scheme for mixed use of a contact type IC card and a long-distance induction type Bluetooth card, and the device comprises an acquisition module and a processing module. The acquisition module is configured to acquire passage request data; the passage request data is a license plate number or identity data of a current motor vehicle to be passed; the identity data includes Bluetooth card data or IC card data, and the identifiable range of the Bluetooth card data is greater than the identifiable range of the IC card data; in a case where the passage request data is a license plate number of a current motor vehicle to be passed and there is Bluetooth card data in the Bluetooth card cache queue, the Bluetooth card data in the Bluetooth card cache queue is taken as the identity data to be verified; the Bluetooth card data stored in the Bluetooth card cache queue is different from the Bluetooth card data corresponding to one or more historical passing motor vehicles in a first period, or the acquisition time of the Bluetooth card data stored in the Bluetooth card cache queue is separated from the acquisition time of target Bluetooth card data by a time greater than a preset time threshold, and the target Bluetooth card data is the Bluetooth card data corresponding to the last historical passing motor vehicle of the one or more historical passing motor vehicles. The processing module is configured to, if the identity data to be verified is Bluetooth card data and the license plate number of the current motor vehicle to be passed matches the identity data to be verified, control a barrier at a gate where the current motor vehicle to be passed is located to release. The acquisition module is further configured to, in a case where the passage request data is identity data and the identity data is IC card data, acquire a license plate number of a motor vehicle to be passed, which has a recognized license plate number but has not been released within a preset time, as license plate data to be verified. The processing module is further configured to, if the identity data of the current motor vehicle to be passed matches the license plate data to be verified, control a barrier at a gate where the current motor vehicle to be passed is located to release.

7. A release management apparatus characterized by comprising: comprises: a processor and a memory; the memory stores instructions executable by the processor; the processor is configured to execute the instructions, so that the release management device implements the method according to any one of claims 1-5.

8. A readable storage medium, characterized by, The readable storage medium comprises software instructions; when the software instructions run in the release management device, the release management device implements the method according to any one of claims 1-5.

9. A release management system characterized by, The application discloses a release management scheme applied to a mixed use of a contact type IC card and a long-distance induction type Bluetooth card, and the system comprises an integrated circuit (IC) card reader, a Bluetooth card reader, an automatic number plate recognition (ANPR) camera, a release management device and a barrier gate; the IC card reader, the Bluetooth card reader, the ANPR camera and the barrier gate are connected with the release management device. The IC card reader is used for collecting IC card data. The Bluetooth card reader is used for collecting Bluetooth card data. The ANPR camera is used for collecting a license plate number of a current motor vehicle to be passed. The release management device is configured to acquire passage request data; the passage request data is a license plate number of a current motor vehicle to be passed or identity data; the identity data comprises Bluetooth card data or IC card data, and the identifiable range of the Bluetooth card data is larger than that of the IC card data; in the case that the passage request data is the license plate number of the current motor vehicle to be passed and Bluetooth card data exists in a Bluetooth card cache queue, the Bluetooth card data in the Bluetooth card cache queue is taken as the identity data to be verified; the Bluetooth card data stored in the Bluetooth card cache queue is different from Bluetooth card data corresponding to one or more historical motor vehicles having passed in a first period, or the acquisition time of the Bluetooth card data stored in the Bluetooth card cache queue and the acquisition time of target Bluetooth card data are separated by a time length greater than a preset time length threshold, the target Bluetooth card data is Bluetooth card data corresponding to the last historical motor vehicle having passed in the one or more historical motor vehicles having passed; if the identity data to be verified is the Bluetooth card data, and the license plate number of the current motor vehicle to be passed and the identity data to be verified match each other, the barrier gate at the gate where the current motor vehicle to be passed is located is controlled to release; in the case that the passage request data is the identity data and the identity data is the IC card data, a license plate number of a motor vehicle to be passed, which has a recognized license plate number but has not been released in a preset time length, is taken as identity data to be verified; if the identity data of the current motor vehicle to be passed and the identity data to be verified match each other, the barrier gate at the gate where the current motor vehicle to be passed is located is controlled to release.

Images