CN117768234A - Cross-scene login method and device - Google Patents

Abstract

The application discloses a cross-scene login method and device, when a scene jump request sent by a current scene is received, a random application number, login elements, the number of the current scene and the number of a target scene which are acquired in advance are spliced into a first character string; calculating according to the first character string to obtain a first authorization credential, and jumping to a target scene by using the first authorization credential; when a login request sent by a target scene is received, the second random application number, the login element, the number of the first scene and the number of the target scene are spliced into a second character string; calculating according to the second character string to obtain a second authorization credential; and if the first authorization credential and the second authorization credential are consistent, acquiring login information of the target scene, and logging in by using the login information. By synchronizing the login information and the user number to all scenes, all scenes can be logged in by adopting the same login element, so that the login process of the user for logging in different scenes is simplified, and the experience of the user is improved.

Description

Cross-scene login method and device

Technical Field

The application relates to the technical field of internet, in particular to a cross-scene login method and device.

Background

With the development of the internet and mobile payment, conventional banking has been gradually replaced with digitization and intellectualization. In order to meet market demands, banks need to be continuously innovated, and demands of users are met through construction of online scenes.

Currently, online scenarios of banks are generally built based on self accounts and payment capabilities, and provide services (such as capability services for querying personal account information) for users holding physical bank cards. Because the information systems under different on-line scenes are usually independently developed and managed, data between the information systems cannot be shared and exchanged directly, so that the user needs to provide or verify information again under different scenes, the information systems are complicated, and the experience of the user is poor.

Therefore, how to improve the experience of the user is a problem to be solved in the art.

Disclosure of Invention

The application provides a cross-scene login method and device, and aims to improve experience of a user.

In order to achieve the above object, the present application provides the following technical solutions:

a cross-scene login method, comprising:

when a scene jump request carrying a first random application number sent by a current scene is received, acquiring a login element, the number of the current scene and the number of a target scene; the scene hop request indicates a request to hop from the current scene to the target scene; the first random application number is obtained by calculating the current scene in advance according to the verification random number;

splicing the random application number, the login element, the number of the current scene and the number of the target scene to obtain a first character string;

calculating the first character string by utilizing a hash function to obtain a first authorization credential, and jumping to the target scene by utilizing the first authorization credential;

when a login request carrying a second random application number and the first authorization credential sent by the target scene is received, splicing the second random application number, the login element, the number of the first scene and the number of the target scene to obtain the second character string; the second random application number is calculated in advance according to the verification random number for the target scene;

calculating the second character string by utilizing the hash function to obtain a second authorization credential;

when the first authorization credential and the second authorization credential are consistent, acquiring login information of the target scene, and logging in by using the login information.

Optionally, the method further comprises:

and when the first authorization credential and the second authorization credential are inconsistent, sending prompt information of login failure to the user.

Optionally, when receiving a scene jump request carrying a first random application number sent by a current scene, before obtaining a login element, a number of the current scene and a number of a target scene, the method further includes:

when receiving a login element sent by a current scene, detecting whether the login element is contained in a database;

if the database does not contain the login element, the login element is used for registering, and login information is obtained;

generating a user number based on the login information;

after generating a user number corresponding to the login information, acquiring authentication information of a user, and performing real-name authentication by using the authentication information;

and after the real-name authentication is completed, synchronizing the login information and the user number into all scenes.

Optionally, the obtaining authentication information of the user and performing real-name authentication by using the authentication information include:

when the bank card information corresponding to the user exists in the information database, acquiring the bank card information corresponding to the user, and performing real-name authentication by utilizing the bank card information;

when the bank card information corresponding to the user does not exist in the information database, the basic information of the user is acquired, and real-name authentication is performed by utilizing the basic information.

Optionally, the method further comprises:

when a login request carrying login elements sent by the target scene is received, detecting whether the login elements are contained in a database or not;

and if the database contains the login element, acquiring the login information of the target scene, and logging in by using the login information.

A cross-scene login device comprising:

the acquisition unit is used for acquiring a login element, the number of the current scene and the number of the target scene when receiving a scene jump request carrying a first random application number sent by the current scene; the scene hop request indicates a request to hop from the current scene to the target scene; the first random application number is obtained by calculating the current scene in advance according to the verification random number;

the first splicing unit is used for splicing the random application number, the login element, the number of the current scene and the number of the target scene to obtain a first character string;

the jump unit is used for calculating the first character string by utilizing a hash function to obtain a first authorization credential and jumping to the target scene by utilizing the first authorization credential;

the second splicing unit is used for splicing the second random application number, the login element, the number of the first scene and the number of the target scene to obtain the second character string when receiving a login request carrying the second random application number and the first authorization credential, wherein the login request is sent by the target scene; the second random application number is calculated in advance according to the verification random number for the target scene;

the calculating unit is used for calculating the second character string by utilizing the hash function to obtain a second authorization credential;

and the login unit is used for acquiring the login information of the target scene when the first authorization credential and the second authorization credential are consistent, and logging in by utilizing the login information.

Optionally, the method further comprises:

and the sending unit is used for sending prompt information of login failure to the user when the first authorization credential and the second authorization credential are inconsistent.

Optionally, the method further comprises:

the detection unit is used for detecting whether the login element is contained in the database or not when the login element sent by the current scene is received;

a registration unit, configured to register with the login element if the database does not include the login element, to obtain login information;

a generation unit for generating a user number based on the login information;

the authentication unit is used for acquiring authentication information of the user after generating the user number corresponding to the login information and performing real-name authentication by utilizing the authentication information;

and the synchronization unit is used for synchronizing the login information and the user number to all scenes after the real-name authentication is completed.

Optionally, the authentication unit is specifically configured to:

when the bank card information corresponding to the user exists in the information database, acquiring the bank card information corresponding to the user, and performing real-name authentication by utilizing the bank card information;

when the bank card information corresponding to the user does not exist in the information database, the basic information of the user is acquired, and real-name authentication is performed by utilizing the basic information.

Optionally, the method further comprises:

the element detection unit is used for detecting whether the login element is contained in the database or not when a login request carrying the login element sent by the target scene is received;

and the scene registration unit is used for acquiring the registration information of the target scene if the database contains the registration elements and registering by using the registration information.

According to the technical scheme, when a scene jump request carrying a first random application number sent by a current scene is received, a login element, the number of the current scene and the number of a target scene are obtained; splicing the random application number, the login element, the number of the current scene and the number of the target scene to obtain a first character string; calculating the first character string by utilizing a hash function to obtain a first authorization credential, and jumping to a target scene by utilizing the first authorization credential; when a login request carrying a second random application number and a first authorization credential sent by a target scene is received, splicing the second random application number, a login element, the number of the first scene and the number of the target scene to obtain a second character string; calculating the second character string by utilizing the hash function to obtain a second authorization credential; when the first authorization credential and the second authorization credential are consistent, acquiring login information of the target scene, and logging in by using the login information. In the method, all scenes can be logged in by synchronizing the login information and the user number to all scenes and adopting the same login element subsequently, and repeated login information is not needed for different scenes, so that the login process of the user for logging in different scenes is simplified, and the experience of the user is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flowchart of a cross-scene login method provided in an embodiment of the present application;

fig. 2 is a flowchart of a method for synchronizing information according to an embodiment of the present application;

fig. 3 is a flowchart of a login method of a target scene according to an embodiment of the present application;

fig. 4 is a schematic architecture diagram of a cross-scenario login device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

As shown in fig. 1, a flowchart of a cross-scene login method provided in an embodiment of the present application is applied to a user center module, and includes the following steps:

s101: when a scene jump request carrying a first random application number sent by a current scene is received, acquiring a login element, the number of the current scene and the number of a target scene.

Wherein the scene jump request indicates a request to jump from a current scene to a target scene; the first random application number is obtained by calculating the current scene in advance according to the verification random number.

It should be noted that, when the current scene receives the scene jump request, a verification random number (for example, a verification code) is generated, and a hash calculation is performed on the verification random number to obtain a first random application number.

Optionally, the login element includes, but is not limited to,: account number, password, weChat OpenID, third party scene own user system ID.

It can be understood that the number of the current scene and the number of the target scene refer to the unique identification of the scene in all scenes, and the current scene or the target scene can be queried through the unique identification.

Optionally, before step S101, in order to reduce the complexity of the user to repeatedly input the account number and the password, the overall user experience is improved. The user does not need to log in after repeated registration in different scenes, and can operate and interact more conveniently. In another embodiment of the present application, there is therefore provided a method for synchronizing information, as shown in fig. 2, including the steps of:

s201: when receiving the login element sent by the current scene, detecting whether the login element is contained in the database.

If the database does not include the login element, step S202 is executed.

Optionally, the bank and the third party scene may establish a membership relationship, and the bank is utilized to deploy the joint member opening service in the third party scene platform, and when the user accesses the joint member service in the third party scene (for example, the current scene), the user login element is acquired through the third party scene, and the login element is sent to the user center module.

It can be understood that when the user center module receives the login element sent by the current scene, it detects whether the login element is included in the database, that is, determines whether the element has completed registration in the current scene or other scenes, and if the login element is not included in the database, it indicates that the element has not completed registration in the current scene or other scenes; if the database contains the login element, the element is registered in the current scene or other scenes.

S202: and registering by using the login element to obtain login information.

It will be appreciated that when the registration operation is completed, the current scene may be subsequently registered using the registration information.

S203: a user number is generated based on the login information.

Wherein the user number is a sequence code uniquely identifying the user, e.g., user number 10.

It should be noted that, the user is in an unauthentic state at this time, the user number only ensures that the same login element in the same scene will not be repeated, and the user code may be repeated in different scenes. For example, the user code for scene a is 10, the user code for scene B is 15, and the user code for scene C is 10.

S204: after the user number corresponding to the login information is generated, the authentication information of the user is acquired, and real-name authentication is performed by using the authentication information.

Wherein the authentication information indicates information that the user completes real-name authentication.

It can be understood that the authentication information acquired in different situations is different, and the real-name authentication modes corresponding to different authentication information are different.

Optionally, in another embodiment of the present application, the step S204 of obtaining authentication information of the user, and a specific implementation manner of real-name authentication using the authentication information includes the following steps:

when the bank card information corresponding to the user exists in the information database, the bank card information corresponding to the user is acquired, and real-name authentication is performed by using the bank card information.

Among them, the bank card information includes, but is not limited to: bank card account, cell phone number.

The specific process of real-name authentication by using the bank card information is as follows: and carrying out real-name authentication by using the bank card account number and the mobile phone number through the short message verification code.

When the bank card information corresponding to the user does not exist in the information database, the basic information of the user is obtained, and real-name authentication is performed by using the basic information.

Wherein, the basic information of the user includes, but is not limited to: age, identification card number, face information.

The specific process of real-name authentication by using the basic information is as follows: when the basic information is received, acquiring target face information corresponding to the basic information from a weight database; acquiring face information of a user, and comparing target face information with the face information; and when the target face information is consistent with the face information, real-name authentication is completed.

S205: and after the real-name authentication is completed, synchronizing the login information and the user number into all scenes.

It should be noted that, before the real-name authentication is not completed, the user number of each scene may have an inconsistent condition, and after the real-name authentication is completed, the login information and the user number are synchronized to all the scenes, so that the login information and the user number of the user are consistent in all the scenes, and all the scenes can be logged in through the same login information later, no additional registration or real-name authentication is required, and login across the scenes is realized.

S102: and splicing the first random application number, the login element, the number of the current scene and the number of the target scene to obtain a first character string.

Alternatively, the concatenation of the strings may be implemented using a string join operator (e.g., +) or a string join function (e.g., concat ()), i.e., the random application number, the login element, the number of the current scene, and the number of the target scene are spliced into the first string using the string join operator or string join function.

S103: and calculating the first character string by utilizing the hash function to obtain a first authorization credential, and jumping to the target scene by utilizing the first authorization credential.

Wherein the hash function includes, but is not limited to,: md5.

It will be appreciated that the first string is calculated using the md5 hash function, and the resulting hash value is used as a first authorization credential (i.e., token) that is valid for a specified time.

It should be noted that, the first authorization credential is used to jump to the target scene, specifically, the first authorization credential is fed back to the user, and the user needs to be carried with the first authorization credential at the designated time to complete the operation of jumping to the target scene.

S104: when a login request carrying a second random application number and a first authorization credential sent by a target scene is received, the second random application number, a login element, the number of the first scene and the number of the target scene are spliced to obtain a second character string.

The second random application number is calculated in advance according to the verification random number for the target scene.

It should be noted that, when the target scene receives the login request, a verification random number (for example, a verification code) is generated, and a hash calculation is performed on the verification random number to obtain a second random application number.

Optionally, the second random application number, the login element, the number of the current scene and the number of the target scene may be spliced into the second string by using a string connection operator or a string connection function.

S105: and calculating the second character string by utilizing the hash function to obtain a second authorization credential.

Alternatively, the first string may be calculated using an md5 hash function, and the resulting hash value is used as the second authorization credential (i.e., token).

Optionally, after step S105, further includes:

and when the first authorization credential and the second authorization credential are inconsistent, sending prompt information of login failure to the user.

It can be understood that, because the first character string is formed by splicing the first random application number and other information, and the second character string is formed by splicing the second random application number and other information, the random application numbers adopted during splicing may be the same or different, so that the condition that the first authorization certificate and the second authorization certificate are inconsistent can occur. And when the first authorization credential and the second authorization credential are inconsistent, sending prompt information of login failure to the user.

S106: when the first authorization credential and the second authorization credential are consistent, acquiring login information of the target scene, and logging in by using the login information.

When the first authorization credential and the second authorization credential are consistent, the first authorization credential can be checked to obtain the login information of the target scene at the moment, and login is performed by using the login information, so that the cross-scene login is completed.

Optionally, if the user does not perform the scene skip operation, but directly logs in the target scene, the user can log in through the login information without re-registering and real name, so that the time for logging in the current scene by the user is shortened. Therefore, in another embodiment of the present application, there is provided a login method of a target scene, as shown in fig. 3, including:

s301: when a login request carrying a login element sent by a target scene is received, whether the login element is contained in a database is detected.

If the database contains the login element, step S302 is executed.

It can be understood that, since the login information and the user number are already synchronized in all the scenes, when the same login element is adopted to log in other scenes, the login can be directly performed, and in order to further confirm whether the login information and the user number are synchronously completed in all the scenes, whether the login element is included in the database needs to be detected, if the login element is not included in the database, it is determined that the login information and the user number are not synchronously completed in all the scenes, and the login cannot be directly performed.

S302: and acquiring login information of the target scene, and logging in by using the login information.

It can be understood that if the database includes the login element, it is determined that the login information and the user number are completed synchronously in all the scenes, and the login information of the target scene can be obtained, and the login information is used for logging in, so as to complete the login step.

In summary, the first character string is calculated by using the hash function to obtain the first authorization credential, the first authorization credential is used to jump to the target scene, when a login request carrying the second random application number and the first authorization credential sent by the target scene is received, the second random application number, the login element, the number of the first scene and the number of the target scene are spliced to obtain the second character string, the hash function is used to calculate the second character string to obtain the second authorization credential, and when the first authorization credential and the second authorization credential are consistent, login information of the target scene is obtained, and login is performed by using the login information. In the embodiment of the application, by synchronizing the login information and the user number to all scenes, all scenes can be logged in by adopting the same login element, and repeated login information is not needed for different scenes, so that the login process of the user for logging in different scenes is simplified, and the experience of the user is improved.

As shown in fig. 4, an architecture diagram of a cross-scenario login device according to an embodiment of the present application is provided, where the login device includes: the device comprises an acquisition unit 100, a first splicing unit 200, a jumping unit 300, a second splicing unit 400, a calculation unit 500 and a login unit 600.

An obtaining unit 100, configured to obtain a login element, a number of a current scene, and a number of a target scene when a scene jump request carrying a first random application number sent by the current scene is received; the scene jump request indicates a request to jump from a current scene to a target scene; the first random application number is obtained by calculating the current scene in advance according to the verification random number.

The first splicing unit 200 is configured to splice the random application number, the login element, the number of the current scene, and the number of the target scene to obtain a first character string.

The jumping unit 300 is configured to calculate the first string by using the hash function, obtain a first authorization credential, and jump to the target scene by using the first authorization credential.

The second splicing unit 400 is configured to splice, when receiving a login request carrying a second random application number and a first authorization credential sent by a target scene, the second random application number, a login element, a number of the first scene, and a number of the target scene, to obtain a second character string; the second random application number is obtained by calculating the target scene in advance according to the verification random number.

The calculating unit 500 is configured to calculate the second string by using the hash function, so as to obtain a second authorization credential.

And a login unit 600, configured to obtain login information of the target scene when the first authorization credential and the second authorization credential are consistent, and login using the login information.

In summary, the first character string is calculated by using the hash function to obtain the first authorization credential, the first authorization credential is used to jump to the target scene, when a login request carrying the second random application number and the first authorization credential sent by the target scene is received, the second random application number, the login element, the number of the first scene and the number of the target scene are spliced to obtain the second character string, the hash function is used to calculate the second character string to obtain the second authorization credential, and when the first authorization credential and the second authorization credential are consistent, login information of the target scene is obtained, and login is performed by using the login information. In the embodiment of the application, by synchronizing the login information and the user number to all scenes, all scenes can be logged in by adopting the same login element, and repeated login information is not needed for different scenes, so that the login process of the user for logging in different scenes is simplified, and the experience of the user is improved.

Preferably, in combination with the content shown in fig. 4, the login device further includes: and the sending unit is used for sending prompt information of login failure to the user when the first authorization credential and the second authorization credential are inconsistent.

Preferably, in combination with the content shown in fig. 4, the login device further includes: the device comprises a detection unit, a registration unit, a generation unit, an authentication unit and a synchronization unit.

And the detection unit is used for detecting whether the login element is contained in the database or not when the login element sent by the current scene is received.

And the registration unit is used for registering by using the login element to obtain login information if the database does not contain the login element.

And the generating unit is used for generating the user number based on the login information.

And the authentication unit is used for acquiring the authentication information of the user after generating the user number corresponding to the login information and performing real-name authentication by using the authentication information.

The authentication unit is specifically configured to: when the bank card information corresponding to the user exists in the information database, acquiring the bank card information corresponding to the user, and performing real-name authentication by utilizing the bank card information; when the bank card information corresponding to the user does not exist in the information database, the basic information of the user is obtained, and real-name authentication is performed by using the basic information.

And the synchronization unit is used for synchronizing the login information and the user number into all scenes after the real-name authentication is completed.

Preferably, in combination with the content shown in fig. 4, the login device further includes: element detection means and scene registration means.

And the element detection unit is used for detecting whether the login element is contained in the database or not when receiving the login request carrying the login element sent by the target scene.

And the scene registration unit is used for acquiring the registration information of the target scene if the database contains the registration elements and registering by using the registration information.

In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same or similar parts of each embodiment are referred to each other. In particular, for a system or system embodiment, since it is substantially similar to a method embodiment, the description is relatively simple, with reference to the description of the method embodiment being made in part. The systems and system 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 purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A cross-scene login method, comprising:

when a scene jump request carrying a first random application number sent by a current scene is received, acquiring a login element, the number of the current scene and the number of a target scene; the scene hop request indicates a request to hop from the current scene to the target scene; the first random application number is obtained by calculating the current scene in advance according to the verification random number;

splicing the random application number, the login element, the number of the current scene and the number of the target scene to obtain a first character string;

calculating the first character string by utilizing a hash function to obtain a first authorization credential, and jumping to the target scene by utilizing the first authorization credential;

when a login request carrying a second random application number and the first authorization credential sent by the target scene is received, splicing the second random application number, the login element, the number of the first scene and the number of the target scene to obtain the second character string; the second random application number is calculated in advance according to the verification random number for the target scene;

calculating the second character string by utilizing the hash function to obtain a second authorization credential;

when the first authorization credential and the second authorization credential are consistent, acquiring login information of the target scene, and logging in by using the login information.

2. The method as recited in claim 1, further comprising:

and when the first authorization credential and the second authorization credential are inconsistent, sending prompt information of login failure to the user.

3. The method of claim 1, wherein when receiving the scene jump request carrying the first random application number sent by the current scene, before obtaining the login element, the number of the current scene, and the number of the target scene, the method further comprises:

when receiving a login element sent by a current scene, detecting whether the login element is contained in a database;

if the database does not contain the login element, the login element is used for registering, and login information is obtained;

generating a user number based on the login information;

after generating a user number corresponding to the login information, acquiring authentication information of a user, and performing real-name authentication by using the authentication information;

and after the real-name authentication is completed, synchronizing the login information and the user number into all scenes.

4. A method according to claim 3, wherein the obtaining authentication information of the user, and using the authentication information for real-name authentication, comprises:

when the bank card information corresponding to the user exists in the information database, acquiring the bank card information corresponding to the user, and performing real-name authentication by utilizing the bank card information;

when the bank card information corresponding to the user does not exist in the information database, the basic information of the user is acquired, and real-name authentication is performed by utilizing the basic information.

5. The method as recited in claim 1, further comprising:

when a login request carrying login elements sent by the target scene is received, detecting whether the login elements are contained in a database or not;

and if the database contains the login element, acquiring the login information of the target scene, and logging in by using the login information.

6. A cross-scene login device, comprising:

the acquisition unit is used for acquiring a login element, the number of the current scene and the number of the target scene when receiving a scene jump request carrying a first random application number sent by the current scene; the scene hop request indicates a request to hop from the current scene to the target scene; the first random application number is obtained by calculating the current scene in advance according to the verification random number;

the first splicing unit is used for splicing the random application number, the login element, the number of the current scene and the number of the target scene to obtain a first character string;

the jump unit is used for calculating the first character string by utilizing a hash function to obtain a first authorization credential and jumping to the target scene by utilizing the first authorization credential;

the second splicing unit is used for splicing the second random application number, the login element, the number of the first scene and the number of the target scene to obtain the second character string when receiving a login request carrying the second random application number and the first authorization credential, wherein the login request is sent by the target scene; the second random application number is calculated in advance according to the verification random number for the target scene;

the calculating unit is used for calculating the second character string by utilizing the hash function to obtain a second authorization credential;

and the login unit is used for acquiring the login information of the target scene when the first authorization credential and the second authorization credential are consistent, and logging in by utilizing the login information.

7. The apparatus as recited in claim 6, further comprising:

and the sending unit is used for sending prompt information of login failure to the user when the first authorization credential and the second authorization credential are inconsistent.

8. The apparatus as recited in claim 6, further comprising:

the detection unit is used for detecting whether the login element is contained in the database or not when the login element sent by the current scene is received;

a registration unit, configured to register with the login element if the database does not include the login element, to obtain login information;

a generation unit for generating a user number based on the login information;

the authentication unit is used for acquiring authentication information of the user after generating the user number corresponding to the login information and performing real-name authentication by utilizing the authentication information;

and the synchronization unit is used for synchronizing the login information and the user number to all scenes after the real-name authentication is completed.

9. The apparatus according to claim 8, wherein the authentication unit is specifically configured to:

when the bank card information corresponding to the user exists in the information database, acquiring the bank card information corresponding to the user, and performing real-name authentication by utilizing the bank card information;

when the bank card information corresponding to the user does not exist in the information database, the basic information of the user is acquired, and real-name authentication is performed by utilizing the basic information.

10. The apparatus as recited in claim 6, further comprising:

the element detection unit is used for detecting whether the login element is contained in the database or not when a login request carrying the login element sent by the target scene is received;

and the scene registration unit is used for acquiring the registration information of the target scene if the database contains the registration elements and registering by using the registration information.