Shared vehicle control method and server

Abstract

The invention provides a shared vehicle control method and a server. The method comprises the following steps: acquiring positioning data and elevation data of a target shared vehicle; wherein the elevation data represents a first elevation of the target shared vehicle; according to the positioning data, whether the target shared vehicle is located in a dangerous area is determined, and the dangerous area is an area of at least two road sections with horizontal space overlapping; when it is determined that the target shared vehicle is located in the dangerous area, determining whether the target shared vehicle is located in a forbidden road section where the target shared vehicle is forbidden to travel in the dangerous area according to the elevation data; and under the condition that the target shared vehicle is in the forbidden road section, carrying out safety management and control on the target shared vehicle so as to guide a user to drive the target shared vehicle to safely leave the forbidden road section.

Description

Technical Field

[0001] This disclosure relates to the field of shared vehicle technology, and more specifically, to a shared vehicle control method and server. Background Technology

[0002] With the rapid development of the shared two-wheeler industry (including shared bicycles and shared electric bicycles), it has become an important part of urban short-distance transportation due to its advantages of flexibility, convenience, and environmental friendliness, effectively alleviating the "last mile" problem of urban travel. However, in the actual operation of shared two-wheelers, the problem of users illegally riding into prohibited areas such as overpasses and interchanges has become increasingly prominent, causing serious safety and traffic order risks.

[0003] Elevated bridges and interchanges, designed as urban expressways for high-speed motor vehicle traffic, inherently conflict with the characteristics of shared two-wheeled vehicles. Shared two-wheeled vehicles have weak stability, limited braking performance, and riders lack professional safety equipment. When sharing traffic with motor vehicles on bridges, collisions and rollovers are highly likely due to speed differences, blind spots of shared vehicles, and sudden lane changes, seriously threatening the lives of riders and other road users. Furthermore, users' illegal riding, going against traffic, and haphazard parking on bridges disrupt normal traffic flow, reduce bridge efficiency, exacerbate traffic congestion, and place significant pressure on urban traffic management.

[0004] Currently, the riding range of shared vehicles is mainly controlled through technologies such as electronic fences and GPS positioning, in order to restrict users from riding in prohibited areas.

[0005] However, for special geographical spaces such as overpasses and interchanges that overlap horizontally, some cities have resorted to manual intervention by adding traffic signs and arranging personnel for patrols. However, such methods are costly, have limited coverage, and are slow to respond, making it difficult to meet the needs of shared two-wheeled vehicles that are widely distributed and frequently used. They cannot fundamentally solve the safety and order hazards caused by illegal riding on bridges. Summary of the Invention

[0006] One objective of this disclosure is to provide a new technical solution for the safety management of shared vehicles traveling on prohibited sections of dangerous areas where at least two road segments have horizontal spatial overlap.

[0007] According to a first aspect of the present disclosure, a shared vehicle control method is provided, comprising: Acquire the location data and elevation data of the target shared vehicle; wherein the elevation data represents the first elevation of the target shared vehicle; Based on the location data, it is determined whether the target shared vehicle is in a dangerous area, wherein the dangerous area is an area where at least two road segments have horizontal spatial overlap; If it is determined that the target shared vehicle is in the danger zone, the elevation data is used to determine whether the target shared vehicle is located in a restricted section of the danger zone where the target shared vehicle is prohibited from driving. When the target shared vehicle is in the restricted road section, safety management is implemented for the target shared vehicle to guide the user to drive the target shared vehicle safely away from the restricted road section.

[0008] Optionally, determining whether the target shared vehicle is located within the danger zone and on a restricted road section where the target shared vehicle is prohibited from driving, based on the elevation data, includes: Obtain the second elevation of the restricted road section within the danger zone; Determine whether the difference between the first elevation and the second elevation is within a set first error range. If so, determine that the target shared vehicle is located in the restricted road section.

[0009] Optionally, the security management of the target shared vehicle includes at least one of the following: The target shared vehicle is controlled to issue a first voice warning to remind the user to leave the restricted road section; Control the target shared vehicle to reduce its driving speed; Control the target shared vehicle to stop power output.

[0010] Optionally, the method further includes: Detect whether the target shared vehicle has left the restricted road section; Once the target shared vehicle leaves the restricted road section, the safety management of the target shared vehicle shall cease.

[0011] Optionally, detecting whether the target shared vehicle has left the restricted road section includes: Obtain the third elevation of the normal road section within the danger zone; Obtain the second elevation of the restricted road section within the danger zone; determine whether the difference between the first elevation and the second elevation is within a set first error range; if not, determine that the target shared vehicle has left the restricted road section; or, Obtain the third elevation of the normal road section within the danger zone; determine whether the difference between the first elevation and the third elevation is within a set second error range; if so, determine that the target shared vehicle has left the prohibited road section; or, If the location data determines that the target shared vehicle has left the dangerous area, then the location data indicates that the target shared vehicle has left the restricted road section.

[0012] Optionally, the method further includes: If it is determined that the target shared vehicle is in the dangerous area, the frequency of acquiring the location data and elevation data of the target shared vehicle shall be increased.

[0013] Optionally, the method further includes: If it is determined that the target shared vehicle is in the dangerous area, the system controls the target shared vehicle to issue a second voice warning to remind the user not to enter the restricted area.

[0014] Optionally, the method further includes: Send a reminder message to the terminal device using the target shared vehicle indicating that the target shared vehicle is traveling on the restricted road section.

[0015] Optionally, the method further includes: When the terminal device finishes using the target shared vehicle, penalty information is generated based on the prohibited road sections traveled by the target shared vehicle during this use. The penalty information is sent to the terminal device for display.

[0016] Optionally, the method further includes: The terminal device controlling the use of the target shared vehicle displays a map of the shared vehicle and highlights the dangerous areas in the map.

[0017] Optionally, the method further includes: Based on the positioning data and the elevation data, determine whether the target shared vehicle is located within the set three-dimensional electronic fence; If it is determined that the target shared vehicle is located within the three-dimensional electronic fence, parking of the target shared vehicle is prohibited.

[0018] According to a second aspect of this disclosure, a server is provided, including a processor and a memory, the memory being used to store a computer program, and the processor being used to execute the method as described in the first aspect of this disclosure under the control of the computer program.

[0019] According to a third aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the method described in the first aspect of this disclosure.

[0020] Through the embodiments of this disclosure, based on the positioning and elevation data of the target shared vehicle, it is possible to accurately detect whether the target shared vehicle has driven into a prohibited section of a dangerous area with at least two road segments that overlap horizontally. When the target shared vehicle is detected to have driven into a prohibited section, safety management is implemented to guide the user to drive the target shared vehicle safely away from the prohibited section. This allows for precise intervention for users who are actually driving dangerously in prohibited sections, ensuring user safety and improving the safety management efficiency of shared vehicles.

[0021] Other features and advantages of the invention will become clear from the following detailed description of exemplary embodiments of the invention with reference to the accompanying drawings. Attached Figure Description

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

[0023] Figure 1 This is a block diagram showing an example of a hardware configuration that can be used to implement embodiments of the present invention for a shared vehicle system; Figure 2 This is a flowchart of a shared vehicle management method according to an embodiment of the present disclosure; Figure 3 This is a block diagram of a server according to an embodiment of the present disclosure. Detailed Implementation

[0024] 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, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the invention.

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

[0026] Techniques, methods, and apparatus known to those skilled in the art in the relevant field may not be discussed in detail, but where appropriate, such techniques, methods, and apparatus should be considered part of the specification.

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

[0028] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0029] <Hardware Configuration> like Figure 1 As shown, the shared vehicle system 100 includes a server 1000, terminal equipment 2000, shared vehicles 3000, and a network 4000.

[0030] Server 1000 provides service points for processing, databases, and communication facilities. Server 1000 can be a monolithic server or a distributed server spanning multiple computers or computer data centers. Servers can be of various types, such as, but not limited to, web servers, news servers, mail servers, messaging servers, advertising servers, file servers, application servers, interactive servers, database servers, or proxy servers. In some embodiments, each server may include hardware, software, or embedded logical components for performing suitable functions supported or implemented by the server, or combinations of two or more such components. For example, servers may be blade servers, cloud servers, etc., or may be a server cluster consisting of multiple servers, which may include one or more of the types of servers described above, etc.

[0031] In one example, server 1000 can be like... Figure 1 As shown, the system includes a processor 1100, a memory 1200, an interface device 1300, a communication device 1400, a display device 1500, and an input device 1600. Although the server may also include speakers, microphones, etc., these components are irrelevant to the present invention and are therefore omitted here.

[0032] The processor 1100 may be, for example, a central processing unit (CPU) or a microprocessor (MCU). The memory 1200 may include, for example, ROM (Read-Only Memory), RAM (Random Access Memory), or non-volatile memory such as a hard disk. The interface device 1300 may include, for example, a USB interface, a serial interface, or an infrared interface. The communication device 1400 may be capable of wired or wireless communication. The display device 1150 may be, for example, a liquid crystal display (LCD), an LED display, or a touchscreen display. The input device 1160 may include, for example, a touchscreen or a keyboard.

[0033] In this embodiment, the terminal device 2000 is an electronic device with communication and business processing functions. The terminal device 2000 can be a mobile phone, laptop, tablet computer, PDA, or other electronic device. In one example, the terminal device 2000 is a device for managing the shared vehicles 3000; for example, it is a mobile phone with an application (APP) installed that supports the operation and management of shared vehicles.

[0034] like Figure 1As shown, the terminal device 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, etc. The processor 2100 may be a central processing unit (CPU), a microprocessor (MCU), etc. The memory 2200 may include, for example, ROM (Read-Only Memory), RAM (Random Access Memory), or non-volatile memory such as a hard disk. The interface device 2300 may include, for example, a USB interface, a headphone jack, etc. The communication device 2400 may be capable of wired or wireless communication. The display device 2500 may be, for example, an LCD screen, a touch screen, etc. The input device 2600 may include, for example, a touch screen, a keyboard, etc. Users can input / output voice information through the speaker 2700 and the microphone 2800.

[0035] The shared vehicle 3000 can be any type of vehicle, including bicycles, tricycles, electric bicycles, motorcycles, and four-wheeled passenger vehicles. In one example, the shared vehicle 3000 can also be any shared vehicle for which the right to use can be transferred by time or location for different users to share.

[0036] The shared vehicle 3000 may have an identification code to uniquely identify the item, which may be a QR code and / or a number, which may consist of numbers and / or characters.

[0037] Users can input or identify the serial number on the shared vehicle 3000 through the terminal device 2000, and then send the serial number information to the server 1000 to perform the unlocking operation.

[0038] When a user scans the QR code on the shared vehicle 3000 or enters the number using the terminal device 2000, the terminal device 2000's functions are required, such as its flashlight, location tracking, and camera functions.

[0039] like Figure 1As shown, the shared vehicle 3000 may include a processor 3100, a memory 3200, an interface device 3300, a communication device 3400, a display device 3500, an input device 3600, a positioning device 3700, a Bluetooth device 3800, etc. The processor 3100 may be a central processing unit (CPU), a microprocessor (MCU), etc. The memory 3200 may include, for example, ROM (Read-Only Memory), RAM (Random Access Memory), or non-volatile memory such as a hard disk. The interface device 3300 may include, for example, a USB interface, a headphone jack, etc. The communication device 3400 may be capable of wired or wireless communication. The output device 3500 may be a device that outputs signals, a display device such as an LCD screen, a touch screen, etc., or a speaker that outputs voice information. The input device 3600 may include, for example, a touch screen, a keyboard, etc., or a microphone that inputs voice information. The positioning device 3700 provides positioning functionality, and may be, for example, a GPS positioning module, a BeiDou positioning module, etc. Bluetooth device 3800 is used to scan for Bluetooth signals broadcast by surrounding Bluetooth devices and broadcast its own Bluetooth signal.

[0040] Network 4000 can be a wireless communication network or a wired communication network, and can be a local area network (LAN) or a wide area network (WAN). Figure 1 In the shared vehicle system shown, the shared vehicle 3000 and the server 1000, and the terminal device 2000 and the server 1000, can communicate via network 4000. Furthermore, the network 4000 on which the shared vehicle 3000 and the server 1000, and the terminal device 2000 and the server 1000 communicate, can be the same or different.

[0041] It should be understood that, despite Figure 1 Only one server 1000, terminal device 2000, and shared vehicle 3000 are shown, but this does not mean that the corresponding number is limited. The shared vehicle system 100 may contain multiple servers 1000, terminal devices 2000, and shared vehicles 3000.

[0042] Taking shared vehicle 3000 as an example of a shared electric bicycle, shared vehicle system 100 is a shared electric bicycle system. Server 1000 is used to provide all the necessary functions to support the use of shared electric bicycles. Terminal device 2000 can be a mobile phone with a shared electric bicycle application installed on it. The shared electric bicycle application can help users use shared vehicle 3000 to obtain corresponding functions, etc.

[0043] Figure 1 The shared vehicle system 100 shown is merely illustrative and is by no means intended to limit the invention, its application, or its uses.

[0044] In the embodiments applied to the present invention, although Figure 1 Only one server 1000, one terminal device 2000, and one shared vehicle 3000 are shown. However, it should be understood that in specific applications, the shared vehicle system 100 can include multiple servers 1000, multiple terminal devices 2000, and multiple shared vehicles 3000 according to actual needs.

[0045] In an embodiment of the present invention, the memory 1200 of the server 1000 is used to store instructions for controlling the processor 1100 to perform the shared vehicle positioning method based on parking area provided in the embodiment of the present invention.

[0046] Despite Figure 1 The present invention illustrates multiple devices for server 1000, terminal device 2000, and shared vehicle 3000; however, the invention may relate only to a portion of these devices. For example, server 1000 may relate only to memory 1200 and processor 1100. Terminal device 2000 may relate only to memory 2200 and processor 2100. Shared vehicle 3000 may relate only to processor 3100, memory 3200, and positioning device 3700.

[0047] In the above description, those skilled in the art can design instructions based on the scheme disclosed in this invention. How the instructions control the processor to operate is well known in the art, and therefore will not be described in detail here.

[0048] <Method Implementation> This disclosure provides a shared vehicle control method, which can be implemented by an electronic device. Specifically, the electronic device control method can be implemented by, for example... Figure 1 The server 1000 shown is implemented.

[0049] Figure 2 This is a flowchart of a shared vehicle control method according to an embodiment of the present disclosure.

[0050] like Figure 2 As shown, the shared vehicle control method includes the following steps S2100 to S2400: Step S2100: Obtain the location data and elevation data of the target shared vehicle; wherein, the elevation data represents the first elevation of the target shared vehicle.

[0051] In this embodiment, the location data can represent the horizontal position of the target shared vehicle.

[0052] In this embodiment, the target shared vehicle may be equipped with a positioning sensor and an elevation sensor. The positioning sensor is used to collect the positioning data of the target shared vehicle at a first frequency, and the elevation sensor is used to collect the elevation data of the target shared vehicle at a second frequency.

[0053] A positioning sensor can be a sensor that provides positioning functionality, such as a GPS positioning sensor or a BeiDou positioning sensor.

[0054] An elevation sensor can be a sensor capable of measuring the absolute or relative elevation of the target shared vehicle, such as a barometric pressure sensor or a motion sensor. Specifically, if the elevation sensor is a barometric pressure sensor, the first elevation can be an absolute elevation; if the elevation sensor is a motion sensor, the first elevation can be a relative elevation. The motion sensor can include a gyroscope and an accelerometer.

[0055] In embodiments where the first elevation is a relative elevation, the first elevation can be calibrated based on the horizontal position of the target shared vehicle. Specifically, the first elevation can be calibrated to zero if the horizontal position of the target shared vehicle indicates that the shared vehicle is within a predetermined calibration area. The calibration area is a pre-defined region of road segments without horizontal spatial overlap. For example, this calibration area could be the area surrounding a hazardous area.

[0056] In this embodiment, the target shared vehicle may report its latest collected location data and elevation data to the server at a third frequency, or the target shared vehicle may report the latest collected data to the server after collecting location data and / or elevation data, or the server may send a reporting instruction to the target shared vehicle at a fourth frequency, and the target shared vehicle shall report its latest collected location data and elevation data to the server in response to the reporting instruction.

[0057] In this embodiment, the target shared vehicle can be a shared two-wheeled vehicle.

[0058] Step S2200: Determine whether the target shared vehicle is in a dangerous area based on the positioning data. The dangerous area is an area where at least two road segments have horizontal spatial overlap.

[0059] In this embodiment, at least one horizontal geographical extent of a hazardous area can be pre-defined. Each hazardous area includes at least one prohibited road segment and at least one permitted road segment, with the horizontal geographical extents of the prohibited and permitted road segments overlapping. For example, the prohibited road segment could be a main road on a bridge, and the permitted road segment could be an auxiliary road under the bridge.

[0060] If the horizontal location indicated by the latest acquired location data of the target shared vehicle is within the horizontal geographical range of the danger zone, proceed to step S2300; otherwise, continue to step S2100.

[0061] Step S2300: If it is determined that the target shared vehicle is in a dangerous area, determine whether the target shared vehicle is located in a prohibited section of road within the dangerous area where the target shared vehicle is prohibited from driving, based on the elevation data.

[0062] In this embodiment, the second elevation of the restricted road section within the danger zone can be marked in advance. This second elevation can be an absolute elevation or a relative elevation of the restricted road section to the normal road section.

[0063] In some embodiments, determining whether a target shared vehicle is located in a restricted section of a dangerous area where the target shared vehicle is prohibited from driving, based on elevation data, includes: obtaining a second elevation of the restricted section of the dangerous area; determining whether the difference between the first elevation and the second elevation is within a set first error range; if so, determining that the target shared vehicle is located in the restricted section.

[0064] In this embodiment, the second elevation of the restricted road section within the danger zone can be obtained through surveying or through the location and elevation data reported by the shared vehicle during its operation.

[0065] In this embodiment, the first error range can be determined in advance based on the elevation difference between the restricted road section and the normal road section, and the first error range is smaller than the elevation difference between the restricted road section and the normal road section.

[0066] In some embodiments, the method may further include: increasing the frequency of acquiring the location data and elevation data of the target shared vehicle when it is determined that the target shared vehicle is in a dangerous area.

[0067] In an embodiment where the target shared vehicle actively reports location and elevation data to the server, the server may send an instruction to the target shared vehicle to increase the frequency of location and elevation data collection and reporting.

[0068] In an embodiment where the server sends a reporting instruction to the target shared vehicle to enable the target shared vehicle to report location data and elevation data, the server may send an instruction to the target shared vehicle to increase the frequency of location data and elevation data collection, and increase the frequency of sending reporting instructions to the target shared vehicle.

[0069] In this embodiment, a first target value for the collection frequency and / or reporting frequency may be pre-set in the target shared vehicle when the collection frequency and reporting frequency are increased, so that the target shared vehicle collects and reports data according to the corresponding first target value.

[0070] Alternatively, the server may specify a first target value for the collection frequency and / or reporting frequency in the instruction to increase the frequency, so that the target shared vehicles collect and report data according to the corresponding first target value.

[0071] This embodiment can improve the accuracy of detection results regarding whether a target shared vehicle is in a dangerous area or a restricted section of road while reducing the power consumption of the target shared vehicle, thus avoiding missed detections.

[0072] In some embodiments, the method further includes: if it is determined that the target shared vehicle is in a dangerous area, controlling the target shared vehicle to issue a second voice warning to remind the user not to enter the restricted area.

[0073] In this embodiment, the server may send a second warning command to the target shared vehicle, and the target shared vehicle may respond to the second warning command by issuing a second voice warning to remind the user not to enter the restricted area. For example, issuing a second voice warning to remind the user not to enter the restricted area may be by playing a voice reminder such as "Danger, do not enter" or by playing a second prompt tone.

[0074] This embodiment can guide users to avoid driving the target shared vehicle into restricted areas.

[0075] Step S2400: When the target shared vehicle is in a restricted area, implement safety control measures on the target shared vehicle to guide the user to drive the target shared vehicle safely away from the restricted area.

[0076] In this embodiment, the safety management of the target shared vehicle includes at least one of the following: controlling the target shared vehicle to issue a first voice warning to remind the user to leave the restricted area; controlling the target shared vehicle to reduce its speed; and controlling the target shared vehicle to stop power output.

[0077] In an embodiment where safety management of a target shared vehicle includes controlling the target shared vehicle to issue a first voice warning to remind the user to leave a restricted area, the server may send a first warning command to the target shared vehicle, and the target shared vehicle, in response to the first warning command, issues a first voice warning to remind the user that it has entered a restricted area. For example, issuing the first voice warning to remind the user that it has entered a restricted area may be playing a voice reminder such as "You have entered a restricted area, please pay attention to safety and leave as soon as possible," or it may be playing a first prompt tone.

[0078] In an embodiment of safety management of a target shared vehicle, including controlling the target shared vehicle to reduce its speed, the server may send a speed reduction command to the target shared vehicle, and the target shared vehicle responds to the speed reduction command by reducing its own speed.

[0079] In one example, in response to the speed reduction command, the target shared vehicle may reduce its speed to a set speed. This set speed may be pre-set in the target shared vehicle or included in the speed reduction command. If the target shared vehicle's speed is lower than the set speed, no adjustment to the target shared vehicle's speed is required.

[0080] In this embodiment, the speed of the target shared vehicle can be reduced by limiting the maximum output power of the target shared vehicle.

[0081] Specifically, the maximum output power of the target shared vehicle can be adjusted from a first set value to a second set value, wherein the first set value is greater than the second set value.

[0082] In another example, the target shared vehicle may respond to the speed reduction command by reducing its speed by a set percentage. For instance, if the current speed is v1 and the set percentage is A, reducing the speed by the set percentage will result in the target shared vehicle's speed being v1*(1-A).

[0083] In this embodiment, the speed of the target shared vehicle can be reduced by limiting the current output power of the target shared vehicle.

[0084] Specifically, the current output power of the target shared vehicle can be adjusted from a third setting value to a fourth setting value, where the third setting value is greater than the fourth setting value, and the fourth setting value can be determined based on the third setting value and a setting percentage.

[0085] In embodiments where safety management of a target shared vehicle includes controlling the target shared vehicle to stop power output, the current power output of the target shared vehicle may be adjusted to zero.

[0086] Through the embodiments of this disclosure, based on the positioning and elevation data of the target shared vehicle, it is possible to accurately detect whether the target shared vehicle has driven into a prohibited section of a dangerous area with at least two road segments that overlap horizontally. When the target shared vehicle is detected to have driven into a prohibited section, safety management is implemented to guide the user to drive the target shared vehicle safely away from the prohibited section. This allows for precise intervention for users who are actually driving dangerously in prohibited sections, ensuring user safety and improving the safety management efficiency of shared vehicles.

[0087] In some embodiments, the method further includes: detecting whether the target shared vehicle has left the restricted road section; and stopping the safety control of the target shared vehicle if the target shared vehicle leaves the restricted road section.

[0088] In one embodiment, after detecting the difference between the first and second elevations of the target shared vehicle based on elevation data within a first error range, and then detecting the difference between the first elevation of the target shared vehicle and the third elevation of a normal road segment within the danger zone within a set second error range, it can be determined that the target shared vehicle has left the restricted road segment. Wherein, the horizontal geographical extent of the restricted road segment and the normal road segment within any danger zone overlaps.

[0089] In another embodiment, if the difference between the first elevation and the second elevation of the target shared vehicle is detected to be within a first error range based on elevation data, and then it is detected that the difference between the first elevation and the second elevation of the target shared vehicle exceeds the first error range, then it can be determined that the target shared vehicle has left the restricted road section.

[0090] In another embodiment, after detecting the difference between the first and second elevations of the target shared vehicle based on elevation data within a first error range, and then detecting that the target shared vehicle has left the danger zone based on positioning data, it can be determined that the target shared vehicle has left the restricted road section.

[0091] In this embodiment, stopping the safety control of the target shared vehicle may include: controlling the target shared vehicle to stop issuing the first voice warning and controlling the target shared vehicle to resume driving speed; controlling the target shared vehicle to resume power output.

[0092] In an embodiment where safety control of the target shared vehicle is stopped, including controlling the target shared vehicle to resume its driving speed, the maximum output power of the target shared vehicle may be adjusted from a second set value to a first set value, or the current output power of the target shared vehicle may be adjusted to match the rotation angle of the throttle.

[0093] In an embodiment where safety control of the target shared vehicle is stopped, including controlling the target shared vehicle to restore power output, the current output power of the target shared vehicle may be adjusted to match the rotation angle of the throttle.

[0094] This embodiment ensures that the target shared vehicle can drive normally on normal road sections, ensuring that the user's driving experience on normal road sections is not affected.

[0095] In some embodiments, the method may further include reducing the frequency of acquiring the location and elevation data of the target shared vehicle when the target shared vehicle leaves a dangerous area or a restricted road section.

[0096] In this embodiment, it can be determined that the target shared vehicle has left the restricted road section after the difference between the first and second elevations of the target shared vehicle is detected to be within a first error range based on elevation data, and then the difference between the first elevation of the target shared vehicle and the third elevation of the normal road section within the danger zone is detected to be within a set second error range. Alternatively, it can be determined that the target shared vehicle has left the restricted road section after the difference between the first and second elevations of the target shared vehicle is detected to be within the first error range based on elevation data, and then the difference between the first and second elevations of the target shared vehicle is detected to be outside the first error range. Finally, it can be determined that the target shared vehicle has left the restricted road section after the difference between the first and second elevations of the target shared vehicle is detected to be within the first error range based on elevation data, and then the target shared vehicle is detected to have left the danger zone based on positioning data.

[0097] In addition, if the location data detects that the target shared vehicle has entered the danger zone, and then the location data also detects that the target shared vehicle is no longer in the danger zone, then it can be determined that the target shared vehicle has left the danger zone.

[0098] In an embodiment where the target shared vehicle actively reports location and elevation data to the server, the server may send a command to the target shared vehicle to reduce the frequency of location and elevation data collection and reporting.

[0099] In an embodiment where the server sends a reporting instruction to the target shared vehicle to cause the target shared vehicle to report location data and elevation data, the server may send a command to the target shared vehicle to reduce the frequency of location data and elevation data collection, and reduce the frequency of sending reporting instructions to the target shared vehicle.

[0100] In this embodiment, a second target value for the collection frequency and / or reporting frequency may be pre-set in the target shared vehicle, under the condition of reducing the collection frequency and reporting frequency, so that the target shared vehicle collects and reports data according to the corresponding second target value.

[0101] Alternatively, the server may specify a second target value for the collection frequency and / or reporting frequency in the instruction to reduce the frequency, so that the target shared vehicles collect and report data according to the corresponding second target value.

[0102] This embodiment can reduce the power consumption of the target shared vehicle.

[0103] In some embodiments, the method further includes sending a reminder message to a terminal device using the target shared vehicle indicating that the target shared vehicle is driving on a restricted road section.

[0104] In this embodiment, the terminal device using the target shared vehicle can be a terminal device that unlocks the target shared vehicle by scanning its identification code.

[0105] In this embodiment, the reminder information may include text information to remind the user that they have entered a restricted road section, road section information of the restricted road section, and travel time information of the target shared vehicle in the restricted road section (including the time of entry into the restricted road section and the travel time in the restricted road section).

[0106] This embodiment also allows users to be alerted that they have entered a restricted area by using the terminal device of the target shared vehicle.

[0107] In some embodiments, the method further includes: when the terminal device ends its use of the target shared vehicle, generating penalty information based on the prohibited road sections traveled by the target shared vehicle during the current use; and sending the penalty information to the terminal device for display.

[0108] In this embodiment, the penalty information may include the penalty amount, and may also include information for educating users about safety.

[0109] In this embodiment, penalty information can be generated based on the number of times the target shared vehicle enters a restricted road section.

[0110] Furthermore, penalty information can be generated based on the duration of the target shared vehicle's travel on restricted road sections.

[0111] Furthermore, the weight of each restricted road segment can be preset, and penalty information can be generated based on the weight of the restricted road segments traveled by the target shared vehicle during this use.

[0112] This embodiment allows for the subsequent punishment of users to remind them not to enter restricted areas again.

[0113] In some embodiments, the method further includes: controlling the terminal device to display a shared vehicle map and highlighting dangerous areas in the shared vehicle map.

[0114] In this embodiment, dangerous areas with restricted road sections can be marked in advance on the shared vehicle map displayed on the terminal device to remind users not to drive into the restricted road sections.

[0115] In some embodiments, the method may further include: determining whether the target shared vehicle is parked within a set three-dimensional electronic fence based on positioning data and elevation data; allowing the target shared vehicle to lock if it is determined that the target shared vehicle is within the three-dimensional electronic fence; and prohibiting the target shared vehicle from locking if it is determined that the target shared vehicle is outside the three-dimensional electronic fence.

[0116] In this embodiment, when the terminal device using the target shared vehicle displays a return page or receives a lock request from the terminal device using the target shared vehicle, the system determines whether the target shared vehicle is parked within a set three-dimensional electronic fence based on location data and elevation data, and controls the lock of the target shared vehicle if it is determined that the target shared vehicle is within the three-dimensional electronic fence.

[0117] In this embodiment, at least one three-dimensional electronic fence can be pre-set, and each three-dimensional electronic fence has a corresponding horizontal geographical range and a fourth elevation.

[0118] If the horizontal position indicated by the location data of the target shared vehicle is within the horizontal geographical area of ​​the 3D electronic fence, and the difference between the first elevation indicated by the elevation data and the fourth elevation of the 3D electronic fence is within a set third error range, then the target vehicle can be determined to be within the 3D electronic fence. If the horizontal position indicated by the location data of the target shared vehicle is outside the horizontal geographical area of ​​the 3D electronic fence, or if the difference between the first elevation indicated by the elevation data and the fourth elevation of the 3D electronic fence exceeds the third error range, then the target vehicle can be determined to be outside the 3D electronic fence.

[0119] This embodiment can accurately determine whether a target shared vehicle is located within the three-dimensional electronic fence when the three-dimensional electronic fence and the no-parking zone overlap horizontally, thereby guiding the user to park the target shared vehicle within the three-dimensional electronic fence for return.

[0120] <Electronic Device Examples> This embodiment provides an electronic device, such as... Figure 3 As shown, the electronic device 3000 may include a processor 3100 and a memory 3200. The memory 3200 is used to store computer programs, and the processor 3100 is used to control the electronic device to execute the methods of any embodiment of this disclosure under the control of the computer programs.

[0121] <Example of a readable storage medium> This embodiment provides a computer-readable storage medium storing a computer program that, when executed by a processor, performs the methods described in any of the method embodiments of this disclosure.

[0122] This invention can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of the invention.

[0123] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination of the foregoing. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

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

[0125] The computer program instructions used to perform the operations of this invention may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status 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++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuits, such as programmable logic circuits, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), are personalized by utilizing state information from computer-readable program instructions. These electronic circuits can execute computer-readable program instructions to implement various aspects of the present invention.

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

[0127] 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 apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0128] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be 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 perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0129] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions. It will be known to those skilled in the art that implementation in hardware, implementation in software, and implementation using a combination of software and hardware are equivalent.

[0130] The various embodiments of the present invention have been described above. These descriptions are exemplary and not exhaustive, and are 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 chosen to best explain the principles, practical application, or technical improvements to the embodiments in the market, or to enable others skilled in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.

Claims

1. A shared vehicle control method, characterized in that, include: Acquire the location data and elevation data of the target shared vehicle; wherein the elevation data represents the first elevation of the target shared vehicle; Based on the location data, it is determined whether the target shared vehicle is in a dangerous area, wherein the dangerous area is an area where at least two road segments have horizontal spatial overlap; If it is determined that the target shared vehicle is in the danger zone, the elevation data is used to determine whether the target shared vehicle is located in a restricted section of the danger zone where the target shared vehicle is prohibited from driving. When the target shared vehicle is in the restricted road section, safety management is implemented for the target shared vehicle to guide the user to drive the target shared vehicle safely away from the restricted road section.

2. The method according to claim 1, characterized in that, The step of determining whether the target shared vehicle is located within the danger zone and on a prohibited road section where the target shared vehicle is prohibited from driving, based on the elevation data, includes: Obtain the second elevation of the restricted road section within the danger zone; Determine whether the difference between the first elevation and the second elevation is within a set first error range. If so, determine that the target shared vehicle is located in the restricted road section.

3. The method according to claim 1, characterized in that, The security management of the target shared vehicle includes at least one of the following: The target shared vehicle is controlled to issue a first voice warning to remind the user to leave the restricted road section; Control the target shared vehicle to reduce its driving speed; Control the target shared vehicle to stop power output.

4. The method according to claim 1, characterized in that, The method further includes: Detect whether the target shared vehicle has left the restricted road section; Once the target shared vehicle leaves the restricted road section, the safety management of the target shared vehicle shall cease.

5. The method according to claim 4, characterized in that, The detection of whether the target shared vehicle has left the restricted road section includes: Obtain the second elevation of the restricted road section within the danger zone; determine whether the difference between the first elevation and the second elevation is within a set first error range; if not, determine that the target shared vehicle has left the restricted road section; or, Obtain the third elevation of the normal road section within the danger zone; determine whether the difference between the first elevation and the third elevation is within a set second error range; if so, determine that the target shared vehicle has left the prohibited road section; or, If the location data determines that the target shared vehicle has left the dangerous area, then the location data indicates that the target shared vehicle has left the restricted road section.

6. The method according to claim 1, characterized in that, The method further includes: If it is determined that the target shared vehicle is in the dangerous area, the frequency of acquiring the location data and elevation data of the target shared vehicle shall be increased.

7. The method according to claim 1, characterized in that, The method further includes: If it is determined that the target shared vehicle is in the dangerous area, the system controls the target shared vehicle to issue a second voice warning to remind the user not to enter the restricted area.

8. The method according to claim 1, characterized in that, The method further includes: Send a reminder message to the terminal device using the target shared vehicle indicating that the target shared vehicle is traveling on the restricted road section.

9. The method according to claim 1, characterized in that, The method further includes: When the terminal device finishes using the target shared vehicle, penalty information is generated based on the prohibited road sections traveled by the target shared vehicle during this use. The penalty information is sent to the terminal device for display.

10. The method according to claim 1, characterized in that, The method further includes: The terminal device controlling the use of the target shared vehicle displays a map of the shared vehicle and highlights the dangerous areas in the map.

11. The method according to claim 1, characterized in that, The method further includes: Based on the positioning data and the elevation data, determine whether the target shared vehicle is located within the set three-dimensional electronic fence; If it is determined that the target shared vehicle is within the three-dimensional electronic fence, the target shared vehicle is allowed to be locked; If it is determined that the target shared vehicle is outside the three-dimensional electronic fence, the target shared vehicle shall be prohibited from being locked.

12. A server, characterized in that, It includes a processor and a memory, the memory being used to store a computer program, and the processor being used, under the control of the computer program, to execute the method as described in any one of claims 1 to 11.

Images