Disclosure of Invention
The technical problem to be solved by the present invention is to provide a vehicle remote monitoring and diagnosing system and method for remote monitoring, fault early warning, fault diagnosis and fault removal of a vehicle, so as to reduce or avoid the aforementioned problems.
In order to solve the technical problem, the invention provides a vehicle remote monitoring and diagnosing system which at least comprises a background operation center and a vehicle-mounted terminal, wherein the background operation center at least comprises a database server, a WEB server, a monitoring configuration server, a gateway server and a communication subsystem; the vehicle-mounted terminal is communicated with the communication subsystem to transmit vehicle and running state information; the monitoring configuration server can monitor and manage the communication subsystem; the WEB server can control the information of the configured vehicle and process the registration and customization information of the vehicle user; the communication subsystem can read the early warning condition, compare the early warning condition with the data sent by the vehicle-mounted terminal, if the early warning condition is met, send an early warning instruction to the gateway server, and the gateway server sends early warning information in real time according to a set early warning form and stores related data in the database server.
Preferably, the early warning condition can be customized through the WEB server and stored in the database server.
In addition, the vehicle remote monitoring and diagnosing system further comprises a diagnosis refreshing terminal, wherein the diagnosis refreshing terminal can be in direct communication with the vehicle-mounted terminal and remotely refreshes programs of the vehicle ECU through the vehicle-mounted terminal.
In addition, the background operation center further comprises a WEB server, and the WEB server can provide the data stored in the database server to users on the Internet in a WEB mode, and can receive various information customized by users logging in the WEB server and store the information in the database server.
More preferably, the vehicle-mounted terminal and the communication subsystem communicate through TCP/IP.
Further preferably, the vehicle-mounted terminal includes a wireless communication module, and the wireless communication module can communicate at least through one of GPRS, CDMA, and 3G networks.
And the data stored in the database server at least comprises one of the following data:
(1) monitored vehicle status data and fault diagnosis results;
(2) user permission data;
(3) an ECU program that needs to be downloaded;
(4) vehicle configuration information.
The failure early warning of the gateway server at least comprises one of the following modes:
(1) short message of mobile phone;
(2) an email;
(3) an instant message.
On the other hand, the invention also provides a method for carrying out vehicle remote monitoring diagnosis by adopting the vehicle remote monitoring diagnosis system, which comprises the following steps:
(1) configuring vehicle information, user registration and customization information and early warning conditions in the WEB server, and storing the vehicle information and the early warning conditions in the database server;
(2) the monitoring configuration server checks the change of the configuration in the database server and downloads the configuration to the vehicle-mounted terminal through the communication subsystem;
(3) the vehicle-mounted terminal transmits the customization information to the communication subsystem according to user configuration; the communication subsystem compares the transmitted data with the early warning condition in the database server, and if the early warning condition is met, the communication subsystem sends the early warning information to the gateway server and stores the data in the database server;
(4) and the gateway server sends early warning information in real time according to a set early warning form.
And the above method further comprises the steps of:
(5) when the communication subsystem compares the received customized information with the early warning conditions in the database server, if the vehicle is judged to have a fault, the diagnosis refreshing terminal directly communicates with the vehicle-mounted terminal through the communication subsystem;
(6) the vehicle-mounted terminal controls an ECU of the vehicle to carry out fault diagnosis;
(7) and the vehicle-mounted terminal sends the fault diagnosis result and/or the fault elimination condition back to the diagnosis refreshing terminal.
The invention can customize the information needed to diagnose and pre-warn according to the specific requirements of different vehicles and different users, and set the corresponding pre-warn value by using the information, when the diagnosis value of some equipment of the vehicle deviates or exceeds the set pre-warn value, the alarm can be sent out in advance, and the state information of the equipment or the whole vehicle can also be sent to a remote server, so as to be beneficial to diagnosing the vehicle in a remote way, and can remotely send out related instructions to remove the fault or control the vehicle to avoid the fault or indicate the driver to maintain or repair.
Detailed Description
In order to more clearly understand the technical features, objects, and effects of the present invention, embodiments of the present invention will now be described with reference to the accompanying drawings. Wherein like parts are given like reference numerals.
Fig. 1 is a schematic structural diagram of a vehicle remote monitoring and diagnosing system according to the present invention. As shown in fig. 1, the vehicle remote monitoring and diagnosing system provided by the present invention may include a backoffice operation center 100, a vehicle-mountedterminal 200, adiagnosis refreshing terminal 300 and adisplay terminal 400, which may be connected to each other through the Internet, wherein afirewall 500 may be disposed between the backoffice operation center 100 and the Internet.
Theback office 100 may include adatabase server 102, aWEB server 104, amonitoring configuration server 106, agateway server 108, and acommunications subsystem 110.
Thedatabase server 102 may be responsible for storing basic vehicle operation information, diagnostic information, user-customized information, programs that the in-vehicle terminal 200 needs to download for updating, and the like. That is, thedatabase server 102 stores therein basic operation information of various vehicles under the monitoring of the entire system, such as a vehicle type, an engine model, information for use, a password for logging in the system, relevant parameters of various on-vehicle devices, and the like. Based on the information that has been preset in thedatabase server 102, the relevant personnel can log in the user interface of the system via the Internet to maintain the data in thedatabase server 102, for example, to change the user password, to correct the error information recorded in thedatabase server 102, and so on. In addition, according to the relevant parameters of various vehicle-mounted devices stored in thedatabase server 102, the backoffice operation center 100 may determine the versions of the management and diagnosis software systems of the vehicle-mounted devices of various vehicles in the system, and may determine whether the software systems in the vehicle-mounted devices need to be updated, and under the condition that a set condition is met, for example, under the condition that the vehicles are networked, the backoffice operation center 100 may automatically or manually download relevant update programs to the vehicle-mountedterminals 200 of the vehicles through thecommunication subsystem 110. In addition, thedatabase server 102 may also store customization information corresponding to each vehicle, and vehicle diagnostic information transmitted from the in-vehicle terminal 200, to facilitate vehicle repair and maintenance, as will be described in further detail below.
TheWEB server 104 provides the data stored in thedatabase server 102 to users on the Internet in a WEB manner, and may receive various information customized by the user logging in theWEB server 104 and store the information in thedatabase server 102. That is to say, through the WEB service, the vehicle user can customize information, and achieve personalized acquisition of required data. The personalized design enables the user account to be automatically bound with the WEB page, different user WEB display contents are different and are consistent with respective customized contents, and personalized user experience is achieved. In order to facilitate the user to access the information, the part can adopt a B/S architecture design.
Thecommunication subsystem 110 may communicate with the in-vehicle terminal 200 to acquire various information of the vehicle, and store the data in thedatabase server 102 through analysis processing. Thecommunication subsystem 110 uses a TCP/IP method for communication. Thecommunication subsystem 110 adopts a communication cluster design, realizes scheduling of a plurality of communication servers 114-1 and 114-2 through thescheduling server 112, realizes load balancing of the system, and is suitable for concurrent requests of a large number of vehicle-mountedterminals 200. In addition, thecommunication subsystem 110 is responsible for processing the early warning, the communication servers 114-1 and 114-2 in thecommunication subsystem 110 can read preset early warning conditions in a database, compare the early warning conditions with data sent by the vehicle-mountedterminal 200, if the early warning conditions are met, send an early warning instruction to thegateway server 108, and thegateway server 108 sends early warning information to relevant devices of vehicle users, such as mobile phones and PDAs, in real time according to set early warning forms, such as mobile phone short messages and emails, to notify the set vehicle users, and store relevant data in thedatabase server 102.
Themonitoring configuration server 106 may monitor and manage thecommunication subsystem 110, monitor vehicle operating conditions, check for changes in associated data, and diagnose theupdate terminal 300, monitor vehicle operating condition data.
As shown in fig. 1, onebackground operation center 100 may correspond to a plurality of vehicles of different types, each vehicle has a vehicle-mountedterminal 200, and the vehicle-mountedterminal 200 may be used to collect vehicle customization information, transmit the collected data to thebackground operation center 100 through wireless communication, respond to a request for controlling devices in the vehicle for diagnosis, program refresh, and the like, respond to the request, operate, and return the result data of the response to thebackground operation center 100.
Also as shown in fig. 1, adiagnostic refresh terminal 300 corresponding to a different vehicle may be provided in a service shop or a 4S shop to initiate a specific diagnostic request and remotely refresh the program of the vehicle ECU. Thediagnostic refresh terminal 300 functions as a tester, integrates various diagnostic services and diagnostic logics therein, and thediagnostic refresh terminal 300, the in-vehicle terminal 200, and the vehicle ECU constitute a diagnostic system. First, a diagnostic protocol stack is integrated in the vehicle ECU, and when the vehicle ECU malfunctions, the vehicle ECU itself records the malfunction state. Secondly, the vehicle-mountedterminal 200 integrates the contents of the link layer and the network layer of the communication protocol stack, and realizes the forwarding of information: namely, the diagnosis request of thediagnosis refresh terminal 300 is forwarded to the vehicle ECU, and the response data of the vehicle ECU is forwarded to thediagnosis refresh terminal 300, and the vehicle-mountedterminal 200 is connected to thediagnosis refresh terminal 300 or the background operation center through wireless (GPRS, etc.), and is connected to the vehicle ECU through a diagnosis bus. Again, thediagnostic refresh terminal 300 integrates diagnostic logic for a particular diagnostic, responsible for issuing requests for a particular diagnostic or program refresh.
According to an embodiment of the present invention, the vehicle remote monitoring and diagnosis system of the present invention may further include a plurality ofdisplay terminals 400, which may be used to display customized information of a user of the vehicle. It may be a PC installed in a maintenance shop or a 4S shop, or any other device that can be connected to the Internet, such as a laptop, a PDA, NETNOTE, a mobile phone, etc., and these devices may be installed in a vehicle or inside thebackground operation center 100. The monitoring display program can adopt a B/S framework, and a vehicle user can acquire required data by using a browser carried by a PC system. The detailed process is shown in fig. 4, which shows a flowchart of real-time data monitoring of the terminal 400. Thedisplay terminal 400 is accessed to the vehicle remote monitoring and diagnosing system of the present invention through the Internet.
The functions and operation of the vehicle remote monitoring and diagnosing system of the present invention will be described with reference to fig. 2 to 4. FIG. 2 is a flow chart of the present invention for customizing vehicle user information; FIG. 3 is a flow chart of the message early warning of the present invention; and fig. 4 is a flowchart illustrating real-time data monitoring of thedisplay terminal 400 according to the present invention.
As shown in fig. 2, since vehicles of different models are equipped with different types of equipment devices, the equipment devices can generate different signals, and different vehicle users have different signal acquisition requirements, when a vehicle is networked, the user can set corresponding vehicle information which needs to be acquired and monitored by the vehicle remote monitoring and diagnosing system according to the vehicle model and the self-requirements, thereby realizing information customization of different users.
First, in step S11, the vehicle enters the network and basic vehicle information is created. For example, themonitoring configuration server 106 may be logged in by the administrator, information related to various vehicles, such as vehicle types, engine models, parameters related to various onboard devices, and the like, may be newly created, and the created vehicle information may be stored in thedatabase server 102 through themonitoring configuration server 106.
Then, in step S12, when the system administrator logs in theWEB server 104, the system administrator creates a new user, assigns the previously configured basic vehicle information to each user according to the vehicle type actually driven by the user, and also assigns a corresponding alias, password, personal information of the user, and the like to each user.
Thereafter, in step S13, the user may log in to theWEB server 104 via the Internet, for example, may connect to the Internet via thedisplay terminal 400. The user can log in theWEB server 104 on thedisplay terminal 400 by using the user name or alias set by the system administrator and the corresponding password, and configure some other basic user registration information that is not set by the system administrator, and store the information in thedatabase server 102, where the configuration information may include:
a. defining a signal of interest to a user;
b. the corresponding relation between the source of the signal concerned by the user in the vehicle and the vehicle-mounted terminal channel;
c. the early warning range of the signal concerned by the user;
d. the signal acquisition mode comprises periodic acquisition and trigger acquisition.
Next, in step S14, the user needs to wait for the system administrator to process and authorize the configuration information input by the user, and after the configuration information customized by the user is authorized, theWEB server 104 stores the data of the customized configuration information transmitted from thedisplay terminal 400 in the database, and themonitoring configuration server 106 may check the change of the customized configuration information, and download the change of the configuration information to the in-vehicle terminal 200 through thecommunication subsystem 110, thereby completing the customization of the vehicle user information, as shown in fig. 2.
The vehicle failure early warning process is described in detail below with reference to fig. 3. As shown in fig. 3, when the customization and configuration of the vehicle user information is successful in step S21, the vehicle-mountedterminal 200 collects specific signal data, such as diagnostic information of the engine, according to the user configuration information, and transmits the specific signal data to thecommunication subsystem 110 in step S22.
In step S24, one of the communication servers in thecommunication subsystem 110, for example, the communication server 114-1 accesses thedatabase server 102, reads the preset warning condition in the database, compares the warning condition with the specific signal data sent by the in-vehicle terminal 200, if the warning condition is reached, sends a warning instruction to thegateway server 108 in step S25, thegateway server 108 sends the fault warning information to the user in real time according to the set warning form, such as a mobile phone short message, Email, etc., and stores the relevant fault warning information data in thedatabase server 102 in step S26.
Fig. 4 shows a flow chart of real-time data monitoring of thedisplay terminal 400 according to the present invention. As shown in fig. 4, in step S31, the user or administrator may log in to theWEB server 104 through any Internet-connectabledisplay terminal device 400, such as a laptop, a PDA, a NETNOTE, a mobile phone, etc. In step S32, theWEB server 104 checks whether the user is authorized, and if the user has not been set by theconfiguration server 106 in advance, or has been set but not authorized by only the administrator, the user cannot log in the system through these devices, and in both cases, the user is prompted to be unauthorized in step S321.
After logging on the system, if authorization is obtained, the system checks whether the user information has been configured in step S33, and if not, the system prompts the user to configure information of the relevant vehicle before further customizing various information, especially warning information, in step S331. Generally, the customized information needs to rely on the configuration information to achieve the purpose of early warning. If configured, customized information is displayed to the user in real-time.
Fig. 5 is a block diagram of an in-vehicle terminal 200 in the vehicle remote monitoring diagnosis system according to the present invention.
As shown in fig. 5, the in-vehicle terminal 200 includes an AD acquisition module 202, a digital signal acquisition module 204, a bus acquisition module 206, a power management module 208, a diagnostic refresh module 210, a remote communication module 212, and an embedded processor 214.
Each data acquisition module is responsible for signal data acquisition of various vehicle-mounted equipment devices, and the signals can reflect the basic running conditions of the vehicle. Because vehicles with different models are provided with different types of equipment devices, the equipment devices can generate different signals, and different vehicle users have different signal acquisition requirements, when the vehicles are networked, the system can customize data according to the users and control the vehicle-mountedterminal 200 to acquire the data according to different acquisition modes. And each data acquisition module is connected to the in-vehicle system through a wire harness or a bus.
The remote communication module 212 is connected to the Internet by wireless, and is responsible for sending the collected data to thebackground operation center 100. The backoffice operation center 100 will define different backhaul modes according to different situations and download the relevant configurations to the vehicle-mountedterminal 200.
The power management module 208 may set different operating modes according to the requirement of low power consumption of the vehicle-mounted device, and enter a sleep mode or a low power consumption mode when the vehicle-mountedterminal 200 is not required to operate. And provides a wake-up mechanism to wake up at a required time to enable the vehicle-mountedterminal 200 to enter a normal working state.
The diagnostic refresh module 210 is responsible for responding to diagnostic refresh requests issued by theback office 100. The module is accessed to an in-vehicle network through a bus, communicates with an ECU of the vehicle, and performs control operations such as fault diagnosis and program refreshing on the ECU. Thediagnostic refresh module 200 integrates a diagnostic protocol stack, such as a communication layer protocol stack of ISO 14230, ISO 15765, SAE 1939, etc., to adapt to the diagnosis of different vehicle ECUs.
The vehicle remote failure diagnosis and remote failure removal process will be described in detail below with reference to fig. 6.
First, in steps S41-S43, when a vehicle fails, thediagnostic refresh terminal 300 sends a request to themonitoring configuration server 106 requesting a connection to a particular vehicle. Notably, the timing of sending the request depends on the application with the user: the 4S store diagnosticians can initiate diagnosis after receiving the fault information; or 4S shop maintenance to inquire vehicle state; it may also be that the 4S store has some control over the vehicle. Specifically, in step S42, a fault is warned in accordance with the set warning mode, and the user and the diagnostician are notified. In step S43, the diagnostician uses thediagnostic refresh terminal 300 to request themonitoring configuration server 106 to access the backoffice operations center 100.
Then, in step S44, thebackground operation center 100 checks the diagnostic authority, and if the check is successful, the next step is performed; if the verification is unsuccessful, no diagnosis authority is prompted in step S441, and the procedure ends.
Next, in step S45, the specialist establishes a connection of thediagnostic refresh terminal 300 and the in-vehicle terminal 200; in step S46, the specialist checks for authorization for diagnosis; in step S47, the expert initiates a diagnosis or program refresh request through thediagnosis refresh terminal 300; in step S48, the request is forwarded to the requested vehicle ECU via the in-vehicle terminal 200; in step S49, the vehicle ECU responds to the request; finally, in step S50, the response is forwarded to thediagnostic refresh terminal 300 via the in-vehicle terminal 200.
Specifically, in the operation process, themonitoring configuration server 106 queries a scheduling table in thescheduling server 112, and sends a connection request command to the vehicle-mountedterminal 200 of the specific vehicle through the communication servers 114-1 and 114-2 connected thereto; then the vehicle-mountedterminal 200 of the specific vehicle enters a fault diagnosis and elimination mode, and communication connection with the diagnosis andrefreshing terminal 300 is established;
after the communication connection is established, thediagnosis refreshing terminal 300 initiates a fault diagnosis or fault elimination request for the specific vehicle ECU;
the in-vehicle terminal 200 sends a request to a bus connected to the ECU of the specific vehicle through a communication protocol stack integrated therein;
the specific vehicle ECU performs failure diagnosis in response to the failure diagnosis or the failure removal request, and performs refreshing of the ECU program according to the situation to remove the failure.
Finally, the in-vehicle terminal 200 sends the failure diagnosis result and/or the failure-resolved condition back to the diagnosis refresh terminal 300 (if a diagnosis request is issued, the result of diagnosis and the state of diagnosis are returned; if a program refresh request is issued, the state of program download is returned).
The technical scheme has the characteristics that the original remote fault diagnosis system is changed, a data providing mode is changed, data PUSH required by a user is automatically provided for the user through the system, and user experience is enhanced. This is achieved through WEB by first customizing the information required by the user. Before this, the vehicle and the user also need to be configured and bound through the WEB. After this, themonitoring configuration server 106 is required to download the configuration customized by the user into the corresponding vehicle.
The invention can customize the information needed to diagnose and pre-warn according to the specific requirements of different vehicles and different users, and set the corresponding pre-warn value by using the information, when the diagnosis value of some equipment of the vehicle deviates or exceeds the set pre-warn value, the alarm can be sent out in advance, and the state information of the equipment or the whole vehicle can also be sent to a remote server, so as to be beneficial to diagnosing the vehicle in a remote way, and can remotely send out related instructions to remove the fault or control the vehicle to avoid the fault or indicate the driver to maintain or repair.
The above description is only an exemplary embodiment of the present invention, and is not intended to limit the scope of the present invention. Any equivalent alterations, modifications and combinations can be made by those skilled in the art without departing from the spirit and principles of the invention.