How to use shared devices, shared device server, and shared devices

Abstract

This specification discloses one or more embodiments of a method for using a shared device, a shared device server, and a shared device. The method includes: receiving an unlock request from a user via a user terminal for a target shared device; the unlock request includes a first unlock method for the target shared device and the user's user information; the target shared device includes at least two different unlock methods; determining, based on the user information and preset credit rating verification rules, whether the user's credit rating needs to be verified when using the first unlock method; if so, sending a credit rating verification request for the user to a credit rating server; upon confirmation that the credit rating server has passed the user's credit rating verification, generating unlock authentication information and sending it to the shared device to be unlocked via the user terminal, the unlock authentication information being used to control the unlocking of the target shared device.

Description

Technical Field

[0001] This manual relates to the field of Internet of Things (IoT) application technology, and in particular to a method for using a shared device, a shared device server, and the shared device itself. Background Technology

[0002] The prevalence of shared devices in people's daily lives is increasing, bringing great convenience. However, in areas with high foot traffic, shortages of shared devices still occur. For example, during peak travel times, shared bicycles are scarce at major transportation hubs. Furthermore, some shared devices cannot be unlocked, rendering them unusable and further exacerbating the shortage. For instance, for shared bicycles that can only be unlocked by scanning a QR code or entering the device number, if the QR code or device number is damaged, it cannot be recognized or the device number cannot be fully entered, thus preventing the bicycle from being unlocked. Summary of the Invention

[0003] On one hand, one or more embodiments of this specification provide a method for using a shared device, applied to a shared device server, comprising: receiving an unlock request for a target shared device sent by a user through a user terminal, the unlock request including a first unlock method for the target shared device and user information of the user, the target shared device including at least two different unlock methods. Based on the user information and preset credit rating verification rules, determining whether the user's credit rating needs to be verified when using the first unlock method. If so, sending a credit rating verification request for the user to a credit rating server. Upon confirmation that the credit rating server has passed the user's credit rating verification, generating unlock authentication information and sending it to the shared device to be unlocked through the user terminal, the unlock authentication information being used to control the unlocking of the target shared device.

[0004] On the other hand, one or more embodiments of this specification provide a method for using a shared device, applied to a shared device, including: receiving unlock authentication information sent by a user terminal, the unlock authentication information including device identification information of a target shared device; verifying whether the device identification information of the shared device to be unlocked is consistent with the device identification information of the target shared device; if so, determining that the verification is successful, and controlling the shared device to be unlocked to unlock.

[0005] Furthermore, one or more embodiments of this specification provide a shared device server, comprising: a first receiving module, configured to receive an unlocking request for a target shared device sent by a user through a user terminal, the unlocking request including a first unlocking method for the target shared device and user information of the user, the target shared device including at least two different unlocking methods; a determining module, configured to determine, based on the user information and preset credit rating verification rules, whether the user's credit rating needs to be verified when using the first unlocking method; a first sending module, configured to, if so, send a credit rating verification request for the user to a credit rating server; and a generating and sending module, configured to, upon confirming that the credit rating server has passed the user's credit rating verification, generate unlocking authentication information and send it to the shared device to be unlocked through the user terminal, the unlocking authentication information being used to control the unlocking of the target shared device.

[0006] Furthermore, one or more embodiments of this specification provide a sharing device, comprising: a second receiving module, configured to receive unlocking authentication information sent by a user terminal, the unlocking authentication information including device identification information of a target sharing device; a verification module, configured to verify whether the device identification information of the sharing device to be unlocked is consistent with the device identification information of the target sharing device; and an unlocking module, configured to determine that the verification is successful and control the sharing device to be unlocked to unlock if the verification is successful.

[0007] Furthermore, one or more embodiments of this specification provide a shared device user device, including a processor and a memory electrically connected to the processor. The memory stores a computer program, and the processor is configured to call and execute the computer program from the memory to: receive an unlock request from a user via a user terminal for a target shared device, the unlock request including a first unlock method for the target shared device and user information of the user, the target shared device including at least two different unlock methods; determine, based on the user information and preset credit rating verification rules, whether the user's credit rating needs to be verified when using the first unlock method; if so, send a credit rating verification request for the user to a credit rating server; upon confirmation that the credit rating server has passed the user's credit rating verification, generate unlock authentication information and send it to the shared device to be unlocked via the user terminal, the unlock authentication information being used to control the unlocking of the target shared device.

[0008] Furthermore, one or more embodiments of this specification provide a shared device user device, including a processor and a memory electrically connected to the processor. The memory stores a computer program, and the processor is configured to call and execute the computer program from the memory to: receive unlock authentication information sent by a user terminal, the unlock authentication information including device identification information of a target shared device; verify whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device; if so, determine that the verification is successful, and control the shared device to be unlocked to unlock.

[0009] Furthermore, embodiments of this specification provide a storage medium for storing a computer program that can be executed by a processor to implement the following process: receiving an unlock request for a target shared device sent by a user through a user terminal, the unlock request including a first unlock method for the target shared device and the user's user information, the target shared device including at least two different unlock methods. Based on the user information and preset credit rating verification rules, determining whether the user's credit rating needs to be verified when using the first unlock method. If so, sending a credit rating verification request for the user to a credit rating server. Upon confirmation that the credit rating server has passed the user's credit rating verification, generating unlock authentication information and sending it to the shared device to be unlocked through the user terminal, the unlock authentication information being used to control the unlocking of the target shared device.

[0010] Furthermore, embodiments of this specification provide a storage medium for storing a computer program that can be executed by a processor to implement the following process: receiving unlock authentication information sent by a user terminal, the unlock authentication information including device identification information of a target shared device; verifying whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device; if so, determining that the verification is successful, and controlling the shared device to be unlocked to unlock. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in one or more embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a schematic diagram illustrating an application scenario of a shared device usage method according to an embodiment of this specification;

[0013] Figure 2This is a schematic flowchart illustrating a method of using a shared device according to an embodiment of this specification;

[0014] Figure 3 This is a schematic flowchart illustrating a method of using a shared device according to another embodiment of this specification;

[0015] Figure 4 This is a schematic swimlane diagram of a method of using a shared device according to an embodiment of this specification;

[0016] Figure 5 This is a schematic diagram of the structure of a shared device server according to an embodiment of this specification;

[0017] Figure 6 This is a schematic diagram of the structure of a shared device according to an embodiment of this specification;

[0018] Figure 7 This is a schematic block diagram of a shared device according to an embodiment of this specification. Detailed Implementation

[0019] This specification provides one or more embodiments of a method for using a shared device, a shared device server, and a shared device, in order to solve the problem that existing shared device unlocking methods are limited and do not fully utilize shared device resources.

[0020] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of one or more embodiments of this specification.

[0021] Figure 1 This is a schematic diagram illustrating an application scenario of a shared device usage method according to an embodiment of this specification, such as... Figure 1 As shown, this scenario includes: shared equipment 110, user terminal 120, shared equipment server 130, and credit rating server 140. The shared equipment 110 can be shared bicycles, shared umbrellas, shared power banks, shared cars, shared electric bicycles, etc. Figure 1 The image shows multiple shared bicycles parked in one location, illustrating the shared equipment 110. The user's terminal 120 can be a portable electronic device such as a mobile phone, tablet, or PDA. The shared equipment server 130 can be a standalone server or a server cluster consisting of multiple servers. Figure 1The shared equipment server 130 between China and Israel is illustrated as a standalone server. The credit rating server 140 can be a standalone server or a server cluster consisting of multiple servers. Figure 1 The Sino-Israeli credit rating server 140 is an example of a separate server.

[0022] In one embodiment, the user's terminal 120 is configured to send an unlock request to the shared device server 130 in response to a user trigger. The unlock request includes a first unlock method for the target shared device and the user's user information. The target shared device includes at least two different unlock methods. The shared device server 130 is configured to receive the unlock request sent by the user through the user terminal 120, and determine, based on the user information and preset credit rating verification rules, whether the user's credit rating needs to be verified when using the first unlock method. If it is determined that the user's credit rating needs to be verified when using the first unlock method, a credit rating verification request for the user is sent to the credit rating server 140. When the credit rating server 140 confirms that the user's credit rating verification is successful, unlock authentication information is generated and sent to the user terminal 120. The unlock authentication information is used to control the unlocking of the target shared device. The user terminal 120 is configured to send the unlock authentication information to the shared device to be unlocked when the user terminal 120 is communicating with the shared device to be unlocked. The shared device 110 is used to receive unlock authentication information sent by the user terminal 120. The unlock authentication information includes the device identification information of the target shared device, thereby verifying whether the device identification information of the shared device to be unlocked is consistent with the device identification information of the target shared device. If it is determined that the device identification information of the shared device to be unlocked is consistent with the device identification information of the target shared device, the verification is confirmed to be successful, and the shared device to be unlocked is controlled to unlock.

[0023] The following details the specific operations performed by shared device 110 and shared device server 130 during the use of shared devices. Figure 2 This is a schematic flowchart illustrating a method of using a shared device according to an embodiment of this specification. In this embodiment, the method of using a shared device is applied to, for example... Figure 1 The shared device server 130 is shown in the diagram. (As shown in the diagram...) Figure 2 As shown, the method may include:

[0024] S202, receive an unlock request for the target shared device sent by the user through the user terminal. The unlock request includes the first unlocking method of the target shared device and the user's user information.

[0025] In one embodiment, after discovering a shared device, the user can open a client application for the shared device on their terminal. This client application could be a shared device mini-program, a shared device application, or a shared device service webpage. The user should also enable location services on their terminal, such as GPS, for accurate location tracking, and enable Bluetooth to accurately locate the shared device. Then, the user can select the shared device they wish to unlock (the target shared device in this embodiment) through the client application. Activating the target shared device will bring up an unlocking method selection page. Selecting the first unlocking method on this page will trigger the user's terminal to send an unlock request to the target shared device.

[0026] In this embodiment, the target sharing device includes at least two different unlocking methods. Optionally, the unlocking methods of the target sharing device include multiples of the following: graphic code unlocking, device number unlocking, Bluetooth unlocking, and near-field communication (NFC) unlocking. The graphic code unlocking method includes, but is not limited to, barcode scanning and QR code scanning; the device number unlocking method can be performed by entering the device number; and the Bluetooth unlocking method can be performed by enabling Bluetooth on the user terminal. Near-field communication (NFC) is an emerging technology that allows devices (such as mobile phones) using NFC to exchange data when they are close to each other. Based on this, the NFC unlocking method can be performed by enabling NFC on the user terminal and bringing it close to the target sharing device. Specifically, in this embodiment, the first unlocking method can be Bluetooth unlocking and / or NFC unlocking.

[0027] In this embodiment, the user information carried in the unlock request may include the user account, user identity information, etc. It should be understood that before using the shared device through the shared device's client, the user needs to read and sign relevant authorization information. This authorization information includes, but is not limited to, authorizing the sending of the user account, user identity information, etc., to a third party during the unlocking process. The third party may be, for example, the shared device server, a credit rating server, etc.

[0028] In one embodiment, the unlock request is triggered by the user terminal when the user confirms that the target shared device cannot be unlocked using the second unlocking method. The second unlocking method is one or more of the target shared device's unlocking methods, namely, one or more of pattern code unlocking, device serial number unlocking, Bluetooth unlocking, and near-field communication (NFC) unlocking. For pattern code or device serial number unlocking, if the pattern code or device serial number is damaged, the user can confirm that this unlocking method cannot be used to unlock the target shared device. For Bluetooth or NFC unlocking, if the user attempts to unlock but fails, the user can confirm that this unlocking method cannot be used to unlock the target shared device. Specifically, in this embodiment, the second unlocking method can be a pattern code unlocking method and / or a device serial number unlocking method.

[0029] S204, based on user information and preset credit rating verification rules, determine whether the user's credit rating needs to be verified when the user adopts the first unlocking method.

[0030] Credit rating is a personal credit product, representing an online credit evaluation level for an individual, such as credit points or credit grades. The following embodiments will list three execution methods for S204: steps A1-A3, B1-B3, and C1-C2. It should be noted that in practical applications, one or more execution methods can be selected based on specific application scenario requirements to determine whether user credit rating verification is necessary when the user adopts the first unlocking method. This application embodiment does not limit this.

[0031] S206. If it is determined that the user's credit rating needs to be verified when the user adopts the first unlocking method, a credit rating verification request for the user is sent to the credit rating server.

[0032] The credit rating verification request includes the user's information. The credit rating server can query the user's credit rating based on this information and verify whether the user's credit rating meets the requirements for allowing the user to unlock the shared device. Optionally, the requirement for allowing the user to unlock the shared device could be that the user's credit rating is greater than a preset credit rating threshold.

[0033] S208: Upon confirming that the credit rating server has verified the user's credit rating, unlock authentication information is generated and sent to the shared device to be unlocked via the user's terminal. This unlock authentication information is used to control the unlocking of the target shared device.

[0034] In one embodiment, when it is confirmed that the credit rating server fails to verify the user's credit rating, the server can send the reason for the verification failure to the shared device server and terminate the current shared device usage process.

[0035] In one embodiment, after a user triggers a request from the user terminal to unlock the target shared device, the unlock authentication information can be sent to the shared device via a communication channel by establishing a communication connection between the user terminal and the shared device. For example, if the first unlocking method is Bluetooth unlocking, the unlock authentication information can be sent to the shared device via a Bluetooth channel by establishing a Bluetooth connection between the user terminal and the shared device. If the first unlocking method is Near Field Communication (NFC) unlocking, the unlock authentication information can be sent to the shared device via a NFC channel by establishing a NFC connection between the user terminal and the shared device.

[0036] It should be noted that, generally, the shared device to be unlocked is the target shared device mentioned above. However, in practical applications, there are situations where multiple shared devices are close to each other, such as a large number of shared bicycles parked at a transportation hub. This can easily lead to a situation where the target shared device that the user wants to unlock is different from the shared device that the user actually tries to unlock. In this case, the shared device that the user actually tries to unlock is the shared device to be unlocked in this embodiment. For example, after the user triggers the user terminal to send an unlock request to unlock shared bicycle a using near-field communication (NFC) unlocking, the user activates the NFC function on the user terminal and brings it close to the shared bicycle to send the unlock authentication information to the shared bicycle through the NFC channel. However, because multiple shared bicycles are parked close to each other, the user actually brings the user terminal close to shared bicycle b, resulting in the unlock authentication information being sent to shared bicycle b. In this example, shared bicycle a is the target shared device, and shared bicycle b is the shared device to be unlocked.

[0037] In this embodiment, the unlock authentication information may include the target shared device's device identification information, the user's credit rating, and the user's user information. The device identification information may be a unique identifier for the target shared device; it should be understood that each shared device has a unique identifier that distinguishes it from other shared devices. Optionally, the unlock authentication information may be a time-limited authentication token.

[0038] The technical solution employing one or more embodiments of this specification involves receiving an unlocking request from a user via a user terminal for a target shared device. The unlocking request includes a first unlocking method for the target shared device and the user's user information. The target shared device includes at least two different unlocking methods. Based on the user information and preset credit rating verification rules, it is determined whether credit rating verification is required when the user uses the first unlocking method. If credit rating verification is required, a credit rating verification request for the user is sent to a credit rating server. Upon successful credit rating verification by the credit rating server, unlocking authentication information is generated and sent to the shared device to be unlocked via the user terminal. This unlocking authentication information is used to control the unlocking of the target shared device. Therefore, this technical solution provides diverse unlocking methods for the shared device, effectively avoiding the problem of unlocking failures due to unlocking methods (such as damaged graphic codes or device serial numbers), which could affect the utilization rate of the shared device and promote the full utilization of shared device resources. Furthermore, by determining whether the user's current unlocking method requires verification of the user's credit rating, the system generates and sends unlocking authentication information for controlling the unlocking of shared devices only when the verification is successful. This achieves the effect of providing the first unlocking method for users whose credit rating meets the requirements, and prevents users whose credit rating does not meet the requirements from using the first unlocking method, thereby avoiding further impact on the utilization rate of shared devices.

[0039] In one embodiment, determining whether the user's credit rating needs to be verified when the user adopts the first unlocking method (i.e., S204) based on user information and preset credit rating verification rules can be performed as follows: steps A1-A3:

[0040] Step A1: Obtain the user's historical usage data for the shared device.

[0041] Optionally, the user's historical usage data for the shared device can be obtained based on the user's user information. For example, historical usage data may include the number of times the user used the shared device, whether the user settled the fee in a timely manner after each use of the shared device, and whether the user returned the shared device to the designated location after each use.

[0042] Step A2: Based on historical usage data, score the user's shared device usage behavior.

[0043] Following the example in step A1, optionally, each type of historical usage data carries a certain percentage of the score. For instance, the number of times a user uses the shared device accounts for 20% of the score, whether the user settles the payment promptly after each use accounts for 40%, whether the user returns the shared device to the designated location after each use accounts for 40%, and so on. By calculating the scores corresponding to the user's historical usage data of the shared device according to these percentages, the user's shared device usage behavior score can be obtained.

[0044] In this embodiment, the more frequently a user uses the shared device, the higher their shared device usage behavior score will be, calculated proportionally. Similarly, if a user settles payment promptly after each use, their shared device usage behavior score will also be higher, calculated proportionally. Furthermore, if a user returns the shared device to the designated location after each use, their shared device usage behavior score will also be higher, calculated proportionally. Therefore, a higher shared device usage behavior score indicates that the user is actively using the shared device.

[0045] Step A3: If the score is greater than or equal to the preset threshold, it is determined that the user's credit rating does not need to be verified when the user uses the first unlocking method; if the score is less than the preset threshold, it is determined that the user's credit rating needs to be verified when the user uses the first unlocking method.

[0046] In this embodiment, by setting a preset threshold, it is possible to distinguish between users who actively use shared devices and users who passively use shared devices. This simplifies the process of unlocking shared devices for users who actively use them, which is conducive to the full utilization of shared devices.

[0047] In one embodiment, determining whether credit rating verification is required when a user uses the first unlocking method, based on user information and preset credit rating verification rules (i.e., S204), can be performed as follows: steps B1-B3:

[0048] Step B1: Obtain the user credit rating verification conditions set by the administrator.

[0049] The credit rating verification conditions may include the unlocking request being triggered and sent during a specified usage period and / or in a specified usage area. Optionally, the specified usage period may be a period of high demand for shared equipment, such as morning and evening rush hours, holidays, or periods of high demand for shared equipment, or it may be a period of low demand for shared equipment, such as working hours on weekdays, nighttime, or early morning. The specified usage area may be an area of ​​high demand for shared equipment, such as pedestrian streets, central business districts, bus stations, or subway stations, or it may be an area of ​​low demand for shared equipment, such as suburbs or villages. Managers may set these conditions according to the specific application scenario requirements, and this application embodiment does not limit this.

[0050] Step B2: Determine whether the unlock request sent by the user meets the credit rating verification conditions.

[0051] In this embodiment, it can be determined whether the user triggered the sending of an unlock request during a specified usage period and / or in a specified usage area.

[0052] Step B3: If yes, then it is determined that the user's credit rating does not need to be verified when the user uses the first unlocking method; if no, then it is determined that the user's credit rating needs to be verified when the user uses the first unlocking method.

[0053] In this embodiment, by allowing administrators to flexibly set user credit rating verification conditions, the process of unlocking shared devices for some users can be simplified, which is conducive to the full utilization of shared devices.

[0054] In one embodiment, determining whether credit rating verification is required when a user adopts the first unlocking method (i.e., S204) based on user information and preset credit rating verification rules can be performed as follows: steps C1-C2:

[0055] Step C1: Obtain the correspondence between the unlocking method set by the administrator and whether or not it is necessary to verify the user's credit rating.

[0056] For example, administrators can set a mapping between Bluetooth unlocking methods and the credit ratings of users requiring verification, a mapping between Bluetooth unlocking methods and the credit ratings of users not requiring verification, a mapping between near-field communication (NFC) unlocking methods and the credit ratings of users requiring verification, a mapping between NFC unlocking methods and the credit ratings of users not requiring verification, and so on. In practical applications, administrators can set these parameters according to the specific application scenario requirements, and this application embodiment does not limit this.

[0057] Step C2: Based on the corresponding relationship, determine whether the first unlocking method requires verification of the user's credit rating.

[0058] In this embodiment, by allowing administrators to flexibly set whether each unlocking method requires verification of the user's credit rating, the process of unlocking shared devices for some users can be simplified, which is conducive to the full utilization of shared devices.

[0059] In one embodiment, if it is determined, based on user information and preset credit rating verification rules, that the user does not need to verify their credit rating when using the first unlocking method, then the process of unlocking the shared device to be unlocked using the first unlocking method is executed.

[0060] In this embodiment, if it is determined that the user's credit rating does not need to be verified when using the first unlocking method, unlocking authentication information is directly generated and sent to the shared device to be unlocked via the user terminal. The process of unlocking the shared device using the first unlocking method involves, when the first unlocking method is Bluetooth unlocking, establishing a Bluetooth connection between the user terminal and the shared device to be unlocked, and sending the unlocking authentication information to the shared device via the Bluetooth channel. When the first unlocking method is Near Field Communication (NFC) unlocking, establishing a NFC connection between the user terminal and the shared device to be unlocked, and sending the unlocking authentication information to the shared device via the NFC channel.

[0061] In one embodiment, after generating the unlock authentication information, the unlock authentication information can first be encrypted using the private key of the shared device server to obtain the first encrypted unlock authentication information. Then, the unlock authentication information after the first encryption is encrypted using the public key of the target shared device to obtain the second encrypted unlock authentication information.

[0062] In this embodiment, by encrypting the unlocking authentication information, the security of data exchange between the shared device server, user terminal and shared device can be ensured, the security risk of this process being attacked can be reduced, and the leakage of unlocking authentication information can be avoided.

[0063] In one embodiment, after executing S208, if the shared device to be unlocked is successfully unlocked, a successful unlocking message will be sent to the shared device server; if the shared device to be unlocked fails to unlock, a failed unlocking message will be sent to the shared device server.

[0064] In this embodiment, when the shared device server receives the unlock success information sent by the shared device to be unlocked, it can execute the following steps D1-D3:

[0065] Step D1: Continuously monitor the user's usage data for the shared device to be unlocked.

[0066] For example, the user's usage data for the shared device to be unlocked may include whether the user used the shared device, whether the user settled the fee in a timely manner after using the shared device, and whether the user returned the shared device to the designated location after using it.

[0067] Step D2: If the user uses the shared device to be unlocked normally, record the location information of the shared device to be unlocked after the user finishes using it.

[0068] Following the example in step D1, normal user behavior when using a shared device to be unlocked includes, but is not limited to: the user using the shared device; the user settling the bill promptly after using the shared device; and the user returning the shared device to the designated location after using it.

[0069] Step D3: Based on location information, maintain the second unlocking method for the shared device to be unlocked.

[0070] In this embodiment, by recording the location information of the shared device after it has been successfully unlocked and after normal use, the shared device service provider can accurately and efficiently maintain the second unlocking method of the shared device, thereby reducing the maintenance cost of the shared device.

[0071] In one embodiment, if a user uses the shared device to be unlocked normally, after the user finishes using it, i.e. after executing step D2, the credit rating server can send a first record of the user's normal use of the shared device to be unlocked. The credit rating server can then improve the user's credit rating based on the first record.

[0072] In this embodiment, after a shared device is successfully unlocked and normal use is completed, a record of normal use is sent to the credit rating server to actively maintain the user's credit rating. This ensures that each use of the shared device by the user will affect the user's credit rating. With multiple negative impacts, the user will be unable to unlock the shared device, resulting in losses for themselves. Therefore, this technical solution is conducive to promoting users to actively use the shared device normally, thus forming a virtuous cycle.

[0073] In one embodiment, after executing step D1, if it is determined that the user is using the shared device to be unlocked abnormally, an error message is sent to the user's terminal. The error message may include the cause of the error and a solution. The system monitors whether the user follows the solution. If the user does not follow the solution, a second record of the user's abnormal use of the shared device to be unlocked is sent to the credit rating server. The credit rating server uses this second record to lower the user's credit rating. If the user follows the solution, the current shared device usage process ends.

[0074] Following the example in step D1, abnormal user behavior related to the shared device to be unlocked includes, but is not limited to: the user not using the shared device; the user not settling the bill promptly after using the shared device; and the user not returning the shared device to the designated location after using it. Therefore, reasons for abnormal behavior include, but are not limited to: the user not using the shared device; the user not settling the bill promptly after using the shared device; and the user not returning the shared device to the designated location after using it. Correspondingly, solutions may include: locking the device; settling the bill; and moving the device to the designated location before returning it.

[0075] In this embodiment, when the shared device to be unlocked is not used normally and the user does not actively resolve the anomaly, the abnormal usage record is reported to the credit rating server to lower the user's credit rating. This means that every time the user uses the shared device, it will affect the user's credit rating. After multiple negative impacts, the user will be unable to unlock the shared device, thus causing losses to themselves. Therefore, this technical solution is conducive to promoting users to actively use the shared device normally, so as to form a virtuous cycle.

[0076] In one embodiment, upon receiving an unlocking failure message from the shared device to be unlocked, the following steps E1-E3 can be performed:

[0077] Step E1: Determine whether the shared device to be unlocked is the target shared device.

[0078] In this embodiment, the unlocking failure information may include the reason for the unlocking failure and the current location information of the shared device to be unlocked. The reason for the unlocking failure may be that the device identification information of the shared device to be unlocked is inconsistent with the device identification information of the target shared device, or it may simply be that the unlocking failed, without specifying a particular reason for the failure.

[0079] Optionally, if the unlocking failure is due to a discrepancy between the device identification information of the shared device to be unlocked and the device identification information of the target shared device, then it can be determined that the shared device to be unlocked is not the target shared device. If the reason for the unlocking failure is unknown, there is a possibility that the shared device to be unlocked is not the target shared device, or there is a possibility that the shared device to be unlocked is the target shared device, but the first unlocking method of the shared device has failed. Therefore, in the case where the reason for the unlocking failure is unknown, the distance deviation between the current location information of the shared device to be unlocked and the location information of the target shared device can be calculated. If the distance deviation is not zero, it can be determined that the shared device to be unlocked is not the target shared device.

[0080] Step E2: If the shared device to be unlocked is not the target shared device, then determine the route information between the target shared device and the shared device to be unlocked based on the current location information of the shared device to be unlocked.

[0081] In this embodiment, if the shared device to be unlocked is the target shared device, it means that the first unlocking method of the shared device has failed.

[0082] Step E3: Based on the route information, a switching shared device prompt message is sent to the user terminal. The switching shared device prompt message is used to inform the user that the currently unlocked shared device is inconsistent with the target shared device, and asks the user to confirm whether they need to switch to the target shared device.

[0083] In this embodiment, by analyzing the reasons for unlocking failure, if the user selects the wrong shared device to be unlocked, the user is prompted that the selection is wrong, and the user is informed of the route information between the wrongly selected shared device and the target shared device. This helps the user to promptly discover that the shared device being unlocked is inconsistent with the target shared device, and quickly find the target shared device to unlock, which is conducive to the full utilization of shared device resources.

[0084] Figure 3 This is a schematic flowchart illustrating a method of using a shared device according to another embodiment of this specification. In this embodiment, the method of using a shared device is applied to, for example... Figure 1 The shared device 110 shown is an example. Figure 3 As shown, the method may include:

[0085] S302, receive unlock authentication information sent by the user terminal, the unlock authentication information includes the device identification information of the target shared device.

[0086] Optionally, the unlock authentication information may also include the user's credit rating, user information, etc., and the unlock authentication information may be a time-limited authentication token.

[0087] S304, verify whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device.

[0088] S306 If the device identification information of the shared device to be unlocked matches the device identification information of the target shared device, the verification is confirmed to be successful, and the shared device to be unlocked is unlocked.

[0089] In one embodiment, if the device identification information of the shared device to be unlocked is inconsistent with the device identification information of the target shared device, an unlocking failure message is sent to the shared device server. The unlocking failure message may include the reason for the unlocking failure and the current location information of the shared device to be unlocked. Optionally, the reason for the unlocking failure may be that the device identification information of the shared device to be unlocked is inconsistent with the device identification information of the target shared device, or it may simply be that the unlocking failed, without specifying a particular reason for the failure.

[0090] The technical solution employing one or more embodiments of this specification involves receiving unlocking authentication information sent by a user terminal. This unlocking authentication information includes the device identification information of the target shared device. The system verifies whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device. If the device identification information of the shared device to be unlocked matches the device identification information of the target shared device, the verification is successful, and the shared device to be unlocked is unlocked. Therefore, in this technical solution, the shared device can unlock itself by verifying the unlocking authentication information, and upon successful verification, it can control its own unlocking. Compared to simply unlocking by scanning a graphic code or entering a device number, this technical solution reduces the strong dependence on the clear display of graphic codes and device numbers during the use of the shared device. It effectively avoids the problem of the shared device being unable to unlock due to unlocking method failure (such as damaged graphic codes or damaged device numbers), thus affecting the utilization rate of the shared device and promoting the full utilization of shared device resources.

[0091] In one embodiment, the unlock authentication information is encrypted unlock authentication information. After receiving the unlock authentication information sent by the user terminal (i.e., S302), the following steps F1-F3 can be executed:

[0092] Step F1 involves decrypting the encrypted unlock authentication information.

[0093] Optionally, step F1 can be performed as follows: First, the encrypted unlocking authentication information is decrypted for the first time using the private key of the shared device to be unlocked, to obtain the unlocking authentication information after the first decryption. Then, the unlocking authentication information after the first decryption is decrypted for the second time using the public key of the shared device server, to obtain the device identification information of the target shared device.

[0094] Step F2: If decryption is successful, then verify whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device.

[0095] If decryption fails in step F3, it means that the shared device to be unlocked is not the target shared device.

[0096] In this embodiment, by encrypting the transmission of unlocking authentication information, the security of data exchange between the user terminal and the shared device can be ensured, the security risk of this process being attacked can be reduced, and the leakage of unlocking authentication information can be avoided.

[0097] The following describes the method for using shared equipment provided in this embodiment through a specific scenario. In this embodiment, the method for using shared equipment is applied to the scenario of using shared bicycles. A schematic diagram of the specific application scenario is shown below. Figure 1As shown in this embodiment, the method of using the shared device is explained by assuming that the target shared device and the shared device to be unlocked are the same. The shared device is a shared bicycle, and the shared device server is a shared bicycle server. Figure 4 The illustrated embodiment uses this scenario as an example for explanation.

[0098] Figure 4 This is a schematic swimlane diagram illustrating a method of using a shared device according to an embodiment of this specification. Figure 4 As shown, the method of using shared devices may include the following steps S4.1-S4.12:

[0099] S4.1 If a user confirms that the second unlocking method for the shared bicycle cannot be used to unlock it, the user terminal is triggered to send an unlocking request to the shared bicycle server.

[0100] The unlock request includes a first unlocking method for the shared bicycle and the user's information. The shared bicycle includes at least two different unlocking methods, such as multiple methods including pattern code unlocking, device number unlocking, Bluetooth unlocking, and near-field communication unlocking. In this embodiment, the first unlocking method can be Bluetooth unlocking and / or near-field communication unlocking, and the second unlocking method can be pattern code unlocking and / or device number unlocking.

[0101] S4.2 The shared bicycle server determines whether the user's credit rating needs to be verified when the user uses the first unlocking method based on the user information and the preset credit rating verification rules; if yes, then execute S4.3; if no, then execute S4.6.

[0102] The above embodiments list three execution methods for S4.2, namely steps A1-A3, steps B1-B3 and steps C1-C2. In practical applications, the above three execution methods can be freely combined to determine whether the user's credit rating needs to be verified when the user adopts the first unlocking method. This application embodiment does not limit this.

[0103] S4.3 The shared bicycle server sends a credit rating verification request for the user to the credit rating server.

[0104] The credit rating verification request includes the user's information. The credit rating server can query the user's credit rating based on this information and verify whether the user's credit rating meets the requirements for allowing the user to unlock shared bicycles.

[0105] S4.4 The credit rating server verifies the user's credit rating; if the verification fails, proceed to S4.5; if the verification passes, proceed to S4.6.

[0106] S4.5 The credit rating server sends the verification failure reason to the shared bicycle server and terminates the current shared bicycle usage process.

[0107] S4.6 The shared bicycle server generates unlock authentication information and encrypts it to obtain encrypted unlock authentication information.

[0108] The unlock authentication information is used to control the unlocking of shared bicycles, and may include the bicycle's identification information. Optionally, the unlock authentication information can be first encrypted using the private key of the shared device server to obtain the first encrypted unlock authentication information, and then the first encrypted unlock authentication information can be encrypted a second time using the public key of the target shared device to obtain the second encrypted unlock authentication information.

[0109] S4.7 The shared bicycle server sends the encrypted unlock authentication information to the user's terminal.

[0110] S4.8 The user terminal communicates with the shared bicycle and sends the encrypted unlocking authentication information to the shared bicycle.

[0111] S4.9 Shared bicycles decrypt the encrypted unlock authentication information.

[0112] Optionally, the encrypted unlocking authentication information can be decrypted first using the private key of the shared device to be unlocked, and then the unlocking authentication information after the first decryption can be decrypted a second time using the public key of the shared device server, to obtain the device identification information of the target shared device.

[0113] S4.10 Verify whether the bicycle identification information of the shared bicycle to be unlocked is consistent with the bicycle identification information in the unlocking authentication information; if not, proceed to S4.11; if yes, proceed to S4.12.

[0114] S4.11 Send an unlock failure message to the shared bicycle server.

[0115] S4.12, Control the unlocking of shared bicycles.

[0116] The specific processes of S4.1-S4.12 described above have been explained in detail in the above embodiments and will not be repeated here.

[0117] The technical solution employing one or more embodiments of this specification involves receiving a user's unlocking request for a shared bicycle sent via a user terminal. The unlocking request includes a first unlocking method for the shared bicycle and the user's information. The shared bicycle includes at least two different unlocking methods. Based on the user information and preset credit rating verification rules, it is determined whether credit rating verification is required when the user uses the first unlocking method. If credit rating verification is required, a credit rating verification request is sent to a credit rating server. Upon successful verification of the user's credit rating by the credit rating server, unlocking authentication information is generated and sent to the shared bicycle to be unlocked via the user terminal. This unlocking authentication information is used to control the unlocking of the shared bicycle. Therefore, this technical solution provides diverse unlocking methods for shared bicycles, effectively avoiding the problem of shared bicycles being unable to unlock due to unlocking method failures (such as damaged graphic codes or bicycle serial numbers), thus affecting the utilization rate of shared bicycles and promoting the full utilization of shared bicycle resources. Furthermore, by determining whether the user's current unlocking method requires verification of the user's credit rating, the system generates and sends unlocking authentication information for controlling the unlocking of shared bicycles only when the verification is successful. This achieves the effect of providing the first unlocking method for users whose credit rating meets the requirements, and prevents users whose credit rating does not meet the requirements from using the first unlocking method, thereby avoiding further impact on the utilization rate of shared bicycles.

[0118] In summary, specific embodiments of this subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing can be advantageous.

[0119] The above describes the method of using a shared device provided by one or more embodiments of this specification. Based on the same idea, one or more embodiments of this specification also provide a shared device server and a shared device.

[0120] Figure 5 This is a schematic diagram of the structure of a shared device server according to an embodiment of this specification. Please refer to it. Figure 5 The shared device server may include:

[0121] The first receiving module 510 is used to receive an unlocking request for a target shared device sent by a user through a user terminal; the unlocking request includes a first unlocking method of the target shared device and the user's user information; the target shared device includes at least two different unlocking methods.

[0122] The determination module 520 is used to determine whether the user's credit rating needs to be verified when the user adopts the first unlocking method, based on the user information and the preset credit rating verification rules.

[0123] The first sending module 530 is used to send a credit rating verification request for the user to the credit rating server if the condition is met.

[0124] The generation and sending module 540 is used to generate unlock authentication information when the credit rating server confirms that the user's credit rating has been verified, and send it to the shared device to be unlocked through the user terminal. The unlock authentication information is used to control the unlocking of the target shared device.

[0125] In one embodiment, the unlock request is triggered by the user terminal when it is confirmed that the second unlocking method for the target shared device cannot be used to unlock it.

[0126] In one embodiment, the determining module 520 includes:

[0127] The first acquisition unit is used to acquire historical usage data of users for shared devices;

[0128] The rating unit is used to rate users' shared device usage behavior based on historical usage data;

[0129] The first determining unit is used to determine that if the score is greater than or equal to a preset threshold, the user does not need to verify the user's credit rating when using the first unlocking method; if the score is less than the preset threshold, the user needs to verify the user's credit rating when using the first unlocking method.

[0130] In one embodiment, the determining module 520 includes:

[0131] The second acquisition unit is used to acquire the credit rating verification conditions set by the administrator for users; the credit rating verification conditions include the unlocking request being triggered and sent during a specified usage period and / or in a specified usage area;

[0132] The second determining unit is used to determine whether the unlock request sent by the user meets the credit rating verification conditions.

[0133] The third determining unit is used to determine, if yes, that the user does not need to verify the user's credit rating when using the first unlocking method; otherwise, it determines that the user needs to verify the user's credit rating when using the first unlocking method.

[0134] In one embodiment, the shared device server also includes:

[0135] The first execution module is used to perform the process of unlocking the shared device to be unlocked by using the first unlocking method if it is determined, based on user information and preset credit rating verification rules, that the user does not need to verify the user's credit rating when using the first unlocking method.

[0136] In one embodiment, the shared device server also includes:

[0137] The first encryption processing module is used to perform a first encryption processing on the unlock authentication information using the private key of the shared device server after generating the unlock authentication information, so as to obtain the unlock authentication information after the first encryption processing.

[0138] The second encryption processing module is used to perform a second encryption processing on the unlock authentication information after the first encryption processing using the public key of the target shared device, so as to obtain the encrypted unlock authentication information.

[0139] In one embodiment, the shared device server also includes:

[0140] The first monitoring module is used to continuously monitor the user's usage data of the shared device to be unlocked after receiving the unlock success information sent by the shared device to be unlocked;

[0141] The location recording module is used to record the location information of the shared device to be unlocked after the user finishes using it, if the user is using the shared device normally.

[0142] The maintenance module is used to maintain the second unlocking method for the shared device to be unlocked based on location information.

[0143] In one embodiment, the shared device server also includes:

[0144] The first record feedback module is used to provide feedback to the credit rating server after the user ends use of the shared device if the user has used it normally. The credit rating server is used to improve the user's credit rating based on the first record.

[0145] In one embodiment, the shared device server also includes:

[0146] The second sending module is used to send an abnormal prompt message to the user terminal if the user uses the shared device to be unlocked abnormally; the abnormal prompt message includes the cause of the abnormality and the solution.

[0147] The second monitoring module is used to monitor whether the user handles the exception according to the resolution method.

[0148] The second record feedback module is used to report a second record of abnormal use of the shared device to be unlocked by the user to the credit rating server if no; the credit rating server is used to lower the user's credit rating based on the second record.

[0149] The technical solution employing one or more embodiments of this specification involves receiving an unlocking request from a user via a user terminal for a target shared device. The unlocking request includes a first unlocking method for the target shared device and the user's user information. The target shared device includes at least two different unlocking methods. Based on the user information and preset credit rating verification rules, it is determined whether credit rating verification is required when the user uses the first unlocking method. If credit rating verification is required, a credit rating verification request for the user is sent to a credit rating server. Upon successful credit rating verification by the credit rating server, unlocking authentication information is generated and sent to the shared device to be unlocked via the user terminal. This unlocking authentication information is used to control the unlocking of the target shared device. Therefore, this technical solution provides diverse unlocking methods for the shared device, effectively avoiding the problem of unlocking failures due to unlocking methods (such as damaged graphic codes or device serial numbers), which could affect the utilization rate of the shared device and promote the full utilization of shared device resources. Furthermore, by determining whether the user's current unlocking method requires verification of the user's credit rating, the system generates and sends unlocking authentication information for controlling the unlocking of shared devices only when the verification is successful. This achieves the effect of providing the first unlocking method for users whose credit rating meets the requirements, and prevents users whose credit rating does not meet the requirements from using the first unlocking method, thereby avoiding further impact on the utilization rate of shared devices.

[0150] Those skilled in the art will understand that the aforementioned shared device server can be used to implement the shared device usage method described above. The detailed description therein should be similar to the method description above, and will not be repeated here to avoid redundancy.

[0151] Figure 6 This is a schematic diagram of a shared device according to an embodiment of this specification. Please refer to it. Figure 6 Shared devices may include:

[0152] The second receiving module 610 is used to receive unlock authentication information sent by the user terminal; the unlock authentication information includes the device identification information of the target shared device;

[0153] The verification module 620 is used to verify whether the device identification information of the shared device to be unlocked is consistent with the device identification information of the target shared device.

[0154] The unlocking module 630 is used to confirm that the verification is successful and to control the unlocking of the shared device to be unlocked if the verification is successful.

[0155] In one embodiment, the unlock authentication information is encrypted unlock authentication information;

[0156] Shared devices also include:

[0157] The decryption processing module is used to decrypt the encrypted unlock authentication information after receiving the unlock authentication information sent by the user terminal.

[0158] The second execution module is used to verify whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device if the decryption is successful.

[0159] The technical solution employing one or more embodiments of this specification involves receiving unlocking authentication information sent by a user terminal. This unlocking authentication information includes the device identification information of the target shared device. The system verifies whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device. If the device identification information of the shared device to be unlocked matches the device identification information of the target shared device, the verification is successful, and the shared device to be unlocked is unlocked. Therefore, in this technical solution, the shared device can unlock itself by verifying the unlocking authentication information, and upon successful verification, it can control its own unlocking. Compared to simply unlocking by scanning a graphic code or entering a device number, this technical solution reduces the strong dependence on the clear display of graphic codes and device numbers during the use of the shared device. It effectively avoids the problem of the shared device being unable to unlock due to unlocking method failure (such as damaged graphic codes or damaged device numbers), thus affecting the utilization rate of the shared device and promoting the full utilization of shared device resources.

[0160] Those skilled in the art will understand that the aforementioned shared device can be used to implement the shared device usage method described above, and the detailed description therein should be similar to the method description above. To avoid being cumbersome, it will not be repeated here.

[0161] Based on the same idea, one or more embodiments of this specification also provide a shared device usage device, such as... Figure 7As shown. The shared device user device can vary significantly due to differences in configuration or performance, and may include one or more processors 701 and memory 702. Memory 702 may store one or more application programs or data. Memory 702 can be temporary or persistent storage. The application programs stored in memory 702 may include one or more modules (not shown), each module including a series of computer-executable instructions for the shared device user device. Furthermore, processor 701 may be configured to communicate with memory 702 and execute the series of computer-executable instructions in memory 702 on the shared device user device. The shared device user device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input / output interfaces 705, and one or more keyboards 706.

[0162] Specifically, in this embodiment, the shared device uses a device including a memory and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for use in the shared device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0163] Receives an unlock request for a target shared device sent by a user through a user terminal; the unlock request includes the first unlock method of the target shared device and the user's user information; the target shared device includes at least two different unlock methods;

[0164] Based on user information and preset credit rating verification rules, determine whether the user's credit rating needs to be verified when the user adopts the first unlocking method;

[0165] If so, a credit rating verification request for the user is sent to the credit rating server.

[0166] Once the credit rating server confirms that the user's credit rating has been verified, unlock authentication information is generated and sent to the shared device to be unlocked via the user's terminal. The unlock authentication information is used to control the unlocking of the target shared device.

[0167] The technical solution employing one or more embodiments of this specification involves receiving an unlocking request from a user via a user terminal for a target shared device. The unlocking request includes a first unlocking method for the target shared device and the user's user information. The target shared device includes at least two different unlocking methods. Based on the user information and preset credit rating verification rules, it is determined whether credit rating verification is required when the user uses the first unlocking method. If credit rating verification is required, a credit rating verification request for the user is sent to a credit rating server. Upon successful credit rating verification by the credit rating server, unlocking authentication information is generated and sent to the shared device to be unlocked via the user terminal. This unlocking authentication information is used to control the unlocking of the target shared device. Therefore, this technical solution provides diverse unlocking methods for the shared device, effectively avoiding the problem of unlocking failures due to unlocking methods (such as damaged graphic codes or device serial numbers), which could affect the utilization rate of the shared device and promote the full utilization of shared device resources. Furthermore, by determining whether the user's current unlocking method requires verification of the user's credit rating, the system generates and sends unlocking authentication information for controlling the unlocking of shared devices only when the verification is successful. This achieves the effect of providing the first unlocking method for users whose credit rating meets the requirements, and prevents users whose credit rating does not meet the requirements from using the first unlocking method, thereby avoiding further impact on the utilization rate of shared devices.

[0168] In one embodiment, the shared device uses a device including a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for use in the shared device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0169] Receive unlock authentication information sent by the user terminal; the unlock authentication information includes the device identification information of the target shared device;

[0170] Verify whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device;

[0171] If so, the verification is confirmed to be successful, and the shared device to be unlocked is unlocked.

[0172] The technical solution employing one or more embodiments of this specification involves receiving unlocking authentication information sent by a user terminal. This unlocking authentication information includes the device identification information of the target shared device. The system verifies whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device. If the device identification information of the shared device to be unlocked matches the device identification information of the target shared device, the verification is successful, and the shared device to be unlocked is unlocked. Therefore, in this technical solution, the shared device can unlock itself by verifying the unlocking authentication information, and upon successful verification, it can control its own unlocking. Compared to simply unlocking by scanning a graphic code or entering a device number, this technical solution reduces the strong dependence on the clear display of graphic codes and device numbers during the use of the shared device. It effectively avoids the problem of the shared device being unable to unlock due to unlocking method failure (such as damaged graphic codes or damaged device numbers), thus affecting the utilization rate of the shared device and promoting the full utilization of shared device resources.

[0173] One or more embodiments of this specification also provide a storage medium storing one or more computer programs, the one or more computer programs including instructions that, when executed by an electronic device including multiple applications, enable the electronic device to perform various processes of the above-described shared device usage method embodiments, and specifically for performing:

[0174] Receives an unlock request for a target shared device sent by a user through a user terminal; the unlock request includes the first unlock method of the target shared device and the user's user information; the target shared device includes at least two different unlock methods;

[0175] Based on user information and preset credit rating verification rules, determine whether the user's credit rating needs to be verified when the user adopts the first unlocking method;

[0176] If so, a credit rating verification request for the user is sent to the credit rating server.

[0177] Once the credit rating server confirms that the user's credit rating has been verified, unlock authentication information is generated and sent to the shared device to be unlocked via the user's terminal. The unlock authentication information is used to control the unlocking of the target shared device.

[0178] The technical solution employing one or more embodiments of this specification involves receiving an unlocking request from a user via a user terminal for a target shared device. The unlocking request includes a first unlocking method for the target shared device and the user's user information. The target shared device includes at least two different unlocking methods. Based on the user information and preset credit rating verification rules, it is determined whether credit rating verification is required when the user uses the first unlocking method. If credit rating verification is required, a credit rating verification request for the user is sent to a credit rating server. Upon successful credit rating verification by the credit rating server, unlocking authentication information is generated and sent to the shared device to be unlocked via the user terminal. This unlocking authentication information is used to control the unlocking of the target shared device. Therefore, this technical solution provides diverse unlocking methods for the shared device, effectively avoiding the problem of unlocking failures due to unlocking methods (such as damaged graphic codes or device serial numbers), which could affect the utilization rate of the shared device and promote the full utilization of shared device resources. Furthermore, by determining whether the user's current unlocking method requires verification of the user's credit rating, the system generates and sends unlocking authentication information for controlling the unlocking of shared devices only when the verification is successful. This achieves the effect of providing the first unlocking method for users whose credit rating meets the requirements, and prevents users whose credit rating does not meet the requirements from using the first unlocking method, thereby avoiding further impact on the utilization rate of shared devices.

[0179] One or more embodiments of this specification also provide a storage medium storing one or more computer programs, the one or more computer programs including instructions that, when executed by an electronic device including multiple applications, enable the electronic device to perform various processes of the above-described shared device usage method embodiments, and specifically for performing:

[0180] Receive unlock authentication information sent by the user terminal; the unlock authentication information includes the device identification information of the target shared device;

[0181] Verify whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device;

[0182] If so, the verification is confirmed to be successful, and the shared device to be unlocked is unlocked.

[0183] The technical solution employing one or more embodiments of this specification involves receiving unlocking authentication information sent by a user terminal. This unlocking authentication information includes the device identification information of the target shared device. The system verifies whether the device identification information of the shared device to be unlocked matches the device identification information of the target shared device. If the device identification information of the shared device to be unlocked matches the device identification information of the target shared device, the verification is successful, and the shared device to be unlocked is unlocked. Therefore, in this technical solution, the shared device can unlock itself by verifying the unlocking authentication information, and upon successful verification, it can control its own unlocking. Compared to simply unlocking by scanning a graphic code or entering a device number, this technical solution reduces the strong dependence on the clear display of graphic codes and device numbers during the use of the shared device. It effectively avoids the problem of the shared device being unable to unlock due to unlocking method failure (such as damaged graphic codes or damaged device numbers), thus affecting the utilization rate of the shared device and promoting the full utilization of shared device resources.

[0184] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0185] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing one or more embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0186] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0187] This specification describes one or more embodiments of methods, apparatus (systems), and computer program products according to embodiments of this specification with reference to flowchart illustrations and / or block diagrams. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, produce a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0188] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0189] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0190] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0191] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0192] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0193] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0194] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. This specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0195] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0196] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of one or more embodiments of this specification.

Claims

1. A method for using a shared device, applied to a shared device server, the method comprising: Receive unlock requests for the target shared device sent by the user through the user terminal; The unlock request includes the first unlocking method of the target shared device and the user's user information; The target sharing device includes at least two different unlocking methods; the first unlocking method includes Bluetooth unlocking and / or near-field communication unlocking; the unlocking request is triggered by the user terminal when the user confirms that the second unlocking method of the target sharing device cannot be used to unlock it; the second unlocking method includes graphic code unlocking and device number unlocking; the unlocking request is sent by the user through the first unlocking method selection page of the target sharing device; the target sharing device unlocking method selection page is displayed by the user through the target sharing device on the client page of the sharing device. Based on the user information and the preset credit rating verification rules, determine whether the user's credit rating needs to be verified when the user uses the first unlocking method; If so, a credit rating verification request for the user is sent to the credit rating server. When the credit rating server confirms that the user's credit rating has been verified, unlock authentication information is generated and sent to the shared device to be unlocked through the user terminal. The unlock authentication information is used to control the unlocking of the target shared device.

2. The method according to claim 1, wherein determining whether the user's credit rating needs to be verified when the user uses the first unlocking method based on the user information and preset credit rating verification rules includes: Obtain the user's historical usage data for the shared device; Based on the historical usage data, the user's shared device usage behavior is scored; If the score is greater than or equal to a preset threshold, it is determined that the user does not need to verify the user's credit rating when using the first unlocking method; If the score is less than the preset threshold, it is determined that the user's credit rating needs to be verified when the user uses the first unlocking method.

3. The method according to claim 1, wherein determining whether the user's credit rating needs to be verified when the user uses the first unlocking method based on the user information and preset credit rating verification rules includes: Obtain the user's credit rating verification conditions set by the administrator; The credit rating verification conditions include the unlocking request being triggered and sent during a specified usage period and / or in a specified usage area; Determine whether the unlock request sent by the user meets the credit rating verification conditions; If so, then it is determined that the user does not need to verify the user's credit rating when using the first unlocking method; If not, then it is determined that the user's credit rating needs to be verified when the user uses the first unlocking method.

4. The method according to claim 1, further comprising: If, based on the user information and preset credit rating verification rules, it is determined that the user does not need to verify their credit rating when using the first unlocking method, then the process of unlocking the shared device to be unlocked using the first unlocking method is executed.

5. The method according to claim 1, wherein after generating the unlock authentication information, the method further comprises: The unlock authentication information is first encrypted using the private key of the shared device server to obtain the first encrypted unlock authentication information; The unlock authentication information after the first encryption is encrypted a second time using the public key of the target shared device to obtain the encrypted unlock authentication information.

6. The method according to claim 1, further comprising: Upon receiving a successful unlock message from the shared device to be unlocked, continuously monitor the user's usage data of the shared device to be unlocked; If the user uses the shared device to be unlocked normally, then after the user finishes using it, the location information of the shared device to be unlocked is recorded. Based on the location information, the second unlocking method of the shared device to be unlocked is maintained.

7. The method according to claim 6, wherein if the user is using the shared device to be unlocked normally, the method further includes, after the user ends use: The credit rating server is provided with the first record of the user's normal use of the shared device to be unlocked; The credit rating server is used to improve the user's credit rating based on the first record.

8. The method according to claim 6, further comprising: If the user uses the shared device to be unlocked abnormally, an abnormal prompt message will be sent to the user's terminal; The error message includes the cause of the error and the solution; Monitor whether the user handles the exception according to the described solution; If not, the credit rating server will send a second record of the user's abnormal use of the shared device to be unlocked to the credit rating server; the credit rating server will then lower the user's credit rating based on the second record.

9. A shared device server, comprising: The first receiving module is used to receive the unlocking request for the target shared device sent by the user through the user terminal; The unlock request includes the first unlocking method of the target shared device and the user's user information; The target shared device includes at least two different unlocking methods; the first unlocking method includes Bluetooth unlocking and / or near-field communication unlocking; the unlocking request is triggered by the user terminal when the user confirms that the second unlocking method of the target shared device cannot be used to unlock it; the second unlocking method includes graphic code unlocking and device number unlocking; the unlocking request is sent by the user through the first unlocking method on the unlocking method selection page of the target shared device; The unlocking method selection page for the target shared device is displayed by the user on the client page of the target shared device; The determining module is used to determine, based on the user information and preset credit rating verification rules, whether the user's credit rating needs to be verified when the user adopts the first unlocking method; The first sending module is used to send a credit rating verification request for the user to the credit rating server if the condition is met. The generation and sending module is used to generate unlock authentication information when the credit rating server confirms that the user's credit rating verification is successful, and send it to the shared device to be unlocked through the user terminal. The unlock authentication information is used to control the unlocking of the target shared device.

10. A shared device user device, comprising: processor; as well as A memory configured to store computer-executable instructions, which, when executed, enable the processor to: Receives an unlock request for a target shared device sent by a user through a user terminal; the unlock request includes a first unlocking method for the target shared device and the user's user information; The target sharing device includes at least two different unlocking methods; the first unlocking method includes Bluetooth unlocking and / or near-field communication unlocking; the unlocking request is triggered by the user terminal when the user confirms that the second unlocking method of the target sharing device cannot be used to unlock it; the second unlocking method includes graphic code unlocking and device number unlocking; the unlocking request is sent by the user through the first unlocking method selection page of the target sharing device; the target sharing device unlocking method selection page is displayed by the user through the target sharing device on the client page of the sharing device. Based on the user information and the preset credit rating verification rules, determine whether the user's credit rating needs to be verified when the user uses the first unlocking method; If so, a credit rating verification request for the user is sent to the credit rating server. When the credit rating server confirms that the user's credit rating has been verified, unlock authentication information is generated and sent to the shared device to be unlocked through the user terminal. The unlock authentication information is used to control the unlocking of the target shared device.

11. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Receives an unlock request for a target shared device sent by a user through a user terminal; the unlock request includes a first unlocking method for the target shared device and the user's user information; The target sharing device includes at least two different unlocking methods; the first unlocking method includes Bluetooth unlocking and / or near-field communication unlocking; the unlocking request is triggered by the user terminal when the user confirms that the second unlocking method of the target sharing device cannot be used to unlock it; the second unlocking method includes graphic code unlocking and device number unlocking; the unlocking request is sent by the user through the first unlocking method selection page of the target sharing device; the target sharing device unlocking method selection page is displayed by the user through the target sharing device on the client page of the sharing device. Based on the user information and the preset credit rating verification rules, determine whether the user's credit rating needs to be verified when the user uses the first unlocking method; If so, a credit rating verification request for the user is sent to the credit rating server. When the credit rating server confirms that the user's credit rating has been verified, unlock authentication information is generated and sent to the shared device to be unlocked through the user terminal. The unlock authentication information is used to control the unlocking of the target shared device.

Images