CN109040049B - User registration method and device and electronic equipment - Google Patents
User registration method and device and electronic equipment Download PDFInfo
- Publication number
- CN109040049B CN109040049B CN201810829785.1A CN201810829785A CN109040049B CN 109040049 B CN109040049 B CN 109040049B CN 201810829785 A CN201810829785 A CN 201810829785A CN 109040049 B CN109040049 B CN 109040049B
- Authority
- CN
- China
- Prior art keywords
- user
- registration
- account
- client
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000009191 jumping Effects 0.000 claims description 16
- 230000004044 response Effects 0.000 claims description 14
- 230000000977 initiatory effect Effects 0.000 claims description 8
- 238000010586 diagram Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 238000012790 confirmation Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
Abstract
One or more embodiments of the present specification provide a user registration method and apparatus, and an electronic device, where the method may include: responding to an assisted registration operation initiated by a first user, and outputting an assisted registration interface to the first user; acquiring a second user identifier of a second user, which is input in the assistance registration interface by the first user; sending an assistance registration message to a second client corresponding to the second user identifier through a server, wherein the assistance registration message comprises the first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and configures a payment security policy for the registered account.
Description
Technical Field
One or more embodiments of the present disclosure relate to the technical field of computer applications, and in particular, to a user registration method and apparatus, and an electronic device.
Background
Generally, a user can log in to a client based on an account which is already registered, and the logged-in client can output a user interface to the user. In the user interface of the client output, a plurality of function entries can be provided, and the user can trigger the function entries to complete corresponding operations on the client. However, for special user groups such as the elderly, it is difficult for such user groups to autonomously complete account registration. Under the circumstances, how to enable some user groups which cannot finish account registration independently to finish account registration conveniently through a client becomes a problem which needs to be solved urgently.
Disclosure of Invention
The present specification provides a user registration method, which is applied to a first client, and includes:
responding to an assisted registration operation initiated by a first user, and outputting an assisted registration interface to the first user;
acquiring a second user identifier of a second user, which is input in the assistance registration interface by the first user;
sending an assistance registration message to a second client corresponding to the second user identifier through a server, wherein the assistance registration message comprises the first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and configures a payment security policy for the registered account.
Optionally, the method further comprises:
receiving a registration result returned by the server; the registration result comprises a first user identification which is an account name and an account login password which is set for the first user on the second client by the second user;
and displaying the registration result through the assistant registration interface.
Optionally, the method further comprises:
and automatically executing login based on the account name and the account login password in the registration result.
Optionally, the first client includes a voice input option;
the acquiring a second user identifier of a second user input by the first user in the assistance registration interface includes:
responding to the triggering operation of the first user for the voice input option, and acquiring a voice instruction input by the first user;
and analyzing the voice command to acquire a second user identifier of a second user input by the first user.
Optionally, the account is a payment account; the security policy is a payment security policy;
the payment security policy comprises any one or a combination of more of:
maximum limit for single payment;
pay exemption scenario.
Optionally, the server maintains a binding relationship between the first user identifier and the second user identifier;
the method further comprises the following steps:
responding to the user binding updating operation of the first user, and acquiring a third user identifier of a third user specified by the first user;
and sending the third user identifier to the server, so that the server updates the binding relationship between the first user identifier and the second user identifier into the binding relationship between the first user identifier and the third user identifier.
Optionally, the obtaining a third user identifier of a third user specified by the first user includes:
acquiring a third user identification of a third user input by the first user; alternatively, the first and second electrodes may be,
and responding to the scanning operation of the first user on the graphic code generated based on the third user identification of the third user, analyzing the graphic code, and acquiring the third user identification of the third user.
Optionally, the first user identifier and the second user identifier include mobile phone numbers.
Optionally, the user interface of the first client is a simple interface consisting of a scanning entry and a payment code entry.
The present specification also provides another user registration method, which is applied to a second client, and includes:
responding to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, and jumping to an assistance registration interface;
acquiring registration information input by the second user in the assisted registration interface; wherein the registration information includes a security policy configured for the registered account by the second user;
and initiating account registration for the first user to a server based on the acquired registration information.
Optionally, the encoding information carried in the graphic code includes a URL address of the assisted registration interface;
the jumping to a help registration interface in response to a second user initiated image scanning operation on a graphical code output on a first client of a first user comprises:
in response to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, analyzing the graphic code to acquire a URL (uniform resource locator) address of the assisted registration interface;
and jumping to the assistant registration interface based on the acquired URL address.
Optionally, the encoding information carried in the graphic code further includes a first user identifier of the first user;
the method further comprises the following steps:
analyzing the graphic code to obtain a first user identifier of the first user;
and displaying the first user identification through the assistant registration interface.
The present specification also provides a user registration apparatus, which is applied to a first client, and includes:
the output module is used for responding to assisted registration operation initiated by a first user and outputting an assisted registration interface to the first user;
the first acquisition module is used for acquiring a second user identifier of a second user, which is input in the assistance registration interface by the first user;
the first sending module is used for sending an assistance registration message to a second client corresponding to the second user identifier through a server, wherein the assistance registration message comprises the first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and a payment security policy is configured for the registered account.
Optionally, the apparatus further comprises:
the receiving module is used for receiving the registration result returned by the server; the registration result comprises a first user identification which is an account name and an account login password which is set for the first user on the second client by the second user;
and the display module is used for displaying the registration result through the assisted registration interface.
Optionally, the apparatus further comprises:
and the login module is used for automatically executing login based on the account name and the account login password in the registration result.
Optionally, the first client includes a voice input option;
the first obtaining module is specifically configured to:
responding to the triggering operation of the first user for the voice input option, and acquiring a voice instruction input by the first user;
and analyzing the voice command to acquire a second user identifier of a second user input by the first user.
Optionally, the account is a payment account; the security policy is a payment security policy;
the payment security policy comprises any one or a combination of more of:
maximum limit for single payment;
pay exemption scenario.
Optionally, the server maintains a binding relationship between the first user identifier and the second user identifier;
the device further comprises:
a second obtaining module, configured to obtain, in response to a user binding update operation of the first user, a third user identifier of a third user specified by the first user;
and the second sending module is used for sending the third user identifier to the server so that the server updates the binding relationship between the first user identifier and the second user identifier into the binding relationship between the first user identifier and the third user identifier.
Optionally, the second obtaining module is specifically configured to:
acquiring a third user identification of a third user input by the first user; alternatively, the first and second electrodes may be,
and responding to the scanning operation of the first user on the graphic code generated based on the third user identification of the third user, analyzing the graphic code, and acquiring the third user identification of the third user.
Optionally, the first user identifier and the second user identifier include mobile phone numbers.
Optionally, the user interface of the first client is a simple interface consisting of a scanning entry and a payment code entry.
The present specification also provides another user registration apparatus, which is applied to a second client, the apparatus including:
the skip module is used for responding to image scanning operation initiated by a second user on the graphic code output on the first client of the first user and skipping to the assisted registration interface;
the acquisition module is used for acquiring the registration information input by the second user in the assisted registration interface; wherein the registration information includes a security policy configured for the registered account by the second user;
and the registration module is used for initiating account registration aiming at the first user to a server side based on the acquired registration information.
Optionally, the encoding information carried in the graphic code includes a URL address of the assisted registration interface;
the skip module is specifically configured to:
in response to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, analyzing the graphic code to acquire a URL (uniform resource locator) address of the assisted registration interface;
and jumping to the assistant registration interface based on the acquired URL address.
Optionally, the encoding information carried in the graphic code further includes a first user identifier of the first user;
the device further comprises:
the analysis module is used for analyzing the graphic code to obtain a first user identifier of the first user;
and the display module is used for displaying the first user identification through the assistant registration interface.
This specification also provides an electronic device, including:
a processor;
a memory for storing machine executable instructions;
wherein, by reading and executing machine-executable instructions stored by the memory that correspond to user-registered control logic, the processor is caused to:
responding to an assisted registration operation initiated by a first user, and outputting an assisted registration interface to the first user;
acquiring a second user identifier of a second user, which is input in the assistance registration interface by the first user;
sending an assistance registration message to a second client corresponding to the second user identifier through a server, wherein the assistance registration message comprises the first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and configures a payment security policy for the registered account.
This specification also provides another electronic device, including:
a processor;
a memory for storing machine executable instructions;
wherein, by reading and executing machine-executable instructions stored by the memory that correspond to user-registered control logic, the processor is caused to:
responding to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, and jumping to an assistance registration interface;
acquiring registration information input by the second user in the assisted registration interface; wherein the registration information includes a security policy configured for the registered account by the second user;
and initiating account registration for the first user to a server based on the acquired registration information.
By the technical scheme, the third-party user can assist some user groups which cannot finish account registration to finish account registration, and the third-party user configures the security policy for the registered account, so that the account registration process can be simplified, some user groups which cannot finish account registration can also finish account registration conveniently through the client.
Drawings
FIG. 1 is a flow chart illustrating a method of user registration in an exemplary embodiment of the present description;
FIG. 2 is a schematic diagram of a user interaction system shown in the present specification;
FIG. 3 is a schematic diagram of a login interface shown herein;
FIG. 4 is a schematic illustration of an assistance registration interface shown herein;
FIG. 5 is a schematic illustration of another assistance registration interface shown herein;
FIG. 6 is a schematic diagram of a user interface of a simplified version of a payment client shown in the present specification;
FIG. 7 is a flow chart illustrating another method of user registration in an exemplary embodiment of the present description;
fig. 8 is a hardware configuration diagram of an electronic device in which a user registration apparatus is located according to an exemplary embodiment of the present specification;
FIG. 9 is a block diagram of a user registration apparatus shown in an exemplary embodiment of the present description;
fig. 10 is a block diagram of another user registration apparatus shown in an exemplary embodiment of the present specification.
Detailed Description
The technical scheme is that a third-party user assists some user groups (such as elderly people groups and the like) incapable of autonomously completing account registration to complete account registration, and the third-party user performs security configuration on the account which is completed by registration.
When the method is implemented, a first user who cannot autonomously complete the registration operation can initiate the registration assisting operation on a first client and invite a second user to assist the first user to complete account registration.
For example, taking the first user as an example of an elderly person who cannot autonomously complete the registration operation, the first user may initiate the assisted registration operation on the first client to invite a child of the first user to assist the first user in completing the account registration.
The first client-side can respond to the assistance registration operation initiated by the first user, and output an assistance registration interface to the first user, and prompt the first user to input the relevant information of the assistant in the assistance registration interface. The first user can input a second user identification of a second user serving as a helper in the assistance registration interface, and sends an assistance registration message to a second client corresponding to the second user identification of the second user through the server;
wherein, the assistance registration message may include a first user identifier of the first user; for example, when the first user inputs the information related to the helper in the assistance registration interface, the first user may also submit the user identifier (e.g., a mobile phone number, etc.) of the first user in the assistance registration interface as the information of the registrar.
After receiving the registration assisting message, the second client may assist the first user in completing account registration based on the first user identifier of the first user on the second client, and configure a corresponding security policy for the registered account.
In the technical scheme, the third-party user can assist some user groups which cannot finish account registration to finish account registration, and the third-party user configures a security policy for the registered account, so that the account registration process can be simplified, some user groups which cannot finish account registration can also finish account registration conveniently through the client.
The technical solution of the present specification is described in detail by the following specific examples.
Referring to fig. 1, fig. 1 is a flowchart illustrating a user registration method according to an exemplary embodiment of the present disclosure. The method can be applied to a first client, and comprises the following steps:
step 101: and responding to the assisted registration operation initiated by the first user, and outputting an assisted registration interface to the first user.
Step 102: and acquiring a second user identification of a second user, which is input in the assistance registration interface by the first user.
Step 103: sending an assistance registration message to a second client corresponding to the second user identifier through a server, wherein the assistance registration message comprises the first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and configures a payment security policy for the registered account.
In this embodiment, the first user may include a group of users who cannot autonomously complete account registration; the second user may include a group of users who have a certain social relationship with the first user and have completed account registration;
for example, the first user may be an elderly person who cannot perform account registration autonomously, and the second user may be a child of the elderly person.
The first client is a client currently used by the first user; the second client is a client currently used by the second user, that is, the second user logs in based on the registered account.
The first user identifier may specifically include identification information capable of uniquely identifying the first user; similarly, the second user identifier may specifically include identification information capable of uniquely identifying the second user.
In practical applications, the first user identifier and the second user identifier may include mobile phone numbers. Of course, the first user identifier and the second user identifier may be other forms of identification information capable of completing account registration, such as: mailboxes, social accounts, etc. of the first user and the second user.
The following describes the technical solution of the present specification in detail by taking an application scenario in which the second user assists the first user in completing the payment account registration as an example.
It should be noted that, taking an application scenario in which the second user assists the first user in completing registration of the payment account as an example, this is only exemplary; obviously, the technical solution of the present specification can also be applied to other forms of account registration scenarios, for example: the second user assists the first user in completing social account registration, etc.
Referring to fig. 2, fig. 2 is a schematic diagram of a user interaction system shown in this specification.
As shown in fig. 2, data exchange between a first client currently used by a first user and a second client registered by a second user using a payment account of the second user may be performed through a server.
In this embodiment, the first client may provide a login interface for the first user. The first user may log in through the login interface based on the payment account that has been registered for completion.
Referring to fig. 3, fig. 3 is a schematic diagram of a login interface shown in this specification.
As shown in fig. 3, in the login interface, an assistance registration button 31 may be provided in addition to the usual login button and registration button. The first user may enter into a subsequent process of completing the registration of the payment account with the assistance of the second user by triggering the assistance registration button 31.
After the first user triggers the assistance registration button 31, the first client may regard as detecting an assistance registration operation initiated by the first user, so as to output an assistance registration interface to the first user. The first user can invite the second user to assist the second user in completing the payment account registration through the assisted registration interface.
Referring to fig. 4, fig. 4 is a schematic diagram of an assisted registration interface shown in this specification, where the assisted registration interface is output by a first client to a first user.
As shown in fig. 4, in the assistance registration interface, a text input option 41 for inputting a second user identification may be provided. The first user may enter a second user identification via the text entry option 41 to invite the second user to assist in completing the payment account registration itself. For example, the first user may input a mobile phone number currently used by the second user as the second user identifier through the text input option 41.
In one illustrated embodiment, a voice input option 42 may also be provided in the assistance registration interface shown in FIG. 4. The first user may, upon triggering the voice input option 42, vocally input a second user identification via the microphone. After detecting the triggering operation of the first user on the voice input option 42, the first client may collect a voice signal through a microphone to obtain a voice instruction input by the first user. Subsequently, the first client may parse the voice instruction to obtain a second user identifier input by the first user in a voice manner.
In addition, in the assistance registration interface shown in fig. 4, a submit button 43 may be provided, and the first user may perform a trigger operation on the submit button 43 after completing the input of the second user identifier. The first client may acquire the second user identifier input by the first user after detecting the triggering operation of the first user on the submit button 43.
The first client may obtain the first user identifier in addition to the second user identifier input by the first user in the assistance registration interface. For example, if the first client runs on a mobile phone used by the first user, the first client may directly obtain a mobile phone number currently used by the first user as the first user identifier.
In one embodiment shown, a text entry option 44 may also be provided in the assistance registration interface shown in fig. 4, and the first user may enter his or her first user identification through the text entry option 44. The first user may perform a trigger operation on the submit button 43 after completing the input of the second user identification and the first user identification. The first client may acquire the first user identification and the second user identification input by the first user after detecting the triggering operation of the first user on the submit button 43.
After acquiring the first user identifier and the second user identifier, the first client may send an assistance registration message to the second client through the server according to the second user identifier. Wherein the assistance registration message may include the first subscriber identity.
Specifically, please refer to fig. 2 again, after the first client obtains the first user identifier and the second user identifier, the first client may generate an assistance registration message including the first user identifier, and send the assistance registration message and the second user identifier to the server.
After receiving the assisted registration message sent by the first client, the server may first confirm whether the payment account of the second user (i.e., the payment account with the second user identifier as the account name) is online based on the received second user identifier.
If the server confirms that the payment account of the second user is online, the assistance registration message can be sent to the second client according to the second user identification.
If the server side confirms that the payment account of the second user is not on line, the second user can be informed in a short message or mail mode that the first user invites the second user to assist the second user to complete the payment account registration. For example, assuming that the second user identifier is a mobile phone number used by the second user, a notification short message may be sent to the mobile phone number, where the notification short message may include the first user identifier and text content for explaining the assisted registration request; or, assuming that the second user identifier is a mailbox used by the second user, a notification email may be sent to the mailbox, and the notification email may also include the first user identifier and text content of the user description assistance registration request.
After receiving the assistance registration message sent by the server, the second client may output an assistance registration interface to the second user, and display the first user identifier to the second user in the assistance registration interface. The second user can complete the registration of the payment account aiming at the first user through the assistant registration interface, and configures a payment security policy for the registered payment account.
Referring to fig. 5, fig. 5 is a schematic diagram illustrating another assistance registration interface output by the second client to the second user according to the present disclosure.
As shown in fig. 5, in the assistance registration interface, a text input option 51 for inputting an account name and a text input option 52 for inputting an account login password may be provided.
The second client may present the first user identification directly in the text input option 51 for viewing by the second user so that the second user may identify the first user who needs assistance in completing the payment account registration. At this time, the first user identifier may be used as an account name of a payment account registered by the second user to assist the first user.
Alternatively, the second user may re-enter the account name of the payment account that assisted the registration of the first user through the text entry option 51.
On the other hand, the second user may enter an account login password that assists the payment account registered by the first user through the text entry option 52.
In the assistance registration interface shown in fig. 5, a submit button 53 may also be provided. The second user may perform a trigger operation on the submit button 53 after completing the input of the account name and the account login password. The second client may acquire the account name and the account login password of the payment account registered by the second user with the assistance of the first user after detecting the triggering operation of the second user on the submit button 53.
Subsequently, with continued reference to fig. 2, the second client may return the registration result including the account name and the account login password to the server. After receiving the registration result returned by the second client, the server may store the corresponding relationship between the account name and the account login password, and use the corresponding relationship for checking the login of the payment account of the first user. In this way, the second user completes the registration of the payment account with respect to the first user.
Since the first user may generally be an old person, in order to reduce the probability and loss of the old person being cheated, that is, to reduce the security risk of the old person using the payment client, when the second user assists the first user in registering the payment account, the second user may further configure a payment security policy for the registered payment account, that is, configure a payment security policy for the payment account that assists the first user in registering, for example: and configuring a single payment maximum limit, a payment exemption scene and the like for the payment account for assisting the first user to register.
With continued reference to fig. 5, in the assisted registration interface shown in fig. 5, a plurality of text entry options for payment security policy configuration may also be provided, through which the second user may enter a payment security policy configured for the payment account registered with the first user. For example, text entry option 54 may be a text entry option for entering a maximum limit for a single payment, and text entry option 55 may be a text entry option for entering a payment exemption scenario.
The second user can not only input the account name of the payment account for assisting the first user's registration through the text input option 51 and the account login password of the payment account for assisting the first user's registration through the text input option 52, but also input the maximum limit of a single payment through the text input option 54 and input the payment exemption scene through the text input option 55. The second user may trigger the submit button 53 after completing the entry of the account name, account login password, and payment security policy. After detecting the triggering operation of the second user on the submit button 53, the second client may obtain not only the account name and the account login password of the payment account registered by the second user with the first user, but also the payment security policy configured for the payment account by the second user.
Subsequently, with continuing reference to fig. 2, the second client may return the registration result including the account name, the account login password, and the payment security policies to the server, and after receiving the registration result returned by the second client, the server may store the correspondence between the account name and the account login password for the payment account login verification of the first user, and store the correspondence between the payment account and the payment security policies that the second user assists the first user in registering for the payment security verification of the first user. In this way, the second user completes the registration of the payment account for the first user, and configures the payment security policy for the registered payment account.
Further, the server may return the registration result to the first client, and after receiving the registration result returned by the server, the first client may display the registration result to the first user through an assisted registration interface (an assisted registration interface shown in fig. 4) output to the first user. The first user can check the account name and the account login password of the payment account which is registered by the second user, and login is carried out on the first client based on the payment account.
In one embodiment shown, after receiving the registration result returned by the server, the first client may automatically perform login based on the account name and the account login password in the registration result, that is, automatically perform login based on the payment account registered by the first user assisted by the second user, without inputting the account name and the account login password by the first user himself, so as to further simplify the operation flow of the first user.
After logging in to the first client with the payment account, the first client may output a user interface to the first user. The first user may complete the payment operation through the user interface on the first client.
In a conventional payment client, a user interface may be provided with a plurality of function entries facing a user group, and the user may trigger the function entries to complete corresponding operations on the payment client.
However, in practical applications, a lot of functional entries are provided in the user interface of the payment client, on one hand, there may be many unnecessary functional entries; on the other hand, the increase of function entries also increases the operation complexity of the user intangibly, so that the user experience is affected for some special user groups which cannot finish the operation on the payment client autonomously.
Referring to fig. 6, fig. 6 is a schematic diagram of a user interface of a simplified payment client shown in this specification.
As shown in fig. 6, in the user interface of the easy version payment client, only a scan entry and a pay code entry may be included, for example: the pay code entry is shown at 61 in fig. 6 and the scan entry is shown at 62 in fig. 6. In this way, functional entries provided in the user interface of the payment client are reduced, and the operational complexity of the user is reduced.
It should be noted that, the server may store and maintain the binding relationship between the first user identifier and the second user identifier, so that the second user may configure and manage the payment account of the first user.
In one example, a user binding update button may be provided in a user interface output by the first client to the first user. After the first user triggers the user binding update button, the first client may output a user binding update interface to the first user.
In the user binding update interface, text entry options may be provided. The first user can input a third user identifier of a third user needing to be bound with the first user through the text input option, and trigger operation is carried out aiming at a confirmation button provided in the user binding updating interface.
After detecting the trigger operation of the first user for the confirmation button, the first client may be regarded as detecting the user binding update operation of the first user, so that the third user identifier input by the first user may be acquired.
Subsequently, the first client may send the third user identifier of the third user to the server, and the server may update the originally maintained binding relationship between the first user identifier of the first user and the second user identifier of the second user to the binding relationship between the first user identifier and the third user identifier, that is, the third user may replace the second user to configure and manage the payment account of the first user.
In another example, a scan portal may be provided in a user interface output by the first client to the first user. The first user can scan the graphic code generated based on the third user identification of the third user needing to be bound with the first user through the scanning entrance. The graphic code may specifically include a graphic code in the form of a two-dimensional code or a barcode.
When detecting the scanning operation executed by the first user through the scanning entrance, the first client may parse the scanned graphic code, so as to obtain a third user identifier of a third user.
Subsequently, the first client may send the third user identifier of the third user to the server, and the server may update the originally maintained binding relationship between the first user identifier of the first user and the second user identifier of the second user to the binding relationship between the first user identifier and the third user identifier, that is, the third user may replace the second user to configure and manage the payment account of the first user.
In an illustrated embodiment, the first client may construct a binding message carrying the third user identifier and the timestamp, and send the binding message to the server. When receiving the binding message sent by the first client, the server may first determine whether the binding message is within the validity period according to the timestamp in the binding message. If the binding message is still within the validity period, the server side can update the originally maintained binding relationship between the first user identifier and the second user identifier into the binding relationship between the first user identifier and the third user identifier according to the third user identifier in the binding message; if the binding message is not in the validity period, the server does not need to update the binding relationship between the user identifications, that is, the server can continue to maintain the binding relationship between the first user identification and the second user identification.
The present specification also provides another embodiment of a user registration method based on the same concept as the embodiment shown in fig. 1. Referring to fig. 7, a flowchart of another user registration method according to an exemplary embodiment of the present disclosure is shown. The method can be applied to a second client, and comprises the following steps:
step 701: and jumping to the assistance registration interface in response to a second user-initiated image scanning operation on the graphical code output on the first client of the first user.
Step 702: acquiring registration information input by the second user in the assisted registration interface; wherein the registration information includes a security policy configured for the registered account by the second user.
Step 703: and initiating account registration for the first user to a server based on the acquired registration information.
In this embodiment, the first user, the first client, the second user, and the second client may refer to the description in the foregoing embodiments, and are not repeated here.
In this embodiment, the first client may output a graphical code for the first user upon detecting the assisted registration operation initiated by the first user. The graphic code may specifically include a graphic code in the form of a two-dimensional code or a barcode.
For example, referring to fig. 3, after the first user triggers the assisted registration button 31 in the login interface shown in fig. 3, the first client may be regarded as detecting the assisted registration operation initiated by the first user, so that the graphic code for the first user may be output.
In a user interface output by the second client to the second user, a scan portal may be provided. The second user may scan the graphical code output on the first client through the scan portal. When detecting a scanning operation performed by the second user through the scanning entry for the graphic code output on the first client, the second client may jump to an assistance registration interface (the assistance registration interface shown in fig. 5), that is, output the assistance registration interface to the second user. The second user may complete the payment account registration for the first user through the assisted registration interface.
In one embodiment shown, the encoded information carried in the graphical code output on the first client may include the URL address of the assisted registration interface. When detecting that the second user performs a scanning operation on the graphic code output on the first client through the scanning entry, the second client may parse the scanned graphic code, so as to obtain the URL address of the assistance registration interface.
Subsequently, the second client may jump to the assisted registration interface based on the URL address of the assisted registration interface, so that the second user may complete the payment account registration for the first user through the assisted registration interface.
In one embodiment, the encoded information carried in the graphical code output on the first client may include a first user identifier of the first user in addition to the URL address of the assisted registration interface. When detecting that the second user performs a scanning operation on the graphic code output on the first client through the scanning entry, the second client may parse the scanned graphic code, so as to obtain the URL address of the assistance registration interface and the first user identifier.
Subsequently, on one hand, the second client can jump to the assisted registration interface based on the URL address of the assisted registration interface, so that the second user can complete the payment account registration for the first user through the assisted registration interface; on the other hand, after jumping to the assistance registration interface, the second client may display the first user identifier to the second user through the assistance registration interface.
For example, with continued reference to fig. 5, after jumping to the assistance registration interface shown in fig. 5, the second client may directly present the first user identifier in the text input option 51 for the second user to view, so that the second user may confirm the first user who needs assistance to complete the payment account registration.
In practical application, the first user identifier may be carried in a URL address of the assistance registration interface as a URL parameter; for example, the first user identification may be stitched as a URL parameter into a string of URL addresses of the assistance registration interface. In this case, after the second client parses the URL address of the assisted registration interface from the scanned graphic code, the first user identifier carried in the URL address may be further read, so that the first user identifier may be displayed in the assisted registration interface.
After the second client outputs the assisted registration interface to the second user, the second user may input registration information in the assisted registration page. The registration information may include a payment security policy configured for the payment account by the second user, and may also include an account name and an account login password of the payment account that the second user assists the first user in registering.
After acquiring the registration information input by the second user in the assisted registration interface, the second client may initiate account registration for the first user to the server based on the registration information.
Specifically, the implementation of steps 702 and 703 may refer to the description in the foregoing embodiments, and details are not repeated here.
In the technical scheme, the third-party user can assist some user groups which cannot finish account registration to finish account registration, and the third-party user configures a security policy for the registered account, so that the account registration process can be simplified, some user groups which cannot finish account registration can also finish account registration conveniently through the client.
Corresponding to the embodiment of the user registration method, the specification also provides an embodiment of a user registration device.
The embodiment of the user registration device in the specification can be applied to electronic equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is formed by reading, by a processor of the electronic device where the device is located, a corresponding computer program instruction in the nonvolatile memory into the memory for operation. From a hardware aspect, as shown in fig. 8, the hardware structure diagram of the electronic device where the user registration apparatus is located in this specification is shown, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 8, the electronic device where the apparatus is located in the embodiment may also include other hardware according to an actual function of the electronic device, which is not described again.
Referring to fig. 9, fig. 9 is a block diagram of a user registration apparatus according to an exemplary embodiment of the present disclosure. The apparatus 900 may be applied to the electronic device shown in fig. 8, and includes:
an output module 901, configured to output an assisted registration interface to a first user in response to an assisted registration operation initiated by the first user;
a first obtaining module 902, configured to obtain a second user identifier of a second user, which is input in the assistance registration interface by the first user;
a first sending module 903, configured to send, through a server, an assisted registration message to a second client corresponding to the second user identifier, where the assisted registration message includes the first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and configures a payment security policy for a registered account.
In this embodiment, the apparatus 900 may further include:
a receiving module 904, configured to receive a registration result returned by the server; the registration result comprises a first user identification which is an account name and an account login password which is set for the first user on the second client by the second user;
a display module 905, configured to display the registration result through the assisted registration interface.
In this embodiment, the apparatus 900 may further include:
a login module 906, configured to automatically perform login based on the account name and the account login password in the registration result.
In this embodiment, the first client includes a voice input option;
the first obtaining module 902 may specifically be configured to:
responding to the triggering operation of the first user for the voice input option, and acquiring a voice instruction input by the first user;
and analyzing the voice command to acquire a second user identifier of a second user input by the first user.
In this embodiment, the account is a payment account; the security policy is a payment security policy;
the payment security policy comprises any one or a combination of more of:
maximum limit for single payment;
pay exemption scenario.
In this embodiment, the server maintains a binding relationship between the first user identifier and the second user identifier;
the apparatus 900 may further include:
a second obtaining module 907, configured to obtain, in response to a user binding update operation of the first user, a third user identifier of a third user specified by the first user;
a second sending module 908, configured to send the third user identifier to the server, so that the server updates the binding relationship between the first user identifier and the second user identifier to the binding relationship between the first user identifier and the third user identifier.
In this embodiment, the second obtaining module 907 may be specifically configured to:
acquiring a third user identification of a third user input by the first user; alternatively, the first and second electrodes may be,
and responding to the scanning operation of the first user on the graphic code generated based on the third user identification of the third user, analyzing the graphic code, and acquiring the third user identification of the third user.
In this embodiment, the first user identifier and the second user identifier include mobile phone numbers.
In this embodiment, the user interface of the first client is a simple interface composed of a scan entry and a payment code entry.
The present specification also provides another embodiment of a user registration apparatus based on the same concept as the embodiment shown in fig. 9. Referring to fig. 10, fig. 10 is a block diagram illustrating another user registration apparatus according to an exemplary embodiment of the present disclosure. The apparatus 1000 may also be applied to the electronic device shown in fig. 8, including:
a skip module 1001, configured to skip to an assistance registration interface in response to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user;
an obtaining module 1002, configured to obtain registration information input by the second user in the assisted registration interface; wherein the registration information includes a security policy configured for the registered account by the second user;
a registration module 1003, configured to initiate account registration for the first user to a server based on the acquired registration information.
In this embodiment, the encoding information carried in the graphic code includes a URL address of the assisted registration interface;
the skip module 1001 may be specifically configured to:
in response to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, analyzing the graphic code to acquire a URL (uniform resource locator) address of the assisted registration interface;
and jumping to the assistant registration interface based on the acquired URL address.
In this embodiment, the encoding information carried in the graphic code further includes a first user identifier of the first user;
the apparatus 1000 may further comprise:
the analyzing module 1004 is configured to analyze the graphic code to obtain a first user identifier of the first user;
a displaying module 1005, configured to display the first user identifier through the assistance registration interface.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
The systems, devices, modules or modules illustrated in the above embodiments may be implemented by a computer chip or an entity, or by an article of manufacture with certain functionality. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
Corresponding to the embodiment of the user registration method, the specification further provides an embodiment of an electronic device. The electronic device includes: a processor and a memory for storing machine executable instructions; wherein the processor and the memory are typically interconnected by an internal bus. In other possible implementations, the device may also include an external interface to enable communication with other devices or components.
In this embodiment, the processor is caused to:
responding to an assisted registration operation initiated by a first user, and outputting an assisted registration interface to the first user;
acquiring a second user identifier of a second user, which is input in the assistance registration interface by the first user;
sending an assistance registration message to a second client corresponding to the second user identifier through a server, wherein the assistance registration message comprises the first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and configures a payment security policy for the registered account.
In this embodiment, the processor is further caused to:
receiving a registration result returned by the server; the registration result comprises a first user identification which is an account name and an account login password which is set for the first user on the second client by the second user;
and displaying the registration result through the assistant registration interface.
In this embodiment, the processor is further caused to:
and automatically executing login based on the account name and the account login password in the registration result.
In this embodiment, the first client includes a voice input option;
by reading and executing machine-executable instructions stored by the memory that correspond to user-registered control logic, the processor is caused to:
responding to the triggering operation of the first user for the voice input option, and acquiring a voice instruction input by the first user;
and analyzing the voice command to acquire a second user identifier of a second user input by the first user.
In this embodiment, the server maintains a binding relationship between the first user identifier and the second user identifier;
by reading and executing machine-executable instructions stored by the memory that correspond to user-registered control logic, the processor is further caused to:
responding to the user binding updating operation of the first user, and acquiring a third user identifier of a third user specified by the first user;
and sending the third user identifier to the server, so that the server updates the binding relationship between the first user identifier and the second user identifier into the binding relationship between the first user identifier and the third user identifier.
In this embodiment, the processor is caused to:
acquiring a third user identification of a third user input by the first user; alternatively, the first and second electrodes may be,
and responding to the scanning operation of the first user on the graphic code generated based on the third user identification of the third user, analyzing the graphic code, and acquiring the third user identification of the third user.
The present specification also provides another embodiment of an electronic device based on the same concept as the above-described embodiments of the electronic device.
In this embodiment, the processor is caused to:
responding to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, and jumping to an assistance registration interface;
acquiring registration information input by the second user in the assisted registration interface; wherein the registration information includes a security policy configured for the registered account by the second user;
and initiating account registration for the first user to a server based on the acquired registration information.
In this embodiment, the encoding information carried in the graphic code includes a URL address of the assisted registration interface;
by reading and executing machine-executable instructions stored by the memory that correspond to user-registered control logic, the processor is caused to:
in response to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, analyzing the graphic code to acquire a URL (uniform resource locator) address of the assisted registration interface;
and jumping to the assistant registration interface based on the acquired URL address.
In this embodiment, the encoding information carried in the graphic code further includes a first user identifier of the first user;
by reading and executing machine-executable instructions stored by the memory that correspond to user-registered control logic, the processor is further caused to:
analyzing the graphic code to obtain a first user identifier of the first user;
and displaying the first user identification through the assistant registration interface.
Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (24)
1. A user registration method, applied to a first client, the method comprising:
responding to an assisted registration operation initiated by a first user, and outputting an assisted registration interface to the first user;
acquiring a second user identifier of a second user, which is input in the assistance registration interface by the first user;
sending an assistance registration message to a second client corresponding to the second user identifier through a server, wherein the assistance registration message comprises the first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and configures a payment security policy for the registered account;
wherein the account is a payment account; the payment security policy comprises any one or a combination of more of: maximum limit for single payment; pay exemption scenario.
2. The method of claim 1, further comprising:
receiving a registration result returned by the server; the registration result comprises a first user identification which is an account name and an account login password which is set for the first user on the second client by the second user;
and displaying the registration result through the assistant registration interface.
3. The method of claim 2, further comprising:
and automatically executing login based on the account name and the account login password in the registration result.
4. The method of claim 1, wherein the first client includes a voice input option;
the acquiring a second user identifier of a second user input by the first user in the assistance registration interface includes:
responding to the triggering operation of the first user for the voice input option, and acquiring a voice instruction input by the first user;
and analyzing the voice command to acquire a second user identifier of a second user input by the first user.
5. The method according to claim 1, wherein the server maintains a binding relationship between the first subscriber identity and the second subscriber identity;
the method further comprises the following steps:
responding to the user binding updating operation of the first user, and acquiring a third user identifier of a third user specified by the first user;
and sending the third user identifier to the server, so that the server updates the binding relationship between the first user identifier and the second user identifier into the binding relationship between the first user identifier and the third user identifier.
6. The method of claim 5, wherein obtaining a third user identification of a third user specified by the first user comprises:
acquiring a third user identification of a third user input by the first user; alternatively, the first and second electrodes may be,
and responding to the scanning operation of the first user on the graphic code generated based on the third user identification of the third user, analyzing the graphic code, and acquiring the third user identification of the third user.
7. The method of claim 1, wherein the first subscriber identity and the second subscriber identity comprise mobile phone numbers.
8. The method of claim 1, wherein the user interface of the first client is a simplified interface comprising a scan portal and a pay code portal.
9. A user registration method applied to a second client, the method comprising:
responding to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, and jumping to an assistance registration interface;
acquiring registration information input by the second user in the assisted registration interface; wherein the registration information includes a payment security policy configured by the second user for the registered account;
initiating account registration for the first user to a server based on the acquired registration information;
wherein the account is a payment account; the payment security policy comprises any one or a combination of more of: maximum limit for single payment; pay exemption scenario.
10. The method of claim 9, wherein the encoded information carried in the graphical code includes a URL address of the assisted registration interface;
the jumping to a help registration interface in response to a second user initiated image scanning operation on a graphical code output on a first client of a first user comprises:
in response to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, analyzing the graphic code to acquire a URL (uniform resource locator) address of the assisted registration interface;
and jumping to the assistant registration interface based on the acquired URL address.
11. The method of claim 10, wherein the encoded information carried in the graphical code further comprises a first user identification of the first user;
the method further comprises the following steps:
analyzing the graphic code to obtain a first user identifier of the first user;
and displaying the first user identification through the assistant registration interface.
12. A user registration apparatus, applied to a first client, the apparatus comprising:
the output module is used for responding to assisted registration operation initiated by a first user and outputting an assisted registration interface to the first user;
the first acquisition module is used for acquiring a second user identifier of a second user, which is input in the assistance registration interface by the first user;
a first sending module, configured to send, through a server, an assistance registration message to a second client corresponding to the second user identifier, where the assistance registration message includes a first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and configures a payment security policy for a registered account;
wherein the account is a payment account; the payment security policy comprises any one or a combination of more of: maximum limit for single payment; pay exemption scenario.
13. The apparatus of claim 12, further comprising:
the receiving module is used for receiving the registration result returned by the server; the registration result comprises a first user identification which is an account name and an account login password which is set for the first user on the second client by the second user;
and the display module is used for displaying the registration result through the assisted registration interface.
14. The apparatus of claim 13, further comprising:
and the login module is used for automatically executing login based on the account name and the account login password in the registration result.
15. The apparatus of claim 12, wherein the first client comprises a voice input option;
the first obtaining module is specifically configured to:
responding to the triggering operation of the first user for the voice input option, and acquiring a voice instruction input by the first user;
and analyzing the voice command to acquire a second user identifier of a second user input by the first user.
16. The apparatus according to claim 12, wherein the server maintains a binding relationship between the first subscriber identity and the second subscriber identity;
the device further comprises:
a second obtaining module, configured to obtain, in response to a user binding update operation of the first user, a third user identifier of a third user specified by the first user;
and the second sending module is used for sending the third user identifier to the server so that the server updates the binding relationship between the first user identifier and the second user identifier into the binding relationship between the first user identifier and the third user identifier.
17. The apparatus of claim 16, wherein the second obtaining module is specifically configured to:
acquiring a third user identification of a third user input by the first user; alternatively, the first and second electrodes may be,
and responding to the scanning operation of the first user on the graphic code generated based on the third user identification of the third user, analyzing the graphic code, and acquiring the third user identification of the third user.
18. The apparatus of claim 12, wherein the first subscriber identity and the second subscriber identity comprise mobile phone numbers.
19. The apparatus of claim 12, wherein the user interface of the first client is a simplified interface comprising a scan portal and a pay code portal.
20. A user registration apparatus, applied to a second client, the apparatus comprising:
the skip module is used for responding to image scanning operation initiated by a second user on the graphic code output on the first client of the first user and skipping to the assisted registration interface;
the acquisition module is used for acquiring the registration information input by the second user in the assisted registration interface; wherein the registration information includes a payment security policy configured by the second user for the registered account;
the registration module is used for initiating account registration for the first user to a server side based on the acquired registration information;
wherein the account is a payment account; the payment security policy comprises any one or a combination of more of: maximum limit for single payment; pay exemption scenario.
21. The apparatus of claim 20, wherein the encoded information carried in the graphical code includes a URL address of the assisted registration interface;
the skip module is specifically configured to:
in response to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, analyzing the graphic code to acquire a URL (uniform resource locator) address of the assisted registration interface;
and jumping to the assistant registration interface based on the acquired URL address.
22. The apparatus of claim 21, wherein the encoded information carried in the graphical code further comprises a first user identification of the first user;
the device further comprises:
the analysis module is used for analyzing the graphic code to obtain a first user identifier of the first user;
and the display module is used for displaying the first user identification through the assistant registration interface.
23. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing machine executable instructions;
wherein, by reading and executing machine-executable instructions stored by the memory that correspond to user-registered control logic, the processor is caused to:
responding to an assisted registration operation initiated by a first user, and outputting an assisted registration interface to the first user;
acquiring a second user identifier of a second user, which is input in the assistance registration interface by the first user;
sending an assistance registration message to a second client corresponding to the second user identifier through a server, wherein the assistance registration message comprises the first user identifier of the first user, so that the second user completes account registration for the first user on the second client based on the first user identifier, and configures a payment security policy for the registered account;
wherein the account is a payment account; the payment security policy comprises any one or a combination of more of: maximum limit for single payment; pay exemption scenario.
24. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing machine executable instructions;
wherein, by reading and executing machine-executable instructions stored by the memory that correspond to user-registered control logic, the processor is caused to:
responding to an image scanning operation initiated by a second user on a graphic code output on a first client of a first user, and jumping to an assistance registration interface;
acquiring registration information input by the second user in the assisted registration interface; wherein the registration information includes a payment security policy configured by the second user for the registered account;
initiating account registration for the first user to a server based on the acquired registration information;
wherein the account is a payment account; the payment security policy comprises any one or a combination of more of: maximum limit for single payment; pay exemption scenario.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810829785.1A CN109040049B (en) | 2018-07-25 | 2018-07-25 | User registration method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810829785.1A CN109040049B (en) | 2018-07-25 | 2018-07-25 | User registration method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109040049A CN109040049A (en) | 2018-12-18 |
| CN109040049B true CN109040049B (en) | 2021-02-26 |
Family
ID=64645432
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810829785.1A Active CN109040049B (en) | 2018-07-25 | 2018-07-25 | User registration method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109040049B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109828819A (en) * | 2019-02-16 | 2019-05-31 | 深圳市技达信息技术有限公司 | The method of the long-range display client of binding and long-range display server-side |
| CN109961793B (en) * | 2019-02-20 | 2021-04-27 | 北京小米移动软件有限公司 | Method and device for processing voice information |
| CN116681445A (en) * | 2020-08-31 | 2023-09-01 | 支付宝（中国）网络技术有限公司 | Payment processing method, device and system |
| CN113852777A (en) * | 2021-11-29 | 2021-12-28 | 见面(天津)网络科技有限公司 | Method, device, equipment and storage medium for home group quick call |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105450648A (en) * | 2015-12-02 | 2016-03-30 | 上海斐讯数据通信技术有限公司 | Shopping assistance method of intelligent terminal and intelligent terminal |
| CN105608569A (en) * | 2014-11-24 | 2016-05-25 | 阿里巴巴集团控股有限公司 | Paying-for-another method based on payment platform and payment platform |
| CN105657634A (en) * | 2014-11-13 | 2016-06-08 | 中兴通讯股份有限公司 | Method, business assistance server, device and system for realizing remote assistance between terminals |
| CN107196909A (en) * | 2017-04-14 | 2017-09-22 | 阿里巴巴集团控股有限公司 | Invitation registration method and device |
| CN108063806A (en) * | 2017-12-11 | 2018-05-22 | 北京小米移动软件有限公司 | Long-range control method and remote control apparatus |
| CN108076079A (en) * | 2016-11-09 | 2018-05-25 | 阿里巴巴集团控股有限公司 | A kind of user information obtains system, method and device |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150052253A1 (en) * | 2014-09-22 | 2015-02-19 | Weaved, Inc. | Multi-server fractional subdomain dns protocol |
| US9367367B2 (en) * | 2013-06-06 | 2016-06-14 | Avaya Inc. | Application router |
-
2018
- 2018-07-25 CN CN201810829785.1A patent/CN109040049B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105657634A (en) * | 2014-11-13 | 2016-06-08 | 中兴通讯股份有限公司 | Method, business assistance server, device and system for realizing remote assistance between terminals |
| CN105608569A (en) * | 2014-11-24 | 2016-05-25 | 阿里巴巴集团控股有限公司 | Paying-for-another method based on payment platform and payment platform |
| CN105450648A (en) * | 2015-12-02 | 2016-03-30 | 上海斐讯数据通信技术有限公司 | Shopping assistance method of intelligent terminal and intelligent terminal |
| CN108076079A (en) * | 2016-11-09 | 2018-05-25 | 阿里巴巴集团控股有限公司 | A kind of user information obtains system, method and device |
| CN107196909A (en) * | 2017-04-14 | 2017-09-22 | 阿里巴巴集团控股有限公司 | Invitation registration method and device |
| CN108063806A (en) * | 2017-12-11 | 2018-05-22 | 北京小米移动软件有限公司 | Long-range control method and remote control apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109040049A (en) | 2018-12-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109040049B (en) | User registration method and device and electronic equipment | |
| US20200244661A1 (en) | Linking Channel-Specific Systems with a User Authentication Hub to Provide Omni-Channel User Authentication | |
| US9578027B1 (en) | Multiple data store authentication | |
| US7796742B1 (en) | Systems and methods for simplified provisioning | |
| US20140136704A1 (en) | Method and system for registration or login | |
| US20130254858A1 (en) | Encoding an Authentication Session in a QR Code | |
| CN107800765B (en) | Information processing method, terminal and system | |
| CN110392054A (en) | Log in method of calibration, device, system, equipment and readable storage medium storing program for executing | |
| CN107172087A (en) | Verification method, device and storage medium based on checking mail | |
| US11257084B2 (en) | Linking channel-specific systems with a user authentication hub to provide omni-channel user authentication | |
| JP2019040557A (en) | Authentication system, authentication method, authentication device, and program | |
| CN106453245A (en) | Method and apparatus for verifying identity | |
| CN109285102B (en) | Taxi taking method and device and electronic equipment | |
| TWI777520B (en) | Calibration method and device for electronic equipment insurance | |
| JP6856146B2 (en) | Biological data registration support system, biometric data registration support method, program | |
| JP7078707B2 (en) | Information processing methods, information processing devices, programs, and information processing terminals | |
| CN108364171B (en) | Graphic code generation method, resource sending and receiving method, device and electronic equipment | |
| CN110445760A (en) | Information processing method, device, equipment and computer readable storage medium | |
| US20210266366A1 (en) | Device linking method | |
| US20130042326A1 (en) | Mobile-Device User Authentication | |
| US20140279672A1 (en) | Tools for Collecting and Managing Services-Related Information | |
| CN108111533A (en) | The registration login method and system of APP | |
| CN107395624A (en) | Information processing method and device | |
| CN112560815B (en) | File calling method, device, medium and electronic equipment | |
| CN112929835B (en) | Message notification method, device, electronic terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200929 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200929 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 190 Elgin Street, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Country or region after: Cayman Islands Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Innovative advanced technology Co.,Ltd. Country or region before: Cayman Islands |
|
| CP03 | Change of name, title or address | ||
| OL01 | Intention to license declared |