Unlocking method and device of shared equipment and computer readable storage medium

Abstract

The invention provides an unlocking method and device of shared equipment and a computer readable storage medium, and can be applied to the technical field of shared services. Based on the method, when a user wants to unlock and use a target shared device belonging to other different service platforms, the user does not need to specially install and open a client of a corresponding service platform, and can directly use a first client of an existing first service platform of a user terminal to obtain target identification information of the target shared device; and directly sending the target unlocking request about the target sharing equipment to the corresponding service platform through the first client according to the preset protocol rule under the condition of determining that the preset condition is met, so as to realize the unlocking of the target sharing equipment. Therefore, the user operation can be effectively simplified, and the user can efficiently and conveniently realize the unlocking operation on the shared equipment of other service platforms without replacing the client of the used service platform, so that the user can obtain better use experience.

Description

Technical Field

[0001] The present invention relates to the field of shared service technology, and in particular to a method, device and computer-readable storage medium for unlocking a shared device. Background Art

[0002] With the development and popularization of related technologies, more and more sharing service providers are involved in related business services such as shared bicycles. Usually, different sharing service providers will each deploy and maintain their own shared bicycles and release corresponding client apps for users to use.

[0003] Based on the existing method, users can only use the client app of a certain sharing service provider to unlock and use the shared bicycles provided by the sharing service provider, but cannot use the client app to unlock and use shared bicycles provided by other sharing service providers. If the user wants to use a shared bicycle provided by another sharing service provider, he must install and use the corresponding client app of the sharing provider in order to unlock and use the shared bicycle. When the above method is implemented, the user operation is cumbersome and complicated, which affects the user experience.

[0004] To address the above problems, no effective solution has been proposed yet. Summary of the invention

[0005] This specification provides a method, apparatus and computer-readable storage medium for unlocking a shared device, which can efficiently and conveniently realize the unlocking operation of shared devices on other service platforms, so that users can get a better user experience.

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

[0007] In response to the trigger instruction, using the first client to obtain target identification information of the target shared device;

[0008] When the target identification information indicates that the target sharing device does not belong to the first sharing device, using the first client to determine whether the target sharing device belongs to the second sharing device according to the target identification information;

[0009] When the target shared device belongs to the second shared device, when it is determined that the preset conditions are met, a target unlocking request about the target shared device is sent to the second service platform through the first client; wherein the target unlocking request carries at least the target identification information of the target shared device.

[0010] In one embodiment, in response to the trigger instruction, obtaining the target identification information of the target sharing device by using the first client includes:

[0011] In response to a trigger instruction for a device unlocking icon in the first client, a camera connected to the user terminal is called to capture a target image containing a target shared device; a target identification code and / or target identification characters arranged on the target shared device are identified from the target image by the first client as target identification information of the target shared device;

[0012] and / or,

[0013] In response to a trigger instruction for a device unlocking icon in the first client, a device description information input box is displayed to the target user; target description information about the target shared device input by the user is obtained through the device description information input box; the target shared device is determined based on the target description information; and target identification information of the target shared device is obtained.

[0014] In one embodiment, in response to the trigger instruction, obtaining the target identification information of the target sharing device by using the first client further includes:

[0015] Get the location information of the target user;

[0016] Using the first client to obtain identification information of a first shared device and / or identification information of a second shared device located in a vicinity of the target user according to the location information of the target user;

[0017] Displaying a first search result interface to a target user through a first client; wherein the first search result interface includes a device icon of the first shared device and / or a device icon of the second shared device;

[0018] The identification information of the shared device corresponding to the device icon selected by the target user in the first search result interface is determined as the target identification information of the target shared device.

[0019] In one embodiment, the first search result interface includes: a local map interface generated based on the location information of the target user and including at least the location of the target user.

[0020] In one embodiment, after obtaining, using the first client according to the location information of the target user, identification information of the first sharing device and / or identification information of the second sharing device located in the vicinity of the target user, the method further includes:

[0021] Displaying a second search result interface to the target user through the first client; wherein the second search result interface includes a device icon of the first shared device and other device display icons;

[0022] When it is detected that the target user triggers the display icon of other devices, the device icon of the second shared device is displayed in the second search result interface.

[0023] In one embodiment, the target description information of the target sharing device includes at least one of the following: a device number of the target sharing device, location information of the target sharing device, and environment information of the location of the target sharing device.

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

[0025] According to the preset protocol rules, it is determined whether the preset conditions are met; wherein the preset protocol rules include: an identification rule of the first shared device and an identification rule of the second shared device;

[0026] Correspondingly, using the first client to determine whether the target sharing device belongs to the second sharing device according to the target identification information includes:

[0027] Using the first client to detect whether the target identification information matches the identification rule of the second sharing device;

[0028] When it is determined that the target identification information matches the identification rule of the second sharing device, it is determined that the target sharing device belongs to the second sharing device.

[0029] In one embodiment, when the target shared device belongs to the second shared device, the method further includes:

[0030] Detect whether the user type of the target user is a joint user;

[0031] When it is determined that the user type of the target user is a joint user, it is determined that a preset condition is satisfied.

[0032] In one embodiment, when it is determined that the user type of the target user is a joint user, the method further includes:

[0033] Detecting whether the user terminal is deployed with a second client; wherein the second client is associated with a second shared device of a second service platform;

[0034] When it is determined that the user terminal is not deployed with the second client, it is determined that a preset condition is met.

[0035] In one embodiment, when it is determined that the user type of the target user is a non-federated user, the method further includes:

[0036] Detecting whether the user terminal is deployed with a second client; wherein the second client is associated with a second shared device of a second service platform;

[0037] When it is determined that the user terminal is not deployed with the second client, it is determined that a preset condition is met.

[0038] In one embodiment, when it is determined that the user type of the target user is a non-federated user, the method further includes:

[0039] Display a temporary authorization interface to the target user;

[0040] Obtain the target user's temporary authorization credentials through the temporary authorization interface;

[0041] When the temporary authorization credentials of the target user are verified, the target user is determined as a temporary joint user.

[0042] In one embodiment, the temporary authorization credentials of the target user include: at least one of an account identification of a first account of the target user based on a first client and a login credential of the first account, and / or, at least one of an account identification of a second account of the target user based on a second client and a login credential of the second account.

[0043] In one embodiment, when it is determined that the user type of the target user is a non-federated user, the method further includes:

[0044] Display the user application interface about the joint user to the target user.

[0045] In one embodiment, when it is determined that the user type of the target user is a joint user, the method further includes:

[0046] Using the first client, obtaining first preferential information based on the first client unlocking and using the target shared device, and second preferential information based on the second client unlocking and using the target shared device;

[0047] When the matching degree between the first preferential information and the target user is higher than the matching degree between the second preferential information and the target user, it is determined that the preset condition is met.

[0048] In one embodiment, when it is determined that the user type of the target user is a non-federated user, the method further includes:

[0049] Using the first client, obtaining first preferential information based on the first client unlocking and using the target shared device, and second preferential information based on the second client unlocking and using the target shared device;

[0050] When the matching degree between the first preferential information and the target user is higher than the matching degree between the second preferential information and the target user, it is determined that the preset condition is met.

[0051] In one embodiment, after using the first client to obtain first preferential information based on the first client unlocking and using the target shared device, and second preferential information based on the second client unlocking and using the target shared device, the method further includes:

[0052] Displaying an unlocking client selection interface to the target user through the first client; wherein the unlocking client selection interface at least includes a first selection icon representing unlocking based on the first client and a second selection icon representing unlocking based on the second client;

[0053] When it is detected that the target user triggers the first selection icon, it is determined that the preset condition is met.

[0054] In one embodiment, the unlocking client selection interface further includes first preferential information and second preferential information.

[0055] In one embodiment, when the user type of the target user is a non-joint user and meets a preset condition, the method further includes:

[0056] Display prompt information to the target user that settlement and payment must be made through an electronic account of a medium other than the first client.

[0057] In one embodiment, when the user type of the target user is a non-joint user, and the first preferential information and the second preferential information are different, the method further includes:

[0058] Prompt information about the difference in benefits between unlocking and using the target shared device through the first client and unlocking and using the target shared device through the second client is displayed to the target user.

[0059] In one embodiment, when it is determined that the user type of the target user is a joint user, the method further includes:

[0060] Using the first client to detect whether the electronic account used by the first client supports bill settlement of the second service platform;

[0061] When it is determined that the electronic account used by the first client supports bill settlement of the second service platform, it is determined that a preset condition is met.

[0062] In one embodiment, when it is determined that the user type of the target user is a joint user, the method further includes:

[0063] Predict the target user’s current operational tendency;

[0064] Detecting whether the current operation tendency of the target user matches the first client;

[0065] When it is determined that the current operation tendency of the target user matches the first client, it is determined that a preset condition is satisfied.

[0066] In one embodiment, when it is determined that the preset conditions are met, sending a target unlocking request for the target shared device to the second service platform includes:

[0067] When the user terminal is deployed with the second client, the first client is used to generate an unlocking interface for the target shared device; and the unlocking interface is displayed to the target user through the first client; wherein the unlocking interface at least includes an unlocking icon;

[0068] When it is detected that the target user triggers the unlock icon, a target unlock request is generated; and the target unlock request is sent to the second service platform through the first client.

[0069] In one embodiment, when it is determined that the preset condition is met, sending a target unlocking request for the target shared device to the second service platform further includes:

[0070] When the user terminal is not deployed with the second client, an unlocking interface for the target shared device is generated; and the unlocking interface is displayed to the target user through the first client; wherein the unlocking interface at least includes an unlocking icon;

[0071] When it is detected that the target user triggers the unlock icon, using the first client to generate an unlock credential based on the first client;

[0072] A target unlocking request carrying the unlocking credential is sent to the second service platform.

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

[0074] If it is determined that the preset condition is not met, detecting whether the user terminal is deployed with a second client;

[0075] When it is determined that the user terminal is deployed with the second client, the second client is awakened to generate and display an unlocking interface about the target shared device to the target user through the second client.

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

[0077] When it is determined that the user terminal is not deployed with the second client, searching and obtaining a download link of the second client; and displaying the download link of the second client to the target user through the first client;

[0078] or,

[0079] An account application interface for the joint account is displayed to the target user through the first client.

[0080] This manual also provides a method for using resources, including:

[0081] In response to the trigger instruction, the target identification information of the target resource is obtained by using the first client;

[0082] When the target identification information indicates that the target resource does not belong to the first resource, using the first client to determine whether the target resource belongs to the second resource according to the target identification information;

[0083] When the target resource belongs to the second resource, when it is determined that the preset condition is met, a target use request for the target resource is sent to the second service platform through the first client; wherein the target use request carries at least target identification information of the target resource.

[0084] This manual also provides a method for unlocking a shared device, including:

[0085] Receive a target unlocking request; wherein the target unlocking request is generated by the user terminal through the first client according to a preset protocol rule; the target unlocking request carries at least target identification information of the target shared device;

[0086] When it is determined that the preset conditions are met, the target unlocking request is responded to, the target shared device is determined, and the unlocking operation is performed on the target shared device.

[0087] This specification also provides a shared device unlocking device, which is applied to a user terminal, wherein the user terminal is at least deployed with a first client, and the first client is associated with a first shared device of a first service platform, and the device includes:

[0088] An acquisition module, used to respond to the trigger instruction and use the first client to acquire the target identification information of the target sharing device;

[0089] a judgment module, configured to judge whether the target sharing device belongs to the second sharing device by using the first client according to the target identification information when the target identification information indicates that the target sharing device does not belong to the first sharing device;

[0090] The sending module is used to send a target unlocking request about the target shared device to the second service platform through the first client when the target shared device belongs to the second shared device and when it is determined that the preset conditions are met; wherein the target unlocking request carries at least the target identification information of the target shared device.

[0091] The present specification also provides a computer-readable storage medium on which computer instructions are stored. When the instructions are executed by a processor, the relevant steps of the unlocking method of the shared device are implemented.

[0092] Based on the unlocking method, device and computer-readable storage medium for shared devices provided in this specification, when a user wants to unlock and use a target shared device belonging to other different service platforms, there is no need to specially install and open the corresponding client, and the target identification information of the target shared device can be directly obtained by using the first client of the first service platform currently available on the user terminal; and when the first client determines that the preset conditions are met, the target unlocking request for the target shared device is directly sent to the corresponding service platform through the first client. This can effectively simplify user operations, and users do not need to change the client of the service platform they are using to efficiently and conveniently realize the unlocking operation of shared devices on other service platforms, so that users can obtain a better user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0093] In order to more clearly illustrate the embodiments of this specification, the drawings required for use in the embodiments will be briefly introduced below. The drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0094] Figure 1 It is a flowchart of a method for unlocking a shared device provided by an embodiment of this specification;

[0095] Figure 2 It is a schematic diagram of an embodiment of an unlocking method for a shared device provided by an embodiment of this specification, in a scenario example;

[0096] Figure 3 It is a schematic diagram of an embodiment of an unlocking method for a shared device provided by an embodiment of this specification, in a scenario example;

[0097] Figure 4 It is a schematic diagram of an embodiment of an unlocking method for a shared device provided by an embodiment of this specification, in a scenario example;

[0098] Figure 5 It is a schematic diagram of an embodiment of an unlocking method for a shared device provided by an embodiment of this specification, in a scenario example;

[0099] Figure 6 It is a schematic diagram of an embodiment of an unlocking method for a shared device provided by an embodiment of this specification, in a scenario example;

[0100] Figure 7 It is a schematic diagram of an embodiment of an unlocking method for a shared device provided by an embodiment of this specification, in a scenario example;

[0101] Figure 8 It is a schematic diagram of an embodiment of an unlocking method for a shared device provided by an embodiment of this specification, in a scenario example;

[0102] Fig. 9 is a schematic diagram of the structure of an electronic device provided by an embodiment of this specification;

[0103] Fig.10 It is a schematic diagram of the structural composition of an unlocking device for a shared device provided by an embodiment of the present specification. DETAILED DESCRIPTION

[0104] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this specification.

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

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

[0107] See also Figure 1 As shown, the embodiment of this specification provides a method for unlocking a shared device. The method is specifically applied to a user terminal. The user terminal is at least deployed with a first client, and the first client is associated with a first shared device of a first service platform. When the method is specifically implemented, it may include the following contents:

[0108] S101: Responding to a trigger instruction, using a first client to obtain target identification information of a target sharing device;

[0109] S102: when the target identification information indicates that the target sharing device does not belong to the first sharing device, using the first client to determine whether the target sharing device belongs to the second sharing device according to the target identification information;

[0110] S103: When the target shared device belongs to the second shared device, upon determining that a preset condition is met, a target unlocking request regarding the target shared device is sent to the second service platform through the first client; wherein the target unlocking request carries at least target identification information of the target shared device.

[0111] The second shared device belongs to a second service platform, and the first service platform and the second service platform are different service platforms having a cooperative relationship.

[0112] The target shared device may be specifically understood as a shared device that the target user currently wants to unlock.

[0113] During specific implementation, the first client may be used to determine whether a preset condition is met according to a preset protocol rule.

[0114] Specifically, the target sharing device may include at least one of the following: shared bicycles, shared two-wheeled electric vehicles, shared cars, shared power supplies, etc. Of course, it should be noted that the target sharing devices listed above are only schematic illustrations. In specific implementation, according to specific application scenarios and processing requirements, the target sharing devices may also include other types of sharing devices. This specification does not limit this.

[0115] The above-mentioned first service platform can be specifically understood as a sharing service provider, for example, xx shared bicycles, etc.

[0116] Specifically, the first service platform deploys and maintains the first shared device; at the same time, the first service platform also releases online the first client associated with the first shared device.

[0117] The above-mentioned first client can be a client application installed and run on the user terminal, for example, xx shared bicycle app.

[0118] The user terminal may specifically include a front-end device applied to the target user side and capable of realizing functions such as data collection and data transmission. Specifically, the user terminal may be, for example, a desktop computer, a tablet computer, a laptop computer, a smart phone, a smart watch or other electronic device. The target user is the user who currently wants to unlock and use the target shared device.

[0119] The above-mentioned second service platform can be specifically understood as another sharing service provider that is different from the first service platform, for example, zz shared bicycles, etc.

[0120] Specifically, the second service platform deploys and maintains the second shared device; at the same time, the second service platform also releases online the second client associated with the second shared device.

[0121] The second service platform may also be a plurality of other sharing service providers that are different from the first service platform. For example, the second service platform may include: zz shared bicycles, tt shared power supplies, uu shared cars and other sharing service providers.

[0122] It should be noted that the first shared device and the second shared device may be the same type of shared devices, for example, the first shared device and the second shared device are both shared bicycles. The first shared device and the second shared device may also be different types of shared devices, for example, the first shared device is a shared bicycle, and the second shared device is a shared power source.

[0123] It should also be noted that the above-mentioned first service platform and the second service platform can specifically be service platforms with corresponding cooperative relationships. For example, in order to facilitate users to use the shared equipment of both parties, the above-mentioned first service platform and the second service platform have signed a corresponding cooperation agreement in advance. Based on the cooperation agreement, the first service platform and the second service platform launched a joint card business. After the user applies to open the joint card business, he is regarded as a joint user jointly recognized by the first service platform and the second service platform. At this time, the user can use the account registered on the first service platform or the second service platform to directly log in to the client of the other service platform and enjoy the shared services provided by other service platforms.

[0124] The above-mentioned preset protocol rules are a set of rules for realizing unlocking of shared devices of different service platforms, which are generated by the first service platform and the second service platform based on the corresponding cooperation treaty.

[0125] The preset protocol rules may specifically include: an identification rule for a first shared device based on a first service platform (or an identification rule for the first service platform), an identification rule for a second shared device based on a second service platform (or an identification rule for the second service platform), and a first interaction rule based on the first service platform and a second interaction rule based on the second service platform. Furthermore, the preset protocol rules may also include: a first encrypted transmission rule and a first unlocking process rule based on the first service platform, and a second encrypted transmission rule and a second unlocking process rule based on the second service platform.

[0126] Before specific implementation, the first client can obtain the above preset protocol rules through the first service platform and save the above preset protocol rules locally on the first client. During specific implementation, the first client can implement data processing on unlocking the second shared device based on the above preset protocol rules.

[0127] The target identification information may be specifically understood as identification information for indicating the target sharing device, such as the device number of the target sharing device, the device name of the target sharing device, or the identification code of the target sharing device, etc. The identification code may be a QR code, a bar code, or the like.

[0128] For specific implementation, see Figure 2 As shown, when the target user wants to unlock and use the target shared device, it is not necessary to distinguish whether the target shared device belongs to the first shared device or the second shared device, and the target identification information of the target shared device can be directly obtained using the first client deployed on the user terminal.

[0129] After acquiring the target identification information, the first client can detect, based on the target identification information, whether the target sharing device indicated by the target identification information belongs to the first sharing device.

[0130] Specifically, when the target identification information is an identification code, the first client can locate the platform coding area in the identification code according to the built-in identification rule based on the first service platform; then extract the coding information in the platform coding area and match it with the platform coding information of the first service platform in the identification rule. If the match succeeds, it can be determined that the target shared device belongs to the first shared device. On the contrary, if the match fails, it can be determined that the target shared device does not belong to the first shared device.

[0131] When the target identification information is a device name or a device number, the first client can generate a first identification information query request about the target identification information; wherein the first identification information query request carries at least the target identification information; and send the first identification information query to the server of the first service platform (which can be recorded as the first server).

[0132] The first server of the first service platform receives and responds to the first identification information query request, queries the device information database of the first service platform according to the target identification information, and when the target identification information is queried in the device information database, it can be determined that the target shared device belongs to the first shared device, and a positive query result that the target shared device belongs to the first shared device is fed back to the first client. On the contrary, when the target identification information is not queried in the device information database, it can be determined that the target shared device does not belong to the first shared device, and a negative query result that the target shared device does not belong to the first shared device is fed back to the first client.

[0133] When the target identification information indicates that the target shared device belongs to the first shared device, the first client can normally generate an unlocking interface based on the first client about the target shared device; and display the unlocking interface to the target user through the first client.

[0134] When it is determined through the unlocking interface that the target user instructs to unlock, the first client can generate a corresponding target unlocking request, and send the target unlocking request to the first service platform, so as to unlock the target shared device through the server of the first service platform; or, the first client directly generates an unlocking instruction for the target shared device according to the built-in code, and sends the unlocking instruction to the target shared device to unlock the target shared device.

[0135] When the target identification information indicates that the target sharing device does not belong to the first sharing device, the first client may further detect and determine whether the target sharing device belongs to the second sharing device.

[0136] Specifically, the first client determines whether the target shared device belongs to the second shared device by detecting whether the target identification information matches the identification rule of the second shared device based on the second service platform in the preset protocol rules; or, generates a second identification information query request about the target identification information according to the second interaction rule based on the second service platform in the preset protocol rules; and sends the second identification information query request to the second service platform, so that the server of the second service platform (which can be recorded as the second server) determines whether the target shared device belongs to the second shared device by querying the device information database of the second service platform.

[0137] When the target shared device belongs to the second shared device, it can be further determined whether the preset operating conditions are met according to the preset protocol rules; when it is determined that the preset conditions are met, a target unlocking request carrying at least the target identification information of the target shared device can be directly generated by the first client according to the second unlocking process based on the second service platform in the preset protocol rules; and the target unlocking request is sent to the second server of the second service platform through the first client to implement the unlocking operation on the target shared device.

[0138] When the target shared device does not belong to the first shared device or the second shared device, the first client terminal can also retrieve a preset reference identification information set based on the target identification information, and calculate the similarity between the target identification information and the reference identification information based on the structure, form, and sorting rules; select the reference identification information with the highest similarity as the target reference identification information; and determine the sharing service platform corresponding to the target reference identification information as the target sharing service platform to which the target shared device belongs.

[0139] The preset reference identification information set includes reference identification information of shared devices deployed by other sharing service platforms except the first service platform and the second service platform; each reference identification information corresponds to at least one sharing service platform. The above reference identification information can be obtained by the first service platform in advance by collecting and collating the introduction information, user guides, reference cases and other materials disclosed by various sharing service platforms.

[0140] After determining the target sharing service platform to which the target sharing device belongs, the first client may further search and determine a target client corresponding to the target sharing service platform, and detect whether the user terminal has the target client installed.

[0141] When it is determined that the user terminal has installed the target client, the first client may generate and display first prompt information indicating that the target shared device belongs to a target shared service platform and that the target client of the user terminal is required to be used to unlock the device.

[0142] When it is determined that the user terminal does not have the target client installed, the first client can search and obtain the download link of the target client; while generating and displaying the second prompt information that the target shared device belongs to the target sharing service platform and please download and install the target client to unlock it, the download link of the target client will also be displayed.

[0143] Based on the above embodiment, the target user does not need to open and use the second client, and can conveniently and efficiently unlock the first shared device and the second shared device using only the first client, thereby effectively simplifying user operations and improving user experience.

[0144] In some embodiments, the above-mentioned response trigger instruction, using the first client to obtain the target identification information of the target sharing device, may include the following contents when implemented:

[0145] In response to a trigger instruction for a device unlocking icon in the first client, a camera connected to the user terminal is called to capture a target image containing a target shared device; a target identification code and / or target identification characters arranged on the target shared device are identified from the target image by the first client as target identification information of the target shared device;

[0146] and / or,

[0147] In response to a trigger instruction for a device unlocking icon in the first client, a device description information input box is displayed to the target user; target description information about the target shared device input by the user is obtained through the device description information input box; the target shared device is determined based on the target description information; and target identification information of the target shared device is obtained.

[0148] The target identification code may be an identification code set on the target sharing device to indicate the target sharing device, such as a QR code, a barcode, etc. The target identification characters may be characters set on the target sharing device to indicate the target sharing device, such as a device number, a device name, etc. of the target sharing device.

[0149] The target description information may specifically be text information manually input by the user to describe the target sharing device, for example, the device number of the target sharing device corresponding to the target sharing device, the location information of the target sharing device, the environment information of the location of the target sharing device, etc. manually input by the user.

[0150] In specific implementation, the target user can click on the device unlocking icon in the first interface of the first client, for example, "Scan code to unlock", to initiate a trigger instruction. Accordingly, the first client can respond to the trigger instruction, call the camera of the user terminal, or the external camera connected to the user terminal to take a picture containing the target shared device as the target picture. Furthermore, the first client can call a preset image recognition model to identify and locate the local image area where the identification information is located in the target picture; then use the preset OCR recognition model to perform character recognition and extraction on the local image area to obtain the target identification information of the target shared device.

[0151] In specific implementation, the first client can also respond to the trigger instruction and automatically pop up a device description information input box; wherein, the input box can also display guidance information such as "Please describe the shared device you want to unlock". Based on the above guidance information, the target user can manually enter the device number of the target shared device seen in the input box as the target description information of the target shared device. Correspondingly, the first client can obtain the target description information through the above input box, and determine the target shared device described by the target user based on the target description information; and then automatically obtain the target identification information of the target shared device through query and other methods.

[0152] Based on the above embodiment, the first client may collect and process a target image including a target sharing device to automatically extract the target identification information of the target sharing device.

[0153] In some embodiments, the target description information of the target sharing device may specifically include at least one of the following: a device number of the target sharing device, location information of the target sharing device, environmental information of the location of the target sharing device, and the like.

[0154] During specific implementation, according to specific application scenarios and processing requirements, the user may also be supported to input other types of description information as the target description information.

[0155] In some embodiments, see Figure 3 As shown, the above-mentioned response trigger instruction uses the first client to obtain the target identification information of the target sharing device. When implemented specifically, it may also include the following contents:

[0156] S1: Obtain the location information of the target user;

[0157] S2: using the first client to obtain identification information of a first shared device and / or identification information of a second shared device located in a vicinity of the target user according to the location information of the target user;

[0158] S3: displaying a first search result interface to the target user through the first client; wherein the first search result interface includes a device icon of the first shared device and / or a device icon of the second shared device;

[0159] S4: Determine the identification information of the shared device corresponding to the device icon selected by the target user in the first search result interface as the target identification information of the target shared device.

[0160] Specifically, the location information of the target user may be obtained in response to a trigger instruction for a device search icon in the first client.

[0161] During specific implementation, firstly, the first client may obtain the location information of the target user through a positioning module (eg, GPS locator) built into the user terminal.

[0162] Next, the first client can generate a first search request for the first service platform according to the location information of the target user; wherein the first search request at least carries the location information of the target user. At the same time, the first client can also generate a second search request for the second service platform according to the preset protocol rules; wherein the second search request at least carries the location information of the target user. Then the first search request is sent to the first service platform, and the second search request is sent to the second service platform.

[0163] The first server of the first service platform can respond to the first search request, search and determine the first shared device currently located within the vicinity of the target user, as well as the identification information and location parameters of the first shared device based on the location information of the target user; and feed back the identification information and location parameters of the first shared device to the first client.

[0164] Similarly, the second server of the second service platform can respond to the second search request, search and determine the second shared device currently located in the vicinity of the target user, as well as the identification information and location parameters of the second shared device based on the location information of the target user; and feed back the identification information and location parameters of the second shared device to the first client.

[0165] The first client can first determine and obtain a local map of the vicinity of the target user based on the location information of the target user; then, based on the identification information and location parameters of the first shared device, set a device icon of the first shared device corresponding to the identification information of the first shared device at a corresponding position in the local map; at the same time, based on the identification information and location parameters of the second shared device, set a device icon of the second shared device corresponding to the identification information of the second shared device at a corresponding position in the local map; then use the above-mentioned local map to generate a corresponding first search result interface; and display the first search result interface to the target user.

[0166] For details, please refer to Figure 4 As shown, in the first search result interface of the first client, a local map of the target user's current location can be displayed to the target user, and the target user's current location can be marked in the map. Furthermore, in the above-mentioned first search result interface, not only the device icons of the first shared device belonging to the first service platform around the target user are displayed, but also the device icons of the second shared device belonging to the second service platform are displayed.

[0167] Specifically, in Figure 4 In the first search result interface shown, the circular icon is the device icon of the first shared device, and the triangular icon is the device icon of the second shared device.

[0168] In this way, the target user can relatively more freely choose to use the first shared device or the second shared device as the target shared device actually used for unlocking in the first search result interface displayed by the first client according to the specific situation and personal preference, so that the target user has more choices.

[0169] In specific implementation, the first client can receive and respond to the target user's selection operation on the first search result interface, determine the device icon selected by the target user as the device icon of the target shared device; and then obtain the identification information corresponding to the device icon as the target identification information of the target shared device.

[0170] Based on the above embodiment, the first client can be used to display a first search result interface that includes both the device icon of the first shared device and the device icon of the second shared device to the target user, so that the target user can directly select the first shared device or the second shared device as the target shared device to be unlocked in the first client, and then automatically obtain the target identification information of the target shared device through the first search result interface.

[0171] In some embodiments, the first search result interface may specifically include: a local map interface generated based on the location information of the target user and including at least the location of the target user.

[0172] In some embodiments, after the first client obtains the identification information of the first shared device and / or the identification information of the second shared device located in the vicinity of the target user according to the location information of the target user, the method may further include the following when implemented:

[0173] S1: Displaying a second search result interface to a target user through a first client; wherein the second search result interface includes a device icon of the first shared device and other device display icons;

[0174] S2: When it is detected that the target user triggers the display icon of other devices, the device icon of the second shared device is displayed in the second search result interface.

[0175] In order to avoid too many device icons in the search results and interfere with user selection, refer to Figure 5 As shown, the first client may display the second search result interface to the target user. The second search result interface displays only the device icon of the first shared device by default at the beginning.

[0176] When the target user wants to browse and view the second shared devices nearby at the same time, the trigger operation can be initiated by sliding the other device display icons in the second search result interface. At this time, the second search result interface can display the device icons of the second shared devices in the vicinity of the target user.

[0177] In addition, during specific implementation, after obtaining the identification information of the first shared device and the identification information of the second shared device located within the proximity of the target user, the method may also include the following contents during specific implementation: counting the number of device icons of the shared devices to be displayed based on the identification information of the first shared device and the identification information of the second shared device located within the proximity of the target user; detecting whether the number of device icons is greater than a preset number threshold; wherein the preset number threshold is determined based on the size of the second search result interface; when it is determined that the number of device icons is greater than the preset number threshold, the second search result interface initially displays only the device icon of the first shared device by default; when it is determined that the number of device icons is less than or equal to the preset number threshold, the second search result interface may initially display the device icon of the first shared device and the device icon of the second shared device at the same time.

[0178] Based on the above embodiment, the first client can more reasonably display the device icons of the shared devices in the vicinity of the target user through the second search result interface, so that the target user can obtain a relatively better user experience.

[0179] In some embodiments, the method may further include:

[0180] According to the preset protocol rules, it is determined whether the preset conditions are met; wherein the preset protocol rules include: an identification rule of the first shared device and an identification rule of the second shared device;

[0181] Accordingly, the above-mentioned use of the first client to determine whether the target sharing device belongs to the second sharing device according to the target identification information may include the following contents during specific implementation:

[0182] S1: using the first client to detect whether the target identification information matches the identification rule of the second sharing device;

[0183] S2: When it is determined that the target identification information matches the identification rule of the second sharing device, it is determined that the target sharing device belongs to the second sharing device.

[0184] In a specific implementation, the identification features of the target identification information can be extracted based on the target identification information; wherein the identification features of the target identification information include at least one of the following: the character length of the target identification information, the character type of the characters contained in the target identification information (for example, lowercase English characters, uppercase English characters, numeric characters, Chinese characters, etc.), the encoding structure of the target identification, the platform encoding area of ​​the target identification information, etc.; then the matching degree between the identification features of the target identification information and the identification rules of the second shared device is calculated, and it is detected whether the matching degree is greater than a preset matching degree threshold; when it is determined that it is greater than the preset matching degree threshold, it is determined that the target identification information matches the identification rules of the second shared device.

[0185] Based on the above embodiment, the first client can accurately determine whether the target sharing device belongs to the second sharing device according to the preset protocol rule.

[0186] In some embodiments, when the target shared device is a second shared device, the method may further include the following when implemented:

[0187] S1: Detect whether the user type of the target user is a joint user;

[0188] S2: When it is determined that the user type of the target user is a joint user, it is determined that a preset condition is satisfied.

[0189] The aforementioned joint user may specifically be a joint user jointly recognized by the first service platform and the second service platform based on a cooperation agreement, for example, a joint card user.

[0190] During specific implementation, the first client may be used to detect whether the user type of the target user is a joint user according to a preset protocol rule.

[0191] For the joint user, the first service platform allows the user to unlock and use the first shared device through the second client; at the same time, the second service platform allows the user to unlock and use the second shared device through the first client.

[0192] During specific implementation, the first client may detect whether the user type of the target user is a joint user by detecting the account tag of the account that the target user logs into on the first client according to preset protocol rules; or, it may detect whether the user type of the target user is a joint user by querying the first server of the first service platform according to preset protocol rules.

[0193] When it is determined that the user type of the target user is a joint user, it can be determined that the second service platform allows the target user to unlock and use the second shared device through the first client based on the cooperation agreement, and then it can be determined that the preset condition is met.

[0194] On the contrary, when it is determined that the user class of the target user is a non-joint user, it can be determined that the second service platform does not meet the preset condition.

[0195] In specific implementation, when it is determined that the preset conditions are met, the target user can directly unlock and use the target shared device through the first client.

[0196] On the contrary, if it is determined that the preset conditions are not met, the target user cannot directly unlock and use the target shared device through the first client. At this time, the first client can display prompt information about whether to apply for a joint user to the target user; after detecting that the target user initiates a confirmation operation in response to the prompt information, the first client automatically jumps to and displays the account application interface for the joint account, so that the target user can conveniently apply for a joint account.

[0197] Alternatively, the first client can also search whether the user terminal has the second client installed. When it is determined that the user terminal has the second client installed, the second client is started or woken up through the user terminal so that the target user does not need to perform manual operations. The interface displayed by the user terminal can automatically jump from the current first client interface to the second client interface, so that the target user can efficiently and conveniently unlock and use the target shared device through the second client.

[0198] Alternatively, when it is determined that the user terminal does not have the second client installed, the download link of the second client can be obtained, and then the download link can be displayed on the current interface, and the target user is prompted to download and install the second client through the download link, and then unlock and use the target shared device through the second client.

[0199] Based on the above embodiment, the first client can be used to detect whether the user type of the target user is a joint user, and determine whether the second service platform allows the target user to unlock and use the second common device through the first client, thereby accurately determining whether the preset conditions are met.

[0200] In some embodiments, when it is determined that the user type of the target user is a joint user, the method may further include the following when implemented:

[0201] S1: Detect whether the user terminal is deployed with a second client; wherein the second client is associated with a second shared device of a second service platform;

[0202] S2: When it is determined that the user terminal is not deployed with the second client, determine that a preset condition is met.

[0203] During specific implementation, it may be possible to detect whether the user terminal is deployed with the second client according to a preset protocol rule.

[0204] Based on the above embodiment, the first client can be used to intelligently and automatically determine whether the preset conditions are met by detecting whether the user terminal is deployed with the second client, thereby avoiding the target user wasting time downloading and installing the second client, thereby improving the unlocking efficiency of the target shared device.

[0205] In some embodiments, when it is determined that the user type of the target user is a non-joint user, the method may further include the following when implemented:

[0206] S1: Detect whether the user terminal is deployed with a second client; wherein the second client is associated with a second shared device of a second service platform;

[0207] S2: When it is determined that the user terminal is not deployed with the second client, determine that a preset condition is met.

[0208] Based on the above embodiment, for non-joint users, in some cases, the first client can also be used to automatically and intelligently determine whether the preset conditions are met by detecting whether the user terminal is deployed with the second client, thereby avoiding the target user wasting time downloading and installing the second client.

[0209] In some embodiments, when it is determined that the user type of the target user is a non-joint user, the method may further include the following when implemented:

[0210] S1: Display the temporary authorization interface to the target user;

[0211] S2: Obtain the temporary authorization credentials of the target user through the temporary authorization interface;

[0212] S3: When the temporary authorization credential of the target user is verified, the target user is determined as a temporary joint user.

[0213] In specific implementation, when it is determined that the user type of the target user is a non-joint user, the first client can also generate a temporary authorization interface for the second service platform according to the preset protocol rules; and display the temporary authorization interface to the target user. When the target user agrees to temporarily authorize the first client to interact with the second service platform on behalf of the second client to complete the unlocking process of the target shared device, the corresponding temporary authorization certificate can be provided.

[0214] Accordingly, the first client can receive the temporary authorization certificate provided by the target user through the temporary authorization interface; and verify the temporary authorization certificate (for example, authenticity verification); if the verification is confirmed to be passed, the target user can be determined as a temporary joint user, so that the target user temporarily obtains the identity of the joint user within a period of time (for example, within 1 hour). Furthermore, the first client can temporarily interact with the second service platform in place of the second client according to the preset protocol rules and in accordance with the processing method for the joint user, so as to complete the relevant data processing related to the unlocking of the second shared device.

[0215] Based on the above embodiment, for non-federated users, the target user can also obtain the identity of a temporary federated user through temporary authorization, and then based on the identity of the temporary federated user, the first client can be temporarily used instead of the second client to complete the corresponding interaction, thereby improving the interaction experience of the non-federated user.

[0216] In some embodiments, the temporary authorization credentials of the above-mentioned target user may specifically include: at least one of the account identification of the target user's first account based on the first client and the login credentials of the first account, and / or, at least one of the account identification of the target user's second account based on the second client and the login credentials of the second account.

[0217] In some embodiments, when it is determined that the user type of the target user is a non-joint user, the method may further include: displaying a user application interface for the joint user to the target user.

[0218] Accordingly, the first client can receive the target user's application information through the user application interface; and automatically complete the application of the joint user according to the application information, so that the target user can obtain a relatively permanent joint user identity.

[0219] Furthermore, the first client can permanently interact with the second service platform on behalf of the second client according to the preset protocol rules and in accordance with the processing method for the joint user to complete the relevant data processing related to the unlocking of the second shared device.

[0220] In some embodiments, when it is determined that the user type of the target user is a joint user, refer to Figure 6 As shown, when the method is implemented specifically, it may also include the following contents:

[0221] S1: using a first client to obtain first preferential information based on the first client unlocking and using a target shared device, and second preferential information based on the second client unlocking and using the target shared device;

[0222] S2: When the matching degree between the first preferential information and the target user is higher than the matching degree between the second preferential information and the target user, it is determined that the preset condition is met.

[0223] During specific implementation, the first client may be used to obtain, according to a preset protocol rule, first preferential information that can be enjoyed when the first client unlocks and uses the target shared device.

[0224] In specific implementation, the first client can determine the first preferential information that the target user can currently enjoy by unlocking and using the target shared device based on the first client according to the user ID of the target user through interaction with the first service platform. For example, the target user can currently receive and use the limited-time coupon launched for a limited time and enjoy a discount of 5 yuan by unlocking and using the target shared device through the first service platform.

[0225] At the same time, the first client can also determine the second preferential information that the target user can enjoy by unlocking and using the target shared device based on the second client according to the preset protocol rules and the user ID of the target user through interaction with the second service platform. For example, the target user can enjoy a 2 yuan discount by unlocking and using the target shared device based on the VIP identity of the second service platform.

[0226] Furthermore, the first client may calculate the matching degree between the first preferential information and the target user, and the matching degree between the second preferential information and the target user, respectively; and then determine which preferential treatment is most suitable for the target user by comparing the two matching degrees.

[0227] For example, when it is determined that the matching degree between the first preferential information and the target user is higher than or equal to the matching degree between the second preferential information and the target user, it can be determined that the target user currently obtains a higher discount by unlocking and using the target shared device through the first client than by unlocking and using the target shared device through the second client. At this time, it can be determined that the preset condition is met, and the unlocking operation of the target shared device can be completed through the first client.

[0228] When it is determined that the matching degree between the first preferential information and the target user is lower than the matching degree between the second preferential information and the target user, it can be determined that the current discount obtained by the target user through the first client to unlock and use the target shared device is lower than that obtained through the second client to unlock and use the target shared device. At this time, it can be determined that the preset condition is not met, and the user automatically jumps to complete the unlocking operation of the target shared device through the second client.

[0229] Based on the above embodiments, the preferential conditions of target users based on different service platforms can be fully considered to accurately determine whether the preset conditions are met.

[0230] In some embodiments, when it is determined that the user type of the target user is a non-joint user, the method may further include the following when implemented:

[0231] S1: using a first client to obtain first preferential information based on the first client unlocking and using a target shared device, and second preferential information based on the second client unlocking and using the target shared device;

[0232] S2: When the matching degree between the first preferential information and the target user is higher than the matching degree between the second preferential information and the target user, it is determined that the preset condition is met.

[0233] Based on the above embodiment, in some cases (for example, the target user temporarily authorizes and applies for a temporary joint user), the first client can also treat the joint user as it does, taking into full consideration the preferential conditions of the target user based on different service platforms, and accurately determining whether the preset conditions are met.

[0234] In some embodiments, after obtaining, using the first client according to a preset protocol rule, first preferential information based on the first client unlocking and using the target shared device, and second preferential information based on the second client unlocking and using the target shared device, the method may further include the following when implemented:

[0235] S1: displaying an unlocking client selection interface to a target user through a first client; wherein the unlocking client selection interface at least includes a first selection icon representing unlocking based on the first client and a second selection icon representing unlocking based on the second client;

[0236] S2: When it is detected that the target user triggers the first selection icon, it is determined that a preset condition is met.

[0237] On the contrary, when it is detected that the target user triggers the second selection icon, it can be determined that the preset condition is not satisfied.

[0238] The target user may be a joint user or a non-joint user in some cases.

[0239] Based on the above embodiment, the target user can freely choose which client to use to unlock the target shared device according to specific circumstances and processing requirements in the interface of the first client.

[0240] In some embodiments, the unlocking client selection interface further includes first preferential information and second preferential information.

[0241] Based on the above embodiment, by using the first client to display the first preferential information and the second preferential information in the unlocking client selection interface for reference by the target user, the target user can be helped to make a better decision and choice.

[0242] In some embodiments, when it is determined that the user type of the target user is a joint user, the method may further include the following when implemented:

[0243] S1: Using the first client to detect whether the electronic account used by the first client supports bill settlement of the second service platform according to a preset protocol rule;

[0244] S2: When it is determined that the electronic account used by the first client supports bill settlement of the second service platform, it is determined that a preset condition is met.

[0245] Specifically, the electronic account bound to the first client by the target user supports the bill settlement of the first service platform, but may not support the bill settlement of the second service platform. In this case, even if the target unlocking request can be sent to the second service platform through the first client, it is still necessary to jump to the second client and use the electronic account bound to the second client to connect to the second service platform to complete the bill settlement.

[0246] Based on the above embodiment, by further detecting whether the electronic account used by the first client supports the bill settlement of the second service platform, only when it is determined that the electronic account used by the first client supports the bill settlement of the second service platform, it is determined that the preset conditions are met, and the first client is used to complete the unlocking operation of the target shared device; when it is determined that the electronic account used by the first client does not support the bill settlement of the second service platform, it is determined that the preset conditions are not met, and the second client is jumped and used to complete the unlocking operation of the target shared device, thereby effectively simplifying user operations.

[0247] In some embodiments, when the user type of the target user is a non-joint user, and the first preferential information and the second preferential information are different, the method may further include the following contents when implemented:

[0248] Prompt information about the difference in benefits between unlocking and using the target shared device through the first client and unlocking and using the target shared device through the second client is displayed to the target user.

[0249] Based on the above embodiment, when the target user is a non-joint user, the first client can also prompt the target user in a timely manner when the preferential conditions of different service platforms are different, so as to help the target user make better decisions.

[0250] In some embodiments, when the user type of the target user is a non-joint user and meets the preset conditions, the method may further include the following contents when implemented:

[0251] Display prompt information to the target user that settlement and payment must be made through an electronic account of a medium other than the first client.

[0252] When the target user is a non-joint user, in some cases, the target user may not be able to directly use the electronic account of the first client to complete the settlement payment for unlocking and using the target shared device.

[0253] At this time, the first client can actively display to the target user a prompt message that the settlement and payment must be made through an electronic account of another medium other than the first client. Furthermore, the prompt message can also include a settlement and payment trigger link based on an electronic account of another medium.

[0254] In this way, the target user can directly select an electronic account of a medium that meets his or her requirements in the prompt information and trigger the corresponding settlement payment trigger link; then the first client can respond to the above trigger operation and automatically complete the relevant settlement payment through the electronic account of the above selected medium. This can simplify the operation of non-joint users and further improve the interactive experience of non-joint users.

[0255] In some embodiments, when it is determined that the user type of the target user is a joint user, refer to Figure 7 As shown, when the method is implemented specifically, it may also include:

[0256] S1: predict the current operation tendency of the target user;

[0257] S2: Detect whether the current operation tendency of the target user matches the first client;

[0258] S3: When it is determined that the current operation tendency of the target user matches the first client, it is determined that a preset condition is satisfied.

[0259] In specific implementation, the target user's historical operation records can be queried and statistics can be obtained on the frequency of the target user using the first client in the current time period (for example, the last week) and the frequency of using the second client; based on the frequency of using the first client and the frequency of using the second client, the target user's current operation tendency can be predicted.

[0260] Specifically, if the frequency of using the first client is greater than or equal to the frequency of using the second client, it can be predicted that the current operation tendency of the target user is to use the first client, and then it can be determined that the current operation tendency of the target user matches the first client, and it is determined that the preset condition is met. On the contrary, if the frequency of using the first client is less than the frequency of using the second client, it can be predicted that the current operation tendency of the target user is to use the second client, and then it can be determined that the current operation tendency of the target user does not match the first client, and it is determined that the preset condition is not met.

[0261] During specific implementation, the first client may also detect whether there is a client icon of the first client and a client icon of the second client in the shortcut page of the user terminal of the target user; wherein the shortcut page of the user terminal is used to store program icons of applications frequently used by the user; when it is detected that there is a client icon of the first client in the shortcut page of the user terminal of the target user, and / or that there is no client icon of the second client in the shortcut page, it can be determined that the preset conditions are met.

[0262] During specific implementation, the first client may also query and determine, based on the target user's historical operation records, whether the sharing service client last used by the target user within a specified time period (for example, 5 hours from now) is the second client; when it is determined that the sharing service client last used by the target user is not the second client, it may be determined that the preset conditions are met.

[0263] During specific implementation, the first client may also collect current target feature data; wherein the current target feature data includes at least one of the following: the target user's current location information, the program identifier of the application that the target user has most recently used on the user terminal, the current time information, the current environmental information, the current activity information of the first service platform, the current activity information of the second service platform, etc.; and then use the preset client prediction model to process the current target feature data, predict the target user's operation behavior, and obtain the corresponding prediction result; based on the preset result, determine the target user's current operation tendency.

[0264] Among them, the above-mentioned preset client prediction model can be specifically understood as a neural network model that is pre-trained using the historical operation records and historical target feature data of the target user, and can predict the client that the target user wants to operate based on the input target feature data.

[0265] Specifically, according to the prediction result, when it is determined that the target user's current operation tendency is that the client used for the operation is the first client, it can be determined that the preset condition is met. Conversely, according to the prediction result, when it is determined that the target user's current operation tendency is that the client used for the operation is the second client, it can be determined that the preset condition is not met.

[0266] Based on the above embodiments, the first client can be used to accurately predict the current operation tendency of the target user, and then it can be more intelligently and accurately determined whether the preset conditions are met according to the current operation tendency of the target user.

[0267] In some embodiments, see Figure 8 As shown, when it is determined that the preset conditions are met, a target unlocking request for the target shared device is sent to the second service platform. When implemented specifically, the following contents may be included:

[0268] S1: When the user terminal is deployed with the second client, the first client is used to generate an unlocking interface for the target shared device; and the unlocking interface is displayed to the target user through the first client; wherein the unlocking interface at least includes an unlocking icon;

[0269] S2: When it is detected that the target user triggers the unlocking icon, a target unlocking request is generated; and the target unlocking request is sent to the second service platform through the first client.

[0270] In specific implementation, the first client can obtain the preset code segment of the second client through the preset interface according to the preset protocol rules; and generate the unlocking interface of the target shared device according to the preset code segment and the target identification information. Correspondingly, when it is detected that the target user triggers the unlocking icon, a target unlocking request can be generated according to the preset code segment.

[0271] Specifically, the preset code may be a code file produced by the second service platform according to the corresponding cooperation agreement and built into the second client for the first client to call, so as to generate a code segment based on the unlocking interface of the second client in the first client.

[0272] In a specific implementation, first, the first client can determine a corresponding preset interface according to a preset protocol rule; and then obtain a corresponding preset code segment from a second client deployed on a user terminal through the preset interface.

[0273] Furthermore, the first client can determine the identity certificate corresponding to the first service platform according to the preset protocol rules, and then carry the identity certificate to apply to the second client through the preset interface to obtain the corresponding preset code segment. The second client will verify the validity of the identity certificate according to the preset protocol rules, and if the verification is successful, the first client can normally obtain the preset code segment.

[0274] Next, the first client can generate an unlocking interface for the target shared device based on the second client according to the preset code segment and the target identification information; and display the unlocking interface to the target user through the first client. The unlocking interface at least includes an unlocking icon. In addition, the bottom layer of the unlocking interface also includes a designated transmission interface pointing to the second service platform that is the same as that of the second client. Moreover, the unlocking interface can also be the same as the unlocking interface generated by the second client itself.

[0275] Then, when it is detected that the target user triggers the unlock icon on the unlock interface, a target unlock request can be generated according to the preset code segment, and the target unlock request can be directly sent to the second service platform through the designated transmission interface.

[0276] Since the second service platform receives the target unlocking request through the designated transmission interface, it can determine that the target unlocking request is authentic and trustworthy, and can directly respond to the target unlocking request and generate a corresponding unlocking instruction based on the target identification information; and encrypt the unlocking instruction according to the preset encryption rules to obtain the corresponding encrypted unlocking instruction; and then send the encrypted unlocking instruction to the target shared device based on the target identification information.

[0277] After receiving the encrypted unlocking instruction, the target shared device can perform decryption processing according to the preset encryption rules to obtain the unlocking instruction; verify the unlocking instruction, and respond to the unlocking instruction and automatically perform the unlocking operation if the verification passes.

[0278] Based on the above embodiment, the first client may be used to generate and display an unlocking interface based on the second client, so as to efficiently and conveniently complete the unlocking operation on the target shared device.

[0279] In some embodiments, when it is determined that the preset conditions are met, a target unlocking request for the target shared device is sent to the second service platform. When implemented specifically, the following contents may also be included:

[0280] S1: when the user terminal is not deployed with the second client, generating an unlocking interface for the target shared device according to the relevant code segment and target identification information of the first client; and displaying the unlocking interface to the target user through the first client; wherein the unlocking interface at least includes an unlocking icon;

[0281] S2: when it is detected that the target user triggers the unlocking icon, using the first client to generate an unlocking credential based on the first client according to a preset protocol rule;

[0282] S3: Sending a target unlocking request carrying the unlocking credential to the second service platform.

[0283] In a specific implementation, the first client may also generate an unlocking interface based on the first client according to the relevant code segment and target identification information of the first client, so that the target user can trigger the unlocking icon through the unlocking interface.

[0284] When the target user triggers the unlocking icon through the above unlocking interface, the identity certificate of the first service platform can be used to generate an unlocking credential based on the first client according to the preset protocol rules; and the target unlocking request carrying the unlocking credential is sent to the second service platform.

[0285] After receiving the target unlocking request, the second service platform can first detect whether the unlocking credential is valid according to the preset protocol rules; if the unlocking credential is determined to be valid, the target unlocking request can be judged to be authentic and credible; and then the target unlocking request can be responded to normally to complete the unlocking operation of the target shared device.

[0286] Based on the above embodiment, the first client may be used to generate and display an unlocking interface based on the first client, so as to efficiently and conveniently complete the unlocking operation on the target shared device.

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

[0288] S1: If it is determined that the preset condition is not met, detecting whether the user terminal is deployed with a second client;

[0289] S2: When it is determined that the user terminal is deployed with the second client, the second client is awakened to generate and display an unlocking interface for the target shared device to the target user through the second client.

[0290] During specific implementation, the first client may wake up the second client according to a preset protocol rule.

[0291] Based on the above embodiment, when the preset conditions are not met, the first client can be used to wake up the second client according to the preset protocol rules to jump and complete the unlocking operation of the target shared device through the relevant interface of the second client.

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

[0293] When it is determined that the user terminal is not deployed with the second client, searching and obtaining a download link of the second client; and displaying the download link of the second client to the target user through the first client;

[0294] or,

[0295] An account application interface for the joint account is displayed to the target user through the first client.

[0296] Based on the above embodiment, when it is determined that the preset condition is not met, the first client can also be used to help the target user complete the unlocking operation of the target shared device through the second client in a corresponding manner.

[0297] In some embodiments, after sending the target unlocking request for the target shared device to the second service platform, the method may further include the following when implemented:

[0298] S1: receiving the unlocking instruction fed back by the second service platform;

[0299] S2: According to the preset protocol rules, the unlocking instruction is used to establish a communication link with the target shared device to perform an unlocking operation on the target shared device.

[0300] Based on the above embodiment, the first client can replace the second client to establish a communication link with the target shared device according to a preset protocol rule, and complete the unlocking operation of the target shared device through the communication link.

[0301] In some embodiments, after the unlocking operation is completed, the communication link between the first client and the target sharing device can be maintained. During the process of the target user using the target sharing device, the target sharing device can regularly collect relevant parameter information, such as the location information of the target sharing device, the usage time of the target sharing device, the speed of the target sharing device, etc., and send the above parameter information to the first client through the above communication link.

[0302] Correspondingly, the first client can generate a usage interface of the target shared device in real time or periodically based on the parameter information; and display and update the relevant parameter information on the usage interface, so that the target user can timely and conveniently understand the specific situation during the use of the target shared device through the first client, so that the target user can obtain a better user experience.

[0303] In addition, the target user can also adjust the relevant parameter information on the above usage interface according to the specific situation and actual needs. The first client will provide the adjusted parameter information to the target sharing device through the communication link, so that the target sharing device can timely meet the needs of the target user and adjust the operation based on the adjusted parameter information, thereby further improving the user experience.

[0304] As can be seen from the above, based on the unlocking method of the shared device provided in the embodiment of this specification, when the user wants to unlock and use the target shared device belonging to other different service platforms, there is no need to specially install and open the corresponding client, and the first client of the first service platform currently available on the user terminal can be directly used to obtain the target identification information of the target shared device; and the first client is used according to the preset protocol rules, and when it is determined that the preset conditions are met, the target unlocking request about the target shared device is directly sent to the corresponding service platform through the first client. This can effectively simplify the user operation, and the user does not need to change the client of the service platform used, and can efficiently and conveniently realize the unlocking operation of the shared device of other service platforms, so that the user can get a better user experience.

[0305] This specification also provides a method for unlocking a shared device, wherein the method can be specifically applied to a server of a second service platform (or a second server). When the method is specifically implemented, it can include the following contents:

[0306] S1: receiving a target unlocking request; wherein the target unlocking request is generated by a user terminal through a first client according to a preset protocol rule; the target unlocking request carries at least target identification information of a target shared device;

[0307] S2: When it is determined that the preset conditions are met, respond to the target unlocking request, determine the target shared device, and perform an unlocking operation on the target shared device.

[0308] In specific implementation, when it is determined that the preset conditions are met, the second server can generate a corresponding unlocking instruction according to the preset protocol rules, and send the unlocking instruction directly to the target shared device to complete the unlocking operation. Alternatively, the second server can also send the generated unlocking instruction to the first client, and then the first client uses the unlocking instruction to interact with the target shared device to complete the unlocking operation.

[0309] Based on the above embodiment, the server of the second service platform can accurately respond to the unlocking request initiated by the user through the client of other service platforms according to the preset protocol rules, helping the user to complete the unlocking operation efficiently and conveniently, effectively simplifying the user operation and improving the user's interactive experience.

[0310] This specification also provides a method for using resources. The method is specifically applied to a user terminal. The user terminal is at least deployed with a first client, and the first client is associated with a first resource of a first service platform. When the method is specifically implemented, it may include the following contents:

[0311] S1: Responding to a trigger instruction, using a first client to obtain target identification information of a target resource;

[0312] S2: when the target identification information indicates that the target resource does not belong to the first resource, using the first client to determine whether the target resource belongs to the second resource according to the target identification information;

[0313] S3: When the target resource belongs to the second resource, and when it is determined that the preset conditions are met, a target use request for the target resource is sent to the second service platform through the first client; wherein the target use request carries at least target identification information of the target resource.

[0314] The second service platform is specifically responsible for delivering and maintaining the second resource and providing the associated second client. The first service platform is specifically responsible for delivering and maintaining the first resource and providing the associated first client.

[0315] The target resource may be a shared resource, such as a shared battery, a shared bicycle, a shared car, etc. Of course, according to the specific application scenario, the target resource may also be other types of resources, such as a server resource that allows users to apply for scheduling; another example, a book resource that allows users to apply for borrowing; another example, an office resource that allows users to apply for borrowing, etc. The specific type and content of the target resource are not limited in this specification.

[0316] Based on the above embodiments, user operations can be effectively simplified. Users do not need to change the client of the service platform they use, and can efficiently and conveniently apply for and use resources of other service platforms, so that users can obtain a better user experience.

[0317] This specification embodiment provides an electronic device, referring to Fig. 9 The server includes a network communication port 901, a processor 902 and a memory 903, and the above structures are connected through internal cables so that each structure can perform specific data interaction.

[0318] The network communication port 901 can be used to obtain a trigger instruction.

[0319] The processor 902 can be specifically used to respond to a trigger instruction and use the first client to obtain the target identification information of the target shared device; when the target identification information indicates that the target shared device does not belong to the first shared device, use the first client to determine whether the target shared device belongs to the second shared device based on the target identification information; when the target shared device belongs to the second shared device, when it is determined that the preset conditions are met, send a target unlocking request for the target shared device to the second service platform through the first client; wherein, the target unlocking request carries at least the target identification information of the target shared device.

[0320] The memory 903 may be specifically used to store corresponding instruction programs, target identification information, preset protocol rules and other related data.

[0321] Based on the above method, the relevant structural performance of the server can be effectively utilized, the data processing speed of the electronic device can be improved, and the relevant data processing of unlocking the shared device can be efficiently realized.

[0322] In this embodiment, the network communication port 901 can be a virtual port that is bound to different communication protocols so that different data can be sent or received. For example, the network communication port can be a port responsible for web data communication, a port responsible for FTP data communication, or a port responsible for email data communication. In addition, the network communication port can also be a physical communication interface or communication chip. For example, it can be a wireless mobile network communication chip, such as GSM, CDMA, etc.; it can also be a Wifi chip; it can also be a Bluetooth chip.

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

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

[0325] The embodiment of the present specification also provides a computer-readable storage medium based on the unlocking method of the above-mentioned shared device, and the computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed, the following steps are implemented: responding to a trigger instruction, using a first client to obtain target identification information of a target shared device; when the target identification information indicates that the target shared device does not belong to the first shared device, using the first client to determine whether the target shared device belongs to a second shared device based on the target identification information; when the target shared device belongs to the second shared device, when it is determined that a preset condition is met, sending a target unlocking request for the target shared device to the second service platform through the first client; wherein, the target unlocking request carries at least the target identification information of the target shared device.

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

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

[0328] The embodiments of the present specification also provide a computer program product, which at least includes a computer program, and when the computer program is executed by a processor, it implements the following method steps: responding to a trigger instruction, using a first client to obtain target identification information of a target shared device; when the target identification information indicates that the target shared device does not belong to the first shared device, using the first client to determine whether the target shared device belongs to a second shared device based on the target identification information; when the target shared device belongs to the second shared device, when it is determined that a preset condition is met, sending a target unlocking request for the target shared device to the second service platform through the first client; wherein the target unlocking request carries at least the target identification information of the target shared device.

[0329] See also Fig.10 As shown, the embodiment of this specification also provides an unlocking device for a shared device, a user terminal, the user terminal is at least deployed with a first client, the first client is associated with a first shared device of a first service platform, and the device may specifically include the following structural modules:

[0330] The acquisition module 1001 may be specifically used to respond to the trigger instruction and use the first client to acquire the target identification information of the target sharing device;

[0331] The judgment module 1002 may be specifically used to judge whether the target sharing device belongs to the second sharing device using the first client according to the target identification information when the target identification information indicates that the target sharing device does not belong to the first sharing device;

[0332] The sending module 1003 can be specifically used to send a target unlocking request about the target shared device to the second service platform through the first client when the target shared device belongs to the second shared device and the preset conditions are determined to be met; wherein the target unlocking request carries at least the target identification information of the target shared device.

[0333] In some embodiments, when the above-mentioned acquisition module 1001 is implemented, it can respond to the trigger instruction in the following manner and use the first client to obtain the target identification information of the target shared device: in response to the trigger instruction for the device unlocking icon in the first client, call the camera connected to the user terminal to capture the target picture containing the target shared device; use the first client to identify the target identification code and / or target identification character arranged on the target shared device from the target picture as the target identification information of the target shared device; and / or, in response to the trigger instruction for the device unlocking icon in the first client, display the device description information input box to the target user; obtain the target description information about the target shared device input by the user through the device description information input box; determine the target shared device based on the target description information; and obtain the target identification information of the target shared device.

[0334] In some embodiments, when the above-mentioned acquisition module 1001 is implemented, it can also respond to the trigger instruction in the following manner and use the first client to obtain the target identification information of the target shared device: obtain the location information of the target user; use the first client to obtain the identification information of the first shared device and / or the identification information of the second shared device located in the vicinity of the target user based on the location information of the target user; display the first search result interface to the target user through the first client; wherein the first search result interface includes the device icon of the first shared device and / or the device icon of the second shared device; and determine the identification information of the shared device corresponding to the device icon selected by the target user in the first search result interface as the target identification information of the target shared device.

[0335] In some embodiments, the first search result interface may specifically include: a local map interface generated based on the location information of the target user and including at least the location of the target user.

[0336] In some embodiments, after using the first client to obtain the identification information of the first shared device and / or the identification information of the second shared device located in the vicinity of the target user based on the location information of the target user, the device, when implemented specifically, can also be used to: display a second search result interface to the target user through the first client; wherein the second search result interface includes a device icon for the first shared device and other device display icons; and when it is detected that the target user triggers other device display icons, the device icon for the second shared device is displayed in the second search result interface.

[0337] In some embodiments, the target description information of the target sharing device may specifically include at least one of the following: a device number of the target sharing device, location information of the target sharing device, environmental information of the location of the target sharing device, and the like.

[0338] In some embodiments, when the device is specifically implemented, it can determine whether the preset conditions are met according to the preset protocol rules; wherein the preset protocol rules can specifically include: the identification rule of the first shared device and the identification rule of the second shared device;

[0339] Correspondingly, when the above-mentioned judgment module 1002 is implemented, the first client can be used to judge whether the target shared device belongs to the second shared device according to the target identification information in the following manner: use the first client to detect whether the target identification information matches the identification rule of the second shared device; when it is determined that the target identification information matches the identification rule of the second shared device, it is determined that the target shared device belongs to the second shared device.

[0340] In some embodiments, when the target shared device belongs to the second shared device, the apparatus can also be used, when implemented, to: use the first client to detect whether the user type of the target user is a joint user according to preset protocol rules; and when it is determined that the user type of the target user is a joint user, determine whether the preset conditions are met.

[0341] In some embodiments, when it is determined that the user type of the target user is a joint user, the device can also be used when it is implemented to: detect whether the user terminal is deployed with a second client according to preset protocol rules; wherein the second client is associated with a second shared device of the second service platform; and when it is determined that the user terminal is not deployed with the second client, determine whether the preset conditions are met.

[0342] In some embodiments, when it is determined that the user type of the target user is a non-joint user, the device, when implemented specifically, can also be used to: detect whether the user terminal is deployed with a second client; wherein the second client is associated with a second shared device of a second service platform; and when it is determined that the user terminal is not deployed with the second client, determine whether a preset condition is met.

[0343] In some embodiments, when it is determined that the user type of the target user is a non-joint user, the device, when implemented, can also be used to: display a temporary authorization interface to the target user; obtain the temporary authorization credentials of the target user through the temporary authorization interface; and when the temporary authorization credentials of the target user are verified, determine the target user as a temporary joint user.

[0344] In some embodiments, the temporary authorization credentials of the target user may specifically include: at least one of an account identification of the target user's first account based on the first client and the login credentials of the first account, and / or, at least one of an account identification of the target user's second account based on the second client and the login credentials of the second account.

[0345] In some embodiments, when it is determined that the user type of the target user is a non-joint user, the device may be further configured to: display a user application interface for the joint user to the target user.

[0346] In some embodiments, when it is determined that the user type of the target user is a joint user, the device can also be used, when implemented, to: use a first client to obtain first preferential information based on the first client unlocking and using the target shared device, and second preferential information based on the second client unlocking and using the target shared device; when the match between the first preferential information and the target user is higher than the match between the second preferential information and the target user, it is determined that the preset condition is met.

[0347] In some embodiments, when it is determined that the user type of the target user is a non-joint user, the device, when implemented specifically, can also be used to: use a first client to obtain first preferential information based on the first client unlocking and using the target shared device, and second preferential information based on the second client unlocking and using the target shared device; when the match degree between the first preferential information and the target user is higher than the match degree between the second preferential information and the target user, it is determined that the preset condition is met.

[0348] In some embodiments, after using the first client to obtain the first preferential information based on the first client unlocking and using the target shared device, and the second preferential information based on the second client unlocking and using the target shared device, when the device is specifically implemented, it can also be used to: display the unlocking client selection interface to the target user through the first client; wherein the unlocking client selection interface at least includes a first selection icon representing unlocking based on the first client and a second selection icon representing unlocking based on the second client; when it is detected that the target user triggers the first selection icon, it is determined that the preset condition is met. wherein, the target user can specifically be a joint user, and in some cases, can also be a non-joint user.

[0349] In some embodiments, the unlocking client selection interface may further include first preferential information and second preferential information.

[0350] In some embodiments, when the user type of the target user is a non-joint user and meets the preset conditions, the device can also be used to: display prompt information to the target user that settlement and payment must be made through an electronic account of other media other than the first client.

[0351] In some embodiments, when the user type of the target user is a non-joint user and the first preferential information and the second preferential information are different, the device, when implemented, can also be used to: display to the target user prompt information about the difference in preferential treatment between unlocking and using the target shared device through the first client and unlocking and using the target shared device through the second client.

[0352] In some embodiments, when it is determined that the user type of the target user is a joint user, the device can also be used when it is implemented: using the first client to detect whether the electronic account used by the first client supports bill settlement of the second service platform; when it is determined that the electronic account used by the first client supports bill settlement of the second service platform, it is determined that the preset conditions are met.

[0353] In some embodiments, when it is determined that the user type of the target user is a joint user, the device, when implemented, can also be used to: predict the current operation tendency of the target user; detect whether the current operation tendency of the target user matches the first client; and when it is determined that the current operation tendency of the target user matches the first client, determine that a preset condition is met.

[0354] In some embodiments, when the above-mentioned sending module 1003 is implemented, it can send a target unlocking request regarding the target shared device to the second service platform in the following manner when it is determined that the preset conditions are met: when the user terminal is deployed with a second client, use the first client to generate an unlocking interface for the target shared device; and display the unlocking interface to the target user through the first client; wherein the unlocking interface at least includes an unlocking icon; when it is detected that the target user triggers the unlocking icon, a target unlocking request is generated; and the target unlocking request is sent to the second service platform through the first client.

[0355] In some embodiments, when the above-mentioned sending module 1003 is implemented, it can also send a target unlocking request regarding the target shared device to the second service platform in the following manner when it is determined that the preset conditions are met: when the user terminal is not deployed with the second client, generate an unlocking interface for the target shared device; and display the unlocking interface to the target user through the first client; wherein the unlocking interface at least includes an unlocking icon; when it is detected that the target user triggers the unlocking icon, generate an unlocking credential based on the first client using the first client; and send a target unlocking request carrying the unlocking credential to the second service platform.

[0356] In some embodiments, when the device is implemented, it can also be used to: detect whether the user terminal is deployed with a second client when it is determined that a preset condition is not met; and wake up the second client when it is determined that the user terminal is deployed with a second client, so as to generate and display an unlocking interface about the target shared device to the target user through the second client.

[0357] In some embodiments, when the device is implemented, it can also be used to: search for and obtain a download link of the second client when it is determined that the user terminal is not deployed with the second client; and display the download link of the second client to the target user through the first client; or, display an account application interface for a joint account to the target user through the first client.

[0358] In some embodiments, after sending a target unlocking request regarding a target shared device to a second service platform, the device, when implemented, can also be used to: receive an unlocking instruction fed back by the second service platform; and establish a communication link with the target shared device using the unlocking instruction according to preset protocol rules to perform an unlocking operation on the target shared device.

[0359] This specification also provides another unlocking device for a shared device, which may specifically include the following structure:

[0360] The receiving module may be specifically used to receive a target unlocking request; wherein the target unlocking request is generated by the user terminal through the first client according to a preset protocol rule; the target unlocking request at least carries the target identification information of the target shared device;

[0361] The unlocking module may be specifically configured to respond to a target unlocking request and determine a target shared device when it is determined that a preset condition is met; and to perform an unlocking operation on the target shared device.

[0362] This specification also provides a resource use device, which may specifically include the following structure:

[0363] The acquisition module may be specifically used to respond to the trigger instruction and obtain the target identification information of the target resource by using the first client;

[0364] The judgment module may be specifically used to judge whether the target resource belongs to the second resource using the first client according to the target identification information when the target identification information indicates that the target resource does not belong to the first resource;

[0365] The sending module can be specifically used to send a target use request about the target resource to the second service platform through the first client when the target resource belongs to the second resource and it is determined that the preset conditions are met; wherein the target use request carries at least the target identification information of the target resource.

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

[0367] It can be seen from the above that the unlocking device for a shared device provided in the embodiments of this specification can effectively simplify user operations. Users do not need to change the client of the service platform they are using, and can efficiently and conveniently unlock shared devices on other service platforms, allowing users to obtain a better user experience.

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

[0369] Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code, the controller can be made to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

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

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

[0372] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. This specification can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.

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

Claims

1. A method for unlocking a shared device, characterized in that: include: In response to the trigger instruction, using the first client to obtain target identification information of the target shared device; When the target identification information indicates that the target sharing device does not belong to the first sharing device, using the first client to determine whether the target sharing device belongs to the second sharing device according to the target identification information; When the target shared device belongs to the second shared device, when it is determined that the preset conditions are met, a target unlocking request about the target shared device is sent to the second service platform through the first client; wherein the target unlocking request carries at least the target identification information of the target shared device.

2. The method according to claim 1, characterized in that In response to the trigger instruction, using the first client to obtain the target identification information of the target sharing device includes: In response to a trigger instruction for a device unlocking icon in the first client, a camera connected to the user terminal is called to capture a target image containing a target shared device; a target identification code and / or target identification characters arranged on the target shared device are identified from the target image by the first client as target identification information of the target shared device; and / or, In response to a trigger instruction for a device unlocking icon in the first client, a device description information input box is displayed to the target user; target description information about the target shared device input by the user is obtained through the device description information input box; the target shared device is determined based on the target description information; and target identification information of the target shared device is obtained.

3. The method according to claim 1, characterized in that In response to the trigger instruction, using the first client to obtain the target identification information of the target sharing device, further comprising: Get the location information of the target user; Using the first client to obtain identification information of a first shared device and / or identification information of a second shared device located in a vicinity of the target user according to the location information of the target user; Displaying a first search result interface to a target user through a first client; wherein the first search result interface includes a device icon of the first shared device and / or a device icon of the second shared device; The identification information of the shared device corresponding to the device icon selected by the target user in the first search result interface is determined as the target identification information of the target shared device.

4. The method according to claim 3, characterized in that The first search result interface includes: a local map interface generated based on the location information of the target user and including at least the location of the target user.

5. The method according to claim 3, characterized in that: After acquiring identification information of a first sharing device and / or identification information of a second sharing device located in a vicinity of the target user according to the location information of the target user by using the first client, the method further includes: Displaying a second search result interface to the target user through the first client; wherein the second search result interface includes a device icon of the first shared device and other device display icons; When it is detected that the target user triggers the display icon of other devices, the device icon of the second shared device is displayed in the second search result interface.

6. The method according to claim 2, characterized in that The target description information of the target sharing device includes at least one of the following: a device number of the target sharing device, location information of the target sharing device, and environment information of the location of the target sharing device.

7. The method according to claim 1, characterized in that The method further comprises: According to the preset protocol rules, it is determined whether the preset conditions are met; wherein the preset protocol rules include: an identification rule of the first shared device and an identification rule of the second shared device; Correspondingly, using the first client to determine whether the target sharing device belongs to the second sharing device according to the target identification information includes: Using the first client to detect whether the target identification information matches the identification rule of the second sharing device; When it is determined that the target identification information matches the identification rule of the second sharing device, it is determined that the target sharing device belongs to the second sharing device.

8. The method according to claim 1, characterized in that: When the target shared device is a second shared device, the method further includes: Detect whether the user type of the target user is a joint user; When it is determined that the user type of the target user is a joint user, it is determined that a preset condition is satisfied.

9. The method according to claim 8, characterized in that When it is determined that the user type of the target user is a joint user, the method further includes: Detecting whether the user terminal is deployed with a second client; wherein the second client is associated with a second shared device of a second service platform; When it is determined that the user terminal is not deployed with the second client, it is determined that a preset condition is met.

10. The method according to claim 8, characterized in that In the case where it is determined that the user type of the target user is a non-federated user, the method further includes: Detecting whether the user terminal is deployed with a second client; wherein the second client is associated with a second shared device of a second service platform; When it is determined that the user terminal is not deployed with the second client, it is determined that a preset condition is met.

11. The method according to claim 8, characterized in that In the case where it is determined that the user type of the target user is a non-federated user, the method further includes: Display a temporary authorization interface to the target user; Obtain the target user's temporary authorization credentials through the temporary authorization interface; When the temporary authorization credentials of the target user are verified, the target user is determined as a temporary joint user.

12. The method according to claim 11, characterized in that The temporary authorization credentials of the target user include: at least one of an account identification of a first account of the target user based on the first client and a login credential of the first account, and / or at least one of an account identification of a second account of the target user based on the second client and a login credential of the second account.

13. The method according to claim 9, characterized in that In the case where it is determined that the user type of the target user is a non-federated user, the method further includes: Display the user application interface about the joint user to the target user.

14. The method according to claim 9, characterized in that When it is determined that the user type of the target user is a joint user, the method further includes: Using the first client, obtaining first preferential information based on the first client unlocking and using the target shared device, and second preferential information based on the second client unlocking and using the target shared device; When the matching degree between the first preferential information and the target user is higher than the matching degree between the second preferential information and the target user, it is determined that the preset condition is met.

15. The method according to claim 9, characterized in that In the case where it is determined that the user type of the target user is a non-federated user, the method further includes: Using the first client, obtaining first preferential information based on the first client unlocking and using the target shared device, and second preferential information based on the second client unlocking and using the target shared device; When the matching degree between the first preferential information and the target user is higher than the matching degree between the second preferential information and the target user, it is determined that the preset condition is met.

16. The method according to claim 14 or 15, characterized in that After using the first client to obtain first preferential information based on the first client unlocking and using the target shared device, and second preferential information based on the second client unlocking and using the target shared device, the method further includes: Displaying an unlocking client selection interface to the target user through the first client; wherein the unlocking client selection interface at least includes a first selection icon representing unlocking based on the first client and a second selection icon representing unlocking based on the second client; When it is detected that the target user triggers the first selection icon, it is determined that the preset condition is met.

17. The method according to claim 16, characterized in that The unlocking client selection interface also includes first preferential information and second preferential information.

18. The method according to claim 1, characterized in that When the user type of the target user is a non-joint user and meets a preset condition, the method further includes: Display prompt information to the target user that settlement and payment must be made through an electronic account of a medium other than the first client.

19. The method according to claim 1, characterized in that When the user type of the target user is a non-joint user, and the first preferential information and the second preferential information are different, the method further includes: Prompt information about the difference in benefits between unlocking and using the target shared device through the first client and unlocking and using the target shared device through the second client is displayed to the target user.

20. The method according to claim 9, characterized in that When it is determined that the user type of the target user is a joint user, the method further includes: Using the first client to detect whether the electronic account used by the first client supports bill settlement of the second service platform; When it is determined that the electronic account used by the first client supports bill settlement of the second service platform, it is determined that a preset condition is met.

21. The method according to claim 9, characterized in that When it is determined that the user type of the target user is a joint user, the method further includes: Predict the target user’s current operational tendency; Detecting whether the current operation tendency of the target user matches the first client; When it is determined that the current operation tendency of the target user matches the first client, it is determined that a preset condition is satisfied.

22. The method according to claim 1, characterized in that When it is determined that the preset conditions are met, a target unlocking request for the target shared device is sent to the second service platform, including: When the user terminal is deployed with the second client, the first client is used to generate an unlocking interface for the target shared device; and the unlocking interface is displayed to the target user through the first client; wherein the unlocking interface at least includes an unlocking icon; When it is detected that the target user triggers the unlock icon, a target unlock request is generated; and the target unlock request is sent to the second service platform through the first client.

23. The method according to claim 1, characterized in that When it is determined that the preset conditions are met, sending a target unlocking request for the target shared device to the second service platform also includes: When the user terminal is not deployed with the second client, an unlocking interface for the target shared device is generated; and the unlocking interface is displayed to the target user through the first client; wherein the unlocking interface at least includes an unlocking icon; When it is detected that the target user triggers the unlock icon, using the first client to generate an unlock credential based on the first client; A target unlocking request carrying the unlocking credential is sent to the second service platform.

24. The method according to claim 1, characterized in that The method further comprises: If it is determined that the preset condition is not met, detecting whether the user terminal is deployed with a second client; When it is determined that the user terminal is deployed with the second client, the second client is awakened to generate and display an unlocking interface about the target shared device to the target user through the second client.

25. The method according to claim 24, characterized in that The method further comprises: When it is determined that the user terminal is not deployed with the second client, searching and obtaining a download link of the second client; and displaying the download link of the second client to the target user through the first client; or, An account application interface for the joint account is displayed to the target user through the first client.

26. A method for unlocking a shared device, characterized in that: include: Receive a target unlocking request; wherein the target unlocking request is generated by the user terminal through the first client according to a preset protocol rule; the target unlocking request carries at least target identification information of the target shared device; When it is determined that the preset conditions are met, the target unlocking request is responded to, the target shared device is determined, and the unlocking operation is performed on the target shared device.

27. An unlocking device for a shared device, characterized in that: Applied to a user terminal, the user terminal is deployed with at least a first client, the first client is associated with a first shared device of a first service platform, and the apparatus includes: An acquisition module, used to respond to the trigger instruction and use the first client to acquire the target identification information of the target sharing device; a judgment module, configured to judge whether the target sharing device belongs to the second sharing device by using the first client according to the target identification information when the target identification information indicates that the target sharing device does not belong to the first sharing device; The sending module is used to send a target unlocking request about the target shared device to the second service platform through the first client when the target shared device belongs to the second shared device and when it is determined that the preset conditions are met; wherein the target unlocking request carries at least the target identification information of the target shared device.

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

Images