CN113011943A

CN113011943A - Interaction method, interaction system, storage medium and electronic device

Info

Publication number: CN113011943A
Application number: CN202110265762.4A
Authority: CN
Inventors: 熊伟
Original assignee: Beijing Qisheng Technology Co Ltd
Current assignee: Beijing Qisheng Technology Co Ltd
Priority date: 2021-03-11
Filing date: 2021-03-11
Publication date: 2021-06-22

Abstract

The embodiment of the invention discloses an interaction method, an interaction system, a storage medium and electronic equipment. The terminal of the embodiment of the invention determines the main account identification corresponding to the sharing device according to the sharing device identification after acquiring the target account identification and the sharing device identification of the sharing device, then renders and displays the account binding control when the target account identification is matched with the main account identification, receives the input account identification, and further determines the account binding request and sends the account binding request to the server by the target account identification, the sharing device identification and the input account identification when the account binding control is triggered. After receiving the account binding request, the server extracts the target account identifier, the sharing device identifier and the input account identifier, and binds the input account identifier and the sharing device according to the target account identifier and the sharing device identifier. The embodiment of the invention can improve the utilization rate of the shared equipment rented for a long time in an idle time by adding the account identifier bound with the shared equipment.

Description

Interaction method, interaction system, storage medium and electronic device

Technical Field

The invention relates to the technical field of computers, in particular to an interaction method, an interaction system, a storage medium and electronic equipment.

Background

With the continuous development of internet technology and computer technology, online leasing platforms are developed rapidly. Taking the shared bicycle rental platform as an example, the user can rent the shared bicycle through the shared bicycle rental platform. For some users who use shared bicycles more frequently, the shared bicycle rental platform can also provide the service of renting the shared bicycles for a long time for the users. However, how to improve the utilization rate of the shared bicycle rented for a long time in idle time becomes a problem to be solved gradually.

Disclosure of Invention

In view of this, embodiments of the present invention provide an interaction method, an interaction system, a storage medium, and an electronic device, which are used to improve the utilization rate of a shared device rented for a long time in an idle period.

According to a first aspect of the embodiments of the present invention, an interaction method is provided, which is applicable to a terminal, and the method includes:

acquiring a target account identifier and a sharing device identifier, wherein the sharing device identifier is the identifier of a target sharing device;

determining a primary account identifier corresponding to the target sharing device according to the sharing device identifier;

in response to the target account identification matching the primary account identification, rendering and displaying an account binding control;

receiving an input first account identification;

in response to the account binding control being triggered, determining an account binding request according to the target account identifier, the shared device identifier, and the first account identifier;

and sending the account binding request to a server to bind the first account identifier with the target sharing device.

According to a second aspect of the embodiments of the present invention, there is provided an interaction method, adapted to a server, the method including:

in response to receiving an account binding request, extracting a first account identifier, a target account identifier and a shared device identifier in the account binding request, wherein the shared device identifier is an identifier of a target shared device;

and binding the first account identifier with the target sharing device according to the target account identifier and the sharing device identifier.

According to a third aspect of the embodiments of the present invention, there is provided an interactive apparatus, adapted to a terminal, the apparatus including:

a first identifier obtaining unit, configured to obtain a target account identifier and a shared device identifier, where the shared device identifier is an identifier of a target shared device;

a primary account determining unit, configured to determine, according to the sharing device identifier, a primary account identifier corresponding to the target sharing device;

the control display unit is used for rendering and displaying the account binding control in response to the matching of the target account identification and the main account identification;

the first identification receiving unit is used for receiving an input first account identification;

a binding request determining unit, configured to determine, in response to the account binding control being triggered, an account binding request according to the target account identifier, the shared device identifier, and the first account identifier;

a binding request sending unit, configured to send the account binding request to a server, so as to bind the first account identifier with the target sharing device.

According to a fourth aspect of the embodiments of the present invention, there is provided an interaction apparatus, adapted to a server, the apparatus including:

the device comprises a first identification extracting unit, a second identification extracting unit and a sharing device identification extracting unit, wherein the first identification extracting unit is used for responding to the received account binding request and extracting a first account identification, a target account identification and a sharing device identification in the account binding request, and the sharing device identification is the identification of a target sharing device;

and the account binding unit is used for binding the first account identifier and the target sharing device according to the target account identifier and the sharing device identifier.

According to a fifth aspect of embodiments of the present invention, there is provided an interactive system, the system comprising:

the terminal is used for acquiring a target account identifier and a sharing device identifier, determining a main account identifier corresponding to the target sharing device according to the sharing device identifier, rendering and displaying an account binding control in response to the target account identifier being matched with the main account identifier, receiving an input first account identifier, determining an account binding request according to the target account identifier, the sharing device identifier and the first account identifier in response to the account binding control being triggered, and sending the account binding request to a server to bind the first account identifier with the target sharing device, wherein the sharing device identifier is an identifier of the target sharing device;

the server is used for responding to the received account binding request, extracting a first account identifier, a target account identifier and a sharing device identifier in the account binding request, and binding the first account identifier and the target sharing device according to the target account identifier and the sharing device identifier.

According to a sixth aspect of embodiments of the present invention, there is provided a computer readable storage medium having stored thereon computer program instructions, wherein the computer program instructions, when executed by a processor, implement the method according to the first or second aspect.

According to a seventh aspect of embodiments of the present invention, there is provided an electronic device comprising a memory and a processor, wherein the memory is configured to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method according to the first or second aspect.

According to an eighth aspect of embodiments of the present invention, there is provided a computer program product comprising computer programs/instructions, wherein the computer programs/instructions are executed by a processor to implement the method according to the first aspect.

The terminal of the embodiment of the invention determines the main account identification corresponding to the sharing device according to the sharing device identification after acquiring the target account identification and the sharing device identification of the sharing device, then renders and displays the account binding control when the target account identification is matched with the main account identification, receives the input account identification, and further determines the account binding request and sends the account binding request to the server by the target account identification, the sharing device identification and the input account identification when the account binding control is triggered. After receiving the account binding request, the server extracts the target account identifier, the sharing device identifier and the input account identifier, and binds the input account identifier and the sharing device according to the target account identifier and the sharing device identifier. The embodiment of the invention can improve the utilization rate of the shared equipment rented for a long time in an idle time by adding the account identifier bound with the shared equipment.

Drawings

The above and other objects, features and advantages of the present invention will become more apparent from the following description of the embodiments of the present invention with reference to the accompanying drawings, in which:

FIG. 1 is a schematic diagram of a hardware system architecture of an embodiment of the present invention;

FIG. 2 is a flow chart of an interaction method of an embodiment of the invention;

FIG. 3 is a schematic view of an interface according to an embodiment of the present invention;

FIG. 4 is a schematic view of another interface according to an embodiment of the present invention;

fig. 5 is a flowchart of the interaction method of the first embodiment of the present invention at the terminal side;

FIG. 6 is a flow chart of the interaction method of the first embodiment of the present invention on the server side;

FIG. 7 is a flow chart of an interaction method of the second embodiment of the present invention;

FIG. 8 is a schematic view of another interface according to an embodiment of the present invention;

FIG. 9 is a schematic view of another interface according to an embodiment of the present invention;

fig. 10 is a flowchart of an interaction method of the second embodiment of the present invention at a terminal side;

FIG. 11 is a flow chart of the interaction method of the second embodiment of the present invention on the server side;

FIG. 12 is a schematic diagram of an interactive system of a third embodiment of the present invention;

fig. 13 is a schematic view of an electronic apparatus according to a fourth embodiment of the present invention.

Detailed Description

The present invention will be described below based on examples, but the present invention is not limited to only these examples. In the following detailed description of the present invention, certain specific details are set forth. It will be apparent to one skilled in the art that the present invention may be practiced without these specific details. Well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present invention.

Further, those of ordinary skill in the art will appreciate that the drawings provided herein are for illustrative purposes and are not necessarily drawn to scale.

Unless the context clearly requires otherwise, throughout the description, the words "comprise", "comprising", and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is, what is meant is "including, but not limited to".

In the description of the present invention, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In addition, in the description of the present invention, "a plurality" means two or more unless otherwise specified.

In the embodiment of the present invention, the sharing device is taken as a sharing bicycle for example, but it is easily understood by those skilled in the art that the method of the embodiment of the present invention is also applicable when the sharing device is other devices, such as a sharing charger and an electric vehicle.

The shared bicycle leasing platform is an on-line leasing platform for providing bicycle sharing service for users in public service areas such as campuses, subway stations, bus stations, residential areas and the like. The user can rent the shared bicycle on the shared bicycle leasing platform to facilitate traveling. For some users who use shared bicycles more frequently, the shared bicycle rental platform can also provide the service of renting the shared bicycles for a long time for the users. However, the usage of the shared bicycle rented for a long time by the users is also limited, so how to improve the utilization rate of the shared bicycle rented for a long time in an idle period (that is, a period of time when the user rents the shared bicycle for a long time does not use the shared bicycle) becomes a problem to be solved gradually.

FIG. 1 is a diagram of a hardware system architecture of an embodiment of the present invention. The hardware system architecture shown in fig. 1 may include at least one first terminal 11, at least one sharing device 12, at least one server 13, and at least one second terminal 14, and fig. 1 illustrates one first terminal 11, one sharing device 12, one server 13, and one second terminal 14 as an example. The first terminal 11 is a terminal that logs in a primary account bound to the sharing device 12, and the first terminal 11, the sharing device 12, the server 13, and the second terminal 14 may establish a communication connection through a network.

The user leasing the shared device 12 for a long term can cause the first terminal 11 to send an unlocking request for the shared device 12 to the server 13 by the way that the first terminal 11 scans the two-dimensional code set on the shared device 12, or the like. The server 13 may send an unlocking instruction to the shared device 12 after receiving an unlocking request for the shared device 12, so that the user holding the first terminal 11 may unlock and use the shared device 12. The user holding the first terminal 11 can add the second terminal 14 as the secondary account of the shared device 12, so that the user holding the second terminal 14 can use the shared device 12 in the idle period of the shared device 12, thereby achieving the purpose of increasing the usage rate of the shared device 12 in the idle period. Similarly, when the second terminal 14 is a terminal that logs in a secondary account bound to the shared device 12, the user may also unlock and use the shared device 12 by scanning a two-dimensional code set on the shared device 12 by the second terminal 14, or the like.

In the embodiment of the present invention, the first terminal 11 may obtain the account identifier of the current login account (i.e., the target account identifier) and the sharing device identifier of the sharing device 12 (i.e., the target sharing device), and determines the primary account identifier corresponding to the sharing device 12 according to the sharing device identifier of the sharing device 12, if the account identifier of the currently logged-in account matches with the primary account identifier corresponding to the sharing device 12, the first terminal 12 may render and display an account binding control on the interface, and receives the account identification of the second terminal 14 (i.e., the first account identification) entered via the account binding control, further determining an account binding request according to the account identifier of the currently logged-in account, the sharing device identifier of the sharing device 12 and the input account identifier, thereby sending an account binding request to the server to bind the input account identification with the shared device 12.

After receiving the account binding request sent by the first terminal 11, the server may extract the account identifier, the target account identifier, and the shared device identifier of the second terminal 14 in the account binding request, and bind the account identifier of the second terminal 14 as the secondary account identifier with the shared device 12 according to the first account identifier and the shared device identifier.

Optionally, after the account identifier of the second terminal 14 is bound with the shared device 12, the embodiment of the present invention may also release the binding between the secondary account identifier and the shared device 12 in an interactive manner. The first terminal 11 or the second terminal 14 may obtain the account identifier (i.e., the second account identifier) of the second terminal 14, and determine the account unbinding request according to the account identifier (i.e., the target account identifier) of the first terminal 11 and the account identifier of the second terminal 14, or the sharing device identifier of the sharing device 12 and the account identifier of the second terminal 14, so as to send the account unbinding request to the server 13.

After receiving the account unbinding request sent by the first terminal 11 or the second terminal 14, the server 13 extracts the account identifier of the first terminal 11 and the account identifier of the second terminal 14, or the shared device identifier of the shared device 12 and the account identifier of the second terminal 14 in the account unbinding request, and unbound the account identifier of the second terminal 14 and the shared device 12 according to the account identifier of the first terminal 11 or the shared device identifier of the shared device 12.

The following describes in detail embodiments of the present invention by way of method examples. Fig. 2 is a flow chart of an interaction method of an embodiment of the present invention. As shown in fig. 2, the method of the present embodiment includes the following steps:

step S201, a target account identifier and a shared device identifier are obtained.

After the user registers and logs in the account through the terminal, the user can log in the shared bicycle leasing platform through the terminal and can lease the shared bicycle on the shared bicycle leasing platform for a long time. The binding duration may be set according to the actual requirement of the user, for example, one week, one month, and the like. The terminal can determine that the current login account is the main account of the target sharing equipment bound with the account from the time when the user successfully applies for renting the sharing bicycle for a long time to the binding time, and store the sharing equipment identification of the target sharing equipment in the local; similarly, the server may also obtain, through the shared bicycle rental platform, the account identifier of the current login account of the terminal and the shared device identifier of the bound target shared device, and store the account identifier of the current login account of the terminal as the main account identifier of the bound target shared device. It is easily understood that in the present embodiment, any account id may be bound to multiple sharing devices, but each sharing device corresponds to only one primary account id.

In this step, after the user logs in the shared bicycle platform through the terminal, the terminal may acquire the account identifier of the current login account as the target account identifier, and locally acquire the shared device identifier of the target shared device bound to the target account identifier, or receive the shared device identifier input by the user. The target account Identifier may be a user ID (Identity Document) set by a user or automatically generated by the platform, such as a mobile phone number, a mailbox number, an Identity card number, a UUID (universal Unique Identifier) of the user, and the like.

Step S202, determining a primary account identifier corresponding to the target sharing device according to the sharing device identifier.

In order to reduce the possibility that the target sharing device is added with the secondary account under the condition that the primary account user does not know, the use of the target sharing device by the primary account user is negatively affected and the benefit of the primary account user is damaged, in this embodiment, only the primary account of the target sharing device may add at least one account identifier as the secondary account of the target sharing device.

Optionally, for any terminal, if the user logs in any account including the current login account on the terminal, the terminal may store data generated by the account locally. Therefore, when the user logs in the account again through the terminal, the terminal can directly obtain the primary account identifier corresponding to the target sharing device from the local according to the sharing device identifier.

Optionally, for any terminal, if the user has not logged in the current login account on the terminal, the terminal may send the sharing device identifier of the target sharing device to the server, and receive the primary account identifier sent by the server.

And step S203, in response to the matching of the target account identification and the main account identification, rendering and displaying the account binding control.

If the target account identifier is matched with the primary account identifier, indicating that the target account is the primary account of the target sharing device, the terminal may render and display the account binding control in the interface. In order to facilitate the user to log in, the user can log in the same account through a plurality of account identifications, for example, the user can log in the same account through a mobile phone number and a mailbox number, and the terminal local area and the database can store the corresponding relation between the account identifications and the account. Therefore, even though the account identifier of the current login account of the user may be different from the primary account identifier corresponding to the target sharing device, as long as the account identifier of the current login account and the primary account identifier corresponding to the target sharing device correspond to the same account, the target account identifier and the primary account identifier may be considered to be matched.

Optionally, in step S201, the terminal may present a first page, so that the user may input the sharing device identifier of the target sharing device at a first position of the first page. In the step, after the target account identifier is determined to be the main account identifier bound with the target sharing device, the terminal renders and displays the account binding control in the first page. Wherein, the first page may be an account binding page.

FIG. 3 is a schematic diagram of an interface according to an embodiment of the invention. As shown in fig. 3, page P1 is an account binding page. As shown on the left side of fig. 3, the user may enter or select the sharing device identification of the target sharing device through the sharing device identification input control 31 (i.e., the first position of the account binding page) within page P1. When the user does not enter the correctly formatted shared device identification, the terminal may not render the account binding control 32 in page P1, and in some alternative implementations, the account binding control 32 may be displayed in a non-clickable state. As shown in the right side of fig. 3, after the user inputs the sharing device identifier with the correct format, that is, the sharing device identifier of the sharing bicycle B1, the terminal may determine the primary account identifier corresponding to the sharing bicycle B1 according to the sharing device identifier of the sharing bicycle B1, and render and display the account binding control 32 when the primary account identifier corresponding to the sharing bicycle B1 matches the target account identifier, and in some optional implementations, the account binding control 32 may be displayed in a clickable state.

Optionally, in step S201, the terminal may present a second page, so that the user may input the sharing device identifier of the target sharing device at the first position of the second page. In this step, after determining that the target account identifier is the primary account identifier bound to the target sharing device, the terminal may jump to a third page, and render and display the account binding control in the third page. The second page may be a shared device identifier input page, and the third page may be an account binding page.

FIG. 4 is another interface schematic of an embodiment of the invention. As shown in FIG. 4, page P2 is the shared device identification input page and page P3 is the account binding page. As shown on the left side of fig. 4, the user may enter or select the sharing device identification of the target sharing device through the sharing device identification input control 41 (i.e., the first position of the sharing device identification input page) within page P2. When the user enters the correctly formatted shared device identifier, i.e., shared device identifier of shared bicycle B1, or alternatively, when the user clicks the "next" control 42 after entering the shared device identifier of shared bicycle B1, as shown on the right side of fig. 4, the interface may jump to the account binding page, i.e., page P3, and render and display the account binding control in page P3.

For convenience of explanation, the first page, the second page and the third page are used in this embodiment for description, but it is easy to understand that the account binding control of this embodiment may be displayed in any page, and this embodiment is not limited to rendering and showing the account binding control in the above manner.

Step S204, receiving the input first account identification.

In this step, the terminal may receive an account identifier input by the user, and use the account identifier input by the user as the first account identifier, where the first account identifier input by the user may be used as a secondary account identifier to be bound with the target sharing device. Similar to the target account ID, the first account ID may also be a user ID set by the user or automatically generated by the platform, such as a mobile phone number, a mailbox number, an identification number, a UUID, and the like of the user.

Alternatively, the user may enter the account identification at a second location on the first page or at a second location on a third page. The page shown in fig. 3 and the page shown in fig. 4 are still used as examples for explanation. As shown in fig. 3, the user may enter the first account identification in the correct format via account identification input control 33 of page P1 (i.e., the second position of the first page); similarly, the user may enter the first account identification in the correct format via account identification input control 44 of page P3 (i.e., the second position of the third page).

It is easy to understand that step S203 and step S204 may be executed simultaneously or sequentially, and this embodiment is not limited.

Step S205, in response to the account binding control being triggered, determining an account binding request according to the target account identifier, the shared device identifier and the first account identifier.

After the user inputs the first account identifier, the account binding control can be triggered by single click, multiple clicks, long press and the like. After the account binding control is triggered, the terminal may determine the account binding request according to the account identifier of the current login user, the sharing device identifier of the target sharing device, and the first account identifier input by the user.

Step S206, sending an account binding request to the server.

After determining the account binding request, the terminal may send an account binding request to the server, so as to bind the first account identifier as a secondary account identifier of the target sharing device with the target sharing device.

Step S207, in response to receiving the account binding request, extracting the first account identifier, the target account identifier, and the shared device identifier in the account binding request.

After receiving the account binding request sent by the terminal, the server may extract the first account identifier, the target account identifier, and the shared device identifier in the account binding request.

And step S208, binding the first account identifier and the target sharing device according to the first account identifier and the sharing device identifier.

In this step, the server may also determine the primary account identifier corresponding to the target sharing device according to the sharing device identifier of the target sharing device, so as to reduce the possibility that the terminal side erroneously determines the account identifier of the current login account as the primary account identifier of the target sharing device, thereby improving the accuracy of the account binding process.

When the target account identifier matches with the primary account identifier of the target sharing device, the server may obtain the account permission of the target account according to the target account identifier, and obtain the binding relationship between the first account identifier and the target sharing device. The account authority is used for characterizing whether the target account can add the secondary account of the target sharing device or the number of the secondary accounts which can be added, and the like. The binding relationship is used for representing whether the first account identifier and the second account identifier are bound, and specifically, the binding relationship may include bound and unbound. When the account authority of the target account meets the preset binding condition and the binding relationship between the first account identifier and the target sharing device is not bound, the server can bind the first account identifier and the target sharing device.

For example, the predetermined binding condition is that when the primary account can add the secondary account, the number of the secondary accounts that can be added does not exceed 3. After the server obtains the account authority of the target account, the server determines that the target account can be added with the secondary accounts, and the number of the added secondary accounts is 2, so that the preset binding condition is met. The server may thus bind the target sharing device with the first account identification.

Optionally, the present embodiment may further include step S209 and step S210.

Step S209, in response to the target account identifier not matching with the primary account identifier and/or the account authority not meeting the predetermined binding condition and/or the binding relationship between the first account identifier and the target sharing device being bound, sending a binding rejection prompt to the terminal.

If the target account identifier is not the main account identifier of the target sharing device, and/or the account authority of the target account does not meet the predetermined binding condition, and/or the binding relationship between the first account identifier and the target sharing device is bound, the server does not bind the first account identifier and the target sharing device, and can send a binding rejection prompt to the terminal. Optionally, the rejection of the binding prompt may be used to characterize that the target account identity does not match the primary account identity of the target sharing device and/or that the account right of the target account does not satisfy a predetermined binding condition and/or that the binding relationship of the first account identity and the target sharing device is bound.

Step S210, responding to the received rejection binding prompt, displaying the rejection binding prompt.

After receiving the binding rejection prompt, the terminal can display the binding rejection prompt in the forms of bubbles, characters and the like, and can also broadcast the character content of the binding rejection prompt in the form of voice.

Fig. 5 is a flowchart of the interaction method of the first embodiment of the present invention on the terminal side. As shown in fig. 5, the method of the present embodiment includes the following steps at the terminal side:

Step S204, receiving the input first account identification.

Step S206, sending an account binding request to the server.

Optionally, the method of this embodiment may further include the following steps at the terminal side:

Fig. 6 is a flow chart of the interaction method of the first embodiment of the present invention on the server side. As shown in fig. 5, the method of this embodiment includes the following steps on the server side:

Optionally, the method of this embodiment may further include the following steps at the server side:

The terminal of this embodiment, after acquiring the target account identifier and the sharing device identifier of the sharing device, determines a primary account identifier corresponding to the sharing device according to the sharing device identifier, then renders and displays an account binding control when the target account identifier matches the primary account identifier, and receives an input account identifier, and further when the account binding control is triggered, determines an account binding request by the target account identifier, the sharing device identifier, and the input account identifier and sends the account binding request to the server. After receiving the account binding request, the server extracts the target account identifier, the sharing device identifier and the input account identifier, and binds the input account identifier and the sharing device according to the target account identifier and the sharing device identifier. The utilization rate of the shared device rented for a long time in the idle period can be improved by adding the account identifier bound with the shared device.

Fig. 7 is a flowchart of an interaction method of the second embodiment of the present invention. As shown in fig. 7, the method of the present embodiment includes the following steps:

step S701, obtain a target account identifier and a shared device identifier.

In this embodiment, the implementation manner of step S701 is similar to that of step S201, and is not described herein again.

Step S702, determining a primary account identifier corresponding to the target sharing device according to the sharing device identifier.

In this embodiment, the implementation manner of step S702 is similar to that of step S202, and is not described herein again.

And step S703, in response to the matching of the target account identifier and the main account identifier, rendering and displaying the account binding control.

In this embodiment, the implementation manner of step S703 is similar to that of step S203, and is not described herein again.

Step S704, receiving the input first account identifier.

In this embodiment, the implementation manner of step S704 is similar to that of step S204, and is not described herein again.

Step S705, in response to the account binding control being triggered, determining an account binding request according to the target account identifier, the shared device identifier, and the first account identifier.

In this embodiment, the implementation manner of step S705 is similar to that of step S205, and is not described herein again.

Step S706, sends an account binding request to the server.

In this embodiment, the implementation manner of step S706 is similar to that of step S206, and is not described herein again.

Step S707, in response to receiving the account binding request, extracts the first account identifier, the target account identifier and the shared device identifier in the account binding request.

In this embodiment, the implementation manner of step S707 is similar to that of step S207, and is not described herein again.

Step S708, binding the first account identifier and the target sharing device according to the first account identifier and the sharing device identifier.

In this embodiment, the implementation manner of step S708 is similar to that of step S208, and is not described herein again.

Optionally, the method of this embodiment may further include step S709 and step S710.

Step S709, in response to the target account identifier not matching with the main account identifier and/or the account authority not meeting the predetermined binding condition and/or the binding relationship between the first account identifier and the target sharing device being bound, sending a binding rejection prompt to the terminal.

In this embodiment, the implementation manner of step S709 is similar to that of step S209, and is not described herein again.

Step S710, in response to receiving the binding rejection prompt, displaying the binding rejection prompt.

In this embodiment, the implementation manner of step S710 is similar to that of step S210, and is not described herein again.

In step S711, the input second account identifier is received.

Similarly, the user may unbind the account identifier from the target sharing device through the terminal without continuing to use the target sharing device, or the like. Similar to the target account ID, the second account ID may also be a user ID set by the user or automatically generated by the platform, such as a mobile phone number, a mailbox number, an identification number, a UUID, and the like of the user. Optionally, in this embodiment, the first account identifier and the second account identifier may be the same account identifier.

In this embodiment, both the primary account and the secondary account may be unbound from the target sharing device. Optionally, when the current login account is the primary account of the target sharing device, the second account identifier received and input by the terminal may be an account identifier to be unbound from the target sharing device; when the current login account is the secondary account of the target sharing device, the terminal receives the input second account identifier which can be the primary account identifier of the target sharing device; when the current login account is neither the primary account nor the secondary account of the target sharing device, the second account identifier received by the terminal may be any account identifier.

Step S712, determining an account unbinding request according to the second account identifier and the target account identifier and/or the shared device identifier.

After the target sharing device adds the binding account, the terminal can store the account identifier of the added binding account as a secondary account identifier locally; similarly, the server may also obtain the account identifier of the newly added bound account through the shared bicycle rental platform, and store the account identifier of the newly added bound account as the secondary account of the target shared device, which may be specifically stored in the database.

Therefore, the terminal can determine that the current login account is the primary account of the target sharing device or the secondary account of the target sharing device or is neither the primary account of the target sharing device nor the secondary account of the target sharing device according to the account identifier of the current login account.

In an optional implementation manner, in order to reduce the possibility that the target sharing device is unbound from the target sharing device without the knowledge of the secondary account user, and the use of the target sharing device by the secondary account user is negatively affected and the benefit of the secondary account user is damaged, in this embodiment, when the current login account identifier matches the primary account identifier of the target sharing device or the secondary account identifier of the target sharing device, the terminal may render and display an account unbound control in the interface, and when the account unbound control is triggered, determine the account unbound request according to the second account identifier and at least one of the target account identifier and the sharing device identifier of the target sharing device.

In this embodiment, the terminal may render and display the account unbinding control while receiving the input second account identifier; or receiving the input second account identifier first and then rendering and displaying the account unbinding control; the account unbinding control may also be rendered and displayed first, and then the input second account identifier is received, which is not specifically limited in this embodiment.

Optionally, the terminal may display a fourth page, and render and display the account binding control in the fourth page after determining that the target account identifier is the primary account identifier bound to the target sharing device. Wherein the fourth page may be an account unbinding page.

FIG. 8 is another interface schematic of an embodiment of the invention. As shown in FIG. 8, page P4 is an account unbinding page, and the user can enter or select the sharing device identification of the target sharing device through the sharing device identification input control 81 (i.e., the fourth position of the account binding page) within page P4. After the user inputs the sharing device identifier with the correct format, the terminal may determine whether the current login account is the primary account or the secondary account of the target sharing device. If the current login account is not the primary account or the secondary account of the target sharing device, the terminal does not render and display the account binding control 82 in the page P4, and in some alternative implementations, the account binding control 82 may be displayed in a non-clickable state.

FIG. 9 is another interface schematic of an embodiment of the invention. As shown in fig. 9, page P4 is an account unbinding page, and the user can enter or select the sharing device identification of the target sharing device through the sharing device identification input control 91 (i.e., the fourth position of the account binding page) within page P4. After the user inputs the sharing device identifier with the correct format, the terminal may determine whether the current login account is the primary account or the secondary account of the target sharing device. If the current login account is the primary account or the secondary account of the target sharing device, the terminal may render and display an account unbinding control 92 in page P4, and in some alternative implementations, the account unbinding control 92 may be displayed in a non-clickable state. Also, the terminal may receive a second account identification input by the user through an account identification input control 93 (i.e., the fourth position of the account binding page) within page P4. It will be readily appreciated that the shared device identification input control 91 and the account identification input control 93 may be the same control or different controls.

In another optional implementation manner, the terminal may also determine the account unbinding request according to the second account identifier, the target account identifier, and the sharing device identifier of the target sharing device.

Step S713, an account unbinding request is sent to the server.

After determining the account unbinding request, the terminal may send an account unbinding request to the server to unbind the second account identification from the target sharing device.

Step S714, in response to receiving the account unbinding request, extracting the second account identifier and the target account identifier and/or the shared device identifier in the account unbinding request.

After receiving the account unbinding request sent by the terminal, the server may extract the second account identifier and at least one of the target account identifier and the shared device identifier of the target shared device in the account unbinding request.

Step S715, the second account identifier and the target sharing device are unbound according to the sharing device identifier or the target account identifier.

In an alternative implementation manner, the server may determine the primary account identifier or the secondary account identifier bound to the target sharing device according to the target account identifier or the sharing device identifier. If the second account identifier matches the primary account identifier or any one of the secondary account identifiers, the server may determine that the binding relationship between the second account identifier and the target sharing device is bound, and unbind the second account identifier from the target sharing device.

Optionally, the present embodiment may further include step S716 and step S717.

Step S716, in response to the binding relationship being not bound, sending a prompt to the terminal to refuse to release the binding.

Optionally, if the server cannot determine the primary account identifier or the secondary account identifier bound to the target sharing device according to the target account identifier, or the second account identifier is not matched with the primary account identifier and each secondary account identifier of the target sharing device, it may be determined that the binding relationship between the second account identifier and the target sharing device is not bound, and a prompt of refusing to unbind is sent to the terminal.

Similarly, the unbinding prompt may be used to characterize the binding relationship of the second account identification to the target sharing device or that the target account is not a primary account identification or a secondary account of the target sharing device.

In step S717, in response to receiving the prompt to refuse the unbinding, the prompt to refuse the unbinding is displayed.

After receiving the prompt of refusing to remove the binding, the terminal can display the prompt of refusing to remove the binding in the forms of bubbles, characters and the like, and can also broadcast the character content of refusing to remove the binding prompt in the form of voice.

Fig. 10 is a flowchart of the interaction method of the second embodiment of the present invention at the terminal side. As shown in fig. 10, the method of the present embodiment includes the following steps on the terminal side:

step S701, obtain a target account identifier and a shared device identifier.

Step S704, receiving the input first account identifier.

Step S706, sends an account binding request to the server.

In step S711, the input second account identifier is received.

Step S713, an account unbinding request is sent to the server.

Fig. 11 is a flow chart of the interaction method of the second embodiment of the present invention on the server side. As shown in fig. 11, the method of the present embodiment includes the following steps on the server side:

The terminal of this embodiment, after acquiring the target account identifier and the sharing device identifier of the sharing device, determines a primary account identifier corresponding to the sharing device according to the sharing device identifier, then renders and displays an account binding control when the target account identifier matches the primary account identifier, and receives an input account identifier, and further when the account binding control is triggered, determines an account binding request by the target account identifier, the sharing device identifier, and the input account identifier and sends the account binding request to the server. After receiving the account binding request, the server extracts the target account identifier, the sharing device identifier and the input account identifier, and binds the input account identifier and the sharing device according to the target account identifier and the sharing device identifier. In addition, after acquiring the target account identifier and the sharing device identifier of the sharing device, the terminal of this embodiment may receive the input second account identifier, and determine, according to at least one of the second account identifier and the target account identifier and the sharing device identifier of the sharing device, that the account unbinding request is sent to the server. After receiving the account unbinding request, the server extracts at least one of the account identifier and the target account identifier, which are input in the account unbinding request, and the shared device identifier of the shared device, and unbound the second account identifier and the shared device according to the at least one of the input account identifier and the target account identifier, and the shared device identifier of the shared device. The utilization rate of the shared device rented for a long time in the idle period can be improved by adding the account identifier bound with the shared device.

Fig. 12 is a schematic diagram of an interactive system of a third embodiment of the present invention. As shown in fig. 12, the system of the present embodiment includes an interaction device 12A and an interaction device 12B.

The interaction device 12A includes a first identifier obtaining unit 1201, a primary account determining unit 1202, a control displaying unit 1203, a first identifier receiving unit 1204, a binding request determining unit 1205, and a binding request sending unit 1206.

The first identifier obtaining unit 1201 is configured to obtain a target account identifier and a shared device identifier, where the shared device identifier is an identifier of a target shared device. The primary account determining unit 1202 is configured to determine, according to the sharing device identifier, a primary account identifier corresponding to the target sharing device. The control display unit 1203 is configured to render and display an account binding control in response to the target account identifier matching with the primary account identifier. The first identifier receiving unit 1204 is configured to receive an input first account identifier. The binding request determining unit 1205 is configured to determine, in response to the account binding control being triggered, an account binding request according to the target account identifier, the shared device identifier, and the first account identifier. The binding request sending unit 1206 is configured to send the account binding request to a server to bind the first account identifier with the target sharing device.

Further, the primary account determination unit 1202 includes a device identifier transmission subunit and a primary account identifier reception subunit.

The device identifier sending subunit is configured to send the shared device identifier to a server. The main account identification receiving subunit is configured to receive the main account identification sent by the server.

Further, the interaction apparatus 12A further includes a second identifier receiving unit 1207, a release request determining unit 1208, and a release request transmitting unit 1209.

The second identifier receiving unit 1207 is configured to receive an input second account identifier. The unbinding request determining unit 1208 is configured to determine an account unbinding request according to the second account identifier and the target account identifier and/or the shared device identifier. A unbinding request sending unit 1209 is configured to send the account unbinding request to the server to unbind the second account identifier from the target sharing device.

Further, the release request determining unit 1208 includes a secondary account determining subunit, a control displaying subunit, and a release request determining subunit.

And the secondary account determining subunit is used for determining a secondary account identifier corresponding to the target sharing device according to the sharing device identifier. And the control display subunit is used for rendering and displaying the account unbinding control in response to the matching of the target account identifier and the main account identifier or the matching of the target account identifier and the secondary account identifier. The unbinding request determining subunit is configured to determine, in response to the account unbinding control being triggered, the account unbinding request according to the second account identifier and the target account identifier and/or the shared device identifier.

Further, the interaction device 12A further includes a first prompt display unit 1210.

The first prompt display unit 1210 is configured to display a binding rejection prompt in response to receiving the binding rejection prompt.

Further, the interaction device 12A further includes a second prompt display unit 1211.

The second prompt display unit 1211 displays the rejection unbinding prompt in response to receiving the rejection unbinding prompt.

The interaction means 12B comprises a first identity extraction unit 1212 and an account binding unit 1213.

The first identifier extracting unit 1212 is configured to, in response to receiving the account binding request, extract the first account identifier, the target account identifier, and the shared device identifier in the account binding request, where the shared device identifier is an identifier of the target shared device. The account binding unit 1213 is configured to bind the first account identifier with the target sharing device according to the target account identifier and the sharing device identifier.

Further, the account binding unit 1213 includes a primary account determination subunit, a first binding relationship determination subunit, and a binding subunit.

And the primary account determining subunit is configured to determine, according to the sharing device identifier, a primary account identifier corresponding to the target sharing device. The first binding relationship determining subunit is configured to, in response to matching between the target account identifier and the primary account identifier, obtain an account permission of the target account identifier and a binding relationship between the first account identifier and the target sharing device. And the binding subunit is used for binding the first account identifier and the target sharing device in response to the account permission meeting a preset binding condition and the binding relationship being unbound.

Further, the interaction device 12B further includes a first prompt sending unit 1214.

The first prompt sending unit is used for sending a binding rejection prompt to the terminal in response to that the target account identifier is not matched with the main account identifier and/or the account authority does not meet the preset binding condition and/or the binding relationship between the first account identifier and the target sharing device is bound.

Further, the interaction device 12B further comprises a second identity extraction unit 1215 and an account unbinding unit 1216.

Wherein the second identifier extracting unit 1215 is configured to, in response to receiving the account unbinding request, extract the second account identifier and the target account identifier and/or the shared device identifier in the account unbinding request. The account unbinding unit 1216 is configured to unbind the second account identifier from the target sharing device according to at least one of the sharing device identifier and the target account identifier.

Further, the account unbinding unit 1216 includes a second binding relationship determination subunit and a unbinding subunit.

The second binding relationship determining subunit is configured to determine, according to at least one of the shared device identifier and the target account identifier, a binding relationship between the second account identifier and the target shared device. And the unbinding subunit is used for unbinding the second account identifier and the target sharing device in response to the binding relationship being bound.

Further, the interaction device 12B further includes a second prompt sending unit 1217.

The second prompt sending unit 1217 is configured to send a prompt to reject unbinding to the terminal in response to that the binding relationship is not binding.

Fig. 13 is a schematic view of an electronic apparatus according to a fourth embodiment of the present invention. The electronic device shown in fig. 13 is a general-purpose data processing apparatus comprising a general-purpose computer hardware structure including at least a processor 1301 and a memory 1302. The processor 1301 and the memory 1302 are connected by a bus 1303. The memory 1302 is adapted to store instructions or programs executable by the processor 1301. Processor 1301 may be a stand-alone microprocessor or a collection of one or more microprocessors. Thus, the processor 1301 implements the processing of data and the control of other devices by executing the commands stored in the memory 1302 to thereby execute the method flows of the embodiments of the present invention as described above. The bus 1303 connects the above-described components together, and also connects the above-described components to a display controller 1304 and a display device and an input/output (I/O) device 1305. Input/output (I/O) devices 1305 may be a mouse, keyboard, modem, network interface, touch input device, motion sensing input device, printer, and other devices known in the art. Typically, an input/output (I/O) device 1305 is connected to the system through an input/output (I/O) controller 1306.

The memory 1302 may store, among other things, software components such as an operating system, communication modules, interaction modules, and application programs. Each of the modules and applications described above corresponds to a set of executable program instructions that perform one or more functions and methods described in embodiments of the invention.

The flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention described above illustrate various aspects of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

Also, as will be appreciated by one skilled in the art, aspects of embodiments of the present invention may be embodied as a system, method or computer program product. Accordingly, various aspects of embodiments of the invention may take the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," module "or" system. Further, aspects of the invention may take the form of: a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.

Any combination of one or more computer-readable media may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of embodiments of the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to: electromagnetic, optical, or any suitable combination thereof. The computer readable signal medium may be any of the following computer readable media: is not a computer readable storage medium and may communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including: object oriented programming languages such as Java, Smalltalk, C + +, PHP, Python, and the like; and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package; executing in part on a user computer and in part on a remote computer; or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The embodiment of the invention discloses a TS1 and an interaction method, which are applicable to a terminal, and the method comprises the following steps:

receiving an input first account identification;

TS2, the method of TS1, the determining, from the sharing device identification, a primary account identification corresponding to the target sharing device includes:

sending the sharing equipment identification to a server;

and receiving the primary account identification sent by the server.

TS3, the method of TS1, the method further comprising:

receiving an input second account identification;

determining an account unbinding request according to the second account identifier and the target account identifier and/or the shared device identifier;

sending the account unbinding request to a server to unbind the second account identification from the target sharing device.

TS4, the method of TS3, the determining an account unbinding request from the second account identification and the target account identification and/or the shared device identification comprising:

determining a secondary account identifier corresponding to the target sharing device according to the sharing device identifier;

in response to the target account identification matching the primary account identification or the target account identification matching the secondary account identification, rendering and displaying an account unbinding control;

in response to the account unbinding control being triggered, determining the account unbinding request according to the second account identification and the target account identification and/or the shared device identification.

TS5, the method of TS1, the method further comprising:

and responding to the received binding rejection prompt, and displaying the binding rejection prompt.

TS6, the method of TS3, the method further comprising:

in response to receiving a decline to unbind prompt, displaying the decline to unbind prompt.

The embodiment of the invention also discloses a TS7 and an interaction method, which are applicable to a server, and the method comprises the following steps:

TS8, the method of TS7, the binding the first account identification with the target shared device according to the target account identification and the shared device identification comprising:

responding to the matching of the target account identification and the main account identification, and acquiring the account authority of the target account identification and the binding relationship between the first account identification and the target sharing device;

and in response to the account authority meeting a preset binding condition and the binding relationship being unbound, binding the first account identifier with the target sharing device.

TS9, the method of TS8, the method further comprising:

and sending a binding rejection prompt to a terminal in response to that the target account identification is not matched with the main account identification and/or the account authority does not meet the preset binding condition and/or the binding relationship between the first account identification and the target sharing device is bound.

TS10, the method of TS7, the method further comprising:

in response to receiving an account unbinding request, extracting a second account identifier and the target account identifier and/or the shared device identifier in the account unbinding request;

and unbinding the second account identifier and the target shared device according to at least one of the shared device identifier and the target account identifier.

TS11, the method of TS10, the unbinding the second account identification from the target shared device as a function of at least one of the shared device identification and the target account identification including:

determining a binding relationship between the second account identifier and the target sharing device according to at least one of the sharing device identifier and the target account identifier;

in response to the binding relationship being bound, unbinding the second account identification from the target shared device.

TS12, the method of TS11, the method further comprising:

and responding to the condition that the binding relationship is not bound, and sending a prompt of refusing to remove the binding to the terminal.

The embodiment of the invention also discloses a TS13 and an interaction device, which are applicable to terminals, and the device comprises:

The embodiment of the invention also discloses a TS14 and an interaction device, which are applicable to a server, wherein the device comprises:

The embodiment of the invention also discloses a TS15 and an interactive system, wherein the system comprises:

The embodiment of the invention also discloses a TS16 and a computer readable storage medium, wherein computer program instructions are stored on the storage medium, and when the computer program instructions are executed by a processor, the method is realized according to any one of TS1-TS 12.

The embodiment of the invention also discloses TS17 and an electronic device, which comprises a memory and a processor, wherein the memory is used for storing one or more computer program instructions, and the one or more computer program instructions are executed by the processor to realize the method according to any one of TS1-TS 12.

Embodiments of the present invention also disclose TS18, a computer program product comprising computer programs/instructions for execution by a processor for implementing a method as described in any of TS1-TS 12.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. An interaction method applicable to a terminal, the method comprising:

receiving an input first account identification;

2. The method according to claim 1, wherein the determining, according to the sharing device identifier, a primary account identifier corresponding to the target sharing device includes:

sending the sharing equipment identification to a server;

and receiving the primary account identification sent by the server.

3. An interaction method applied to a server, the method comprising:

4. The method of claim 3, wherein the binding the first account identifier with the target sharing device according to the target account identifier and the sharing device identifier comprises:

5. An interactive device adapted for a terminal, the device comprising:

6. An interaction apparatus adapted for use with a server, the apparatus comprising:

7. An interactive system, characterized in that the system comprises:

8. A computer-readable storage medium on which computer program instructions are stored, which, when executed by a processor, implement the method of any one of claims 1-4.

9. An electronic device comprising a memory and a processor, wherein the memory is configured to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method of any of claims 1-4.

10. A computer program product comprising computer programs/instructions, characterized in that the computer programs/instructions are executed by a processor to implement the method according to any of claims 1-4.