Vehicle operation and maintenance management system and method

Abstract

The invention relates to the technical field of vehicle management, and discloses a vehicle operation and maintenance management system and method, and the system comprises an infrastructure layer which is used for detecting parking space occupation and recognizing the identity of a vehicle, a vehicle-mounted terminal layer which is provided with a vehicle-mounted terminal and obtains the precise instrument display mileage through a vehicle bus interface, and a software platform layer which is used for carrying out the operation and maintenance of the vehicle. The software platform layer receives the vehicle identity, compares the vehicle identity with a preset parking space binding relationship, and realizes real-time early warning of the traveled distance abnormity by comparing the actual traveled distance reported by the vehicle-mounted terminal with the reference mileage planned by the system; and dual condition verification of team registration is executed by combining a team request initiated by a driver at a mobile terminal and physical in-place information reported by a parking space alarm device, so that a management closed loop is formed. According to the invention, the problems of lack of monitoring means, disordered parking and inaccurate cost accounting in traditional management are solved, and full-cycle automatic and precise closed-loop supervision of vehicles is realized.

Description

Technical Field

[0001] This invention relates to the field of vehicle management technology, specifically to a vehicle operation and maintenance management system and method. Background Technology

[0002] With the development of the social economy, the number of vehicles owned by various enterprises and institutions is expanding daily. These vehicles, as important production and operational assets, play a vital role in daily patrols, official travel, and emergency repairs. Therefore, efficient and standardized management of these vehicles is crucial for ensuring asset safety, improving operational efficiency, and controlling operating costs. Traditional vehicle management models rely heavily on manual registration, paper dispatch slips, and the experience of dispatchers, resulting in generally low levels of information technology and relatively simplistic management methods.

[0003] However, existing technologies are insufficient for the refined management of vehicles. In the parking management stage, vehicles are often parked haphazardly in parking lots, occupying key passages or emergency parking spaces, resulting in low outbound efficiency, delayed task response time, and making vehicle inventory and status confirmation cumbersome and prone to errors. In the on-the-go usage stage, there is a lack of technical means to accurately monitor the actual driving routes and mileage of vehicles, providing opportunities for misuse of official vehicles and false mileage reporting. This not only directly leads to an abnormal increase in operating costs such as fuel and maintenance, but also makes it difficult for managers to effectively audit the compliance of vehicle use.

[0004] Therefore, a solution is needed that deeply integrates the physical status of vehicles with the digital management of an information platform. This solution must achieve fully automated closed-loop management of the entire process, from vehicle parking and driving monitoring to return confirmation, and on this basis, perform accurate cost collection and data analysis, thereby comprehensively improving the efficiency and level of vehicle operation and maintenance management. To this end, this invention proposes a vehicle operation and maintenance management system and method to address the shortcomings of existing technologies. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention provides a vehicle operation and maintenance management system and method. This system solves the problem that in vehicle parking management, haphazard parking often leads to low outbound efficiency and delayed task response times. Furthermore, the lack of precise mileage monitoring technology during vehicle use creates management loopholes for misuse of company vehicles and falsified mileage, resulting not only in abnormally increased operating costs but also making it difficult for managers to effectively audit the compliance of vehicle use.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a vehicle operation and maintenance management system, comprising: The software platform layer includes a data processing module, which performs management, monitoring, and analysis functions according to preset logic, and generates the alarm trigger command and the early warning command. An infrastructure layer, deployed in the vehicle parking area, includes multiple parking space alarm devices. Each parking space alarm device is configured in a fixed parking space to detect the vehicle identity information and the parking space information of the parked vehicle, and sends the vehicle identity information and parking space information to the software platform layer, and receives alarm triggering instructions from the software platform layer to execute the alarm. The vehicle-mounted terminal layer, installed inside the controlled vehicle, includes a positioning unit, a data communication unit, and a driver warning device. It is used to collect and report the real-time geographical coordinates and actual mileage of the vehicle, and to receive warning instructions from the software platform layer to drive the driver warning device to work.

[0007] A second aspect of the present invention provides a vehicle operation and maintenance management method, comprising the following steps: S1. Collect and report vehicle dynamic data through the vehicle terminal layer, including the vehicle's real-time geographical location and the mileage displayed on the instrument panel obtained through the vehicle bus interface; S2. Through the infrastructure layer, detect and report vehicle parking status data, including parking space occupancy status and the unique electronic identity information of parked vehicles; S3. Receive and process the dynamic data and parking status data through the software platform layer, and perform parking location verification, driving process monitoring, and return registration management.

[0008] The method further includes a parking location verification step: after receiving the vehicle's electronic identity information reported by the parking space alarm device, the software platform layer queries the preset vehicle identity information bound to the parking space in the system for comparison; if the two are inconsistent, it is determined to be an incorrect parking and a command is sent to the parking space alarm device to trigger an alarm.

[0009] The method further includes a return-to-base registration step: after receiving a return-to-base request initiated by the driver, the software platform layer further verifies whether the vehicle associated with the task has been parked in its designated parking space; the return-to-base registration is only completed when both conditions are met: the request has been received and the vehicle is in the correct location.

[0010] The method further includes a driving process monitoring step: the software platform layer obtains the planned reference mileage for the vehicle dispatch task and continuously receives the actual mileage of the vehicle reported by the vehicle terminal layer; when the actual mileage exceeds the sum of the planned reference mileage and the preset deviation threshold, an instruction is sent to the vehicle terminal layer to drive the driver warning device to work.

[0011] This invention provides a vehicle operation and maintenance management system and method. It has the following beneficial effects: 1. This invention utilizes a parking alarm device that integrates a geomagnetic sensor and a radio frequency identification reader in a fixed parking space. Combined with the vehicle-parking space binding relationship preset in the software platform, it achieves automatic identification and compliance verification of parked vehicles. When a vehicle is misplaced and not parked in the designated location, the system can automatically trigger a physical alarm, thereby standardizing parking order, ensuring that high-priority vehicles such as those for emergency repairs are parked in the most convenient location, and reducing the cost of manual inspection and management.

[0012] 2. This invention obtains tamper-proof mileage data from the vehicle's controller LAN bus directly through the vehicle bus interface of the vehicle terminal. The mileage data provides a reliable basis for comparing the actual mileage with the planned reference mileage, preventing detours under the pretext of traffic congestion or misuse of public vehicles. Based on this accurate mileage, combined with the collection of fuel, maintenance and other costs, the cost accounting of a single vehicle becomes more accurate, providing solid data support for enterprises to save energy and increase efficiency.

[0013] 3. The dual-condition verification mechanism for returning to the parking space proposed in this invention binds and verifies the driver's active operation on the mobile phone with the physical presence information reported by the parking space alarm device. Only when both conditions of the driver's confirmation and the vehicle's presence are met simultaneously can the task process be closed in the system, ensuring the consistency between the system state and physical reality, avoiding human negligence or false registration, realizing automated and unmanned supervision of the entire process from vehicle dispatch to return to the parking space, and providing reliable triggering conditions for subsequent linkage operations such as triggering automatic sunshades. Attached Figure Description

[0014] Figure 1 This is a structural block diagram of the vehicle operation and maintenance management system of the present invention; Figure 2 This is a schematic diagram of the parking lot zoning and fixed parking space layout of the present invention; Figure 3 This is a schematic diagram of the parking space alarm device of the present invention; Figure 4 This is a schematic diagram of the structure of the fully automatic sunshade of the present invention; Figure 5 This is a structural block diagram of the vehicle-mounted terminal of the present invention; Figure 6 This is a flowchart of the vehicle application and dispatch process in the vehicle management method of the present invention; Figure 7 This is a flowchart of the driving process monitoring and abnormal early warning process in the vehicle management method of the present invention; Figure 8 This is a flowchart of the parking location verification and alarm triggering process in the vehicle management method of the present invention; Figure 9 This is a flowchart of the vehicle management method of the present invention, which includes the registration and linkage operation process for returning to the vehicle. Figure 10 This is a flowchart of the automatic collection and calculation of back-end costs in the vehicle management method of the present invention. Detailed Implementation

[0015] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0016] See attached document Figure 1 The present invention provides a vehicle operation and maintenance management system, which includes an infrastructure layer, an in-vehicle terminal layer and a software platform layer.

[0017] The infrastructure layer, deployed in the vehicle parking area, provides physical parking management and environmental support. The vehicle terminal layer, installed inside the controlled vehicle, collects and reports dynamic vehicle data. The software platform layer receives and processes data from the infrastructure layer and the vehicle terminal layer, and performs management, monitoring, and analysis functions according to preset logic.

[0018] Specifically, the infrastructure layer includes multiple fixed parking spaces set up in the parking lot. Each fixed parking space is equipped with a parking space alarm device. Some designated areas of fixed parking spaces are also equipped with fully automatic sunshades. The parking space alarm device is used to detect whether a vehicle is in a designated parking space and to send an alarm signal when the vehicle is detected to be parked in a position that does not conform to the preset rules. The fully automatic sunshade is used to receive control instructions from the software platform layer to automatically unfold or retract.

[0019] The vehicle terminal layer includes a positioning unit, a data communication unit, and a driver warning device. The positioning unit is used to obtain the real-time geographical coordinates of the vehicle. The data communication unit is used to send the location coordinates obtained by the positioning unit and other vehicle status information to the software platform layer and receive instructions issued by the software platform layer. The driver warning device is connected to the data communication unit and is used to output warning information to the driver according to the received instructions.

[0020] The software platform layer includes a data processing module, a PC client, and a mobile client. The PC client and mobile client serve as human-computer interaction interfaces for data input, display, and the issuance of operation commands. The data processing module connects to the PC client and mobile client and interacts with the data communication unit to perform data analysis, logical judgment, and command generation.

[0021] During system operation, the data communication unit of the vehicle terminal layer sends real-time vehicle data to the software platform layer, and the parking space alarm device sends the vehicle parking status data to the software platform layer. The data processing module of the software platform layer processes and analyzes the received data and displays it through PC and mobile terminals. When preset conditions are met, the data processing module generates control commands and sends them to the driver warning device of the vehicle terminal layer and the fully automatic sunshade of the infrastructure layer to execute the corresponding physical operations.

[0022] The data processing module is configured to perform specific logical operations to achieve monitoring functions.

[0023] For example, the data processing module determines abnormal vehicle mileage by first calculating the mileage deviation: ; in, This represents the vehicle's actual mileage. This represents a reference mileage for system planning.

[0024] Subsequently, the mileage deviation was used to determine the mileage anomaly status. : ; in, It is a preset mileage deviation threshold, when At that time, the data processing module generates a command to trigger the driver's warning device.

[0025] The data processing module determines whether the vehicle is parked correctly using the following methods, and verifies the parking position status. The determination criteria are: ; in, It specifies the center geographic coordinates of the parking space. These are the actual geographical coordinates of the vehicle's center where it is parked. It is the preset maximum parking position tolerance, when At that time, the data processing module generates a command to trigger the parking space alarm device.

[0026] The data processing module is also used to automatically calculate the total operating cost of the vehicle. : ; in, This is the total cost of maintenance and repair. This represents the total fuel cost for the vehicle. The total amount of insurance premiums, The total cost of car accessories. The total parking fee. This is the total amount of other expenses.

[0027] The data processing module also identifies abnormal fuel consumption per 100 kilometers by first calculating the fuel consumption per 100 kilometers over a specified period. : ; in, It is the volume of fuel consumed within the cycle. It is the total mileage driven within the period.

[0028] Subsequently, the abnormal fuel consumption status was determined based on the calculated fuel consumption. : ; in, This is the vehicle's historical average fuel consumption per 100 kilometers. This is a preset fuel consumption fluctuation threshold. When At that time, the data processing module generates an early warning message.

[0029] See attached document Figure 2 In an embodiment of the present invention, the infrastructure layer includes a parking lot with physical functional zones. The physical functional zones are implemented by marking different colors or styles of lines on the ground, and area signs are set at the entrance or prominent location of each area, such as signs for emergency repair vehicles, routine patrol vehicles, official vehicles, and special vehicles.

[0030] The specific layout of the physical functional zones is configured according to the usage characteristics of the vehicles. In one specific implementation, the emergency repair vehicle area is located closest to the parking lot exit to ensure that vehicles have the shortest exit route when performing emergency tasks, thereby shortening the task response time. The daily patrol vehicle area and the official vehicle area can be arranged in a secondary layout according to the dispatch frequency, while the special vehicle area can be set up in a relatively independent area to facilitate special operations or maintenance.

[0031] Within each designated area, there are multiple fixed parking spaces. Each fixed parking space is clearly marked by ground lines and has a unique parking space number in a prominent position on the ground. The parking space number uses a structured coding system, such as "QX-01" or "RC-01". The prefix letter represents the area to which it belongs ("QX" represents emergency repair and "RC" represents routine repair), and the suffix number is the serial number within that area.

[0032] Accordingly, each vehicle included in the system is assigned a unique vehicle number. The vehicle number is not only recorded as a data entity in the vehicle ledger at the software platform layer, but can also be materialized as a physical identifier, such as an RFID tag or a numbered sign attached to the vehicle body.

[0033] Within the resource management module of the software platform layer, a vehicle-parking space mapping data structure is established and stored, such as a database table or lookup table. The data structure binds the unique vehicle number of each vehicle to the unique parking space number of a fixed parking space. This binding relationship provides basic data support for the system to perform parking location verification and vehicle positioning in the future. When the system needs to verify whether a vehicle is correctly parked, it obtains the target parking location information of the vehicle by querying this mapping data structure and compares it with the actual location information reported by the vehicle terminal layer.

[0034] See attached document Figure 3 The parking space alarm device is installed in a designated fixed parking space. In one embodiment, the main body of the parking space alarm device can be encapsulated in a waterproof and pressure-resistant shell and pre-embedded in the center of the parking space ground, or installed on a fixed post at the front or rear of the parking space.

[0035] The parking space alarm device includes a vehicle detection unit, a microcontroller, a communication unit, and an alarm execution unit.

[0036] The vehicle detection unit is used to acquire physical information about parked vehicles. In one specific embodiment, the vehicle detection unit consists of a geomagnetic sensor and a radio frequency identification (RFID) reader. The geomagnetic sensor is used to detect changes in the local geomagnetic field caused by the vehicle's metal chassis and to determine whether a vehicle is in the parking space based on these changes, i.e., to determine the occupancy status of the parking space. The RFID reader is used to read the unique electronic identification information inside the RFID tag affixed to a designated location on the vehicle (e.g., on the windshield or license plate). Through this combination, the vehicle detection unit can not only determine whether the parking space is occupied, but also identify the specific identity of the occupied vehicle.

[0037] The microcontroller is electrically connected to the vehicle detection unit, communication unit, and alarm execution unit. It is responsible for processing raw signals from the vehicle detection unit, such as converting changes in the geomagnetic field into a binary status signal representing occupancy or vacancy, and parsing the vehicle electronic identification information obtained by the RFID reader.

[0038] The communication unit is used to establish a data link between the microcontroller and the software platform layer. In one embodiment, the communication unit can be a low-power wide-area network (LPWAN) module, such as LoRa (long-range radio) or NB-IoT (narrowband Internet of Things) module. The microcontroller periodically or when the state of the vehicle detection unit changes, sends data packets containing parking space occupancy status and vehicle identity information to the software platform layer through the communication unit. At the same time, the communication unit also receives control commands from the software platform layer.

[0039] The alarm execution unit is used to output physical alarm signals to the outside. In one embodiment, the unit includes a high-decibel buzzer and a high-brightness light-emitting diode (LED). When the microcontroller receives an alarm trigger command from the software platform layer, it drives the buzzer to emit a continuous or intermittent sound and drives the LED to emit a high-frequency flashing red light.

[0040] When a vehicle enters a parking space during operation, the vehicle detection unit of the parking space alarm device is triggered and reports the detected parking space occupancy status and vehicle identity information through the communication unit. After receiving this information, the data processing module of the software platform layer queries the preset vehicle and parking space mapping data structure to verify whether the identity of the currently parked vehicle is consistent with the identity of the vehicle bound to the parking space. If they are inconsistent, the data processing module determines it as an incorrect parking behavior and immediately sends an alarm trigger command to the communication unit of the parking space alarm device through the data link, thereby activating the alarm execution unit.

[0041] See attached document Figure 4 Fully automatic sunshades are installed above fixed parking spaces in specific areas (e.g., emergency repair vehicle areas). Their structure is fixed to the ground or an adjacent building structure to provide physical shelter for parked vehicles.

[0042] The automatic sunshade consists of a control unit, a drive unit, and a mechanical structure. The control unit interacts with the drive unit and the software platform layer via signals, and the drive unit is mechanically coupled to the mechanical structure.

[0043] The control unit includes a wireless communication module and a microcontroller. The wireless communication module is used to receive unfold or retract control commands sent by the software platform layer. The microcontroller is connected to the wireless communication module and is used to parse the received control commands and generate corresponding control signals to send to the drive unit.

[0044] The drive unit includes a reversible electric motor and a motor drive circuit. The motor drive circuit is electrically connected to the microcontroller of the control unit, and is used to receive control signals from the microcontroller and control the forward, reverse, or stop rotation of the motor accordingly, thereby providing a power source for the movement of the mechanical structure.

[0045] The mechanical structure includes a retractable support frame, a sunshade awning covering the support frame, an unfolding limit switch, and a retracting limit switch. The input end of the support frame is connected to the output shaft of the motor of the drive unit. The sunshade awning is made of a material with waterproof and UV-resistant properties. The unfolding limit switch and the retracting limit switch are respectively installed at the two extreme positions of the support frame's movement stroke, and their status signals are fed back to the microcontroller of the control unit.

[0046] The workflow of the fully automatic sunshade is as follows: When the software platform layer confirms that the designated vehicle has completed the registration process and the parking space alarm device of the corresponding parking space reports that the vehicle is parked correctly, the data processing module of the software platform layer generates and sends an unfolding command.

[0047] After receiving the deployment command, the control unit's wireless communication module sends a drive signal to the drive unit, causing the motor to rotate forward and drive the mechanical support frame to begin deployment. When the support frame reaches the fully deployed position, it triggers the deployment limit switch. The deployment limit switch sends a status change signal to the microcontroller. Upon receiving the status change signal, the microcontroller immediately controls the drive unit to stop the motor, completing the awning deployment. The retraction process is similar, triggered by a retraction command and terminated by a retraction limit switch.

[0048] See attached document Figure 5 The vehicle terminal layer is an integrated and packaged electronic device installed in a concealed location inside the vehicle, such as under the dashboard or inside the glove box. The vehicle terminal layer is connected to the vehicle's constant power supply or the ACC power supply (auxiliary power supply controlled by the ignition switch) controlled by the key via a dedicated wiring harness to obtain continuous and stable working power. Functionally, it includes a positioning unit, a data communication unit, a driver warning device, a vehicle main control unit, and a vehicle bus interface.

[0049] The vehicle-mounted main control unit, with a microprocessor at its core, serves as the data processing and control center of the vehicle terminal. It is electrically connected to the positioning unit, data communication unit, driver warning device, and vehicle bus interface, and is responsible for scheduling and managing the operation of the entire terminal. The vehicle-mounted main control unit receives and processes data from the positioning unit and vehicle bus interface, packages the data according to a preset data format, controls the data communication unit to send and receive data, and parses instructions from the software platform layer to drive the driver warning device.

[0050] The positioning unit is a multi-mode satellite positioning receiver module, which integrates a chip capable of simultaneously receiving and parsing signals from multiple Global Navigation Satellite Systems (GNSS). GNSS systems include, but are not limited to, the US Global Positioning System (GPS), China's BeiDou Navigation Satellite System (BDS), and Russia's GLONASS system. The positioning unit is configured to periodically calculate the current longitude, latitude, altitude, speed, and timing information of the vehicle and output it to the vehicle's main control unit in a standard data frame format (e.g., NMEA-0183 format).

[0051] The data communication unit is a cellular network communication module that supports 4G LTE or higher network standards. It integrates a SIM card slot or has an eSIM chip soldered on inside for accessing public mobile communication networks. Under the control of the vehicle main control unit, the data communication unit is responsible for uploading the packaged vehicle data to the server address specified by the software platform layer via TCP / IP or UDP protocol, and receiving control commands or data issued by the software platform layer.

[0052] The vehicle bus interface is a Controller Area Network (CAN) bus transceiver that connects directly to the vehicle's CAN-High and CAN-Low buses via physical lines. It is typically accessed through the vehicle's diagnostic interface (OBD-II), which is configured to listen for and decode data packets on the vehicle's internal network. From these packets, it reads low-level status data such as the vehicle's instrument display mileage, engine speed, real-time vehicle speed, and fuel tank level, and provides this data to the vehicle's main control unit.

[0053] The driver warning device is an electroacoustic or optoelectronic device. In one embodiment, it is a piezoelectric buzzer that outputs a pulse width modulation (PWM) signal with a specific frequency and duty cycle to the buzzer when the vehicle main control unit interprets a warning command from the software platform layer (e.g., triggered by mileage anomaly judgment logic). This drives the buzzer to emit a sound with a specified tone and pattern (e.g., a short alert tone or a long and rapid alarm tone) to convey a warning message to the driver.

[0054] In the software platform layer, the PC client is physically implemented as a web application accessed through a web browser. Its user interface and front-end logic run on the user's computer, while the back-end logic is executed by the data processing module deployed on the server. The PC client serves as the main management and monitoring entry point for the system, targeting vehicle management personnel, dispatchers, and financial personnel within the organization. Specifically, the PC client is functionally divided into multiple modules, including a resource management module, a vehicle management module, an operation management module, a cost management module, an early warning management module, and a statistical analysis module.

[0055] The resource management module is used to create, query, update, and delete basic static data of the system. This module is further divided into vehicle ledger management, driver ledger management, driver overtime record management, service provider ledger management, and service provider evaluation management. Vehicle ledger management provides a structured data entry interface for recording the fixed attributes of each vehicle. Attribute fields include, but are not limited to: vehicle license plate number, vehicle identification number (VIN), engine number, purchase date, vehicle type, and the associated fixed parking space number. Driver ledger management also provides a structured interface for recording driver information, with fields including: name, driver's license number, permitted vehicle type, initial driver's license issuance date, and annual inspection date.

[0056] The vehicle management module is used to manage the entire lifecycle of a vehicle from its entry into the unit to its final disposal in a process-oriented manner. The vehicle management module includes four sub-functions: purchase management, vehicle inspection management, disposal management, and scrapping management. The purchase management function is used to add a vehicle to the system, and its operation will insert a new record into the vehicle ledger of the resource management module. The scrapping management function is used to change the in-use status of a specified vehicle to scrapped and remove its binding relationship with a fixed parking space. After that, the vehicle will no longer appear in the dispatch list.

[0057] The Operations Management module handles the daily dispatching and usage of vehicles. It includes four core functional interfaces: vehicle application, vehicle dispatch, dispatch order, and return registration. The vehicle dispatch interface displays a list of all approved vehicle applications to the dispatcher, along with a map or list showing all currently available vehicles and their locations. After the dispatcher selects a vehicle application and an available vehicle, the system generates a unique electronic dispatch order record. This record is linked to the task, vehicle, driver, and estimated trip information. The return registration interface is used by drivers or administrators to mark the dispatch order as completed after the task, triggering subsequent cost accounting and vehicle status updates.

[0058] The cost management module is used to collect and manage all expenses related to vehicle operation. The cost management module includes seven independent expense entry and query interfaces, namely maintenance and repair expense management, vehicle fuel expense management, insurance expense management, vehicle decoration and accessories expense management, parking fee management, and other expense management. In any expense entry interface, the operator must fill in fields such as expense amount, date of occurrence, and expense type, and must select a specific vehicle number from the vehicle ledger and associate it with the expense. This mandatory association provides a data foundation for subsequent accurate single-vehicle cost accounting.

[0059] The early warning management module is an automatic monitoring and alert engine based on preset rules. It periodically performs checks in the background. For vehicle inspection reminders, insurance reminders, driver's license renewal reminders, and scrapping reminders, the judgment logic is as follows: it reads the corresponding date stored in the resource management module and compares it with the current system date. When the time difference is less than a preset threshold, an early warning message is generated. For abnormal fuel consumption and mileage reminders, the judgment logic is based on the aforementioned... and The formula is used for calculation, and when the state value is 1, an early warning message is generated.

[0060] The statistical analysis module is used to perform multi-dimensional and visual analysis and presentation of various types of data collected by the system. The statistical analysis module provides a report generation interface, which allows administrators to select time range, vehicle range or driver range to generate various statistical charts such as pie chart of single vehicle cost composition, bar chart of multi-vehicle fuel consumption comparison, and line chart of vehicle mileage trend. The various types of data collected by the system come from the expense data recorded by the cost management module and the trip data reported by the vehicle terminal layer.

[0061] In addition, the PC version includes a homepage module, a system management module, a system monitoring module, a system tools module, a workbench module, and an example demonstration module. The homepage module serves as the default interface after login, aggregating and displaying to-do reminders from the early warning management module and pending approval tasks from the operation management module. The workbench module integrates the most frequently used function entry points based on the logged-in user's role and permissions.

[0062] The mobile client in the software platform layer is a native application installed on mobile terminal devices such as smartphones or tablets. As the mobile interactive interface of the system, the native application is mainly aimed at drivers and managers with mobile office needs. Functionally, the mobile client is divided into a vehicle operation module, a trajectory query module, and a "My" module.

[0063] The vehicle operation module is a collection of functions that execute core vehicle-use business processes. Specifically, the vehicle operation module includes: The car rental application function provides a structured electronic form interface where drivers can enter required fields, including: expected start time, expected end time, destination, and reason for the ride. After submitting the form, the mobile device sends the application data to the data processing module, generating a car rental application record with a status of "pending approval".

[0064] Vehicle Use Approval Function: For administrators with approval authority, when there are applications pending approval, users can see the application list on this function interface. Clicking on any application will display its details. At the bottom of the interface, there are two operation buttons: Agree and Reject. Clicking either button will send an instruction carrying the application ID and approval result to the data processing module.

[0065] Vehicle dispatch function: For administrators with dispatch authority, the interface displays all vehicle requests that are in the approved state. After the dispatcher selects a request, the system will display a list of all available vehicles and their real-time locations on the map. After the dispatcher selects a specific vehicle and confirms the dispatch, the data processing module will generate a dispatch order and push the dispatch order information to the designated driver's mobile phone.

[0066] Return registration function: For drivers returning from a mission, after parking their vehicle in the designated parking space, the driver can click the "Confirm Return" button on this interface to send a return request to the data processing module. After receiving the request, the data processing module will further verify whether the parking space alarm device has reported the correct vehicle location information. Only after receiving the correct location information will the system finally update the status of the dispatch order to "completed", thus forming a complete business loop.

[0067] The vehicle dispatch order supplementary entry function is used to supplement the data of vehicle use events that have occurred but were not applied for in advance. This function provides a form similar to the vehicle application form, but requires additional information such as the actual usage time and mileage to ensure that all vehicle use behaviors are recorded.

[0068] Announcements and Today's Traffic Restriction Functions: These are purely information display interfaces, used to show management announcements issued by the PC client and vehicle restriction information queried based on the current date and city regulations.

[0069] The trajectory query module is used to replay the vehicle's historical driving routes. Users select a vehicle ID and a time range (start and end dates) in the trajectory query module interface. The mobile device sends this query request to the data processing module, which retrieves the coordinate sequence of all historical location points for the vehicle within that time range from the database and returns this sequence data to the mobile device. Upon receiving this coordinate sequence, the map component on the mobile device connects these points sequentially on the map interface, drawing and displaying them as a visual path.

[0070] My module is the entry point for various functions and information related to the currently logged-in user. Specifically, My module includes: The ride log feature displays all of the current user's historical ride logs in a list. Clicking on any item in the list allows you to view detailed information about the ride, including start and end times, route, mileage, and cost.

[0071] Vehicle Viewing Function: Provides users with a map interface that displays the current geographical location icons of all vehicles within their authorized range in real time.

[0072] Message notification function: As a message center, it displays all system notifications pushed to users in a list format, such as the approval result notification of car use application, and warning information from the warning management module.

[0073] The feature I initiated is a filter that specifically displays all car rental applications submitted by the current user and their current processing status (e.g., "pending approval", "approved", "rejected").

[0074] "Pending Approval" Feature: This feature is only visible to users with approval permissions. It functions as a to-do list, specifically displaying all vehicle use requests awaiting the user's approval.

[0075] Logout function: Clears the user's authentication credentials stored locally and returns to the login screen.

[0076] See attached document Figure 6 The vehicle application and dispatch process includes the following steps: Submit a vehicle application: This step is initiated by the applicant who needs a vehicle via their mobile phone. The applicant first logs into the mobile application, enters the vehicle operation module, and selects the vehicle application function. At this time, a structured electronic application form will be displayed on the user interface of the mobile phone.

[0077] Applicants need to enter their car usage information in the preset fields of the form. The fields must include at least the reason for car usage, destination, expected start time, and expected end time. After the information is filled in completely, the applicant submits the form. The mobile device encapsulates the data entered in the form into a standard format data packet (e.g., JSON format) and sends the data packet to the data processing module of the software platform layer through its network communication interface.

[0078] Application processing and approval: After receiving the data packet of the vehicle use application, the data processing module first verifies the validity of the data, then stores the application information in the vehicle use application table of the database, generates a unique application ID for the application, and sets its initial status field to pending approval.

[0079] Subsequently, the data processing module determines the approver corresponding to the application based on the pre-configured approval rules in the system. The approval rules can be set based on the applicant's department or the type of reason for vehicle use. After determining the approver, the data processing module generates an approval task and pushes a notification message containing the application ID to the designated approver's user account. The notification message is displayed in the approver's pending approval list on their mobile phone or in the workbench interface on their PC.

[0080] The approver can view the approval task on their mobile phone or PC and can click to view the detailed information of the vehicle application. The interface provides two operation options: approve and reject. After the approver selects one, the operation instruction along with the application ID is sent back to the data processing module. According to the received instruction, the data processing module updates the record status field of the corresponding application ID in the database to "approved" or "rejected" and pushes the approval result notification information back to the applicant's mobile phone.

[0081] Vehicle dispatching: If the status of a vehicle application record is updated to "approved", the data processing module will automatically present the record in the vehicle dispatching interface of the operation management module on the PC, so that the dispatcher can operate it.

[0082] On this interface, the dispatcher can see a list of all vehicle requests that are approved but not yet dispatched. At the same time, the interface also displays a vehicle status monitoring view, which shows all vehicles that are currently available in the vehicle register in the form of a map and a list. For each available vehicle, its real-time geographical location reported by the vehicle terminal layer is marked.

[0083] The dispatcher first selects a pending vehicle request from the request list, and then selects the most suitable vehicle from the vehicle status monitoring view based on factors such as vehicle location and type, and executes the assignment operation.

[0084] Generate and issue dispatch orders: After the dispatcher executes the assignment operation and confirms it, the confirmation instruction is sent to the data processing module. Upon receiving the instruction, the data processing module executes two parallel core operations: A new electronic vehicle dispatch record is generated in the database. The dispatch record is linked in data structure to the aforementioned application ID, the unique ID of the selected vehicle, and the user ID of the applicant, thereby binding the task, vehicle, and personnel. The dispatch record also inherits information such as the destination and estimated time from the original application. In the vehicle ledger of the resource management module, the status field of the selected vehicle is updated from available to in a task. This status change ensures that the vehicle cannot be selected for other scheduling tasks before it completes the current task and performs the return registration, thus guaranteeing the uniqueness of vehicle resource scheduling.

[0085] After completing the above operations, the data processing module will push the core information of the dispatch order (including the license plate number of the assigned vehicle and its fixed parking space number) to the driver's mobile phone in the form of a notification, guiding the driver to the designated location to pick up the vehicle. At this point, the vehicle application and dispatch process is completed.

[0086] See attached document Figure 7 The vehicle management method includes the following steps for monitoring the driving process and issuing early warnings for abnormalities: Route planning and monitoring parameter setting: At the same time as the dispatch order is generated, the data processing module of the software platform layer automatically performs route planning. It uses the coordinates of the vehicle's current parking space recorded in the vehicle ledger as the starting point and the destination recorded in the dispatch order as the ending point, calls the integrated electronic map service API (application interface) to calculate and generate a recommended driving route.

[0087] The data returned by the electronic map service API includes not only the sequence of geographic coordinates of the route, but also the reference mileage for system planning. The data processing module will use the reference mileage planned by the system. And a mileage deviation pre-configured in the system. This information is stored together in the associated data field of the dispatch order and used as a baseline parameter for subsequent monitoring.

[0088] Real-time collection and uploading of vehicle dynamic data: After the driver picks up the vehicle according to the dispatch order information and starts driving, the vehicle-mounted terminal layer installed on the vehicle begins to perform real-time data collection and uploading tasks.

[0089] Specifically, the positioning unit of the vehicle terminal layer calculates the real-time latitude and longitude coordinates of the vehicle at fixed time intervals (e.g., every 5 seconds). At the same time, the vehicle bus interface reads the real-time odometer reading from the vehicle's CAN bus. The vehicle main control unit combines the acquired latitude and longitude coordinates, current timestamp, and odometer reading into a data frame.

[0090] Subsequently, the vehicle-mounted main control unit controls the data communication unit to send data frames to the designated data receiving server in the software platform layer via the mobile communication network. The data uploading action continues at a set frequency (e.g., once per second) until the vehicle task is completed.

[0091] Calculate and compare actual mileage: The data processing module at the software platform layer continuously receives data frames from the vehicle terminal layer. For dispatch orders that are being executed, the data processing module will calculate the vehicle's actual mileage since the start of the task in real time based on the received odometer reading or continuous location coordinates. .

[0092] The data processing module periodically performs a comparison operation, comparing the currently calculated actual mileage. Reference mileage for system planning and storage of dispatch orders Compare and calculate the mileage deviation. .

[0093] Detect mileage anomalies and issue warnings: After calculating the mileage deviation... Then, the data processing module immediately compares it with the stored mileage deviation threshold. Comparison is used to determine abnormal mileage conditions. : Mileage abnormality status The calculation result is 1, indicating that the vehicle's actual mileage has exceeded the planned mileage plus the allowable deviation range. The data processing module determines that a mileage anomaly event has occurred. At this time, the data processing module performs two parallel operations: A new anomaly record is generated in the warning record table of the database. This record contains the dispatch order ID, the time of the anomaly, the vehicle's location at the time, and the specific values ​​of the actual mileage and the reference mileage, for post-event auditing and analysis. A warning command is generated, which contains a specific warning code to identify the abnormal type of mileage exceeding the limit. The data processing module sends the warning command to the data communication unit of the corresponding vehicle through the data link maintained with the vehicle terminal layer.

[0094] After receiving the warning command, the vehicle-mounted main control unit at the vehicle terminal layer parses the warning code and drives the driver's warning device to issue a corresponding warning signal based on the code. For example, it drives the buzzer to emit a series of short warning sounds to remind the driver that the driving distance has deviated from the planned distance. The warning process ensures the real-time nature of monitoring and the immediacy of intervention.

[0095] See attached document Figure 8 The parking location verification and alarm triggering process in the vehicle management method is triggered after the driver completes the task and drives the vehicle back to the parking lot. It specifically includes the following steps: Detecting vehicle parking and reporting identification information: When the driver parks the vehicle in a fixed parking space, the vehicle detection unit of the parking space alarm device installed under the parking space is activated. Specifically, the geomagnetic sensor built into the vehicle detection unit first detects the change in geomagnetic field caused by the metal parts of the vehicle, thereby determining that the parking space status changes from vacant to occupied.

[0096] Next, its built-in RFID reader automatically scans the vehicle and reads the unique electronic vehicle identification information stored in the RFID tag attached to the vehicle. After the microcontroller of the parking space alarm device obtains the parking space occupancy status and the vehicle's electronic identification information, it packages these two data with the device's own unique device ID into a data frame. Subsequently, the data frame is sent to the data processing module of the software platform layer through the communication unit.

[0097] Receiving information and performing data comparison: After receiving the data frame from the parking space alarm device, the data processing module immediately performs data parsing and verification. First, based on the device ID in the data frame, it queries the pre-stored hardware device mapping table in the system to determine the specific parking space number.

[0098] At the same time, based on the vehicle's electronic identity information in the data frame, the vehicle ledger in the resource management module is queried to determine the unique vehicle number of the currently parked vehicle.

[0099] Subsequently, the data processing module uses the vehicle number as an index to query the vehicle-parking space binding relationship mapping table stored in the system, thereby obtaining the correct fixed parking space number that uniquely assigns to the vehicle.

[0100] Determining the correctness of the parking location: The data processing module compares the two parking space numbers obtained: one is the actual parking space number parsed from the device ID of the parking space alarm device, and the other is the parking space number that should be parked in, which is queried from the vehicle-parking space binding relationship.

[0101] If the two parking space numbers are exactly the same, the data processing module determines that the parking behavior is correct, and the process enters the state of waiting for subsequent return registration.

[0102] If the two parking space numbers are inconsistent, the data processing module determines that the parking behavior is incorrect and immediately triggers the subsequent alarm process.

[0103] Triggering a physical alarm: After determining that the parking is incorrect, the data processing module generates an alarm trigger command. The data structure of the alarm trigger command contains a code that identifies the alarm type and the ID of the target device (i.e., the device ID of the parking space alarm device that reported the information).

[0104] The data processing module sends the alarm command to the target parking space alarm device via the data link. After the microcontroller of the device receives and parses the command, it drives its alarm execution unit to work. Specifically, it drives the buzzer to emit intermittent high-frequency sounds and simultaneously drives the LED light to emit a bright red flashing light.

[0105] This physical alarm signal, consisting of sound and visual signals, is intended to inform drivers that their vehicles are not parked in the correct designated location, prompting them to move their vehicles back to their designated parking spaces. Once the driver has moved the vehicle out of the incorrect parking space, the parking alarm device returns to idle status and the alarm automatically stops.

[0106] See attached document Figure 9 The vehicle management process, including registration and coordination, follows immediately after the vehicle is correctly parked. Specifically, it includes the following steps: Initiating a return-to-team registration request: After confirming that the vehicle has been parked in its unique and designated fixed parking space, the driver performs the return-to-team operation on the mobile app. Specifically, the driver enters the vehicle operation module, finds the dispatch order corresponding to the current task, and selects the return-to-team registration function button. The mobile app will generate a return-to-team registration request, which is a data packet containing the unique ID of the current dispatch order. The mobile app sends this data packet to the data processing module of the software platform layer through the network interface.

[0107] Perform dual-condition verification: After receiving a return-to-station registration request, the data processing module does not immediately complete the registration. Instead, it initiates a dual-condition verification procedure to ensure consistency between the person, vehicle, and location. This verification procedure includes two conditions that must be met simultaneously: Condition 1: Operation confirmed. The data processing module confirms that it has received the return registration request initiated by the driver via mobile phone for this dispatch order ID.

[0108] Condition 2: Physical presence confirmation. The data processing module queries the database based on the received dispatch order ID to obtain the vehicle ID bound to the dispatch order and its corresponding unique fixed parking space ID. Subsequently, it queries the real-time status table, which is continuously updated by all parking space alarm devices. The data processing module checks whether the status currently reported by the parking space alarm device corresponding to the target fixed parking space ID is occupied, and whether the identified vehicle electronic identity information is consistent with the vehicle ID bound to the dispatch order.

[0109] The branch operation is executed based on the verification results: The data processing module judges the verification results of the above dual conditions: If any condition is not met (for example, only vehicle availability information is received but the driver has not clicked to register, or the driver clicked to register but the vehicle is not in the correct location), verification fails. The data processing module sends an operation failure notification to the mobile device that initiated the request. The notification message states that the registration for returning to the parking space has failed. Please confirm that the vehicle is parked in the designated parking space. The process terminates and will be triggered again once the conditions are met.

[0110] If both conditions are met, the verification is successful. The data processing module determines that the queuing registration can be performed and proceeds to the next step.

[0111] Execution status update and linkage control: After successful verification, the data processing module executes the following three operations in parallel: Update dispatch status: It updates the status field of the record corresponding to the dispatch ID in the database from the task to "completed".

[0112] Update vehicle status: In the vehicle ledger of the resource management module, it restores the availability status field of the dispatched vehicle to available status from the task, so that the vehicle can be selected by a new scheduling task.

[0113] Trigger linkage operation: If the area to which the vehicle belongs (e.g., the emergency repair vehicle area) is equipped with a fully automatic sunshade, the data processing module generates an unfolding command. The unfolding command is sent via the data link to the control unit of the specific fully automatic sunshade installed above the vehicle's fixed parking space, thereby driving the sunshade to unfold automatically and provide shade for the vehicle returning to the parking space.

[0114] At this point, the process of returning to the team, registration, and coordinated operation has been completed, and the vehicle's current usage cycle has formed a closed loop in the system.

[0115] Referring to the attached diagram, the automatic back-end cost aggregation and calculation in the vehicle management method precisely binds various expenses incurred during vehicle operation to specific vehicles, and performs automated cost aggregation and calculation based on this. Specifically, it includes the following steps: Enter discrete cost data: This step is performed by authorized back-office administrators (e.g., finance or administration personnel) through the cost management module on the PC. The cost management module provides independent data entry interfaces for different expense types, including: maintenance and repair costs, insurance premiums, vehicle accessories costs, parking fees, and other expenses.

[0116] In any expense entry interface, the user interface contains a set of structured data input fields, such as expense amount, date of occurrence, expense description, etc. The mandatory key operation is that the user must select a unique vehicle from a drop-down list or search box that has been preloaded with all vehicle license plates in the system. The data source of the list comes directly from the vehicle ledger in the resource management module. When the user submits the expense record, the data processing module will forcibly associate the expense amount with the selected unique vehicle ID in the database. This design ensures that every discrete, non-automatically collected expense can be aggregated to a single vehicle entity.

[0117] Fuel cost data collection: Fuel costs are collected by entering each refueling event in the vehicle fuel cost management interface of the cost management module. When entering data, managers need to fill in the volume of fuel consumed within the refueling cycle. Total amount paid And the vehicle's current total mileage displayed on the dashboard when refueling. The refueling event record is also forcibly bound to a unique vehicle ID.

[0118] Triggering Cost Summary Calculation: Cost summary calculation is not performed in real time, but is triggered by a specific event. In one embodiment, the triggering event is a query request initiated by a user in the statistical analysis module on the PC. The user selects one or more vehicle numbers on the statistical analysis module interface and specifies a time interval to be analyzed (e.g., a specific month or quarter). The query request is then sent to the data processing module.

[0119] Performing category summation and total cost calculation: After receiving a query request, the data processing module uses the received vehicle ID and time interval as filtering conditions for the database query, and performs data retrieval and calculation operations. First, retrieve all records that meet the criteria from different cost data tables, and then sum them up according to cost type. For example, sum the amounts of all maintenance and repair cost records to obtain the total maintenance and repair cost for that time period. Add up all the recorded premium amounts to get the total premium. Similarly, the costs for car accessories and decorations are calculated separately. ,Parking Fee Other expenses .

[0120] For fuel costs, retrieve all refueling event records that meet the criteria, and then... Add all the values ​​in the fields to get the total vehicle fuel cost for that time period. .

[0121] After summing all the categorized fees, the data processing module calculates the total operating cost of the vehicle over the time period. .

[0122] After the calculation is completed, the data processing module will return the structured data containing the cost of each item and the total cost to the PC, and the statistical analysis module will present it in the form of reports or charts.

[0123] The multi-dimensional early warning and alert mechanism is automatically executed in the background by the data processing module at the software platform layer. Its purpose is to proactively monitor key vehicle-related events and data, and issue timely alerts to management personnel. The specific process is as follows: Initiate periodic scanning tasks: The data processing module integrates a system scheduler, which is configured to automatically trigger global scanning tasks at a preset time frequency (e.g., once every morning). Global scanning tasks are the starting point of the entire early warning and reminder mechanism.

[0124] Retrieving static and dynamic data: When a scanning task is triggered, the data processing module first retrieves the baseline data and status data used for judgment from various modules of the system in batches.

[0125] Static baseline data retrieval: This module extracts specific date information for vehicles and drivers from the vehicle and driver ledgers in the resource management module. This information primarily includes the vehicle's next annual inspection date, insurance expiration date, mandatory scrapping date, and the driver's license annual review date. It also extracts the preset maintenance mileage intervals and standard fuel consumption per 100 kilometers for each vehicle model. and its allowed floating threshold .

[0126] Dynamic status data retrieval: The module extracts the current cumulative mileage, mileage since the last maintenance, and fuel volume at the two most recent refuelings for each vehicle from the cost management module and vehicle operation history. and the corresponding total mileage at the time of refueling .

[0127] Execute multi-dimensional rule judgments: The data processing module applies the retrieved data to a series of preset rule judgment logics, which constitute the multi-dimensional core of the early warning mechanism.

[0128] Time-based judgment (expiration reminder): For events such as vehicle annual inspection, insurance, and driver's license renewal, the judgment logic is as follows: compare the retrieved target expiration date with the current system date. If: target expiration date - current system date ≤ preset reminder days (e.g., days), then an alert is triggered. The preset reminder days are a parameter that can be flexibly configured by the administrator in the system management module.

[0129] Usage Dimension Judgment (Maintenance Reminder): The judgment logic is as follows: compare the mileage retrieved since the last maintenance with the preset maintenance mileage interval for this model. If the mileage since the last maintenance is greater than or equal to the maintenance mileage interval, then it is determined that a maintenance warning has been triggered.

[0130] Performance dimension judgment (abnormal fuel consumption): The judgment logic is based on the most recent refueling interval. The module first calculates the actual fuel consumption per 100 kilometers for that interval based on the mileage difference between the two refuelings and the volume of fuel refueled during that period. Then, Standard fuel consumption per 100 kilometers for the vehicle and floating threshold If a comparison is made, If this occurs, it is determined to be abnormal fuel consumption, triggering a warning. This is the abnormal fuel consumption status mentioned earlier in this article. The case where the value is 1.

[0131] Behavioral dimension judgment (mileage anomaly): The judgment logic is to perform post-event auditing on completed dispatch orders. The module scans all dispatch orders with a status of "completed" since the last task execution and compares their recorded actual mileage. and planning reference mileage ,like If this occurs, it is determined to be an abnormal mileage, triggering a warning, i.e., an abnormal mileage status. The case where the value is 1.

[0132] Generate and push alert information: For any event determined by the judgment logic to be triggered, the data processing module will perform the following standardized operations: First, it generates a new record in the warning information table of the database. The record details the type of warning (e.g., insurance is about to expire), the associated vehicle or driver, specific data to support the warning (e.g., current fuel consumption is 15L / 0km, exceeding the standard value by %), and the time of generation.

[0133] Subsequently, the data processing module pushes the warning information to the relevant management personnel according to the preset notification strategy. The notification strategy is configurable in the system, allowing different types of warnings to be assigned to different roles (for example, finance personnel receive insurance expiration reminders, and fleet captains receive maintenance and fuel consumption anomaly reminders). The information is pushed through two channels: one is presented as a to-do item in the warning management module and homepage workbench on the PC; the other is sent as an instant push notification to the mobile phone of the corresponding management personnel account via mobile application push service.

Claims

1. A vehicle operation and maintenance management system, characterized in that, include: The software platform layer includes a data processing module, which performs management, monitoring, and analysis functions according to preset logic, and generates the alarm trigger command and the early warning command. An infrastructure layer, deployed in the vehicle parking area, includes multiple parking space alarm devices. Each parking space alarm device is configured in a fixed parking space to detect the vehicle identity information and the parking space information of the parked vehicle, and sends the vehicle identity information and parking space information to the software platform layer, and receives alarm triggering instructions from the software platform layer to execute the alarm. The vehicle-mounted terminal layer, installed inside the controlled vehicle, includes a positioning unit, a data communication unit, and a driver warning device. It is used to collect and report the real-time geographical coordinates and actual mileage of the vehicle, and to receive warning instructions from the software platform layer to drive the driver warning device to work.

2. The vehicle operation and maintenance management system according to claim 1, characterized in that, The data processing module stores the binding relationship between vehicle numbers and fixed parking space numbers; The data processing module further includes: after receiving the vehicle identity information and parking space information reported by the parking space alarm device, parsing out the actual parked vehicle number and the actual parked parking space number, querying the pre-stored binding relationship based on the actual parked vehicle number, obtaining the corresponding target parking space number, and when it is determined that the actual parked parking space number is inconsistent with the target parking space number, generating and sending the alarm trigger command to the parking space alarm device.

3. The vehicle operation and maintenance management system according to claim 2, characterized in that, The software platform layer also includes a mobile terminal; The data processing module is also configured to perform dual-condition verification to complete the return registration; Receive a return-to-team registration request from a dispatch order initiated by the driver via the mobile device; Confirm that the vehicle bound to the dispatch order has been parked in the designated fixed parking space. The confirmation is based on the vehicle identity information and parking space information reported by the parking space alarm device being consistent with the preset binding relationship. The data processing module determines that the registration for returning to the team is successful and updates the status of the dispatch order to "completed" only when both conditions are met simultaneously.

4. A vehicle operation and maintenance management system according to claim 1, characterized in that, The data processing module stores the reference mileage and mileage deviation threshold of the system plan associated with the vehicle dispatch order; The data processing module further includes: acquiring the actual mileage of the vehicle reported by the vehicle terminal layer in real time, and calculating the mileage deviation by comparing the actual mileage with the reference mileage planned by the system; When the mileage deviation is determined to be greater than the mileage deviation threshold, a warning command is generated and sent to the vehicle terminal layer, driving the driver warning device to output warning information to the driver.

5. A vehicle operation and maintenance management system according to claim 3, characterized in that, The infrastructure layer also includes fully automated sunshades installed above designated fixed parking spaces; After determining that the registration for returning to the parking space is successful, the data processing module is also configured to generate and send an unfolding command to the fully automatic sunshade corresponding to the fixed parking space, driving the fully automatic sunshade to unfold automatically.

6. A vehicle operation and maintenance management system according to claim 1, characterized in that, The data processing module further includes: The fuel consumption per 100 kilometers per cycle is calculated based on the volume of fuel consumed within a specified cycle and the total mileage driven within that cycle. By comparing the periodic fuel consumption per 100 kilometers with the vehicle's historical average fuel consumption per 100 kilometers, and combining this with a preset fuel consumption fluctuation threshold, it is determined whether an abnormal fuel consumption state has occurred. When the abnormal fuel consumption condition is determined to occur, an early warning message is generated and pushed to the management personnel.

7. A vehicle operation and maintenance management system according to claim 1, characterized in that, The software platform layer also includes a PC client; The PC terminal includes a cost management module, which is used to input discrete cost data that is forcibly associated with a unique vehicle number; The data processing module further includes: according to the query request, collecting and classifying the discrete cost data and fuel cost data of the specified vehicle within a specified time interval, and summing them to calculate the total operating cost of the vehicle.

8. A vehicle operation and maintenance management system according to claim 1, characterized in that, The vehicle terminal layer also includes a vehicle main control unit and a vehicle bus interface; The vehicle bus interface is connected to the vehicle's controller area network bus and is used to read the mileage displayed on the vehicle's instrument panel. The vehicle-mounted main control unit is connected to the vehicle bus interface and the data communication unit, and is used to package the data including the mileage displayed by the instrument, and control the data communication unit to report it to the software platform layer as the data source of the actual driving mileage.

9. A vehicle operation and maintenance management system according to claim 1, characterized in that, The parking space alarm device includes a vehicle detection unit; The vehicle detection unit consists of a geomagnetic sensor and a radio frequency identification reader; The geomagnetic sensor is used to detect whether there is a vehicle in the parking space to determine the parking space occupancy status, and the radio frequency identification reader is used to read the radio frequency identification tag on the vehicle and obtain the vehicle's identity information.

10. A vehicle operation and maintenance management method according to claim 1, characterized in that, Includes the following steps: S1. By deploying a parking space alarm device in the infrastructure layer of the vehicle parking area, the vehicle identity information and the parking space information of the parked vehicle are detected, and the vehicle identity information and parking space information are sent to the software platform layer; S2. The vehicle's real-time geographical location coordinates and actual mileage are collected and reported to the software platform layer through the vehicle terminal layer installed inside the controlled vehicle. S3. The data processing module of the software platform layer receives and processes data from the parking space alarm device and the vehicle terminal layer, and determines whether an alarm trigger command or a warning command needs to be generated according to preset logic. S4. When the alarm trigger command is generated, the alarm trigger command is sent to the corresponding parking space alarm device to execute the alarm; When the warning command is generated, it is sent to the corresponding vehicle terminal layer to drive the driver warning device to work.

Images