CN112738105B - Invitation registration method and device - Google Patents
Invitation registration method and device Download PDFInfo
- Publication number
- CN112738105B CN112738105B CN202011599799.2A CN202011599799A CN112738105B CN 112738105 B CN112738105 B CN 112738105B CN 202011599799 A CN202011599799 A CN 202011599799A CN 112738105 B CN112738105 B CN 112738105B
- Authority
- CN
- China
- Prior art keywords
- registration
- user
- invited
- server
- credential
- 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 44
- 238000009434 installation Methods 0.000 claims abstract description 29
- 238000012795 verification Methods 0.000 claims description 24
- 230000008569 process Effects 0.000 claims description 16
- 238000006243 chemical reaction Methods 0.000 abstract description 8
- 238000012790 confirmation Methods 0.000 description 16
- 230000004044 response Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000006870 function Effects 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
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- 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/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/108—Network architectures or network communication protocols for network security for controlling access to devices or network resources when the policy decisions are valid for a limited amount of time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
Abstract
The application provides an invitation registration method, which comprises the following steps: receiving an invitation registration request sent by a registration invitation user; wherein, the invitation registration request carries the user identification of the invited user; generating a registration credential corresponding to a user identification of the invited user and issuing the registration credential to the invited user; receiving a registration request sent by the invited user; wherein the registration request carries the registration credential; verifying the registration credentials carried in the registration request; if the authentication is passed, user registration corresponding to the invited user is initiated, and a registration success page is returned to the invited user after the registration is successful; the successful registration page comprises an installation file downloading inlet corresponding to the client which is successfully registered by the invited user. The method and the device can also improve the conversion rate of invitation registration.
Description
Technical Field
The present disclosure relates to the field of computer applications, and in particular, to an invitation registration method and apparatus.
Background
In the related art, more and more operators of client products pull potential user crowd to register and use own client products by introducing an invitation registration mechanism; for example, the operator may provide an "invite to register" portal in the client product through which registered users may initiate a registration invitation to those potential users that are not registered with the client product.
However, existing "invite registration" mechanisms, while enabling registered people to actively initiate registration invitations to those potential users, have the problem of low "conversion" of the invite registration. The potential user, upon receipt of the registration invitation, will in most cases typically ignore the registration invitation; therefore, how to promote the conversion rate of the invitation registration has great significance for enlarging the scale of the using crowd of the client product.
Disclosure of Invention
The application provides an invitation registration method which is applied to a server; the method comprises the following steps:
receiving an invitation registration request sent by a registration invitation user; wherein, the invitation registration request carries the user identification of the invited user;
generating a registration credential corresponding to a user identification of the invited user and issuing the registration credential to the invited user;
receiving a registration request sent by the invited user; wherein the registration request carries the registration credential;
verifying the registration credentials carried in the registration request; if the authentication is passed, user registration corresponding to the invited user is initiated, and a registration success page is returned to the invited user after the registration is successful; the successful registration page comprises an installation file downloading inlet corresponding to the client which is successfully registered by the invited user.
Optionally, the generating a registration credential corresponding to the user identifier of the invited user and issuing the registration credential to the invited user includes:
generating a registration credential corresponding to the user identifier of the invited user, and locally caching the corresponding relation between the registration credential and the user identifier of the invited user;
constructing a registration link carrying the registration credential;
the constructed registration link is issued to the invited user in the form of a short message, so that the invited user jumps to a corresponding registration confirmation page when accessing the registration link; wherein the registration confirmation page includes a user option for triggering the registration request.
Optionally, the locally cached registration credential presets an effective duration;
the verifying the registration credential carried in the registration request includes:
acquiring a registration credential carried in the registration request;
inquiring whether the registration credentials are cached locally;
if the registration credential is cached locally, verifying whether the registration credential has been revoked;
and if the registration certificate is not invalid, confirming that the registration certificate passes verification, and further acquiring a locally cached user identifier corresponding to the registration certificate.
Optionally, the method further comprises:
after successful registration, generating a login password for the invited user;
the generated login password is issued to the invited user in a short message mode, so that the invited user logs in the client based on the login password after the client which is successfully registered is downloaded and installed through the successful registration page; or,
and adding the generated login password into an installation file of the client which is successfully registered by the invited user, so that the invited user automatically logs in the client based on the login password added in the installation file of the client after the client which is successfully registered is downloaded and installed through the successful registration page.
Optionally, before generating the registration credential corresponding to the user identifier of the invited user, the method further includes:
verifying whether the invitation registration times of the inviting user reach a preset threshold value or not; if yes, terminating the invitation registration process; if not, continuing to generate registration credentials corresponding to the user identification of the invited user; the method comprises the steps of,
verifying whether the invited registration times of the invited user reach a preset threshold value or not; if yes, terminating the invitation registration process; if not, continuing to generate registration credentials corresponding to the user identification of the invited user.
The application also provides an invitation registering device which is applied to the server; the device comprises:
the first receiving module receives an invitation registration request sent by a registration inviting user; wherein, the invitation registration request carries the user identification of the invited user;
a issuing module for generating a registration credential corresponding to a user identifier of the invited user and issuing the registration credential to the invited user;
the second receiving module receives a registration request sent by the invited user; wherein the registration request carries the registration credential;
the registration module is used for verifying the registration credentials carried in the registration request; if the authentication is passed, user registration corresponding to the invited user is initiated, and a registration success page is returned to the invited user after the registration is successful; the successful registration page comprises an installation file downloading inlet corresponding to the client which is successfully registered by the invited user.
Optionally, the issuing module:
generating a registration credential corresponding to the user identifier of the invited user, and locally caching the corresponding relation between the registration credential and the user identifier of the invited user;
Constructing a registration link carrying the registration credential;
the constructed registration link is issued to the invited user in the form of a short message, so that the invited user jumps to a corresponding registration confirmation page when accessing the registration link; wherein the registration confirmation page includes a user option for triggering the registration request.
Optionally, the locally cached registration credential presets an effective duration;
the registration module:
acquiring a registration credential carried in the registration request;
inquiring whether the registration credentials are cached locally;
if the registration credential is cached locally, verifying whether the registration credential has been revoked;
and if the registration certificate is not invalid, confirming that the registration certificate passes verification, and further acquiring a locally cached user identifier corresponding to the registration certificate.
Optionally, the registration module further:
after successful registration, generating a login password for the invited user;
the generated login password is issued to the invited user in a short message mode, so that the invited user logs in the client based on the login password after the client which is successfully registered is downloaded and installed through the successful registration page; or,
And adding the generated login password into an installation file of the client which is successfully registered by the invited user, so that the invited user automatically logs in the client based on the login password added in the installation file of the client after the client which is successfully registered is downloaded and installed through the successful registration page.
Optionally, the issuing module further:
before generating registration credentials corresponding to a user identity of the invited user, verifying whether an inviting registration number of the inviting user reaches a preset threshold; if yes, terminating the invitation registration process; if not, continuing to generate registration credentials corresponding to the user identification of the invited user; the method comprises the steps of,
before generating registration credentials corresponding to a user identity of the invited user, verifying whether a preset threshold is reached for the invited registration number of the invited user; if yes, terminating the invitation registration process; if not, continuing to generate registration credentials corresponding to the user identification of the invited user.
In the application, when receiving an invitation registration request sent by a registration inviting user, a server side can generate a registration credential for the invited user based on a user identifier of the invited user carried by the invitation registration request, and send the registration credential to the invited user; after receiving the registration certificate issued by the server, the invited user can confirm the registration and send a registration request carrying the registration certificate to the server after confirmation; after receiving the registration request sent by the invited user, the server can verify the registration credentials carried in the registration request; when the authentication is passed, user registration for the invited user can be initiated immediately, and a registration success page containing an installation file download entrance is returned to the invited user after the registration is successful, so as to guide the invited user to download the installation file of the client with successful registration;
In the application, the invited user can trigger the server to automatically complete the registration process in the background by only carrying out simple invitation registration confirmation on the registration invitation initiated by the invited user in the complete flow of the invitation registration, and does not need to access the registration page to manually submit the related registration information to complete the registration, so that the operation complexity of the invited user party in carrying out the invitation registration can be obviously reduced, and the conversion rate of the invitation registration can be improved.
Drawings
FIG. 1 is a flow chart of an invitation registration method according to an embodiment of the present application;
FIG. 2 is a flow chart illustrating invitation registration according to an embodiment of the present application;
FIG. 3 is a flow chart illustrating one-touch registration according to one embodiment of the present application;
FIG. 4 is a logical block diagram of an invitation registering apparatus according to an embodiment of the present application;
fig. 5 is a hardware architecture diagram of an invitation registering device according to an embodiment of the present application, where the hardware architecture diagram carries a server of the invitation registering device.
Detailed Description
In the related art, when an inviting user initiates "inviting registration", as a party of an invited user, it is still generally required to access a registration page, and manually submit registration information through the registration page to complete further registration; since there is still a certain operational complexity for the invited user, the invited user is likely to completely ignore the registration invitation after receiving the registration invitation initiated by the inviting user, resulting in a problem that the conversion rate of the "invite registration" is too low.
For example, for an elderly user group, or a group that cannot autonomously complete user registration, when a registration invitation initiated by another user is received, it is likely that the registration invitation is completely ignored because it cannot complete the user registration operation by itself.
It can be seen how to reduce the complexity of the operation as a party to the invited user in completing the "invite registration" has a great significance for improving the conversion rate of the "invite registration".
In view of this, in order to simplify the complexity of operation as a party to the invited user in performing the invitation registration, the present application proposes an invitation registration scheme in which a party to the invited user can perform "one-touch" registration.
When the server receives an invitation registration request sent by a registration inviting user, the server can generate a registration credential for the invited user based on a user identifier of the invited user carried by the invitation registration request, and send the registration credential to the invited user; after receiving the registration certificate issued by the server, the invited user can confirm the registration and send a registration request carrying the registration certificate to the server after confirmation; after receiving the registration request sent by the invited user, the server can verify the registration credentials carried in the registration request; when the authentication is passed, user registration for the invited user can be initiated immediately, and a registration success page containing an installation file download entrance is returned to the invited user after the registration is successful, so as to guide the invited user to download the installation file of the client with successful registration;
In the application, the invited user can trigger the server to automatically complete the registration process in the background by only carrying out simple invitation registration confirmation on the registration invitation initiated by the invited user in the complete flow of the invitation registration without accessing a registration page and manually submitting related registration information to complete the registration, so that the operation complexity of the invited user party in carrying out the invitation registration can be obviously reduced, and the conversion rate of the invitation registration can be improved.
The following describes the present application through specific embodiments and in connection with specific application scenarios.
Referring to fig. 1, fig. 1 is a schematic diagram of an invitation registration method provided in an embodiment of the present application, which is applied to a server; the method performs the steps of:
step 101, receiving an invitation registration request sent by a registration invitation user; wherein, the invitation registration request carries the user identification of the invited user;
step 102, generating a registration credential corresponding to a user identifier of the invited user, and issuing the registration credential to the invited user;
step 103, receiving a registration request sent by the invited user; wherein the registration request carries the registration credential;
Step 104, verifying the registration credentials carried in the registration request; if the authentication is passed, user registration corresponding to the invited user is initiated, and a registration success page is returned to the invited user after the registration is successful; the successful registration page comprises an installation file downloading inlet corresponding to the client which is successfully registered by the invited user.
The client may include client software for providing a specific service to a user; for example, a Web client, or APP application;
the server may include a server, a server cluster, or a distributed service platform set up based on the server cluster, where the server provides a registration service for the client to a user.
The inviting user specifically refers to an inviting registered initiator user; the invited user specifically refers to a potential user who has a certain social relationship with the inviting user and does not complete the registration of the client.
The user identifier of the invited user specifically refers to identifier information capable of uniquely identifying the invited user; for example, in practical application, the invited user may specifically be a mobile phone number of a user that has not registered the client, which is selected from a personal address book when the inviting user initiates the inviting registration.
The following description will be given by taking the user identifier as a mobile phone number as an example; obviously, in practical application, the user identifier may be in other forms, and the user identifier information can be registered at the server; such as the social account number of the invited user.
In the present application, a user portal for initiating invitation registration may be provided for the inviting user on the client side of the inviting user.
The specific form of the user entry is not particularly limited in the present application, and may specifically be a resident function button provided in a user page of the client, or may be a dynamic page entry issued to the client by the server;
for example, taking the above client as a payment device client, in one case, in the login page of the payment device client, an "invite registration" button of a resident login page may be provided; the user may enter the subsequent "invite registration" flow by triggering the "invite registration" button. In another case, when the operator of the payment device performs operation activities of registering by some potential users under the pull line, an activity page containing an invitation registration button can be dynamically issued to the payment device client through the server; the user may enter the subsequent "invite to register" flow by triggering the "invite to register" button in the active page.
In the present application, the inviting user may trigger (e.g. click on) the "user portal" to start a subsequent "invite registration" process, and select, from an address book, an invited user who has not registered the client, and initiate invite registration for the invited user.
Referring to fig. 2, fig. 2 is a flowchart of "invite registration" shown in the present application.
As shown in fig. 2, the client side of the inviting user may monitor the triggering event of the user for the "page entry" in real time; when the triggering event of the user aiming at the user entrance is monitored, the client can access the URL address of a preconfigured registration invitation page, send a get request message corresponding to the URL address to the server based on the HTTP protocol, and request the page content of the registration invitation page to the server;
wherein, in the get request message, the URL address of the registration invitation page is carried; the UserId of the inviting user (i.e. the user ID uniformly distributed by the server after the user completes registration) can be used as a parameter to be submitted to the server to be filled into the URL address.
With continued reference to fig. 2, after receiving the get request message, the server may parse the information carried in the get request message, obtain the UserId of the inviting user, and verify whether the inviting user is in a login state based on the UserId of the inviting user.
On the one hand, if the inviting user is in a non-login state, the process of inviting registration can be directly terminated, a get response message is returned to the client of the inviting user, and a general error reporting page which is completely preconfigured by the server is returned to the client.
On the other hand, if the inviting user is in the login state, the subsequent process of inviting registration may be continued, a corresponding session is created for the inviting user, and the UserId of the inviting user is recorded in the session.
The session is used for recording registration information related to the invitation registration initiated by the inviting user. In practical application, in the session, besides recording UserId of the inviting user, other information related to the inviting registration can be recorded based on practical requirements;
in one embodiment shown, an proviteuserid attribute may be defined in the session for recording UserId of the inviting user; a context attribute may also be defined for recording the specific context of the invitation registration.
With continued reference to fig. 2, when the server side login state verifies that the inviting user is in the login state, a get response message may also be returned to the client side, and page content of the login invitation page that is preconfigured by the server side is returned to the client side;
In addition to the page content that can still carry the registration invitation page, the get response message may also fill, as a parameter, information such as a mobile phone number of the invited user that is not registered with the client and that can be currently invited by the inviting user into a URL address of the registration invitation page carried in the get response message.
For example, in one implementation, the mobile phone address book of the inviting user may be synchronized to the server in advance, and stored in association with the UserId of the inviting user on the server. After analyzing the get request message sent by the client of the inviting user and obtaining the UserId of the inviting user, the server can extract the mobile phone address book of the inviting user, then traverse the contacts one by one, find out the contacts which are not registered with the client in the mobile phone address book, and fill the mobile phone numbers of the found contacts which are not registered with the client into the get response message.
With continued reference to fig. 2, after receiving the get response message returned by the server, the client of the inviting user may parse the information carried in the get response message, obtain the page content of the registration invitation page and the mobile phone number of the invited user, and then render the registration invitation page based on the page content of the registration invitation page returned by the server, and add the mobile phone number of the invited user returned by the server to the registration invitation page, and display the same to the inviting user.
Further, after the rendering of the registration invitation page is completed, the inviting user may select an invited user in the registration invitation page, then send a post request message (i.e. the invitation registration request) corresponding to the URL address of the registration invitation page to the server based on the HTTP protocol, submit the mobile phone number of the selected invited user to the server, and perform relevant invitation registration verification by the server.
With continued reference to fig. 2, after receiving the post request message, the server may parse the information carried in the post request message to obtain the mobile phone number of the invited user carried in the post request message, and then perform related verification on the mobile phone number of the invited user.
It should be noted that, for a certain user, registration invitations are frequently initiated to other users; or, the user experience is affected to some extent by frequently receiving registration invitations initiated by other users; thus, in the present application, the verification performed for the mobile phone number of the invited user may specifically include verification of the number of invitations registration initiated by the inviting user and the number of invitations registration of the invited user.
When the method is implemented, the server can count the number of times of invitation registration actively initiated by a user and the number of times of invited registration received by the user in the background, respectively preset a tolerance threshold for the number of times of invitation registration and the number of times of invited registration, and control the number of times of invitation registration and the number of times of invited registration through the preset tolerance threshold so as to terminate the invitation registration process in time when the number of times of invitation registration and the number of times of invited registration reach the tolerance threshold, thereby preventing frequent requests from harassment to the user.
In practical applications, the tolerance threshold value preset for the number of invitations and registrations may be the same or different, and is not particularly limited in the present application.
With continued reference to fig. 2, after receiving the client of the inviting user and the mobile phone number of the invited user submitted by the post request message, the server may further verify whether the number of inviting registrations of the inviting user and the number of invited registrations of the invited user reach a preset tolerance threshold;
On the one hand, if any one of the number of the inviting registration and the number of the invited registration reaches the tolerance threshold, the inviting registration process can be directly terminated, a post response message is returned to the client of the inviting user, and a general error reporting page which is preconfigured by the server is returned to the client so as to prompt the inviting user that the inviting registration initiated by the current time fails.
On the other hand, if the number of inviting registrations and the number of invited registrations do not reach the preset threshold, the server may continue to execute a subsequent inviting registration procedure.
Note that, when verifying whether or not the number of invitations and the number of invitees registered reach the tolerance threshold, the specific verification procedure of the number of invitations and the number of invitees registered is not particularly limited in the present application.
Of course, in practical applications, the verification performed on the mobile phone number of the invited user may include verification of whether the number of times of registration of the invitation and the number of times of registration of the invited user reach the tolerance threshold, and may further include verification of whether the format of the mobile phone number of the invited user is correct, whether the mobile phone number of the invited user is available for registration, or other types of verification operations, which are not listed one by one in the present application, and when the technical solution of the present application is put into practice, a person skilled in the art may freely define and add corresponding verification operations based on actual requirements.
With continued reference to fig. 2, after the mobile phone number of the invited user passes the above-described authentication, the mobile phone number of the invited user may also be recorded into the session created for the inviting user,
a post response message is returned to the client of the inviting user, and an inviting confirmation page which is pre-configured by the server is returned to the client of the inviting user;
wherein in the invitation confirmation page, a user option for triggering invitation registration confirmation may be provided in particular. When the user option is triggered by the inviting user, the client of the inviting user may further return a post request message for confirming the inviting registration to the server. At this time, the session created by the server side has cached information such as UserId of the inviting user and mobile phone number of the invited user, so the post request message returned by the inviting user may not carry any parameter.
After the server receives the post request message for confirming the invitation registration returned by the client of the inviting user, the server can read the information recorded in the session at the moment and execute the related verification again for the mobile phone number of the invited user based on the information recorded in the session; for example, the above-described various verifications such as verification that the number of invitations registration and whether the number of invites registration reaches the preset tolerance threshold are performed again, and will not be repeated.
With continued reference to fig. 2, after the mobile phone number of the invited user passes the above-described various authentications again, a corresponding Token credential (i.e., the registration credential) may be generated for the invited user, and a valid duration may be set for the Token credential, and then the Token credential and the mobile phone number of the invited user recorded in the session are cached in a designated storage space; wherein, the designated storage space is different from the storage space corresponding to the session;
for example, in one embodiment, the Token credential may be used as a key, the mobile phone number of the invited user recorded in the session may be used as a Value, and the correspondence between the two may be cached in the TAIR storage system carried by the server in a form of key+value.
The Token credential may be a calculated unique character string.
For example, in one embodiment, taking the server as a distributed server cluster as an example, the registration credential may specifically be a Token credential generated based on a UUID (identifier for uniquely identifying a device in a distributed system) and a timestamp.
Of course, in practical applications, the calculation parameters used in generating Token credentials may also include other parameters with uniqueness, which are not particularly limited in this application.
With continued reference to fig. 2, after the server generates a corresponding registration credential for the invited user, the Token credential may be used as a transfer parameter to splice with a URL address of a registration page to construct a URL link for registration, and then the constructed URL link is converted into a short link suitable for sending through a short message, and sent to the invited user in a form of a mobile phone short message.
For example, taking the registration page as the registration page of the payment device as an example, the URL link constructed may be in the following format:
https://memberprod.alipay.com/account/h5/invitedoreg.htmtoken＝{token}。
when the server side successfully transmits the mobile phone short message to the invited user, a post response message can be returned to the client side of the invited user, and a short message transmission success page which is preconfigured by the server side is returned to the client side so as to prompt the invited user that the short message transmission is successful.
After the URL link is successfully issued to the invited user through the mobile phone short message:
on the one hand, the server side can generate a log stream file related to the current mobile phone short message sending in the background, then clear the session, count the number of times of invitation registration initiated by the inviting user and the number of times of invited registration of the invited user and update the number of times of invited registration;
On the other hand, the server side can return a post response message to the client side of the inviting user, and return a successful message issuing page of the pre-configured short message of the server side to the client side so as to inform the inviting user that the short message issuing is successful.
When the invited user receives the mobile phone short message carrying the URL link, the invited user can finish one-key registration by clicking the URL link.
Referring to fig. 3, fig. 3 is a flowchart of "one-touch registration" shown in this example.
As shown in fig. 3, after the invited user "clicks" the URL link of the registration page carried in the mobile phone short message, the invited user may jump to the URL link through the browser, and send a get request message (i.e. the registration request) corresponding to the URL link to the server based on the HTTP protocol;
wherein, in the get request message, the URL address carrying the registration page and Token credential filled in the URL address as parameters will be carried. After the server receives the get request message, the server can analyze the information carried in the get request message to obtain the Token credential, and then verify the obtained Token credential.
Specifically, after the server side obtains the Token credential, the server side can use the Token credential as a query key to query the mobile phone number of the invited user corresponding to the Token credential from a local TAIR system; the valid time length is preset because of the Token credential cached in the TAIR system, and the server can verify whether the valid time length of the Token credential is overtime or not;
On the one hand, if the validity period of the Token credential has timed out, which indicates that the Token credential has exceeded the validity period, in this case, the server may return a get response message to the browser of the invited user, and return the invite expiration page that the server has been preconfigured to the invited user.
On the other hand, if the valid duration of the Token credential is not timed out, it indicates that the Token credential is still valid, and the server can normally read the cached mobile phone number of the invited user corresponding to the Token credential from the TAIR system.
In this case, it indicates that the invited user can complete the subsequent user registration procedure, and the server may return a get response message to the browser of the invited user, and return the registration page that the server pre-configures to be completed to the client of the invited user.
Wherein, in the above-mentioned registration confirmation page, a user option for triggering registration confirmation may be provided; after triggering the user option, the invited user can send a post request message for confirming registration to the server through the browser. At this time, the server has already cached the corresponding relationship between the mobile phone number of the inviting user and the Token credential locally, so the post request message returned by the inviting user may not carry any parameter.
After the server receives the post request message for confirming the registration returned by the client of the inviting user, the user registration for the client can be initiated based on the mobile phone number of the invited user acquired from the TAIR system.
In one aspect, after registration is completed based on the mobile phone number of the invited user, the server may return a post response message to the browser of the invited user, and return a registration success page that is preconfigured by the server to the browser of the invited user, so as to prompt that registration of the invited user is completed.
In the successful registration page, a download portal for downloading the installation file of the registered client may be provided, so that the invited user may quickly complete the downloading and installation of the installation file of the registered client through the download portal.
On the other hand, after the registration is completed based on the mobile phone number of the invited user, the server may randomly generate a login password for the invited user in the background, and then issue the login password to the invited user.
With continued reference to fig. 3, in an embodiment shown, the server may enable a dynamic packaging mechanism of an installation file, and add login passwords generated for different invited users to the installation file of the client that the invited users register successfully, so as to implement dynamic packaging.
In this way, the server can generate personalized installation files for different invited users respectively. After the invited user finishes downloading and installing the installation file based on the downloading port, the invited user can execute automatic login based on the login password packaged and completed in the installation file without manually inputting the registered mobile phone number and the login password to finish login, so that one-key registration and one-key login of the invited user can be truly realized, and the registration experience of the invited user can be remarkably improved.
Of course, in practical application, the server side may also issue the generated login password to the invited user in the form of a short message, so that the invited user can complete login by manually inputting the mobile phone number and the login password after the invited user successfully downloads and installs the client side with successful registration through the download port.
Therefore, in the application, as one party of the invited user, the one-key registration can be completed only by performing one registration confirmation in the complete process of the invitation registration, so that the operation complexity of the invited user in the process of the invitation registration can be remarkably reduced.
In addition, it should be emphasized that in the above embodiments, the technical solutions of the present application are described in detail in a general message interaction manner based on the http protocol.
Obviously, in practical application, other forms of message interaction modes besides http protocol can be adopted between the server and the client, which are not listed in the present application.
According to the embodiments, when receiving an invitation registration request sent by a registration inviting user, a server side can generate a registration credential for the invited user based on a user identifier of the invited user carried by the invitation registration request, and send the registration credential to the invited user; after receiving the registration certificate issued by the server, the invited user can confirm the registration and send a registration request carrying the registration certificate to the server after confirmation; after receiving the registration request sent by the invited user, the server can verify the registration credentials carried in the registration request; when the authentication is passed, user registration for the invited user can be initiated immediately, and a registration success page containing an installation file download entrance is returned to the invited user after the registration is successful, so as to guide the invited user to download the installation file of the client with successful registration;
In the application, the invited user can trigger the server to automatically complete the registration process in the background by only carrying out simple invitation registration confirmation on the registration invitation initiated by the invited user in the complete flow of the invitation registration, and does not need to access the registration page to manually submit the related registration information to complete the registration, so that the operation complexity of the invited user party in carrying out the invitation registration can be obviously reduced, and the conversion rate of the invitation registration can be improved.
Corresponding to the method embodiments described above, the present application also provides embodiments of the apparatus.
Referring to fig. 4, the present application proposes an invitation registering apparatus 40 applied to a server; referring to fig. 5, the hardware architecture of the server for carrying the invitation registering device 40 generally includes a CPU, a memory, a nonvolatile memory, a network interface, an internal bus, and the like; taking a software implementation as an example, the invitation registering device 40 may be generally understood as a computer program loaded in a memory, and the logic device formed by combining software and hardware after the CPU runs, where the device 40 includes:
the first receiving module 401 receives an invite registration request sent by a registration inviting user; wherein, the invitation registration request carries the user identification of the invited user;
A issuing module 402, configured to generate a registration credential corresponding to a user identifier of the invited user, and issue the registration credential to the invited user;
a second receiving module 403, configured to receive a registration request sent by the invited user; wherein the registration request carries the registration credential;
a registration module 404, configured to verify a registration credential carried in the registration request; if the authentication is passed, user registration corresponding to the invited user is initiated, and a registration success page is returned to the invited user after the registration is successful; the successful registration page comprises an installation file downloading inlet corresponding to the client which is successfully registered by the invited user.
In this example, the issuing module 402:
generating a registration credential corresponding to the user identifier of the invited user, and locally caching the corresponding relation between the registration credential and the user identifier of the invited user;
constructing a registration link carrying the registration credential;
and sending the constructed registration link to the invited user in the form of a short message, so that the invited user sends the registration request to the server when accessing the registration link.
In this example, the locally cached registration credential presets an effective duration;
the registration module 404:
verifying whether the registration credential has been revoked;
and if the registration certificate is not invalid, confirming that the registration certificate passes verification, and further acquiring a locally cached user identifier corresponding to the registration certificate.
In this example, the registration module 404 further:
after successful registration, generating a login password for the invited user;
the generated login password is issued to the invited user in a short message mode, so that the invited user logs in the client based on the login password after the client which is successfully registered is downloaded and installed through the successful registration page; or,
and adding the generated login password into an installation file of the client which is successfully registered by the invited user, so that the invited user automatically logs in the client based on the login password added in the installation file of the client after the client which is successfully registered is downloaded and installed through the successful registration page.
In this example, the issuing module 402 further:
verifying the number of times of invitation registration of the inviting user, and whether the number of times of the invited registration of the invited user reaches a preset threshold value or not;
If any one of the number of inviting registrations and the number of invited registrations reaches the preset threshold, terminating the inviting registration flow;
and if the number of the inviting registration times and the number of the invited registration times do not reach the preset threshold, continuing to generate registration credentials corresponding to the user identification of the invited user.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
The foregoing description of the preferred embodiments of the present invention is not intended to limit the invention to the precise form disclosed, and any modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present invention are intended to be included within the scope of the present invention.
Claims (10)
1. An invitation registration method, characterized by being applied to a client corresponding to an invited user; the method comprises the following steps:
Receiving a registration link issued by a server; the registration link is constructed based on the generated registration credential corresponding to the user identifier of the invited user when the server receives the invitation registration request carrying the user identifier of the invited user sent by the registration inviting user;
sending a registration request to the server when the invited user accesses the registration link; wherein the registration request carries the registration credential;
receiving a registration success page returned by the server; the login success page comprises an installation file downloading inlet corresponding to a client which is successfully registered by the invited user; the successful registration page is a successful registration page returned after the server passes the verification of the registration credentials carried in the registration request and the user registration of the invited user is initiated; the verification process of the registration credential includes: verifying whether the registration credential is invalid; and if the registration credential does not fail, confirming that the registration credential passes verification.
2. The method of claim 1, wherein the server generates the registration credential corresponding to the user identification of the invited user by:
Generating a registration credential corresponding to the user identification of the invited user, and locally caching the corresponding relation between the registration credential and the user identification of the invited user.
3. The method of claim 2, wherein the registration credential cached in the server is preset for a valid duration;
the server verifies the registration credentials carried in the registration request by:
verifying whether the registration credential has been revoked;
and if the registration certificate is not invalid, confirming that the registration certificate passes verification, and further acquiring a locally cached user identifier corresponding to the registration certificate.
4. The method according to claim 1, wherein the method further comprises:
receiving a login password issued by the server;
after the client which is successfully registered is downloaded and installed through the successful registration page, logging in the client based on the login password; or,
after the client which is successfully registered is downloaded and installed through the page which is successfully registered, automatically logging in the client based on a login password added in an installation file of the client;
the login password is generated for the invited user after the server side is successfully registered.
5. The method of claim 1, wherein the server generates the registration credential corresponding to the user identification of the invited user by:
verifying the number of times of invitation registration of the inviting user, and whether the number of times of the invited registration of the invited user reaches a preset threshold value or not;
if any one of the number of inviting registrations and the number of invited registrations reaches the preset threshold, terminating the inviting registration flow;
and if the number of the inviting registration times and the number of the invited registration times do not reach the preset threshold, continuing to generate registration credentials corresponding to the user identification of the invited user.
6. An invitation registering apparatus, characterized by being applied to a client corresponding to an invited user; the device comprises:
the first receiving module is used for receiving a registration link issued by the server; the registration link is constructed based on the generated registration credential corresponding to the user identifier of the invited user when the server receives the invitation registration request carrying the user identifier of the invited user sent by the registration inviting user;
The sending module is used for sending a registration request to the server when the invited user accesses the registration link; wherein the registration request carries the registration credential;
the second receiving module is used for receiving a registration success page returned by the server; the login success page comprises an installation file downloading inlet corresponding to a client which is successfully registered by the invited user; the successful registration page is a successful registration page returned after the server passes the verification of the registration credentials carried in the registration request and the user registration of the invited user is initiated; the verification process of the registration credential includes: verifying whether the registration credential is invalid; and if the registration credential does not fail, confirming that the registration credential passes verification.
7. The apparatus of claim 6, wherein the server generates the registration credential corresponding to the user identification of the invited user by:
generating a registration credential corresponding to the user identification of the invited user, and locally caching the corresponding relation between the registration credential and the user identification of the invited user.
8. The apparatus of claim 7, wherein the registration credential cached in the server is pre-set for a valid duration;
the server verifies the registration credentials carried in the registration request by:
verifying whether the registration credential has been revoked;
and if the registration certificate is not invalid, confirming that the registration certificate passes verification, and further acquiring a locally cached user identifier corresponding to the registration certificate.
9. The apparatus of claim 6, wherein the apparatus further comprises:
the third receiving module is used for receiving the login password issued by the server;
the login module is used for logging in the client based on the login password after the client which is successfully registered is downloaded and installed through the successful registration page; or,
after the client which is successfully registered is downloaded and installed through the page which is successfully registered, automatically logging in the client based on a login password added in an installation file of the client;
the login password is generated for the invited user after the server side is successfully registered.
10. The apparatus of claim 6, wherein the server generates the registration credential corresponding to the user identification of the invited user by:
Verifying the number of times of invitation registration of the inviting user, and whether the number of times of the invited registration of the invited user reaches a preset threshold value or not;
if any one of the number of inviting registrations and the number of invited registrations reaches the preset threshold, terminating the inviting registration flow;
and if the number of the inviting registration times and the number of the invited registration times do not reach the preset threshold, continuing to generate registration credentials corresponding to the user identification of the invited user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011599799.2A CN112738105B (en) | 2017-04-14 | 2017-04-14 | Invitation registration method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710245189.4A CN107196909B (en) | 2017-04-14 | 2017-04-14 | Invitation registration method and device |
| CN202011599799.2A CN112738105B (en) | 2017-04-14 | 2017-04-14 | Invitation registration method and device |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710245189.4A Division CN107196909B (en) | 2017-04-14 | 2017-04-14 | Invitation registration method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112738105A CN112738105A (en) | 2021-04-30 |
| CN112738105B true CN112738105B (en) | 2024-03-15 |
Family
ID=59871977
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011599799.2A Active CN112738105B (en) | 2017-04-14 | 2017-04-14 | Invitation registration method and device |
| CN201710245189.4A Active CN107196909B (en) | 2017-04-14 | 2017-04-14 | Invitation registration method and device |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710245189.4A Active CN107196909B (en) | 2017-04-14 | 2017-04-14 | Invitation registration method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN112738105B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109040049B (en) * | 2018-07-25 | 2021-02-26 | 创新先进技术有限公司 | User registration method and device and electronic equipment |
| CN109345277A (en) * | 2018-08-13 | 2019-02-15 | 宜人恒业科技发展（北京）有限公司 | A kind of intelligent recalling system for registration failure user |
| CN110022350A (en) * | 2019-01-28 | 2019-07-16 | 阿里巴巴集团控股有限公司 | The treating method and apparatus of client registers and registration information |
| CN110222531B (en) * | 2019-05-31 | 2023-07-07 | 创新先进技术有限公司 | Method, system and equipment for accessing database |
| CN111949863A (en) * | 2020-07-20 | 2020-11-17 | 上海淇馥信息技术有限公司 | Information pushing method and device and electronic equipment |
| CN113221080A (en) * | 2021-05-21 | 2021-08-06 | 支付宝(杭州)信息技术有限公司 | Account registration processing method and device |
| CN114221795A (en) * | 2021-11-30 | 2022-03-22 | 麒麟软件有限公司 | High-concurrency registration method |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1543167A (en) * | 2002-12-02 | 2004-11-03 | ���ǵ�����ʽ���� | Terminal registration method using session initiation protocol |
| CN101697538A (en) * | 2009-10-21 | 2010-04-21 | 深圳市融创天下科技发展有限公司 | Method for quickly spreading registration among broad community of users in network system |
| CN102904900A (en) * | 2012-10-26 | 2013-01-30 | 王维国 | Method for authenticating user status for registering and/or logging in network application |
| WO2013078811A1 (en) * | 2011-11-28 | 2013-06-06 | 华为技术有限公司 | User registration method, interaction method and associated device |
| CN103747423A (en) * | 2013-12-25 | 2014-04-23 | 华为技术有限公司 | Registration method, apparatus and system of terminal application |
| CN103945009A (en) * | 2014-05-09 | 2014-07-23 | 张志强 | Software sharing method and device |
| CN104796491A (en) * | 2015-05-07 | 2015-07-22 | 北京智膜科技有限公司 | Server and software downloading and registration method based on once code-scanning |
| CN105760435A (en) * | 2016-02-02 | 2016-07-13 | 浙江慧脑信息科技有限公司 | Method for recommending fast registration through message |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050021975A1 (en) * | 2003-06-16 | 2005-01-27 | Gouping Liu | Proxy based adaptive two factor authentication having automated enrollment |
| US9230286B2 (en) * | 2008-03-14 | 2016-01-05 | Industrial Technology Research Institute | Methods and systems for associating users through network societies |
| WO2010119427A2 (en) * | 2009-04-16 | 2010-10-21 | Fireid (Proprietary) Limited | Method and system for deployment of software applications to mobile computing devices |
| US8863253B2 (en) * | 2009-06-22 | 2014-10-14 | Beyondtrust Software, Inc. | Systems and methods for automatic discovery of systems and accounts |
| US20120191861A1 (en) * | 2011-01-20 | 2012-07-26 | Cardless Technologies, Llc | Cardless Contact Information Exchange |
| US9680814B2 (en) * | 2013-12-25 | 2017-06-13 | Huawei Technologies Co., Ltd. | Method, device, and system for registering terminal application |
-
2017
- 2017-04-14 CN CN202011599799.2A patent/CN112738105B/en active Active
- 2017-04-14 CN CN201710245189.4A patent/CN107196909B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1543167A (en) * | 2002-12-02 | 2004-11-03 | ���ǵ�����ʽ���� | Terminal registration method using session initiation protocol |
| CN101697538A (en) * | 2009-10-21 | 2010-04-21 | 深圳市融创天下科技发展有限公司 | Method for quickly spreading registration among broad community of users in network system |
| WO2013078811A1 (en) * | 2011-11-28 | 2013-06-06 | 华为技术有限公司 | User registration method, interaction method and associated device |
| CN102904900A (en) * | 2012-10-26 | 2013-01-30 | 王维国 | Method for authenticating user status for registering and/or logging in network application |
| CN103747423A (en) * | 2013-12-25 | 2014-04-23 | 华为技术有限公司 | Registration method, apparatus and system of terminal application |
| CN103945009A (en) * | 2014-05-09 | 2014-07-23 | 张志强 | Software sharing method and device |
| CN104796491A (en) * | 2015-05-07 | 2015-07-22 | 北京智膜科技有限公司 | Server and software downloading and registration method based on once code-scanning |
| CN105760435A (en) * | 2016-02-02 | 2016-07-13 | 浙江慧脑信息科技有限公司 | Method for recommending fast registration through message |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107196909B (en) | 2020-11-17 |
| CN107196909A (en) | 2017-09-22 |
| CN112738105A (en) | 2021-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112738105B (en) | Invitation registration method and device | |
| US11431501B2 (en) | Coordinating access authorization across multiple systems at different mutual trust levels | |
| CN111556006B (en) | Third-party application system login method, device, terminal and SSO service platform | |
| US8892885B2 (en) | System and method for delivering a challenge response in an authentication protocol | |
| US9548975B2 (en) | Authentication method, authentication system, and service delivery server | |
| US8918853B2 (en) | Method and system for automatic recovery from lost security token on embedded device | |
| WO2019218747A1 (en) | Third party authorized login method and system | |
| US20030191964A1 (en) | Method for verifying the identity of a user for session authentication purposes during web navigation | |
| KR101451359B1 (en) | User account recovery | |
| CN109815684B (en) | Identity authentication method, system, server and storage medium | |
| WO2012120106A1 (en) | Method and system for granting access to a secured website | |
| CN103685139A (en) | Authentication and authorization processing method and device | |
| CN106161475B (en) | Method and device for realizing user authentication | |
| CN111062023B (en) | Method and device for realizing single sign-on of multi-application system | |
| CN110069909B (en) | Method and device for login of third-party system without secret | |
| CN110175448B (en) | Trusted device login authentication method and application system with authentication function | |
| CN108259457B (en) | WEB authentication method and device | |
| CN103944861A (en) | Voice verification system | |
| CN111949959B (en) | Authorization authentication method and device in Oauth protocol | |
| CN111523102A (en) | Applet login method, device, equipment and computer readable storage medium | |
| CN109784024A (en) | One kind authenticating FIDO method and system based on the polyfactorial quick online identity of more authenticators | |
| US10277579B2 (en) | Information processing system that provides a resource to an application of a terminal through a network | |
| CN108390878B (en) | Method and device for verifying network request security | |
| TWI465128B (en) | Method, system of server authentication, and a computer-readable medium | |
| CN112966242A (en) | User name and password authentication method, device and equipment and readable 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |