Vehicle Rule SYSTEM INTRODUCTION

Vehicle Rule SYSTEM INTRODUCTION

 

I. Overview

The driving rule, that is, the driving specification, is a kind of driving specification for vehicles and drivers. The driving rule is divided into two modules: Rules and subsequent handling. Subsequent handling is the prompt, handling, and operation after violation of the rules.

The rules include non-work-time vehicle alert, regional alert, regional alert, route alert, speeding alert, key-point alert, off-site alert, and illegal picking alert. For subsequent processing, you can take a photo (the camera number is optional) and send the information.

For example, if a rule is set to "overspeed alarm: The maximum speed is 100" and "Photo: Camera 1" is subsequently processed, when the vehicle travel speed exceeds 100 km/h, the background will analyze the vehicle overspeed, generate the overspeed alarm, send the alarm information to the monitoring client in real time, generate the overspeed alarm report, and send a photo command to the terminal camera 1.

 

II. Introduction to rules

This section describes the principles and implementation of various rules. The subsequent processing involves sending text messages and issuing photo commands. We will not introduce them any more. The following describes only the rules.

2.1 Non-working hours vehicle use alarm

If a vehicle is not used within a valid period of time, the vehicle is regarded as a non-working time vehicle. If the vehicle is in use, the vehicle is determined based on the speed and on/off status. The valid time is set on the setting interface, it can be set by day, week, month, or specific time.

 

2.2 cross-border alarm

The "border" refers to the area, multi-border area. When n (n> 2) points are connected in order, a polygon area is formed. on the map of the Set interface, any point is circled manually. An out-of-boundary alarm is then triggered when the vehicle enters the area and an out-of-boundary alarm is triggered. If the vehicle is not in the area, an out-of-boundary alarm is triggered when the vehicle is not in the area, it is determined by the longitude and latitude of the vehicle uploaded in real time, combined with the N points that constitute the region (in fact, the points are also a pair of latitude and longitude.

 

2.3 regional speeding

The concept of a region is the same as that of area 2.2. When a region is configured with a speed, the vehicle is driving in a specified area and the driving speed exceeds the specified speed, the system generates a regional speeding alarm.

 

2.4 route Deviation

The line is interpreted as a curve in which n (n> 1) points are connected sequentially. These points can be obtained by manually labeling on the map on the rule setting interface, you can also extract the driving track of a vehicle to determine whether the vehicle is on the specified route. You can use the real-time longitude and latitude uploaded by the vehicle to determine whether the vehicle is on the specified route, if the distance of the vehicle's offline route exceeds the specified value, it is deemed that the vehicle is not on the specified route and an alarm is triggered for line deviation.

 

2.5 route speeding

Route overspeed is divided into two situations: Custom route and default route. Custom route is obtained by the method in 2.4, the default route refers to the actual routes on the map, such as "Guangdong-Guangdong expressway ".

For a custom route, set a speed threshold. First, use the method in 2.6 to determine whether the vehicle is on the specified line. If yes, then compare it with the set speed, determines whether the current speed of the vehicle has exceeded the set threshold value. If yes, a route overspeed alarm is triggered.

For the default route, the longitude and latitude data uploaded by the vehicle in real time matches the map data to determine the current attributes of the vehicle on the road, whether it is on the expressway, National Highway, provincial road or normal road, then, you can set a speed threshold value for each type of link to compare the current speed of the vehicle with the corresponding threshold value to determine whether the vehicle is speeding.

 

2.6 out-of-site timeout

"Station" is the region in "2.2". The acquisition method is also the same as that in "2.2". First, you can use the real-time longitude and latitude of the vehicle to determine whether the vehicle is in the "station". If not, start timing (the vehicle returns to the station to stop). If the time exceeds the set time threshold and the vehicle has not returned to the station, an off-site timeout alarm is generated.

 

2.7 off-site parking timeout alarm

The concept of "station" is the same as that of "2.6". The same method is used to determine the departure. If a vehicle leaves the station and stops at the same time (the parking speed is determined based on the speed less than 5 km/h ), start timing (the vehicle is not stopped or is returned to the station to stop timing). If the time exceeds the set time threshold, and the vehicle has not returned to the station, generates an off-site parking timeout alarm.

 

2.8 key points

The "Key Points" are the same as the "station" concept in section 2.6. Based on the Real-Time longitude and latitude of the vehicle uploaded, combined with the "station" analysis, if the vehicle enters the station, a record is generated and the inbound record is recorded, when a vehicle leaves the station, record the departure record.

 

2.9 alarm on illegal discharge of concrete vehicles

The basis for determining whether a vehicle is out of stock illegally is: whether to exit at the specified location. The station in the specified map and 2.6 is a concept. Through map setting, the status analysis of whether the vehicle is out of stock is uploaded in real time. An alarm is triggered if the data is not delivered at the specified location.

Iii. Architecture Description

The driving rule software runs on the backend server and analyzes the status information (such as speed, positioning point, and flameout status) uploaded by the terminal in real time based on the driving rules to determine whether the terminal is in violation, and make corresponding processing. Real-time terminal data comes from the gateway or internal software, and the vehicle rule information comes from the database, local database or remote database.

The rule data in the database is added, deleted, modified, and queried through the BS rule setting interface.