Operation processing method and device based on shared equipment and computer equipment

Abstract

The invention provides an operation processing method and device based on shared equipment and computer equipment, before specific implementation, historical data when users use the shared equipment is obtained, and locking points matched with all the users are determined for all the users in combination with personal habits and preferences of the users according to the historical data. In specific implementation, in the process that a target user uses a target shared device, whether the target user uses the target shared device to enter an adjacent range of a target locking point or not is monitored; when it is detected that a user enters the adjacent range of the target locking point, a locking prompt is initiated, and whether a triggering request related to the locking prompt is received or not is detected; and according to the trigger request, distinguishing different conditions, and automatically carrying out corresponding operation. For example, when it is detected that a use trigger request is not received beyond a first duration, it is determined that a target user ends use of the target shared device, and locking operation is automatically conducted on the target shared device. Therefore, the user operation can be effectively simplified, and the user experience is improved.

Description

Technical Field

[0001] This specification belongs to the field of Internet technology, and in particular to an operation processing method, apparatus, and computer equipment based on a shared device. Background Art

[0002] With the promotion and popularization of shared bicycle services, more and more users are starting to use shared bicycles for travel.

[0003] With existing methods, dockless shared bikes often require additional manual steps on their phones to lock and return the bike after use. For example, users must open their phones, navigate to the app's return interface, and then tap the return icon to lock and return the bike. This increases user-side operations and impacts the user experience.

[0004] To address the above issues, no effective solutions have been proposed so far. Summary of the Invention

[0005] This specification provides an operation processing method, apparatus, and computer device based on a shared device, which can intelligently implement related operations such as automatic locking and returning of shared devices, effectively simplifying user operations and improving the user experience.

[0006] This manual provides a method for operating a shared device, including:

[0007] When a target user is detected to be entering the vicinity of a target locking point using a target shared device, a locking prompt is initiated; wherein the target locking point is associated with the target user;

[0008] Detect and perform corresponding operations on the target shared device based on the trigger request related to the lock prompt.

[0009] In one embodiment, the trigger request includes: an usage trigger request, or a lock trigger request.

[0010] In one embodiment, when the trigger request includes a usage trigger request, detecting and performing corresponding operations on the target shared device according to the trigger request related to the lock prompt includes:

[0011] When no trigger request related to the lock prompt is received within a first time period, a lock operation is performed on the target shared device.

[0012] In one embodiment, the usage trigger request includes: a first type of usage trigger request, or a second type of usage trigger request;

[0013] The first type of usage trigger request includes: a renewal request for the target shared device initiated by the target user through the user terminal, or an unlocking request initiated by the target user by scanning the identification code of the target shared device;

[0014] The second type of usage triggering request includes: an unlocking request initiated by a user other than the target user by scanning the identification code of the target shared device.

[0015] In one embodiment, when a first type of usage trigger request for a lock prompt is received within a first time period, the method further includes:

[0016] Stop the lock operation and continue to maintain the first order currently associated with the target user.

[0017] In one embodiment, when a second type of usage trigger request for the lock prompt is received within the first time period, the method further includes:

[0018] Stop the lock operation and end the first order currently associated with the target user;

[0019] Create a second order associated with another user.

[0020] In one embodiment, when no trigger request related to the lock-off prompt is received for more than a first period of time, the method further includes:

[0021] Acquire motion state data of the target shared device within the second time period;

[0022] determining whether a preset locking condition is met based on the motion state data of the target shared device within the second time period;

[0023] When it is determined that the preset locking condition is met, a locking operation is performed on the target shared device.

[0024] In one embodiment, when the trigger request includes a usage trigger request, detecting and performing corresponding operations on the target shared device according to the trigger request related to the lock prompt includes:

[0025] When a lock triggering request for the lock prompt is received within a specified time period, a lock operation is performed on the target shared device.

[0026] In one embodiment, the target locking point includes at least one of the following: a recommended locking point selected by the target user, a locking point customized by the target user, a locking point modified by the target user based on the recommended locking point, and an automatically determined recommended locking point for the target user.

[0027] In one embodiment, the recommended locking point is determined as follows:

[0028] Obtain historical order records of target users;

[0029] Based on the target user's historical order records, multiple historical lock points are determined;

[0030] Based on multiple historical locking points, a corresponding candidate point set is constructed;

[0031] Based on the candidate point set, the recommended locking points associated with the target user are determined.

[0032] In one embodiment, a corresponding candidate point set is constructed based on multiple historical locking points, including:

[0033] According to the historical order records of the target user, the historical lock-out times of each historical lock-out point are counted;

[0034] Calculate and find adjacent historical locking points based on the distance between them;

[0035] Construct an initial point set based on multiple historical locking points;

[0036] In the initial point set, the corresponding historical locking times are marked for each historical locking point; and corresponding adjacent marks are added to adjacent historical locking points to obtain an adjusted initial point set;

[0037] According to the adjusted initial point set, a corresponding candidate point set is determined through depth optimization search and / or breadth optimization search.

[0038] In one embodiment, determining a recommended locking point associated with a target user based on a set of candidate points includes:

[0039] Based on the target user's historical order records, extract the local historical location records after the third period of time since the unlocking;

[0040] Determining, based on the local historical position records, local historical position records of candidate points corresponding to the candidate points in the candidate point set;

[0041] Calculate the time difference between the appearance time and the lock time of the corresponding candidate point in the local historical position record of the candidate point based on the local historical position record of the candidate point; and determine the local historical position record of the candidate point with a time difference greater than the first time length as the historical passage record of the candidate point;

[0042] Count and determine the passing points from the candidate points based on their historical passing records;

[0043] Eliminating the passing point from the candidate point set;

[0044] According to the eliminated candidate point set, the recommended locking point associated with the target user is determined.

[0045] In one embodiment, after removing the passing point from the candidate point set, the method further includes:

[0046] According to the historical order records of the target user, the total number of associated orders of the candidate point set after elimination is counted;

[0047] According to the total number of associated orders of the eliminated candidate point set, a target candidate point set that meets the requirements is determined from the eliminated candidate point set;

[0048] According to the target candidate point set, a recommended locking point associated with the target user is determined.

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

[0050] Receive and respond to an unlock request for a target shared device, and perform an unlock operation on the target shared device;

[0051] From the third time after unlocking, the target user is monitored to see whether he or she uses the target shared device to enter the vicinity of the target locking point based on the location information of the target shared device.

[0052] In one embodiment, the target shared device includes at least one of the following: a shared bicycle, a shared electric vehicle, and a shared car.

[0053] This manual also provides an operation processing method based on a shared device, including:

[0054] When it is detected that the target user enters the vicinity of the associated location point using the target shared device, a prompt message is initiated; wherein the associated location point is associated with the target user;

[0055] Detect and perform corresponding operations on the target shared device based on the trigger request related to the prompt information.

[0056] This specification also provides an operation processing apparatus based on a shared device, comprising:

[0057] an initiating module, configured to initiate a lock prompt when detecting that a target user uses a target shared device to enter the vicinity of a target lock point; wherein the target lock point is associated with the target user;

[0058] The operation module is used to detect and perform corresponding operations on the target shared device according to the trigger request related to the lock prompt.

[0059] This specification also provides a computer device, including a processor and a memory for storing processor-executable instructions, wherein the processor implements the relevant steps of the operation processing method based on the shared device when executing the instructions.

[0060] This specification also provides a computer-readable storage medium having computer instructions stored thereon, which implement the steps of the operation processing method based on the shared device when the instructions are executed by a processor.

[0061] Based on the operation processing method, device and computer equipment based on shared devices provided in this specification, before specific implementation, obtain and determine the locking point suitable for each user based on the historical data of the user's use of the shared device, combined with the user's personal habits (for example, locking habits, riding habits, etc.) and personal preferences. During specific implementation, when the target user uses the target shared device, automatically monitor whether the target user uses the target shared device to enter the vicinity of the target locking point associated with the target user; when it is detected that the target user enters the vicinity of the target locking point, it is determined that the target user is likely to want to park and lock near the current location; then automatically initiate a locking prompt, and then detect and automatically perform corresponding operations on the target shared device based on the trigger request related to the locking prompt. For example, it detects whether a trigger request related to the lock prompt is received within a first time period to further determine whether the target user actually wants to park and lock the device. When it detects that no such use trigger request is received after the first time period, it can be determined that the target user has currently finished using the target shared device and indeed needs to park and lock the device. In this case, the target shared device can be automatically locked. On the contrary, when it detects that a use trigger request is received within the first time period, it can be determined that the target user has not currently finished using the target shared device and does not need to park and lock the device. In this case, the target shared device can continue to be unlocked to avoid interfering with the target user's normal use of the target shared device. This can better adapt to the user's lock habits and personal preferences when using shared devices, intelligently implement operations such as automatic lock return for shared devices, effectively simplify user operations, and improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] In order to more clearly illustrate the embodiments of this specification, the following is a brief introduction to the drawings required for use in the embodiments. The drawings described below are only some of the embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0063] Figure 1 This is a flowchart of an operation processing method based on a shared device provided by an embodiment of this specification;

[0064] Figure 2 This is a schematic diagram of an embodiment of an operation processing method based on a shared device provided by an embodiment of this specification, in a scenario example;

[0065] Figure 3 This is a schematic diagram of an embodiment of an operation processing method based on a shared device provided by an embodiment of this specification, in a scenario example;

[0066] Figure 4 This is a schematic diagram of an embodiment of an operation processing method based on a shared device provided by an embodiment of this specification, in a scenario example;

[0067] Figure 5 This is a schematic diagram of an embodiment of an operation processing method based on a shared device provided by an embodiment of this specification, in a scenario example;

[0068] Figure 6 This is a schematic diagram of the structure of a computer device provided by one embodiment of this specification;

[0069] Figure 7 This is a schematic diagram of the structural composition of an operation processing device based on a shared device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0070] To help those skilled in the art better understand the technical solutions in this specification, the following will provide a clear and complete description of the technical solutions in the embodiments of this specification, in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. All other embodiments derived by those skilled in the art based on the embodiments in this specification without creative effort shall fall within the scope of protection of this specification.

[0071] It should be noted that the user-related information and data involved in the embodiments of this specification are all information and data authorized by the user or fully authorized by relevant parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users or relevant parties to choose to authorize or refuse.

[0072] It should also be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary and their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0073] Considering the existing methods, for shared devices that operate without docking stations (for example, shared bicycles), users usually need to use mobile phones or other user terminals to actively perform special lock-and-return operations after use, in order to achieve operations such as locking and returning shared devices. Based on the above method, on the one hand, the amount of operations required for users to lock and return the devices will be increased; on the other hand, the above operation process will take at least 20 to 30 seconds for users, especially when users are in a hurry, which is bound to cause a more obvious negative experience for users. In addition, some users often forget to actively perform the above operations after using shared devices, which can easily cause losses to users.

[0074] In response to the above problems, the applicant has found through long-term practice and analysis that: in most cases, when most users use shared devices to lock and park, they will show characteristics related to the user's personal habits and preferences, and are relatively fixed. Specifically, for example, user A is accustomed to using shared devices to lock and park in front of the xx company during weekdays (Monday to Friday); on weekends (Saturday or Sunday), he uses shared devices to lock and park in front of the yy supermarket. Based on the above characteristics, for user A, when it is detected that the user uses a shared device to arrive at the door of the xx company during the weekday, it can be judged that the user is likely to lock and return the car near this location. At this time, if user A can be automatically helped to lock and return the car, it can avoid interfering with user A's normal riding, and it can also simplify the operation of user A when locking the car, thereby improving the user experience. For another example, user B personally prefers to lock and return the car near the entrance of the subway station. Based on the above characteristics, for user B, when it is detected that the user arrives at a subway station entrance using a shared device and the user is automatically prompted whether he needs to lock and return the device, if user B does not give a negative feedback, it can also be judged that the user is likely to lock and return the device near the location, and thus user B can be accurately helped to achieve automatic locking and returning.

[0075] Based on the above considerations and analysis, the applicant has proposed an improved operation and processing method for shared devices. Based on historical data from each user's shared device usage, combined with their personal habits and preferences, a corresponding locking point can be pre-determined and set for each user. When a target user is detected using a shared device, a target locking point corresponding to the target user can be determined. By monitoring whether the target user uses the shared device within the vicinity of the target locking point, it can be determined whether the target user is likely to lock and return the device near that location. When the target user is detected using the shared device within the vicinity of the target locking point, a lock prompt can be issued to the target user to further determine whether the target user intends to lock and return the device at that location. If it is determined that the target user intends to lock and return the device at that location, the lock operation is automatically performed. This effectively simplifies user operations and intelligently and automatically implements lock return for shared devices. It also effectively prevents interference with the user's normal use of the shared device due to erroneous locking due to misjudgment, thereby providing a better user experience.

[0076] See Figure 1 As shown, the embodiment of this specification provides an operation processing method based on a shared device. In specific implementation, the method may include the following contents:

[0077] S101: When a target user is detected to enter the vicinity of a target locking point using a target shared device, a locking prompt is initiated; wherein the target locking point is associated with the target user;

[0078] S102: Detect and perform corresponding operations on the target shared device according to a trigger request related to the lock prompt.

[0079] Among them, the above-mentioned target shared device can be specifically understood as a shared device that is currently unlocked and in use. The above-mentioned shared device can specifically be a shared riding device, which can specifically include at least one of the following: shared bicycles, shared electric vehicles, shared cars, etc. Of course, it should be noted that the shared devices listed above are only a schematic illustration. In some cases, the above-mentioned shared devices may also include other types of shared devices such as shared batteries and shared printers. This specification does not limit this.

[0080] The above-mentioned target user can be specifically understood as a user who is currently using the target shared device.

[0081] The target locking point is associated with a target user. Specifically, the target locking point may be understood as a location corresponding to the target user, at which the target user is likely to perform a locking and returning operation based on personal habits and / or personal preferences.

[0082] The trigger request related to the lock closing prompt may be specifically understood as a trigger request received after the lock closing prompt is initiated.

[0083] Prior to implementation, a lockout point can be determined and set for each user based on historical data of each user, combined with their personal habits and / or preferences. The target lockout point for a target user can be a single lockout point or multiple lockout points. The specific method for determining the lockout point associated with a user will be described in detail later.

[0084] The proximity of the target access point can be understood as the area adjacent to the target access point. For example, the area around the target access point with a radius of 5 meters. Another example is the area indicated by the electronic fence corresponding to the target access point.

[0085] The lock prompt can be understood as a prompt message that prompts the user to confirm whether to allow the lock operation. Specifically, the lock prompt can be a voice prompt with specific semantic content, a prompt tone without specific semantic content, or a vibration signal emitted by the shared device to indicate the lock prompt.

[0086] The above-mentioned usage trigger request can be specifically understood as a kind of request data that can indicate that there is a user (including the target user, or other users except the target user) who currently needs to continue to use the target shared device.

[0087] Specifically, the above-mentioned operation processing method based on a shared device can be applied to a server or a shared device side. This specification mainly uses the application on the server side as an example for specific description.

[0088] See Figure 2 As shown, the above-mentioned server may specifically include a background server applied to one side of a business platform (for example, a cloud service platform for shared devices) that can realize functions such as data transmission and data processing. Specifically, the server may be, for example, a communication module with data calculation, storage and network interaction functions. Alternatively, the server may also be a software program running in the communication module to provide support for data processing, storage and network interaction. In this embodiment, the number of the servers is not specifically limited. The server may specifically be one server, or several servers, or a server cluster formed by several servers.

[0089] The target user may hold a user terminal. The target shared device is at least equipped with a communication module capable of communicating with a server and / or a user terminal, and a device lock.

[0090] The device lock may specifically include a horseshoe lock or a hub lock, etc. Specifically, the communication module may be electrically connected to the device lock. The server may control the device lock to unlock or lock via the communication module.

[0091] The user terminal may specifically include a front-end, applied to the user side, capable of performing functions such as data collection and data transmission. Specifically, the user terminal may be a communication module such as a mobile phone, tablet computer, or smartwatch. Alternatively, the user terminal may be a software application capable of running on the communication module.

[0092] In specific implementation, the server can first determine the target locking point associated with the target user when the target user is using the target shared device based on the information fed back by the target user's user terminal and / or the communication module of the target shared device; then obtain the location information of the target shared device in real time or at a fixed time and monitor whether the target user uses the target shared device to enter the vicinity of the target locking point.

[0093] When it is detected that the target user uses the target shared device to enter the vicinity of the target locking point, the server can determine that the target user is likely to lock and return the lock near this location. At this time, the server can initiate a lock prompt to the target user through the user terminal or the target shared device; detect and perform corresponding operations on the target shared device based on the trigger request related to the lock prompt. For example, starting from the initiation of the lock prompt, it can monitor whether a use trigger request for the lock prompt is received within a first time period (for example, 60 seconds); or whether a lock trigger request for the lock prompt is received within a specified time period (for example, 45 seconds).

[0094] If the server detects that no use trigger request for the lock prompt has been received for a period exceeding the first time, it can determine that the target user has ended use of the target shared device. At this point, the server can interact with the communication module on the target shared device to control the device lock and lock, thereby automatically locking the target shared device. This allows for intelligent and accurate automatic locking of the shared device without requiring additional user intervention.

[0095] Conversely, if a use trigger request for the unlock prompt is received within the first duration, the server can determine that there is still a user who needs to use the target shared device. In this case, the server can continue to maintain the target shared device in an unlocked state. This can avoid interference and impact on the user's normal use of the target shared device, ensuring that the user has a better user experience.

[0096] Alternatively, upon detecting that a lock trigger request has been initiated by the target user in response to the lock prompt within a specified time period, the server may determine that the target user has ended use of the target shared device. In this case, the server may control the device lock or unlock by interacting with a communication module on the target shared device, thereby achieving the lock operation on the target shared device.

[0097] In some embodiments, in addition to the communication module and the lock device, the target sharing device may also be equipped with a positioning module (e.g., a GPS positioning module). Accordingly, the server may determine the location information of the target sharing device by acquiring and using the data collected by the positioning module of the target sharing device.

[0098] The user terminal may also be equipped with a positioning module. Accordingly, the server may also determine the location information of the target shared device by acquiring and using the data collected by the positioning module of the user terminal.

[0099] Furthermore, the target shared device may also be equipped with a processor. The processor may be electrically connected to the positioning module, communication module, device lock, and other modules. Accordingly, the target shared device may also utilize the processor to execute the shared device-based operation processing method provided herein to perform relevant data processing locally on the target shared device.

[0100] In some embodiments, the method may further include the following when implemented:

[0101] S1: Receive and respond to an unlock request for a target shared device, and perform an unlock operation on the target shared device;

[0102] S2: From the third time after unlocking, obtain and monitor whether the target user uses the target shared device to enter the vicinity of the target locking point based on the location information of the target shared device.

[0103] Specifically, an identification code may be set on the target shared device, wherein the identification code may specifically include a QR code or a bar code.

[0104] When the target user needs to unlock and use the target shared device, the target user can scan the identification code on the target shared device through the user terminal to initiate an unlocking request for the target shared device to the server.

[0105] Correspondingly, the server can receive and respond to the unlocking request, and unlock the target shared device to put the target shared device into an unlocked state so that the target user can use the target shared device normally; at the same time, an order is created for the target user to use the target shared device, which is recorded as the first order associated with the target user.

[0106] Among them, the above-mentioned unlocking request may carry the user identification of the target user (for example, the user name, user number, etc. of the target user), and the device identification corresponding to the target shared device obtained by parsing the identification code of the target shared device (for example, the device number, MAC address, etc. of the target shared device).

[0107] At the same time, the server can also create an order for the target user to use the target shared device based on the user ID of the target user and the device ID of the target shared device, record it as the first order associated with the target user, and then start providing related services of the shared device to the target user.

[0108] In addition, the server can query a user database based on the target user's user ID to determine a target locking point associated with the target user. Based on the target locking point, the server can automatically monitor whether the target user has entered the vicinity of the target locking point using the target shared device. The user database stores at least a plurality of locking points, each of which corresponds to at least one user ID.

[0109] In specific implementation, the server can determine and update the location information of the target shared device (for example, the latitude and longitude information of the location coordinates of the target shared device, etc.) in real time or periodically through the positioning data collected and uploaded by the user terminal of the target user and / or the positioning module deployed on the target shared device; and then, based on the location information of the target shared device, it can detect whether the target user uses the target shared device to enter the vicinity of the target locking point.

[0110] Considering that the location where the target user unlocks the target shared device is likely to be a locking point for the target user. When unlocking the device, and for a relatively short period of time after unlocking, the target shared device is likely to be within the vicinity of the locking point. At this time, if we start monitoring whether the target user uses the target shared device to enter the vicinity of the target locking point, it is obviously easy to misjudge the location of the target shared device when the target user is currently unlocking the device as the location where the target user is about to lock and return the device, thereby interfering with the target user's normal use of the target shared device and affecting the target user's user experience.

[0111] Based on the above considerations, the timer can be started from the moment the lock is unlocked. After the accumulated time reaches the third time, the target shared device's location information is obtained and monitored to see if the target user has used the target shared device to enter the vicinity of the target locking point. This can effectively avoid interference with the user's normal use of the shared device due to misjudgment, ensuring a better user experience.

[0112] The third time period may be specifically understood as a reference threshold time period required for the user to use the shared device to leave the vicinity of the unlocking location.

[0113] The third duration can be a reference threshold duration that is pre-calculated and applied to the majority of users by statistically analyzing partial post-unlocking records from a large number of users' historical order records. After the reference threshold duration from unlocking, the majority of users have generally used the shared device to leave the vicinity of the unlocking location.

[0114] Furthermore, the third duration may be adjusted based on the reference threshold duration and the target user's attribute characteristics to obtain a duration suitable for the target user. The target user's attribute characteristics may include one or more of the following: gender, age, personality, health status, etc.

[0115] For example, when determining the third duration for user C, based on the fact that user C is 65 years old and has a cold, an adjustment duration (for example, 20 seconds) can be added to the reference threshold duration as the third duration for user C.

[0116] For example, when determining the third duration for user D, based on the fact that user D is 25 years old and in a healthy state, an adjustment duration can be subtracted from the reference threshold duration as the third duration for user D.

[0117] In some embodiments, the server may obtain and monitor in real time or periodically whether the target user uses the target shared device to enter the vicinity of the target locking point based on the location information of the target shared device.

[0118] In specific implementation, when the target user is detected to be within the vicinity of the target locking point using the target shared device, it can be determined that the target user is likely to lock and return the device near the current location. In this case, in order to avoid misjudgment, further detection can be performed by initiating a lock prompt.

[0119] On the other hand, if it is detected that the target user has not entered the vicinity of the target locking point using the target shared device, it can be determined that the target user is unlikely to lock and return the device near the current location. In this case, in order to avoid interfering with the target user's normal use of the target shared device, no action can be taken and the target user can continue to be monitored to see if he or she enters the vicinity of the target locking point using the target shared device.

[0120] Specifically, a voice player may also be deployed on the target sharing device. Accordingly, the server may send a corresponding lock prompt instruction to the target sharing device to control the voice player of the target sharing device to play a relevant voice lock prompt to the target user. The voice content contained in the lock prompt may include, for example: Please confirm whether to lock and return the device. If you want to continue to use the current target sharing device, please initiate a renewal request (a use trigger request) through the user terminal or by pressing the renewal button on the target sharing device; otherwise, the device will be automatically locked and returned after the first period of time.

[0121] The server may start timing after initiating the lock-off prompt, and monitor whether a trigger request related to the lock-off prompt is received within the first time period.

[0122] When a trigger request related to the lock prompt is detected within the first time period, it can be determined that at least one user (which can be the target user or another user other than the target user) needs to continue using the target shared device. In this case, the lock operation can be stopped to avoid interfering with the user's normal use of the target shared device.

[0123] Conversely, if no trigger request related to the lock prompt is received for a period exceeding the first time period, it can be determined that the target user has terminated use of the target shared device. At this point, the lock operation can be continued, automatically locking the target shared device. Specifically, the server can generate a lock instruction corresponding to the target shared device based on the device identifier of the target shared device and a corresponding cryptographic algorithm. This lock instruction can then be sent to the communication module of the target shared device. The device lock disposed on the target shared device receives and, in response to the lock instruction forwarded by the communication module, performs the specific lock operation.

[0124] In addition, the server may also start timing after initiating the lock-off prompt, and monitor whether a lock-off trigger request for the lock-off prompt is received within a specified time period.

[0125] If a lock instruction (a lock trigger request) is detected from the target user via a user terminal in the form of text or voice within a specified time period, it can be determined that the target user has currently ended use of the target shared device. In this case, the lock operation can be continued to automatically lock the target shared device. Otherwise, it is determined that the target user has not yet ended use of the target shared device. In this case, the lock operation can be stopped and the target shared device can continue to be unlocked to avoid interfering with the user's normal use of the target shared device.

[0126] While performing the locking operation on the target shared device, the server can also end the first order and perform corresponding settlement processing on the first order, thereby automatically completing the locking and returning of the target shared device.

[0127] The first time duration may be specifically understood as a reference threshold time duration required for the user to select a specific parking location and park at the location after entering the vicinity of the locking point.

[0128] The first duration can be a reference threshold duration that is pre-determined by analyzing partial pre-locking records from a large number of users' historical order records and is applicable to most users. After entering the vicinity of the locking point and exceeding the reference threshold duration, most users have generally found their final parking location and parked the target shared device there.

[0129] Furthermore, the first duration may be adjusted based on the reference threshold duration and the target user's attribute characteristics to obtain a duration suitable for the target user. The target user's attribute characteristics may include one or more of the following: gender, age, personality, health status, etc.

[0130] In some embodiments, the trigger request may specifically include: an usage trigger request, a lock trigger request, etc.

[0131] The above-mentioned use trigger request can be specifically understood as request data initiated by a user (including the target user, or other users except the target user) to instruct to continue using the target shared device. The above-mentioned lock trigger request can be specifically understood as request data initiated by a user (including the target user, or other users except the target user) to instruct to end the use of the target shared device.

[0132] In specific implementation, the above detection and corresponding operation on the target shared device based on the trigger request related to the lock prompt may include: detecting whether a trigger request related to the lock prompt is received within a first time period; and / or detecting whether a lock trigger request for the lock prompt is received within a specified time period.

[0133] In specific implementation, when the trigger request includes a usage trigger request, the above detection and corresponding operation on the target shared device based on the trigger request related to the lock prompt may include: when no trigger request related to the lock prompt is received for more than a first time period, locking the target shared device.

[0134] In the case where the trigger request includes a usage trigger request, the above detection and performing corresponding operations on the target shared device based on the trigger request related to the lock prompt may include: when a lock trigger request for the lock prompt is received within a specified time period, performing a lock operation on the target shared device.

[0135] In some embodiments, the usage trigger request may specifically include: a first type of usage trigger request, or a second type of usage trigger request, etc.;

[0136] The first type of usage trigger request may specifically include: a renewal request for the target shared device initiated by the target user through the user terminal, or an unlocking request initiated by the target user by scanning the identification code of the target shared device;

[0137] The second type of usage trigger request may specifically include: an unlocking request initiated by a user other than the target user by scanning an identification code of the target shared device.

[0138] During specific implementation, the usage trigger request may also carry the user identification of the initiating user.

[0139] Accordingly, the server may parse and determine the type of the received usage trigger request based on the user identifier of the initiating user carried in the usage trigger request.

[0140] Specifically, based on the user ID of the initiating user, when it is determined that the initiating user is the target user, the usage trigger request can be determined as a first-class usage trigger request; when it is determined that the initiating user is a user other than the target user, the usage trigger request can be determined as a second-class usage trigger request.

[0141] In some embodiments, when a first type of usage trigger request for a lock-off prompt is received within a first time period, the method may further include the following steps during implementation:

[0142] Stop the lock operation and continue to maintain the first order currently associated with the target user.

[0143] Specifically, when it is determined that the received usage trigger request is a first type of usage trigger request, it can be determined that the target user still needs to continue using the target shared device.

[0144] At this time, the server may stop locking the target shared device and maintain the target shared device unlocked so that the target user can continue to use the target shared device normally; at the same time, the server continues to maintain the first order currently associated with the target user.

[0145] In some embodiments, when a second type of usage trigger request for a lock-off prompt is received within the first duration, the method may further include the following when implemented:

[0146] S1: Stop the lock operation and end the first order currently associated with the target user;

[0147] S2: Create a second order associated with another user.

[0148] While stopping the locking operation, the target shared device may also be unlocked to ensure that the target shared device is in an unlocked state.

[0149] Specifically, when it is determined that the received usage trigger request is the second type of usage trigger request, it can be determined that the target user has currently ended the use of the target shared device, but other users other than the target user need to use the target shared device.

[0150] At this point, while the server stops locking the target shared device, it can also unlock it again. This prevents the target shared device from having been locked in order to reclaim the target user's right to use the device due to information asynchrony. This ensures that the target shared device remains unlocked, allowing other users to use the device normally. Furthermore, the server can terminate the first order associated with the previous target user, perform the corresponding settlement, and terminate service for the target user. Simultaneously, it can create a second order associated with the current other user and begin service for the other user.

[0151] In some embodiments, see Figure 3 As shown, when no trigger request related to the lock prompt is received within the first time period, the method may further include the following steps during implementation:

[0152] S1: Acquire motion state data of the target shared device within a second time period;

[0153] S2: determining whether a preset locking condition is met based on the motion state data of the target shared device within the second time period;

[0154] S3: When it is determined that the preset locking condition is met, the target shared device is locked.

[0155] The second duration may be an inspection duration (eg, 30 seconds) after the first duration.

[0156] In a specific implementation, the server may obtain the location information of the target shared device through a positioning module on the target shared device at preset time intervals (e.g., every 5 seconds) within a second time period after the first time period ends, thereby obtaining multiple pieces of location information corresponding to multiple time points within the second time period; and combining the multiple pieces of location information in chronological order to obtain a corresponding position sequence as the motion state data of the target shared device within the second time period. Based on the position sequence, the server then determines whether the position of the target shared device has not changed within the second time period.

[0157] When it is determined that the location has not changed, it is determined that the preset locking condition is met, the target user has indeed parked the target shared device within the vicinity of the target locking point, and the target user has indeed finished using it and needs to lock it and return it. At this time, the server can automatically lock the target shared device.

[0158] On the contrary, if it is determined that the location is still changing, it is determined that the preset locking condition is not met, and the target user is still using the target shared device and does not need to lock it and return it. In this case, in order to avoid interfering with the target user's normal use of the target shared device, the target shared device is not locked and monitoring continues.

[0159] Furthermore, the target sharing device may also be equipped with a speed sensor and / or acceleration sensor. Accordingly, the server may also use the speed sensor and / or acceleration sensor to obtain speed data and / or acceleration data of the target sharing device at multiple time points during the second duration as motion state data of the target sharing device during the second duration. Furthermore, based on the motion state data, the server may determine whether the preset locking condition is met by determining whether the target sharing device enters and maintains a stationary state during the second duration.

[0160] When the target sharing device enters and maintains a stationary state within the second time period, it can be determined that the preset locking condition is satisfied. Conversely, when the target sharing device does not enter and / or maintain a stationary state within the second time period, it can be determined that the preset locking condition is not satisfied.

[0161] Based on the above embodiment, by examining and detecting the operating status data of the shared device within the second period after the first period, it is possible to more accurately determine whether the user really wants to lock and return the device, thereby further reducing misjudgments and improving user experience.

[0162] In some embodiments, the target shared device may specifically include at least one of the following: a shared bicycle, a shared electric vehicle, a shared car, etc.

[0163] In some embodiments, the target locking points associated with the target user stored in the user database may include multiple different target locking points; wherein each target locking point may carry an effectiveness condition parameter corresponding to the target locking point.

[0164] The aforementioned validation condition parameters may specifically include one or more of the following: validation time, validation weather, validation season, etc. The validation condition parameters for the target lock point can be determined based on the target user's historical order records and associated information corresponding to the historical order records. The specific method for determining the validation condition parameters will be described later.

[0165] Correspondingly, when the user database is queried and multiple target locking points associated with the target user are searched, the method further includes: obtaining current auxiliary information based on the effectiveness condition parameters carried by the target locking point; determining a target locking point that matches the current one from multiple target locking points based on the current auxiliary information and the effectiveness condition parameters carried by the target locking point, and then using the target locking point for subsequent monitoring.

[0166] Specifically, for example, in the user database, the target lock-in points associated with user A may include: target lock-in point 1 (the entrance of xx company) and target lock-in point 2 (the entrance of yy supermarket). Among them, the validity condition parameter carried by target lock-in point 1 is the validity time: weekday, and the validity condition parameter carried by target lock-in point 2 is the validity time: weekend.

[0167] Accordingly, when determining user A's target locking point, if two target locking points associated with user A are detected in the user database, the server can obtain and determine the matching auxiliary information as date and time based on the validity condition parameters carried by the two target locking points. At this time, the server can obtain the current date and time and, based on the current date and time, determine the target locking point that matches the current one from the two target locking points. If the current date and time indicates a weekday, target locking point 1 can be determined as the matching target locking point. Conversely, if the current date and time indicates a weekend, target locking point 2 can be determined as the matching target locking point.

[0168] Based on the above method, the target locking point adapted to the target user can be determined more accurately, and then the automatic locking and returning of the target shared device can be achieved more accurately based on the target locking point, further reducing errors.

[0169] In some embodiments, the target locking point includes at least one of the following: a recommended locking point selected by the target user, a locking point customized by the target user, a locking point obtained by the target user after modification based on the recommended locking point, an automatically determined recommended locking point for the target user, and the like.

[0170] Among them, the above-mentioned automatically determined recommended closing points for the target user can be recommended closing points that are likely to be used by the target user and are automatically determined based on the target user's historical order records; they can also be recommended closing points that are more closely matched with the target user and are likely to be used by the target user and are automatically determined based on the historical order records of associated users (for example, relatives, colleagues, etc. of the target user) who have an associated relationship with the target user; they can also be popular recommended closing points that are relatively practical for most users and are determined through big data analysis based on the historical order records of a large number of users on the platform, etc.

[0171] Before specific implementation, the server can obtain and analyze the target user's historical order records and combine them with the target user's personal habits and preferences to determine the location points that the target user is likely to use to lock and park the target shared device, which are relatively unlikely to cause misjudgment and will not interfere with the target user's normal use of the riding device, and use them as recommended locking points.

[0172] Furthermore, the server may display a lock point setting interface to the target user through the user terminal.

[0173] Among them, the above-mentioned locking point setting interface can specifically include an electronic map of the range area where the target user uses the shared device with a frequency greater than a preset frequency threshold, determined based on the target user's historical order records; and recommended locking points are also marked at the corresponding positions on the electronic map.

[0174] The target user can select one or more recommended lock-in points that meet their requirements from multiple recommended lock-in points on the lock-in point setting interface as the target lock-in points associated with the target user; or the target user can first select one or more recommended lock-in points that are relatively close to their requirements on the lock-in point setting interface, and then adjust the selected recommended lock-in points (for example, drag the selected recommended lock-in point on the electronic map to a nearby location) to obtain the modified lock-in point as the target lock-in point associated with the target user; or the target user can customize a location point on the key point setting interface as the target lock-in point associated with the target user.

[0175] Correspondingly, the server receives and responds to the above operation of the target user, determines the target locking point associated with the target user, establishes a correspondence between the target locking point and the user identifier of the target user, and then stores the target locking point of the target user and the relevant correspondence in the user database.

[0176] In some embodiments, see Figure 4 As shown, the recommended locking point can be determined in the following way:

[0177] S1: Obtain the historical order records of the target user;

[0178] S2: Determine multiple historical lock points based on the target user's historical order records;

[0179] S3: Construct a corresponding candidate point set based on multiple historical locking points;

[0180] S4: Determine a recommended locking point associated with the target user based on the candidate point set.

[0181] The above-mentioned historical order records of the target user may specifically be historical records generated when the target user used the target shared device in the past year.

[0182] The above historical order records at least include the location information and time information when the target user unlocks and uses the shared device, and the location information and time information when the target user locks and parks the shared device.

[0183] Furthermore, the above historical order records also include the location points that the target user passed through when using the shared device, as well as the corresponding time information.

[0184] In addition, associated information corresponding to the historical order record can also be obtained, such as the season information, date information, weather information, etc. when the historical order record was generated.

[0185] In specific implementations, the server can first query the platform database based on the target user's user ID to obtain the target user's historical order records. Next, the server can determine multiple corresponding historical locking points by extracting the location information of each shared device locked or parked in each historical order record. By combining these multiple historical locking points, a set of candidate points for the target user is constructed. Furthermore, based on this set of candidate points, a recommended locking point associated with the target user can be determined.

[0186] In specific implementation, after determining the recommended lock point associated with the target user, the server can also determine the historical order records related to the recommended lock point; obtain and determine whether the effective condition parameters of the recommended lock point exist based on the associated information of the relevant historical order records; if it is determined that the effective condition parameters exist, the corresponding effective condition parameters are added to the recommended lock point.

[0187] Specifically, for example, clustering can be performed on the associated information of relevant historical order records to obtain corresponding clustering results. Based on the clustering results, common feature information is identified from the associated information to construct the validation condition parameters for the recommended lock point. If the clustering results determine that no common feature information exists, the validation condition parameters for the recommended lock point are set to null.

[0188] The above-mentioned embodiment of determining the recommended key points associated with the target user may be referred to to determine the recommended key points associated with each other user respectively.

[0189] In some embodiments, the above-mentioned construction of a corresponding candidate point set based on multiple historical locking points may include the following contents during specific implementation:

[0190] S1: Based on the historical order records of the target user, count the historical lock times of each historical lock point;

[0191] S2: Calculate and find adjacent historical locking points based on the distance between them;

[0192] S3: Construct an initial point set based on multiple historical locking points;

[0193] S4: In the initial point set, mark the corresponding historical locking times for each historical locking point; and add corresponding neighboring marks to adjacent historical locking points to obtain an adjusted initial point set;

[0194] S5: According to the adjusted initial point set, a corresponding candidate point set is determined through depth optimization search and / or breadth optimization search.

[0195] In specific implementation, the distance between any two historical locking points can be calculated, and the distance can be detected to see if it is less than a preset distance threshold (for example, 20 meters). Two historical locking points whose distance is less than the preset distance threshold are determined to be adjacent historical locking points. And according to the preset marking rules, corresponding proximity marks are added to the adjacent historical locking points.

[0196] For example, after determining that historical locking points a and b are adjacent, a connector "-" can be used to connect them, marking them as "ab." "ab" can then be used to replace historical locking points a and b in the initial point set.

[0197] The preset distance threshold may be determined based on the user's attribute characteristics.

[0198] In specific implementations, based on the adjusted initial point set, a depth-optimized search and / or breadth-optimized search can be performed to obtain multiple subgraphs, each of which can contain multiple adjacent historical locked points. Based on these multiple subgraphs, corresponding candidate point sets are determined, each of which can correspond to a candidate point set.

[0199] Furthermore, for each subgraph, based on the number of historical locks marked on each historical lock point in the subgraph, historical lock points with a number of historical locks less than a preset lower limit (for example, 2) can be deleted from the candidate point set. This removes historical lock points that are accidentally used by users when returning the lock and cannot effectively reflect the user's personal habits and / or personal preferences, thereby obtaining a candidate point set with relatively higher reference value.

[0200] In some embodiments, see Figure 5As shown, the above method of determining the recommended locking point associated with the target user based on the candidate point set may include the following steps during implementation:

[0201] S1: Based on the target user's historical order records, extract the local historical location records after the third period of time since the unlocking;

[0202] S2: determining, based on the local historical position records, local historical position records of candidate points corresponding to the candidate points in the candidate point set;

[0203] S3: Calculate the time difference between the appearance time and the lock time of the corresponding candidate point in the local historical position record of the candidate point based on the local historical position record of the candidate point; and determine the local historical position record of the candidate point with a time difference greater than the first time length as the historical passage record of the candidate point;

[0204] S4: Count and determine the passing points from the candidate points based on their historical passing records;

[0205] S5: Eliminate the passing point from the candidate point set;

[0206] S6: Determine a recommended locking point associated with the target user based on the eliminated candidate point set.

[0207] The above-mentioned passing points can be understood as the locations that the user often passes by during the normal use of the cycling device. If such locations are set as locking points, it is easy to interfere with the normal use of the cycling device by the user.

[0208] It should be noted that only the partial historical location records after the third period of time since the lock was unlocked are intercepted and used here instead of the complete historical order records of the target user. This is because during the third period of time since the lock was unlocked, the user is often still in the vicinity of the unlocking location. Therefore, the historical location records during this period are meaningless for the subsequent determination of the passing points and may even introduce error interference. In addition, if the historical location records during this period of time are taken into account, the overall data processing volume will increase and the overall processing efficiency will be reduced. Therefore, here we intercept and use the partial historical location records after the third period of time since the lock was unlocked so that the passing points can be determined relatively more efficiently and accurately.

[0209] If the time difference is greater than the first duration, it indicates that the candidate point is not within the proximity of the locking point in the local historical location record, and thus the candidate point can be determined to be a passing point rather than a locking point. Conversely, if the time difference is less than or equal to the first duration, it indicates that the candidate point is within the proximity of the locking point in the local historical location record, and thus the candidate point can be determined to be a locking point rather than a passing point.

[0210] In specific implementations, for each set of eliminated candidate points, surrounding environment information for each candidate point in the set can be collected. Based on this surrounding environment information, multiple candidate points that meet safety requirements and are suitable for locking and parking can be screened. Furthermore, the spacing between the multiple selected candidate points can be calculated, and candidate points with spacing less than or equal to a preset lower distance limit (e.g., 1 meter) can be merged. Based on the remaining candidate points in the merged candidate point set, a recommended locking point corresponding to the candidate point set can be determined.

[0211] Based on the above embodiment, passing points can be accurately and efficiently determined and eliminated from the candidate point set, thereby avoiding interference with the user's normal use of the shared device due to the subsequent use of the passing points as locking points.

[0212] In some embodiments, after removing the passing point from the candidate point set, the method may further include the following steps when implemented:

[0213] S1: Based on the historical order records of the target user, the total number of associated orders of the candidate point set after elimination is counted;

[0214] S2: Determine a target candidate point set that meets the requirements from the eliminated candidate point set based on the total number of associated orders of the eliminated candidate point set;

[0215] S3: Determine a recommended locking point associated with the target user based on the target candidate point set.

[0216] In specific implementation, for each set of eliminated candidate points, historical orders involving at least one candidate point in the set of eliminated candidate points can be screened out as associated orders of the set of eliminated candidate points based on the local historical location records after the third period of time since unlocking in the historical order records of the target user; and then the total number of associated orders of the set of eliminated candidate points can be obtained by counting.

[0217] In specific implementations, a set of candidate points that have been eliminated and whose total number of associated orders exceeds a preset threshold (e.g., 30) can be determined as a target candidate point set that meets the requirements. This allows for the selection of a target candidate point set that relatively effectively reflects the target user's personal habits and / or preferences. Subsequently, based on this target candidate point set, recommended locking points with higher reference value and better application effects can be determined for the target user.

[0218] Among them, the preset total order threshold can be determined based on the big data analysis results of the platform users as a whole, combined with the total number of historical orders for a single user.

[0219] The target candidate point set determined using this method includes candidate points that the target user has historically and habitually used to lock and park their shared device. The recommended locking points determined based on these locations are more suited to the target user's personal habits and preferences, and thus have a relatively high reference value.

[0220] As can be seen from the above, the operation processing method based on the shared device provided in the embodiment of this specification, before specific implementation, obtains and determines the locking point adapted to each user for each user based on the historical data of the user's use of the shared device, combined with the user's personal habits and preferences. During specific implementation, in the process of the target user using the target shared device, monitor whether the target user uses the target shared device to enter the vicinity of the target locking point associated with the target user; when it is detected that the target user enters the vicinity of the target locking point, a locking prompt is automatically initiated; and then, by detecting and based on the trigger request related to the locking prompt, the target shared device is operated accordingly. Specifically, it can be detected whether a trigger request related to the locking prompt is received within a first time period, and / or whether a locking trigger request for the locking prompt is received within a specified time period. For example, when it is detected that the use trigger request has not been received for more than a first time period, it can be determined that the target user has currently ended the use of the target shared device, and the target shared device can be automatically locked; on the contrary, when it is detected that the use trigger request is received within the first time period, it can be determined that the target user has not currently ended the use of the target shared device, and the current unlocked state of the target shared device can be maintained to avoid interfering with the target user's normal use of the target shared device. For another example, when it is detected that the lock trigger request is received within a specified time period, it can be determined that the target user has ended the use of the target shared device and actively confirmed to lock and return it, and the target shared device can be automatically locked. In this way, it can better adapt to the locking habits and personal preferences of users when using shared devices, distinguish between multiple different situations, and intelligently implement related operations such as automatic lock and return for shared devices, effectively simplifying user operations and improving the user experience.

[0221] This specification also provides an operation processing method based on a shared device, which may include the following contents during implementation:

[0222] S1: When a target user is detected to enter the vicinity of an associated location point using a target shared device, a prompt message is initiated; wherein the associated location point is associated with the target user;

[0223] S2: Detect and perform corresponding operations on the target shared device according to the trigger request related to the prompt information.

[0224] The above-mentioned associated position point may specifically include: a target locking point; correspondingly, the above-mentioned prompt information may include: a locking prompt.

[0225] Of course, the above-mentioned associated location points are merely illustrative. In specific implementations, the above-mentioned associated location points may also include other types of location points according to specific application scenarios and processing requirements. This specification does not limit this.

[0226] This specification provides a computer device, referring to Figure 6 The computer device includes a network communication port 601, a processor 602, and a memory 603, and the above structures are connected through internal cables so that each structure can perform specific data interaction.

[0227] The network communication port 601 can be used to receive a trigger instruction.

[0228] The processor 602 can be specifically used to respond to a trigger instruction and monitor whether the target user uses the target shared device to enter the vicinity of the target locking point; when it is detected that the target user uses the target shared device to enter the vicinity of the target locking point, initiate a locking prompt; wherein the target locking point is associated with the target user; detect and perform corresponding operations on the target shared device based on the trigger request related to the locking prompt.

[0229] The memory 603 may be specifically used to store corresponding instruction programs and other related intermediate data.

[0230] Based on the above method, the relevant structural performance of computer equipment can be effectively utilized, the data processing speed of electronic equipment can be improved, and the locked data processing based on shared equipment can be efficiently realized.

[0231] In this embodiment, the network communication port 601 can be a virtual port that is bound to different communication protocols, thereby being capable of sending or receiving different data. For example, the network communication port can be a port responsible for web data communication, a port responsible for FTP data communication, or a port responsible for email data communication. Furthermore, the network communication port can also be a physical communication interface or communication chip. For example, it can be a wireless mobile network communication chip, such as GSM or CDMA; it can also be a Wi-Fi chip; or it can be a Bluetooth chip.

[0232] In this embodiment, the processor 602 may be implemented in any suitable manner. For example, the processor may take the form of a microprocessor or a processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, an embedded microcontroller, etc. This specification is not intended to limit this.

[0233] In this embodiment, the memory 603 may include multiple levels. In a digital system, anything that can store binary data can be a memory. In an integrated circuit, a circuit with a storage function that has no physical form is also called a memory, such as RAM, FIFO, etc. In a system, a storage device with a physical form is also called a memory, such as a memory stick, TF card, etc.

[0234] The embodiments of this specification also provide a computer-readable storage medium based on the above-mentioned operation processing method based on a shared device, wherein the computer-readable storage medium stores computer program instructions, which, when executed, implement: when it is detected that the target user uses the target shared device to enter the vicinity of the target locking point, initiate a locking prompt; wherein the target locking point is associated with the target user; detect and perform corresponding operations on the target shared device based on a trigger request related to the locking prompt.

[0235] In this embodiment, the storage medium includes, but is not limited to, random access memory (RAM), read-only memory (ROM), cache, hard disk drive (HDD), or memory card. The memory can be used to store computer program instructions. The network communication unit can be an interface configured in accordance with the standards specified by the communication protocol for network connection communication.

[0236] In this embodiment, the functions and effects specifically implemented by the program instructions stored in the computer-readable storage medium can be explained in comparison with other implementations and will not be repeated here.

[0237] An embodiment of this specification also provides a computer program product, which at least includes a computer program, and when the computer program is executed by a processor, implements the following method steps: when it is detected that a target user uses a target shared device to enter the vicinity of a target locking point, initiating a locking prompt; wherein the target locking point is associated with the target user; detecting and performing corresponding operations on the target shared device based on a trigger request related to the locking prompt.

[0238] See Figure 7 As shown, the embodiment of this specification also provides an operation processing device based on a shared device, which may specifically include the following structural modules:

[0239] The initiating module 701 may be specifically configured to initiate a lock prompt when a target user is detected to be within the vicinity of a target lock point using a target shared device; wherein the target lock point is associated with the target user;

[0240] The operation module 702 may be specifically configured to detect and perform corresponding operations on the target shared device according to a trigger request related to the lock prompt.

[0241] In some embodiments, the trigger request may specifically include: an usage trigger request, a lock trigger request, etc.

[0242] In some embodiments, when the trigger request includes a usage trigger request, the above-mentioned operation module 702 can be specifically implemented to detect and perform corresponding operations on the target shared device according to the trigger request related to the lock prompt in the following manner: when no trigger request related to the lock prompt is received for more than a first time period, the target shared device is locked.

[0243] In some embodiments, the usage trigger request may specifically include: a first type of usage trigger request, or a second type of usage trigger request, etc.;

[0244] The first type of usage trigger request may specifically include: a renewal request for the target shared device initiated by the target user through the user terminal, or an unlocking request initiated by the target user by scanning the identification code of the target shared device;

[0245] The second type of usage trigger request may specifically include: an unlocking request initiated by a user other than the target user by scanning an identification code of the target shared device, etc.

[0246] In some embodiments, when a first type of usage trigger request for a lock prompt is received within a first time period, the device, when implemented, can also be used to: stop the lock operation and continue to maintain the first order currently associated with the target user.

[0247] In some embodiments, when a second type of usage trigger request for a lock prompt is received within a first time period, the device, when implemented, can also be used to: stop the lock operation and end the first order currently associated with the target user; and create a second order associated with other users.

[0248] In some embodiments, when no trigger request related to the lock prompt is received for more than a first time period, the device can also be used to: obtain motion status data of the target shared device within a second time period; determine whether the preset lock condition is met based on the motion status data of the target shared device within the second time period; and perform a lock operation on the target shared device if it is determined that the preset lock condition is met.

[0249] In some embodiments, when the trigger request includes a usage trigger request, the above-mentioned operation module 702, when implemented, can detect and perform corresponding operations on the target shared device based on the trigger request related to the lock prompt in the following manner: when a lock trigger request for the lock prompt is received within a specified time period, the target shared device is locked.

[0250] In some embodiments, the target locking point may specifically include at least one of the following: a recommended locking point selected by the target user, a locking point customized by the target user, a locking point obtained by the target user after modification based on the recommended locking point, an automatically determined recommended locking point for the target user, etc.

[0251] In some embodiments, the recommended closing point can be determined specifically in the following manner: obtaining the historical order records of the target user; determining multiple historical closing points based on the historical order records of the target user; constructing a corresponding set of candidate points based on the multiple historical closing points; and determining a recommended closing point associated with the target user based on the set of candidate points.

[0252] In some embodiments, when the device is implemented, a corresponding candidate point set can be constructed based on multiple historical locking points in the following manner: based on the historical order records of the target user, the historical locking times of each historical locking point are counted; the adjacent historical locking points are found based on the distances between the historical locking points; an initial point set is constructed based on the multiple historical locking points; in the initial point set, the corresponding historical locking times are marked for each historical locking point; and corresponding proximity marks are added to the adjacent historical locking points to obtain an adjusted initial point set; based on the adjusted initial point set, a corresponding candidate point set is determined through depth optimization search and / or breadth optimization search.

[0253] In some embodiments, when the device is implemented, the recommended locking point associated with the target user can be determined based on the candidate point set in the following manner: based on the historical order record of the target user, the local historical position record after the third time period from the unlocking is intercepted; based on the local historical position record, the local historical position record of the candidate point corresponding to the candidate points in the candidate point set is determined; based on the local historical position record of the candidate point, the time difference between the appearance time of the corresponding candidate point in the local historical position record of the candidate point and the locking time is calculated; and the local historical position record of the candidate point with a time difference greater than the first time period is determined as the historical passing record of the candidate point; the passing point is determined from the candidate points based on the historical passing record of the candidate point; the passing point is eliminated from the candidate point set; and the recommended locking point associated with the target user is determined based on the eliminated candidate point set.

[0254] In some embodiments, after the passing point is eliminated from the candidate point set, the device, when implemented, can also be used to: count the total number of associated orders of the candidate point set after elimination based on the historical order records of the target user; determine the target candidate point set that meets the requirements from the candidate point set after elimination based on the total number of associated orders of the candidate point set after elimination; and determine the recommended locking points associated with the target user based on the target candidate point set.

[0255] In some embodiments, when the device is implemented, it can also be used to: receive and respond to unlocking requests for the target shared device, and unlock the target shared device; from the third time after unlocking, obtain and monitor whether the target user uses the target shared device to enter the vicinity of the target locking point based on the location information of the target shared device.

[0256] In some embodiments, the target shared device may specifically include at least one of the following: a shared bicycle, a shared electric vehicle, a shared car, etc.

[0257] An embodiment of this specification also provides an operation processing device based on a shared device, which may specifically include the following structural modules: an initiation module, which may be specifically used to initiate a prompt message when it is detected that a target user uses a target shared device to enter the vicinity of an associated location point; wherein the associated location point is associated with the target user; an operation module, which may be specifically used to detect and perform corresponding operations on the target shared device based on a trigger request related to the prompt message.

[0258] It should be noted that the units, devices or modules described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. For the convenience of description, the above devices are described in terms of functions and are divided into various modules and described separately. Of course, when implementing this specification, the functions of each module can be implemented in the same or multiple software and / or hardware, or the module that implements the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0259] As can be seen from the above, the operation processing device based on shared devices provided in the embodiments of this specification can better adapt to the locking habits and personal preferences of users when using shared devices, and intelligently realize automatic locking and returning of shared devices, effectively simplifying user operations and improving user experience.

[0260] In a specific scenario example, the shared device operation processing method provided in this specification can be applied to realize automatic return point mining and user-free automatic locking of a two-wheeled vehicle (a shared device). The specific implementation process may include the following.

[0261] In this scenario, given the regulatory requirements for shared vehicles, the proportion of shared vehicles without physical locking devices offered by shared two-wheeled mobility companies is increasing, becoming the mainstream operating solution. Using existing methods, when returning a vehicle, users must pull out their phones, open the app, lock the vehicle, and confirm that the lock was successful before completing their order and leaving. This process takes an additional 20 to 30 seconds compared to shared vehicles with physical locking devices, creating a significant user experience loss. Faced with this problem, some companies are using NFC for faster interaction. However, tens of millions of existing smart hardware devices do not support NFC, and replacing them completely would be costly. Furthermore, not all users' phones support NFC, making this a suboptimal solution.

[0262] In response to the above problems and the root causes of the above problems, in this scenario example, a method is proposed to automatically lock the car based on the user's car usage habits through automatic judgment by the system and algorithm, so as to reduce the user's operation process and improve the user's car usage efficiency and experience.

[0263] The processing system constructed and used based on the above ideas includes at least two parts: a commonly used locking point recommendation / reporting module and a real-time parking determination module.

[0264] 1. Common lock point recommendation / reporting module:

[0265] 1. User submission function: Users can actively select several points as their frequently used locking points (as target locking points). For cities and businesses operating in a virtual site mode, the points are electronic fences corresponding to the full set of sites provided by the system. For the free return mode, the system will generate several candidate electronic fences and a full set of geohash8 as candidate points.

[0266] 2. Algorithm Identification Method: The system collects all historical vehicle usage records (e.g., historical order records) within a year and obtains all locking times and longitude and latitude records of the user. For example, if Mr. Zhang locked his vehicle near XX subway station between 7:00 and 9:00 three times in the past two weeks, XX subway station is selected as a candidate locking point. The specific calculation method for selecting candidate locking points is as follows:

[0267] a) Candidate point set selection: Obtain all order records of the user within one year. Based on the recorded lock points or the calculated order lock points, count the number of locks at each point and create a set V of records. Precompute the distances between all pairs of points in V. If the distance between points a and b is less than the specified distance X (dynamically adjustable, with a default value of 50 meters), then a and b are considered adjacent, and a record indicating the existence of an edge (a, b) is added to the set E. Enumerate all possible subgraphs using a graph traversal algorithm such as depth-first search (DFS) or breadth-first search (BFS). These subgraphs are then considered candidate point sets.

[0268] b) Illegal point (e.g., passing point) judgment: For each candidate point set, traverse up to x orders of the user in the past year (x defaults to 100), obtain all the location reporting information of each order after T1 seconds (e.g., the third time period, the default is 180) after the order is unlocked (from the user APP or the active reporting of the smart lock), calculate whether all locations are within the electronic fence of any point in the candidate point set, obtain the earliest location record time in the candidate point set (if any), if the difference between this time and the order lock time is greater than T2 seconds (e.g., the first time period, the default is 60), then record a suspected passing record for the point. Count the suspected passing records of all points in the candidate point set. If the number of suspected passing records of a point is greater than or equal to x (x defaults to 3) and the proportion exceeds x% (x defaults to 30), then delete the point (corresponding to the passing point).

[0269] c) Count the total number of orders o of all points in each candidate point set. If o>=n (dynamically adjustable, default is 5), the candidate point set is regarded as a legal candidate point set (eg, target candidate point set).

[0270] d) In the APP, a set of candidate points that meet the conditions is recommended to the user, and the user can select the candidate point set or a subset thereof as a commonly used locking point (set).

[0271] 2. Real-time parking determination module:

[0272] T1 seconds after the user unlocks the vehicle (the same as T1 in the illegal location determination), the user's trajectory is monitored. If the user's reported location is within the electronic fence of any commonly used locking point (for example, within the vicinity of the target locking point), the vehicle is automatically returned, and this time is recorded as t0.

[0273] a) The in-vehicle voice reminds the user, "The vehicle will automatically lock after T2 seconds (the same as T2 in illegal point determination). If you need to continue using the vehicle, please click on the app to continue using the vehicle within T2 seconds.

[0274] b) If the vehicle does not move for T3 seconds (e.g., the second duration) after the voice prompt (e.g., initiating the lock prompt) T2-T3 seconds, (if the smart lock has a sensor such as an accelerometer, the status of the sensor is used for identification; if there is no sensor, the location information such as GPS is used for identification), then automatic locking is triggered.

[0275] c) After the voice reminder and before the vehicle is automatically locked, if the user clicks to continue using the vehicle or re-scans the code, the order will not be completed and the locking instruction will be canceled; if another user scans the code, the locking instruction will be canceled, the order will be ended early, the unlocking instruction will be re-issued, and the next order will be started.

[0276] Through the above scenario examples, it is verified that the operation processing method based on shared devices provided in this manual can indeed reduce the time users spend on locking and greatly improve the car-using experience of core users.

[0277] Although this specification provides the method operation steps as described in the embodiments or flow charts, more or fewer operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the device or client product in practice is executed, it can be executed in sequence or in parallel according to the method shown in the embodiments or the drawings (for example, a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment). The term "comprise", "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or device including a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such process, method, product or device. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or device including the elements. Words such as first and second are used to represent names and do not represent any particular order.

[0278] Those skilled in the art will also appreciate that, in addition to implementing the controller in pure computer-readable program code, it is entirely possible to implement the same functionality by logically programming the method steps in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, embedded microcontrollers, and the like. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be considered structures within the hardware component. Alternatively, the devices for implementing various functions can be considered both software modules implementing the method and structures within the hardware component.

[0279] This specification may be described in the general context of computer-executable instructions, such as program modules, executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, classes, and the like that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer-readable storage media, including storage devices.

[0280] Through the description of the above embodiments, it can be seen that those skilled in the art can clearly understand that this specification can be implemented by means of software plus the necessary general hardware platform. Based on this understanding, the technical solution of this specification can essentially be embodied in the form of a software product. This computer software product can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, a mobile terminal, a server, or a network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments of this specification.

[0281] The various embodiments in this specification are described in a progressive manner. References to the common or similar parts of the various embodiments are sufficient. Each embodiment focuses on the differences from the other embodiments. This specification can be used in a variety of general-purpose or specialized computer system environments or configurations. For example, personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable electronic devices, network PCs, minicomputers, mainframe computers, and distributed computing environments that include any of the above systems or devices.

[0282] Although the present specification is described through embodiments, those skilled in the art will appreciate that there are many modifications and variations to the present specification without departing from the spirit of the present specification. It is intended that the appended claims include these modifications and variations without departing from the spirit of the present specification.

Claims

1. An operation processing method based on a shared device, characterized in that: include: When a target user is detected to be entering the vicinity of a target locking point using a target shared device, a locking prompt is initiated; wherein the target locking point is associated with the target user; Detect and perform corresponding operations on the target shared device based on the trigger request related to the lock prompt.

2. The method according to claim 1, characterized in that The trigger request includes: an activation trigger request or a lock trigger request.

3. The method according to claim 2, characterized in that In a case where the trigger request includes a usage trigger request, detecting and performing corresponding operations on the target shared device according to the trigger request related to the lock prompt, including: When no trigger request related to the lock prompt is received within a first time period, a lock operation is performed on the target shared device.

4. The method according to claim 3, characterized in that The usage trigger request includes: a first type of usage trigger request, or a second type of usage trigger request; The first type of usage trigger request includes: a renewal request for the target shared device initiated by the target user through the user terminal, or an unlocking request initiated by the target user by scanning the identification code of the target shared device; The second type of usage triggering request includes: an unlocking request initiated by a user other than the target user by scanning the identification code of the target shared device.

5. The method according to claim 4, characterized in that When a first type of usage trigger request for a lock prompt is received within a first time period, the method further includes: Stop the lock operation and continue to maintain the first order currently associated with the target user.

6. The method according to claim 4, characterized in that When a second type of usage trigger request for the lock prompt is received within the first time period, the method further includes: Stop the lock operation and end the first order currently associated with the target user; Create a second order associated with another user.

7. The method according to claim 3, characterized in that When no trigger request related to the lock-off prompt is received for more than the first time period, the method further includes: Acquire motion state data of the target shared device within the second time period; determining whether a preset locking condition is met based on the motion state data of the target shared device within the second time period; When it is determined that the preset locking condition is met, a locking operation is performed on the target shared device.

8. The method according to claim 2, characterized in that In a case where the trigger request includes a usage trigger request, detecting and performing corresponding operations on the target shared device according to the trigger request related to the lock prompt, including: When a lock triggering request for the lock prompt is received within a specified time period, a lock operation is performed on the target shared device.

9. The method according to claim 1, characterized in that The target locking point includes at least one of the following: a recommended locking point selected by the target user, a locking point customized by the target user, a locking point modified by the target user based on the recommended locking point, and an automatically determined recommended locking point for the target user.

10. The method according to claim 9, characterized in that The recommended locking point is determined in the following manner: Obtain historical order records of target users; Based on the target user's historical order records, multiple historical lock points are determined; Based on multiple historical locking points, a corresponding candidate point set is constructed; Based on the candidate point set, the recommended locking points associated with the target user are determined.

11. The method according to claim 10, characterized in that Based on multiple historical locking points, a corresponding candidate point set is constructed, including: According to the historical order records of the target user, the historical lock-out times of each historical lock-out point are counted; Calculate and find adjacent historical locking points based on the distance between them; Construct an initial point set based on multiple historical locking points; In the initial point set, the corresponding historical locking times are marked for each historical locking point; and corresponding adjacent marks are added to adjacent historical locking points to obtain an adjusted initial point set; According to the adjusted initial point set, a corresponding candidate point set is determined through depth optimization search and / or breadth optimization search.

12. The method according to claim 10, characterized in that Based on the candidate point set, the recommended engagement points associated with the target user are determined, including: Based on the target user's historical order records, extract the local historical location records after the third period of time since the unlocking; Determining, based on the local historical position records, local historical position records of candidate points corresponding to the candidate points in the candidate point set; Calculate the time difference between the appearance time and the lock time of the corresponding candidate point in the local historical position record of the candidate point based on the local historical position record of the candidate point; and determine the local historical position record of the candidate point with a time difference greater than the first time length as the historical passage record of the candidate point; Count and determine the passing points from the candidate points based on their historical passing records; Eliminating the passing point from the candidate point set; According to the eliminated candidate point set, the recommended locking point associated with the target user is determined.

13. The method according to claim 12, characterized in that After removing the passing point from the candidate point set, the method further includes: According to the historical order records of the target user, the total number of associated orders of the candidate point set after elimination is counted; According to the total number of associated orders of the eliminated candidate point set, a target candidate point set that meets the requirements is determined from the eliminated candidate point set; According to the target candidate point set, a recommended locking point associated with the target user is determined.

14. The method according to claim 1, wherein The method further comprises: Receive and respond to an unlock request for a target shared device, and perform an unlock operation on the target shared device; From the third time after unlocking, the target user is monitored to see whether he or she uses the target shared device to enter the vicinity of the target locking point based on the location information of the target shared device.

15. The method according to claim 1, wherein The target shared device includes at least one of the following: a shared bicycle, a shared electric vehicle, and a shared car.

16. An operation processing method based on a shared device, characterized in that: include: When it is detected that the target user enters the vicinity of the associated location point using the target shared device, a prompt message is initiated; wherein the associated location point is associated with the target user; Detect and perform corresponding operations on the target shared device based on the trigger request related to the prompt information.

17. An operation processing device based on a shared device, characterized in that: include: an initiating module, configured to initiate a lock prompt when detecting that a target user uses a target shared device to enter the vicinity of a target lock point; wherein the target lock point is associated with the target user; The operation module is used to detect and perform corresponding operations on the target shared device according to the trigger request related to the lock prompt.

18. A computer device, characterized in that: The method comprises a processor and a memory for storing processor-executable instructions, wherein the processor implements the steps of the method according to any one of claims 1 to 16 when executing the instructions.

19. A computer-readable storage medium, characterized in that Computer instructions are stored thereon, and when the instructions are executed by a processor, the steps of the method according to any one of claims 1 to 16 are implemented.

Images