CN111835787A

CN111835787A - Account registration method and device, and storage medium

Info

Publication number: CN111835787A
Application number: CN202010719816.5A
Authority: CN
Inventors: 刘志健
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2020-07-23
Filing date: 2020-07-23
Publication date: 2020-10-27

Abstract

The disclosure relates to an account registration method, account registration equipment and a storage medium, and relates to the field of communication. The embodiment of the disclosure can solve the problem that in the related art, the server stores the user record which cannot be normally used, so that the storage resource in the server is wasted. The method comprises the following steps: the server receives a registration request from the client; the server sends account data and a verification prompt instruction to the client; the server receives a verification result and account data from the client; and after the short message verification of the target mobile phone number is determined to be successful according to the verification result, creating a user record of the first account, and recording account data from the client in the user record.

Description

Account registration method and device, and storage medium

Technical Field

The present disclosure relates to the field of communications, and in particular, to an account registration method and device, and a storage medium.

Background

Currently, in order to simplify the operation of a user when registering an account and provide a more convenient login channel for the user, when performing account registration in an Application (APP), a common account registration method is as follows: and finishing account registration by using account data of a second application account in a second application (namely, an application except the first application for currently registering the user account). In the method, the server may obtain account data of the second application account (for example, information such as an avatar and a user name of the second application account), and then the server creates a user record of the new account and stores the account data of the second application account in the user record. Thereby completing the registration of the new account in the first application.

With the progress of the technical level, in order to meet the requirements of the operation product of the application or the requirements of relevant national regulation and regulations, the user account is required to be bound with a mobile phone number when being registered at present.

After a user record is created in the server and account data of the second application account is recorded in the user record, if the user does not perform short message verification, a user record which cannot be normally used is stored in the server. This results in a waste of storage resources in the server.

Disclosure of Invention

The disclosure provides an account registration method, device and storage medium, which at least solve the problem that in the related art, a server stores user records which cannot be normally used, so that storage resources in the server are wasted. The technical scheme of the disclosure is as follows:

according to a first aspect of the embodiments of the present disclosure, there is provided an account registration method applied to a server, the method including: receiving a registration request from a client; the registration request is used for indicating that a first account with an association relation with a second account is registered; the first account is an account in a first application, the second account is an account in a second application, and the second application is different from the first application; responding to the registration request, accessing the second application, and acquiring account data of the second account; sending the account data and a verification prompt instruction to the client; receiving a verification result and the account data from the client; after the short message verification of the target mobile phone number is determined to be successful according to the verification result, a user record of the first account is created, and the account data from the client side is recorded in the user record; and the target mobile phone number is used for binding with the first account number.

According to the technical scheme, the user record can be created after the short message verification is successfully carried out on the target mobile phone number. The problem of memory resource waste described in the background art is avoided. Furthermore, in the disclosure, after the server acquires the account data of the second account, the server first sends the account data to the client, then performs short message verification on the target mobile phone at the client, and then sends the account data and the verification result to the server by the client, so that the server can complete registration of the first account by using the account data from the client after confirming that the short message verification is successful, and extra resource overhead for saving and searching the account data is avoided.

Optionally, the registration request carries a target authorization code; the step of responding to the registration request, accessing the second application, and acquiring account data of the second account includes: and responding to the registration request, accessing the second application, and acquiring account data of the second account by using the target authorization code. Through the above optional manner, the server may obtain the account data of the second account by using the authorization code.

Optionally, sending the account data and a verification prompt instruction to the client includes: sending a target ciphertext and the verification prompt instruction to the client; the target ciphertext comprises encrypted data obtained by encrypting the account number data; the verification prompt instruction is used for instructing the client to perform short message verification on the target mobile phone number and sending the verification result and the account number data to the server after obtaining the verification result of the short message verification on the target mobile phone number; the receiving the verification result and the account data from the client includes: receiving the verification result and the target ciphertext from the client. Through the optional mode, the confidentiality of the account data in the transmission process can be improved, and the safety of data transmission is improved.

Optionally, the target ciphertext specifically includes encrypted data obtained by encrypting the account data by using a symmetric encryption method. Through the optional mode, the data operation amount when the account data are encrypted and decrypted can be reduced on the premise of ensuring the data transmission safety.

Optionally, the verification result includes: the target mobile phone number and a verification code obtained by the client in response to an input operation; after the short message verification is successfully carried out on the target mobile phone number according to the verification result, the creating of the user record of the first account number comprises the following steps: after the short message verification of the target mobile phone number is determined to be successful according to the verification code, creating a user record of the first account; the method further comprises the following steps: and stopping registering the first account after determining that short message verification on the target mobile phone number fails according to the verification code.

Optionally, the user record further includes: and the target mobile phone number and the incidence relation between the first account and the second account.

In a second aspect, an embodiment of the present disclosure provides an account registration method, including: responding to an account registration instruction, and sending a registration request to a server; the account registration instruction is used for indicating a first account which is registered to have an association relation with a second account; the first account is an account in a first application, the second account is an account in a second application, and the second application is different from the first application; the registration request is used for indicating the server to acquire account data of the second account in the second application; receiving the account data and the verification prompt instruction from the server; responding to the verification prompt instruction, and performing short message verification on the target mobile phone number; the target mobile phone number is used for binding with the first account; and responding to an acquired verification result of short message verification on the target mobile phone number, and sending the verification result and the account number data to a server, so that the server creates a user record of the first account number after determining that the short message verification is successfully performed on the target mobile phone number according to the verification result, and records the account number data from the client in the user record.

Optionally, the registration request includes a target authorization code; the target authorization code is used for acquiring the account data in the process of accessing the second application; prior to said sending the registration request to the server, the method further comprises: and responding to an account registration instruction, and accessing the second application to obtain the target authorization code.

Through the optional mode, the existing process steps (namely the existing step that the server acquires the account data of the second account by using the authorization code) can be utilized, and the implementation difficulty of the scheme is simplified.

Optionally, the receiving the account data and the verification prompt instruction from the server includes: receiving a target ciphertext and the verification prompt instruction from the server; the target ciphertext comprises encrypted data obtained by encrypting the account number data; the step of sending the verification result and the account data to a server comprises the following steps: and sending the verification result and the target ciphertext to a server.

Through the optional mode, the confidentiality of the account data in the transmission process can be improved, and the safety of data transmission is improved.

In a third aspect, an account registration apparatus is provided, including: a receiving unit, configured to receive a registration request from a client; the registration request is used for indicating that a first account with an association relation with a second account is registered; the first account is an account in a first application, the second account is an account in a second application, and the second application is different from the first application; the data acquisition unit is used for responding to the registration request, accessing the second application and acquiring account data of the second account; the sending unit is used for sending the account data and a verification prompt instruction to the client; the receiving unit is further configured to receive a verification result and the account data from the client; the establishing unit is used for establishing a user record of the first account after the short message verification of the target mobile phone number is determined to be successful according to the verification result, and recording the account data from the client in the user record; and the target mobile phone number is used for binding with the first account number.

Optionally, the registration request carries a target authorization code; the information obtaining unit is specifically configured to respond to the registration request, access the second application, and obtain account information of the second account by using the target authorization code.

Optionally, the sending unit is specifically configured to send the target ciphertext and the verification prompt instruction to the client; the target ciphertext comprises encrypted data obtained by encrypting the account number data; the verification prompt instruction is used for instructing the client to perform short message verification on the target mobile phone number and sending the verification result and the account number data to the account number registration device after obtaining the verification result of the short message verification on the target mobile phone number; the receiving unit is specifically configured to receive the verification result and the target ciphertext from the client.

Optionally, the target ciphertext specifically includes encrypted data obtained by encrypting the account data by using a symmetric encryption method.

Optionally, the verification result includes: the target mobile phone number and a verification code obtained by the client in response to an input operation; after the short message verification is successfully carried out on the target mobile phone number according to the verification result, the creating of the user record of the first account number comprises the following steps: after the short message verification of the target mobile phone number is determined to be successful according to the verification code, creating a user record of the first account; the account registration device also comprises a registration stopping unit; and the registration stopping unit is used for stopping registering the first account after the short message verification of the target mobile phone number is determined to be failed according to the verification code.

In a fourth aspect, an account registration apparatus is provided, including: the sending unit is used for responding to the account registration instruction and sending a registration request to the server; the account registration instruction is used for indicating a first account which is registered to have an association relation with a second account; the first account is an account in a first application, the second account is an account in a second application, and the second application is different from the first application; the registration request is used for indicating the server to acquire account data of the second account in the second application; the receiving unit is used for receiving the account data and the verification prompt instruction from the server; the short message verification unit is used for responding to the verification prompt instruction and performing short message verification on the target mobile phone number; the target mobile phone number is used for binding with the first account; the sending unit is further configured to send the verification result and the account number data to a server in response to an obtained verification result of short message verification on the target mobile phone number, so that the server creates a user record of the first account number after determining that short message verification is successfully performed on the target mobile phone number according to the verification result, and records the account number data from the account number registration device in the user record.

Optionally, the registration instruction includes a target authorization code; the target authorization code is used for acquiring the account data in the process of accessing the second application; the account registration apparatus further includes: an access unit; the access unit is configured to access the second application to obtain the target authorization code in response to an account registration instruction.

Optionally, the receiving unit is specifically configured to receive a target ciphertext and the verification prompt instruction from the server; the target ciphertext comprises encrypted data obtained by encrypting the account number data; the sending unit is specifically configured to send the verification result and the target ciphertext to a server.

Optionally, the verification result includes: and the target mobile phone number and the verification code obtained by the account registration device in response to the input operation.

In a fifth aspect, a server is provided, including: a processor, a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the account registration method provided by the first aspect.

In a sixth aspect, a client is provided, including: a processor, a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the account registration method provided by the second aspect.

In a seventh aspect, a computer-readable storage medium is provided, which includes instructions, and when the instructions are executed by a processor, the processor is configured to execute the account registration method provided in the first aspect or the second aspect.

In an eighth aspect, there is provided a computer program product comprising instructions which, when executed by a processor, cause the processor to perform the account registration method provided in the first aspect or provided in the second aspect.

Exemplarily, any design manner of the third aspect to the eighth aspect may correspond to the first aspect and any possible design thereof or the second aspect and any possible design thereof, and therefore, similar technical effects can be brought, and are not described herein again.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

Fig. 1 is a network structure diagram provided in the embodiment of the present disclosure.

Fig. 2 is a schematic interface diagram of a client according to an embodiment of the present disclosure.

Fig. 3 is a flowchart illustrating an account registration method provided in the related art.

Fig. 4 is a second flowchart of an account registration method provided in the related art.

Fig. 5 is a flowchart illustrating an account registration method according to an embodiment of the present disclosure.

Fig. 6 is a second flowchart of an account registration method according to the second embodiment of the disclosure.

Fig. 7 is a third schematic flowchart of an account registration method according to the third embodiment of the present disclosure.

Fig. 8 is a fourth flowchart illustrating an account registration method according to an embodiment of the present disclosure.

Fig. 9 is a schematic structural diagram of a server according to an embodiment of the present disclosure.

Fig. 10 is a second schematic structural diagram of a server according to the second embodiment of the present disclosure.

Fig. 11 is a schematic structural diagram of a client according to an embodiment of the present disclosure.

Fig. 12 is a second schematic structural diagram of a client according to the embodiment of the disclosure.

Detailed Description

In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

First, technical terms involved in the present disclosure are introduced:

an Application (APP), also called an application program or application software, specifically refers to a software program running on a terminal device and capable of implementing a specific function.

Open Authorization (OAUTH), provides a secure, open, yet easy standard for authorization of user resources. The difference from the previous authorization method is that the authorization of OAUTH does not make the client of the third-party application (i.e. the authorized application) touch the account information (such as the user name and password) of the user, i.e. the client of the third-party application can apply for obtaining the authorization of the user resource without using the user name and password of the user. For example, in the present disclosure, when the client acquires the authorization of the third-party application through the OAUTH protocol, the client does not directly acquire account information (a user name, a password, and the like) of an account of the third-party application but acquires an authorization code. The processes of registering, logging in and the like of the target account corresponding to the third-party application account can be completed through the authorization code.

Advanced Encryption Standard (AES), also known as Rijndael Encryption method in cryptography, is a block Encryption Standard adopted by the federal government in the united states, and is the most common symmetric Encryption algorithm.

Application scenarios of the technical scheme provided by the embodiment of the present disclosure are introduced as follows:

referring to fig. 1, a schematic diagram of an implementation environment to which the technical solution provided by the embodiments of the present disclosure may be applied is shown. As shown in fig. 1, the implementation environment may include a server 101 and a plurality of clients (e.g., a client 102a, a client 102b, a client 102c, and a client 102d), which may be connected to the server 101 through a wired network or a wireless network.

For example, the client in the embodiment of the present disclosure may be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a Personal Digital Assistant (PDA), an Augmented Reality (AR) \ Virtual Reality (VR) device, and the like, and may also be a container for implementing a client-related function in the above devices. The embodiment of the present disclosure does not specifically limit the specific form of the client.

The server 101 may be a server or a server cluster, or the server may also be a container for implementing the server-related function in the server or the server cluster. The server 101 may be configured to create a user record of a target account and record related account information corresponding to the target account in the user record according to a preset manner in an account registration process, so as to register the target account in a target application. In addition, the server 101 may also be used to support the client to implement the relevant service function through the target application. For example, when the target application is a short video application, the server 101 may distribute the short video content published by a certain client to other clients so that the other clients can play the short video content.

The inventive concepts of the present disclosure are described below: in the prior art, account registration methods provided by common software are roughly divided into two types:

the first method comprises the following steps: the user manually inputs related account information (such as a user name, a password, a head portrait, a gender and the like) in a registration interface of the client, and then the client sends the account information to the server after receiving the account information input by the user. And then the server creates a user record of the first account in a database, and records the account information in the user record, thereby completing the registration process of the first account.

And the second method comprises the following steps: and completing account registration by using account information of the second application account in the second application (namely, other applications except the first application for registering the first account).

Specifically, the client may set a control in the registration interface to trigger the second application to authorize registration. Then, after the user clicks the control, the client may obtain an authorization code of the second account from the second application through the OAUTH protocol and send the authorization code to the server, so that the server obtains account information (for example, information including a head portrait, a user name, and the like of the second account) corresponding to the authorization code by accessing a system of the second application, and then the server creates a user record of the new account and stores the account information in the user record, thereby completing the registration process of the first account.

As shown in fig. 2, in the registration interface of the client, content for prompting the user to manually input account information is displayed in a first area 201. The user can complete account registration by inputting corresponding account information in the first region 201. In addition, the user may also jump to the second application by clicking the control "APP 1" or "APP 2" in the second area 202 in fig. 2, so as to obtain the authorization code of the second account. And then the second account registration method is completed.

The server stores the account data of the second account into the user record, which may specifically refer to that the server stores the account data of the second account in a database for recording account information of the first account, so as to use the account data of the second account as the account information of the first account. For example, the avatar of the second account is used as the avatar of the first account, and the user name of the second account is used as the user name of the first account. On the other hand, the server stores the account data of the second account into the user record, which may specifically mean that the server stores the account data of the second account in a preset database, so that when logging in the first account again, the first account is logged in through the second account according to the incidence relation between the first account and the second account in the preset database.

As described in the background, in some application scenarios, when registering a user account, it is also required that the user account must be bound with a mobile phone number. In order to bind a mobile phone number, in the related art, account registration is generally performed by using one of the following schemes one or two:

the first scheme is as follows: according to the technical means, a user record of a first account is created in a server, and account data of a second account is recorded after the user record. At this time, the first account is marked as the state of the unbound mobile phone number. And then the client displays an interactive interface for prompting the user to bind the mobile phone number so that the user can finish the operation of binding the mobile phone number. If the user does not bind the mobile phone number (i.e., does not complete the operation of binding the mobile phone number), the first account cannot be used normally because the first account is in a state of not binding the mobile phone number. That is, the user record for the first account created in the server at this time is useless.

Fig. 3 is a schematic flowchart illustrating an account registration method. Specifically, when the user needs to create the first account, the user may click on any of the controls in the second area 202 in fig. 2. Then, the client accesses the second application through the OAUTH protocol to obtain an authorization code of the second account (i.e., S301 in the figure), and the second application feeds back the authorization code to the client (S302); then the client initiates a three-party authorization registration process and sends an authorization code to the server (S303); then, the server accesses the second application through the authorization code to obtain account data of the second account (S304), and the second application feeds the account data of the second account back to the server (S305); the server creates a user record of a first account in a database, records account data of a second account in the user record, and marks the state that the first account is an unbound mobile phone number in the user record (S306); then the server sends a request to the client so that the client displays a prompt message to prompt the user to bind the mobile phone number (S307); then the client feeds back the target mobile phone number and the short message verification code input by the user to the server (S308); the server verifies the short message verification code (S309), and after the target mobile phone number is successfully verified, modifies the user record created in the database in the step S306, adds the target mobile phone number information in the user record and changes the first account number into the state of the bound mobile phone number (S310). Then, after the user record is successfully modified, the server sends registration success information to the client to prompt the user that the first account is successfully registered and can be used normally. And then, the user can normally log in and use the application through the first account.

In the flow of fig. 3, if after S306, the user does not complete the input of the target mobile phone number and the short message verification process according to the contents of S307 to S308, a user record corresponding to the first account that cannot be used normally is stored in the database. Then, when the user logs in the first account again, the client will start to execute from step S307 again, so that the user can normally use the first account only after completing the mobile phone number binding.

It can be seen that, in the first scheme, after the user record of the first account is created, if the process of binding the mobile phone number (i.e., S307-S310) is not continuously completed and the registration process is ended in advance, a user record corresponding to the first account that cannot be normally used is generated, and the storage resource of the database is occupied. On the other hand, the user records stored in the database may include both the user records of the user account to which the mobile phone number is bound and the user records of the user accounts to which the mobile phone number is not bound. Therefore, when data analysis is performed, if a user account with a bound mobile phone number is to be extracted from user accounts in a target application, a logic (determining whether the state of the account is the state of the bound mobile phone number) needs to be added, so that the complexity of data processing is increased.

Scheme II: the problem that the complexity of data analysis is increased due to the fact that the user accounts stored in the database possibly comprise the user accounts with the bound mobile phone numbers and the user accounts with the unbound mobile phone numbers is solved. In the second scheme, a three-party user table is established in a database, after account data of a second account is acquired by a server in the process of registering a first account, the account data of the second account is stored in the three-party user table, then after a mobile phone number binding process is completed and a target mobile phone number is successfully verified, a user record of the first account is established, the account data of the second account is read from the three-party user table, and the account data is stored in the user record.

Specifically, as shown in fig. 4, in the second scheme, the server is first enabled to obtain the account data of the second account through S401 to S405 (for specific contents of S401 to S405, reference may be made to contents of S301 to S305 in the first scheme, and details are not described here again). Then, after the server acquires the account data of the second account, the server stores the account data of the second account in the three-party user table (S406). And then, short message verification is performed on the target mobile phone number according to the contents of S407-S409 (the specific contents of S407-S409 may refer to the contents of S307-S309 in the first scheme, which is not described herein again). And then after the short message verification of the target mobile phone number is determined to be successful, the server creates a user record, reads the account data of the second account from the three-party user table, records the account data of the second account (and the target mobile phone number) in the user record (S410), and deletes the account data of the second account stored in the three-party user table.

It can be seen that in the second scheme, account data of the second account corresponding to the user account not bound with the mobile phone number is separately stored in the three-party user table, so that information of the user account not bound with the mobile phone number and user records of normal user accounts bound with the mobile phone number are separately stored, and integrity judgment logic related to the accounts is simplified. However, in the second scheme, before the target mobile phone number is successfully verified, the storage space in the database is still occupied to store the account data of the second account. In addition, in the process of creating the user record, an execution step of querying the account data of the second account in the three-party user table and then deleting the account data of the second account in the three-party user table needs to be added, and the process is still complex.

In order to solve the above problem, the present disclosure provides an account registration method, in which a client sends a registration request carrying account data of a second account to a server after obtaining a verification result of a bound mobile phone number, so that the server completes a registration process by using the account data of the second account carried in the registration request (i.e., creating a user record and recording the account data of the second account in the user record). Therefore, after the short message verification is successfully carried out on the target mobile phone number, the account registration is carried out to create the user record. The problem of memory resource waste described in the first scheme is avoided. In addition, because the server obtains the account data of the second account by analyzing the registration request in the present disclosure, the server does not need to query the account data of the second account from the data stored in the three-party user table like the second scheme, thereby increasing the speed of acquiring the account data of the second account. In addition, the corresponding expense for maintaining the current three-party user table is saved.

Specifically, as shown in fig. 5, the account registration method provided by the present disclosure may include the following steps S501 to S507:

s501, the client receives an account registration instruction.

The account registration instruction comprises an instruction for registering a first account associated with a second account in the first application. The first account is an account in a first application, the second account is an account in a second application, and the second application is different from the first application.

For example, the account registration instruction may specifically refer to an instruction generated after the user clicks any one of the controls "APP 1" and "APP 2" in the registration interface of the client shown in fig. 2.

S502, the client sends a registration request to the server in response to the account registration instruction.

The registration request is used for indicating that a first account with an association relation with a second account is registered.

S503, the server responds to the registration request, accesses the second application, and acquires account data of the second account.

The account data of the second account includes various account information of the second account in the second application.

For example, the account data of the second account may specifically include various user data corresponding to the second account, such as an avatar pattern, a user name, a nickname, user personal information (gender, age, and the like), an account code of the second account, and the like of the second account, or information for identifying the second account. The present disclosure is not limited thereto.

S504, the server sends account data and a verification prompt instruction of the second account to the client.

And S505, the client side responds to the verification prompt instruction and performs short message verification on the target mobile phone number.

And the target mobile phone number is used for binding with the first account number.

Illustratively, after receiving the verification prompt instruction, the client displays the prompt information to prompt the user to input the target mobile phone number and prompts the user to input the short message verification code corresponding to the target mobile phone number, so as to obtain the verification result of the short message verification of the target mobile phone number.

The verification prompt instruction may specifically include a short message verification instruction for instructing the client to perform short message verification on the target mobile phone number. And then the client can send the verification result to the server after obtaining the verification result of the short message verification of the target mobile phone number.

S506, the client responds to the verification result of the short message verification of the target mobile phone number, and sends the verification result and the account number data to the server.

In an implementation manner, the verification result may include a target mobile phone number and a verification code obtained by the client in response to an input operation.

In another implementation manner, the verification result may include the target mobile phone number and information indicating whether the verification code is correct. For example, after acquiring the verification code input by the user, the client may first verify the correctness of the verification code. If the client determines that the short message verification is successfully carried out on the target mobile phone number, a verification result comprising preset content is sent to the server, for example, one bit of '0' or '1' is transmitted in a preset field; and if the client determines that the short message verification is not successfully carried out on the target mobile phone number (for example, the user inputs an incorrect short message verification code, or the user does not input the short message verification code and quits the registration interface, and the like), the client does not send the verification result to the server. Therefore, the server can determine whether the short message authentication is successfully carried out on the target mobile phone number or not by receiving the authentication result or not.

S507, after the server determines that the short message verification is successfully carried out on the target mobile phone number according to the verification result, a user record of the first account is created, and account data from the client side is recorded in the user record.

And when the verification result comprises the target mobile phone number and the verification code obtained by the client in response to the input operation, the server establishes a user record of the first account after determining that the short message verification is successfully carried out on the target mobile phone number according to the verification code in the verification result, and records the account data from the client in the user record.

Furthermore, after determining that short message verification fails to be performed on the target mobile phone number according to the verification code, the method further comprises the following steps: and stopping registering the first account.

For example, when the server determines that the verification code from the client is incorrect, it may be considered that the short message verification of the target mobile phone number is determined to be failed according to the verification code.

In addition, stopping registering the first account may specifically refer to: the server stops running the process started for registering the first account, or releases the hardware resources for registering the first account, and the like.

In addition, the user record in the present disclosure may specifically include a storage area for recording account information of the first account. Specifically, the user record may be used to record account data of the second account. In addition, the user record may further include: the target mobile phone number, the association relationship between the first account number and the second account number, and other account number information (such as head portrait, nickname, etc.) of the first account number.

In an implementation manner, the creating, by the server, a user record of the first account may specifically refer to creating, by the server, a user record in a preset database stored in the local storage space. That is, the database used to store the user records is now made part of the server. In another implementation manner, the server creates a user record of the first account, which may specifically refer to the server controlling a server for maintaining a preset database to create the user record in the preset database. That is, the server and the server for maintaining the preset database are two independent devices or two independent device clusters at this time. The present disclosure may not be limited thereto.

In an implementation manner, it is considered that the client may access the second application and obtain the authorization code corresponding to the second account through the OAUTH protocol, and then the client sends the authorization code to the server, so that the server may access the second application and obtain the account data of the second account by using the authorization code. Therefore, as shown in fig. 6, before the client sends the registration request to the server in step S502, the method further includes:

s508, the client accesses the second application to obtain the target authorization code.

In addition, the registration request includes a target authorization code.

Further, the step S503 specifically includes: s503a, the server responds to the registration request, accesses the second application, and obtains the account data of the second account by using the target authorization code.

In an implementation manner, in order to ensure data security of the account data of the second account in the transmission process, the transmission of the account data may be implemented in a manner of encrypting the account data and transmitting a ciphertext. Therefore, as shown in fig. 7, in the step S504, the sending, by the server, the account data of the second account and the verification prompt instruction to the client includes:

s504 and 504a, the server sends the target ciphertext and the verification prompt instruction to the client. The target ciphertext comprises encrypted data obtained by encrypting the account number data.

Further, in step S506, in response to obtaining a verification result of performing short message verification on the target mobile phone number, the client sends the verification result and the account data to the server, where the method includes:

s506a, the client responds to the verification result of the short message verification of the target mobile phone number, and sends the verification result and the target ciphertext to the server.

Further, in a possible design, it is considered that the client does not need to decrypt the target ciphertext because the client does not need to process account data of the second account. Therefore, when the account data of the second account is encrypted, a symmetric encryption mode can be adopted. Therefore, the data security can be ensured, and the problem of larger calculation amount in encryption and decryption caused by an asymmetric encryption algorithm can be avoided.

For example, the account data may be encrypted by using an AES encryption algorithm to obtain a target ciphertext. For another example, the account data may be encrypted by using other symmetric encryption algorithms (e.g., Data Encryption Standard (DES), triple data encryption standard (TripleDES), RC2(Ron Rivest2), RC4(Ron Rivest 4), and RC5(Ron Rivest 5)) to obtain the target ciphertext. The present disclosure may not be so limited.

In addition, since the server creates the user record after determining that the first account number is successfully bound to the target mobile phone number, it is not necessary to mark whether the first account number is bound to the mobile phone number in the user record. Therefore, after the account registration is successful, when the first account is logged in, the state of the account does not need to be judged any more.

For example, in a case where the account registration method provided by the present disclosure is applied, as shown in fig. 8, a process of logging in an account includes:

s701, the client receives login operation of the user.

Specifically, the login operation may include a user operation for instructing to login to the first account through the second account.

S702, the client accesses the second application through the OAUTH protocol to obtain an authorization code corresponding to the second account (the authorization code may be the target authorization code in the foregoing).

And S703, the second application feeds back the target authorization code to the client.

S704, the client initiates a three-party authorization login process and sends the target authorization code to the server.

S705, the server accesses the second application through the target authorization code to obtain account data of the second account.

And S706, the second application feeds the account data of the second account back to the server.

S707, the server uses the account data of the second account to query the database for the user record (i.e. the target user record) recorded with the account data of the second account.

And S708, after the target user record is inquired in the data, the authorization client logs in the first account corresponding to the target user record.

Based on the same inventive concept as the account registration method, the invention also provides an account registration device. The account registration device is used for realizing the function of the server in the account registration method. As shown in fig. 9, the account registration apparatus 80 includes:

a receiving unit 801 configured to receive a registration request from a client; the registration request is used for indicating that a first account with an association relation with a second account is registered; the first account is an account in first application, the second account is an account in second application, and the second application is different from the first application.

A data obtaining unit 802, configured to access the second application in response to the registration request, and obtain account data of the second account.

The sending unit 803 is configured to send the account data and the verification prompt instruction to the client.

The receiving unit 801 is further configured to receive a verification result and account data from the client.

A creating unit 804, configured to create a user record of the first account after determining that short message authentication is successfully performed on the target mobile phone number according to the authentication result, and record account data from the client in the user record; and the target mobile phone number is used for binding with the first account number.

Optionally, the registration request carries a target authorization code; the data obtaining unit 802 is specifically configured to respond to the registration request, access the second application, and obtain the account data of the second account by using the target authorization code.

Optionally, the sending unit 803 is specifically configured to send the target ciphertext and the verification prompt instruction to the client; the target ciphertext comprises encrypted data obtained by encrypting the account number data; and the verification prompt instruction is used for indicating the client to carry out short message verification on the target mobile phone number and sending the verification result and the account number data to the account number registration device after obtaining the verification result of carrying out short message verification on the target mobile phone number.

The receiving unit 801 is specifically configured to receive a verification result and a target ciphertext from a client.

Optionally, the verification result includes: and the target mobile phone number and the verification code obtained by the client in response to the input operation.

After the target mobile phone number is successfully verified by the short message according to the verification result, a user record of a first account is created, wherein the user record comprises: and after the target mobile phone number is successfully verified by the short message according to the verification code, creating a user record of the first account. The account registration device also comprises a registration stopping unit; and the registration stopping unit is used for stopping registering the first account after the short message verification of the target mobile phone number is determined to be failed according to the verification code.

Optionally, the user record further includes: and the association relationship between the first account and the second account.

In addition, fig. 10 is a schematic structural diagram of a server according to an embodiment of the present disclosure. The server 90 may have a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 901 and one or more memories 902, where the memory 902 stores at least one instruction, and the at least one instruction is loaded and executed by the processor 901 to implement the functions of the server in the account registration method provided in the above embodiments. For example, the server 90 may implement the functions of the account registration apparatus 80 described above.

Certainly, the server 90 may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input and output, and the server 90 may also include other components for implementing the functions of the device, which is not described herein again.

The embodiment of the disclosure also provides an account registration device. As shown in fig. 11, the account registration apparatus 100 includes:

a transmitting unit 1001 for transmitting a registration request to a server; the first account is an account in first application, the second account is an account in second application, and the second application is different from the first application; the registration request is used for indicating that a first account with an association relation with a second account is registered;

a receiving unit 1002, configured to receive account data and a verification prompt instruction from a server;

a short message verification unit 1003, configured to perform short message verification on the target mobile phone number in response to the verification prompt instruction; the target mobile phone number is used for binding with the first account;

the sending unit 1001 is further configured to send, in response to an obtained verification result of short message verification on the target mobile phone number, the verification result and the account number data to the server, so that the server creates a user record of the first account number after determining that short message verification is successfully performed on the target mobile phone number according to the verification result, and records the account number data from the account number registration device in the user record.

Optionally, the registration request includes a target authorization code; the target authorization code is used for acquiring account data in the process of accessing the second application. The account registration apparatus further includes: the unit 1004 is accessed.

An accessing unit 1004, configured to access the second application to obtain the target authorization code.

Optionally, the receiving unit 1002 is specifically configured to receive a target ciphertext and a verification prompt instruction from a server; the target ciphertext includes encrypted data obtained by encrypting the account data.

The sending unit 1001 is specifically configured to send the verification result and the target ciphertext to the server.

In addition, the present disclosure also provides a client, and fig. 12 shows a schematic diagram of a possible structure of the client. As shown in fig. 12, the client 110 includes a processor 1101 and a memory 1102.

It is understood that the client 110 shown in fig. 12 can implement all of the functions of the client in the above embodiments. For example, the functions of the respective units in the client 110 described above may be implemented in the processor 1101 of the client 110 by processing the corresponding data.

Processor 1101 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so forth. The processor 1101 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

Memory 1102 may include one or more computer-readable storage media, which may be non-transitory. Memory 1102 can also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 1102 is used to store at least one instruction for execution by processor 1101 to implement an account registration method provided by embodiments of the disclosed method.

In some embodiments, the client 110 may further optionally include: a peripheral interface 1103 and at least one peripheral. The processor 1101, memory 1102 and peripheral interface 1103 may be connected by a bus or signal lines. Various peripheral devices may be connected to the peripheral interface 1103 by buses, signal lines, or circuit boards. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1104, display screen 1105, camera assembly 1106, audio circuitry 1107, positioning assembly 1108, and power supply 1109.

The peripheral interface 1103 may be used to connect at least one peripheral associated with I/O (Input/Output) to the processor 1101 and the memory 1102. In some embodiments, the processor 1101, memory 1102, and peripheral interface 1103 are integrated on the same chip or circuit board; in some other embodiments, any one or both of the processor 1101, the memory 1102, and the peripheral device interface 1103 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

The Radio Frequency circuit 1104 is used to receive and transmit RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuit 1104 communicates with communication networks and other communication devices via electromagnetic signals. The radio frequency circuit 1104 converts an electric signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electric signal. Optionally, the radio frequency circuit 1104 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 1104 may communicate with other video compositing devices via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or Wi-Fi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 1104 may also include NFC (Near Field Communication) related circuits, which are not limited by this disclosure.

The display screen 1105 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 1105 is a touch display screen, the display screen 1105 also has the ability to capture touch signals on or over the surface of the display screen 1105. The touch signal may be input to the processor 1101 as a control signal for processing. At this point, the display screen 1105 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display screen 1105 may be one, setting the front panel of the client 110; the Display screen 1105 may be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), and the like.

Camera assembly 1106 is used to capture images or video. Optionally, camera assembly 1106 includes a front camera and a rear camera. In general, a front camera is disposed on a front panel of a video compositing apparatus, and a rear camera is disposed on a rear surface of the video compositing apparatus. The audio circuitry 1107 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 1101 for processing or inputting the electric signals to the radio frequency circuit 404 for realizing voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones may be provided at different positions of the client 110. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 1101 or the radio frequency circuit 1104 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 1107 may also include a headphone jack.

The positioning component 1108 is used to locate the current geographic location of the client 110 to implement navigation or LBS (location based Service). The positioning component 1108 may be a positioning component based on the united states GPS (global positioning System), the chinese beidou System, the russian graves System, or the european union's galileo System.

The power supply 1109 is used to supply power to the various components in the client 110. The power supply 1109 may be alternating current, direct current, disposable or rechargeable. When the power supply 1109 includes a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, client 110 also includes one or more sensors 1110. The one or more sensors 1110 include, but are not limited to: acceleration sensors, gyroscope sensors, pressure sensors, fingerprint sensors, optical sensors, and proximity sensors.

The acceleration sensor may detect the magnitude of acceleration on three coordinate axes of the coordinate system established with the client 110. The gyro sensor may detect a body direction and a rotation angle of the client 110, and the gyro sensor may cooperate with the acceleration sensor to acquire a 3D action of the user on the client 110. The pressure sensors may be disposed on the side bezel of the client 110 and/or underlying the touch display screen 1105. When the pressure sensor is disposed on the side frame of the client 110, a user's holding signal to the client 110 may be detected. The fingerprint sensor is used for collecting fingerprints of users. The optical sensor is used for collecting the intensity of ambient light. Proximity sensors, also known as distance sensors, are typically provided on the front panel of the client 110. The proximity sensor is used to collect the distance between the user and the front of the client 110.

The present disclosure also provides a computer-readable storage medium, on which instructions are stored, and when the instructions in the storage medium are executed by a processor of a computer, the computer is enabled to execute all or part of the functions of the client or the server in the embodiments of the present disclosure, so as to implement the account registration method provided by the present disclosure.

Embodiments of the present disclosure also provide a computer program product including instructions, which when run on a computer, enable the computer to perform all or part of the functions of the client or the server in the embodiments of the present disclosure, so as to implement the account registration method provided by the present disclosure.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure 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 disclosure is limited only by the appended claims.

Claims

1. An account registration method is applied to a server, and the method comprises the following steps:

receiving a registration request from a client; the registration request is used for indicating that a first account with an association relation with a second account is registered; the first account is an account in a first application, the second account is an account in a second application, and the second application is different from the first application;

responding to the registration request, accessing the second application, and acquiring account data of the second account;

sending the account data and a verification prompt instruction to the client;

receiving a verification result and the account data from the client;

after the short message verification of the target mobile phone number is determined to be successful according to the verification result, a user record of the first account is created, and the account data from the client side is recorded in the user record; and the target mobile phone number is used for binding with the first account number.

2. The account registration method according to claim 1, wherein the registration request carries a target authorization code;

the step of responding to the registration request, accessing the second application, and acquiring account data of the second account includes:

and responding to the registration request, accessing the second application, and acquiring account data of the second account by using the target authorization code.

3. The account registration method according to claim 1, wherein the sending the account details and the verification prompt instruction to the client includes:

sending a target ciphertext and the verification prompt instruction to the client; the target ciphertext comprises encrypted data obtained by encrypting the account number data; the verification prompt instruction is used for instructing the client to perform short message verification on the target mobile phone number and sending the verification result and the account number data to the server after obtaining the verification result of the short message verification on the target mobile phone number;

the receiving the verification result and the account data from the client includes:

receiving the verification result and the target ciphertext from the client.

4. The account registration method according to claim 3, wherein the target cryptogram specifically includes encrypted data obtained by encrypting the account data by a symmetric encryption method.

5. An account registration method is applied to a client, and comprises the following steps:

sending a registration request to a server; the method comprises the steps that a first account is an account in first application, a second account is an account in second application, and the second application is different from the first application; the registration request is used for indicating that a first account with an association relation with a second account is registered;

receiving account data and a verification prompt instruction from the server;

responding to the verification prompt instruction, and performing short message verification on the target mobile phone number; the target mobile phone number is used for binding with the first account;

and responding to an acquired verification result of short message verification on the target mobile phone number, and sending the verification result and the account number data to a server, so that the server creates a user record of the first account number after determining that the short message verification is successfully performed on the target mobile phone number according to the verification result, and records the account number data from the client in the user record.

6. An account registration apparatus, comprising:

a receiving unit, configured to receive a registration request from a client; the registration request is used for indicating that a first account with an association relation with a second account is registered; the first account is an account in a first application, the second account is an account in a second application, and the second application is different from the first application;

the data acquisition unit is used for responding to the registration request, accessing the second application and acquiring account data of the second account;

the sending unit is used for sending the account data and a verification prompt instruction to the client;

the receiving unit is further configured to receive a verification result and the account data from the client;

the establishing unit is used for establishing a user record of the first account after the short message verification of the target mobile phone number is determined to be successful according to the verification result, and recording the account data from the client in the user record; and the target mobile phone number is used for binding with the first account number.

7. An account registration apparatus, comprising:

a sending unit, configured to send a registration request to a server; the method comprises the steps that a first account is an account in first application, a second account is an account in second application, and the second application is different from the first application; the registration request is used for indicating that a first account with an association relation with a second account is registered;

the receiving unit is used for receiving account data and a verification prompt instruction from the server;

the short message verification unit is used for responding to the verification prompt instruction and performing short message verification on the target mobile phone number; the target mobile phone number is used for binding with the first account;

the sending unit is further configured to send the verification result and the account number data to a server in response to an obtained verification result of short message verification on the target mobile phone number, so that the server creates a user record of the first account number after determining that short message verification is successfully performed on the target mobile phone number according to the verification result, and records the account number data from the account number registration device in the user record.

8. A server, comprising: a processor, a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the account registration method of any of claims 1-4.

9. A client, comprising: a processor, a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the account registration method as claimed in claim 5.

10. A computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to perform the account registration method of any one of claims 1-4 or claim 5.