A control method and device for a shared vehicle and a shared vehicle

By obtaining the status information of shared vehicle components to calculate health scores for fault prediction, the problem that shared vehicles cannot prevent failure is solved, and early warning and precise control of faults are achieved to prevent user injury and vehicle damage.

CN116142363BActive Publication Date: 2025-08-22HANHAI INFORMATION TECH SHANGHAI
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202211591650.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-12-12
Publication Date
2025-08-22
Estimated Expiration
2042-12-12

AI Technical Summary

Technical Problem

The existing shared vehicle fault detection technology cannot prevent the occurrence of failures, resulting in the inability to use shared vehicles and even affecting user safety.

Method used

By obtaining the status information of preset components in the shared vehicle, calculating health scores and predicting faults, early warning and preventing shared vehicle failures.

Benefits of technology

It realizes an early warning of the upcoming failures of shared vehicles to prevent users from being injured by personal injury and irreversible damage to shared vehicles.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116142363B_ABST
    Figure CN116142363B_ABST
Patent Text Reader

Abstract

The present disclosure provides a control method and device for a shared vehicle, and a shared vehicle. The method includes: obtaining status information of at least one preset component in the shared vehicle; determining the health of the shared vehicle based on the status information; and performing fault prediction on the shared vehicle based on the health.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the technical field of shared vehicle control, and more specifically, to a control method and device for a shared vehicle and a shared vehicle. Background Art

[0002] Currently, shared vehicles have become an emerging mode of transportation in cities, effectively meeting the travel needs of urban residents. Existing shared vehicles include ordinary bicycles powered by users, as well as electric bicycles with power-assisted motors.

[0003] If a shared vehicle breaks down, it will make the shared vehicle unusable and even affect the safety of users who are using the shared vehicle.

[0004] Existing technical solutions are all about detecting and handling faults that have already occurred in shared vehicles, and are unable to prevent them from happening again. Moreover, these faults that have already occurred often have already caused serious consequences, even causing adverse consequences for the shared vehicles and the personal safety of users. Summary of the Invention

[0005] One purpose of the embodiments of the present disclosure is to provide a new technical solution for fault prediction of shared vehicles.

[0006] According to a first aspect of the present disclosure, a method for controlling a shared vehicle is provided, comprising:

[0007] Obtaining status information of at least one preset component in the shared vehicle;

[0008] determining a health score of the shared vehicle according to the status information, where the health score is a score indicating the health of the shared vehicle;

[0009] Fault prediction is performed on the shared vehicle based on the health score.

[0010] Optionally, the preset components include at least one of a network communication module, a Bluetooth module, a charging module, a small battery, a positioning module, an RS485 communication module, a CAN communication module, a large battery, an electronic control, a load sensor, and a helmet lock; and determining the health of the shared vehicle based on the status information includes:

[0011] Determining a status score corresponding to the status information;

[0012] According to the preset weight of the status information, a weight calculation process is performed on the status score corresponding to the status information to obtain a health score representing the health level of the shared vehicle.

[0013] Optionally, the method further includes:

[0014] Acquire a feature value representing a scene feature of the scene in which the shared vehicle is located;

[0015] Obtaining a scene score corresponding to the state information according to a feature value of a scene feature that affects the state information;

[0016] A health score of the shared vehicle is also determined based on the scenario score.

[0017] Optionally, determining the health score of the shared vehicle according to the scenario score further includes:

[0018] Determine a product of a state score and a scene score corresponding to the state information;

[0019] According to the weight, weight calculation processing is performed on the product corresponding to the status information to obtain the health score.

[0020] Optionally, the performing fault prediction on the shared vehicle according to the health score includes:

[0021] comparing the health score with a preset score range;

[0022] Determine whether a fault prediction alarm event occurs based on the comparison result;

[0023] When the fault prediction alarm event occurs, the result of the shared vehicle predicted fault is reported to the server.

[0024] Optionally, determining whether a fault prediction alarm event occurs according to the comparison result includes:

[0025] If the comparison result is that the health score is not within the preset score range, determining whether the first number is greater than or equal to a preset first number threshold; wherein the first number is the number of times it is determined that the comparison result is that the health score is not within the preset score range;

[0026] When the first number is greater than or equal to the first number threshold, it is determined that the fault prediction alarm event occurs.

[0027] Optionally, the method includes:

[0028] Determine whether the second number is greater than or equal to a preset second number threshold; wherein the second number is the number of consecutive times that the comparison result shows that the health score is within the preset score range;

[0029] When the second number of times is greater than or equal to the second number threshold, the first number of times is reset.

[0030] Optionally, the method further includes:

[0031] When the fault prediction alarm event occurs, determining the fault prediction type of the shared vehicle according to the status information;

[0032] Report the fault prediction type to the server.

[0033] According to a second aspect of the present disclosure, there is provided a control device for a shared vehicle, comprising:

[0034] A status information acquisition module, configured to acquire status information of at least one preset component in the shared vehicle;

[0035] a health score determination module, configured to determine a health score of the shared vehicle based on the status information, the health score being a score indicating the health level of the shared vehicle;

[0036] A fault prediction module is used to predict faults of the shared vehicle based on the health score.

[0037] According to a third aspect of the present disclosure, a shared vehicle is provided, comprising the control device for the shared vehicle according to the second aspect of the present disclosure; or,

[0038] The shared vehicle includes a memory and a processor, the memory is used to store a computer program, and the processor is used to control the shared vehicle to execute the method described in the first aspect of the present disclosure when executing the computer program.

[0039] Through the embodiments of the present disclosure, the health score of a shared vehicle is determined based on the status information of at least one component in the shared vehicle, and then faults of the shared vehicle are predicted based on the health score. This allows for early warning and prevention of impending faults in the shared vehicle, and allows for precise control before the shared vehicle actually fails, thereby preventing personal injury to users and preventing irreversible damage to the shared vehicle due to further use by users.

[0040] Further features and advantages of the present invention will become apparent from the following detailed description of exemplary embodiments of the present invention with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.

[0042] Figure 1 1 is a schematic diagram of the structure of a shared vehicle system capable of implementing the shared vehicle control method according to an embodiment of the present invention;

[0043] Figure 2is a flow chart of a method for controlling a shared vehicle according to one embodiment;

[0044] Figure 3 is a block diagram of a vehicle return processing device according to one embodiment;

[0045] Figure 4 is a block diagram of a shared vehicle according to one embodiment. DETAILED DESCRIPTION

[0046] Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present invention.

[0047] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.

[0048] Technologies, methods and equipment known to persons of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, such technologies, methods and equipment should be considered part of the specification.

[0049] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0050] It should be noted that like reference numerals and letters refer to like items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0051] <Hardware Configuration>

[0052] Figure 1 1 is a schematic diagram of the structure of a shared vehicle system 100 that can be used to implement the shared vehicle control method of the embodiment of the present disclosure. The shared vehicle system 100 can be applied as a whole to the control scenario of shared vehicles.

[0053] like Figure 1 As shown, the shared vehicle system 100 includes a server 1000 , a user terminal 2000 , a shared vehicle 3000 , and a network 4000 .

[0054] The server 1000 provides a business point for processing, database, and communication facilities. The server 1000 can be a monolithic server, a distributed server across multiple computers, a computer data center, a cloud server, or a server cluster deployed in the cloud. The server can be of various types, such as, but not limited to, a web server, a news server, a mail server, a message server, an advertising server, a file server, an application server, an interactive server, a database server, or a proxy server. In some embodiments, each server can include hardware, software, or an embedded logic component or a combination of two or more such components for performing the appropriate functions supported or implemented by the server. For example, the server can be a blade server, a cloud server, etc., or it can be a server group consisting of multiple servers, which can include one or more of the above-mentioned types of servers, etc.

[0055] In one embodiment, the server 1000 may be configured as follows: Figure 1 As shown, it includes a processor 1100 , a memory 1200 , an interface device 1300 , a communication device 1400 , a display device 1500 , and an input device 1600 .

[0056] The processor 1100 is used to execute a computer program, which can be written using an instruction set of an architecture such as x86, Arm, RISC, MIPS, or SSE. The memory 1200 includes, for example, ROM (read-only memory), RAM (random access memory), and non-volatile memory such as a hard disk. The interface device 1300 includes, for example, various bus interfaces, such as a serial bus interface (including a USB interface) and a parallel bus interface. The communication device 1400 is capable of wired or wireless communication. The display device 1500 is, for example, a liquid crystal display, an LED display, a touch screen display, etc. The input device 1600 may include, for example, a touch screen, a keyboard, etc.

[0057] In this embodiment, the memory 1200 of the server 1000 is used to store a computer program that controls the processor 1100 to execute the vehicle return processing method according to an embodiment of the present invention. A skilled person can design this computer program based on the disclosed solution. How this computer program controls the processor's operations is well known in the art and will not be described in detail here.

[0058] Despite Figure 1 , multiple devices of the server 1000 are shown; however, the present invention may only involve some of the devices, for example, the server 1000 only involves the memory 1200 , the processor 1100 and the communication device 1400 .

[0059] In this embodiment, the user terminal 2000 is, for example, a mobile phone, a portable computer, a tablet computer, a PDA, a wearable device, etc.

[0060] The user terminal 2000 is installed with a car-using application client, so as to achieve the purpose of using a shared car by operating the car-using application client.

[0061] like Figure 1 As shown, the user terminal 2000 may include a processor 2100, a memory 2200, an interface device 2300, a communication device 2400, a display device 2500, an input device 2600, a speaker 2700, a microphone 2800, and the like.

[0062] The processor 2100 is used to execute a computer program, which can be written using an instruction set of an architecture such as x86, Arm, RISC, MIPS, or SSE. The memory 2200 includes, for example, ROM (read-only memory), RAM (random access memory), and non-volatile memory such as a hard disk. The interface device 2300 includes, for example, a USB interface, a headphone jack, and the like. The communication device 2400 is capable of wired or wireless communication. The communication device 2400 may include at least one short-range communication module, such as any module that performs short-range wireless communication based on a short-range wireless communication protocol such as Hilink protocol, WiFi (IEEE 802.11 protocol), Mesh, Bluetooth, ZigBee, Thread, Z-Wave, NFC, UWB, or LiFi. The communication device 2400 may also include a long-range communication module, such as any module that performs WLAN, GPRS, or 2G / 3G / 4G / 5G long-range communication. The display device 2500 is, for example, an LCD display, a touch screen display, and the like. The input device 2600 may include, for example, a touch screen, a keyboard, and the like. The user terminal 2000 can output audio signals through the speaker 2700 and collect audio signals through the microphone 2800 .

[0063] In this embodiment, the memory 2200 of the user terminal 2000 is used to store a computer program that controls the processor 2100 to execute a shared vehicle control method, including, for example, obtaining a unique identifier for the shared vehicle 3000, generating an unlock request for the specific shared vehicle and sending it to a server; and performing bill settlement based on the fee settlement notification sent by the server. A skilled person can design a computer program based on the disclosed solution. How a computer program controls the processor's operations is well known in the art and will not be described in detail here.

[0064] like Figure 1As shown, shared vehicle 3000 may include a processor 3100, memory 3200, interface device 3300, communication device 3400, output device 3500, and input device 3600, among others. Processor 3100 is used to execute computer programs, which may be written using an instruction set such as an x86, Arm, RISC, MIPS, or SSE architecture. Memory 3200 may include, for example, ROM (read-only memory), RAM (random access memory), and non-volatile memory such as a hard drive. Interface device 3300 may include, for example, a USB interface and a headphone jack. Communication device 3400 may include at least one communication module, such as one capable of wired or wireless communication, or short-range and long-range communication. Output device 3500 may be, for example, a device that outputs signals, a display device such as an LCD screen or a touchscreen display, or a speaker for outputting voice information. Input device 3600 may include, for example, a touchscreen or other touch device, buttons, a sound sensor such as a microphone, a pressure sensor or other pressure sensor, and so on.

[0065] The shared vehicle 3000 can be any type of shared vehicle, such as a bicycle, an electric bicycle, an electric motorcycle, a tricycle, a four-wheel vehicle, etc., and is not limited here.

[0066] In this embodiment, the shared vehicle 3000 can report its own location information to the server 1000 .

[0067] In this embodiment, the memory 3200 of the shared vehicle 3000 is used to store a computer program that controls the processor 3100 to execute the vehicle return processing method according to any embodiment of the present invention. A skilled person can design such a computer program based on the disclosed solution. How such a computer program controls the processor is well known in the art and will not be described in detail here.

[0068] The network 4000 can be a wireless communication network or a wired communication network, and can be a local area network or a wide area network. Figure 1 In the shared vehicle system 100 shown, the shared vehicle 3000 and the server 1000, and the user terminal 2000 and the server 1000 can communicate via a network 4000. The network 4000 on which the shared vehicle 3000 and the server 1000, and the user terminal 2000 and the server 1000 communicate can be the same or different.

[0069] It should be understood that although Figure 1Only one server 1000 , user terminal 2000 , and shared vehicle 3000 are shown, but this does not limit the number of each. The shared vehicle system 100 may include multiple servers 1000 , multiple user terminals 2000 , multiple shared vehicles 3000 , etc.

[0070] Figure 1 The illustrated shared vehicle system 100 is illustrative only and is in no way intended to limit the invention, its application, or uses.

[0071] <Method Example>

[0072] Figure 2 The flow chart of the control method of a shared vehicle according to an embodiment is shown. The method steps of this embodiment are implemented by a shared vehicle, for example, Figure 1 3000 shared vehicles are implemented.

[0073] like Figure 2 As shown, the control method of the shared vehicle in this embodiment may include the following steps S2100 to S2300:

[0074] Step S2100: Obtain status information of at least one preset component in the shared vehicle.

[0075] The preset components in this embodiment may be pre-set based on the application scenario or specific requirements. For example, the at least one preset component may include at least one of a network communication module, a Bluetooth module, a charging module, a small battery, a positioning module, an RS485 communication module, a CAN communication module, a large battery, an electronic control, a load sensor, and a helmet lock.

[0076] In an embodiment where the preset component includes a network communication module, the status information of the network communication module may include physical link connectivity, signal strength information, number of network communication successes, number of network communication failures, and number of network reinitializations.

[0077] In an embodiment where the preset component includes a Bluetooth module, the status information of the Bluetooth module may include physical link on / off status, signal strength information, number of successful Bluetooth communications, number of failed Bluetooth communications, and number of Bluetooth module reinitializations.

[0078] In an embodiment where the preset component includes a charging module, the status information of the charging module may include the on / off status of the physical link, the charging efficiency, and the discharging efficiency.

[0079] In an embodiment where the preset component includes a small battery, the status information of the small battery may include the battery life and output voltage when fully charged.

[0080] In an embodiment where the preset component includes a positioning module, the status information of the positioning module may include the physical link on / off status, satellite information (number of satellites and SNR value of each satellite), number of floating point solution successes, number of floating point solution failures, number of fixed point connection successes, and number of fixed point connection failures.

[0081] In an embodiment where the preset component includes an RS485 communication module, the status information of the RS485 communication module may include the on / off status of the physical link, the number of RS485 communication successes, and the number of RS485 communication failures.

[0082] In an embodiment where the preset component includes a CAN communication module, the status information of the CAN communication module may include the on / off status of the physical link, the number of CAN communication successes, and the number of CAN communication failures.

[0083] In an embodiment where the preset component includes a large battery, the status information of the large battery may include physical link on / off status, discharge voltage, discharge current, battery cell temperature, protection status, and fault status.

[0084] In an embodiment where the preset components include electronic control, the status information of the electronic control may include the on / off status of the physical link, electronic control protection status, electronic control fault status, brake handle voltage, throttle handle voltage, power assist status, and working mode.

[0085] In an embodiment where the preset component includes a helmet lock, the status information of the load sensor may include the on / off status of the physical link, the switch status of the helmet lock, the placement status of the helmet, and the wearing status of the helmet.

[0086] In an embodiment where the preset component includes a load sensor, the status information of the helmet lock may include the on / off status of the physical link, the collected weight information, and the determination of single-person riding and multi-person riding.

[0087] In one embodiment of the present disclosure, while a shared vehicle is in use, steps S2100 to S2300 of this embodiment may be executed at a first frequency; when the shared vehicle is not in use, steps S2100 to S2300 of this embodiment may be executed at a second frequency. The first frequency and the second frequency may be set based on the application scenario or specific needs, respectively, and may be the same or different. In one example, the first frequency is greater than the second frequency.

[0088] Step S2200: Determine the health of the shared vehicle based on the status information.

[0089] In one embodiment of the present disclosure, determining the health score of a shared vehicle based on the status information may include: inputting the status information obtained in step S2100 into a pre-trained health score prediction model to obtain a health score representing the health level of the shared vehicle.

[0090] In another embodiment of the present disclosure, determining the health of the shared vehicle according to the status information may include steps S2210 to S2220 as follows:

[0091] Step S2210: Determine the status score corresponding to the status information.

[0092] In an embodiment where the status information is any one of the following: physical link on / off status, protection status, fault status, electronic control protection status, electronic control fault status, power assist status, working mode, helmet lock switch status, helmet placement status, helmet wearing status, single-person riding and multi-person riding determination status, a status score corresponding to each status information can be pre-set.

[0093] For example, if the physical link is on, the corresponding state score is 1, and if the physical link is off, the corresponding state score is 0; if the electric control fault state is faulty, the corresponding state score is 0, and if the electric control fault state is not faulty, the corresponding state score is 1; if the power assist state is power assisting, the corresponding state score is 1, and if the power assist state is not power assisting, the corresponding state score is 0; if the working mode is the first mode, the corresponding state score is 1, and if the working mode is the second mode, the corresponding state score is 2; if the helmet lock switch state is unlocked, the corresponding state score is 0. The corresponding state score is 1 when the helmet lock switch state is locked, and the corresponding state score is 0 when the helmet is placed in the bicycle basket; the corresponding state score is 1 when the helmet is placed in the bicycle basket, and the corresponding state score is 0 when the helmet is not placed in the bicycle basket; the corresponding state score is 1 when the helmet is worn, and the corresponding state score is 0 when the helmet is not worn; the corresponding state score is 1 when the determination of single-person riding and multi-person riding is single-person riding, and the corresponding state score is 2 when the determination of single-person riding and multi-person riding is multi-person riding.

[0094] In an embodiment where the status information is any one of signal strength information, number of successful network communications, number of failed network communications, number of network reinitializations, number of successful Bluetooth communications, number of failed Bluetooth communications, number of Bluetooth module reinitializations, charging efficiency, discharge efficiency, battery life when fully charged, output voltage, satellite information searched (number of satellites and signal-to-noise ratio of each satellite), number of successful floating-point solutions, number of failed floating-point solutions, number of successful fixed-point connections and number of failed fixed-point connections, number of successful RS485 communications, number of failed RS485 communications, number of successful CAN communications, number of failed CAN communications, discharge voltage, discharge current, battery cell temperature, brake handle voltage, throttle handle voltage, and weight information, the status score of the status information may be the specific value of the collected status information.

[0095] In step S2220, a weight calculation process is performed on the status score corresponding to the status information according to the preset weight of the status information to obtain a health score representing the health level of the shared vehicle.

[0096] In this embodiment, a corresponding weight can be set in advance for each status information of each preset component based on the application scenario or specific needs. Based on the preset weight of the status information, a weighted calculation process is performed on the status score corresponding to the status information. Based on the weight of the status information, a weighted sum or weighted average of the status scores corresponding to all status information can be performed to obtain the health score of the shared vehicle.

[0097] In one embodiment of the present disclosure, the method may further include: obtaining a characteristic value representing a scene feature of the scene in which the shared vehicle is located; obtaining a scene score corresponding to the state information based on the characteristic value of the scene feature affecting the state information, and determining a health score of the shared vehicle based on the scene score.

[0098] The scenario features in this embodiment can be pre-set based on the application scenario or specific needs. For example, the scenario features may include: vehicle lock status, shared vehicle riding status, ambient temperature, ambient occlusion status, large battery life, small battery life, and the length of time the shared vehicle has been in riding status.

[0099] In an embodiment where the scene feature is any one of a vehicle lock state, a riding state of a shared vehicle, and an ambient occlusion state, a feature value corresponding to the scene feature may be pre-set.

[0100] For example, the characteristic value corresponding to the unlocked state of the vehicle lock can be 1, and the characteristic value corresponding to the locked state of the vehicle lock can be 0; the characteristic value corresponding to the riding state of the shared vehicle can be 1, and the characteristic value corresponding to the unridden state of the shared vehicle can be 0; the characteristic value corresponding to the unobstructed state of the environmental occlusion can be 0, and the characteristic value corresponding to the severe occlusion state of the environmental occlusion can be 2.

[0101] In an embodiment where the scene feature is any one of the ambient temperature, the service life of the large battery, the service life of the small battery, and the length of time the shared vehicle is in a riding state, the feature value of the scene feature may be the specific numerical value of the scene feature collected.

[0102] In one embodiment of the present disclosure, the scenario features that affect each state information may be pre-set according to the application scenario or specific requirements.

[0103] For each piece of state information, the scene score corresponding to the state information may be obtained according to the feature value of the scene feature that affects the state information.

[0104] In one embodiment, the feature values ​​of the scene features that affect the state information can be input into the scene score prediction model corresponding to the state information to obtain the scene score corresponding to the state information. The scene score prediction model corresponding to each state information can be pre-trained based on the historical usage data of the shared vehicle.

[0105] In another embodiment, the scene score corresponding to the state information may be obtained by performing weight calculation on the feature values ​​of the scene features affecting the state information according to preset weights of the scene features affecting the state information.

[0106] In one embodiment of the present disclosure, the health score of the shared vehicle is also determined based on the scenario score, which may include: determining the product of the status score corresponding to the status information and the scenario score; and performing weight calculation processing on the product corresponding to the status information based on the weight to obtain the health score of the shared vehicle.

[0107] The weight calculation process in this embodiment may be a weighted summation process or a weighted average process.

[0108] For example, the health score of the shared vehicle can be determined by the following formula:

[0109]

[0110] in, is the health score of the shared vehicle, k is the total number of status information, a i is the weight corresponding to the i-th state information, xi is the state score corresponding to the i-th state information, f i is the scene score corresponding to the i-th state information.

[0111] Step S2300: Predict faults of the shared vehicle based on the health score.

[0112] In one embodiment of the present disclosure, performing fault prediction on the shared vehicle based on its health status may include steps S2310 to S2330 as follows:

[0113] Step S2310: Compare the health score with a preset score range.

[0114] The preset score range may be set in advance according to an application scenario or specific requirements. For example, the preset score range may be greater than or equal to 100.

[0115] Step S2320: Determine whether a fault prediction alarm event occurs based on the comparison result.

[0116] In one embodiment of the present disclosure, when the comparison result is that the health score is not within the preset score range, it is determined that a fault prediction alarm event has occurred; when the comparison result is that the health score is within the preset score range, it is determined that a fault prediction alarm event has not occurred.

[0117] In another embodiment of the present disclosure, determining whether a fault prediction alarm event occurs according to the comparison result may further include steps S2321 to S2323 as shown below:

[0118] Step S2321: If the comparison result shows that the health score is not within the preset score range, determine whether the first number is greater than or equal to a preset first number threshold. The first number is the number of times the comparison result shows that the health score is not within the preset score range.

[0119] The first number threshold may be pre-set according to an application scenario or specific requirements. For example, the first number threshold may be 3.

[0120] In this embodiment, the first scalar is incremented by one each time the comparison result shows that the health score is not within the preset score range.

[0121] In one embodiment of the present disclosure, the method may further include: determining whether the second number is greater than or equal to a preset second number threshold, wherein the second number is the number of consecutive comparison results indicating that the health score is within a preset score range; and resetting the first number if the second number is greater than or equal to the second number threshold.

[0122] The second threshold value may be pre-set based on the application scenario or specific needs. For example, the second threshold value may be 5. Then, if the comparison results obtained for 5 consecutive times all show that the health score is within the preset score range, the first threshold value is reset.

[0123] Resetting the first number in this embodiment may be resetting the first number to zero.

[0124] Step S2322: When the first number of times is greater than or equal to the first number threshold, it is determined that a fault prediction alarm event occurs.

[0125] Step S2323 : If the comparison result is within the preset score range, it is determined that the fault prediction alarm event has not occurred, and steps S2100 to S2300 of this embodiment are executed again.

[0126] Since the status information of some preset components has large jitter, through this embodiment, when the comparison result is that the health score is not within the preset score range for the first time and is greater than or equal to the first number threshold, it is determined that a fault prediction alarm event has occurred, which can make the obtained fault prediction result more accurate.

[0127] Step S2330: When a fault prediction alarm event occurs, the result of the shared vehicle's predicted fault is reported to the server.

[0128] In this embodiment, the result of the shared vehicle predicted failure may include a result indicating that the shared vehicle is about to fail. By reporting the result of the shared vehicle predicted failure to the server, the server processes the shared vehicle according to the result.

[0129] Specifically, the server may notify the operation and maintenance personnel to repair the shared vehicle based on the result, or notify the user terminal that is using the shared vehicle to stop using the shared vehicle to avoid causing personal injury to the user of the shared vehicle.

[0130] Through the embodiments of the present disclosure, the health score of a shared vehicle is determined based on the status information of at least one component in the shared vehicle, and then faults of the shared vehicle are predicted based on the health score. This allows for early warning and prevention of impending faults in the shared vehicle, and allows for precise control before the shared vehicle actually fails, thereby preventing personal injury to users and preventing irreversible damage to the shared vehicle due to further use by users.

[0131] In one embodiment of the present disclosure, the method may further include: determining a predicted fault level of the shared vehicle based on the health score, and reporting the predicted fault level to a server.

[0132] In this embodiment, multiple fault levels and health score ranges corresponding to each fault level may be pre-set. When a fault prediction alarm event occurs, the shared vehicle may determine the fault level corresponding to the health score range to which its health score belongs, as the predicted fault level of the shared vehicle.

[0133] The server can determine the maintenance order of the shared vehicle based on the predicted fault level of the shared vehicle.

[0134] In one embodiment of the present disclosure, the method may further include: when a fault prediction alarm event occurs, determining the fault prediction type of the shared vehicle based on the status information; and reporting the fault prediction type to the server.

[0135] In this embodiment, a corresponding qualified range and fault prediction type may be determined in advance for at least one piece of status information. Determining the fault prediction type of the shared vehicle based on the status information may include comparing the status information with the corresponding qualified range, determining status information that exceeds the corresponding qualified range, and determining the fault prediction type corresponding to the status information that exceeds the corresponding qualified range as the fault prediction type of the shared vehicle.

[0136] The server may pre-set the priority of each fault prediction type according to the application scenario or specific needs. Upon receiving the fault prediction type of the shared vehicle, the server determines the maintenance order of the shared vehicle according to the priority of the fault prediction type of the shared vehicle.

[0137] In one embodiment, the server may comprehensively determine the maintenance order of the shared vehicles based on the predicted fault level of the shared vehicles and the priority of the predicted fault type of the shared vehicles.

[0138] Specifically, the shared vehicles may be sorted first according to the predicted fault level; then, for each shared vehicle of the predicted fault level, the shared vehicles of each predicted fault level may be sorted according to the priority of the fault prediction type corresponding to the shared vehicle, and the sorting value of each shared vehicle may be obtained, which may represent the maintenance order of the shared vehicles.

[0139] In one embodiment of the present disclosure, the shared vehicle may report the result of the predicted failure to the server through a network communication module, or may send the result of the predicted failure to a maintenance client used by maintenance personnel through a Bluetooth module, and then the maintenance client reports the result of the predicted failure to the server.

[0140] <Device Example>

[0141] Corresponding to the above method, the present disclosure also provides a control device 300 for a shared vehicle, such as Figure 3As shown, the system includes a status information acquisition module 310, a health score determination module 320, and a fault prediction module 330. The status information acquisition module 310 is used to obtain status information of at least one preset component in the shared vehicle; the health score determination module 320 is used to determine the health level of the shared vehicle based on the status information; and the fault prediction module 330 is used to predict faults of the shared vehicle based on the health level.

[0142] In one embodiment of the present disclosure, the health score determination module 320 is used to:

[0143] Determining a status score corresponding to the status information;

[0144] According to the preset weight of the status information, a weight calculation process is performed on the status score corresponding to the status information to obtain a health score representing the health level of the shared vehicle.

[0145] In one embodiment of the present disclosure, the control device 300 of the shared vehicle further includes:

[0146] A module for obtaining a feature value representing a scene feature of a scene in which the shared vehicle is located;

[0147] a module for obtaining a scene score corresponding to the state information according to a feature value of a scene feature affecting the state information;

[0148] The health score determination module 320 is further configured to determine the health score of the shared vehicle according to the scenario score.

[0149] In one embodiment of the present disclosure, the health score determination module 320 is further configured to:

[0150] Determine a product of a state score and a scene score corresponding to the state information;

[0151] According to the weight, weight calculation processing is performed on the product corresponding to the status information to obtain the health score.

[0152] In one embodiment of the present disclosure, the fault prediction module 330 is further configured to:

[0153] comparing the health score with a preset score range;

[0154] Determine whether a fault prediction alarm event occurs based on the comparison result;

[0155] When the fault prediction alarm event occurs, the result of the shared vehicle predicted fault is reported to the server.

[0156] In one embodiment of the present disclosure, determining whether a fault prediction alarm event occurs according to the comparison result includes:

[0157] If the comparison result is that the health score is not within the preset score range, determining whether the first number is greater than or equal to a preset first number threshold; wherein the first number is the number of times it is determined that the comparison result is that the health score is not within the preset score range;

[0158] When the first number is greater than or equal to the first number threshold, it is determined that the fault prediction alarm event occurs.

[0159] In one embodiment of the present disclosure, the control device 300 of the shared vehicle further includes:

[0160] A module for determining whether the second number is greater than or equal to a preset second number threshold; wherein the second number is the number of consecutive times that the comparison result shows that the health score is within the preset score range;

[0161] A module configured to reset the first number of times when the second number of times is greater than or equal to a second number threshold.

[0162] In one embodiment of the present disclosure, the control device 300 of the shared vehicle further includes:

[0163] A module for determining a fault prediction type of the shared vehicle according to the status information when the fault prediction alarm event occurs;

[0164] A module for reporting the fault prediction type to the server.

[0165] Those skilled in the art should understand that the control device 300 of the shared vehicle can be implemented in various ways. For example, the control device 300 of the shared vehicle can be implemented by configuring the processor with instructions. For example, the instructions can be stored in a ROM, and when the device is started, the instructions are read from the ROM into a programmable device to implement the control device 300 of the shared vehicle. For example, the control device 300 of the shared vehicle can be solidified into a dedicated device (such as an ASIC). The control device 300 of the shared vehicle can be divided into independent units, or they can be combined together for implementation. The control device 300 of the shared vehicle can be implemented by one of the various implementations described above, or can be implemented by a combination of two or more of the various implementations described above.

[0166] In this embodiment, the control device 300 of the shared vehicle can have multiple implementation forms. For example, the control device 300 of the shared vehicle can be a functional module running in any software product or application that provides control services for shared vehicles, or it can be a peripheral embedded component, plug-in, patch, etc. of these software products or applications, or it can be these software products or applications themselves.

[0167] <Shared Vehicle Example>

[0168] This embodiment provides a shared vehicle 400. In one example, the shared vehicle may include the aforementioned control device 300 for the shared vehicle.

[0169] In another example, Figure 4 As shown, the shared vehicle 400 may include a memory 420 and a processor 410, the memory 420 is used to store program instructions, and the processor 410 is used to control the shared vehicle 400 to execute any one of the shared vehicle control methods provided in this embodiment when executing the computer program.

[0170] Through the embodiments of the present disclosure, the health score of a shared vehicle is determined based on the status information of at least one component in the shared vehicle, and then faults of the shared vehicle are predicted based on the health score. This allows for early warning and prevention of impending faults in the shared vehicle, and allows for precise control before the shared vehicle actually fails, thereby preventing personal injury to users and preventing irreversible damage to the shared vehicle due to further use by users.

[0171] The present invention may be a system, a method and / or a computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present invention.

[0172] A computer-readable storage medium can be a tangible device that can hold and store instructions for use by an instruction execution device. A computer-readable storage medium can be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination thereof. As used herein, a computer-readable storage medium is not to be construed as a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted through an electrical wire.

[0173] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in the computer-readable storage medium in each computing / processing device.

[0174] The computer program instructions for performing the operation of the present invention can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, and conventional procedural programming languages ​​such as "C" language or similar programming languages. The computer readable program instructions can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect via the Internet). In some embodiments, an electronic circuit, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), is personalized by utilizing the state information of the computer readable program instructions, and the electronic circuit can execute the computer readable program instructions, thereby realizing various aspects of the present invention.

[0175] Various aspects of the present invention are described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0176] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0177] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0178] The flowcharts and block diagrams in the accompanying drawings show the possible implementation architectures, functions and operations of the systems, methods and computer program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, program segment or part of an instruction, and a module, program segment or part of an instruction contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, as well as the combination of boxes in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or can be implemented using a combination of dedicated hardware and computer instructions. It is well known to those skilled in the art that implementation by hardware, implementation by software, and implementation by a combination of software and hardware are all equivalent.

[0179] While various embodiments of the present invention have been described above, the foregoing description is intended to be illustrative, non-exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or technological improvements in the marketplace, or to enable others skilled in the art to understand the embodiments disclosed herein. The scope of the present invention is defined by the appended claims.

Claims

1. A method for controlling a shared vehicle, comprising: Obtaining status information of at least one preset component in the shared vehicle; determining the health of the shared vehicle according to the status information; Predicting faults of the shared vehicle based on the health status; The preset components include at least one of a network communication module, a Bluetooth module, a charging module, a small battery, a positioning module, an RS485 communication module, a CAN communication module, a large battery, an electronic control, a load sensor, and a helmet lock; Determining the health of the shared vehicle according to the status information includes: determining a status score corresponding to the status information; Performing weight calculation processing on the status score corresponding to the status information according to the preset weight of the status information to obtain a health score representing the health level of the shared vehicle; Predicting a fault of the shared vehicle based on the health score includes: comparing the health score with a preset score range, and determining whether a fault prediction alarm event has occurred based on the comparison result; and reporting a result of the shared vehicle's predicted fault to a server when the fault prediction alarm event occurs; The method also includes: in the event that the fault prediction alarm event occurs, determining the fault prediction type of the shared vehicle according to the status information; reporting the fault prediction type to the server, and upon receiving the fault prediction type of the shared vehicle, the server determines the maintenance order of the shared vehicle according to the priority of the fault prediction type of the shared vehicle. Specifically, the shared vehicles are first sorted according to the predicted fault level; then, for each shared vehicle of each predicted fault level, the shared vehicles of each predicted fault level are sorted according to the priority of the fault prediction type of the corresponding shared vehicle to obtain a ranking value for each shared vehicle, and the ranking value is used to represent the maintenance order of the shared vehicle.

2. The method according to claim 1, further comprising: Acquire a feature value representing a scene feature of the scene in which the shared vehicle is located; Obtaining a scene score corresponding to the state information according to a feature value of a scene feature that affects the state information; A health score of the shared vehicle is also determined based on the scenario score.

3. The method according to claim 2, further determining the health score of the shared vehicle based on the scenario score, comprising: Determine a product of a state score and a scene score corresponding to the state information; According to the weight, weight calculation processing is performed on the product corresponding to the status information to obtain the health score.

4. The method according to claim 1, wherein determining whether a fault prediction alarm event occurs based on the comparison result comprises: If the comparison result is that the health score is not within the preset score range, determining whether the first number is greater than or equal to a preset first number threshold; wherein the first number is the number of times it is determined that the comparison result is that the health score is not within the preset score range; When the first number is greater than or equal to the first number threshold, it is determined that the fault prediction alarm event occurs.

5. The method according to claim 4, comprising: Determine whether the second number is greater than or equal to a preset second number threshold; wherein the second number is the number of consecutive times that the comparison result shows that the health score is within the preset score range; When the second number of times is greater than or equal to the second number threshold, the first number of times is reset.

6. A control device for a shared vehicle, comprising: A status information acquisition module, configured to acquire status information of at least one preset component in the shared vehicle; a health score determination module, configured to determine a health score of the shared vehicle based on the status information, the health score being a score indicating the health level of the shared vehicle; A fault prediction module, configured to perform fault prediction on the shared vehicle based on the health score; Determining the health of the shared vehicle according to the status information includes: determining a status score corresponding to the status information; Performing weight calculation processing on the status score corresponding to the status information according to the preset weight of the status information to obtain a health score representing the health level of the shared vehicle; Predicting a fault of the shared vehicle based on the health score includes: comparing the health score with a preset score range, and determining whether a fault prediction alarm event has occurred based on the comparison result; and reporting a result of the shared vehicle's predicted fault to a server when the fault prediction alarm event occurs; When the fault prediction alarm event occurs, the fault prediction type of the shared vehicle is determined according to the status information; the fault prediction type is reported to the server, and when the server receives the fault prediction type of the shared vehicle, the server determines the maintenance order of the shared vehicle according to the priority of the fault prediction type of the shared vehicle. Specifically, the shared vehicles are first sorted according to the predicted fault level; then, for each shared vehicle of each predicted fault level, the shared vehicles of each predicted fault level are sorted according to the priority of the fault prediction type of the corresponding shared vehicle to obtain a ranking value for each shared vehicle, which is used to represent the maintenance order of the shared vehicle.

7. A shared vehicle, comprising a control device for a shared vehicle as claimed in claim 6; or, the shared vehicle comprises a memory and a processor, the memory being used to store a computer program, the processor being used to control the shared vehicle to execute the method according to any one of claims 1 to 5 when executing the computer program.

Citation Information

Patent Citations

  • Shared vehicle state detection method and device

    CN111915403A

  • New energy vehicle health condition remote evaluation method and system

    CN111968268A