Shared vehicle management method and device

By introducing user levels and parking spot type classifications into the shared vehicle management system, differentiated parking management strategies are provided, solving the problem of lack of differentiated user management in shared vehicle management and improving operational efficiency and user experience.

CN121789501APending Publication Date: 2026-04-03ZHEJIANG YUANXIAOLI INFORMATION TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-12-23
Publication Date
2026-04-03

AI Technical Summary

Technical Problem

The existing shared vehicle management system lacks differentiated management strategies for different user groups, resulting in reduced operational efficiency and user experience.

Method used

By introducing a user level classification and parking spot type division mechanism into the shared vehicle management system, differentiated parking guidance and management strategies, including display, penalty or preferential measures, can be provided based on the matching of user level and parking spot type.

Benefits of technology

It has improved the sophistication of shared vehicle parking management, reduced management costs, enhanced operational efficiency and user satisfaction, and reduced dispatch costs caused by indiscriminate parking.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121789501A_ABST
    Figure CN121789501A_ABST
Patent Text Reader

Abstract

The invention provides a shared vehicle management method and device, and relates to the technical field of shared vehicle management, and the method comprises the steps: obtaining the position information of a shared vehicle in response to a vehicle returning request sent by a user terminal; determining a current parking point and the type of the parking point based on the position information; judging whether the user level corresponding to the user terminal is matched with the type of the parking spot; and if yes, feeding back prompt information of successful vehicle returning to the user terminal. According to the shared vehicle management method and device provided by the invention, the user needs to return the vehicle in the parking spot matched with the user grade, the user can be effectively guided to return the vehicle in the planned parking spot normatively, the scheduling cost caused by blind parking is further reduced, and meanwhile, based on the user grade and the type of the parking spot, the user experience is improved. In addition, the method can effectively improve the refinement level of parking management of shared vehicles, reduces the management cost, provides differentiated services for users of different user levels, and remarkably improves the operation efficiency and user satisfaction.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the technical field of shared vehicle management, and in particular to a method and apparatus for managing shared vehicles. Background Technology

[0002] With the widespread deployment of shared vehicles in cities, users have gained a convenient mode of transportation, but this has also led to serious problems with haphazard parking. To regulate parking order, operating platforms typically mark recommended parking areas—i.e., parking spots—on maps using precise positioning and electronic fence technology, guiding users to "park at designated spots." Some cities have also installed hardware such as Bluetooth beacons in parking spaces, requiring vehicles to recognize the signal within designated parking spaces before they can be locked and returned; otherwise, they cannot be locked or returned, ensuring that shared vehicles are parked in legal areas. Furthermore, the service agreements of shared vehicle platforms generally explicitly require users to park vehicles in recommended parking areas or parking spots stipulated by relevant laws and regulations; otherwise, the platform can charge illegal parking management fees or dispatch fees for parking outside designated areas or returning vehicles illegally. These measures have regulated the parking order of shared vehicles to some extent; however, most treat all users the same, meaning all users are subject to the same management strategy, lacking strategies for differentiated management for different user groups.

[0003] In reality, different users, such as frequent users and members who pay monthly service fees, have different management needs for parking spots. Therefore, the approach of using the same management strategy for all users in related technologies is difficult to meet the parking or return needs of different users, thereby reducing the operational efficiency of shared vehicles. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to provide a method and apparatus for managing shared vehicles to alleviate the above-mentioned technical problems.

[0005] In a first aspect, embodiments of the present invention provide a method for managing shared vehicles, the method comprising: responding to a return request sent by a user terminal and obtaining location information of the shared vehicle; determining the current parking spot and the type of the parking spot based on the location information; determining whether the user level corresponding to the user terminal matches the type of the parking spot; and if so, sending a successful return notification to the user terminal.

[0006] In conjunction with the first aspect, the present invention provides a first possible implementation of the first aspect, wherein the method further includes: responding to a parking spot query request and obtaining the user level corresponding to the user terminal; querying parking spots within a preset distance range that match the user level; and displaying the location information of the queried parking spots through a graphical user interface.

[0007] In conjunction with the first possible implementation of the first aspect, this embodiment of the invention provides a second possible implementation of the first aspect, wherein the step of displaying the location information of the queried parking spot through a graphical user interface includes: displaying the location information of the queried parking spot that matches the user level through a graphical user interface; and not displaying the location information for parking spots that do not match the user level.

[0008] In conjunction with the first possible implementation of the first aspect, this embodiment of the invention provides a third possible implementation of the first aspect, wherein the step of determining whether the user level corresponding to the user terminal matches the type of the parking spot includes: if the type of the parking spot is a first type, then determining that the user level corresponding to the user terminal matches the type of the parking spot, wherein the parking spot of the first type allows users of all user levels to return the vehicle.

[0009] In conjunction with the third possible implementation of the first aspect, this embodiment of the invention provides a fourth possible implementation of the first aspect, wherein the step of determining whether the user level corresponding to the user terminal matches the type of the parking spot further includes: if the type of the parking spot is a second type, then determining whether the user level corresponding to the user terminal is a second level or a third level; wherein the parking spot of the second type allows users of the second level and the third level to return the vehicle; and, setting a vehicle return penalty rule for users of the first level; if yes, determining that the user level corresponding to the user terminal matches the type of the parking spot; if no, determining that the user level corresponding to the user terminal does not match the type of the parking spot, and displaying the vehicle return penalty rule through a graphical user interface.

[0010] In conjunction with the fourth possible implementation of the first aspect, this embodiment of the invention provides a fifth possible implementation of the first aspect, wherein the step of determining whether the user level corresponding to the user terminal matches the type of the parking spot further includes: if the type of the parking spot is a third type, then determining whether the user level corresponding to the user terminal is the third level; wherein the third type of parking spot allows users of the third level to return the vehicle, and users of the first level and the second level are prohibited from returning the vehicle; if yes, it is determined that the user level corresponding to the user terminal matches the type of the parking spot; if no, it is determined that the user level corresponding to the user terminal does not match the type of the parking spot, and a prompt message prohibiting returning the vehicle is displayed through a graphical user interface.

[0011] In conjunction with the fifth possible implementation of the first aspect, this embodiment of the invention provides a sixth possible implementation of the first aspect, wherein the step of querying parking spots matching the user level within a preset distance range includes: if the user level is the first level and the second level, then querying other parking spots within the preset distance range other than the first type, the second type and the third type; if the user level is the third level, then querying the parking spots within the preset distance range.

[0012] In conjunction with the fifth possible implementation of the first aspect, this embodiment of the invention provides a seventh possible implementation of the first aspect, wherein the above method further includes: acquiring historical order heat information; the historical order heat information being used to characterize the peak usage period of the shared vehicle; and adjusting the type of the parking spot based on the historical order heat information.

[0013] In conjunction with the first aspect, this invention provides an eighth possible implementation of the first aspect, wherein the method further includes: obtaining user identity information, searching for consumption records and historical vehicle usage records corresponding to the user identity information; and determining the user level corresponding to the user identity information based on the consumption records and the historical vehicle usage records.

[0014] Secondly, embodiments of the present invention also provide a management device for shared vehicles, the device comprising: a response module, configured to respond to a return request sent by a user terminal and obtain location information of the shared vehicle; a determination module, configured to determine the current parking spot and the type of the parking spot based on the location information; a judgment module, configured to determine whether the user level corresponding to the user terminal matches the type of the parking spot; and a prompt module, configured to provide a prompt message to the user terminal indicating successful return of the vehicle when the judgment result of the judgment module is yes.

[0015] The embodiments of the present invention bring the following beneficial effects: This invention provides a method and apparatus for managing shared vehicles, which can respond to a return request sent by a user terminal and obtain the location information of the shared vehicle; determine the current parking spot and the type of parking spot based on the location information; determine whether the user level corresponding to the user terminal matches the type of parking spot; if so, send a successful return message to the user terminal; that is, the user needs to return the vehicle at a parking spot that matches their user level, which can effectively guide users to return the vehicle in a standardized manner within the planned parking spots, thereby reducing the scheduling costs caused by blind parking. At the same time, based on the user level and the type of parking spot, it can also effectively improve the precision of parking management of shared vehicles, reduce management costs, and provide differentiated services for users of different user levels, significantly improving operational efficiency and user satisfaction.

[0016] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0017] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0018] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0019] Figure 1 A flowchart illustrating a shared vehicle management method provided in an embodiment of the present invention; Figure 2 A schematic diagram of the structure of a shared vehicle management device provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0021] Currently, the parking and return management of shared vehicles adopts the same management strategy for all users, lacking refined segmentation for differentiated management of different user groups, which makes it difficult to improve the operational efficiency and user experience of shared vehicles.

[0022] Based on this, the shared vehicle management method and device provided by the embodiments of the present invention can effectively improve the level of refinement of shared vehicle parking and return management, provide refined and differentiated services for users at different levels, and thus significantly improve operational efficiency and user satisfaction.

[0023] To facilitate understanding of this embodiment, a management method for shared vehicles disclosed in this embodiment of the invention will first be described in detail.

[0024] In one possible implementation, this invention provides a method for managing shared vehicles. This method can be applied to a backend server for shared vehicle operation or to a user terminal. Users install a corresponding application (APP) for the shared vehicles on their terminals, register as legitimate users through the APP, and then log in to the backend server to use the shared vehicles. Furthermore, the shared vehicles in this invention include shared bicycles, shared electric bicycles, shared cars, etc., specifically, such as... Figure 1 The flowchart shown illustrates a method for managing shared vehicles, which includes the following steps: Step S102: Respond to the vehicle return request sent by the user terminal and obtain the location information of the shared vehicle; Step S104: Determine the current parking spot and its type based on the location information; In actual use, users can unlock shared vehicles by scanning the vehicle identification, such as a QR code containing vehicle information, using their user terminals. After use, users need to park the shared vehicle at a pre-planned parking spot. This parking spot refers to a pre-planned recommended parking area. To standardize vehicle returns and avoid haphazard parking, users are typically only allowed to return vehicles within the designated parking area. Returns outside of designated areas usually incur a dispatch fee. Therefore, in this embodiment, upon receiving a return request from a user via their user terminal, the system further obtains the shared vehicle's location information to determine if the current location is within the designated parking area. If so, the system further determines the current parking spot and its type based on the location information.

[0025] Step S106: Determine whether the user level corresponding to the user terminal matches the type of the parking spot; Step S108: If yes, send a message to the user terminal indicating successful vehicle return.

[0026] In practical use, this embodiment of the invention sets up different types of parking spots within the operating area of ​​the shared vehicles to facilitate more refined management of the shared vehicle operation based on traffic flow, geographical location, and management requirements. Furthermore, this embodiment of the invention also classifies users into different levels, such as based on user recharge consumption and usage frequency, and matches different types of parking spots with user types to improve the precision of parking management based on user level and parking spot type. In step S106, if it is determined that the user level corresponding to the user terminal does not match the parking spot type, the user is prompted that returning the vehicle is prohibited at the current parking spot, or that a certain dispatch fee needs to be charged, etc., to guide the user to the corresponding parking spot for returning the vehicle.

[0027] Therefore, the shared vehicle management method provided by this invention can respond to a user terminal's return request and obtain the shared vehicle's location information; determine the current parking spot and its type based on the location information; determine whether the user terminal's user level matches the parking spot type; if so, send a successful return notification to the user terminal; that is, users need to return the vehicle at a parking spot that matches their user level, which can effectively guide users to return the vehicle in a standardized manner within the planned parking spots, thereby reducing the scheduling costs caused by blind parking. At the same time, based on the user level and the parking spot type, it can also effectively improve the precision of shared vehicle parking management, reduce management costs, and provide differentiated services for users with different user levels, significantly improving operational efficiency and user satisfaction.

[0028] In practical use, the parking spot types in this embodiment of the invention include a first type, a second type, and a third type; the user levels include a first level, a second level, and a third level; wherein, the first type of parking spot allows users of the first level, the second level, and the third level to return the vehicle; the second type of parking spot allows users of the second level and the third level to return the vehicle; and, a return penalty rule is set for users of the first level; the third type of parking spot allows users of the third level to return the vehicle, and users of the first level and the second level are prohibited from returning the vehicle.

[0029] Typically, the parking spots mentioned above can be categorized into the first, second, and third types within the operating range of shared vehicles based on factors such as traffic flow, geographical location, and management requirements. In addition to the above-mentioned parking spot categories, ordinary parking spots are also included. Furthermore, the backend server can mark each parking spot, such as whether it belongs to the first, second, or third type of special parking spot, or whether it is marked as an ordinary parking spot.

[0030] Furthermore, the aforementioned user levels are typically determined based on a user's consumption records and historical vehicle usage records. Specifically, the backend server can periodically obtain user identity information, search for the corresponding consumption records and historical vehicle usage records, and determine the user level corresponding to the user identity information based on the consumption records and historical vehicle usage records. For example, user spending records can be accumulated, or user usage frequency can be statistically analyzed. Alternatively, user levels can be dynamically assessed based on recent (e.g., the frequency of shared vehicle use and spending amount) data. For instance, based on accumulated spending, a user can be classified as a higher level, such as Level 2 or Level 3, for a future period. Typically, Level 1 users are considered ordinary users. As a user's level increases, their parking privileges also increase. For example, for Type 1 parking spots, Level 1, Level 2, and Level 3 users are allowed to return vehicles; that is, all users can legally return vehicles at Type 1 parking spots without incurring additional fees. For Type 2 parking spots, only Level 2 and Level 3 users are allowed to return vehicles. Furthermore, Level 1 users are subject to return penalty rules; for example, if a Level 1 user returns a vehicle at a Type 2 parking spot, it is considered illegal parking and a dispatch penalty fee will be charged. For Type 3 parking spots, neither Level 1 nor Level 2 users have permission to return vehicles; these spots are only open to Level 3 users.

[0031] In practical use, the first type of parking spots mentioned above mostly refer to parking spots with relatively poor mobility of shared vehicles. To avoid shared vehicles spending too much time idle at these first-type parking spots, operators usually discourage returning vehicles at them. Furthermore, the second type of parking spots can be parking spots in pre-planned target areas, such as dedicated parking spots set up in industrial parks, office buildings, and commercial areas. Of course, in addition to the second type of parking spots, there can also be regular parking spots in these target areas. Typically, the corresponding second-level users can be associated users in the target area, such as staff or resident personnel. Users can apply to register as second-level users through their user terminals. Furthermore, the third type of parking spots can be parking spots specifically for third-level or advanced-level users; other levels of users are prohibited from returning or using the vehicles.

[0032] Typically, the backend server can mark each user's user level. When a user returns the car, the backend server can determine whether the user level matches the type of the current parking spot, and then determine whether the user is allowed to return the car.

[0033] Specifically, based on the aforementioned user level and parking spot type, in step S106, when determining whether the user level corresponding to the user terminal matches the parking spot type, if the parking spot type is the first type, then it is determined that the user level corresponding to the user terminal matches the parking spot type, that is, parking spots of the first type allow users of the first, second, and third levels to return the car; furthermore, if the parking spot type is the second type, then it is determined whether the user level corresponding to the user terminal is the second or third level; wherein, parking spots of the second type allow users of the second and third levels to return the car; and, a return penalty rule is set for users of the first level; if yes, it is determined that the user level corresponding to the user terminal matches the parking spot type; if no, it is determined that the user level corresponding to the user terminal does not match the parking spot type, and the return penalty rule is displayed through the graphical user interface. That is, the second type of parking spot allows users of the second and third levels to return their vehicles; and a penalty rule is set for users of the first level to return their vehicles; further, if the parking spot type is the third type, it is determined whether the user level corresponding to the user terminal is the third level; wherein, the third type of parking spot allows users of the third level to return their vehicles, and users of the first and second levels are prohibited from returning their vehicles; if yes, it is determined that the user level corresponding to the user terminal matches the type of parking spot; if no, it is determined that the user level corresponding to the user terminal does not match the type of parking spot, and a prompt message prohibiting the return of vehicles is displayed through the graphical user interface, that is, the third type of parking spot only allows users of the third level to return their vehicles, and refuses users of other levels to return their vehicles. When other users return their vehicles at the third type of parking spot, they can be prompted that the current parking spot is only open to users of the third level, and other parking spots can be recommended.

[0034] Furthermore, users can also query available parking spots through their user terminals, such as before returning the car or when they need to use the car. Therefore, in this embodiment of the invention, in response to a parking spot query request, the system can obtain the user level corresponding to the user terminal; query parking spots within a preset distance range that match the user level; and display the location information of the queried parking spots through a graphical user interface.

[0035] Specifically, if the user level is Level 1 or Level 2, then other parking spots within a preset distance range, excluding Type 1, Type 2, and Type 3, will be queried; if the user level is Level 3, then parking spots within a preset distance range will be queried.

[0036] Furthermore, in this embodiment of the invention, when displaying the queried parking spots, the location information of parking spots matching the user's level can be displayed through a graphical user interface; and the location information of parking spots that do not match the user's level is not displayed. That is, when a user queries available parking spots, in this embodiment of the invention, parking spots are dynamically displayed according to the user's level. Typically, for users at the first and second levels, only ordinary parking spots are displayed, that is, the markers for the aforementioned first, second, and third types of parking spots are hidden and not displayed. For users at the third level, all parking spots within a preset distance range are displayed, that is, ordinary parking spots and parking spots of the first, second, and third types are displayed. For parking spots of the third type, special markers can be displayed, such as highlighting, or using other colors or rendering methods for prompt display. For parking spots of the first and second types, prompts can be displayed or not, which can be set according to the actual usage situation. This embodiment of the invention does not limit this.

[0037] Furthermore, in this embodiment of the invention, historical order heat map information can also be obtained; this information is used to characterize peak usage periods for shared vehicles; and the type of parking spot can be adjusted based on this information. For example, the backend server monitors the usage of each parking spot in real time and can dynamically adjust the category or opening status of the parking spot according to the time period and historical order heat map information. For example, during peak commuting hours, some ordinary parking spots can be temporarily upgraded to third-type parking spots to prioritize access for users with higher user levels, thereby alleviating local parking pressure. Simultaneously, capacity thresholds can be set for parking spots and warnings can be issued; for example, when the number of shared vehicles parked in a certain area approaches saturation, an alert is triggered or a dispatch instruction is automatically generated.

[0038] Furthermore, the backend server in this embodiment of the invention can analyze parking spot usage data and user behavior to support intelligent management of shared vehicles. For example, it can provide data support by collecting data such as parking traffic, occupancy rate, and user level distribution at each parking spot, providing a basis for planning and adjusting parking spots, and optimizing the distribution and quantity of various types of parking spots based on historical data. It also provides real-time alerts and scheduling: for example, for a configured operating area, it can automatically issue an alert when the number of parked shared vehicles exceeds a certain proportion, and can coordinate with maintenance personnel to promptly clear or guide users to park shared vehicles in nearby vacant parking spots. Finally, it enables user management: for example, the backend server dynamically tracks user usage of shared vehicles, regularly reviews the list of third-level users, and adjusts their permission levels if it finds a decrease in user activity or an increase in violation rate. It can also provide promotion channels for high-performing ordinary users, such as encouraging first-level users to upgrade. In addition, the backend server can flexibly modify parking spot classifications, electronic fence ranges, and parking fee settings according to urban management requirements and operational strategies, enabling dynamic distribution of operational strategies without requiring client upgrades each time.

[0039] In summary, the shared vehicle management method provided by this invention, by introducing a hierarchical management mechanism and dynamic adjustment strategy for parking spots and user levels during the operation of shared vehicles, has the following beneficial effects: (1) Standardize parking order: Set different parking access permissions for high-value users, such as the third-level users mentioned above and ordinary users, effectively guide users to park in a standardized manner within the planned operation area, and reduce fines and manual dispatch costs caused by users blindly parking shared vehicles.

[0040] (2) Reduce illegal parking: Since the back-end server can automatically identify the user level and remind or punish illegal parking behavior, it greatly suppresses the parking behavior of users in no-parking zones or unplanned areas and improves the overall parking compliance rate.

[0041] (3) Improve user satisfaction: Provide exclusive parking privileges for users with higher user levels, such as setting up third-level parking spots for third-level users, so that third-level users can use some parking spots where returning cars is usually prohibited, thereby enhancing user experience and stickiness; at the same time, let ordinary users know where they can park, reducing anxiety about finding parking spots.

[0042] (4) Optimize resource utilization: Dynamic visibility and access control enable operators to manage parking resources in a “tidal” elastic manner. For example, during peak hours, priority can be given to ensuring the parking needs of high-value users (users with higher user levels), while during off-peak hours, more ordinary parking spots can be opened to balance vehicle distribution and reduce local congestion.

[0043] (5) Improve operational efficiency: The back-end server can achieve automated management to reduce the need for manual intervention. Through data analysis and early warning mechanisms, it can promptly detect and respond to abnormalities at parking spots, thereby improving dispatch efficiency and vehicle turnover rate.

[0044] Therefore, the shared vehicle management method provided by the embodiments of the present invention can effectively improve the level of precision in shared vehicle parking management by utilizing intelligent user identification and parking point management strategies, reduce management costs, and provide differentiated services for users at different levels, thereby significantly improving operational efficiency and user satisfaction.

[0045] Furthermore, based on the above embodiments, this invention also provides a management device for shared vehicles, such as... Figure 2 The diagram shows a structural schematic of a shared vehicle management device, which includes: The response module 20 is used to respond to the vehicle return request sent by the user terminal and obtain the location information of the shared vehicle; The determining module 22 is used to determine the current parking spot and the type of the parking spot based on the location information; The judgment module 24 is used to determine whether the user level corresponding to the user terminal matches the type of the parking spot; The prompt module 26 is used to send a prompt message to the user terminal indicating that the vehicle has been successfully returned when the judgment result of the judgment module is yes.

[0046] The shared vehicle management device provided in this embodiment of the invention has the same technical features as the shared vehicle management method provided in the above embodiments, so it can also solve the same technical problems and achieve the same technical effects.

[0047] Furthermore, embodiments of the present invention also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above method.

[0048] This invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the above-described method.

[0049] Furthermore, embodiments of the present invention also provide a schematic diagram of the structure of an electronic device, such as... Figure 3 The diagram shows the structure of the electronic device, which includes a processor 31 and a memory 30. The memory 30 stores computer-executable instructions that can be executed by the processor 31, and the processor 31 executes the computer-executable instructions to implement the above-described method.

[0050] exist Figure 3 In the illustrated embodiment, the electronic device further includes a bus 32 and a communication interface 33, wherein the processor 31, the communication interface 33, and the memory 30 are connected via the bus 32.

[0051] The memory 30 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 33 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 32 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 32 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0052] Processor 31 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 31 or by software instructions. Processor 31 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this invention can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory, and the processor 31 reads the information in the memory and uses its hardware to complete the aforementioned method.

[0053] The computer program product of the shared vehicle management method and apparatus provided in this embodiment of the invention includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementation, please refer to the method embodiments, which will not be repeated here.

[0054] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0055] Furthermore, in the description of the embodiments of the present invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0056] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0057] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0058] Finally, it should be noted that the above embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for managing shared vehicles, characterized in that, The method includes: Responding to the vehicle return request sent by the user terminal, obtain the location information of the shared vehicle; The current parking spot and its type are determined based on the location information. Determine whether the user level corresponding to the user terminal matches the type of the parking spot; If so, a message indicating successful vehicle return will be sent to the user's terminal.

2. The method according to claim 1, characterized in that, The method further includes: In response to a parking spot query request, obtain the user level corresponding to the user terminal; Query parking spots within a preset distance range that match the user's level; The location information of the queried parking spot is displayed through a graphical user interface.

3. The method according to claim 2, characterized in that, The steps of displaying the location information of the queried parking spot through a graphical user interface include: The location information of parking spots matching the user level is displayed through a graphical user interface. Furthermore, the location information will not be displayed for parking spots that do not match the user's level.

4. The method according to claim 2, characterized in that, The step of determining whether the user level corresponding to the user terminal matches the type of the parking spot includes: If the parking spot is of type 1, then the user level corresponding to the user terminal is determined to match the type of the parking spot, wherein the parking spot of type 1 allows users of all user levels to return the vehicle.

5. The method according to claim 4, characterized in that, The step of determining whether the user level corresponding to the user terminal matches the type of the parking spot further includes: If the parking spot is of type two, then it is determined whether the user level corresponding to the user terminal is level two or level three; wherein, the parking spot of type two allows users of level two and level three to return the car; and, a car return penalty rule is set for users of level one. If so, determine that the user level corresponding to the user terminal matches the type of the parking spot; If not, it is determined that the user level corresponding to the user terminal does not match the type of the parking spot, and the return penalty rules are displayed through the graphical user interface.

6. The method according to claim 5, characterized in that, The step of determining whether the user level corresponding to the user terminal matches the type of the parking spot further includes: If the parking spot is of type three, then it is determined whether the user level corresponding to the user terminal is the third level; wherein, the parking spot of type three allows users of the third level to return the car, and users of the first level and the second level are prohibited from returning the car; If so, determine that the user level corresponding to the user terminal matches the type of the parking spot; If not, it is determined that the user level corresponding to the user terminal does not match the type of the parking spot, and a prompt message prohibiting returning the car is displayed through the graphical user interface.

7. The method according to claim 6, characterized in that, The steps for querying parking spots within a preset distance range that match the user level include: If the user level is the first level and the second level, then query other parking spots within a preset distance range, excluding the first type, the second type and the third type; If the user level is level 3, then query the parking spots within a preset distance range.

8. The method according to claim 6, characterized in that, The method further includes: Obtain historical order heat map information; the historical order heat map information is used to characterize the peak usage periods of the shared vehicles; The type of parking spot is adjusted based on the historical order heat map information.

9. The method according to claim 1, characterized in that, The method further includes: Obtain user identity information and search for the corresponding consumption records and historical vehicle usage records; The user level corresponding to the user's identity information is determined based on the consumption records and the historical vehicle usage records.

10. A management device for shared vehicles, characterized in that, The device includes: The response module is used to respond to the vehicle return request sent by the user terminal and obtain the location information of the shared vehicle; The determination module is used to determine the current parking spot and the type of the parking spot based on the location information; The judgment module is used to determine whether the user level corresponding to the user terminal matches the type of the parking spot; The prompting module is used to send a prompt message to the user terminal indicating that the vehicle has been successfully returned when the judgment result of the judgment module is yes.