CN116206300B - Multi-manufacturer identification camera integration compatible method, equipment and storage medium - Google Patents
Multi-manufacturer identification camera integration compatible method, equipment and storage medium Download PDFInfo
- Publication number
- CN116206300B CN116206300B CN202310491679.8A CN202310491679A CN116206300B CN 116206300 B CN116206300 B CN 116206300B CN 202310491679 A CN202310491679 A CN 202310491679A CN 116206300 B CN116206300 B CN 116206300B
- Authority
- CN
- China
- Prior art keywords
- camera
- license plate
- identification
- recognition
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003860 storage Methods 0.000 title claims abstract description 56
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000010354 integration Effects 0.000 title claims abstract description 15
- 230000007123 defense Effects 0.000 claims abstract description 17
- 238000013507 mapping Methods 0.000 claims description 14
- 230000006870 function Effects 0.000 claims description 10
- 230000008569 process Effects 0.000 claims description 7
- 230000007246 mechanism Effects 0.000 claims description 6
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 230000005059 dormancy Effects 0.000 claims description 3
- 238000012545 processing Methods 0.000 abstract description 6
- 230000011218 segmentation Effects 0.000 abstract 2
- 238000010586 diagram Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000009826 distribution Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V20/00—Scenes; Scene-specific elements
- G06V20/60—Type of objects
- G06V20/62—Text, e.g. of license plates, overlay texts or captions on TV images
- G06V20/625—License plates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V10/00—Arrangements for image or video recognition or understanding
- G06V10/10—Image acquisition
- G06V10/12—Details of acquisition arrangements; Constructional details thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5018—Thread allocation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Multimedia (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Traffic Control Systems (AREA)
Abstract
The application discloses a multi-manufacturer identification camera integration compatible method, equipment and a storage medium, and belongs to the technical field of traffic control systems. The method comprises the following steps: introducing license plate recognition control at the front end of the system; based on the license plate recognition control, camera connection information of each recognition camera is obtained and sent to the rear end of the system; the rear end of the system performs segmentation processing on the camera connection information and stores the segmentation processing into a preset storage structure body; determining preset specific implementation classes corresponding to all the identification cameras according to the storage structure body, and starting license plate identification threads corresponding to the identification cameras according to the specific implementation classes; triggering license plate recognition events under the condition that the vehicle enters the defense arrangement area of the corresponding recognition camera, and calling the corresponding manufacturer recognition SDK through the license plate recognition thread of the corresponding recognition camera to acquire vehicle license plate information. The method solves the problem that license plate recognition cameras of different manufacturers are loaded in the same program, and realizes license plate recognition calling of multiple manufacturers.
Description
Technical Field
The application relates to the technical field of databases, in particular to a multi-manufacturer identification camera integration compatible method, equipment and a storage medium.
Background
The existing license plate recognition integration mode is integrated on the basis of calling a manufacturer SDK library, and is generally single-manufacturer single-call; when two or more manufacturer cameras (for example, cameras of different manufacturers appear on the left and right sides of the wagon balance) are simultaneously appeared, the SDK of each manufacturer needs to be reinitialized, which is very easy to cause two problems: firstly, resource waste is caused, and unnecessary resources are consumed; secondly, this alternate initialization and thread invocation approach is particularly prone to browser crashes.
Therefore, how to load license plate recognition cameras of different manufacturers in the same set of program and realize the license plate recognition calling of multiple manufacturers becomes a technical problem to be solved urgently.
Disclosure of Invention
The embodiment of the application provides a multi-manufacturer identification camera integration compatible method, equipment and storage medium, which are used for solving the following technical problems: and how to load license plate recognition cameras of different manufacturers in the same set of program so as to realize the recognition and the calling of license plates of multiple manufacturers.
In a first aspect, an embodiment of the present application provides a multi-vendor identification camera integration compatible method, which is characterized in that the method includes: introducing license plate recognition control at the front end of the system; the license plate recognition control is used for controlling dynamic connection files corresponding to the recognition cameras; the front end of the system is based on license plate recognition controls, camera connection information of each recognition camera is obtained, and the camera connection information is sent to the rear end of the system; dividing the camera connection information at the rear end of the system, and storing the divided camera connection information into a preset storage structure; determining preset specific implementation classes corresponding to all the identification cameras according to the storage structure body, and starting license plate identification threads corresponding to the identification cameras according to the specific implementation classes; triggering license plate recognition events under the condition that a vehicle enters a defense arrangement area of a corresponding recognition camera, so as to call a corresponding manufacturer recognition SDK through a license plate recognition thread of the corresponding recognition camera, and acquire vehicle license plate information; and sending the acquired license plate information of the vehicle to the front end of the system.
In one implementation manner of the application, introducing a license plate recognition control at the front end of the system specifically comprises: determining the CLSID value of a dynamic connection file corresponding to each identification camera; constructing a calling address mapping table of the CLSID value and the dynamic connection file, and packaging the calling address mapping table into a license plate recognition control; and installing a license plate recognition space at the front end of the system to finish initialization introduction.
In one implementation manner of the present application, before acquiring the camera connection information of each identification camera based on the license plate identification control, the method further includes: creating a database, and storing camera information of each identification camera in the database; wherein, the camera information includes: camera connection information, camera manufacturer information, and camera position information; the camera connection information includes: camera IP, username, password, port number, channel number, control parameters; the camera manufacturer information at least comprises: vendor ID, vendor map call package; the camera position information includes at least: camera mounting position code, camera number, camera physical address code.
In one implementation of the present application, before sending the camera connection information to the system backend, the method further includes: dividing specific parameter information in each camera connection information based on a preset first special symbol; and carrying out serial combination on the camera connection information, and inserting a preset second special symbol between the camera connection information.
In one implementation manner of the present application, determining, according to a storage structure, a preset specific implementation class corresponding to each identification camera specifically includes: defining a public interface; wherein the public interface comprises the following steps: starting license plate recognition, closing license plate recognition and releasing manufacturer SDK resources; defining a specific implementation class of each identification camera for realizing a public interface; based on the connection information of each camera in the storage structure body, the specific implementation class corresponding to each identification camera is mapped through a C# reflection mechanism, so that each identification camera can synchronously start a license plate identification thread.
In one implementation manner of the present application, before starting the license plate recognition thread of the corresponding recognition camera according to the specific implementation class, the method further includes: defining license plate recognition threads of all recognition cameras; the license plate recognition thread at least comprises the following preset attribute information: the circulation times, the dormancy time, the connection time and disconnection reconnection time of the license plate recognition camera; and logging in the interface through the camera connection information in the storage structure body, acquiring a user handle, and calling a corresponding recognition camera to start the defense distribution mode through the user handle.
In one implementation manner of the present application, calling a corresponding vendor identification SDK through a license plate identification thread corresponding to the identification camera, and obtaining a vehicle license plate specifically includes: calling a corresponding manufacturer identification SDK through a license plate identification thread of a corresponding identification camera, identifying a vehicle image acquired by the identification camera, and storing an identification result in a storage structure body of the corresponding identification camera; and (3) circulating the identification process of the preset times, determining whether the identification results in the storage structure body are consistent, and determining that the identification results are the vehicle license plate information of the vehicle under the condition that the identification results are consistent.
In one implementation of the present application, before the acquiring the system front end, the method further includes: and setting a callback function at the front end of the system so that the front end can receive the vehicle license plate information sent by the rear end of the system based on the callback function.
In a second aspect, an embodiment of the present application further provides a multi-vendor identification camera integrated compatible device, where the device includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to: introducing license plate recognition control at the front end of the system; the license plate recognition control is used for controlling dynamic connection files corresponding to the recognition cameras; the front end of the system is based on license plate recognition controls, camera connection information of each recognition camera is obtained, and the camera connection information is sent to the rear end of the system; dividing the camera connection information at the rear end of the system, and storing the divided camera connection information into a preset storage structure; determining preset specific implementation classes corresponding to all the identification cameras according to the storage structure body, and starting license plate identification threads corresponding to the identification cameras according to the specific implementation classes; triggering license plate recognition events under the condition that a vehicle enters a defense arrangement area of a corresponding recognition camera, so as to call a corresponding manufacturer recognition SDK through a license plate recognition thread of the corresponding recognition camera, and acquire vehicle license plate information; and sending the acquired license plate information of the vehicle to the front end of the system.
In a third aspect, embodiments of the present application further provide a multi-vendor identification camera integrated compatible non-volatile computer storage medium storing computer executable instructions, where the computer executable instructions are configured to: introducing license plate recognition control at the front end of the system; the license plate recognition control is used for controlling dynamic connection files corresponding to the recognition cameras; the front end of the system is based on license plate recognition controls, camera connection information of each recognition camera is obtained, and the camera connection information is sent to the rear end of the system; dividing the camera connection information at the rear end of the system, and storing the divided camera connection information into a preset storage structure; determining preset specific implementation classes corresponding to all the identification cameras according to the storage structure body, and starting license plate identification threads corresponding to the identification cameras according to the specific implementation classes; triggering license plate recognition events under the condition that a vehicle enters a defense arrangement area of a corresponding recognition camera, so as to call a corresponding manufacturer recognition SDK through a license plate recognition thread of the corresponding recognition camera, and acquire vehicle license plate information; and sending the acquired license plate information of the vehicle to the front end of the system.
According to the scheme, license plate recognition integration work is greatly saved for a system with a plurality of license plate recognition manufacturers, and the system is not a traditional single linear calling mode of a single channel, but a plurality of message transmission mechanisms such as license plate recognition defense setting parameters, defense setting modes, triggering frequencies, interaction modes, callback messages and the like are adopted; the license plate recognition method is compatible with license plate recognition of multiple manufacturers and multiple camera defense deployment modes as much as possible while ensuring the performance.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
fig. 1 is a flowchart of a multi-vendor identification camera integration compatibility method provided in an embodiment of the present application;
fig. 2 is a schematic diagram of an internal structure of a multi-vendor identification camera integrated compatible device according to an embodiment of the present application.
Detailed Description
For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The embodiment of the application provides a multi-manufacturer identification camera integration compatible method, equipment and storage medium, which are used for solving the following technical problems: and how to load license plate recognition cameras of different manufacturers in the same set of program so as to realize the recognition and the calling of license plates of multiple manufacturers.
The following describes in detail the technical solution proposed in the embodiments of the present application through the accompanying drawings.
Fig. 1 is a flowchart of a multi-vendor identification camera integration compatibility method provided in an embodiment of the present application. As shown in fig. 1, the method for integrating and compatible multi-vendor identification cameras provided in the embodiment of the application specifically includes the following steps:
step 101, introducing license plate recognition control at the front end of the system.
In one embodiment of the present application, the license plate recognition control is used to control dynamic connection files corresponding to each recognition camera. Introducing license plate recognition control at the front end of the system, which comprises the following steps: determining the CLSID value of a dynamic connection file corresponding to each identification camera; constructing a calling address mapping table of the CLSID value and the dynamic connection file, and packaging the calling address mapping table into a license plate recognition control; and installing a license plate recognition space at the front end of the system to finish initialization introduction.
Step 102, acquiring camera connection information of each identification camera by the front end of the system based on the license plate identification control, and sending the camera connection information to the rear end of the system.
In one embodiment of the present application, it is first noted that the license plate recognition is implemented based on license plate recognition cameras, and each license plate recognition camera has different IP, user name, password, and manufacturer model, but each piece of information is necessary for license plate recognition, so it is necessary to store the information. Therefore, before acquiring the camera connection information of each identification camera based on the license plate identification control, a database needs to be created, and the camera information of each identification camera is stored in the database.
In one embodiment of the present application, the camera information includes: camera connection information, camera manufacturer information, and camera position information; the camera connection information includes: camera IP, username, password, port number, channel number, control parameters; the camera manufacturer information at least comprises: vendor ID, vendor map call package; the camera position information includes at least: camera mounting position code, camera number, camera physical address code.
In one embodiment of the present application, the front end of the system obtains camera connection information of each recognition camera based on the license plate recognition control, and specifically includes: and calling an address mapping table based on the license plate recognition control so as to read camera connection information of each recognition camera in the database through the dynamic connection file corresponding to each recognition camera.
In one embodiment of the present application, after acquiring the camera connection information of each identification camera, specific parameter information in each camera connection information is segmented based on a preset first special symbol; and carrying out serial combination on the camera connection information, and inserting a preset second special symbol between the camera connection information.
In one embodiment of the present application, the camera connection information is sent to the system back end after the insertion of the special symbol.
And 103, dividing the camera connection information at the rear end of the system, and storing the divided camera connection information into a preset storage structure body.
In one embodiment of the present application, after the system rear end receives the camera connection information, the information is first split into a plurality of camera connection information according to the second special symbol; and then, according to the first special symbol, identifying specific parameters in the camera connection information, and storing the specific parameters into the preset structural body.
It should be noted that, the structure body defined here is actually a camera element information set, the outer layer is each camera, and the inner layer is detailed information of each camera; the structure body is used for storing information, the information is more convenient to store and call, and timeliness is high.
And 104, determining a preset specific implementation class corresponding to each identification camera according to the storage structure body, and starting a license plate identification thread corresponding to the identification cameras according to the specific implementation class.
In one embodiment of the present application, after the system backend has partitioned information and stored data in a storage structure, a common interface is defined; wherein the public interface comprises the following steps: starting license plate recognition, closing license plate recognition and releasing manufacturer SDK resources; defining a specific implementation class of each identification camera for realizing a public interface; based on the connection information of each camera in the storage structure body, the specific implementation class corresponding to each identification camera is mapped through a C# reflection mechanism, so that each identification camera can synchronously start a license plate identification thread.
In one embodiment of the present application, before starting the license plate recognition thread of the corresponding recognition camera according to the specific implementation class, the license plate recognition thread of each recognition camera needs to be defined; the license plate recognition thread at least comprises the following preset attribute information: the circulation times, the dormancy time, the connection time and disconnection reconnection time of the license plate recognition camera; and logging in the interface through the camera connection information in the storage structure body, acquiring a user handle, and calling a corresponding recognition camera to start the defense distribution mode through the user handle.
Step 105, triggering a license plate recognition event to call a corresponding manufacturer recognition SDK through a license plate recognition thread of the corresponding recognition camera to acquire vehicle license plate information under the condition that the vehicle enters a defense arrangement area of the corresponding recognition camera.
In one embodiment of the application, when a vehicle enters a defense arrangement area of a corresponding identification camera, triggering a license plate identification event, calling a corresponding manufacturer identification SDK through a license plate identification thread of the corresponding identification camera, identifying a vehicle image acquired by the identification camera, and storing an identification result in a storage structure body of the corresponding identification camera; and (3) circulating the identification process of the preset times, determining whether the identification results in the storage structure body are consistent, and determining that the identification results are the vehicle license plate information of the vehicle under the condition that the identification results are consistent.
And step 106, the acquired license plate information of the vehicle is sent to the front end of the system.
In one embodiment of the present application, before the system front end is acquired, a callback function needs to be set at the system front end, so that the front end can receive the vehicle license plate information sent by the system back end based on the callback function.
In one embodiment of the application, after the license plate identification thread of the corresponding identification camera calls the corresponding manufacturer identification SDK to acquire the license plate information of the vehicle, the acquired license plate information of the vehicle is sent to the front end of the system.
The foregoing is a method embodiment presented herein. Based on the same inventive concept, the embodiment of the application also provides a multi-manufacturer identification camera integrated compatible device, and the structure of the multi-manufacturer identification camera integrated compatible device is shown in fig. 2.
Fig. 2 is a schematic diagram of an internal structure of a multi-vendor identification camera integrated compatible device according to an embodiment of the present application. As shown in fig. 2, the apparatus includes:
at least one processor 201;
and a memory 202 communicatively coupled to the at least one processor;
wherein the memory 202 stores instructions executable by the at least one processor, the instructions being executable by the at least one processor 201 to enable the at least one processor 201 to:
introducing license plate recognition control at the front end of the system; the license plate recognition control is used for controlling dynamic connection files corresponding to the recognition cameras; the front end of the system is based on license plate recognition controls, camera connection information of each recognition camera is obtained, and the camera connection information is sent to the rear end of the system; dividing the camera connection information at the rear end of the system, and storing the divided camera connection information into a preset storage structure; determining preset specific implementation classes corresponding to all the identification cameras according to the storage structure body, and starting license plate identification threads corresponding to the identification cameras according to the specific implementation classes; triggering license plate recognition events under the condition that a vehicle enters a defense arrangement area of a corresponding recognition camera, so as to call a corresponding manufacturer recognition SDK through a license plate recognition thread of the corresponding recognition camera, and acquire vehicle license plate information; and sending the acquired license plate information of the vehicle to the front end of the system.
Some embodiments of the present application provide a multi-vendor identification camera integration compatible non-volatile computer storage medium corresponding to fig. 1, storing computer executable instructions configured to:
introducing license plate recognition control at the front end of the system; the license plate recognition control is used for controlling dynamic connection files corresponding to the recognition cameras; the front end of the system is based on license plate recognition controls, camera connection information of each recognition camera is obtained, and the camera connection information is sent to the rear end of the system; dividing the camera connection information at the rear end of the system, and storing the divided camera connection information into a preset storage structure; determining preset specific implementation classes corresponding to all the identification cameras according to the storage structure body, and starting license plate identification threads corresponding to the identification cameras according to the specific implementation classes; triggering license plate recognition events under the condition that a vehicle enters a defense arrangement area of a corresponding recognition camera, so as to call a corresponding manufacturer recognition SDK through a license plate recognition thread of the corresponding recognition camera, and acquire vehicle license plate information; and sending the acquired license plate information of the vehicle to the front end of the system.
All embodiments in the application are described in a progressive manner, and identical and similar parts of all embodiments are mutually referred, so that each embodiment mainly describes differences from other embodiments. In particular, for the internet of things device and the medium embodiment, since they are substantially similar to the method embodiment, the description is relatively simple, and the relevant points are referred to in the description of the method embodiment.
The systems and media and the methods provided in the embodiments of the present application are in one-to-one correspondence, so that the systems and media also have similar beneficial technical effects to the corresponding methods, and since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the systems and media are not described here again.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.
Claims (7)
1. A multi-vendor identification camera integration compatible method, the method comprising:
introducing license plate recognition control at the front end of the system; the license plate recognition control is used for controlling dynamic connection files corresponding to the recognition cameras;
the front end of the system acquires camera connection information of each identification camera based on the license plate identification control, and sends the camera connection information to the rear end of the system;
dividing the camera connection information at the rear end of the system, and storing the divided camera connection information into a preset storage structure;
determining a preset specific implementation class corresponding to each identification camera according to the storage structure body, and starting a license plate identification thread corresponding to the identification cameras according to the specific implementation class;
triggering license plate recognition events under the condition that a vehicle enters a defense arrangement area of a corresponding recognition camera, so as to call a corresponding manufacturer recognition SDK through a license plate recognition thread of the corresponding recognition camera, and acquire vehicle license plate information;
the acquired license plate information of the vehicle is sent to the front end of the system;
introducing license plate recognition controls at the front end of the system, wherein the license plate recognition controls specifically comprise:
determining the CLSID value of a dynamic connection file corresponding to each identification camera;
constructing a calling address mapping table of the CLSID value and the dynamic connection file, and packaging the calling address mapping table into a license plate recognition control;
installing the license plate recognition control at the front end of the system to finish initialization introduction;
before acquiring the camera connection information of each identification camera based on the license plate identification control, the method further comprises the following steps:
creating a database, and storing camera information of each identification camera in the database;
wherein, the camera information includes: camera connection information, camera manufacturer information, and camera position information;
the camera connection information includes: camera IP, username, password, port number, channel number, control parameters;
the camera manufacturer information at least comprises: vendor ID, vendor map call package;
the camera position information at least comprises: camera mounting position code, camera number and camera physical address code;
according to the storage structure, determining a preset specific implementation class corresponding to each identification camera, wherein the specific implementation class comprises the following steps:
defining a public interface; wherein the common interface comprises the following steps: starting license plate recognition, closing license plate recognition and releasing manufacturer SDK resources;
defining a specific implementation class of each identification camera for realizing the public interface;
based on the connection information of each camera in the storage structure body, mapping the specific implementation class corresponding to each identification camera through a C# reflection mechanism, so that each identification camera can synchronously start a license plate identification thread.
2. The multi-vendor identification camera integration compatible method of claim 1, wherein prior to transmitting the camera connection information to the system back-end, the method further comprises:
dividing specific parameter information in each camera connection information based on a preset first special symbol;
and carrying out serial combination on the camera connection information, and inserting a preset second special symbol between the camera connection information.
3. The method of claim 1, wherein before turning on a license plate recognition thread of a corresponding recognition camera according to the specific implementation class, the method further comprises:
defining license plate recognition threads of all recognition cameras; the license plate recognition thread at least comprises the following preset attribute information: the circulation times, the dormancy time, the connection time and disconnection reconnection time of the license plate recognition camera;
and logging in an interface through the camera connection information in the storage structure body, acquiring a user handle, and calling a corresponding recognition camera to start a defense deployment mode through the user handle.
4. The method for integrating and compatible with multiple vendor-identified cameras according to claim 1, wherein the method for acquiring the vehicle license plate comprises the steps of:
calling a corresponding manufacturer identification SDK through a license plate identification thread of a corresponding identification camera, identifying a vehicle image acquired by the identification camera, and storing an identification result in a storage structure body of the corresponding identification camera;
and (3) circulating the identification process of preset times, determining whether the identification results in the storage structure body are consistent, and determining that the identification results are the vehicle license plate information of the vehicle under the condition that the identification results are consistent.
5. The multi-vendor identification camera integration compatible method of claim 1, wherein prior to the accessing the system front end, the method further comprises:
and setting a callback function at the front end of the system so that the front end can receive the vehicle license plate information sent by the rear end of the system based on the callback function.
6. A multi-vendor identification camera integrated compatible device, the device comprising:
at least one processor;
and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to:
introducing license plate recognition control at the front end of the system; the license plate recognition control is used for controlling dynamic connection files corresponding to the recognition cameras;
the front end of the system acquires camera connection information of each identification camera based on the license plate identification control, and sends the camera connection information to the rear end of the system;
dividing the camera connection information at the rear end of the system, and storing the divided camera connection information into a preset storage structure;
determining a preset specific implementation class corresponding to each identification camera according to the storage structure body, and starting a license plate identification thread corresponding to the identification cameras according to the specific implementation class;
triggering license plate recognition events under the condition that a vehicle enters a defense arrangement area of a corresponding recognition camera, so as to call a corresponding manufacturer recognition SDK through a license plate recognition thread of the corresponding recognition camera, and acquire vehicle license plate information;
the acquired license plate information of the vehicle is sent to the front end of the system;
introducing license plate recognition controls at the front end of the system, wherein the license plate recognition controls specifically comprise:
determining the CLSID value of a dynamic connection file corresponding to each identification camera;
constructing a calling address mapping table of the CLSID value and the dynamic connection file, and packaging the calling address mapping table into a license plate recognition control;
installing the license plate recognition control at the front end of the system to finish initialization introduction;
before acquiring the camera connection information of each identification camera based on the license plate identification control, the license plate identification control further comprises:
creating a database, and storing camera information of each identification camera in the database;
wherein, the camera information includes: camera connection information, camera manufacturer information, and camera position information;
the camera connection information includes: camera IP, username, password, port number, channel number, control parameters;
the camera manufacturer information at least comprises: vendor ID, vendor map call package;
the camera position information at least comprises: camera mounting position code, camera number and camera physical address code;
according to the storage structure, determining a preset specific implementation class corresponding to each identification camera, wherein the specific implementation class comprises the following steps:
defining a public interface; wherein the common interface comprises the following steps: starting license plate recognition, closing license plate recognition and releasing manufacturer SDK resources;
defining a specific implementation class of each identification camera for realizing the public interface;
based on the connection information of each camera in the storage structure body, mapping the specific implementation class corresponding to each identification camera through a C# reflection mechanism, so that each identification camera can synchronously start a license plate identification thread.
7. A multi-vendor identification camera integrated compatible non-volatile computer storage medium storing computer executable instructions, the computer executable instructions configured to:
introducing license plate recognition control at the front end of the system; the license plate recognition control is used for controlling dynamic connection files corresponding to the recognition cameras;
the front end of the system acquires camera connection information of each identification camera based on the license plate identification control, and sends the camera connection information to the rear end of the system;
dividing the camera connection information at the rear end of the system, and storing the divided camera connection information into a preset storage structure;
determining a preset specific implementation class corresponding to each identification camera according to the storage structure body, and starting a license plate identification thread corresponding to the identification cameras according to the specific implementation class;
triggering license plate recognition events under the condition that a vehicle enters a defense arrangement area of a corresponding recognition camera, so as to call a corresponding manufacturer recognition SDK through a license plate recognition thread of the corresponding recognition camera, and acquire vehicle license plate information;
the acquired license plate information of the vehicle is sent to the front end of the system;
introducing license plate recognition controls at the front end of the system, wherein the license plate recognition controls specifically comprise:
determining the CLSID value of a dynamic connection file corresponding to each identification camera;
constructing a calling address mapping table of the CLSID value and the dynamic connection file, and packaging the calling address mapping table into a license plate recognition control;
installing the license plate recognition control at the front end of the system to finish initialization introduction;
before acquiring the camera connection information of each identification camera based on the license plate identification control, the license plate identification control further comprises:
creating a database, and storing camera information of each identification camera in the database;
wherein, the camera information includes: camera connection information, camera manufacturer information, and camera position information;
the camera connection information includes: camera IP, username, password, port number, channel number, control parameters;
the camera manufacturer information at least comprises: vendor ID, vendor map call package;
the camera position information at least comprises: camera mounting position code, camera number and camera physical address code;
according to the storage structure, determining a preset specific implementation class corresponding to each identification camera, wherein the specific implementation class comprises the following steps:
defining a public interface; wherein the common interface comprises the following steps: starting license plate recognition, closing license plate recognition and releasing manufacturer SDK resources;
defining a specific implementation class of each identification camera for realizing the public interface;
based on the connection information of each camera in the storage structure body, mapping the specific implementation class corresponding to each identification camera through a C# reflection mechanism, so that each identification camera can synchronously start a license plate identification thread.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310491679.8A CN116206300B (en) | 2023-05-05 | 2023-05-05 | Multi-manufacturer identification camera integration compatible method, equipment and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310491679.8A CN116206300B (en) | 2023-05-05 | 2023-05-05 | Multi-manufacturer identification camera integration compatible method, equipment and storage medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN116206300A CN116206300A (en) | 2023-06-02 |
CN116206300B true CN116206300B (en) | 2024-02-27 |
Family
ID=86515011
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202310491679.8A Active CN116206300B (en) | 2023-05-05 | 2023-05-05 | Multi-manufacturer identification camera integration compatible method, equipment and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN116206300B (en) |
Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101441628A (en) * | 2007-11-19 | 2009-05-27 | 上海新纳广告传媒有限公司 | Intelligent client terminal website system based on desktop application program |
US8950007B1 (en) * | 2008-04-07 | 2015-02-03 | Lumension Security, Inc. | Policy-based whitelisting with system change management based on trust framework |
CN105160884A (en) * | 2015-07-30 | 2015-12-16 | 北京工业大学 | Vehicle identification method and device fusing video monitoring and RFID |
CN105721831A (en) * | 2016-01-28 | 2016-06-29 | 安徽四创电子股份有限公司 | Method for designing video monitoring client side based on multi-process architecture |
CN106412127A (en) * | 2016-12-07 | 2017-02-15 | 清华大学苏州汽车研究院(吴江) | IPv6 and IPv4 dual-stack compatible road monitoring video analysis system |
CN106657797A (en) * | 2017-02-27 | 2017-05-10 | 济南浪潮高新科技投资发展有限公司 | Camera calling method, camera calling device and camera calling system |
KR101753117B1 (en) * | 2016-09-21 | 2017-07-05 | (주) 플래누리 | Lpr system for controlling entrance time and exit time of vehicle by implementing camera and lpr module integrally and the method threof |
CN107741866A (en) * | 2017-09-29 | 2018-02-27 | 山东浪潮通软信息科技有限公司 | A kind of implementation method for realizing multi-vendor video camera front end loading |
CN109409280A (en) * | 2018-10-22 | 2019-03-01 | 郑州云海信息技术有限公司 | A kind of driving warning system, method, equipment, platform and medium |
CN111191481A (en) * | 2018-11-14 | 2020-05-22 | 杭州海康威视数字技术股份有限公司 | Vehicle identification method and system |
CN111294556A (en) * | 2020-02-07 | 2020-06-16 | 山东浪潮通软信息科技有限公司 | Video front-end processing method based on GB/T28181 |
CN111832337A (en) * | 2019-04-16 | 2020-10-27 | 高新兴科技集团股份有限公司 | License plate recognition method and device |
CN114485874A (en) * | 2021-12-22 | 2022-05-13 | 航天信息股份有限公司 | Automatic weighing method based on grain depot license plate recognition |
CN114495297A (en) * | 2021-12-31 | 2022-05-13 | 广东奥博信息产业股份有限公司 | Parking-free payment parking management method and system based on intelligent terminal |
CN114758501A (en) * | 2022-04-24 | 2022-07-15 | 浪潮软件科技有限公司 | Traffic big data support platform and device |
CN115116233A (en) * | 2022-06-28 | 2022-09-27 | 深圳市奥肯特科技有限公司 | Parking space blocking device based on license plate recognition |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2493190A4 (en) * | 2009-10-23 | 2013-03-06 | Sharp Kk | Master device, map table update method, program, and recording medium |
-
2023
- 2023-05-05 CN CN202310491679.8A patent/CN116206300B/en active Active
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101441628A (en) * | 2007-11-19 | 2009-05-27 | 上海新纳广告传媒有限公司 | Intelligent client terminal website system based on desktop application program |
US8950007B1 (en) * | 2008-04-07 | 2015-02-03 | Lumension Security, Inc. | Policy-based whitelisting with system change management based on trust framework |
CN105160884A (en) * | 2015-07-30 | 2015-12-16 | 北京工业大学 | Vehicle identification method and device fusing video monitoring and RFID |
CN105721831A (en) * | 2016-01-28 | 2016-06-29 | 安徽四创电子股份有限公司 | Method for designing video monitoring client side based on multi-process architecture |
KR101753117B1 (en) * | 2016-09-21 | 2017-07-05 | (주) 플래누리 | Lpr system for controlling entrance time and exit time of vehicle by implementing camera and lpr module integrally and the method threof |
CN106412127A (en) * | 2016-12-07 | 2017-02-15 | 清华大学苏州汽车研究院(吴江) | IPv6 and IPv4 dual-stack compatible road monitoring video analysis system |
CN106657797A (en) * | 2017-02-27 | 2017-05-10 | 济南浪潮高新科技投资发展有限公司 | Camera calling method, camera calling device and camera calling system |
CN107741866A (en) * | 2017-09-29 | 2018-02-27 | 山东浪潮通软信息科技有限公司 | A kind of implementation method for realizing multi-vendor video camera front end loading |
CN109409280A (en) * | 2018-10-22 | 2019-03-01 | 郑州云海信息技术有限公司 | A kind of driving warning system, method, equipment, platform and medium |
CN111191481A (en) * | 2018-11-14 | 2020-05-22 | 杭州海康威视数字技术股份有限公司 | Vehicle identification method and system |
CN111832337A (en) * | 2019-04-16 | 2020-10-27 | 高新兴科技集团股份有限公司 | License plate recognition method and device |
CN111294556A (en) * | 2020-02-07 | 2020-06-16 | 山东浪潮通软信息科技有限公司 | Video front-end processing method based on GB/T28181 |
CN114485874A (en) * | 2021-12-22 | 2022-05-13 | 航天信息股份有限公司 | Automatic weighing method based on grain depot license plate recognition |
CN114495297A (en) * | 2021-12-31 | 2022-05-13 | 广东奥博信息产业股份有限公司 | Parking-free payment parking management method and system based on intelligent terminal |
CN114758501A (en) * | 2022-04-24 | 2022-07-15 | 浪潮软件科技有限公司 | Traffic big data support platform and device |
CN115116233A (en) * | 2022-06-28 | 2022-09-27 | 深圳市奥肯特科技有限公司 | Parking space blocking device based on license plate recognition |
Non-Patent Citations (1)
Title |
---|
车辆牌照识别系统的设计与仿真;张敏;李爱兰;;电子测试;20160305(第05期);12-13 * |
Also Published As
Publication number | Publication date |
---|---|
CN116206300A (en) | 2023-06-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10505796B2 (en) | Network function virtualization | |
KR102674017B1 (en) | Network resource management method, system, network device and readable storage medium | |
CN112328363B (en) | Cloud hard disk mounting method and device | |
CN112783642A (en) | In-container logic configuration method, device and computer readable medium | |
CN112738181B (en) | Method, device and server for cluster external IP access | |
CN116206300B (en) | Multi-manufacturer identification camera integration compatible method, equipment and storage medium | |
CN106855821B (en) | Distributed transaction processing method and device | |
CN110958278B (en) | API gateway-based data processing method and system and API gateway | |
CN112600765B (en) | Method and device for scheduling configuration resources | |
CN114217697A (en) | Multi-screen input method and device, electronic equipment and computer readable storage medium | |
CN108563514A (en) | Access method, application and the electronic equipment of application configuration service | |
CN113741912A (en) | Model management system, method, device and equipment | |
CN111045812A (en) | Block chain intelligent contract reverse calling method, equipment and medium | |
CN113010263A (en) | Method, system, equipment and storage medium for creating virtual machine in cloud platform | |
CN112749149A (en) | Database switching method and device | |
CN112583740A (en) | Network communication method and device | |
CN111404709B (en) | Method and device for operating policy rules under network function virtualization | |
CN117573359B (en) | Heterogeneous cluster-based computing framework management system and method | |
CN111767330B (en) | Data interaction method and device, electronic equipment and storage medium | |
US11757830B2 (en) | Method and apparatus for allocating CTDB-based virtual IP address, and distributed storage device | |
CN117076473B (en) | Metadata operation method, system, equipment and medium for SaaS multi-tenant | |
CN110659033B (en) | Protocol registration distribution method, storage medium, electronic equipment and system | |
CN116186145A (en) | Method, device, system, equipment and medium for realizing database service isolation | |
CN113568964A (en) | Method, device and medium for using session temporary table in connection pool | |
CN116578398A (en) | Task scheduling method, device and storage medium based on blockchain |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |