Monitoring method, device, computer equipment and readable storage medium of vehicle-mounted unit

Abstract

The present application relates to a monitoring method, device, computer equipment, computer-readable storage medium and computer program product for an on-board unit. The method comprises: in response to a status monitoring trigger operation for the on-board unit, obtaining a plurality of status fields recorded in the on-board unit, wherein the plurality of status fields respectively correspond to a different target status; for each status field, determining the current status value of the targeted status field; according to the current status value of the targeted status field, determining the configuration progress of the on-board unit in the corresponding target status; generating status prompt information for the on-board unit according to the configuration progress, and voice broadcasting the status prompt information. The use of this method can greatly improve the interaction between the user and the OBU device through an intelligent monitoring and voice feedback mechanism, so that the user can independently diagnose and solve equipment problems, improve the convenience of use and driving safety, and also enhance the user experience.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a monitoring method, device, computer equipment, computer-readable storage medium and computer program product for an on-board unit. Background Art

[0002] With the promotion and popularization of high-speed OBU (On-Board Unit, the on-board unit of the electronic toll collection system) equipment, more and more car owners purchase and install and activate OBU devices online, resulting in various problems in the use of OBU devices, such as not knowing how to install and activate OBU devices, OBU devices running out of power, highway barriers not being lifted, device failure and inability to reactivate and trade, device hardware failure and other types of failures.

[0003] However, the current OBU equipment itself does not have key status monitoring capabilities, and cannot provide users with simple, clear interactive feedback that they can understand. As a result, users are unable to understand the status of the equipment and perform corresponding operations. As a result, very simple problems cannot be solved quickly, and users need to go to manual outlets to have professionals inspect and handle them, which affects the user experience and driving safety of the OBU equipment. It is also time-consuming and labor-intensive, causing some users to give up using OBU equipment. Summary of the invention

[0004] Based on this, it is necessary to provide a monitoring method, device, computer equipment, computer-readable storage medium and computer program product for an on-board unit that can accurately locate the OBU device status in various scenarios and output corresponding feedback signals in response to the above technical problems.

[0005] In a first aspect, the present application provides a method for monitoring a vehicle-mounted unit, comprising:

[0006] In response to a status monitoring trigger operation for an onboard unit, obtaining a plurality of status fields recorded in the onboard unit, wherein each of the plurality of status fields corresponds to a different target status;

[0007] For each of the status fields, determine the current status value of the status field;

[0008] Determining the configuration progress of the onboard unit in the corresponding target state according to the current state value of the targeted state field;

[0009] Generate status prompt information for the on-board unit according to the configuration progress, and perform voice broadcasting on the status prompt information.

[0010] In one embodiment, the generating of status prompt information for the onboard unit according to the configuration progress includes:

[0011] For each target state, the configuration progress of the on-board unit in the target state is used as the state prompt information for the on-board unit.

[0012] In one embodiment, the generating of status prompt information for the onboard unit according to the configuration progress includes:

[0013] For each target state, obtain the preset mode conditions under the target state; determine the current working mode of the on-board unit in the target state according to the configuration progress and preset mode conditions of the on-board unit in the target state; use the current working mode of the on-board unit in each target state as the status prompt information for the on-board unit.

[0014] In one of the embodiments, in response to a status self-check trigger operation for an on-board unit, multiple transaction information within a preset time period recorded in a transaction log of the on-board unit is obtained, and the multiple transaction information includes at least one of normal transaction information and abnormal transaction information; based on the multiple transaction information, the transaction amount of the last normal transaction is determined, and the transaction amount is voice broadcast.

[0015] In one of the embodiments, the total number of the multiple transaction information is determined; the target number of abnormal transaction information in the multiple transaction information is determined; based on the total number and the target number, fault prompt information for the on-board unit is generated, and the fault prompt information is voice broadcast.

[0016] In one embodiment, generating fault prompt information for the onboard unit according to the total number of times and the target number of times, and voice broadcasting the fault prompt information, includes:

[0017] According to the ratio between the target number of times and the total number of times, the false awakening probability value of the on-board unit is determined, and the false awakening probability value represents the probability of erroneously awakening the on-board unit for abnormal transactions; a preset false awakening fault threshold is obtained; according to the false awakening probability value and the false awakening fault threshold of the on-board unit, fault prompt information for the on-board unit is generated, and the fault prompt information is voice broadcast.

[0018] In one of the embodiments, in response to a status self-check trigger operation for an on-board unit, abnormal transaction information within a preset time period recorded in a transaction log of the on-board unit is obtained; based on the abnormal transaction information, fault prompt information for the on-board unit is generated, and the fault prompt information is voice broadcast.

[0019] In a second aspect, the present application also provides a monitoring device for a vehicle-mounted unit, comprising:

[0020] An acquisition module, configured to acquire, in response to a state monitoring trigger operation for an on-board unit, a plurality of state fields recorded in the on-board unit, wherein each of the plurality of state fields corresponds to a different target state;

[0021] A first determining module is used to determine, for each of the status fields, a current status value of the status field;

[0022] A second determination module, used to determine the configuration progress of the on-board unit in the corresponding target state according to the current state value of the state field;

[0023] The voice module is used to generate status prompt information for the vehicle-mounted unit according to the configuration progress, and to voice broadcast the status prompt information.

[0024] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0025] In response to a status monitoring trigger operation for an onboard unit, obtaining a plurality of status fields recorded in the onboard unit, wherein each of the plurality of status fields corresponds to a different target status;

[0026] For each of the status fields, determine the current status value of the status field;

[0027] Determining the configuration progress of the onboard unit in the corresponding target state according to the current state value of the targeted state field;

[0028] Generate status prompt information for the on-board unit according to the configuration progress, and perform voice broadcasting on the status prompt information.

[0029] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0030] In response to a status monitoring trigger operation for an onboard unit, obtaining a plurality of status fields recorded in the onboard unit, wherein each of the plurality of status fields corresponds to a different target status;

[0031] For each of the status fields, determine the current status value of the status field;

[0032] Determining the configuration progress of the onboard unit in the corresponding target state according to the current state value of the targeted state field;

[0033] Generate status prompt information for the on-board unit according to the configuration progress, and perform voice broadcasting on the status prompt information.

[0034] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0035] In response to a status monitoring trigger operation for an onboard unit, obtaining a plurality of status fields recorded in the onboard unit, wherein each of the plurality of status fields corresponds to a different target status;

[0036] For each of the status fields, determine the current status value of the status field;

[0037] Determining the configuration progress of the onboard unit in the corresponding target state according to the current state value of the targeted state field;

[0038] Generate status prompt information for the on-board unit according to the configuration progress, and perform voice broadcasting on the status prompt information.

[0039] The above-mentioned on-board unit monitoring method, device, computer equipment, computer-readable storage medium and computer program product obtain multiple status fields recorded in the on-board unit in response to the status monitoring trigger operation for the on-board unit, and the multiple status fields each correspond to a different target state; various status information of the OBU can be obtained in real time or on demand, solving the problem that the user cannot grasp the device status. For each of the status fields, the current status value of the targeted status field is determined; at this stage, the system not only obtains the status information, but also specifically determines the current values ​​of these states. This means that the user can obtain specific values ​​or status descriptions about the device status, which makes the diagnosis of the problem clearer and helps the user understand the problem. According to the current status value of the targeted status field, the configuration progress of the on-board unit in the corresponding target state is determined; this is crucial to guide the user to perform the next operation because it provides the specific steps or conditions required to complete the configuration. According to the configuration progress, the status prompt information for the on-board unit is generated, and the status prompt information is voice broadcast. Through voice broadcast, the user can safely obtain information even during driving without relying on visual feedback. This method is more humane and easy to understand, especially in a driving environment, which improves the user's experience and safety. And through intelligent monitoring and voice feedback mechanisms, the interaction between users and OBU devices is greatly improved, allowing users to independently diagnose and solve equipment problems, reducing the need to go to manual outlets, improving ease of use and driving safety, and also enhancing user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0041] FIG1 is a diagram showing an application environment of a monitoring method for a vehicle-mounted unit in one embodiment;

[0042] FIG2 is a schematic flow chart of a monitoring method of a vehicle-mounted unit in one embodiment;

[0043] FIG3 is a schematic flow chart of a monitoring method of an onboard unit in another embodiment;

[0044] FIG4 is a block diagram of a monitoring device of a vehicle-mounted unit in one embodiment;

[0045] FIG5 is a structural block diagram of a monitoring device of a vehicle-mounted unit in another embodiment;

[0046] FIG. 6 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0048] The monitoring method of the vehicle-mounted unit provided in the embodiment of the present application can be applied in the application environment shown in FIG. 1. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. The terminal 102 generates a monitoring request for the vehicle-mounted unit, and sends the monitoring request for the vehicle-mounted unit to the server 104, so that the server 104 generates status prompt information for the vehicle-mounted unit according to the configuration progress, and voice broadcasts the status prompt information. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart vehicle-mounted devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The head-mounted device can be a virtual reality (VR) device, an augmented reality (AR) device, smart glasses, etc. The server 104 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0049] In an exemplary embodiment, as shown in FIG2 , a method for monitoring a vehicle-mounted unit is provided, and the method is described by taking the application of the method to the server 104 in FIG1 as an example, and includes the following steps 202 to 208 . Among them:

[0050] Step 202 : in response to a status monitoring trigger operation for the onboard unit, a plurality of status fields recorded in the onboard unit are obtained, wherein the plurality of status fields respectively correspond to a different target status.

[0051] Among them, the on-board unit refers to the on-board electronic tag installed on the vehicle. It is part of the ETC system and is used for communication and data processing on the vehicle side. When the vehicle passes through the ETC lane, the OBU device communicates wirelessly with the roadside unit (RSU) to complete functions such as vehicle identity recognition and transaction fee deduction.

[0052] The status field refers to the data item or variable used to record different functional states within the OBU device. These status fields include but are not limited to installation status, power status, Bluetooth status, activation status, stop and enable status, transaction invocation status, fault status, etc. Each status field reflects the operation status of a specific aspect of the OBU device. For example, the status field is stored in the chip of the OBU device.

[0053] The target state refers to some key states that need to be monitored by the OBU device in advance. For example, installation state (the OBU device determines the installation status of the device by monitoring the anti-disassembly button status), power state (the OBU device determines the power status of the device by monitoring the battery voltage status), Bluetooth state (the OBU device determines the Bluetooth status of the device by monitoring the Bluetooth module open, closed and connected status), activation state (the OBU device determines the activation status of the device by monitoring the one-shot, two-shot and failure status), stop and enable state (the OBU device determines the start and stop status of the device by monitoring the plug-in and unplug status of the ESAM card module), wake-up transaction state (after the OBU device communicates with the RSU antenna in the exit lane, the OBU device will record the results of the communication transaction and trigger the voice transaction amount broadcast before the device completes the sleep state of this transaction), fault state (the OBU device determines the device fault status by monitoring several preset detectable fault states, such as Bluetooth module fault, ESAM module fault, etc.).

[0054] Specifically, the triggering of OBU devices is usually divided into two situations. The first situation is normal transaction wake-up: when the vehicle enters the ETC lane, the OBU device will be awakened by the roadside unit (RSU) through wireless communication signals to perform operations such as vehicle identification and transaction fee deduction. The second situation is that the user actively triggers self-test: the user can trigger the device self-test by manually operating the button on the OBU device (for example, double-clicking the main button on the device). At this time, the OBU device will check its own status and broadcast the current status information through voice, such as activation status, power status, fault status, etc., and can also broadcast the most recent transaction amount. When the status monitoring operation is triggered in the above way, the OBU device starts to execute the status monitoring program. Then the OBU device reads multiple status fields stored internally, which include but are not limited to installation status, power status, Bluetooth status, activation status, stop and enable status, transaction awakening status, fault status, etc. Each status field corresponds to a specific operating condition of the OBU device.

[0055] Step 204: for each status field, determine the current status value of the status field.

[0056] Among them, the status value refers to the specific value or status identifier of different status fields stored inside the OBU (on-board electronic tag) device, which reflects the current operating status of the OBU device. Specifically, the OBU device monitors multiple key states such as installation status, power status, Bluetooth status, activation status, stop and enable status, transaction invocation status and fault status, and determines the actual status of the device by monitoring the status value of the corresponding field in the device chip.

[0057] Specifically, when the OBU device is started or the user triggers the self-test function, the device begins to enter the status monitoring mode. The OBU device begins to monitor various status fields stored inside it one by one, including but not limited to installation status, power status, Bluetooth status, activation status, stop and enable status, transaction arousal status and fault status.

[0058] For each status field, the OBU device reads the status value corresponding to the field. For example, for the installation status, the device will check the status of the anti-tamper button; for the power status, it will read the specific value of the battery voltage; for the Bluetooth status, it will confirm whether the Bluetooth module is turned on and the connection status. These status values ​​will be used to evaluate whether the OBU device is installed correctly, whether there is enough power to support operation, whether the Bluetooth module is working properly, whether the device has been activated for transactions, etc.

[0059] Step 206: Determine the configuration progress of the onboard unit in the corresponding target state according to the current state value of the state field.

[0060] Among them, the configuration progress refers to the working condition or readiness of the OBU equipment in each target state. Specifically, the configuration progress can be understood as the completion degree of the OBU equipment in each monitoring state or whether it meets the expected functional requirements.

[0061] For example, the configuration progress in the installation state may refer to whether the OBU device is correctly installed on the vehicle windshield and whether the anti-tamper button is in an untouched state. The configuration progress in the power state may be whether the battery voltage is sufficient to maintain the normal operation of the device. The configuration progress in the Bluetooth state may indicate whether the Bluetooth module is turned on and can be connected to the user's mobile phone or other device. The configuration progress in the activation state indicates whether the OBU device is activated and ready for ETC transactions. The configuration progress in the stop and enable state involves whether the ESAM card module is correctly inserted and whether the OBU device is allowed to be used. The configuration progress in the transaction invocation state indicates whether the OBU device has successfully performed a transaction after passing through the RSU antenna and can broadcast the transaction amount. The configuration progress in the fault state means whether the OBU device has any known faults, such as Bluetooth module failure or ESAM module failure.

[0062] Specifically, according to the current status value of each status field, the configuration progress of the OBU device in the corresponding target state is evaluated. For example: if the anti-disassembly button is in normal state, the configuration progress in the installation state is completed. If the battery voltage is higher than the predetermined threshold, the configuration progress in the power state is normal. If the Bluetooth module is turned on and the connection status is good, the configuration progress in the Bluetooth state is completed. If the OBU device has completed the activation process, the configuration progress in the activation state is completed. If the ESAM card module is correctly inserted and the OBU device is enabled, the configuration progress in the stop-enable state is enabled. If the OBU device successfully completes the transaction with the RSU antenna and triggers the transaction amount broadcast before sleep, the configuration progress in the wake-up transaction state is completed. If no fault is detected, the configuration progress in the fault state is fault-free.

[0063] Step 208: Generate status prompt information for the vehicle-mounted unit according to the configuration progress, and voice broadcast the status prompt information.

[0064] Among them, the status prompt information refers to a descriptive information generated after evaluating the configuration progress of the OBU device in the corresponding target state according to the current status values ​​of different status fields in the OBU (on-board electronic tag) device. This information is intended to help users understand the current specific status of the OBU device, such as whether the device is installed correctly, whether the battery is sufficient, whether the Bluetooth connection is normal, whether the device is activated, whether it is allowed to be used, whether the transaction is successful, and whether there is a fault. It can be understood that the role of the status prompt information is to provide users with a clear and unambiguous status feedback, so that users can know the working status of the OBU device and take appropriate actions accordingly. For example, if the prompt information indicates that the device is too low in power, the user should charge it in time; if it prompts that the device is not activated, the user needs to follow the instructions to complete the activation process.

[0065] Specifically, first, based on the current status values ​​of different status fields in the OBU (on-board electronic tag) device, after evaluating the configuration progress of the OBU device in the corresponding target state, one or more status prompt messages are generated. This information will inform the user of the current overall status of the device and whether there are any problems that need to be paid attention to or solved. Finally, the generated status prompt information is conveyed to the user in the form of voice through the built-in voice broadcast system of the OBU device. This method allows users to understand the status of the OBU without distracting their driving attention, so as to make corresponding adjustments or processing in time.

[0066] In one of the embodiments, for each target state, the configuration progress of the onboard unit in the target state is used as the state prompt information for the onboard unit.

[0067] Specifically, for each monitoring state of the OBU (on-board electronic tag) device (such as installation state, power state, Bluetooth state, etc.), it is necessary to detect the current situation or progress of the OBU device in this state, and convert this detection result into a prompt message to inform the user of the specific situation of the OBU device in this state. For example, in the "installation state", the OBU device will detect its own installation status (usually judged by the state of an anti-disassembly button). If the device is installed correctly, the prompt message may be "OBU has been installed correctly", otherwise it may be "OBU is not installed correctly, please check". For another example, in the "power state", the device will monitor the voltage level of its battery to determine the power status. If the power is sufficient, the prompt message may be "OBU has sufficient power", if the power is low, the prompt message may be "OBU power is low, please charge in time".

[0068] Since the configuration progress of the on-board unit (OBU device) in each target state is directly used as the status prompt information, this method is concise and clear, and users can directly understand the current status of the device, such as whether the installation is correct, whether the power is sufficient, etc. It also directly reflects the completion degree of the device in a certain state, and users can understand the meaning of this information without additional knowledge.

[0069] In one of the embodiments, for each target state, a preset mode condition in the target state is obtained; based on the configuration progress of the on-board unit in the target state and the preset mode condition, the current working mode of the on-board unit in the target state is determined; and the current working mode of the on-board unit in each target state is used as status prompt information for the on-board unit.

[0070] Among them, the preset mode conditions refer to a series of standards or conditions set to determine whether the OBU device has reached the ideal or expected state under a certain target state. For example, for the "installation state", the preset mode conditions may include that the anti-tamper button is not touched and the device is installed in the correct position; for the "power state", the preset mode conditions may be that the battery voltage must be higher than a certain threshold; for the "Bluetooth state", the preset mode conditions are that the Bluetooth module must be turned on and the connection is normal, etc.

[0071] The current working mode refers to the working state or mode that the device is currently in, determined by the configuration progress of the OBU device in a certain target state and the preset mode conditions. That is, when the state value of the device meets the preset mode conditions, it will be in a normal working mode; conversely, if the state value does not meet the preset conditions, the device may be in a state mode that is faulty or needs adjustment. For example, for the "installation state", if the device detects that the anti-tamper button is not touched and the installation position is correct, the current working mode is "normal installation"; otherwise, the current working mode may be "incorrect installation". For the "power state", if the battery voltage is higher than the preset threshold, the current working mode is "sufficient power"; if it is lower than the threshold, the current working mode is "low power". For the "Bluetooth state", if the Bluetooth module is turned on and the connection is normal, the current working mode is "Bluetooth connection normal"; if the Bluetooth module is not turned on or there is a problem with the connection, the current working mode is "Bluetooth connection abnormal".

[0072] Specifically, first determine the target state to be monitored, such as installation state, power state, Bluetooth state, etc. For each target state, obtain the preset mode condition. For example, the preset mode condition corresponding to the installation state is that the anti-disassembly button is not touched and the device is installed in the correct position. The preset mode condition corresponding to the power state is that the battery voltage is higher than a certain threshold. The preset mode condition corresponding to the Bluetooth state is that the Bluetooth module is turned on and the connection is normal.

[0073] Then, according to the configuration progress of the OBU device in the target state, combined with the preset mode conditions, the current working mode is determined. For each target state, perform the following operations: Installation state: If the anti-disassembly button is not touched and the device is installed in the correct position, the current working mode is "normal installation"; otherwise, the current working mode is "incorrect installation". Power state: If the battery voltage is higher than the preset threshold, the current working mode is "sufficient power"; if it is lower than the threshold, the current working mode is "low power". Bluetooth state: If the Bluetooth module is turned on and the connection is normal, the current working mode is "Bluetooth connection normal"; if the Bluetooth module is not turned on or there is a problem with the connection, the current working mode is "Bluetooth connection abnormal".

[0074] Finally, the current working mode in each target state is used as the status prompt information. These prompt information will tell the user the working status of the OBU device in each target state, such as "normal installation", "sufficient power", "normal Bluetooth connection", etc.

[0075] Since not only the configuration progress is taken into account, but also the preset mode conditions are introduced, the determination of the current working mode is more accurate. This means that the device not only needs to reach a certain configuration progress, but also needs to meet certain conditions to be considered to be working normally. Through the combination of preset mode conditions and the current working mode, users can know more clearly whether the device is in an ideal operating state, such as "normal installation", "sufficient power", "normal Bluetooth connection", etc., so as to better guide user operations. And the preset mode conditions provide standards for the evaluation of device status, making the status evaluation more consistent, and no matter which user uses the device, they can get the same standard feedback.

[0076] In one of the embodiments, in response to a status self-check trigger operation for the on-board unit, multiple transaction information within a preset time period recorded in the transaction log of the on-board unit is obtained, and the multiple transaction information includes at least one of normal transaction information and abnormal transaction information; based on the multiple transaction information, the transaction amount of the last normal transaction is determined, and the transaction amount is voice broadcast.

[0077] Among them, the status self-check trigger operation refers to the action that the user actively triggers the OBU device to perform self-check. Specifically, the user can start this self-check program by double-clicking the main button on the device twice. Transaction information refers to the data record generated when the OBU device conducts transactions with the RSU (Road Side Unit) or other systems within a certain period of time. This information includes the details of each transaction, such as the time, location, and amount of the transaction. The preset time period refers to a specific time interval, and the transactions occurring within this interval will be recorded by the OBU device. This time period can be set according to actual needs, such as the last week, month, or longer period. Normal transaction information refers to the transaction record after the communication transaction with the RSU is successfully completed when the OBU device is working normally. These transactions are usually valid and meet the expected toll deduction. Abnormal transaction information refers to the record when an abnormal situation occurs during the transaction process, such as transaction failure, amount discrepancy, device status error, etc. The transaction amount refers to the specific fee amount involved in each transaction, that is, the toll amount deducted when the user uses the ETC system to pass through the toll station.

[0078] Specifically, first, the user triggers the status self-check function of the on-board unit (OBU device) through a specific operation (for example, double-clicking the main button of the OBU device). The OBU device begins to retrieve multiple transaction information recorded in its transaction log within a preset time period. These transaction information contain at least one of normal transaction information or abnormal transaction information. The preset time period can be set according to actual conditions, such as all transaction records in the recent period. Then, normal transaction information is filtered out from the multiple transaction information obtained. Normal transaction information refers to those records of successful transactions, which indicate that the OBU device is in a normal working state during the transaction, the transaction process is smooth, and the fee deduction is correct. Next, the record of the last successful transaction is found in the filtered normal transaction information, and the transaction amount of the transaction is extracted from it. The determined transaction amount of the last normal transaction is converted into voice broadcast information. This information will inform the user of the specific amount of the last successful transaction. Finally, the generated voice broadcast information is played to the user through the built-in voice broadcast system of the OBU device. In this way, the user can hear the information about the last normal transaction amount, thereby confirming whether the transaction function of the OBU device is normal.

[0079] Since the user is informed of the specific amount of the last normal transaction through voice broadcast, the user does not need to rely on visual viewing of transaction details, especially during driving, which not only improves the user experience but also increases driving safety. In addition, the user only needs to perform simple operations (such as double-clicking the button) to start the self-test program and quickly understand the status of the OBU device without complicated steps.

[0080] In one of the embodiments, the total number of multiple transaction information is determined; the target number of abnormal transaction information in the multiple transaction information is determined; based on the total number and the target number, fault prompt information for the vehicle-mounted unit is generated, and the fault prompt information is voice broadcast.

[0081] Among them, fault prompt information refers to a mechanism that analyzes the performance of the OBU device in multiple transactions (including normal transactions and abnormal transactions), calculates the total number of transactions and the number of abnormal transactions, and then uses these two values ​​to determine whether there is a potential problem with the device, and informs the user of this judgment result in the form of voice. In other words, the fault prompt information is actually a notification to inform the user that the OBU device may have a fault, and this notification is based on the analysis of the device transaction log. Understandably, if the OBU device is frequently awakened and abnormalities occur in some transactions (such as failed or incomplete transactions), the number of these abnormal transactions will be counted and compared with the total number of transactions. If the proportion of abnormal transactions is high, it may mean that there is a problem with the device. At this time, a voice broadcast prompt message will be generated to tell the user that the OBU device may have a fault and needs to be checked or repaired.

[0082] Specifically, the OBU device will first record each transaction information, including normal transactions and abnormal transactions, and this information will be stored inside the device as a transaction log. By analyzing the transaction log, the number of all transaction records within a period of time or under specific conditions is counted to determine the total number of multiple transaction information. Then continue to analyze the transaction log, filter out abnormal transaction records, such as transaction failures, unfinished transactions or other unexpected situations, and count the number of these abnormal transactions to determine the target number of abnormal transaction information in multiple transaction information. Next, based on the total number of transactions and the target number of abnormal transactions, the working status of the device is evaluated. If the proportion of abnormal transactions exceeds the preset threshold or reaches a certain standard, a fault prompt message for the on-board unit is generated, which may include the specific situation of the abnormal transaction, recommended treatment measures, etc. Finally, the generated fault prompt message is converted into a voice signal through the built-in voice module of the OBU device and broadcast to the outside, so that the driver can understand the fault prompt information of the on-board unit through hearing, so as to take corresponding actions in time.

[0083] Since users can learn the details of the most recent transaction through voice broadcast, they can obtain important information such as the transaction amount even if they miss the information on the LED screen at the lane end, which increases transparency and makes it convenient for users to check their accounts at any time. In addition, through the user self-detection and feedback mechanism, the need for users to go to the service center for equipment detection is reduced, the cost of maintenance and service is reduced, and service efficiency is also improved. When the proportion of abnormal transactions detected exceeds the preset threshold, a fault prompt message can be generated immediately to remind users that the equipment may have a fault and needs to be inspected or maintained, avoiding inconvenience or additional costs caused by equipment problems.

[0084] In one of the embodiments, a false awakening probability value of the on-board unit is determined based on the ratio between the target number of times and the total number of times, and the false awakening probability value represents the probability of falsely awakening the on-board unit for abnormal transactions; a pre-set false awakening fault threshold is obtained; and fault prompt information for the on-board unit is generated based on the false awakening probability value and the false awakening fault threshold of the on-board unit, and the fault prompt information is voice broadcast.

[0085] Among them, the false awakening probability value refers to the probability that the OBU device is falsely awakened to perform abnormal transactions within a certain period of time or under specific conditions. This probability value is determined by analyzing the transaction log and counting the ratio between the number of abnormal transactions (target number) in all transaction records and the total number of transactions. If the false awakening probability value is high, it means that the OBU device may have frequent false awakening problems, which may cause the device battery to be quickly exhausted or other abnormal operating conditions.

[0086] The false wake-up fault threshold refers to a pre-set value used to determine whether the OBU device has a frequent false wake-up problem. When the calculated false wake-up probability value exceeds this threshold, it means that the false wake-up frequency of the device has reached a level that requires attention. At this time, the system will generate a fault prompt message and convert this message into a voice signal through the built-in voice module of the OBU device and broadcast it to the driver so that the user can know the status of the device in time and take appropriate measures to deal with it.

[0087] Specifically, the OBU device first records the log status and wake-up times of each transaction. This information can be used to analyze the operation of the device, including normal wake-up and abnormal wake-up. By analyzing the transaction log, the ratio between the target number of abnormal transactions and the total number of transactions is calculated. This ratio is the false wake-up probability value, which represents the probability of falsely waking up the OBU device for abnormal transactions.

[0088] Then, a preset false wakeup fault threshold is obtained, which is a standard value used to determine whether the probability of false wakeup has reached a level that requires attention. The calculated false wakeup probability value is compared with the preset false wakeup fault threshold. If the false wakeup probability value exceeds the threshold, it means that the device has frequent false wakeup problems.

[0089] Finally, once the false wake-up probability value exceeds the threshold, a fault prompt message will be generated, which will inform the user that the device has frequent false wake-up problems. The generated fault prompt message is converted into a voice signal through the voice module in the OBU device and broadcast to the user, so that the user can understand the status of the device in time and take corresponding measures accordingly.

[0090] By recording the transaction log status and wake-up times of the OBU device, the operating status of the device can be monitored in real time, abnormal wake-up situations of the device can be discovered in time, and the rapid exhaustion of power or other potential problems that may be caused by this can be prevented. And by counting the ratio of abnormal transaction times to total transaction times, the probability of false wake-up can be quantified, making the device status assessment more objective and accurate, which helps users understand the actual operating status of the device. In addition, the false wake-up fault threshold is introduced as a standard. When the false wake-up probability value exceeds the threshold, it indicates that the device may have the problem of frequent false wake-up, thereby starting the fault warning mechanism and notifying the user in time.

[0091] In one of the embodiments, in response to a status self-check trigger operation for the on-board unit, abnormal transaction information within a preset time period recorded in a transaction log of the on-board unit is obtained; based on the abnormal transaction information, fault prompt information for the on-board unit is generated, and the fault prompt information is voice broadcast.

[0092] Among them, the transaction log refers to a series of transaction data and events recorded when the OBU (on-board electronic tag) communicates with the RSU (roadside unit) or other related equipment on the highway. These transaction data and events include but are not limited to the time, location, transaction amount, whether the transaction is successful, and the status information of the OBU device. The transaction log is very important for tracking and analyzing the use of OBU devices. It can help determine whether the device has abnormal transaction behavior, such as transaction failure, abnormal transaction amount, etc., as well as the frequency and pattern of these abnormalities.

[0093] Specifically, users can first start the self-check function of the OBU (on-board unit) by actively triggering the device button (for example, double-clicking the main button twice). This operation is to allow users to check the status of the OBU device before getting on or off the highway to ensure that the device is working properly and avoid problems such as going into the wrong lane and causing congestion due to abnormal ETC.

[0094] Then once the status self-check is triggered, the OBU device will retrieve abnormal transaction records within the preset time period from its internally stored transaction log. These abnormal transaction information may include records of failed transactions, records of abnormal transaction amounts, etc. The transaction log records all important information when the OBU device communicates with the RSU (roadside unit) or other related equipment on the highway.

[0095] Next, based on the abnormal transaction information obtained, the OBU device will generate corresponding fault prompt information. This information is intended to provide users with specific guidance on the current status of the device, including existing problems and their possible causes, to help users quickly locate and solve problems.

[0096] Finally, the OBU device or a third-party device connected to the OBU device via Bluetooth, such as the user's terminal, broadcasts the generated fault prompt information to the user in the form of voice. This method not only makes the information transmission more intuitive and easy to understand, but also improves the user experience, especially during driving, when the user can understand the status of the OBU without distractingly checking the screen.

[0097] In one of the embodiments, when the OBU device is plugged into or unplugged from the charging port, the current power status of the OBU device will be immediately prompted.

[0098] In one of the embodiments, the Bluetooth of the OBU device will be automatically turned off in the following three situations.

[0099] The first case: When the Bluetooth of the OBU device is turned on for a preset period of time and has not been successfully connected to other devices, the Bluetooth of the OBU device is automatically turned off.

[0100] The second situation: After the Bluetooth of the OBU device is successfully connected to other devices, if there is no data interaction within the preset time, the Bluetooth of the OBU device is automatically turned off

[0101] The third situation: After the OBU device is activated, the Bluetooth of the OBU device is automatically turned off.

[0102] In an exemplary embodiment, as shown in FIG4 , steps 302 to 312 are included. Among them:

[0103] Step 302, in response to a status monitoring trigger operation for the vehicle-mounted unit, obtaining multiple status fields recorded in the vehicle-mounted unit, each of the multiple status fields corresponding to a different target status;

[0104] Step 304, for each status field, determine the current status value of the status field;

[0105] Step 306, determining the configuration progress of the onboard unit in the corresponding target state according to the current state value of the state field;

[0106] Step 308, for each target state, the configuration progress of the onboard unit in the target state is used as the state prompt information for the onboard unit, and the state prompt information is voice broadcasted;

[0107] Or for each target state, obtaining a preset mode condition under the target state; determining the current working mode of the onboard unit under the target state according to the configuration progress of the onboard unit under the target state and the preset mode condition; using the current working mode of the onboard unit under each target state as the state prompt information for the onboard unit, and voice broadcasting the state prompt information;

[0108] Step 310, in response to the self-check triggering operation for the on-board unit, obtaining multiple transaction information within a preset time period recorded in the transaction log of the on-board unit, the multiple transaction information including at least one of normal transaction information and abnormal transaction information; determining the transaction amount of the last normal transaction according to the multiple transaction information, and announcing the transaction amount by voice;

[0109] Step 312, determine the total number of multiple transaction information; determine the target number of abnormal transaction information in the multiple transaction information; determine the false awakening probability value of the on-board unit according to the ratio between the target number and the total number, the false awakening probability value represents the probability of falsely awakening the on-board unit for abnormal transaction; obtain a preset false awakening fault threshold; generate fault prompt information for the on-board unit according to the false awakening probability value and the false awakening fault threshold of the on-board unit, and voice broadcast the fault prompt information.

[0110] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0111] Based on the same inventive concept, the embodiment of the present application also provides a vehicle-mounted unit monitoring device for implementing the vehicle-mounted unit monitoring method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the embodiments of the monitoring device for one or more vehicle-mounted units provided below can refer to the limitations of the vehicle-mounted unit monitoring method above, and will not be repeated here.

[0112] In an exemplary embodiment, as shown in FIG. 4 , a monitoring device 400 for a vehicle-mounted unit is provided, comprising: an acquisition module 402 , a first determination module 404 , a second determination module 406 , and a voice module 408 , wherein:

[0113] An acquisition module 402, for acquiring, in response to a state monitoring trigger operation for the vehicle-mounted unit, a plurality of state fields recorded in the vehicle-mounted unit, wherein each of the plurality of state fields corresponds to a different target state;

[0114] A first determining module 404 is used to determine, for each state field, a current state value of the state field;

[0115] A second determination module 406, for determining the configuration progress of the onboard unit in the corresponding target state according to the current state value of the state field;

[0116] The voice module 408 is used to generate status prompt information for the vehicle-mounted unit according to the configuration progress, and to voice broadcast the status prompt information.

[0117] In one embodiment, the voice module 408 is used to use, for each target state, the configuration progress of the onboard unit in the target state as the state prompt information for the onboard unit.

[0118] In one of the embodiments, the voice module 408 is used to obtain, for each target state, the preset mode conditions under the target state; determine the current working mode of the vehicle-mounted unit in the target state according to the configuration progress and preset mode conditions of the vehicle-mounted unit in the target state; and use the current working mode of the vehicle-mounted unit in each target state as status prompt information for the vehicle-mounted unit.

[0119] In one of the embodiments, the monitoring device 400 of the vehicle-mounted unit also includes a first voice module 410, which is used to obtain multiple transaction information within a preset time period recorded in the transaction log of the vehicle-mounted unit in response to a status self-check trigger operation for the vehicle-mounted unit, and the multiple transaction information includes at least one of normal transaction information and abnormal transaction information; based on the multiple transaction information, determine the transaction amount of the last normal transaction, and voice broadcast the transaction amount.

[0120] In one embodiment, the monitoring device 400 of the vehicle-mounted unit also includes a second voice module 412, which is used to determine the total number of multiple transaction information; determine the target number of abnormal transaction information in the multiple transaction information; generate fault prompt information for the vehicle-mounted unit based on the total number and the target number, and voice broadcast the fault prompt information.

[0121] In one of the embodiments, the monitoring device 400 of the on-board unit also includes a second voice module 412, which is used to determine the false wake-up probability value of the on-board unit based on the ratio between the target number of times and the total number of times, the false wake-up probability value representing the probability of falsely waking up the on-board unit for abnormal transactions; obtain a pre-set false wake-up fault threshold; generate fault prompt information for the on-board unit based on the false wake-up probability value and the false wake-up fault threshold of the on-board unit, and voice broadcast the fault prompt information.

[0122] In one of the embodiments, the monitoring device 400 of the vehicle-mounted unit also includes a third voice module 414, which is used to respond to a status self-check trigger operation for the vehicle-mounted unit, obtain abnormal transaction information within a preset time period recorded in the transaction log of the vehicle-mounted unit; generate fault prompt information for the vehicle-mounted unit based on the abnormal transaction information, and voice broadcast the fault prompt information.

[0123] In another embodiment, as shown in FIG5 , FIG5 is a structural block diagram of a monitoring device of a vehicle-mounted unit in another embodiment, comprising: an acquisition module 402, a first determination module 404, a second determination module 406, and a voice module 408. The monitoring device 400 of the vehicle-mounted unit further comprises a first voice module 410, a second voice module 412, and a third voice module 414.

[0124] The first voice module 410 is used to respond to the status self-check trigger operation for the vehicle-mounted unit, obtain multiple transaction information within a preset time period recorded in the transaction log of the vehicle-mounted unit, and the multiple transaction information includes at least one of normal transaction information and abnormal transaction information; determine the transaction amount of the last normal transaction based on the multiple transaction information, and voice broadcast the transaction amount.

[0125] The second voice module 412 is used to determine the total number of multiple transaction information; determine the target number of abnormal transaction information in the multiple transaction information; determine the false awakening probability value of the on-board unit according to the ratio between the target number and the total number, the false awakening probability value represents the probability of falsely awakening the on-board unit for abnormal transaction; obtain a pre-set false awakening fault threshold; generate fault prompt information for the on-board unit according to the false awakening probability value and the false awakening fault threshold of the on-board unit, and voice broadcast the fault prompt information.

[0126] The third voice module 414 is used to respond to the status self-check trigger operation for the vehicle-mounted unit, obtain abnormal transaction information within a preset time period recorded in the transaction log of the vehicle-mounted unit; generate fault prompt information for the vehicle-mounted unit based on the abnormal transaction information, and voice broadcast the fault prompt information.

[0127] Each module in the monitoring device of the above-mentioned vehicle-mounted unit can be implemented in whole or in part by software, hardware or a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each of the above modules.

[0128] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG6. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data related to the monitoring of the vehicle-mounted unit. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for monitoring a vehicle-mounted unit is implemented.

[0129] Those skilled in the art will understand that the structure shown in FIG. 6 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0130] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0131] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0132] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0133] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0134] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0135] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0136] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A monitoring method for a vehicle-mounted unit, characterized in that: The method comprises: In response to a status monitoring trigger operation for an onboard unit, obtaining a plurality of status fields recorded in the onboard unit, wherein each of the plurality of status fields corresponds to a different target status; For each of the status fields, determine the current status value of the status field; Determining the configuration progress of the onboard unit in the corresponding target state according to the current state value of the state field, wherein the configuration progress is the completion degree of the onboard unit in each target state; For each target state, the preset mode conditions under the target state are obtained, and the preset mode conditions are a series of standards or conditions set for determining whether the on-board unit has reached an ideal or expected state under a certain target state; according to the configuration progress of the on-board unit under the target state and the preset mode conditions, the current working mode of the on-board unit under the target state is determined; the current working mode of the on-board unit under each target state is used as the status prompt information for the on-board unit, and the status prompt information is voice broadcast.

2. The method according to claim 1, characterized in that The method further comprises: In response to a status self-check triggering operation for the on-board unit, obtaining multiple transaction information within a preset time period recorded in a transaction log of the on-board unit, wherein the multiple transaction information includes at least one of normal transaction information and abnormal transaction information; The transaction amount of the last normal transaction is determined based on the multiple transaction information, and the transaction amount is announced by voice.

3. The method according to claim 2, characterized in that The method further comprises: Determine the total number of the multiple transaction information; Determine a target number of abnormal transaction information among the multiple transaction information; According to the total number of times and the target number of times, fault prompt information for the on-board unit is generated, and the fault prompt information is voice broadcasted.

4. The method according to claim 3, characterized in that The generating, according to the total number of times and the target number of times, fault prompt information for the onboard unit and voice broadcasting the fault prompt information comprises: Determining a false awakening probability value of the onboard unit according to a ratio between the target number of times and the total number of times, wherein the false awakening probability value represents a probability of falsely awakening the onboard unit for performing an abnormal transaction; Get the preset false wakeup fault threshold; According to the false awakening probability value and the false awakening fault threshold value of the on-board unit, fault prompt information for the on-board unit is generated, and the fault prompt information is voice broadcasted.

5. The method according to claim 1, characterized in that: The method further comprises: In response to a status self-check triggering operation for the on-board unit, obtaining abnormal transaction information within a preset time period recorded in a transaction log of the on-board unit; According to the abnormal transaction information, fault prompt information for the on-board unit is generated, and the fault prompt information is voice broadcasted.

6. A monitoring device for a vehicle-mounted unit, characterized in that: The device comprises: An acquisition module, configured to acquire, in response to a state monitoring trigger operation for an on-board unit, a plurality of state fields recorded in the on-board unit, wherein each of the plurality of state fields corresponds to a different target state; A first determining module is used to determine, for each of the status fields, a current status value of the status field; A second determination module is used to determine the configuration progress of the on-board unit in the corresponding target state according to the current state value of the state field, wherein the configuration progress is the completion degree of the on-board unit in each target state; The voice module is used to obtain, for each target state, the preset mode conditions under the target state, wherein the preset mode conditions are a series of standards or conditions set for determining whether the on-board unit has reached an ideal or expected state under a certain target state; determine the current working mode of the on-board unit under the target state according to the configuration progress of the on-board unit under the target state and the preset mode conditions; use the current working mode of the on-board unit under each target state as the status prompt information for the on-board unit, and voice broadcast the status prompt information.

7. The device according to claim 6, characterized in that The monitoring device of the vehicle-mounted unit also includes a first voice module, which is used to respond to a status self-check trigger operation for the vehicle-mounted unit, obtain multiple transaction information within a preset time period recorded in the transaction log of the vehicle-mounted unit, and the multiple transaction information includes at least one of normal transaction information and abnormal transaction information; determine the transaction amount of the last normal transaction based on the multiple transaction information, and voice broadcast the transaction amount.

8. The device according to claim 6, characterized in that The monitoring device of the vehicle-mounted unit also includes a second voice module, which is used to determine the total number of multiple transaction information; determine the target number of abnormal transaction information in the multiple transaction information; generate fault prompt information for the vehicle-mounted unit based on the total number and the target number, and voice broadcast the fault prompt information.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images