CN116032550A

CN116032550A - Third party account login method and related equipment thereof

Info

Publication number: CN116032550A
Application number: CN202211583012.2A
Authority: CN
Inventors: 王颖奇; 冯斌; 杨笛; 李伟; 方志恒
Original assignee: Shenzhen Fulin Technology Co Ltd
Current assignee: Shenzhen Fulin Technology Co Ltd
Priority date: 2022-12-09
Filing date: 2022-12-09
Publication date: 2023-04-28

Abstract

The application belongs to the field of artificial intelligence and relates to a third party login method, which comprises the steps of receiving a login request of a third party account carrying a first identifier and a first identity credential; generating a matching result of matching the first identifier with a second identifier in a database, wherein the database stores at least one associated account carrying the second identifier in advance; if the matching result is that a second identifier corresponding to the first identifier is matched in the database, generating a login result of logging in the associated account corresponding to the first identifier by the second identifier; if the matching result is that the second identifier corresponding to the first identifier is not matched in the database, establishing a corresponding relation between the unassociated account and the third party account, and determining the unassociated account as an associated account to generate a login result for logging in the associated account; and processing the login request according to the login result. The application also provides a third party logging device and related equipment thereof. The suitability of the third party account login is improved.

Description

Third party account login method and related equipment thereof

Technical Field

The application relates to the technical field of artificial intelligence, in particular to a third party account login method and related equipment thereof.

Background

In the current third party account, the third party account and the associated account are generally associated in a data synchronization mode, so that when the third party account logs in the system platform, the associated account corresponding to the third party account in synchronization on the system platform can be called to log in, but the method cannot realize the unsynchronized third party account login, has poor suitability, and is easy to cause the problem that a large number of third party accounts need to be synchronized in each data synchronization process, so that the data synchronization efficiency is low.

Disclosure of Invention

The embodiment of the application aims at providing a third party account login method and related equipment thereof, which are used for solving the problem of poor suitability of the third party account login in the prior art.

In order to solve the above technical problems, the embodiment of the present application provides a third party account login method, which adopts the following technical scheme:

receiving a login request of a third party account, wherein the third party account carries a first identifier and a first identity credential;

matching the first identifier with a second identifier in a database to obtain a matching result, wherein the database stores at least one associated account, and each associated account carries the second identifier;

If the matching result is that a second identifier corresponding to the first identifier is matched in the database, generating a login result of logging in an associated account corresponding to the first identifier by the second identifier;

if the matching result is that the second identifier corresponding to the first identifier is not matched in the database, establishing a corresponding relation between the unassociated account acquired from the database and the third party account, determining the unassociated account establishing the corresponding relation with the third party account as an associated account, storing the associated account into the database, and generating a login result of login by the associated account establishing the corresponding relation with the third party account;

and processing the login request according to the login result.

Further, the unassociated account carries a third identifier and a second identity credential; the step of establishing a corresponding relation between the unassociated account acquired from the database and the third party account comprises the following steps:

unassociated account numbers obtained from the database;

associating the first identity credential with the second identity credential, associating the first identifier with the third identifier, and establishing a corresponding relationship between the third party account and the unassociated account;

Before the step of generating the login result of login with the associated account establishing the corresponding relation with the third party account, the method further comprises:

and determining the third identification of the unassociated account establishing a corresponding relation with the third party account as a second identification.

Further, the step of obtaining the unassociated account number from the database includes:

and if the unassociated account is not acquired in the database, receiving a new account instruction, creating an unassociated account in the database according to the new account instruction, and executing the steps of establishing association between the first identity credential and the second identity credential, associating the first identifier with the third identifier, and establishing the corresponding relation between the third party account and the unassociated account.

and if the unassociated account is not acquired in the database, generating a login result which does not allow the third party account to login.

Further, after the step of generating the login result that the third party account is not allowed to log in, the method further includes:

Determining the third party account which does not allow login as a matching failure account, and adding the matching failure account into data to be synchronized, wherein the data to be synchronized comprises at least one third party account;

when a data synchronization instruction is received, a corresponding relation is established between the failed matching account in the data to be synchronized and the unassociated account in the database.

Further, the unassociated account carries a second identity credential; the step of establishing the correspondence between the first identifier, the first identity credential and the third identifier includes:

and associating the first identity credential with the second identity credential, associating the first identifier with the third identifier, and establishing a corresponding relationship between the third party account and the unassociated account.

Further, the associated account also carries an account status; before the step of matching the first identifier with a second identifier in a database, the method further comprises:

acquiring account valid conditions of the associated account;

and deleting the associated account number of which the account number state does not meet the account number effective condition if the account number state of the associated account number does not meet the account number effective condition.

Further, before the step of deleting the associated account number whose account number status does not satisfy the account number valid condition, the method further includes:

receiving feedback information when the account state of the associated account does not meet the account effective condition;

if the feedback information is deleting information, executing the step of deleting the associated account of which the account state does not meet the account effective condition;

and if the feedback information is the reserved information, reserving the associated account of which the account state does not meet the account effective condition.

In order to solve the above technical problems, the embodiment of the present application further provides a third party logging device, which adopts the following technical scheme:

the request receiving module is used for receiving a login request of a third party account, wherein the third party account carries a first identifier and a first identity credential;

the matching module is used for matching the first identifier with a second identifier in a database to obtain a matching result, wherein the database is prestored with at least one associated account, and each associated account carries the second identifier;

the first generation module is used for generating a login result of logging in an associated account corresponding to the first identifier when the matching result is that the second identifier corresponding to the first identifier is matched in the database;

The second generation module is used for establishing a corresponding relation between an unassociated account acquired from the database and the third party account if the matching result is that a second identifier corresponding to the first identifier is not matched in the database, determining the unassociated account establishing the corresponding relation with the third party account as an associated account, storing the associated account into the database, and generating a login result for logging in the associated account establishing the corresponding relation with the third party account;

and the processing module processes the login request according to the login result.

In order to solve the above technical problems, the embodiments of the present application further provide a computer device, which adopts the following technical schemes:

the method comprises a memory and a processor, wherein the memory stores computer readable instructions, and the processor realizes the steps of the third party account login method when executing the computer readable instructions.

In order to solve the above technical problems, embodiments of the present application further provide a computer readable storage medium, which adopts the following technical solutions:

the computer readable storage medium has stored thereon computer readable instructions which when executed by a processor implement the steps of the third party account login method as described above.

Compared with the prior art, the embodiment of the application has the following main beneficial effects: according to the method and the device, the first identification of the third party account is matched with the second identification of the associated account in the database, when the matching is successful, the associated account which is successfully matched is used as a login result, when the matching is failed, the corresponding relation between the third party account and the unassociated account is automatically established, the associated account corresponding to the third party account is obtained, and the associated account is used as the login result, so that the login of the unsynchronized or synchronized third party account can be adapted at the same time, the applicability is wide, the number of the third party accounts in each data synchronization is effectively reduced, the synchronization efficiency is improved, and the more efficient migration of the third party account is realized.

Drawings

For a clearer description of the solution in the present application, a brief description will be given below of the drawings that are needed in the description of the embodiments of the present application, it being obvious that the drawings in the following description are some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.

FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;

FIG. 2 is a flow chart of one embodiment of a third party account login method according to the present application;

FIG. 3 is a schematic diagram illustrating the structure of one embodiment of a third party account login device according to the present application;

FIG. 4 is a schematic structural diagram of one embodiment of a computer device according to the present application.

Detailed Description

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the applications herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having" and any variations thereof in the description and claims of the present application and in the description of the figures above are intended to cover non-exclusive inclusions. The terms first, second and the like in the description and in the claims or in the above-described figures, are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.

In order to better understand the technical solutions of the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings.

As shown in fig. 1, a system architecture 100 may include

terminal devices

101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the

terminal devices

101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

A third party user may interact with the server 105 via the network 104 using the

terminal devices

101, 102, 103 to receive or send messages or the like. Various communication client applications, such as a web browser application, a shopping class application, a search class application, an instant messaging tool, a mailbox client, social platform software, etc., may be installed on the

terminal devices

101, 102, 103.

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablet computers, electronic book readers, MP3 players (Mov i ng P i cture ExpertsGroup Aud i o Layer I I I, dynamic video expert compression standard audio plane 3), MP4 (Mov i ng P i ctureExperts Group Aud i o Layer I V, dynamic video expert compression standard audio plane 4) players, laptop and desktop computers, and the like.

The server 105 may be a server providing various services, such as a background server providing support for pages displayed on the

terminal devices

101, 102, 103.

It should be noted that, the third party account login method provided in the embodiment of the present application is generally executed by a server/terminal device, and accordingly, the third party account login device is generally set in the server/terminal device.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

With continued reference to fig. 2, a flow chart of one embodiment of a method of third party account login according to the present application is shown. The third party account login method comprises the following steps:

step S201, a login request of a third party account is received, where the third party account carries a first identifier and a first identity credential.

In this embodiment, the electronic device (for example, the server/terminal device shown in fig. 1) on which the third party account login method operates may receive the login request of the third party account through a wired connection manner or a wireless connection manner. It should be noted that the wireless connection may include, but is not limited to, 3G/4G/5G connections, wifi connections, bluetooth connections, wimax connections, zgbee connections, UWB (u l t ra W i deband) connections, and other now known or later developed wireless connection means.

The login request is generated by operating an operation option on a target login system by an operator; for example, an operator operates a target interface (where the target interface runs on the target login system) to log in the third party account number, and generates operation options for triggering icons (such as virtual buttons).

The first identifier is characterized by a unique identifier code (uuid) of the third party account, where the unique identifier code may be formed by a set of 16 digits of 32 digits, such as: 550e8400-e29b-41d4-a716-446655440000.

The first identity credential is characterized as a third party attribute of a third party account, wherein the first identity credential includes, but is not limited to, at least one of a mailbox of the third party, a mobile phone number of the third party, an identity card number of the third party, a User name (User id) of the third party, a personnel number of the third party, an identification number (such as a social security number, a passport number, etc.) of the third party.

Step S202, the first identifier is matched with a second identifier in a database, and a matching result is obtained, wherein the database stores at least one associated account, and each associated account carries the second identifier.

In this embodiment, at least one associated account is pre-stored in the database, where one associated account corresponds to at least one third party account.

The associated account is characterized by an account which has established a corresponding relation with a third party account, the associated account is stored in a database of a target login system, and the third party account is an account on a non-target login system; if the target login system is the A website, the associated account is the account of the third party on the A website and the account of the third party is the WeChat account, and the login is carried out on the A website through the associated account associated with the WeChat account of the third party.

The second identifier is a unique identifier (uuid) of the associated account, and the unique identifier may be formed by a set of 16 digits with 32 digits, such as: 550e8400-e29b-41d4-a716-446655440000.

Step S203, if the matching result is that a second identifier corresponding to the first identifier is matched in the database, generating a login result of the second identifier for logging in the associated account corresponding to the first identifier.

In this embodiment, if the matching result is that the second identifier corresponding to the first identifier is matched in the database, the matching result is characterized in that the database stores the associated account corresponding to the third party account, and at this time, the associated account corresponding to the first identifier of the third party account and the second identifier is called from the database, and the login is performed by using the associated account.

Step S204, if the matching result is that the second identifier corresponding to the first identifier is not matched in the database, establishing a corresponding relationship between the unassociated account acquired from the database and the third party account, determining the unassociated account establishing a corresponding relationship with the third party account as an associated account, storing the associated account in the database, and generating a login result for logging in the associated account establishing a corresponding relationship with the third party account.

In this embodiment, the unassociated account is characterized as an account that does not establish a corresponding relationship with the third party account.

If the matching result is that the second identifier corresponding to the first identifier is not matched in the database, the database is characterized in that the associated account corresponding to the third party account is not stored, and in the method, the corresponding relation between the unassociated account and the third party account can be established by acquiring the unassociated account, so that when the third party account is not synchronized in advance, the login of the third party account can be realized, the applicability of the third party login of the method is improved, meanwhile, the number of the third party accounts in each data synchronization is effectively reduced, the synchronization efficiency is improved, and the more efficient migration of the third party account is realized.

Step S205, processing the login request according to the login result.

In this embodiment, the login result includes a login result of logging in with the associated account and a login result of not allowing the third party account to log in.

The login result of the login of the associated account is characterized in that the third party account is matched with the associated account corresponding to the third party account in the database, and the login can be performed with the associated account corresponding to the third party account; and the login result of the third party account login is characterized in that the third party account is not matched with the corresponding associated account in the database, and the third party account login is not allowed.

According to the method and the device, the first identification of the third party account is matched with the second identification of the associated account in the database, when the matching is successful, the associated account which is successfully matched is used as a login result, when the matching is failed, the corresponding relation between the third party account and the unassociated account is automatically established, the associated account corresponding to the third party account is obtained, and the associated account is used as the login result, so that the login of the unsynchronized or synchronized third party account can be adapted at the same time, the applicability is wide, the number of the third party accounts in each data synchronization is effectively reduced, the synchronization efficiency is improved, and the more efficient migration of the third party account is realized.

In some optional implementations, in step S204, the unassociated account carries a third identifier and a second identity credential; the step of establishing a corresponding relation between the unassociated account acquired from the database and the third party account comprises the following steps:

unassociated account numbers obtained from the database;

In this embodiment, the third identifier is a unique identifier (uuid) of the unassociated account, where the unique identifier may be formed by a set of 16 digits of 32 digits, such as: 550e8400-e29b-41d4-a716-446655440000.

The second identity credential is characterized as a system side attribute of the unassociated account, wherein the second identity credential includes, but is not limited to, at least one of a mailbox of the system side, a mobile phone number of the system side, an identity card number of the system side, a User name (User id) of the system side, a personnel number of the system side, an identification number (such as a social security number, a passport number, etc.) of the system side.

In the step of associating the first identity credential with the second identity credential, the first identity credential may be directly covered to replace the second identity credential, so that the first identity credential and the second identity credential directly correspond to each other, thereby facilitating management of the identity credential and reducing data volume; the first identity credential and the second identity credential can be directly associated, and the relationship between the third party account and the associated account is determined according to the association mark of the first identity credential and the second identity credential, so that the identity credential can be managed conveniently.

In the step of associating the first identifier with the third identifier, the first identifier may be directly covered to replace the third identifier, so that the first identifier and the third identifier directly correspond to each other, thereby facilitating management of the identifiers and reducing data volume; the first identifier and the third identifier credential can be directly associated, and the relationship between the third party account and the associated account is determined according to the association mark of the first identifier and the third identifier credential, so that the management of the identifier can be facilitated.

Step S204, before the step of generating the login result of login with the associated account that establishes a correspondence with the third party account, further includes:

determining the third identification of the unassociated account establishing a corresponding relation with the third party account as a second identification; and updating the third identification to the second identification so as to correspond to the associated account number.

In some optional implementations, before the step of obtaining the unassociated account from the database, the method further includes:

In this embodiment, the new account number instruction may be generated by an operator operating the terminal device, or may be automatically generated when no unassociated account number exists in the database.

When the unassociated account is not acquired in the database, the unassociated account is newly established in the database according to the newly established account instruction so as to establish a corresponding relation with the third party account in the follow-up process, so that the login of the unsynchronized third party account is realized, the number of the third party accounts in each data synchronization is reduced, and the synchronization efficiency is improved.

In some optional implementations, the step of obtaining the unassociated account from the database includes:

In this embodiment, after a login result that the third party account is not allowed to login is generated, a login request is processed according to the login result, and at this time, a reminder is generated to remind the user on the third party terminal (such as a mobile phone, a tablet, a PC, etc.) of login failure.

In some embodiments, after reminding a user on a third party terminal (such as a mobile phone, a tablet, a PC, etc.) of a login failure, an account binding boundary surface may be displayed on the third party terminal, and a user on the third party terminal may manually establish a correspondence between a third party account and an unassociated account on an account binding interface, or by operating a new button on the account binding interface, generate the new account instruction, thereby automatically establishing a correspondence between a third party account and an unassociated account.

In some optional implementations, after the step of generating the login result that does not allow the third party account to log in, the method further includes:

In this embodiment, when the synchronization period arrives, a data synchronization instruction is generated to update the associated account in the database; according to the data synchronization instruction, a corresponding relation is established between each third party account to be synchronized in the data to be synchronized and the unassociated account in the database, one of the third party accounts corresponds to one associated account, and meanwhile, a corresponding relation is established between the failed matching account and the unassociated account in the database, so that the associated account can be matched through the failed matching account in subsequent use, and the use experience of the third party user is improved.

When it is noted that the above synchronization period is characterized by each synchronization time, where the synchronization period may be a year, month, day, hour, minute, and second as an interval of each synchronization time, which is not limited herein; if the interval of each synchronization time is 1 day, the data synchronization instruction is generated after the last 1 day of synchronization.

In some embodiments, the unassociated account carries a second identity credential (such as a system-side mailbox, a system-side mobile phone number, etc., which are not specifically limited herein); the step of establishing a corresponding relationship between the failed matching account in the data to be synchronized and the unassociated account in the database includes: and associating the first identity credential of the failed matching account with the second identity credential of the unassociated account, associating the first identifier of the failed matching account with the second identifier of the unassociated account to establish a corresponding relationship between the failed matching account and the unassociated account, removing the failed matching account marked on a third party account, and determining the unassociated account establishing the corresponding relationship with the failed matching account as the associated account.

In some optional implementations, in step S202, the associated account also carries an account status; before the step of matching the first identifier with a second identifier in a database, the method further comprises:

acquiring account valid conditions of the associated account;

In this embodiment, the account status is a status attribute of the associated account, where the status attribute includes, but is not limited to, an associated duration, a number of third party accounts bound, a log of log-in, and the like.

The account effective condition and the account state are set, so that when the account state does not meet the account effective condition, the associated account is deleted, the associated account is prevented from occupying the storage space, and the load of a system is reduced; otherwise, when the account status meets the account valid condition, the associated account continues to run.

In some embodiments, the account validity condition is a validity period, timing is started from when the associated account and the third party account establish a corresponding relationship, the time is used as the associated duration of the associated account, and the associated duration is updated to the account state; when the associated duration reaches the validity period, the associated account is deleted. In other embodiments, the account valid condition is an unregistered duration, and if the log in the account state shows that the difference between the last login time and the current time of the associated account is greater than or equal to the unregistered duration, the associated account is deleted.

In some optional embodiments, before the step of deleting the associated account whose account status does not satisfy the account valid condition, the method further includes:

In this embodiment, when it is determined that the account status of the associated account does not satisfy the account valid condition, deletion determination information is generated, and the deletion determination information is sent to an operation end (which may be an operation end of an operator, a third party terminal of a third party user, or the like, which is not specifically limited herein), and the operation end generates the feedback information according to an operation instruction in response to the deletion determination information.

For example, after the operation end receives the deletion determination information, the operator generates feedback information for deleting the information by clicking the yes button and generates feedback information for retaining the information by clicking the no button at the operation end.

Therefore, when the associated account is judged to not meet the effective account condition, the operator can carry out secondary determination so as to avoid the phenomenon of false deletion.

It is emphasized that to further guarantee the privacy and security of the database, the database may also be stored in a blockchain node.

The blockchain referred to in the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm and the like. The blockchain (Bl ockcha i n) is essentially a de-centralized database, which is a series of data blocks generated by association using a cryptographic method, and each data block contains a batch of information of network transactions, which is used for verifying the validity (anti-counterfeiting) of the information and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, an application services layer, and the like.

The embodiment of the application can acquire and process the related data based on the artificial intelligence technology. Among these, artificial intelligence (Art i f i c i a l I nte l l i gence, A I) is the theory, method, technique and application system that uses a digital computer or a digital computer-controlled machine to simulate, extend and expand human intelligence, sense the environment, acquire knowledge and use knowledge to obtain optimal results.

Artificial intelligence infrastructure technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and other directions.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by computer readable instructions stored in a computer readable storage medium that, when executed, may comprise the steps of the embodiments of the methods described above. The storage medium may be a nonvolatile storage medium such as a magnetic disk, an optical disk, a Read-On-y Memory (ROM), or a random access Memory (Random Access Memory, RAM).

It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited in order and may be performed in other orders, unless explicitly stated herein. Moreover, at least some of the steps in the flowcharts of the figures may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order of their execution not necessarily being sequential, but may be performed in turn or alternately with other steps or at least a portion of the other steps or stages.

With further reference to fig. 3, as an implementation of the method shown in fig. 2, the present application provides an embodiment of a third party account login device, where the embodiment of the device corresponds to the embodiment of the method shown in fig. 2, and the device may be specifically applied to various electronic devices.

As shown in fig. 3, the third party account login device 400 according to the present embodiment includes: a request receiving module 301, a matching module 302, a first generating module 303, a second generating module 304 and a processing module 305. Wherein:

the request receiving module 301 is configured to receive a login request of a third party account, where the third party account carries a first identifier and a first identity credential;

the matching module 302 is configured to match the first identifier with a second identifier in a database, so as to obtain a matching result, where the database stores at least one associated account, and each associated account carries the second identifier;

a first generating module 303, configured to generate a login result of the second identifier for logging in the associated account corresponding to the first identifier, if the matching result is that the second identifier corresponding to the first identifier is matched in the database;

A second generating module 304, configured to establish a correspondence between an unassociated account acquired from the database and the third party account, determine the unassociated account that establishes a correspondence with the third party account as an associated account, store the associated account in the database, and generate a login result for logging in the associated account that establishes a correspondence with the third party account, if the matching result is that a second identifier corresponding to the first identifier is not matched in the database;

and the processing module 305 is configured to process the login request according to the login result.

In some optional implementations, the second generating module 304 includes an account obtaining sub-module, a creating sub-module, and a determining sub-module. Wherein:

an account acquisition sub-module, configured to acquire an unassociated account from the database;

the establishing sub-module is used for associating the first identity certificate with the second identity certificate, associating the first identifier with the third identifier and establishing a corresponding relation between the third party account and the unassociated account;

and the determining submodule is used for determining the third identifier of the unassociated account which is in corresponding relation with the third party account as a second identifier.

In some optional implementations, the account acquisition submodule includes a new unit.

Wherein:

and the new creating unit is used for receiving a new account number instruction if the unassociated account number is not acquired in the database, creating an unassociated account number in the database according to the new account number instruction, executing the steps of establishing association between the first identity credential and the second identity credential, associating the first identifier with the third identifier, and establishing the corresponding relation between the third party account number and the unassociated account number.

In some optional implementations, the account acquisition sub-module includes a generation sub-unit. Wherein:

and the generation subunit is used for generating a login result which does not allow the third party account to login if the unassociated account is not acquired in the database.

In some optional implementations, the account obtaining sub-module further includes an adding unit and an establishing unit. Wherein:

the adding unit is used for determining the third party account which is not allowed to log in as a matching failure account and adding the matching failure account into data to be synchronized, wherein the data to be synchronized comprises at least one third party account;

the establishing unit is used for establishing a corresponding relation between the failed matching account number in the data to be synchronized and the unassociated account number in the database when the data synchronization instruction is received.

In some alternative implementations, the method further includes an acquisition module and a deletion module. Wherein:

the acquisition module is used for acquiring the account valid conditions of the associated account;

and the deleting module is used for deleting the associated account of which the account state does not meet the account effective condition if the account state of the associated account does not meet the account effective condition.

In some alternative implementations, the system further includes an information receiving module, an executing module, and a reserving module. Wherein:

the information receiving module is used for receiving feedback information when the account state of the associated account does not meet the account effective condition;

the execution module is used for executing the step of deleting the associated account number of which the account number state does not meet the account number effective condition if the feedback information is deleting information;

and the reservation module is used for reserving the associated account number of which the account number state does not meet the account number effective condition if the feedback information is the reservation information.

In order to solve the technical problems, the embodiment of the application also provides computer equipment. Referring specifically to fig. 4, fig. 4 is a basic structural block diagram of a computer device according to the present embodiment.

The computer device 4 comprises a memory 41, a processor 42, a network interface 43 communicatively connected to each other via a system bus. It should be noted that only computer device 4 having components 41-43 is shown in the figures, but it should be understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead. It will be appreciated by those skilled in the art that the computer device herein is a device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction, and its hardware includes, but is not limited to, a microprocessor, an application specific integrated circuit (App l I cat I on Spec I F I C I ntegrated C I rcu I t, AS IC), a programmable gate array (Flie d-Programmab l e Gate Ar ray, FPGA), a digital processor (D I g I ta l S I gna l Processor, DSP), an embedded device, and the like.

The computer equipment can be a desktop computer, a notebook computer, a palm computer, a cloud server and other computing equipment. The computer equipment can perform man-machine interaction with a third party user through a keyboard, a mouse, a remote controller, a touch pad or voice control equipment and the like.

The memory 41 includes at least one type of readable storage medium including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the storage 41 may be an internal storage unit of the computer device 4, such as a hard disk or a memory of the computer device 4. In other embodiments, the memory 41 may also be an external storage device of the computer device 4, such as a plug-in hard disk, a smart memory Card (Smart Med i a Card, SMC), a secure digital (Secu re D i g i ta l, SD) Card, a flash memory Card (F1 ash Card) or the like, which are provided on the computer device 4. Of course, the memory 41 may also comprise both an internal memory unit of the computer device 4 and an external memory device. In this embodiment, the memory 41 is typically used to store an operating system and various application software installed on the computer device 4, such as computer readable instructions of a third party logging method. Further, the memory 41 may be used to temporarily store various types of data that have been output or are to be output.

The processor 42 may be a central processing unit (Cent ra lProcess i ng Un i t, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 42 is typically used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is configured to execute computer readable instructions stored in the memory 41 or process data, such as computer readable instructions for executing the third party logging method.

The network interface 43 may comprise a wireless network interface or a wired network interface, which network interface 43 is typically used for establishing a communication connection between the computer device 4 and other electronic devices.

The present application also provides another embodiment, namely, a computer-readable storage medium storing computer-readable instructions executable by at least one processor to cause the at least one processor to perform the steps of a third party logging method as described above.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

It is apparent that the embodiments described above are only some embodiments of the present application, but not all embodiments, the preferred embodiments of the present application are given in the drawings, but not limiting the patent scope of the present application. This application may be embodied in many different forms, but rather, embodiments are provided in order to provide a more thorough understanding of the present disclosure. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that modifications may be made to the embodiments described in the foregoing, or equivalents may be substituted for elements thereof. All equivalent structures made by the specification and the drawings of the application are directly or indirectly applied to other related technical fields, and are also within the protection scope of the application.

Claims

1. The third party account login method is characterized by comprising the following steps of:

and processing the login request according to the login result.

2. The third party account login method according to claim 1, wherein the unassociated account carries a third identification and a second identity credential; the step of establishing a corresponding relation between the unassociated account acquired from the database and the third party account comprises the following steps:

unassociated account numbers obtained from the database;

3. The method of claim 2, wherein the step of obtaining the unassociated account from the database comprises:

4. The method of claim 2, wherein the step of obtaining the unassociated account from the database comprises:

5. The method according to claim 4, further comprising, after the step of generating a login result that does not allow the third party account to login:

6. The method of any one of claims 1 to 5, wherein the associated account also carries an account status; before the step of matching the first identifier with a second identifier in a database, the method further comprises:

acquiring account valid conditions of the associated account;

7. The method of claim 6, further comprising, prior to the step of deleting the associated account for which the account status does not satisfy the account valid condition:

8. A third party logging device, comprising:

9. A computer device comprising a memory having stored therein computer readable instructions which when executed implement the steps of the third party account login method of any of claims 1 to 7, and a processor.

10. A computer readable storage medium having stored thereon computer readable instructions which when executed by a processor implement the steps of the third party account login method of any of claims 1 to 7.