CN112235303A

CN112235303A - Account logout method and device and computer equipment

Info

Publication number: CN112235303A
Application number: CN202011103903.4A
Authority: CN
Inventors: 李飞宏; 张磊; 彭士涛; 李潇
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-10-15
Filing date: 2020-10-15
Publication date: 2021-01-15
Anticipated expiration: 2040-10-15
Also published as: CN112235303B

Abstract

The embodiment of the application discloses an account logout method, an account logout device and computer equipment; the method and the device for verifying the account number can receive an account number verification request, wherein the account number verification request comprises data to be verified of a first application account number; according to the account checking request, determining an account identifier which has a mapping relation with a first application account in the unified account system, wherein the account identifier is generated based on a second application account; based on the data to be verified, performing identity verification on the first application account; receiving an account logout request of a first application account passing the verification, wherein the account logout request carries logout application time information of the first application account; performing logout rule matching on the first application account based on the logout application time information and account login record information of the first application account; and when the first application account can be logged off, removing the mapping relation between the first application account and the account identification so as to log off the first application account. The scheme can improve the efficiency of account logout and is beneficial to account management.

Description

Account logout method and device and computer equipment

Technical Field

The application relates to the technical field of computers, in particular to an account logout method and device and computer equipment.

Background

When the registered user of the application no longer accepts the application protocol or no longer uses the service provided by the application, the account of the registered user can be logged off to terminate the application protocol between the registered user and the application, and the account of the registered user in the application is deleted or anonymized.

In the research and practice process of the related technology, the inventor of the application finds that when account logout is carried out, data related to an account to be logout in an application needs to be located and deleted, or an account anonymization functional component needs to be developed in the application, so that not only is there invasion to application logic, but also the difficulty of account logout is greatly increased.

Disclosure of Invention

The embodiment of the application provides an account logout method and device, which can improve account logout efficiency and are beneficial to account management.

The embodiment of the application provides an account logout method, which comprises the following steps:

receiving an account verification request, wherein the account verification request comprises data to be verified of a first application account;

determining an account identifier having a mapping relation with the first application account in a unified account system according to the account verification request, wherein the account identifier is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications;

based on the data to be verified, performing identity verification on the first application account to obtain a verification result;

receiving an account logout request of a first application account passing verification, wherein the account logout request carries logout application time information of the first application account;

performing logout rule matching on the first application account based on the logout application time information and account login record information of the first application account to determine a logout attribute of the first application account;

and when the logout attribute of the first application account is logout, removing the mapping relation between the first application account and the account identifier so as to logout the first application account.

Correspondingly, an embodiment of the present application further provides an account logout apparatus, including:

the device comprises a first receiving unit, a second receiving unit and a verification processing unit, wherein the first receiving unit is used for receiving an account verification request, and the account verification request comprises to-be-verified data of a first application account;

a determining unit, configured to determine, according to the account verification request, an account identifier in a unified account system, where the account identifier has a mapping relationship with the first application account, where the account identifier is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications;

the verification unit is used for verifying the identity of the first application account based on the data to be verified to obtain a verification result;

the second receiving unit is used for receiving an account logout request of a first application account passing verification, wherein the account logout request carries logout application time information of the first application account;

a matching unit, configured to perform logout rule matching on the first application account based on the logout application time information and account login record information of the first application account to determine a logout attribute of the first application account;

and the canceling unit is used for canceling the mapping relation between the first application account and the account identifier to cancel the cancellation of the first application account when the cancellation attribute of the first application account is cancelled.

In one embodiment, the matching unit includes:

a candidate determining subunit, configured to determine the first application account passing the verification as a candidate logout account for performing account logout;

the time calculation subunit is used for calculating an account logout cold quiet period of the candidate logout account and an account logout buffer period of the candidate logout account after the account logout cold quiet period according to the logout application time information of the candidate logout account;

the information query subunit is used for performing information query in an account login record table of a first application to obtain a first login record of the candidate logout account in the account logout cold quiet period and a second login record of the candidate logout account in the account logout buffer period;

and the rule matching subunit is used for performing logout rule matching on the candidate logout account number based on the first login record and the second login record so as to determine the logout attribute of the candidate logout account number.

In an embodiment, the rule matching subunit is specifically configured to:

comparing the first login record with the second login record to determine account login behavior information of the candidate logout account after an account logout application is submitted; and when the account login behavior information matches the logout rule of the first application, determining the logout attribute of the candidate logout account as logout.

In one embodiment, the releasing unit includes:

a target determining subunit, configured to determine the first application account that can be revoked as a target logout account to be logged out;

a first generation subunit, configured to generate a mapping relationship release request for the target logout account;

and the first sending subunit is configured to send the mapping relationship release request to the unified account system, so as to trigger the unified account system to release the mapping relationship between the target logout account and the account identifier.

In an embodiment, before the sending the mapping relationship release request to the unified account system, the release unit further includes:

a state obtaining subunit, configured to obtain an account state of the target logout account;

an account request subunit, configured to request the unified account system to generate a third application account to be allocated for the account identifier, where the third application account and the target logout account are application accounts belonging to the same application;

and the trigger determining subunit is configured to determine, according to the account status, an account activation trigger event of the third application account.

In an embodiment, after the sending the mapping relationship release request to the unified account system, the release unit further includes:

a peripheral determining subunit, configured to determine a peripheral component of the first application;

a second generation subunit, configured to generate a data cleaning request for the peripheral component, where the data cleaning request carries account information of the target logout account;

and the second sending subunit is configured to send the data cleaning request to the peripheral component, so as to trigger cleaning of application-related data of the target logout account in the peripheral component based on the account information.

In one embodiment, the first receiving unit includes:

the page sending subunit is used for sending the unified account logout page data including the logout verification process data to the terminal so that the terminal can display the unified account logout page;

and the request receiving subunit is used for receiving an account verification request when the terminal performs a logout identity verification process based on the unified account logout page and completes logout identity verification, wherein the account verification request carries the data to be verified, which is acquired in the logout identity verification process.

In one embodiment, the verification unit includes:

the data acquisition subunit is used for acquiring the identity authentication information data of the first application account;

the data comparison subunit is used for carrying out data comparison on the data to be verified and the identity authentication information data;

and the verification determining subunit is used for determining a verification result of the first application account based on the comparison result.

Correspondingly, an embodiment of the present application further provides a storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the account deregistration method shown in the embodiment of the present application.

Correspondingly, an embodiment of the present application further provides a computer device, which includes a memory, a processor, and a computer program that is stored in the memory and can be run on the processor, where the steps of the account logout method shown in the embodiment of the present application are implemented when the processor executes the computer program.

The method and the device for verifying the account number can receive an account number verification request, wherein the account number verification request comprises data to be verified of a first application account number; determining an account identifier having a mapping relation with the first application account in a unified account system according to the account verification request, wherein the account identifier is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications; based on the data to be verified, performing identity verification on the first application account to obtain a verification result; receiving an account logout request of a first application account passing verification, wherein the account logout request carries logout application time information of the first application account; performing logout rule matching on the first application account based on the logout application time information and account login record information of the first application account to determine a logout attribute of the first application account; and when the logout attribute of the first application account is logout, removing the mapping relation between the first application account and the account identifier so as to logout the first application account.

The scheme completes account logout in a thorough and light mode, can improve account logout efficiency, and is beneficial to account management. Specifically, according to the scheme, before the account is cancelled, the identity of the account to be cancelled is checked, so that the safety of the account cancellation in the subsequent process is improved. In addition, after the account number cancellation cold-quiet period is calculated according to the cancellation application time information of the account number to be cancelled, all operations related to account number cancellation in the account number cancellation cold-quiet period can be processed in a unified mode by using the advantages of the unified account number system without paying attention by an application party. Furthermore, the scheme solves the data related to account logout from an account bottom layer, and realizes account logout by removing the mapping relation between the account to be logout and the account identifier corresponding to the account to be logout in the unified account system, so that the user privacy data in the application can be completely anonymized on the premise of not considering the data logic in the application and not causing invasion to the application logic.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a scene schematic diagram of an account logout method according to an embodiment of the present application;

fig. 2 is a flowchart of an account deregistration method according to an embodiment of the present application;

fig. 3 is a schematic view of an account logout entry of an account logout method according to an embodiment of the present application;

fig. 4 is a schematic view illustrating logout content of an account according to an logout method provided in an embodiment of the present application;

fig. 5 is a schematic view of an account verification interface of an account logout method according to an embodiment of the present application;

fig. 6 is a schematic diagram illustrating a cancellation application submission result of an account cancellation method according to an embodiment of the present application;

fig. 7 is a schematic diagram illustrating a system prompt of an account logout method according to an embodiment of the present application;

fig. 8 is a schematic view illustrating an account logout flow of an account logout method according to an embodiment of the present application;

fig. 9 is another flowchart illustrating an account deregistration method according to an embodiment of the present application;

fig. 10 is a schematic view of a logout scheme architecture of an account logout method according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of an account deregistration apparatus according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of an account deregistration device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of an account deregistration device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of an account deregistration device according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of an account deregistration device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of an account deregistration device according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of a computer device provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The embodiment of the application provides an account logout method and device. Specifically, the embodiment of the present application provides an account logout apparatus suitable for a computer device. The computer device may be a server or a terminal. Specifically, the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a CDN, a big data and artificial intelligence platform, and the like. The terminal may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like. The terminal and the server may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.

The embodiment of the application will be introduced by taking an account logout method as an example of execution of the account logout method by a server.

Referring to fig. 1, an account logout system provided by the present application may be run on a server 10, and in particular, the server 10 may receive an account verification request, where the account logout request may include data to be verified of a first application account, the account verification request may be sent by an application running on a terminal or a server, and the application may be an application providing an account registration or logout function, such as a game application, an Instant Messaging (IM) application, a video application, a tool application, and the like. For the application providing the account registration or cancellation function, before cancellation of the account, the operation of the account cancellation application is determined to be safe and credible by checking the identity of the account to be cancelled.

Subsequently, the server 10 may determine, according to the received account verification request, an account id in the unified account system, which has a mapping relationship with the first application account, where the account id is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications.

In practical applications, when a user uses a first application for the first time, the user can use the existing account number of the user on a second application to quickly complete registration or login of the user on the first application. Therefore, the first application account of the user in the first application and the second application account of the user in the second application are application accounts belonging to two different applications. In consideration of protection of user privacy data and operation and maintenance of the applications, the applications may generate account identifiers for the second application account, and map the account identifiers to the first application account of the user in the first application by using the unified account system.

For example, when a user first enters a game application, the user can use the account number of the user existing in the IM application to quickly complete the registration and login operation in the game application. The game account of the user in the game is a first application account, the IM account of the user in the IM application is a second application account, and when the user uses the IM account to rapidly log in the game, the unified account system can generate the game account of the user in the game application based on the account identification of the IM account of the user.

Further, after receiving the account verification request, the server 10 may perform identity verification on the first application account based on the data to be verified carried in the account verification request, so as to obtain a verification result. Optionally, the server 10 may return the verification result to the account verification requester.

Then, the server 10 may receive an account logout request of the verified first application account, where the account logout request may carry logout application time information of the first application account. And, the server 10 may perform logout rule matching on the first application account based on the logout application time information and the account login record information of the first application account to determine a logout attribute of the first application account.

After determining the logout attribute of the first application account, the server 10 may remove the mapping relationship between the first application account and the account id to logout the first application account when the logout attribute is logout capable.

In another embodiment, the account deregistration method can be jointly executed by the terminal and the server.

Referring to fig. 1, a first application may run on a terminal 20, and a user may send an account verification request of a first application account to a server 10 through the terminal 20, where the account verification request includes data to be verified of the first application account.

Accordingly, after receiving the account verification request, the server 10 may determine, according to the account verification request, an account identifier having a mapping relationship with the first application account in the unified account system, where the account identifier is generated based on the second application account, and the first application account and the second application account are application accounts belonging to two different applications.

Subsequently, the server 10 may perform identity verification on the first application account through the data to be verified, and send an obtained verification result to the terminal 20, so that the terminal 20 may send an account logout request of the verified first application account to the server 10 when the verification is passed, where the account logout request carries logout application time information of the first application account.

Further, the server 10 may perform logout rule matching on the first application account based on the logout application time information and the account login record information of the first application account to determine a logout attribute of the first application account, and when the logout attribute is logout capable, may cancel the mapping relationship between the first application account and the account identifier to implement logout of the first application account.

The following are detailed below. It should be noted that the following description of the embodiments is not intended to limit the preferred order of the embodiments.

The account logout method provided by the embodiment of the application can be executed by a server or a terminal, or can be executed by both the server and the terminal; the account logout method is described in the embodiment by taking a server as an example, specifically, the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a CDN, a big data and artificial intelligence platform. The terminal may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like. The terminal and the server may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.

In the embodiment of the application, the method can be executed by an account deregistration device integrated in a server. As shown in fig. 2, the specific flow of the account deregistration method may be as follows:

101. receiving an account number checking request, wherein the account number checking request comprises data to be checked of a first application account number.

An Application (APP) may be a computer program that performs one or more specific tasks. The application may run in user mode, may interact with a user, and may have a visual user interface.

For example, applications may include applications for social interaction, query tools, entertainment, and so forth; for example, the social application may include an IM application, the query tool application may include a search engine, the entertainment application may include a gaming application, and the like.

The account (ID) is also called an Identity Document or a serial number, and is a relatively unique code in a certain system, which is equivalent to an "Identity card" in a specific object, and the Identity identification number is generally unchanged, and as for what is used to identify the object, the Identity identification number can be determined by a rule set by a designer. Generally, the rule has a certain subjectivity in design according to a specific use environment, such as "employee job number", "identification number", "computer address", and the like.

In this embodiment, the application type of the first application may not be limited, for example, the first application may be a social application, a query tool application, or an entertainment application, and so on. Accordingly, the first application account may be an ID used by the user in the first application, for example, when the first application is a game application, the first application account may be a game ID of the user in the game application.

It is noted that the first application may provide a function of account registration or account deregistration in order to manage the user of the application.

The account registration may be performed in various ways, and may include, for example, quick registration and real-name registration. The fast registration is opposite to the real-name registration, and refers to a mode that a registered user can experience the application in advance without filling in authentication information. The real-name registration can comprise a real-name authentication step, so that the authenticity of user data can be verified and checked through the real-name authentication, and the establishment of a perfect and reliable internet credit basis is facilitated.

In this embodiment, before performing account logout on the first application account, account verification may be performed on the first application account first to implement identity verification on the user, so as to ensure the security of a subsequent logout procedure. The account number verification can be performed in various ways, for example, by comparing the identity card number and the name authenticated by the user with the real name; as another example, the bank card number and name may be authenticated by comparing the user's real name, and so on.

Therefore, when the first application runs on the server or the terminal, to perform account verification on the first application account, the server or the terminal may send an account verification request to the server performing account verification, so that the server performing account verification may correspondingly receive the account verification request, where the account verification request may include data to be verified of the first application account. Specifically, the data to be verified may include data required for performing account verification, for example, the data may include application identifier information that identifies the first application, such as an application name and an application version; the method comprises checking related information in an account checking request, such as account information of a first application account, request submission time information of the account checking request, a user identity card number and a user name to be checked, or a bank card number and a user name to be checked; and so on. Specifically, the step "receiving an account verification request, where the account verification request includes data to be verified of a first application account" may include:

sending unified account number logout page data including logout verification process data to the terminal so that the terminal displays a unified account number logout page;

when the terminal carries out a logout identity verification process based on the unified account logout page and completes logout identity verification, an account verification request is received, wherein the account verification request carries data to be verified, which is acquired in the logout identity verification process.

The unified account logout page can be a universal page with a unified logout User Interface (UI) provided by the scheme, and the unified account logout page can include a plurality of logout verification processes, so that the server can send unified account logout page data including the logout verification process data to the terminal, so that the terminal can display the unified account logout page.

For example, the unified account logout page may be in a hypertext 5.0 (hypertext Markup language5.0, H5) product form, which may include a plurality of logout verification procedures, for example, a logout agreement display page may be included for displaying information such as an account logout interpretation during a cool and quiet period and an automatic logout procedure cancellation for logging in a game during the cool and quiet period; for another example, a logout application page may be included, which is used for a user to fill in an identity card number and a name number, or a bank card number and a name number, so as to perform real-name authentication and comparison and ensure authenticity of the user identity; as another example, various logout status cues may be included, including un-logout, logout in, logout cancelled, logout successful, and so on; and so on.

The consolidated account logout page may include a plurality of logout verification processes, so that the server may send consolidated account logout page data for showing the consolidated account logout page to the terminal, and the consolidated account logout page data may include logout verification process data for showing the logout verification processes.

In one embodiment, the first application running on the terminal may be a game application, and the server side may send unified logout page data including logout verification process data to the game application, so that the terminal presents a unified logout page in the form of H5.

In this embodiment, the unified account deregistration page may be in the form of a product of H5, and the gaming application on the terminal may quickly access the H5 product for performing account deregistration by setting a portal in the game so that the user's account deregistration operation can be initiated at the in-game portal. Referring to fig. 3, after entering a game, a user may trigger an application setting control in the game, such as a "setting" button shown as 201 in fig. 3, and further trigger a system setting control in the game, such as a "system setting" button shown as 202 in fig. 3, and after entering a system setting, trigger a terminal to pull up a unified account logout page by triggering an account logout initiation control, such as an "account logout" button shown as 203 in fig. 3.

Furthermore, after the game client pulls up the unified account logout page, a logout verification process can be entered. Referring to fig. 4, the unified account deregistration page may include several deregistration verification processes, and specifically, the user may sequentially read "account deregistration condition" shown in 204, "account deregistration protocol" shown in 205, and "deregistration required to be known" shown in 206 in fig. 4, and enter the account verification process by triggering a deregistration agreement control shown in 209 after checking "i have satisfied the above deregistration condition" shown in 207 and "i have read in detail and agreed to" game account deregistration protocol "shown in 208.

Referring to fig. 5, the logout identity verification process may be shown in a form of a real-name authentication interface shown in 210, in the interface, a user may input an identity card number through a certificate input control shown in 211, input a name through a name input control shown in 212, and trigger a logout initiation control shown in 213 to send an account verification request to the server, where the account verification request may include data to be verified of a game account, for example, in this embodiment, the account verification request may include the identity card number data input by the user in the real-name authentication interface 210 and the input name data.

It should be noted that, in this embodiment, the triggering manner of each control may include clicking, touch-screen, voice-control, and the like, and the display manner of each control may be an icon, a small window, a sub-page, and the like, which is not limited in this scheme.

Therefore, when the terminal performs a logout identity verification process based on the unified account logout page and completes the logout identity verification process, the server may receive an account verification request, and the account verification request may carry data to be verified acquired in the logout identity verification process.

102. According to the account checking request, account identification which has a mapping relation with a first application account in a unified account system is determined, wherein the account identification is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications.

The unified account system may be an account system designed for accessing a first application to a second application, where the first application and the second application are two different applications, and correspondingly, the first application account and the second application account are application accounts belonging to the two different applications. There may be various ways of determining whether the two applications are different applications, for example, an application with a different application name may be determined as a different application, for example, WeChat and QQ may be determined as different applications; for another example, an application with a different application name and version name may be determined as a different application, for example, a WeChat version 1.0 and a WeChat version 2.0 may be determined as different applications; and so on.

In practical applications, the second application may have an attribute of an open platform, that is, the second application may have an attribute of a user login, and the second application may have its own account system, which is a login applicable to other applications. For example, in this embodiment, the account system of the second application may be applied to login in the first application, for example, the second application may be a social platform application based on a social relationship chain, the first application may be a game application, and when a user wants to use or log in the game application, the user may select to login based on the account of the user in the social platform application.

When the user uses or logs in the first application based on the account number of the user in the second application, the account number of the user in the second application and related data may not be exposed to the first application in consideration of protecting the privacy of the user and application data, but an account number identifier may be generated based on the account number of the user in the second application, so that the unified account number system may generate the ID of the user in the first application, that is, the first application account number, according to the account number identifier.

It is to be noted that, in this embodiment, an account of the user in the second application, that is, the second application account, and the account identifier may have a strong correlation mapping relationship, that is, the second application account of the user and the account identifier may have a one-to-one mapping relationship, so that if the account of the user in the second application is not changed, the account identifier of the second application account cannot be changed or deleted.

The unified account system may generate a unique ID of the user in the first application, that is, the first application account, based on the account ID of the second application account, so that a mapping relationship exists between the generated first application account and the account ID, and the relationship may be a weak-correlation mapping relationship, that is, the mapping relationship between the first application account and the account ID may be changed or modified, and one first application account may establish a mapping relationship with one or more account IDs.

In step 102, since the account information of the first application account is carried in the account verification request, after the server acquires the account verification request, the server may extract the first application account from the account verification request, and further determine an account identifier in the unified account system, where the account identifier has a mapping relationship with the first application account.

For example, in an embodiment, the first application is a game application, the second application is an IM application with an open platform attribute, and the first application account of the user in the first application may be recorded as GopenID, and the second application account of the user in the second application may be recorded as IMID. Since the IM application belongs to an open platform, when a user uses or logs in a game application using its IMID in the IM application, the unified account system obtains an account identifier (which may be denoted as OpenID) provided by the IM application, and generates a GopenID based on the OpenID for the user to use. Subsequently, when the user wants to log off his GopenID in the game application, an account verification request may be submitted to the server by following the steps shown in fig. 3 to 5, so that the server may accordingly acquire the account verification request and perform account verification based on the account verification request subsequently. That is, OpenID may be a user identification provided by an open platform, and GopenID may be an in-game unique ID generated for an open platform ID by a unified account.

103. And based on the data to be verified, performing identity verification on the first application account to obtain a verification result.

The identity verification can be used for ensuring the authenticity of the identity of the logout user, so that the security of the logout of the account is improved, and the mistaken logout is avoided. For example, the data to be verified may be compared with the authenticated identity authentication information data to determine whether the data to be verified is verified successfully, and the like. Specifically, the step "performing identity verification on the first application account based on the data to be verified to obtain a verification result" may include:

acquiring identity authentication information data of a first application account;

comparing the data to be verified with the identity authentication information data;

and determining a verification result of the first application account based on the comparison result.

The identity authentication information data may be authenticated identity information data, and the authenticated identity information data is useful for authenticating the user. For example, the authentication information data may include authenticated identification number information and name information; as another example, authenticated bank card number information and name information may be included; as another example, authenticated facial feature information may be included; as another example, authenticated fingerprint characteristic information, voice characteristic information, and the like may be included.

The method for acquiring the identity authentication information data can be various, for example, the server can extract from the stored data table entry; for another example, the server may request acquisition from a related department or a central control system storing the identity authentication information data; as another example, the retrieval may be by requesting from the user; and so on.

After the server acquires the identity authentication information data and the data to be verified, the server can compare the data to be verified with the identity authentication information data to determine a verification result of the first application account. After the comparison result between the data to be verified and the identity authentication information data is obtained, the verification result of the first application account can be determined, for example, if the comparison result between the data to be verified and the identity authentication information data is a comparison pass, the verification result of the first application account can be determined as a verification success, and if the comparison result is a comparison fail, the verification result of the first application account can be determined as a verification failure, or a verification result needs to be further determined through manual processing.

It should be noted that, after determining the verification result of the first application account, the server may also send the verification result to the terminal, so that the terminal may perform interaction with the user based on the verification result. For example, in an embodiment, after the server sends the verification result that the verification passes to the terminal, the terminal may display a "logout application submission success" display page shown in fig. 6, so that the user may know that the account verification passes and the information that the account logout application is successfully submitted. Further, as shown in fig. 6, the user may be prompted, where the account has a lock period (a cool and quiet period) with a certain duration (e.g., 60 days), and the user does not log in and use the account during the lock period, so as to ensure that the account is successfully logged out, otherwise, the user is regarded as canceling the logout application.

Accordingly, when the user returns to the initial game page shown in FIG. 7 by triggering the completion control shown at 214 in FIG. 6, and prompting in the initial game page: and (4) the user account logout application is successfully submitted, and the user account logout application is to return to the game login interface. Therefore, the game application does not need to independently develop the whole UI interaction flow for account logout, can pull up the unified account logout page provided by the scheme in the game by providing the entrance, and returns the unified account logout page to the game after executing the logout verification flow provided by the scheme, so that the logic in the game is not invaded, and a game party does not need to independently develop the whole UI interaction flow. In the above example, the first application is taken as a game application, and the first application may also be taken as another application, so similarly, the unified account logout page provided by the present solution can be free from intruding logic in the first application, and the first application does not need to separately develop the whole UI interaction flow.

104. And receiving an account logout request of the first application account which passes the verification, wherein the account logout request carries logout application time information of the first application account.

The account logout may be a process of, when a user using the first application or a registered user no longer accepts an application protocol provided by the first application or no longer uses a service provided by the first application, logging out the account of the user using the user or the registered user to terminate the application protocol between the user using the user or the registered user and the first application, and deleting or anonymizing the first application account of the user using the user or the registered user in the first application.

When the terminal learns that the identity verification result of the first application account is verified, the terminal can further send an account logout request for the first application account to the server, and accordingly, the server can receive the account logout request of the verified first application account.

The account logout request may include a plurality of information items, for example, application flag information for marking the first application, such as an application name, an application version, and the like; the method comprises the logout related information in an account logout request, such as account information of a first application account and logout application time information of the account logout request; and so on.

Specifically, the logout application time information may be time information corresponding to when the terminal successfully submits the account logout request, or time information corresponding to when the server obtains the account logout request. The time information may include specific time information items such as year, month, day, hour, minute, second, and the like, and for example, the time information may be in a data format of a timestamp.

105. And performing logout rule matching on the verified first application account based on the logout application time information and the account login record information of the first application account to determine the logout attribute of the first application account.

The logout attribute can be used to describe whether the verified first application account can be logged out. The value of a logout attribute may include a variety of circumstances, for example, a logout attribute may be logout-capable or not logout-capable; for another example, a logout attribute may be logout, pending manual review, or not logout; and so on.

The logout rule may describe a rule that a first application account that can be logged out should comply with. For example, the logout rule may be that the first application account is not used or logged in to the first application all the time during and after the expiration of the cool quiet period; for another example, the logout rule may be that the first application uses or logs in the first application in the cold quiet period and after the cold quiet period expires, and all the applications do not use or log in the periphery of the first application all the time; and so on. And performing logout rule matching on the verified first application account, which can be used for determining the logout attribute of the first application account.

In this embodiment, the logout rule matching is performed on the first application account which passes the verification, and whether the first application account matches the logout rule or not can be determined according to the logout application time information and the account login record information of the first application account.

Specifically, the unified account logout page provided by the present solution may be in a product form of H5, and when the terminal completes account verification on the first application account through the H5 page provided by the present solution, and after the verification passes, the terminal can apply for logout of the first application account that passes the verification through the H5 page, and can report logout information of the first application account to the "TDW application logout table" of the data warehouse through a data reporting component (i.e., "TGLOG" component in fig. 8) by calling an interface provided by the unified account system (i.e., "GACC" in fig. 8), and acquire account login record information of the first application account through acquiring the "TDW full service login table" in the data warehouse, so as to perform logout rule matching on the first application account that passes the verification.

It should be noted that the logout rule may be a logout condition shown in fig. 8, that is, the day when the user submits the account logout request may be denoted as day 0, and if the user does not use or log in the first application through the first application account in days 0 to 60, and the time when the user finally uses or logs in the first application through the first application account in day 0 is earlier than the time when the user submits the account logout request, the logout attribute of the first application account may be considered as being logout.

Further, after obtaining the logout application time information and the account login record information of the first application account passing the verification, the logout attribute of the first application account can be determined by performing logout rule matching on the first application account. Specifically, the step of performing logout rule matching on the first application account based on the logout application time information and the account login record information of the first application account to determine a logout attribute of the first application account may include:

determining the first application account passing the verification as a candidate logout account for performing account logout;

calculating an account cancellation cold quiet period of a candidate cancellation account and an account cancellation buffer period of the cancellation account after the account cancellation cold quiet period according to cancellation application time information of the candidate cancellation account;

information query is carried out in an account login record table of a first application to obtain a first login record of a candidate logout account in an account logout cold quiet period and a second login record of the candidate logout account in an account logout buffer period;

and performing logout rule matching on the candidate logout account number based on the first login record and the second login record so as to determine the logout attribute of the candidate logout account number.

Even if the first application account passes the verification, the first application account does not represent that the first application account passes the verification, but needs to be further subjected to logout rule matching to determine whether the first application account can be logout, so that the first application account passing the verification can be determined as a candidate logout account for logging out the account.

The account cancellation cold quiet period may be an account retention period agreed with a user who submits a cancellation application, and specifically, after the user submits the account cancellation application, the account retention period of a certain duration may be provided for the user. Within the account retention period, relevant information, such as head portrait information, nickname information, and the like, of the first application account subjected to anonymization processing is not deleted, and if a user repels the decision of account logout within the account retention period and uses or logs in the first application through the first application account, the user can be considered as revoking the account logout application.

The duration of the account number logout of the cool quiet period may be set based on service requirements, for example, the duration may be 30 days, or 60 days, or 90 days, and the like, which is not limited in this application.

The account logout buffer period can be used for cancelling logout of the first application account for the user when the user still detects the use behavior of the first application account when the first application account is logout after the first application account meets the logout requirement of the account logout cold quiet period. Therefore, the account logout buffer period is set after the account logout cool-quiet period, and the duration of the account logout buffer period may be set to be shorter than the account logout buffer period, such as 1 day, or 2 days, and so on.

In this embodiment, the account deregistration cold quiet period may be set to 60 days, and the account deregistration buffer period may be set to 2 days, so that if the day on which a candidate deregistration account submits an account deregistration request is recorded as day 0, the account deregistration cold quiet period of the candidate deregistration account may be calculated to be day 60, and the account deregistration buffer period is day 62.

After the account number cancellation cold quiet period of the candidate cancellation account number and the account number cancellation buffer period of the cancellation account number after the account number cancellation cold quiet period are determined through calculation, information query can be carried out in an account number login record table of a first application, so that a first login record of the candidate cancellation account number in the account number cancellation cold quiet period and a second login record of the candidate cancellation account number in the account number cancellation buffer period are obtained.

There are various ways to perform information query, for example, the information query may be performed by looking up a table, for example, referring to fig. 8, by looking up in "TDW full service log table".

It should be noted that, if the candidate logout account has an account login behavior in the account logout cold quiet period, the first login record is not null, otherwise, if the candidate logout account has no account login behavior in the account logout cold quiet period, the obtained first login record may be null. Similarly, if the candidate logout account has an account login behavior in the account logout buffer period, the first login record is not null, otherwise, if the candidate logout account has no account login behavior in the account logout buffer period, the obtained first login record may be null.

After the first login record and the second login record are obtained, the logout attribute of the candidate logout account can be further determined based on the first login record and the second login record. Specifically, the step of performing logout rule matching on the candidate logout account based on the first login record and the second login record so as to determine the logout attribute of the candidate logout account. ", may include:

comparing the first login record with the second login record to determine account login behavior information of the candidate logout account after an account logout application is submitted;

and when the account login behavior information matches the logout rule of the first application, determining the logout attribute of the candidate logout account as being logout.

The account login behavior of the candidate logout account in the account logout cool-quiet period can be determined through the first login record, and the account login behavior of the candidate logout account in the account logout buffer period can be determined through the second login record, so that whether the account login is happy or not in the period from the time when the candidate logout account is submitted to logout of the account by the server can be determined through the first login record and the second login record.

For example, if the first login record and the second login record of the candidate logout account are both null values, it may be determined that there is no account login behavior for the candidate logout account within a period from when the account logout application is submitted to before the server performs account logout; if the first login record or the second login record of the candidate logout account is a non-null value, it can be determined that the candidate logout account has an account login behavior in a period from the time when the account logout application is submitted to the time when the server executes account logout; and so on.

After determining account login behavior information of the candidate logout account and the logout rule of the first application, whether the logout attribute of the candidate logout account can be logged out can be determined.

For example, the logout rule may be that the logout attribute of a candidate logout account is determined to be logout only when the candidate logout account has no account login behavior in the account logout cool-quiet period and the account logout buffer period. If the first login record and the second login record of the candidate logout account are displayed, the candidate logout account has no account login behavior in the account logout cold quiet period and the account logout buffer period, and the logout attribute of the candidate logout account can be determined to be logout; otherwise, it can be determined that the logout attribute of the candidate logout account is not logout.

106. And when the logout attribute of the first application account is logout, removing the mapping relation between the first application account and the account identification so as to logout the first application account.

When the logout attribute of the first application account passing the verification is determined to be logout, the first application account can be logout, and because the first application account and the account identifier have a weak correlation mapping relationship and the account identifier and the second application account have a strong correlation mapping relationship, the logout of the first application account can be realized by removing the mapping relationship between the first application account and the account identifier. Specifically, the step "when the logout attribute of the first application account is logout capable, removing the mapping relationship between the first application account and the account identifier to logout the first application account" may include:

determining a first application account which can be logged out as a target logging-out account to be logged out;

generating a mapping relation removing request aiming at a target logout account;

and sending a mapping relation removing request to the unified account system to trigger the unified account system to remove the mapping relation between the target logout account and the account identifier.

After determining that the logout attribute of the first application account is logout, the first application account is determined to be a logout account, so that the logout account can be determined to be a target logout account.

The method comprises the steps of canceling a mapping relation between a target cancellation account and an account identifier to perform account cancellation on the target cancellation account, wherein the mapping relation is established through a unified account system, so that a mapping relation cancellation request aiming at the target cancellation account can be generated, the mapping relation cancellation request is sent to the unified account system to trigger the unified account system to cancel the mapping relation between the target cancellation account and the account identifier, and therefore cancellation of the target cancellation account is achieved.

For the unified account system, the removal of the mapping relationship between the target logout account and the account flag may include processing steps in various situations. For example, when the first application is a game application, referring to fig. 8, a game account that meets the logout condition may be added to a "confirmed logout table", such as "PostgreSQL confirmed logout table", "TDW confirmed logout table 1", and "TDW confirmed logout table 2" in fig. 8 "

The method comprises the steps that a game account meeting logout conditions in a PostgreSQL check logout table is subjected to number sealing processing, specifically, a service security number sealing interface is called to realize the process, further, account information of the game account can be sent to a storm of a real-time account logout calculation platform, so that real-time account logout calculation is carried out through the storm, and a logout interface of a unified account system is called subsequently to logout the game account.

For the game account numbers meeting the logout conditions in the "TDW confirmed logout table 1" and the "TDW confirmed logout table 2", the game account numbers may be added to a message queue, for example, kafka (kafka is a high-throughput distributed publishing and subscribing message system), so that the game account numbers are sent to a real-time processing platform, for example, storm (strom is an open-source distributed real-time big data processing framework), through the message queue; and then call the logout interface of the unified account system to logout the game account; it should be noted that a more detailed verification step may be further included, in which the game accounts meeting the logout conditions in the "TDW confirmed logout table 1" and the "TDW confirmed logout table 2" are added to the "PostgreSQL notification table 2" for more detailed verification, and the game accounts meeting the logout conditions are added to kafka only when the verification is consistent.

It should be noted that, in an actual application, besides account deregistration can be performed on a target deregistered account that can be deregistered, a plurality of cases of processing steps may be included for a deregistered account whose deregistration attribute is a candidate that cannot be deregistered or that cannot be deregistered. For example, when the first application is a game application, referring to fig. 8, account information of a logout attribute as a candidate logout account that cannot be logged out or that cannot be logged out may be added to a "cancel logout table", such as "PostgreSQL cancel logout table", "TDW cancel logout table 1", and "TDW cancel logout table 2" in fig. 8.

For the postgreSQL cancel logout table, if the logout attribute of a candidate logout user is that the logout cannot be logout, canceling the account logout application of the candidate logout user directly by calling a logout cancellation interface of the unified account system; if the logout attribute of the candidate logout user is not logout, that is, the candidate logout account is still in the account logout cold period, and there is no account login behavior so far, then the account information of the candidate logout account can be added to the PostgreSQL notification table 1, and polling is performed at a certain period, such as one day, until the candidate logout account meets the condition, and then the corresponding operation is performed.

For candidate logout accounts whose logging attribute is not logout or can not be logout in the TDW logout canceling table 1 and the TDW logout canceling table 2, the candidate logout accounts can be saved in a data warehouse as data backup, and can be added to the PostgreSQL notification table 2 to perform more detailed verification, so that manual processing is performed when the verification is inconsistent.

In addition, considering that there may be an illegal user who wants to bypass the mark sealing penalty by logging out the account after being marked, before the step "sending a mapping relationship release request to the unified account system to trigger the unified account system to release the mapping relationship between the target logged-out account and the account id", the method may further include:

acquiring the account state of a target logout account;

requesting a unified account system to generate a third application account to be distributed for the account identifier, wherein the third application account and a target logout account are application accounts belonging to the same application;

and determining an account activation triggering event of the third application account according to the account state.

The account state of the target logout account can be used for describing the current state of the target logout account before performing account logout on the target logout account, for example, the account state of the target logout account can be a normal state, which represents that the account does not have any illegal operation currently and belongs to a normal account; for another example, the target logout account can be in a violation state, which represents that the account currently has an unprocessed violation operation and belongs to a violation account; and so on.

Further, the unified account system may be requested to generate a third application account to be allocated for the account identifier, where the account identifier and the target logout account currently have a mapping relationship, and the third application account and the target logout account are application accounts belonging to the same application.

Therefore, the generated account activation triggering event of the third application account can be determined according to the account state of the target logout account. For example, if the account status of the target account logout is a cover number status, since it is to be avoided that the illegal account in the cover number status bypasses the cover number penalty by the account logout, it may be determined that the account activation triggering event of the third application account is: when the number marking punishment is completed and after the target logout account number is completely logged out, if the situation that the user re-registers or uses the first application based on the account number identification is detected, the third application account number can be activated, and the weak correlation mapping relation between the third application account number and the account number identification is established so as to distribute the third application account number to the user for use, thereby generating a brand new account number in the first application for the user.

For another example, if the account status of the target logout account is a normal status, it may be determined that the account activation triggering event of the third application account is: after the target logout account is logged out, if the user is detected to re-register or use the first application based on the account identifier, activating the third application account, and establishing a weak correlation mapping relation between the third application account and the account identifier so as to distribute the third application account to the user for use, thereby generating a brand new account for the user in the first application; and so on.

Therefore, the account activation triggering event of the third application account to be distributed is set based on the account state of the target logout account, so that the illegal account in the seal number state can be prevented from bypassing the seal number punishment through account logout, and then account logout is carried out on the target logout account with the logout attribute being logout, and the safety and the comprehensiveness of the scheme are greatly improved.

Additionally, since it is contemplated that the first application may have associated peripheral components, for example, when the first application is a gaming application, its associated peripheral components may include: the method comprises the following steps that a WeChat or mobile phone QQ, a game center, a Midamask, a marketing activity department, a market department and the like are adopted, so that in addition to account logout of a first application account in a unified account system, data cleaning of peripheral components can be considered, and specifically, after a mapping relation removing request is sent to the unified account system to trigger the unified account system to remove a mapping relation between a target logout account and an account identifier, the method also comprises the following steps:

determining a peripheral component of a first application;

generating a data cleaning request aiming at the peripheral component, wherein the data cleaning request carries account information of a target logout account;

and sending a data cleaning request to the peripheral component to trigger cleaning of the application related data of the target logout account in the peripheral component based on the account information.

The peripheral component may be a component related to the first application, and the related component may have various forms, for example, the peripheral component may be an application, or a department and a service related to a business. For example, when the first application is a game application, referring to fig. 8, the peripheral components of the game application may include: WeChat or cell phone QQ, game center, Midamen, marketing department, pleasure platform, business security services, and so on. Since the peripheral component is closely related to the first application, upon determining the first application, the peripheral component of the first application may be determined.

For data cleaning of a target logout account in a peripheral component, after a unified account system finishes logout of the target logout account, a notification service of each peripheral component of a first application is called to inform that the target logout account is logout, and the peripheral component is requested to clear all game related data of the account. Specifically, a data cleaning request for the peripheral component may be generated, where the data cleaning request carries account information of the target logout account, and the data cleaning request may be sent to the peripheral component to trigger cleaning of application-related data of the target logout account in the peripheral component based on the account information.

As can be seen from the above, the present embodiment may receive an account verification request, where the account verification request includes data to be verified of a first application account; determining an account identifier having a mapping relation with the first application account in a unified account system according to the account verification request, wherein the account identifier is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications; based on the data to be verified, performing identity verification on the first application account to obtain a verification result; receiving an account logout request of a first application account passing verification, wherein the account logout request carries logout application time information of the first application account; performing logout rule matching on the first application account based on the logout application time information and account login record information of the first application account to determine a logout attribute of the first application account; and when the logout attribute of the first application account is logout, removing the mapping relation between the first application account and the account identifier so as to logout the first application account.

The scheme can complete account logout in a thorough and light mode, can improve account logout efficiency, and is beneficial to account management. Specifically, according to the scheme, before the account is cancelled, the identity of the account to be cancelled is checked, so that the safety of the account cancellation in the subsequent process is improved. In addition, after the account number cancellation cold-quiet period is calculated according to the cancellation application time information of the account number to be cancelled, all operations related to account number cancellation in the account number cancellation cold-quiet period can be processed in a unified mode by using the advantages of the unified account number system without paying attention by an application party. Furthermore, the scheme solves the data related to account logout from an account bottom layer, and realizes account logout by removing the mapping relation between the account to be logout and the account identifier corresponding to the account to be logout in the unified account system, so that the user privacy data in the application can be completely anonymized on the premise of not considering the data logic in the application and not causing invasion to the application logic.

And the scheme designs a unified logout UI, for example, an application party can rapidly access in an H5 mode without extra development amount and only needs to set an entrance in the application. Therefore, the scheme helps the application to realize the account logout function on the premise of not invading any application logic, and accelerates the application compliance audit and online speed.

In addition, the scheme can directly generate a new account for the logged-off user, so that the old account can not be associated completely, and the user privacy data in the application can be anonymized completely without considering the complex data logic in the application. In addition, for peripheral components of the application, the scheme also provides a callback mode through unified binding, triggers each component to do special logic, and clears away some necessary data, so that the account number logout is more thorough.

The method described in the above examples is further described in detail below by way of example.

In this embodiment, an account logout apparatus is integrated in a server and a terminal, for example, the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a CDN, and a big data and artificial intelligence platform. The terminal may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like. The terminal and the server may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.

As shown in fig. 9, a method for logging out an account includes the following specific processes:

301. the terminal sends an account number checking request to the server, wherein the account number checking request comprises data to be checked of the first application account number.

In an embodiment, the first application is a game application, and the game application only needs to realize an entry for canceling one account, and the rest of the processes can be completed by the scheme. Referring to fig. 10, the deregistration scheme provided by the present solution includes four layers: the method comprises the steps of logging out the UI of the account, logging out the real-time processing assembly, logging out the off-line processing assembly and unifying the account assembly.

The account logout UI layer is in a direct product form and is directly interacted with a user, and the key point of the layer design is that a game UI logic is not invaded, game customization is supported, and flexible and rapid iteration can be realized, so that the account logout UI layer can be realized in an H5 page mode. For the game client, the whole logout process can be entered only by setting a logout entry in the game and then pulling up the logout H5. Due to the fact that the protocol is cancelled and some documentations may change frequently, the advantage of H5 is achieved, the game does not need to update the client, the user does not feel at all, protocol hot update, UI hot update and documentary hot update can be achieved, and the game is convenient and flexible. In addition, because the H5 scheme supports the embedded function of the user-defined UI, the personalized requirements of the service can be met to a great extent while the UI is unified, the cancellation flow is standardized, and the characteristics of the service are not lost.

Therefore, the terminal can acquire the data to be verified of the first application account through the account logout UI provided by the scheme, and sends the account verification request to the server after generating the account verification request based on the data to be verified.

302. The server receives an account verification request.

303. The server determines account identification which has a mapping relation with a first application account in a unified account system according to the account verification request, wherein the account identification is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications.

In an embodiment, the first application may be a game application, and the second application may be a social application having an open platform attribute, so that the server may extract a first application account, that is, a game account of the user in the game application, from the account verification request, and determine an account identifier having a mapping relationship with the game account in the unified account system, where the account identifier is generated based on the social application.

It should be noted that the mapping relationship between the first application account and the account id may be a weakly related mapping relationship, that is, the weakly related mapping relationship may be changed or deleted, and the mapping relationship between the second application account and the account id may be a strongly related mapping relationship, that is, the strongly related mapping relationship is a one-to-one mapping relationship and may not be changed or deleted.

304. And the server performs identity verification on the first application account based on the data to be verified to obtain a verification result.

In an embodiment, referring to fig. 10, the identity verification may be performed by the logout real-time processing component to check or verify the identity information of the first application account and obtain a verification result.

It should be noted that, referring to fig. 10, the logout real-time processing component is a connection layer between a user account logout application and a back-end actual logout operation, and specifically, when the user applies for logout, the logout real-name authentication component is responsible for verifying real-name authentication information of the user, so as to effectively ensure that the logout operation is the user operation, and meanwhile, the logout operation is verified in a login state of the game, so that the security is further enhanced. After passing the verification, the user is placed into a logout queue, a special logout user table is reported, the subsequent component processes are performed, and meanwhile, the logout state information of the user is stored.

In addition, referring to fig. 10, the logout real-time processing component and the logout offline processing component undertake a core logout scheme logic, and complete a series of complex logout operations, wherein the logout real-time processing component can perform not only identity verification on the first application account, but also login state verification, logout account reporting, logout state storage, and other functions.

305. And the server sends the verification result to the terminal.

306. And the terminal receives the verification result and sends an account cancellation request aiming at the first application account passing the verification to the server when the verification result is that the verification is passed, wherein the account cancellation request carries cancellation application time information of the first application account.

307. The server receives an account logout request.

308. The server performs logout rule matching on the first application account based on the logout application time information and the account login record information of the first application account so as to determine the logout attribute of the first application account.

In an embodiment, the logout rule matching is performed on the first application account, the account logout cold quiet period is calculated according to the logout application time information of the first application account, and the logout user or the logout account is screened according to the login record information of the first application account, so as to determine whether the logout attribute of the first application account can be logout.

In one embodiment, referring to FIG. 10, the cool quiet period calculation and log off user filtering may be accomplished by a log off offline processing component. Specifically, the logout offline processing component is a key layer for logging out the account, and performs a logout calculation operation after the logout real-time processing component writes a user into a logout user table, and the logout offline processing component can complete a cold quiet period calculation and a logout user screening, and can also realize functions including sending a logout flow stop mail, logging out the user, logging out a state update, a security seal number, cleaning peripheral data, returning to a game account and the like.

309. And when the logout attribute of the first application account is logout, removing the mapping relation between the first application account and the account identifier so as to logout the first application account.

In the unified account system, a weak correlation mapping relationship exists between the first application account and the account identifier, and a strong correlation mapping relationship exists between the second application account and the account identifier, so that the first application account can be cancelled by removing the mapping relationship between the first application account and the account identifier.

In addition, the unified account system may be requested to generate a third application account to be allocated for the account identifier, so that when the user uses the first application again through the second application account in the second application after completing logout of the first application account, the third application account used in the first application may be obtained.

Therefore, referring to fig. 10, in the present embodiment, the unified account component, which serves as a basic account system for logout, may be used for an underlying technical support, and completes functions including logout of an old account and generation of a new account.

Therefore, the account logout can be completed in a thorough and light manner, the account logout efficiency can be improved, and account management is facilitated. Specifically, before the account is cancelled, the embodiment of the application performs identity verification on the account to be cancelled, so that the security of the account cancellation in the subsequent process is improved. In addition, after the account number logout cold quiet period is calculated according to the logout application time information of the account number to be logout, all operations related to account number logout in the account number logout cold quiet period can be processed in a unified mode by using the advantages of the unified account number system, and an application party does not need to pay attention. Furthermore, the account logout data is solved from the account bottom layer, and the account logout is realized by removing the mapping relation between the account to be logged out and the account identifier corresponding to the account to be logged out in the unified account system, so that the user privacy data in the application can be completely anonymized on the premise of not considering the data logic in the application and not invading the application logic.

Moreover, the account logout method provided by the embodiment of the application is independent of the implementation architecture and the version of the application, can update and iterate at any time, and is more flexible and convenient.

In order to better implement the method, correspondingly, an account logout apparatus is further provided in an embodiment of the present application, where the account logout apparatus may be integrated in a server or a terminal. The server can be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and can also be a cloud server for providing basic cloud computing services such as cloud service, a cloud database, cloud computing, cloud functions, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, big data and artificial intelligence platform and the like. The terminal may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like.

For example, as shown in fig. 11, the account deregistering apparatus may include a first receiving unit 401, a determining unit 402, a verifying unit 403, a second receiving unit 404, a matching unit 405, and a releasing unit 406, as follows:

a first receiving unit 401, configured to receive an account verification request, where the account verification request includes data to be verified of a first application account;

a determining unit 402, configured to determine, according to the account verification request, an account identifier in a unified account system, where the account identifier has a mapping relationship with the first application account, where the account identifier is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications;

the verification unit 403 may be configured to perform identity verification on the first application account based on the data to be verified to obtain a verification result;

a second receiving unit 404, configured to receive an account logout request of a verified first application account, where the account logout request carries logout application time information of the first application account;

a matching unit 405, configured to perform logout rule matching on the first application account based on the logout application time information and account login record information of the first application account to determine a logout attribute of the first application account;

a removing unit 406, configured to remove a mapping relationship between the first application account and the account id when the logout attribute of the first application account is logout capable, so as to logout the first application account.

In an embodiment, referring to fig. 12, the matching unit 405 may include:

a candidate determining sub-unit 4051, configured to determine the first application account passing the verification as a candidate logout account for performing logout;

a time calculating sub-unit 4052, configured to calculate, according to logout application time information of the candidate logout account, an account logout cold quiet period of the candidate logout account, and an account logout buffer period of the candidate logout account after the account logout cold quiet period;

the information query subunit 4053 may be configured to perform information query in an account login record table of a first application, so as to obtain a first login record of the candidate logout account in the account logout cold quiet period and a second login record of the candidate logout account in the account logout buffer period;

the rule matching sub-unit 4054 may be configured to perform logout rule matching on the candidate logout account based on the first login record and the second login record, so as to determine a logout attribute of the candidate logout account.

In an embodiment, the rule matching subunit 4054 may specifically be configured to:

In an embodiment, referring to fig. 13, the releasing unit 406 may include:

a target determining sub-unit 4061, configured to determine the first application account that can be logged off as a target logout account to be logged off;

a first generating sub-unit 4062, configured to generate a mapping relationship release request for the target logout account;

the first sending sub-unit 4063, configured to send the mapping relationship release request to the unified account system, so as to trigger the unified account system to release the mapping relationship between the target logout account and the account id.

In an embodiment, referring to fig. 14, before the sending the mapping relationship release request to the unified account system, the release unit 406 may further include:

a status acquiring sub-unit 4064, configured to acquire an account status of the target logout account;

an account request sub-unit 4065, configured to request the unified account system to generate a third application account to be allocated for the account identifier, where the third application account and the target logout account are application accounts belonging to the same application;

the trigger determining subunit 4066 may be configured to determine, according to the account status, an account activation trigger event of the third application account.

In an embodiment, referring to fig. 15, after the sending the mapping relationship release request to the unified account system, the release unit 406 may further include:

a peripheral determination subunit 4067, which may be used to determine peripheral components of the first application;

a second generating sub-unit 4068, configured to generate a data cleaning request for the peripheral component, where the data cleaning request carries account information of the target logout account;

a second sending sub-unit 4069, configured to send the data cleaning request to the peripheral component, so as to trigger cleaning of application-related data of the target logout account in the peripheral component based on the account information.

In an embodiment, referring to fig. 16, the first receiving unit 401 may include:

the page sending sub-unit 4011 may be configured to send, to the terminal, consolidated account deregistration page data including deregistration verification process data, so that the terminal displays a consolidated account deregistration page;

the request receiving sub-unit 4012 may be configured to receive an account verification request when the terminal performs a logout identity verification process based on the unified account logout page and completes logout identity verification, where the account verification request carries data to be verified, which is collected in the logout identity verification process.

In an embodiment, referring to fig. a3g, the verification unit 403 may include:

a data obtaining subunit 4031, configured to obtain identity authentication information data of the first application account;

the data comparison subunit 4032 may be configured to perform data comparison between the data to be verified and the identity authentication information data;

a verification determining subunit 4033, configured to determine a verification result of the first application account based on the comparison result.

In a specific implementation, the above units may be implemented as independent entities, or may be combined arbitrarily to be implemented as the same or several entities, and the specific implementation of the above units may refer to the foregoing method embodiments, which are not described herein again.

As can be seen from the above, in the account logout apparatus of this embodiment, the first receiving unit 401 receives an account verification request, where the account verification request includes data to be verified of the first application account; determining, by a determining unit 402, an account identifier having a mapping relationship with the first application account in a unified account system according to the account verification request, where the account identifier is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications; the verification unit 403 performs identity verification on the first application account based on the data to be verified to obtain a verification result; receiving, by a second receiving unit 404, an account logout request of a verified first application account, where the account logout request carries logout application time information of the first application account; performing logout rule matching on the first application account by a matching unit 405 based on the logout application time information and account login record information of the first application account to determine a logout attribute of the first application account; when the logout attribute of the first application account is logout, the removing unit 406 removes the mapping relationship between the first application account and the account id to logout the first application account.

In addition, the embodiment of the present application further provides a computer device, which may be a server or a terminal, where the server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, and big data and artificial intelligence platform. The terminal may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like. Fig. 17 is a schematic diagram showing a structure of a computer device according to an embodiment of the present application, specifically:

the computer device may include components such as memory 501 including one or more computer-readable storage media, input unit 502, display unit 503, audio circuitry 504, Wireless Fidelity (WiFi) module 505, processor 506 including one or more processing cores, and power supply 507. Those skilled in the art will appreciate that the computer device configuration illustrated in FIG. 17 does not constitute a limitation of computer devices, and may include more or fewer components than those illustrated, or some components may be combined, or a different arrangement of components. Wherein:

the memory 501 may be used to store software programs and modules, and the processor 506 executes various functional applications and data processing by operating the software programs and modules stored in the memory 501. The memory 501 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the computer device, and the like. Further, the memory 501 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 501 may also include a memory controller to provide the processor 506 and the input unit 502 access to the memory 501.

The input unit 502 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. In particular, in one particular embodiment, the input unit 502 may include a touch-sensitive surface as well as other input devices. The touch-sensitive surface, also referred to as a touch display screen or a touch pad, may collect touch operations by a user (e.g., operations by a user on or near the touch-sensitive surface using a finger, a stylus, or any other suitable object or attachment) thereon or nearby, and drive the corresponding connection device according to a predetermined program. Alternatively, the touch sensitive surface may comprise two parts, a touch detection means and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 506, and can receive and execute commands sent by the processor 506. In addition, touch sensitive surfaces may be implemented using various types of resistive, capacitive, infrared, and surface acoustic waves. The input unit 502 may include other input devices in addition to a touch-sensitive surface. In particular, other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 503 may be used to display information input by or provided to a user and various graphical user interfaces of the computer device, which may be made up of graphics, text, icons, video, and any combination thereof. The Display unit 503 may include a Display panel, and optionally, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch-sensitive surface may overlay the display panel, and when a touch operation is detected on or near the touch-sensitive surface, the touch operation is transmitted to the processor 506 to determine the type of touch event, and then the processor 506 provides a corresponding visual output on the display panel according to the type of touch event. Although in FIG. 17 the touch sensitive surface and the display panel are two separate components to implement input and output functions, in some embodiments the touch sensitive surface may be integrated with the display panel to implement input and output functions.

Audio circuitry 504, a speaker, and a microphone may provide an audio interface between a user and a computer device. The audio circuit 504 may transmit the electrical signal converted from the received audio data to a speaker, and convert the electrical signal into a sound signal for output; on the other hand, the microphone converts the collected sound signal into an electrical signal, which is received by the audio circuit 504 and converted into audio data, which is then processed by the audio data output processor 506 and sent to, for example, another computer device via the radio frequency circuit, or the audio data is output to the memory 501 for further processing. The audio circuitry 504 may also include an earbud jack to provide communication of peripheral headphones with the computer device.

WiFi belongs to short-range wireless transmission technology, and the computer device can help the user send and receive e-mail, browse web pages, access streaming media, etc. through the WiFi module 505, which provides wireless broadband internet access for the user. Although fig. 17 shows the WiFi module 505, it is understood that it does not belong to the essential constitution of the computer device, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 506 is a control center of the computer device, connects various parts of the entire mobile phone by using various interfaces and lines, and performs various functions of the computer device and processes data by operating or executing software programs and/or modules stored in the memory 501 and calling data stored in the memory 501, thereby performing overall monitoring of the mobile phone. Optionally, processor 506 may include one or more processing cores; preferably, the processor 506 may integrate an application processor, which mainly handles operating systems, user interfaces, applications, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 506.

The computer device also includes a power supply 507 (e.g., a battery) for powering the various components, which may preferably be logically connected to the processor 506 via a power management system that may be used to manage charging, discharging, and power consumption management functions. The power supply 507 may also include any component including one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.

Although not shown, the computer device may further include a camera, a bluetooth module, etc., which will not be described herein. Specifically, in this embodiment, the processor 506 in the computer device loads the executable file corresponding to the process of one or more application programs into the memory 501 according to the following instructions, and the processor 506 runs the application programs stored in the memory 501, so as to implement various functions as follows:

receiving an account verification request, wherein the account verification request comprises data to be verified of a first application account; determining an account identifier having a mapping relation with the first application account in a unified account system according to the account verification request, wherein the account identifier is generated based on a second application account, and the first application account and the second application account are application accounts belonging to two different applications; based on the data to be verified, performing identity verification on the first application account to obtain a verification result; receiving an account logout request of a first application account passing verification, wherein the account logout request carries logout application time information of the first application account; performing logout rule matching on the first application account based on the logout application time information and account login record information of the first application account to determine a logout attribute of the first application account; and when the logout attribute of the first application account is logout, removing the mapping relation between the first application account and the account identifier so as to logout the first application account.

The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.

Therefore, the computer device of the embodiment can complete account logout in a thorough and light manner, can improve account logout efficiency, and is beneficial to account management. Specifically, before the account is logged off, the computer device of this embodiment performs identity verification on the account to be logged off, thereby improving the security when subsequently logging off the account. Moreover, after the computer device of this embodiment calculates the account logout cold quiet period according to the logout application time information of the account to be logout, all operations related to account logout in the account logout cold quiet period can be processed uniformly by using the advantages of the uniform account system without paying attention by an application party. Furthermore, the computer device of the embodiment solves the data related to account logout from the account bottom layer, and realizes account logout by removing the mapping relationship between the account to be logged out and the account identifier corresponding to the account to be logged out in the unified account system, so that the user privacy data in the application can be completely anonymized on the premise of not considering the data logic in the application and not invading the application logic.

It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.

To this end, an embodiment of the present application provides a storage medium, where multiple instructions are stored, where the instructions can be loaded by a processor to perform steps in any account logout method provided in the embodiment of the present application. For example, the instructions may perform the steps of:

Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.

Since the instructions stored in the storage medium may execute the steps in any account deregistration method provided in the embodiment of the present application, beneficial effects that can be achieved by any account deregistration method provided in the embodiment of the present application may be achieved, which are detailed in the foregoing embodiments and will not be described herein again.

According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method provided in the various alternative implementations of the above-described deregistration aspect.

The account logout method, device and system provided by the embodiment of the application are described in detail, a specific example is applied in the description to explain the principle and the implementation of the application, and the description of the embodiment is only used for helping to understand the method and the core idea of the application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. An account logout method is characterized by comprising the following steps:

2. The account logout method according to claim 1, wherein performing logout rule matching on the first application account based on the logout application time information and account login record information of the first application account to determine a logout attribute of the first application account comprises:

calculating account cancellation cold quiet periods of the candidate cancellation accounts and account cancellation buffer periods of the candidate cancellation accounts after the account cancellation cold quiet periods according to cancellation application time information of the candidate cancellation accounts;

information query is carried out in an account login record table of a first application so as to obtain a first login record of the candidate logout account in the account logout cold quiet period and a second login record of the candidate logout account in the account logout buffer period;

3. The account deregistration method of claim 2, wherein performing deregistration rule matching on the candidate deregistration account based on the first login record and the second login record to determine the deregistration attribute of the candidate deregistration account comprises:

and when the account login behavior information matches the logout rule of the first application, determining the logout attribute of the candidate logout account as logout.

4. The account logout method according to claim 1, wherein when a logout attribute of the first application account is logout capable, removing a mapping relationship between the first application account and the account id to logout the first application account, comprises:

determining the first application account number which can be logged off as a target logging-off account number to be logged off;

generating a mapping relation removing request aiming at the target logout account;

and sending the mapping relation removing request to the unified account system to trigger the unified account system to remove the mapping relation between the target logout account and the account identifier.

5. The account deregistration method of claim 4, wherein before the sending of the mapping relationship release request to the unified accounting system, the method further comprises:

acquiring the account state of the target logout account;

requesting the unified account system to generate a third application account to be distributed for the account identifier, wherein the third application account and the target logout account are application accounts belonging to the same application;

6. The account deregistration method of claim 4, wherein after the sending of the mapping relationship release request to the unified accounting system, the method further comprises:

determining a peripheral component of the first application;

generating a data cleaning request aiming at the peripheral component, wherein the data cleaning request carries account information of the target logout account;

and sending the data cleaning request to the peripheral component to trigger cleaning of the application related data of the target logout account in the peripheral component based on the account information.

7. The account deregistration method according to claim 1, wherein receiving an account verification request, wherein the account verification request includes data to be verified of a first application account, and the method includes:

and when the terminal performs a logout identity verification process based on the unified account logout page and completes logout identity verification, receiving an account verification request, wherein the account verification request carries the data to be verified, which is acquired in the logout identity verification process.

8. The account deregistration method according to claim 1, wherein, based on the data to be verified, performing identity verification on the first application account to obtain a verification result, including:

acquiring identity authentication information data of the first application account;

9. An account deregistration apparatus, comprising:

10. A computer device comprising a memory and a processor; the memory stores an application program, and the processor is configured to execute the application program in the memory to perform the operations of the account deregistration method according to any one of claims 1 to 8.