CN115934773A - Method and device for checking flow data of highway, server and storage medium - Google Patents
Method and device for checking flow data of highway, server and storage medium Download PDFInfo
- Publication number
- CN115934773A CN115934773A CN202310015432.9A CN202310015432A CN115934773A CN 115934773 A CN115934773 A CN 115934773A CN 202310015432 A CN202310015432 A CN 202310015432A CN 115934773 A CN115934773 A CN 115934773A
- Authority
- CN
- China
- Prior art keywords
- inspected
- data
- water data
- running water
- vehicle
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 50
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims abstract description 298
- 238000007689 inspection Methods 0.000 claims abstract description 124
- 230000002159 abnormal effect Effects 0.000 claims abstract description 107
- 238000012795 verification Methods 0.000 claims description 119
- 238000012550 audit Methods 0.000 claims description 17
- 238000012216 screening Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 241001124569 Lycaenidae Species 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000010223 real-time analysis Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a method and a device for checking highway running water data, a server and a storage medium, wherein the method comprises the following steps: acquiring running water data to be inspected corresponding to a target highway; determining abnormal running water data and vehicle information corresponding to each abnormal running water data from running water data to be inspected through a pre-configured running water inspection model; the running water inspection model comprises a plurality of inspection sub-models; and generating an abnormal evidence chain corresponding to each piece of vehicle information based on the abnormal running water data so as to execute intercepting operation on the target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain. The method and the device can obviously improve the efficiency of checking the highway running water data and can also obviously improve the accuracy of checking the abnormal running water data.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a method and a device for checking highway running data, a server and a storage medium.
Background
At present, when a vehicle owner drives a vehicle to pass through a highway, the toll is not paid due to subjective or objective reasons, such as the fact that a door frame fails to record the toll accurately, or the door frame cannot communicate with a vehicle-mounted device and cannot be charged due to malicious fee evasion behaviors of the vehicle owner, so that the toll calculation is deviated, and the charging order of the highway is influenced. Therefore, it is very important to accurately audit the flow data of the highway. However, in the prior art, abnormal flow data needs to be manually screened from the flow data and assembled into an evidence chain for further manual review, which results in slower inspection efficiency and lower inspection accuracy of the flow data.
Disclosure of Invention
In view of the above, the present invention provides a method, an apparatus, a server and a storage medium for checking highway running data, which can significantly improve the efficiency of checking highway running data and the accuracy of checking abnormal running data.
In a first aspect, an embodiment of the present invention provides a method for checking highway running water data, including: acquiring running water data to be inspected corresponding to a target highway; determining abnormal running water data and vehicle information corresponding to each abnormal running water data from the running water data to be inspected through a pre-configured running water inspection model; the running inspection model comprises a plurality of inspection submodels; and generating an abnormal evidence chain corresponding to each piece of vehicle information based on the abnormal running water data, and executing an intercepting operation on a target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain.
In one embodiment, the method for determining abnormal running water data from the running water data to be inspected through a pre-configured running water inspection model comprises the following steps: if the inspection submodel comprises a charging abnormity inspection submodel, performing access record verification, passing medium verification, green pass verification and account clearing amount verification on the flowing water data to be inspected through the charging abnormity inspection submodel, and if the flowing water data to be inspected does not pass the verification, determining that the flowing water data to be inspected is abnormal flowing water data; if the checking sub-model comprises a daily checking sub-model, performing export running water verification and vehicle identification verification on the running water data to be checked through the daily checking sub-model, and if the running water data to be checked does not pass the verification, determining that the running water data to be checked is abnormal running water data; if the inspection submodel comprises a vehicle information abnormity inspection submodel, performing vehicle type verification, running time verification and designated vehicle verification on the running water data to be inspected through the vehicle information abnormity inspection submodel, and if the running water data to be inspected does not pass the verification, determining that the running water data to be inspected is abnormal running water data; and if the checking submodel comprises an fee evasion checking submodel, vehicle blacklist data is obtained, fee evasion checking is carried out on the running water data to be checked through the fee evasion checking submodel based on the vehicle blacklist data, and if the running water data to be checked does not pass the checking, the running water data to be checked is determined to be abnormal running water data.
In one embodiment, the steps of performing entry and exit record verification, passing medium verification, green pass verification and clearing amount verification on the running water data to be inspected include: if the to-be-inspected running water data does not meet the entrance and exit record inspection conditions, determining that the to-be-inspected running water data does not pass the entrance and exit record verification; wherein, the entrance and exit record inspection conditions comprise one or more of the following conditions: the method comprises the following steps that an entrance record corresponding to a normal exit record exists, an entrance record corresponding to an exit record of a specified portal exists, an exit record without a passing medium exists, data belonging to entrance override is stored, the entrance and exit time belongs to a specified time range, the number of seats of a vehicle is smaller than a specified number of seats, and the exit record corresponding to the entrance record exists in a first specified duration; extracting first to-be-inspected running water data carrying no passing medium mark from the to-be-inspected running water data, and determining that the first to-be-inspected running water data does not pass the passing medium check if the first to-be-inspected running water data does not belong to a first specified passing type; extracting second to-be-inspected flowing water data carrying a green-pass mark from the to-be-inspected flowing water data, and if the second to-be-inspected flowing water data does not meet green-pass inspection conditions, determining that the second to-be-inspected flowing water data does not pass the green-pass check; wherein the green inspection conditions comprise one or more of the following: the system belongs to the flow data corresponding to the type of the appointed vehicle, the same-station payment record exists within a second appointed time, and the flow data corresponding to the identification of the appointed vehicle; and if the account clearing difference of the account clearing data in the to-be-inspected flowing water data is larger than a first specified value or smaller than a second specified value, determining that the to-be-inspected flowing water data does not pass the check of the account clearing amount.
In one embodiment, the step of performing export pipeline verification and vehicle identification verification on the pipeline data to be inspected includes: extracting third to-be-inspected flowing water data which does not belong to a second specified passage type from the to-be-inspected flowing water data, and if the inlet vehicle type and the outlet vehicle type in the third to-be-inspected flowing water data are inconsistent or the inlet passage medium code and the outlet passage medium code in the third to-be-inspected flowing water data are inconsistent, determining that the third to-be-inspected flowing water data do not pass the outlet flowing water verification; and extracting the to-be-inspected flowing water data which does not carry the ETC identification or the open toll station identification from the to-be-inspected flowing water data, and removing the to-be-inspected flowing water data to obtain fourth to-be-inspected flowing water data, wherein if the inlet vehicle identification and the outlet vehicle identification in the fourth to-be-inspected flowing water data are inconsistent, the fourth to-be-inspected flowing water data is determined not to pass the vehicle identification verification.
In one embodiment, the steps of vehicle type verification, running time verification and designated vehicle verification on the running water data to be inspected comprise: if the inlet vehicle type or the outlet vehicle type in the running water data to be inspected is not consistent with the historical vehicle type, or the quantity of the historical vehicle types corresponding to the single vehicle identification is updated according to the running water data to be inspected, and if the quantity of the updated historical vehicle types is larger than the preset quantity, it is determined that the running water data to be inspected does not pass the vehicle type verification; calculating the running time of the vehicle according to the running data to be inspected, and if the running time of the vehicle is greater than the preset fastest time, and the difference value between the running time of the vehicle and the preset fastest time is greater than a first preset time threshold value, determining that the running data to be inspected does not pass the running time verification; or if the vehicle running time is less than preset slowest time and the difference value between the vehicle running time and the preset slowest time is greater than a second preset time threshold, determining that the running time verification is not passed by the running data to be inspected; and if the to-be-inspected running water data does not belong to a third appointed passing type, or the to-be-inspected running water data does not carry an emergency release mark, or no co-stop payment record exists in the to-be-inspected running water data within a third appointed time length, determining that the to-be-inspected running water data does not pass the appointed vehicle verification.
In one embodiment, the step of fee evasion checking the running water data to be checked based on the vehicle blacklist data comprises the following steps: and if the vehicle identification in the running water data to be inspected is located in the vehicle blacklist data, determining that the running water data to be inspected does not pass the fee evasion check.
In one embodiment, the step of performing an intercepting operation on the target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain includes: sending the abnormal evidence chain to a designated associated terminal so as to feed back an audit result corresponding to the abnormal evidence chain through the designated associated terminal; and if the audit result is that the audit is passed, generating additional payment push information based on the abnormal evidence chain, and sending the additional payment push information to an additional payment system so as to execute intercepting operation on the target vehicle corresponding to each piece of vehicle information through the additional payment system.
In a second aspect, an embodiment of the present invention further provides an apparatus for checking highway running water data, including: the data acquisition module is used for acquiring the running water data to be inspected corresponding to the target highway; the inspection module is used for determining abnormal running water data and vehicle information corresponding to each abnormal running water data from the running water data to be inspected through a pre-configured running water inspection model; the running water inspection model comprises a plurality of inspection sub-models; and the evidence chain generating module is used for generating an abnormal evidence chain corresponding to each piece of vehicle information based on the abnormal running data so as to execute intercepting operation on the target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain.
In a third aspect, an embodiment of the present invention further provides a server, including a processor and a memory, where the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement any one of the methods provided in the first aspect.
In a fourth aspect, embodiments of the present invention also provide a computer-readable storage medium storing computer-executable instructions that, when invoked and executed by a processor, cause the processor to implement any one of the methods provided in the first aspect.
The method, the device, the server and the storage medium for checking the highway running water data provided by the embodiment of the invention are characterized in that the running water data to be checked corresponding to a target highway is firstly obtained, abnormal running water data and vehicle information corresponding to each abnormal running water data are determined from the running water data to be checked through a pre-configured running water checking model, and finally an abnormal evidence chain corresponding to each vehicle information is generated based on the abnormal running water data so as to execute intercepting operation on a target vehicle corresponding to each vehicle information according to the abnormal evidence chain. The running water inspection model comprises a plurality of inspection submodels. The method can utilize a plurality of inspection submodels in the flow inspection model to inspect the flow data to be inspected for a plurality of items, so as to screen the abnormal flow data with questions from the flow data to be inspected and further generate a relevant abnormal evidence chain for vehicle interception.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flow chart illustrating an inspection method for highway running water data according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a pipeline inspection model according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an apparatus for inspecting highway flowing water data according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the embodiments, and it is obvious that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
At present, the problems of slow inspection efficiency and low inspection accuracy of the flow data exist in the prior art, and therefore, the invention provides the method, the device, the server and the storage medium for inspecting the flow data of the highway, which can obviously improve the efficiency of inspecting the flow data of the highway and the accuracy of inspecting the abnormal flow data.
To facilitate understanding of the embodiment, first, a detailed description is given to an inspection method for highway running water data disclosed in the embodiment of the present invention, referring to a flow chart of the inspection method for highway running water data shown in fig. 1, the method mainly includes the following steps S102 to S106:
and S102, acquiring the running water data to be inspected corresponding to the target highway. The running water data to be checked mainly comprises four types of data of export, entry, portal and brand identification, and the export type data can comprise export records, export time and the like. In one embodiment, the to-be-inspected flow data can be read from the relevant equipment for managing the highway, and an uploading channel can be provided for the user, so that the to-be-inspected flow data uploaded by the user can be obtained through the channel.
And step S104, determining abnormal running water data and vehicle information corresponding to each abnormal running water data from the running water data to be inspected through a pre-configured running water inspection model. The running water inspection model comprises a plurality of inspection submodels, the inspection submodels can comprise one or more of a charging abnormity inspection submodel, a daily inspection submodel, a vehicle information abnormity inspection submodel, an fee evasion inspection submodel and an inspection fee compensation management submodel, the charging abnormity inspection submodel is used for providing one or more of entrance and exit record verification, passage medium verification, green pass verification and account clearing amount verification, the daily inspection submodel is used for providing exit running water verification and/or vehicle identification verification, the vehicle information abnormity inspection submodel is used for providing one or more of vehicle type verification, running time verification and designated vehicle verification, the fee evasion inspection submodel is used for providing fee evasion verification, and the inspection fee compensation management submodel is used for inspecting and paying.
In one embodiment, the running water data to be checked can be respectively input into each checking submodel, the running water data to be checked is correspondingly checked by each checking submodel, if the running water data to be checked passes the checking, the running water data to be checked is not abnormal running water data, otherwise, if the running water data to be checked does not pass the checking, the running water data to be checked belongs to the abnormal running water data.
And step S106, generating an abnormal evidence chain corresponding to each piece of vehicle information based on the abnormal running data, and executing intercepting operation on the target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain. In an implementation mode, the abnormal running data can be assembled into an abnormal evidence chain, the abnormal evidence chain is used as to-be-audited tracing details to be pushed to manual auditing, the pushed payment information is sent to a tracing system when the manual auditing is passed, then the vehicle information corresponding to the abnormal running data is added to a blacklist through the tracing system, and the blacklist is pushed to achieve vehicle interception.
The method for inspecting the highway running water data can inspect the to-be-inspected running water data in multiple ways by utilizing multiple inspection submodels in the running water inspection model, screen out abnormal running water data with questions from the to-be-inspected running water data, and further generate a related abnormal evidence chain for vehicle interception.
In order to facilitate understanding of the step S104, the embodiment of the present invention provides a flow chart inspection model, referring to a schematic diagram of the flow chart inspection model shown in fig. 2, where fig. 2 illustrates inspection items including abnormal charging inspection, daily inspection, abnormal vehicle information inspection, malicious fee evasion inspection, and inspection compensation management. On the basis of fig. 2, an embodiment of the present invention provides an implementation manner for determining abnormal running water data from running water data to be inspected through a pre-configured running water inspection model, which can be specifically referred to as the following (1) to (5):
(1) And if the inspection submodel comprises a charge abnormity inspection submodel, performing access record verification, passing medium verification, green pass verification and clearing amount verification on the running water data to be inspected through the charge abnormity inspection submodel, and if the running water data to be inspected does not pass the verification, determining that the running water data to be inspected is abnormal running water data. Referring to fig. 2, the entry and exit record check (which may also be referred to as "checking with an entry and no exit") is to check whether the flow data to be checked has an entry and no exit, the pass medium check (which may also be referred to as "checking without a pass medium") is to check whether the flow data to be checked has no pass medium, the green pass check (which may also be referred to as "checking with an abnormal green pass") is to check whether the flow data to be checked has an abnormal green pass, and the clearing amount check (which may also be referred to as "checking with an abnormal clearing amount") is to check whether the flow data to be checked has an abnormal clearing data.
For convenience of understanding, an embodiment of the present invention provides an implementation manner of performing entry and exit record verification, pass medium verification, green pass verification, and clearing amount verification on to-be-inspected flow data, which is described in the following (1.1) to (1.4):
(1.1) if the running water data to be inspected does not meet the inspection conditions of the entrance and exit records, determining that the running water data to be inspected does not pass the entrance and exit record verification; wherein, the exit record inspection conditions comprise one or more of the following conditions: the method comprises the following steps of storing an entrance record corresponding to a normal exit record, storing an entrance record corresponding to an exit record of a specified portal (such as a provincial portal), storing an exit record of a non-passing medium, storing entrance override data, storing entrance and exit time in a specified time range (such as holidays) and a vehicle seat number smaller than a specified seat number (such as 7 seats), and storing an exit record corresponding to the entrance record in a first specified time period (such as 24 hours or 7 days). With continued reference to FIG. 2, while performing an entry/exit audit: (a) Recording an entry passage record (entry record for short); (b) excluding entry records with normal exits; (c) excluding entry records exiting the provincial portal; (d) Excluding the data recorded by the non-passing medium outlet, and it should be noted that the data recorded by the non-passing medium outlet can be checked by the passing medium check; (e) excluding entrance treatment superordinate data; (f) excluding vehicles with 7 seats and below on holidays. Aiming at the to-be-inspected flow data except the to-be-inspected flow data, further executing: (g) If the data exceeds 7 days and no exit record is found, determining that the data does not pass the inspection of the entrance and the exit; (h) If no record of the same license plate exit exists within 24 hours of the entrance time, the check of the entrance and the exit is determined not to pass; (i) And if other export transaction records within 7 days are not inquired, determining that the import and export check is not passed, wherein only other export transaction records which are the latest within 7 days are inquired.
And (1.2) extracting first to-be-inspected flow data carrying no passing medium mark from the to-be-inspected flow data, and if the first to-be-inspected flow data does not belong to a first appointed passing type (including 10 emergency, 8 military police, 6 public affairs, 12 free, 14 motorcade and 2 green passing), determining that the first to-be-inspected flow data does not pass the passing medium check. Continuing with fig. 2, while performing no-pass medium audit: (a) screening the exit passage records in real time; (b) Screening out data with an outlet marked as a non-passing medium, and excluding open data; (c) Filtering out 10 urgent, 8 military police, 6 public affairs, 12 free, 14 motorcade, 2 green pass, the remaining data will be determined as failing to pass the no-passing medium audit table and added to the no-passing medium audit table.
(1.3) extracting second to-be-inspected flowing water data carrying a green pass mark from the flowing water data to be inspected, and if the second to-be-inspected flowing water data does not meet green pass inspection conditions, determining that the second to-be-inspected flowing water data does not pass green pass inspection; wherein, the green inspection conditions comprise one or more of the following conditions: the running water data corresponding to the specified vehicle type (such as a truck), the co-stop payment record in a second specified time (such as 15 minutes), and the running water data corresponding to the specified vehicle identification (such as a free license plate). With continued reference to fig. 2, while performing a green pass exception check: (a) analyzing exit traffic records in real time; (b) screening export transaction records marked as green pass; (c) truck rejection (screening only non-truck records); (d) the same-station payment record data is obtained within 15 minutes before and after the elimination; and (e) excluding the characteristic library vehicle type as a free license plate.
(1.4) if the clearing difference of the clearing data in the running data to be checked is larger than a first specified value (such as 0) or smaller than a second specified value (such as 0), determining that the running data to be checked does not pass the checking amount check. With continued reference to fig. 2, while performing an inventory exception audit: (a) Analyzing the clearing data uploaded to the center by the toll station in real time; (b) Screening the clearing records with the clearing balance amount larger than 0 and smaller than 0; (c) The difference of the account clearing is greater than 0 yuan and is marked as long money to be added into the checking library, and the sum of the account clearing is less than 0 yuan and is marked as short money to be added into the checking library.
(2) And if the checking submodel comprises a daily checking submodel, performing outlet running water verification and vehicle identification verification on the running water data to be checked through the daily checking submodel, and if the running water data to be checked does not pass the verification, determining the running water data to be checked as abnormal running water data. Referring to fig. 2, outlet flow verification (also referred to as outlet flow inspection) is to verify whether outlet flow in the to-be-inspected flow data is abnormal, and vehicle identification verification (also referred to as inlet and outlet license plate inconsistency inspection) is to verify whether an outlet license plate and an inlet license plate in the to-be-inspected flow data are consistent.
For convenience of understanding, the embodiment of the present invention provides an implementation manner of performing export pipeline verification and vehicle identification verification on pipeline data to be inspected, which is described in the following (2.1) to (2.2):
(2.1) extracting third to-be-inspected flowing water data which does not belong to a second specified passing type (comprising no passing medium, set 1, set 2, military police vehicles, single goods transport vehicles and emergency vehicles) from the to-be-inspected flowing water data, and if the inlet vehicle type and the outlet vehicle type in the third to-be-inspected flowing water data are inconsistent or the inlet passing medium code and the outlet passing medium code in the third to-be-inspected flowing water data are inconsistent, determining that the third to-be-inspected flowing water data do not pass outlet flowing water verification. Continuing with FIG. 2, while performing export pipeline inspection: (a) analyzing the outlet flow water in real time; (b) Eliminating no passing medium, 1, 2, military and police vehicles, single goods transport vehicles and emergency vehicles; (c) Judging whether the vehicle types and the vehicle types of the inlet and the outlet are consistent according to the outlet running water and the inlet running water, if not, determining that the vehicle types and the inlet running water do not pass the outlet running water inspection, and adding the outlet running water inspection into an outlet running water inspection list; (d) And judging whether the inlet and outlet traffic medium codes are consistent according to the outlet flow and the inlet flow, if not, determining that the codes pass through the outlet flow inspection, and adding the codes to an outlet flow inspection list.
And (2.2) extracting the running water data to be inspected, which does not carry an ETC (Electronic Toll Collection) identifier or an open Toll station identifier, from the running water data to be inspected, removing the running water data to be inspected to obtain fourth running water data to be inspected, and determining that the fourth running water data to be inspected does not pass vehicle identifier verification if the inlet vehicle identifier and the outlet vehicle identifier in the fourth running water data to be inspected are inconsistent. Please continue to refer to fig. 2, when the inconsistency of the entrance and exit license plates is checked: (a) analyzing non-ETC export transaction data; (b) excluding open charge seals; (c) Screening data of the inconsistency of the exit license plate and the entrance license plate at the position, and determining that the inconsistency of the exit license plate and the entrance license plate does not pass through the examination of the inconsistency of the entrance license plate and the exit license plate.
(3) And if the inspection sub-model comprises a vehicle information abnormity inspection sub-model, performing vehicle type verification, running time verification and designated vehicle verification on the running water data to be inspected through the vehicle information abnormity inspection sub-model, and if the running water data to be inspected does not pass the verification, determining the running water data to be inspected as abnormal running water data. Referring to fig. 2, the vehicle type check may also be referred to as a historical vehicle type anomaly check, the driving time check may also be referred to as a driving time anomaly check, and the designated vehicle check may also be referred to as an emergency vehicle anomaly check.
For convenience of understanding, the embodiment of the present invention provides an implementation manner of performing vehicle type verification, driving time verification and designated vehicle verification on to-be-inspected running water data, which is described in the following (3.1) to (3.3):
(3.1) if the inlet vehicle type or the outlet vehicle type in the running water data to be inspected is inconsistent with the historical vehicle type, or the quantity of the historical vehicle types corresponding to the single vehicle identification is updated according to the running water data to be inspected, and if the quantity of the updated historical vehicle types is larger than the preset quantity, it is determined that the running water data to be inspected does not pass vehicle type verification. With continued reference to fig. 2, while performing the historical vehicle type anomaly check: (a) real-time screening of exit traffic records; (b) The method comprises the steps of determining vehicle types with a vehicle characteristic library to be compared, if the vehicle types are inconsistent, adding running water data to be checked into a historical vehicle type abnormity checking table, wherein the vehicle type abnormity is also added into the historical vehicle type abnormity checking table, and the data needs checking and verifying; (c) Removing the data of the vehicles which are consistent with the comparison vehicle type of the vehicle characteristic library, green traffic, combine harvesters, emergency vehicles and manual release; (d) counting the passing times corresponding to the vehicle types in real time according to the license plates; (e) If the number of vehicles appearing on the same license plate in the system is more than 1, determining that the historical vehicle type abnormity inspection is not passed, and adding the running water data to be inspected into the historical vehicle type abnormity inspection table.
(3.2) calculating the running time of the vehicle according to the running water data to be inspected, and if the running time of the vehicle is greater than the preset fastest running time and the difference value between the running time of the vehicle and the preset fastest running time is greater than a first preset running time threshold value, determining that the running water data to be inspected does not pass the running time verification; or if the running time of the vehicle is less than the preset slowest time, and the difference value between the running time of the vehicle and the preset slowest time is greater than a second preset time threshold value, determining that the running data to be inspected does not pass the running time verification. With continued reference to fig. 2, while performing the travel time anomaly check: (a) real-time analysis of exit traffic records (MI, CPC); (b) excluding 0-metadata charging data; (c) excluding open toll stations; (d) The system sets the lowest speed at 47 km/h and the highest speed at 130 km/h; (e) The slowest hour = the mileage/the lowest hour, and the fastest hour = the mileage/the highest hour; (f) And when the exit records that the running time exceeds the time range of the fastest running time and the slowest running time and exceeds the range of 120 minutes for abnormity or exceeds twice the maximum running time, determining that the running water data to be inspected does not pass the running time abnormity inspection, and adding the running water data to the running time abnormity inspection list.
And (3.3) if the running water data to be inspected does not belong to a third appointed passage type (including free vehicles), or the running water data to be inspected does not carry an emergency release mark, or no stop-floor payment record exists in the running water data to be inspected within a third appointed time (such as 15 minutes), determining that the running water data to be inspected does not pass the verification of the appointed vehicles. With continued reference to fig. 2, in performing the emergency vehicle anomaly check: (a) real-time screening of exit traffic records; (b) Excluding data that the license plate is a free vehicle in the vehicle feature library; (c) Adding the data of the exit passage record marked as emergency release to an emergency vehicle abnormity inspection table; (d) The timing task processes whether the data has other transactions in the same station 15 minutes ago.
(4) And if the checking submodel comprises an fee evasion checking submodel, vehicle blacklist data is obtained, fee evasion checking is carried out on the running water data to be checked through the fee evasion checking submodel based on the vehicle blacklist data, and if the running water data to be checked does not pass the checking, the running water data to be checked is determined to be abnormal running water data. In one embodiment, if the vehicle identifier in the running water data to be inspected is located in the vehicle blacklist data, it is determined that the running water data to be inspected does not pass the fee evasion check. With continued reference to fig. 2, in particular implementations: the method comprises the following steps that (a) the center is divided to push license plate information corresponding to a blacklist; (b) Malicious fee evasion data reported by the toll station through the small program; (c) The types of reported data comprise big and small car logos, malicious car-following, false green-clear, overtime cards, fake license plates, breakthrough and the like; (d) Malicious fee evasion has been audited and the payment data pushed.
(5) If the inspection submodel comprises an inspection charging management submodel, please continue to refer to fig. 2, and data needs to be pushed manually: historical vehicle type abnormity, abnormal running time, abnormal emergency vehicle and other related data.
For the step S106, when the step of performing the intercepting operation on the target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain is performed, the abnormal evidence chain may be sent to the designated association terminal, so as to feed back the auditing result corresponding to the abnormal evidence chain through the designated association terminal; and if the verification result is that the verification is passed, generating additional payment push information based on the abnormal evidence chain, and sending the additional payment push information to an additional payment system so as to execute intercepting operation on the target vehicle corresponding to each piece of vehicle information through the additional payment system. During specific implementation, the abnormal running data can be assembled into an abnormal evidence chain, the abnormal evidence chain is used as to-be-audited tracing details to be pushed to manual auditing, the pushed payment information is sent to a tracing system when the manual auditing is passed, then vehicle information corresponding to the abnormal running data is added to a blacklist through the tracing system, and the blacklist is pushed to realize vehicle interception.
The embodiment of the invention is used for fighting against fee evasion and standardizing the charging order by checking all charging behaviors on the highway. Specifically, the embodiment of the invention analyzes 4 types of data generated in the charging link through a flow inspection model, then screens out abnormal flow data, and then manually inspects the abnormal flow data. And during screening, attaching a related abnormal evidence chain so as to facilitate the next processing after manual judgment. The method for inspecting the highway running water data provided by the embodiment of the invention can obviously improve the efficiency of inspecting the highway running water data and the accuracy of inspecting the abnormal running water data, thereby standardizing the charging order of the highway.
As to the method for inspecting highway flowing water data provided in the foregoing embodiment, an embodiment of the present invention provides an apparatus for inspecting highway flowing water data, and referring to a schematic structural diagram of the apparatus for inspecting highway flowing water data shown in fig. 3, the apparatus mainly includes the following components:
the data acquisition module 302 is used for acquiring the running water data to be inspected corresponding to the target highway;
the inspection module 304 is used for determining abnormal running water data and vehicle information corresponding to each abnormal running water data from the running water data to be inspected through a pre-configured running water inspection model; the running water inspection model comprises a plurality of inspection sub-models;
the evidence chain generating module 306 is configured to generate an abnormal evidence chain corresponding to each piece of vehicle information based on the abnormal running water data, so as to perform an intercepting operation on a target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain.
The inspection device for the highway running water data provided by the embodiment of the invention can utilize a plurality of inspection submodels in the running water inspection model to inspect the running water data to be inspected in a plurality of ways so as to screen the abnormal running water data with questions from the running water data to be inspected and further generate a related abnormal evidence chain for vehicle interception.
In one embodiment, the audit module 304 is further configured to: if the inspection sub-model comprises a charge abnormity inspection sub-model, performing access record verification, passing medium verification, green pass verification and clearing amount verification on the running water data to be inspected through the charge abnormity inspection sub-model, and if the running water data to be inspected does not pass the verification, determining the running water data to be inspected as abnormal running water data; if the checking sub-model comprises a daily checking sub-model, performing outlet running water verification and vehicle identification verification on the running water data to be checked through the daily checking sub-model, and if the running water data to be checked does not pass the verification, determining the running water data to be checked as abnormal running water data; if the inspection sub-model comprises a vehicle information abnormity inspection sub-model, performing vehicle type verification, running time verification and designated vehicle verification on the running water data to be inspected through the vehicle information abnormity inspection sub-model, and if the running water data to be inspected does not pass the verification, determining the running water data to be inspected as abnormal running water data; and if the checking submodel comprises an fee evasion checking submodel, vehicle blacklist data is obtained, fee evasion checking is carried out on the running water data to be checked through the fee evasion checking submodel based on the vehicle blacklist data, and if the running water data to be checked does not pass the checking, the running water data to be checked is determined to be abnormal running water data.
In one embodiment, the audit module 304 is further configured to: if the running water data to be inspected does not meet the inspection conditions of the entrance and exit records, determining that the running water data to be inspected does not pass the entrance and exit record verification; the entrance and exit record inspection conditions comprise one or more of the following conditions: the method comprises the following steps that an entrance record corresponding to a normal exit record exists, an entrance record corresponding to an exit record of a specified portal exists, an exit record without a passing medium exists, data belonging to entrance override is stored, the entrance and exit time belongs to a specified time range, the number of seats of a vehicle is smaller than a specified number of seats, and the exit record corresponding to the entrance record exists in a first specified duration; and extracting first to-be-inspected running water data carrying no passing medium mark from the to-be-inspected running water data, and if the first to-be-inspected running water data does not belong to a first specified passing type, determining that the first to-be-inspected running water data does not pass the passing medium check; extracting second to-be-inspected flowing water data carrying a green-pass mark from the to-be-inspected flowing water data, and if the second to-be-inspected flowing water data does not meet green-pass inspection conditions, determining that the second to-be-inspected flowing water data does not pass green-pass inspection; the green inspection conditions comprise one or more of the following conditions: the system belongs to the flow data corresponding to the type of the appointed vehicle, the same-station payment record exists within a second appointed time, and the flow data corresponding to the identification of the appointed vehicle; and if the account clearing difference of the account clearing data in the running data to be checked is larger than a first specified value or smaller than a second specified value, determining that the running data to be checked does not pass the check of the account clearing amount.
In one embodiment, the audit module 304 is further configured to: extracting third to-be-inspected flowing water data which does not belong to a second specified passage type from the to-be-inspected flowing water data, and determining that the third to-be-inspected flowing water data does not pass outlet flowing water verification if an inlet vehicle type and an outlet vehicle type in the third to-be-inspected flowing water data are inconsistent or an inlet passage medium code and an outlet passage medium code in the third to-be-inspected flowing water data are inconsistent; and extracting the to-be-inspected flowing water data which does not carry the ETC identification or the open toll station identification from the to-be-inspected flowing water data, and removing the to-be-inspected flowing water data to obtain fourth to-be-inspected flowing water data, wherein if the inlet vehicle identification and the outlet vehicle identification in the fourth to-be-inspected flowing water data are inconsistent, the fourth to-be-inspected flowing water data is determined not to pass the vehicle identification verification.
In one embodiment, the audit module 304 is further configured to: if the inlet vehicle type or the outlet vehicle type in the running water data to be inspected is not consistent with the historical vehicle type, or the quantity of the historical vehicle types corresponding to the single vehicle identification is updated according to the running water data to be inspected, and if the quantity of the updated historical vehicle types is larger than the preset quantity, it is determined that the running water data to be inspected does not pass vehicle type verification; calculating the running time of the vehicle according to the running data to be inspected, and determining that the running data to be inspected does not pass the running time verification if the running time of the vehicle is greater than the preset fastest running time and the difference value between the running time of the vehicle and the preset fastest running time is greater than a first preset running time threshold value; or if the running time of the vehicle is less than the preset slowest time, and the difference value between the running time of the vehicle and the preset slowest time is greater than a second preset time-consuming threshold value, determining that the running data to be inspected does not pass the running time verification; and if the to-be-inspected flow data does not belong to a third appointed passage type, or the to-be-inspected flow data does not carry an emergency release mark, or no co-stop payment record exists in the to-be-inspected flow data within a third appointed time length, determining that the to-be-inspected flow data does not pass the appointed vehicle verification.
In one embodiment, the audit module 304 is further configured to: and if the vehicle identification in the running data to be inspected is positioned in the vehicle blacklist data, determining that the running data to be inspected does not pass fee evasion verification.
In one embodiment, the evidence chain generation module 306 is further configured to: sending the abnormal evidence chain to the appointed association terminal so as to feed back an audit result corresponding to the abnormal evidence chain through the appointed association terminal; and if the verification result is that the vehicle information passes the verification, generating additional payment push information based on the abnormal evidence chain, and sending the additional payment push information to an additional payment system so as to execute an intercepting operation on the target vehicle corresponding to each vehicle information through the additional payment system.
The device provided by the embodiment of the present invention has the same implementation principle and technical effect as the method embodiments, and for the sake of brief description, reference may be made to the corresponding contents in the method embodiments without reference to the device embodiments.
The embodiment of the invention provides a server, which particularly comprises a processor and a storage device; the storage means has stored thereon a computer program which, when executed by the processor, performs the method of any of the above described embodiments.
Fig. 4 is a schematic structural diagram of a server according to an embodiment of the present invention, where the server 100 includes: a processor 40, a memory 41, a bus 42 and a communication interface 43, wherein the processor 40, the communication interface 43 and the memory 41 are connected through the bus 42; the processor 40 is arranged to execute executable modules, such as computer programs, stored in the memory 41.
The Memory 41 may include a high-speed Random Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 43 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, etc. may be used.
The bus 42 may be an ISA bus, PCI bus, EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 4, but that does not indicate only one bus or one type of bus.
The memory 41 is used for storing a program, the processor 40 executes the program after receiving an execution instruction, and the method executed by the apparatus defined by the flow process disclosed in any of the foregoing embodiments of the present invention may be applied to the processor 40, or implemented by the processor 40.
The processor 40 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 40. The Processor 40 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory 41, and the processor 40 reads the information in the memory 41 and completes the steps of the method in combination with the hardware thereof.
The computer program product of the readable storage medium provided in the embodiment of the present invention includes a computer readable storage medium storing a program code, where instructions included in the program code may be used to execute the method described in the foregoing method embodiment, and specific implementation may refer to the foregoing method embodiment, which is not described herein again.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. An inspection method for highway flow data is characterized by comprising the following steps:
acquiring running water data to be inspected corresponding to a target highway;
determining abnormal running water data and vehicle information corresponding to each abnormal running water data from the running water data to be inspected through a pre-configured running water inspection model; the running inspection model comprises a plurality of inspection submodels;
and generating an abnormal evidence chain corresponding to each piece of vehicle information based on the abnormal running water data so as to execute intercepting operation on a target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain.
2. The method of claim 1, wherein determining abnormal flow data from the flow data to be audited through a pre-configured flow audit model comprises:
if the inspection submodel comprises a charging abnormity inspection submodel, performing access record verification, passing medium verification, green pass verification and clearing amount verification on the flowing water data to be inspected through the charging abnormity inspection submodel, and if the flowing water data to be inspected does not pass the verification, determining that the flowing water data to be inspected is abnormal flowing water data;
if the checking sub-model comprises a daily checking sub-model, performing export running water verification and vehicle identification verification on the running water data to be checked through the daily checking sub-model, and if the running water data to be checked does not pass the verification, determining that the running water data to be checked is abnormal running water data;
if the inspection submodel comprises a vehicle information abnormity inspection submodel, performing vehicle type verification, running time verification and designated vehicle verification on the running water data to be inspected through the vehicle information abnormity inspection submodel, and if the running water data to be inspected does not pass the verification, determining that the running water data to be inspected is abnormal running water data;
and if the checking submodel comprises an fee evasion checking submodel, vehicle blacklist data is obtained, fee evasion checking is carried out on the running water data to be checked through the fee evasion checking submodel based on the vehicle blacklist data, and if the running water data to be checked does not pass the checking, the running water data to be checked is determined to be abnormal running water data.
3. The method as claimed in claim 2, wherein the step of performing an entrance and exit record check, a traffic medium check, a green pass check and an inventory check on the running water data to be checked comprises:
if the to-be-inspected running water data does not meet the entrance and exit record inspection conditions, determining that the to-be-inspected running water data does not pass the entrance and exit record verification; wherein, the entrance and exit record inspection conditions comprise one or more of the following conditions: the method comprises the following steps that an entrance record corresponding to a normal exit record exists, an entrance record corresponding to an exit record of a specified portal exists, an exit record without a passing medium exists, the exit record belongs to entrance override data, the entrance and exit time belongs to a specified time range, the seat number of a vehicle is smaller than a specified seat number, and the exit record corresponding to the entrance record exists in a first specified duration;
extracting first to-be-inspected flow data carrying no passing medium mark from the to-be-inspected flow data, and determining that the first to-be-inspected flow data does not pass the passing medium check if the first to-be-inspected flow data does not belong to a first specified passing type;
and extracting second to-be-inspected flowing water data carrying a green pass flag from the to-be-inspected flowing water data, and if the second to-be-inspected flowing water data does not meet green pass inspection conditions, determining that the second to-be-inspected flowing water data does not pass the green pass inspection; wherein the green inspection conditions comprise one or more of the following: the system belongs to the flow data corresponding to the type of the appointed vehicle, the same-station payment record exists within a second appointed time, and the flow data corresponding to the identification of the appointed vehicle;
and if the accounting balance of the accounting data in the to-be-inspected flowing water data is larger than a first specified value or smaller than a second specified value, determining that the to-be-inspected flowing water data does not pass the accounting amount verification.
4. The method of claim 2, wherein the step of performing export pipeline verification and vehicle identification verification on the pipeline data to be audited comprises:
extracting third to-be-inspected flowing water data which does not belong to a second specified passage type from the to-be-inspected flowing water data, and if the inlet vehicle type and the outlet vehicle type in the third to-be-inspected flowing water data are inconsistent or the inlet passage medium code and the outlet passage medium code in the third to-be-inspected flowing water data are inconsistent, determining that the third to-be-inspected flowing water data do not pass the outlet flowing water verification;
and extracting the to-be-inspected flowing water data which does not carry the ETC identification or the open toll station identification from the to-be-inspected flowing water data, and removing the to-be-inspected flowing water data to obtain fourth to-be-inspected flowing water data, wherein if the inlet vehicle identification and the outlet vehicle identification in the fourth to-be-inspected flowing water data are inconsistent, the fourth to-be-inspected flowing water data is determined not to pass the vehicle identification verification.
5. The method as claimed in claim 2, wherein the step of performing vehicle type verification, running time verification and designated vehicle verification on the running water data to be inspected comprises the following steps:
if the inlet vehicle type or the outlet vehicle type in the running water data to be inspected is not consistent with the historical vehicle type, or the quantity of the historical vehicle types corresponding to the single vehicle identification is updated according to the running water data to be inspected, and if the quantity of the updated historical vehicle types is larger than the preset quantity, the running water data to be inspected is determined not to pass the vehicle type verification;
calculating running time of a vehicle according to the running data to be inspected, and if the running time of the vehicle is greater than a preset fastest time, and the difference value between the running time of the vehicle and the preset fastest time is greater than a first preset time threshold, determining that the running time of the running data to be inspected does not pass the running time verification; or if the vehicle running time is less than the preset slowest time, and the difference value between the vehicle running time and the preset slowest time is greater than a second preset time threshold value, determining that the running water data to be inspected does not pass the running time verification;
and if the to-be-inspected running water data does not belong to a third appointed passing type, or the to-be-inspected running water data does not carry an emergency release mark, or no co-stop payment record exists in the to-be-inspected running water data within a third appointed time length, determining that the to-be-inspected running water data does not pass the appointed vehicle verification.
6. The method of claim 2, wherein the step of fee evasion checking the running water data to be audited based on the vehicle blacklist data comprises:
and if the vehicle identification in the running water data to be inspected is located in the vehicle blacklist data, determining that the running water data to be inspected does not pass the fee evasion check.
7. The method according to claim 1, wherein the step of performing an intercepting operation on the target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain comprises:
sending the abnormal evidence chain to a designated association terminal so as to feed back an audit result corresponding to the abnormal evidence chain through the designated association terminal;
and if the verification result is that the vehicle information passes verification, generating additional payment push information based on the abnormal evidence chain, and sending the additional payment push information to an additional payment system so as to execute intercepting operation on the target vehicle corresponding to each piece of vehicle information through the additional payment system.
8. An inspection device for highway flow data is characterized by comprising:
the data acquisition module is used for acquiring the running water data to be inspected corresponding to the target highway;
the inspection module is used for determining abnormal running water data and vehicle information corresponding to each abnormal running water data from the running water data to be inspected through a pre-configured running water inspection model; the running water inspection model comprises a plurality of inspection sub-models;
and the evidence chain generating module is used for generating an abnormal evidence chain corresponding to each piece of vehicle information based on the abnormal running data so as to execute intercepting operation on the target vehicle corresponding to each piece of vehicle information according to the abnormal evidence chain.
9. A server comprising a processor and a memory, the memory storing computer-executable instructions executable by the processor, the processor executing the computer-executable instructions to implement the method of any one of claims 1 to 7.
10. A computer-readable storage medium having computer-executable instructions stored thereon which, when invoked and executed by a processor, cause the processor to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310015432.9A CN115934773A (en) | 2023-01-06 | 2023-01-06 | Method and device for checking flow data of highway, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310015432.9A CN115934773A (en) | 2023-01-06 | 2023-01-06 | Method and device for checking flow data of highway, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115934773A true CN115934773A (en) | 2023-04-07 |
Family
ID=86554174
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310015432.9A Pending CN115934773A (en) | 2023-01-06 | 2023-01-06 | Method and device for checking flow data of highway, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115934773A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117370773A (en) * | 2023-10-24 | 2024-01-09 | 广东省交通运输规划研究中心 | Checking method, system, equipment and medium for J-type running fee evasion vehicle |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110956812A (en) * | 2019-11-05 | 2020-04-03 | 南京感动科技有限公司 | Highway inspection data cloud rapid analysis processing method |
| CN111341113A (en) * | 2019-11-05 | 2020-06-26 | 南京感动科技有限公司 | Highway inspection data management analysis system |
| CN111932897A (en) * | 2020-09-23 | 2020-11-13 | 南京感动科技有限公司 | Method for fast iteration of highway toll inspection |
| CN113838221A (en) * | 2021-09-22 | 2021-12-24 | 招商华软信息有限公司 | Fee chasing method and device, storage medium and computer equipment |
| JP2022020970A (en) * | 2020-07-21 | 2022-02-02 | 株式会社東芝 | Toll management system, toll management device, program, and toll management method |
-
2023
- 2023-01-06 CN CN202310015432.9A patent/CN115934773A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110956812A (en) * | 2019-11-05 | 2020-04-03 | 南京感动科技有限公司 | Highway inspection data cloud rapid analysis processing method |
| CN111341113A (en) * | 2019-11-05 | 2020-06-26 | 南京感动科技有限公司 | Highway inspection data management analysis system |
| JP2022020970A (en) * | 2020-07-21 | 2022-02-02 | 株式会社東芝 | Toll management system, toll management device, program, and toll management method |
| CN111932897A (en) * | 2020-09-23 | 2020-11-13 | 南京感动科技有限公司 | Method for fast iteration of highway toll inspection |
| CN113838221A (en) * | 2021-09-22 | 2021-12-24 | 招商华软信息有限公司 | Fee chasing method and device, storage medium and computer equipment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117370773A (en) * | 2023-10-24 | 2024-01-09 | 广东省交通运输规划研究中心 | Checking method, system, equipment and medium for J-type running fee evasion vehicle |
| CN117370773B (en) * | 2023-10-24 | 2024-05-14 | 广东省交通运输规划研究中心 | Checking method, system, equipment and medium for J-type running fee evasion vehicle |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112581642B (en) | Method for checking fee stealing and escaping vehicles based on highway portal charging data | |
| CN109615853B (en) | Method and device for identifying suspected illegal operating vehicles on expressway | |
| CN105448103A (en) | Vehicle fake license plate detection method and system | |
| CN106846153A (en) | A kind of vehicle insurance compensates method and system | |
| CN112802215A (en) | Method, device, equipment and storage medium for auditing highway passing fees | |
| CN115934773A (en) | Method and device for checking flow data of highway, server and storage medium | |
| CN112711619B (en) | Road fee evasion checking platform based on Beidou positioning | |
| CN110728759B (en) | ETC portal transaction success rate detection method and device, computing equipment and medium | |
| CN116229594A (en) | Vehicle charge monitoring method, device and medium based on expressway | |
| CN113569899A (en) | Intelligent classification method for fee stealing and evading behaviors, storage medium and terminal | |
| CN112183343A (en) | Highway toll balance analysis system, method and analysis system platform | |
| CN108021361A (en) | A kind of the highway fee evasion of falling card vehicle screening method and device | |
| CN116935659B (en) | High-speed service area bayonet vehicle auditing system and method thereof | |
| CN113626656A (en) | Method, device, equipment and storage medium for identifying relation type of enterprise and vehicle | |
| CN110689370B (en) | Classification model training method, device and equipment | |
| CN110727707A (en) | Processing method, medium, equipment and system for operation log of toll collector in parking lot | |
| CN111882686A (en) | ETC portal system-based checking method, system and equipment for toll collection vehicle | |
| CN117854016A (en) | Method and device for detecting abnormal vehicle based on expressway | |
| CN115311750B (en) | ETC portal operation quality monitoring method and device | |
| CN114416686B (en) | Vehicle equipment fingerprint CARID identification system and identification method | |
| CN114780591B (en) | Calculation method and system for detecting travel license plate recognition errors | |
| CN110428156A (en) | Method, apparatus and electronic equipment for business datum verification | |
| CN116188224A (en) | Vehicle fee evasion analysis method and system based on blockchain | |
| CN113838221B (en) | Fee-pursuing method, device, storage medium and computer equipment | |
| CN111369804B (en) | Vehicle data processing method and device, electronic equipment and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20230407 |
|
| RJ01 | Rejection of invention patent application after publication |