Driving direction judgment method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention relates to a driving direction judgment method and device, equipment, a storage medium and a program product. The method comprises the following steps: obtaining a target spike identifier sequence corresponding to a target shared vehicle, the target spike identifier sequence comprising a plurality of Bluetooth spike identifiers sorted according to a scanning sequence, the multiple Bluetooth spike identifiers are obtained by scanning Bluetooth spikes arranged on a driven target road by Bluetooth scanning equipment located on the target shared vehicle in the driving process of the target shared vehicle; and determining whether the target shared vehicle runs reversely according to the target spike identification sequence. By adopting the method, the accuracy of judging whether the shared vehicle runs reversely can be improved.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of vehicle technology, and in particular, to a driving direction determination method, device, equipment, storage medium, and program product. Background Art

[0002] According to traffic regulations, vehicles need to drive on the right. As cities continue to improve their requirements for civilized travel and traffic safety, users of shared vehicles also need to drive on the right to ensure driving safety.

[0003] In related technologies, in order to regulate user riding, the vehicle position continuously reported by the shared vehicle during driving is used to determine whether the user is riding in the wrong direction.

[0004] However, the location reported by the vehicle often drifts on both sides of the road and cannot represent the actual position of the shared vehicle, resulting in an inability to accurately determine whether the user is driving in the wrong direction. Summary of the invention

[0005] The embodiments of the present disclosure provide a driving direction determination method, device, equipment, storage medium and program product, which can be used to improve the accuracy of determining whether a shared vehicle is traveling in the wrong direction.

[0006] In a first aspect, an embodiment of the present disclosure provides a method for determining a driving direction, the method comprising:

[0007] A target road stud identification sequence corresponding to a target shared vehicle is obtained, the target road stud identification sequence comprising a plurality of Bluetooth road stud identifications arranged in a scanning order, the plurality of Bluetooth road stud identifications being obtained by a Bluetooth scanning device located on the target shared vehicle scanning Bluetooth road studs arranged on a target road on which the target shared vehicle is traveling during the driving of the target shared vehicle; and whether the target shared vehicle is traveling in the wrong direction is determined according to the target road stud identification sequence.

[0008] In one embodiment, determining whether the target shared vehicle is traveling in the wrong direction according to the target road spike identification sequence includes:

[0009] A legal road spike identification sequence corresponding to the target road is obtained, wherein the legal road spike identification sequence includes Bluetooth road spike identifications of each Bluetooth road spike on the target road sorted in the order of forward travel; the target road spike identification sequence is compared with the legal road spike identification sequence; if the target road spike identification sequence is consistent with the legal road spike identification sequence, it is determined that the target shared vehicle is not traveling in the wrong direction; if the target road spike identification sequence is inconsistent with the legal road spike identification sequence, it is determined that the target shared vehicle is traveling in the wrong direction.

[0010] In one embodiment, obtaining a legal road stud identification sequence corresponding to the target road includes:

[0011] The Bluetooth road spike identifier to be retrieved is determined from the target road spike identifier sequence; the Bluetooth road spike identifier to be retrieved is searched in a plurality of different legal road spike identifier sequences, and the searched legal road spike identifier sequence including the Bluetooth road spike identifier to be retrieved is used as the legal road spike identifier sequence corresponding to the target road.

[0012] In one embodiment, obtaining a legal road stud identification sequence corresponding to the target road includes:

[0013] Acquire the road sign of the target road; determine a legal road stud mark sequence whose bound preset road sign is consistent with the road sign of the target road from multiple legal road stud mark sequences, so as to obtain a legal road stud mark sequence corresponding to the target road; wherein each legal road stud mark sequence is bound to a different preset road sign.

[0014] In one embodiment, before determining whether the target shared vehicle is traveling in the wrong direction according to the target road spike identification sequence, the method further includes:

[0015] It is determined whether the number of Bluetooth road stud identifiers included in the target road stud identifier sequence meets the direction determination condition; if so, it is determined whether the target shared vehicle is traveling in the wrong direction according to the target road stud identifier sequence.

[0016] In one embodiment, obtaining a target road stud identification sequence corresponding to a target shared vehicle includes:

[0017] A plurality of Bluetooth road spike identifiers are obtained by scanning the Bluetooth scanning device multiple times; and a target road spike identifier sequence is obtained according to the plurality of Bluetooth road spike identifiers obtained multiple times.

[0018] In one of the embodiments, the Bluetooth scanning device is a device built into the target shared vehicle; or, the Bluetooth scanning device is a user terminal corresponding to the user driving the target shared vehicle.

[0019] In one embodiment, the method further comprises:

[0020] If it is determined that the target shared vehicle is driving in the wrong direction, target reminder information is output; the target reminder information is used to remind the user that the vehicle is currently driving in the wrong direction.

[0021] In one embodiment, outputting target reminder information includes:

[0022] The target reminder information is sent to the target shared vehicle; the target reminder information is used to instruct the target shared vehicle to broadcast the target reminder information using a voice component.

[0023] In one embodiment, outputting target reminder information includes:

[0024] The target reminder information is sent to the car-using application; the target reminder information is used to instruct the car-using application to control the user terminal on which the car-using application is installed to output the target reminder information.

[0025] In one embodiment, the method further comprises:

[0026] If it is determined that the target shared vehicle is traveling in the wrong direction, then the preset reminder information corresponding to the geographical area where the target road is located is obtained; and the preset reminder information is used as the target reminder information.

[0027] In a second aspect, an embodiment of the present disclosure provides a driving direction determination device, the device comprising:

[0028] an acquisition module, configured to acquire a target road spike identification sequence corresponding to a target shared vehicle, wherein the target road spike identification sequence includes a plurality of Bluetooth road spike identifications arranged in a scanning order, wherein the plurality of Bluetooth road spike identifications are obtained by scanning Bluetooth road spikes arranged on a target road on which the target shared vehicle is traveling by a Bluetooth scanning device located on the target shared vehicle during the driving of the target shared vehicle;

[0029] The determination module is used to determine whether the target shared vehicle is traveling in the wrong direction according to the target road spike identification sequence.

[0030] In one embodiment, the determining module is specifically configured to:

[0031] A legal road spike identification sequence corresponding to the target road is obtained, wherein the legal road spike identification sequence includes Bluetooth road spike identifications of each Bluetooth road spike on the target road sorted in the order of forward travel; the target road spike identification sequence is compared with the legal road spike identification sequence; if the target road spike identification sequence is consistent with the legal road spike identification sequence, it is determined that the target shared vehicle is not traveling in the wrong direction; if the target road spike identification sequence is inconsistent with the legal road spike identification sequence, it is determined that the target shared vehicle is traveling in the wrong direction.

[0032] In one embodiment, the determining module is specifically configured to:

[0033] The Bluetooth road spike identifier to be retrieved is determined from the target road spike identifier sequence; the Bluetooth road spike identifier to be retrieved is searched in a plurality of different legal road spike identifier sequences, and the searched legal road spike identifier sequence including the Bluetooth road spike identifier to be retrieved is used as the legal road spike identifier sequence corresponding to the target road.

[0034] In one embodiment, the determining module is specifically configured to:

[0035] Acquire the road sign of the target road; determine a legal road stud mark sequence whose bound preset road sign is consistent with the road sign of the target road from multiple legal road stud mark sequences, so as to obtain a legal road stud mark sequence corresponding to the target road; wherein each legal road stud mark sequence is bound to a different preset road sign.

[0036] In one embodiment, the device further includes a determination module, configured to:

[0037] It is determined whether the number of Bluetooth road stud identifiers included in the target road stud identifier sequence meets the direction determination condition; if so, it is determined whether the target shared vehicle is traveling in the wrong direction according to the target road stud identifier sequence.

[0038] In one embodiment, the acquisition module is specifically used to:

[0039] A plurality of Bluetooth road spike identifiers are obtained by scanning the Bluetooth scanning device multiple times; and a target road spike identifier sequence is obtained according to the plurality of Bluetooth road spike identifiers obtained multiple times.

[0040] In one of the embodiments, the Bluetooth scanning device is a device built into the target shared vehicle; or, the Bluetooth scanning device is a user terminal corresponding to the user driving the target shared vehicle.

[0041] In one embodiment, the device further includes a reminder module, which is used to:

[0042] If it is determined that the target shared vehicle is driving in the wrong direction, target reminder information is output; the target reminder information is used to remind the user that the vehicle is currently driving in the wrong direction.

[0043] In one embodiment, the reminder module is specifically used to:

[0044] The target reminder information is sent to the target shared vehicle; the target reminder information is used to instruct the target shared vehicle to broadcast the target reminder information using a voice component.

[0045] In one embodiment, the reminder module is specifically used to:

[0046] The target reminder information is sent to the car-using application; the target reminder information is used to instruct the car-using application to control the user terminal on which the car-using application is installed to output the target reminder information.

[0047] In one embodiment, the device further includes an information acquisition module, which is used to:

[0048] If it is determined that the target shared vehicle is traveling in the wrong direction, then the preset reminder information corresponding to the geographical area where the target road is located is obtained; and the preset reminder information is used as the target reminder information.

[0049] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in the first aspect when executing the computer program.

[0050] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method described in the first aspect above.

[0051] In a fifth aspect, an embodiment of the present disclosure provides a computer program product, including a computer program, which implements the method described in the first aspect when executed by a processor.

[0052] The driving direction determination method, device, equipment, storage medium and program product provided by the embodiments of the present disclosure can obtain a target road stud identification sequence corresponding to a target shared vehicle, which includes multiple Bluetooth road stud identifications sorted in the order of scanning. Among them, the multiple Bluetooth road stud identifications are obtained by scanning the Bluetooth road studs set on the target road on which the target shared vehicle is traveling while the target shared vehicle is traveling, using a Bluetooth scanning device located on the target shared vehicle; thus, it can be determined whether the target shared vehicle is traveling in the opposite direction based on the target road stud identification sequence. In this way, when the target shared vehicle is traveling on the target road, since the Bluetooth road studs on the target road are fixed, the target road stud identification sequence scanned by the target shared vehicle can represent the driving direction of the target shared vehicle on the target road, and further, it can be determined whether the target shared vehicle is traveling in the opposite direction based on the target road stud identification sequence, thereby improving the accuracy of determining whether the shared vehicle is traveling in the opposite direction. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 A diagram showing an application environment of a method for determining a driving direction in an embodiment;

[0054] Figure 2 A schematic diagram of a flow chart of a driving direction determination method in one embodiment;

[0055] Figure 3 A schematic diagram of a process for obtaining a target road spike identification sequence in one embodiment;

[0056] Figure 4 A schematic diagram of a process for determining whether a target shared vehicle is traveling in the wrong direction in one embodiment;

[0057] Figure 5 A schematic diagram of the Bluetooth road stud configuration in one embodiment;

[0058] Figure 6 A schematic diagram of a process for obtaining a legal road stud identification sequence in one embodiment;

[0059] Figure 7 A schematic diagram of another process of obtaining a legal road spike identification sequence in one embodiment;

[0060] Figure 8 A schematic diagram of an application environment of a shared vehicle reverse driving determination method in one embodiment;

[0061] Fig. 9 A schematic diagram of a Bluetooth road stud identification scanning and reporting process in one embodiment;

[0062] Fig.10 A schematic diagram of a flow chart of server judgment processing in one embodiment;

[0063] Fig.11 is a structural block diagram of a driving direction determination device in one embodiment;

[0064] Fig.12 FIG. 4 is a diagram showing the internal structure of a server in one embodiment. DETAILED DESCRIPTION

[0065] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure more clear, the embodiments of the present disclosure are 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 embodiments of the present disclosure and are not used to limit the embodiments of the present disclosure.

[0066] First of all, before specifically introducing the technical solution of the embodiments of the present disclosure, the technical background or technical evolution context on which the embodiments of the present disclosure are based is introduced.

[0067] Normally, in the field of shared vehicles, the current technical background is: according to traffic regulations, vehicles need to drive on the right. As the city's requirements for civilized travel and traffic safety continue to improve, correspondingly, users of shared vehicles also need to drive on the right during driving to ensure driving safety. In the related art, in order to regulate user riding, the vehicle position continuously reported by the shared vehicle during driving is used to determine whether the user is driving in the opposite direction. Based on this background, the applicant has found through long-term model simulation research and development and the collection, demonstration and verification of experimental data that in the related technology, the positioning reported by the shared vehicle often drifts on both sides of the road, and cannot accurately represent the actual position of the shared vehicle, resulting in the inability to accurately judge whether the user is driving in the opposite direction. Therefore, improving the accuracy of judging whether the shared vehicle is driving in the opposite direction has become a problem that needs to be solved urgently. In addition, it should be noted that from the above-mentioned technical problems to the technical solutions introduced in the following embodiments, the inventors have devoted a lot of creative labor.

[0068] The technical solutions involved in the embodiments of the present disclosure are introduced below in combination with the scenarios to which the embodiments of the present disclosure are applied.

[0069] The driving direction determination method provided by the embodiment of the present disclosure can be applied to Figure 1 In the application environment shown. Among them, the target shared vehicle 101 communicates with the server 102. The Bluetooth scanning device on the target shared vehicle 101 scans the Bluetooth road studs set on the target road during the driving of the target shared vehicle, and the target shared vehicle 101 sends the scanned Bluetooth road stud identification to the server 102 to form a target road stud identification sequence. The server 102 determines whether the target shared vehicle is going in the opposite direction based on the target road stud identification sequence. Among them, the target shared vehicle 101 can be various types of shared vehicles, such as shared bicycles, shared electric vehicles, etc., which are not specifically limited here. The server 102 can be implemented with an independent server or a server cluster composed of multiple servers. For ease of understanding, the following description takes the target shared vehicle as a shared bicycle as an example.

[0070] In one embodiment, Figure 2 As shown, a method for determining the driving direction is provided. Figure 1 Taking the server 102 in the example as an example, the following steps are included:

[0071] Step 201, obtaining a target road spike identification sequence corresponding to a target shared vehicle. The target road spike identification sequence includes a plurality of Bluetooth road spike identifications sorted in a scanning order, and the plurality of Bluetooth road spike identifications are obtained by scanning Bluetooth road spikes set on a target road on which the target shared vehicle is traveling by a Bluetooth scanning device located on the target shared vehicle during the driving process of the target shared vehicle.

[0072] Among them, a plurality of Bluetooth road studs are arranged on the target road. Different Bluetooth road studs have different Bluetooth road stud identifiers for identifying the Bluetooth road studs. Optionally, the Bluetooth road stud identifiers may be arranged at preset intervals. The target road in the disclosed embodiment refers to the road on which the user is currently riding the target shared vehicle. The target road is a road that includes only one allowed driving direction, for example, the target shared vehicle is a shared bicycle, and the target road is a non-motorized vehicle lane.

[0073] When a user rides a target shared vehicle on a target road, a Bluetooth scanning device on the target shared vehicle can perform Bluetooth communication with the Bluetooth road studs. In this way, when passing by a Bluetooth road stud, the Bluetooth scanning device can obtain the Bluetooth road stud identifier of the Bluetooth road stud through the Bluetooth communication function.

[0074] It can be understood that, in the process of driving in a certain direction on the target road, the Bluetooth road studs passed by the target shared vehicle are in a certain order corresponding to the driving direction. Therefore, the Bluetooth scanning device obtains the Bluetooth road stud identifier of each Bluetooth road stud in the order of passing through each Bluetooth road stud, that is, the multiple Bluetooth road stud identifiers scanned by the Bluetooth scanning device are sorted in the order of scanning.

[0075] Optionally, the central control system of the target shared vehicle communicates with the server, so that the central control system can obtain multiple Bluetooth road stud identifiers scanned by the Bluetooth scanning device and send the multiple Bluetooth road stud identifiers to the server.

[0076] Optionally, the target shared vehicle may report each Bluetooth road spike identifier to the server whenever it obtains one. Alternatively, the target shared vehicle may periodically report the Bluetooth road spike identifier, reporting multiple Bluetooth road spike identifiers in each period.

[0077] The server constructs the target road spike identification sequence according to the acquired multiple Bluetooth road spike identifications.

[0078] It can be understood that, in the process that the target shared vehicle continuously reports the Bluetooth road spike identifier to the server, the target road spike identifier sequence is continuously updated, and the updated target road spike identifier sequence includes a larger number of Bluetooth road spike identifiers.

[0079] Step 202: Determine whether the target shared vehicle is traveling in the wrong direction according to the target road stud identification sequence.

[0080] Since the target road stud identification sequence includes multiple Bluetooth road stud identifications sorted in the order of scanning, and the scanning order is also the order of the Bluetooth road studs that the user rides the target shared vehicle through, therefore, when the Bluetooth road studs are fixed, the target road stud identification sequence can represent the driving direction of the target shared vehicle on the target road.

[0081] In this way, the server can determine whether the target shared vehicle is driving in the wrong direction based on the target road spike identification sequence.

[0082] For example, the server compares and determines whether the order of the Bluetooth road stud identifiers in the target road stud identifier sequence is correct according to the order of the Bluetooth road stud identifiers that should be scanned when the target road is traveling forward, thereby determining whether the target shared vehicle is traveling in the reverse direction.

[0083] Optionally, the user riding the target shared vehicle can use the target shared vehicle normally after borrowing the target shared vehicle and generating a vehicle order through the vehicle application in the user terminal held by the user terminal. Correspondingly, the server generates the vehicle order and updates the order status in the vehicle order. The order status includes start, riding, pending resource transfer, and completed resource transfer. In the embodiment of the present disclosure, the target road spike identification sequence can be obtained when the order status is riding, thereby saving the power consumption of the target shared vehicle.

[0084] The driving direction determination method provided by the embodiment of the present disclosure can obtain a target road stud identification sequence corresponding to the target shared vehicle, which includes multiple Bluetooth road stud identifications sorted in the order of scanning. Among them, the multiple Bluetooth road stud identifications are obtained by scanning the Bluetooth road studs set on the target road on which the target shared vehicle is traveling while the target shared vehicle is traveling, using a Bluetooth scanning device located on the target shared vehicle; thus, it can be determined whether the target shared vehicle is traveling in the wrong direction based on the target road stud identification sequence. In this way, when the target shared vehicle is traveling on the target road, since the Bluetooth road studs on the target road are fixed, the target road stud identification sequence scanned by the target shared vehicle can represent the driving direction of the target shared vehicle on the target road, and further, it can be determined whether the target shared vehicle is traveling in the wrong direction based on the target road stud identification sequence, thereby improving the accuracy of determining whether the shared vehicle is traveling in the wrong direction.

[0085] In one embodiment, Figure 3 FIG. 1 is a flow chart of obtaining a target road spike identification sequence provided by an embodiment of the present disclosure. Obtaining a target road spike identification sequence corresponding to a target shared vehicle includes:

[0086] Step 301, obtaining multiple Bluetooth road stud identifiers obtained by multiple scans of a Bluetooth scanning device.

[0087] Among them, as mentioned above, the target shared vehicle can periodically report the Bluetooth road stud identification.

[0088] Exemplarily, the Bluetooth scanning device can obtain a scanning cycle parameter, which can be stored in the Bluetooth scanning device or sent by the server to the Bluetooth scanning device in real time. During riding, the Bluetooth scanning device periodically scans according to the scanning cycle parameter, and obtains multiple Bluetooth road stud identifiers each time. The target shared vehicle reports the multiple Bluetooth road stud identifiers obtained in each cycle to the server. In this way, the server can obtain multiple Bluetooth road stud identifiers obtained by the Bluetooth scanning device through multiple scans, and form a target road stud identifier sequence.

[0089] Taking the scanning period parameter including the first duration and the second duration as an example, the Bluetooth scanning device can continuously scan the Bluetooth road stud identifier for the second duration at intervals of the first duration to achieve periodic scanning.

[0090] Optionally, the Bluetooth scanning device may scan a single Bluetooth road stud identifier in each cycle. For example, during a certain cycle of scanning, there may be a situation where a single Bluetooth road stud identifier is scanned if some of the passed Bluetooth road studs are faulty.

[0091] Step 302: Obtain a target road spike identification sequence according to multiple Bluetooth road spike identifications obtained multiple times.

[0092] After the server obtains multiple Bluetooth road spike identifiers for the first time, a target road spike identifier sequence is formed. After obtaining multiple Bluetooth road spike identifiers for the next time, the server adds the latest obtained Bluetooth road spike identifier to the target road spike identifier sequence and updates the target road spike identifier sequence. That is, after obtaining multiple Bluetooth road spike identifiers each time, the multiple Bluetooth road spike identifier sequences are aggregated with the multiple Bluetooth road spike identifier sequences obtained previously, thereby obtaining a target road spike identifier sequence.

[0093] In the related art, since shared vehicles continuously report their vehicle locations, and positioning is a relatively power-consuming function, for shared vehicles such as shared bicycles, continuous positioning will increase power consumption and increase operation and maintenance costs.

[0094] In the disclosed embodiment, the Bluetooth scanning device can perform periodic scanning, so that the server can obtain the target road spike identification sequence according to the multiple Bluetooth road spike identifications obtained multiple times. In this way, since the position of the Bluetooth road spike is fixed and periodic scanning is performed, the accuracy of the scanning can be guaranteed and the power consumption of the Bluetooth scanning device can be reduced.

[0095] In one implementation, the Bluetooth scanning device is a device built into the target shared vehicle.

[0096] Optionally, the scanning cycle parameters may be stored in the Bluetooth scanning device or sent by the server to the central control system of the target shared vehicle, and the central control system transmits them to the Bluetooth scanning device.

[0097] Optionally, when the order status is updated to "riding", the server sends a scanning instruction to the target shared vehicle. After receiving the scanning instruction, the central control system of the target shared vehicle instructs the Bluetooth scanning device to start scanning the Bluetooth road studs of each Bluetooth road stud passed by and report to the server. In this way, the power consumption of the Bluetooth scanning device is saved to a certain extent, that is, the power consumption of the target shared vehicle is saved, and the operation and maintenance cost is reduced.

[0098] It should be noted that the embodiment of the present disclosure does not specifically limit the location of the Bluetooth scanning device on the target shared vehicle body.

[0099] In another implementation, the Bluetooth scanning device is a user terminal corresponding to the user driving the target shared vehicle.

[0100] Optionally, a vehicle-using application is installed in the user terminal, and the user borrows the target shared vehicle based on the vehicle-using application. The scanning cycle parameter is stored in the vehicle-using application, or the vehicle-using application obtains the scanning cycle parameter from the server based on the user terminal.

[0101] Optionally, the order status is updated synchronously in the car application. When the order status is updated to riding, the car application calls the Bluetooth communication function of the terminal to communicate with the Bluetooth road studs to obtain the identification of each Bluetooth road stud in sequence. In addition, the car application communicates with the server and sends the identification of each Bluetooth road stud to the server using the user terminal.

[0102] Among them, the user terminal can be but is not limited to various smart phones, personal computers, laptops, tablets, Internet of Things devices and portable wearable devices with Bluetooth communication functions. The portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc.

[0103] In the disclosed embodiment, the Bluetooth road stud logo is scanned by a device built into the target shared vehicle or a user terminal, thereby improving the flexibility of the scanning process, avoiding scanning failures due to failures in a single scanning method, and improving the reliability of scanning the Bluetooth road stud logo, thereby improving the reliability of determining whether the target shared vehicle is traveling in the wrong direction.

[0104] In one embodiment, before determining whether the target shared vehicle is going in the wrong direction according to the target road spike identification sequence, the method further includes: determining whether the number of Bluetooth road spike identifications included in the target road spike identification sequence meets a direction determination condition; if so, determining whether the target shared vehicle is going in the wrong direction according to the target road spike identification sequence.

[0105] Among them, in order to ensure accurate judgment of whether the target shared vehicle is going in the wrong direction, in the embodiment of the present disclosure, a direction judgment condition is deployed in the server.

[0106] Exemplarily, the direction determination condition may include that the number of Bluetooth road spike identifiers included in the target road spike identifier sequence is greater than a preset identifier number threshold.

[0107] Correspondingly, when the server determines that the number of Bluetooth road stud identifiers included in the target road stud identifier sequence is greater than the preset identifier number threshold, it is determined that the direction judgment condition is met, and whether the target shared vehicle is going in the wrong direction is determined according to the target road stud identifier sequence; and when the server determines that the number of Bluetooth road stud identifiers included in the target road stud identifier sequence is not greater than the preset identifier number threshold, it is determined that the direction judgment condition is not met, and whether the target shared vehicle is going in the wrong direction is not determined based on the target road stud identifier sequence until the direction judgment condition is met, and whether the target shared vehicle is going in the wrong direction is determined according to the target road stud identifier sequence.

[0108] As mentioned above, each time the server receives multiple Bluetooth road spike identifiers, it aggregates the multiple Bluetooth road spike identifiers received most recently with the Bluetooth road spike identifiers received previously to obtain the target road spike identifier sequence, thereby updating the target road spike identifier sequence.

[0109] Optionally, each time after the target road spike identification sequence is updated, it is determined whether the direction determination condition is met.

[0110] Optionally, when a judgment satisfies the direction judgment condition, since the number of Bluetooth road studs scanned on the target road continues to increase, there is no need to judge whether the direction judgment condition is met in the subsequent judgment. Instead, it is directly judged whether the target shared vehicle is going in the opposite direction after updating the target road stud sequence.

[0111] The process of determining whether the target shared vehicle is traveling in the wrong direction is described below.

[0112] Please refer to Figure 4 , which shows a schematic diagram of a process for determining whether a target shared vehicle is traveling in the wrong direction provided by an embodiment of the present disclosure. Determining whether a target shared vehicle is traveling in the wrong direction according to a target road stud identification sequence includes:

[0113] Step 401: Obtain a legal road stud identification sequence corresponding to a target road. The legal road stud identification sequence includes Bluetooth road stud identifications of each Bluetooth road stud on the target road sorted in the order of forward travel.

[0114] Step 402: Compare the target road spike identification sequence with the legal road spike identification sequence.

[0115] like Figure 5 A schematic diagram of a Bluetooth road stud configuration provided by an embodiment of the present disclosure is shown. The target road is non-motorized vehicle lane 1, and the order of the Bluetooth road stud identifiers in the legal road stud identifier sequence corresponding to the target road is C, B, and A. Correspondingly, if the target shared vehicle is traveling in the forward direction, the order of the Bluetooth road stud identifiers in the target road stud identifier sequence is C, B, and A; if the target shared vehicle is traveling in the reverse direction, the order of the Bluetooth road stud identifiers in the target road stud identifier sequence is A, B, and C.

[0116] Step 403: If the target road spike identification sequence is compared and is consistent with the legal road spike identification sequence, it is determined that the target shared vehicle is not traveling in the wrong direction.

[0117] Step 404: If the target road spike identification sequence is inconsistent with the legal road spike identification sequence, it is determined that the target shared vehicle is traveling in the wrong direction.

[0118] If the order of the Bluetooth road spike identifiers in the target road spike identifier sequence is the same as the order of the Bluetooth road spike identifiers in the legal road spike identifier sequence, then the target road spike identifier sequence is consistent with the legal road spike identifier sequence, which means that the target shared vehicle is not traveling in the wrong direction.

[0119] If the order of the Bluetooth road stud identifiers in the target road stud identifier sequence is different from the order of the Bluetooth road stud identifiers in the legal road stud identifier sequence, then the target road stud identifier sequence is inconsistent with the legal road stud identifier sequence, which means that the target shared vehicle is traveling in the wrong direction.

[0120] Optionally, in a possible scenario, the user may turn while riding. In this case, the target road stud identification sequence includes identification sequences of two different directions. Correspondingly, the server can determine whether the current target shared vehicle is going in the opposite direction based on the sequence most recently acquired in time.

[0121] For example, continue to refer to Figure 5 , the target shared vehicle first travels forward on non-motorized vehicle lane 1 and then turns to reverse travel. The order of the Bluetooth road stud identifiers in the target road stud identifier sequence is C, B, A, A, B, C. At this time, the target shared vehicle is determined to be currently traveling in the reverse direction based on the comparison of the newly acquired identifier sequence A, B, C and the legal road stud identifier sequence.

[0122] In the disclosed embodiment, the server can obtain a legal road stud identification sequence, wherein the legal road stud identification sequence includes the Bluetooth road stud identifications of each Bluetooth road stud on the target road sorted in the order of forward travel; thus, the server can compare the target road stud identification sequence with the legal road stud identification sequence; and determine whether the target shared vehicle is traveling in the wrong direction based on the comparison result, thereby effectively ensuring the efficiency and accuracy of determining whether the target shared vehicle is traveling in the wrong direction.

[0123] In one possible implementation, Figure 6 FIG. 1 is a flow chart of obtaining a legal road stud identification sequence provided by an embodiment of the present disclosure. Obtaining a legal road stud identification sequence corresponding to a target road includes:

[0124] Step 601: determine the Bluetooth road spike identifier to be retrieved from the target road spike identifier sequence.

[0125] Optionally, the Bluetooth road spike identifier to be retrieved may be the first Bluetooth road spike identifier obtained first in the target road spike identifier sequence, or may be the last Bluetooth road spike identifier obtained last in the target road spike identifier sequence.

[0126] Optionally, the Bluetooth road spike identifier to be retrieved may be any Bluetooth road spike identifier in the target road spike identifier sequence.

[0127] Step 602: Search for the Bluetooth road spike identifier to be retrieved in a plurality of different legal road spike identifier sequences, and use the searched legal road spike identifier sequence including the Bluetooth road spike identifier to be retrieved as the legal road spike identifier sequence corresponding to the target road.

[0128] The server stores legal road stud identification sequences corresponding to different roads. The Bluetooth road stud identification of each Bluetooth road stud on each road can be unique. Therefore, each Bluetooth road stud identification only exists in one legal road stud identification sequence.

[0129] In this way, the server can query the Bluetooth road stud identifier to be retrieved in multiple different legal road stud identifier sequences according to the Bluetooth road stud identifier to be retrieved, thereby determining the legal road stud identifier sequence corresponding to the target road.

[0130] In another possible implementation, Figure 7 FIG. 2 is a flow chart of another method for obtaining a legal road stud identification sequence according to an embodiment of the present disclosure. The method of obtaining a legal road stud identification sequence corresponding to a target road includes:

[0131] Step 701, obtaining the road sign of the target road.

[0132] Optionally, when entering the target road, the positioning component in the target shared vehicle can obtain the location of the target shared vehicle, so that the target shared vehicle can report the current location information to the server. The server determines the target road according to the location and obtains the identification of the target road.

[0133] Optionally, when entering the target road, the user application can report the location of the target shared vehicle to the server based on the user terminal.

[0134] For example, the server may compare the location information with map data to determine the target road.

[0135] Step 702: Determine a legal road spike identification sequence whose bound preset road identification is consistent with the road identification of the target road from among the plurality of legal road spike identification sequences, so as to obtain a legal road spike identification sequence corresponding to the target road. Each legal road spike identification sequence is bound to a different preset road identification.

[0136] The preset road signs corresponding to different roads may be unique. Thus, for each road, the preset road sign corresponding to the road is bound to the legal road spike sign sequence corresponding to the road. The binding relationship between each legal road spike sign sequence and the corresponding preset road sign is stored in the server.

[0137] In this way, after the server determines the road sign of the target road, it compares the road sign of the target road with each preset road sign, and thus uses the legal road stud mark sequence bound to the preset road signs that are consistent with the comparison as the legal road stud mark sequence corresponding to the target road.

[0138] In the disclosed embodiment, the server can determine the legal road stud identification sequence corresponding to the target road based on the Bluetooth road stud identification to be retrieved or the road identification of the target road, thereby improving the accuracy and reliability of determining the legal road stud identification sequence corresponding to the target road and providing a reliable basis for accurately judging whether the target shared vehicle is traveling in the wrong direction.

[0139] In addition, in the implementation of the present disclosure, when it is determined that the target shared vehicle is driving in the reverse direction, the user can also be reminded that the vehicle is currently driving in the reverse direction, and the user can be reminded to adjust the direction as soon as possible to ensure the user's safety.

[0140] In one embodiment, the method further includes: if it is determined that the target shared vehicle is traveling in the wrong direction, outputting target reminder information; wherein the target reminder information is used to remind the user that the user is currently in a wrong direction driving state.

[0141] That is, the target reminder information includes reverse reminder information, and the reverse reminder information can be used to remind the user that the user is currently in a reverse driving state and remind the user to switch to forward driving as soon as possible.

[0142] Optionally, the target reminder information also includes retrograde processing result prompt information, which is used to remind the user of the retrograde processing result.

[0143] In other words, the target reminder information may include one of reverse reminder information and reverse processing result reminder information.

[0144] In one embodiment, the method further includes: if it is determined that the target shared vehicle is traveling in the wrong direction, obtaining preset reminder information corresponding to the geographical area where the target road is located; and using the preset reminder information as the target reminder information.

[0145] Among them, the reverse processing results corresponding to different geographical areas may be different. In the embodiment of the present disclosure, the geographical area where the target lane is located can be determined according to the target lane. Then, the server can obtain the reverse processing result prompt information corresponding to the geographical area as the preset reminder information corresponding to the geographical area, thereby obtaining the target reminder information.

[0146] In one embodiment, outputting the target reminder information includes: sending the target reminder information to the target shared vehicle; the target reminder information is used to instruct the target shared vehicle to broadcast the target reminder information using a voice component.

[0147] That is, after the target sharing vehicle receives the target reminder information, the voice component set in the target sharing vehicle is controlled to voice broadcast the target reminder information.

[0148] Optionally, other types of reminder components may be provided in the target shared vehicle, and target reminder information in a corresponding format may be output, which is not specifically limited here.

[0149] In one embodiment, outputting the target reminder information includes: sending the target reminder information to the car-using application; the target reminder information is used to instruct the car-using application to control the user terminal on which the car-using application is installed to output the target reminder information.

[0150] That is, the user terminal can receive and output the target reminder information for the user to view.

[0151] Exemplarily, the user terminal may output the target reminder information by at least one of vibration of a vibration component, voice broadcast of a voice component, and screen pop-up window display.

[0152] In the disclosed embodiment, when it is sensed that the target shared vehicle is traveling in the wrong direction, the user is reminded and informed of the consequences of traveling in the wrong direction by outputting target reminder information, thereby improving the user's riding safety.

[0153] The following is an introduction to an embodiment of the present disclosure in conjunction with a specific vehicle usage scenario. Figure 8 As shown, the method includes:

[0154] The data of the legal Bluetooth road stud identification sequence corresponding to each offline road is pre-imported into the Bluetooth road stud database for storage. The device server is responsible for linking and communicating with the vehicle and the car application APP installed on the user terminal. In addition, the device server also needs to forward specific messages (such as the judgment result of whether the target shared vehicle is driving in the wrong direction) to the transaction server, and forward the message returned by the transaction server to the vehicle.

[0155] The transaction server is responsible for creating car orders and managing the status of car orders. Currently, the order status is divided into: starting, riding, waiting for resource transfer, and completed resource transfer.

[0156] Please refer to Fig. 9 The schematic diagram of the Bluetooth road stud identification scanning and reporting process is shown. Among them, after the user unlocks the target shared vehicle based on the user terminal, the target shared vehicle scans the Bluetooth road studs on the target road for x seconds every y seconds, and reports the scanned Bluetooth road stud identification to the device server. Alternatively, when the car application APP is running in the background of the user terminal, the car application APP controls the user terminal to scan the Bluetooth road studs on the target road for x seconds every y seconds, and reports the scanned Bluetooth road stud identification to the device server based on the user terminal. Stop scanning when the car order is completed.

[0157] Please refer to Fig.10 The flow chart of server judgment processing is shown. Among them, the device server receives the Bluetooth scanning result reported by the target shared vehicle or APP, and the Bluetooth scanning result includes multiple Bluetooth road stud identifiers scanned in sequence this time. The multiple Bluetooth road stud identifiers received this time are aggregated with the Bluetooth road stud identifiers received previously to obtain the target Bluetooth road stud identifier sequence.

[0158] The device server compares the target road spike identification sequence with the legal road spike identification sequence corresponding to the target road to determine whether the road is traveling in the wrong direction, and sends the judgment result of traveling in the wrong direction to the transaction server.

[0159] When the transaction server determines that the reverse judgment result is that the target shared vehicle is reversed, it obtains the preset reminder information corresponding to the target road and sends the preset reminder information as the target reminder information to the device server. The device server sends the target reminder information to the target shared vehicle, and the target shared vehicle controls the voice component to broadcast the target reminder information for voice reminder.

[0160] In the disclosed embodiment, when a user is riding a target shared vehicle, the target shared vehicle periodically scans the surrounding Bluetooth road studs. Since the positions of the road studs are known and fixed, it is possible to accurately determine whether the user's riding direction is correct based on the order in which the Bluetooth road stud identifiers are scanned.

[0161] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned 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 does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can 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 to be 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.

[0162] In one embodiment, Fig.11 As shown, a driving direction determination device is provided, and the driving direction determination device 1100 includes: an acquisition module 1101 and a determination module 1102, wherein:

[0163] The acquisition module 1101 is used to acquire a target road spike identification sequence corresponding to the target shared vehicle, where the target road spike identification sequence includes a plurality of Bluetooth road spike identifications sorted in a scanning order, and the plurality of Bluetooth road spike identifications are obtained by a Bluetooth scanning device located on the target shared vehicle scanning Bluetooth road spikes arranged on the target road on which the target shared vehicle is traveling during the driving process of the target shared vehicle;

[0164] The determination module 1102 is used to determine whether the target shared vehicle is traveling in the wrong direction according to the target road stud identification sequence.

[0165] In one embodiment, the determination module 1102 is specifically configured to:

[0166] A legal road spike identification sequence corresponding to the target road is obtained, wherein the legal road spike identification sequence includes the Bluetooth road spike identifications of the Bluetooth road spikes on the target road sorted in the order of forward travel; the target road spike identification sequence is compared with the legal road spike identification sequence; if the target road spike identification sequence is consistent with the legal road spike identification sequence, it is determined that the target shared vehicle is not traveling in the wrong direction; if the target road spike identification sequence is inconsistent with the legal road spike identification sequence, it is determined that the target shared vehicle is traveling in the wrong direction.

[0167] In one embodiment, the determination module 1102 is specifically configured to:

[0168] The Bluetooth road spike identifier to be retrieved is determined from the target road spike identifier sequence; the Bluetooth road spike identifier to be retrieved is searched in a plurality of different legal road spike identifier sequences, and the searched legal road spike identifier sequence including the Bluetooth road spike identifier to be retrieved is used as the legal road spike identifier sequence corresponding to the target road.

[0169] In one embodiment, the determination module 1102 is specifically configured to:

[0170] Acquire a road sign of a target road; determine a legal road stud mark sequence whose bound preset road sign is consistent with the road sign of the target road from a plurality of legal road stud mark sequences, so as to obtain a legal road stud mark sequence corresponding to the target road; wherein each legal road stud mark sequence is bound to a different preset road sign.

[0171] In one embodiment, the device further includes a determination module, configured to:

[0172] It is determined whether the number of Bluetooth road stud identifiers included in the target road stud identifier sequence meets the direction determination condition; if so, it is determined whether the target shared vehicle is traveling in the wrong direction according to the target road stud identifier sequence.

[0173] In one embodiment, the acquisition module 1101 is specifically used to:

[0174] A plurality of Bluetooth road spike identifiers are obtained by scanning the Bluetooth scanning device multiple times; and a target road spike identifier sequence is obtained according to the plurality of Bluetooth road spike identifiers obtained multiple times.

[0175] In one embodiment, the Bluetooth scanning device is a device built into the target shared vehicle; or, the Bluetooth scanning device is a user terminal corresponding to the user driving the target shared vehicle.

[0176] In one embodiment, the device further comprises a reminder module, which is used to:

[0177] If it is determined that the target shared vehicle is driving in the wrong direction, target reminder information is output; the target reminder information is used to remind the user that the vehicle is currently driving in the wrong direction.

[0178] In one embodiment, the reminder module is specifically used to:

[0179] Send target reminder information to the target shared vehicle; the target reminder information is used to instruct the target shared vehicle to broadcast the target reminder information using a voice component.

[0180] In one embodiment, the reminder module is specifically used to:

[0181] Send target reminder information to the car-using application; the target reminder information is used to instruct the car-using application to control the user terminal on which the car-using application is installed to output the target reminder information.

[0182] In one embodiment, the device further includes an information acquisition module 1101, which is used to:

[0183] If it is determined that the target shared vehicle is traveling in the wrong direction, the preset reminder information corresponding to the geographical area where the target road is located is obtained; and the preset reminder information is used as the target reminder information.

[0184] The specific definition of the driving direction determination device can be found in the definition of the driving direction determination method above, which will not be repeated here. Each module in the above driving direction determination device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above modules can be embedded in or independent of the processor in the electronic device in the form of hardware, or can be stored in the memory of the electronic device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0185] Fig.12 1 is a block diagram of a server 1400 according to an exemplary embodiment. Fig.12 The server 1400 includes a processing component 1420, which further includes one or more processors, and a memory resource represented by a memory 1422, for storing instructions or computer programs, such as applications, that can be executed by the processing component 1420. The application stored in the memory 1422 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1420 is configured to execute instructions to perform the above-mentioned method for determining the driving direction.

[0186] The server 1400 may also include a power supply component 1424 configured to perform power management of the device 1400, a wired or wireless network interface 1426 configured to connect the device 1400 to a network, and an input / output (I / O) interface 1428. The server 1400 may operate based on an operating system stored in the memory 1422, such as Windows 14 14erverTM, Mac O14 XTM, UnixTM, LinuxTM, FreeB14DTM or the like.

[0187] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 1422 including instructions, which can be executed by a processor of the server 1400 to perform the above method. The storage medium can be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0188] In an exemplary embodiment, a computer program product is also provided, and when the computer program is executed by a processor, the above method can be implemented. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, part or all of the above method can be implemented in whole or in part according to the process or function described in the embodiment of the present disclosure.

[0189] It should be noted that the solutions described in this specification and the embodiments, if they involve the processing of personal information, will be processed on the premise of having a legal basis (for example, obtaining the consent of the subject of personal information, or being necessary for the performance of a contract, etc.), and will only be processed within the prescribed or agreed scope. The user's refusal to process personal information other than the necessary information required for basic functions will not affect the user's use of basic functions. The solutions in the various embodiments involved in this application are all information and data authorized by the user or fully authorized by all parties, and the implementation and processing of each solution must comply with relevant regulations.

[0190] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods 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 memory, storage, database or other media used in the embodiments provided in the embodiments of the present disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. 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).

[0191] 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 specification.

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

Claims

1. A method for determining a driving direction, characterized in that: The method comprises: Acquire a target road spike identification sequence corresponding to a target shared vehicle, wherein the target road spike identification sequence includes a plurality of Bluetooth road spike identifications arranged in a scanning order, wherein the plurality of Bluetooth road spike identifications are obtained by scanning Bluetooth road spikes arranged on a target road on which the target shared vehicle is traveling by a Bluetooth scanning device located on the target shared vehicle during the driving of the target shared vehicle; Determine whether the target shared vehicle is traveling in the wrong direction according to the target road spike identification sequence.

2. The method according to claim 1, characterized in that The determining whether the target shared vehicle is traveling in the wrong direction according to the target road spike identification sequence includes: Acquire a legal road stud identification sequence corresponding to the target road, wherein the legal road stud identification sequence includes Bluetooth road stud identifications of each Bluetooth road stud on the target road sorted in a forward driving order; Comparing the target road spike identification sequence with the legal road spike identification sequence; If the target road spike identification sequence is consistent with the legal road spike identification sequence, it is determined that the target shared vehicle is not traveling in the wrong direction; If the target road spike identification sequence is inconsistent with the legal road spike identification sequence, it is determined that the target shared vehicle is traveling in the wrong direction.

3. The method according to claim 2, characterized in that The step of obtaining a legal road stud identification sequence corresponding to the target road includes: Determine the Bluetooth road spike identifier to be retrieved from the target road spike identifier sequence; The to-be-searched Bluetooth road spike identifier is searched in a plurality of different legal road spike identifier sequences, and the searched legal road spike identifier sequence including the to-be-searched Bluetooth road spike identifier is used as the legal road spike identifier sequence corresponding to the target road.

4. The method according to claim 2, characterized in that: The step of obtaining a legal road stud identification sequence corresponding to the target road includes: Acquire a road sign of the target road; Determine, from a plurality of legal road spike identification sequences, a legal road spike identification sequence whose bound preset road identification is consistent with the road identification of the target road, so as to obtain a legal road spike identification sequence corresponding to the target road; Wherein, each of the legal road stud identification sequences is bound to a different preset road identification.

5. The method according to claim 1, characterized in that Before determining whether the target shared vehicle is traveling in the wrong direction according to the target road spike identification sequence, the method further includes: Determining whether the number of Bluetooth road stud identifiers included in the target road stud identifier sequence meets a direction determination condition; If so, it is determined whether the target shared vehicle is traveling in the wrong direction according to the target road spike identification sequence.

6. The method according to claim 1, characterized in that The step of obtaining a target road spike identification sequence corresponding to a target shared vehicle includes: Acquire multiple Bluetooth road stud identifiers respectively obtained by scanning multiple times by the Bluetooth scanning device; The target road spike identification sequence is obtained according to the multiple Bluetooth road spike identifications obtained multiple times.

7. The method according to claim 6, characterized in that The Bluetooth scanning device is a device built into the target shared vehicle; or, the Bluetooth scanning device is a user terminal corresponding to a user driving the target shared vehicle.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: If it is determined that the target shared vehicle is traveling in the wrong direction, outputting target reminder information; The target reminder information is used to remind the user that the user is currently in a reverse driving state.

9. The method according to claim 8, characterized in that The output target reminder information includes: Sending the target reminder information to the target shared vehicle; The target reminder information is used to instruct the target shared vehicle to broadcast the target reminder information using a voice component.

10. The method according to claim 8, characterized in that The output target reminder information includes: Sending the target reminder information to the car application; The target reminder information is used to instruct the car-use application to control the user terminal on which the car-use application is installed to output the target reminder information.

11. The method according to claim 8, characterized in that The method further comprises: If it is determined that the target shared vehicle is traveling in the wrong direction, obtaining preset reminder information corresponding to the geographical area where the target road is located; The preset reminder information is used as the target reminder information.

12. A driving direction determination device, characterized in that: The device comprises: an acquisition module, configured to acquire a target road spike identification sequence corresponding to a target shared vehicle, wherein the target road spike identification sequence includes a plurality of Bluetooth road spike identifications arranged in a scanning order, and the plurality of Bluetooth road spike identifications are obtained by a Bluetooth scanning device located on the target shared vehicle scanning Bluetooth road spikes arranged on a target road on which the target shared vehicle is traveling during the driving of the target shared vehicle; A determination module is used to determine whether the target shared vehicle is traveling in the wrong direction according to the target road spike identification sequence.

13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 11 are implemented.

14. A 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 11 are implemented.

15. 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 11 are implemented.

Images