CN102546770A - Unified account management method and third-party account management system - Google Patents
Unified account management method and third-party account management system Download PDFInfo
- Publication number
- CN102546770A CN102546770A CN2011104407761A CN201110440776A CN102546770A CN 102546770 A CN102546770 A CN 102546770A CN 2011104407761 A CN2011104407761 A CN 2011104407761A CN 201110440776 A CN201110440776 A CN 201110440776A CN 102546770 A CN102546770 A CN 102546770A
- Authority
- CN
- China
- Prior art keywords
- login
- account management
- information
- user
- integrated software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title abstract description 190
- 238000012795 verification Methods 0.000 claims description 46
- 238000000034 method Methods 0.000 claims description 25
- 239000000284 extract Substances 0.000 claims description 13
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 238000012550 audit Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 2
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a third-party account management system, which comprises third-party account management equipment and user terminals. The third-party account management equipment is used for storing a comprehensive software material list and a user account management list, and providing comprehensive software login information for the user terminals by the aid of the comprehensive software material list and the user account management list after receiving comprehensive software login requests transmitted by the user terminals, and the user terminals are used for transmitting the comprehensive software login requests to the third-party account management equipment, and receiving the comprehensive software login information provided by the third-party account management equipment. The invention further discloses a unified account management method. By the aid of the third-party account management system and the unified account management method, the comprehensive software with a plurality of integrated businesses can be logged in and used via a unified account, and furthermore, operation of users is reduced.
Description
Technical Field
The invention relates to an account management technology in a network, in particular to a method for uniformly managing accounts and a third-party account management system.
Background
With the rapid development and improvement of the internet and the mobile network, various services are driven to operate. Many services can be used only by inputting login names and login passwords, and users can use different services only by frequently changing the login names and the login passwords of the users, so that inconvenience is brought to the users when accessing different services.
In order to solve the above problems, a third party account management system for managing accounts in a unified manner is provided, which includes a user terminal, a third party account management device and a service providing terminal, and specifically includes: after the user terminal is registered in the third-party account management device, the user terminal can use the registered account number to log in any service signed with the third-party account management system; the third-party account management equipment can verify the service developer, and the service provided by the developer who has passed the verification and signed up the agreement can be logged in by using the account number of the third-party account management system.
However, this kind of third party account management system is not suitable for the existing integrated software that integrates multiple business services; the third-party account management system can only provide a login interface of a single service, and cannot use the third-party account management system to log in and use the integrated software integrating a plurality of services.
It can be seen that the existing third-party account management system cannot log in and use the integrated software integrating multiple services by providing a unified account, and thus, the operation of the user is complicated and complicated.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a method for unified account management and a third-party account management system, which can log in through a unified account and use integrated software integrating multiple services, thereby reducing user operations.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a third party account management system, which comprises: the system comprises a user terminal and third-party account management equipment; wherein,
the third-party account management equipment is used for storing a comprehensive software data list and a user account management list; after receiving a login request for the integrated software sent by a user terminal, providing information for logging in the integrated software for the user terminal by using an integrated software data list and a user account management list;
and the user terminal is used for sending a login request for the integrated software to the third-party account management equipment and receiving the information for logging in the integrated software, which is provided by the third-party account management equipment.
In the above scheme, the third-party account management device is specifically configured to establish a comprehensive software data list according to the identifier of the comprehensive software, the service to be used by the comprehensive software, whether the service to be used by the comprehensive software needs to obtain login information of the service, and related information provided by the user terminal initiating the login request after obtaining the login information of the service.
In the above scheme, the third-party account management device is specifically configured to form a user account management list by using the user basic data, the login password, and other login information of the service required to be provided.
In the above scheme, the third-party account management device is further configured to extract a login name in a login request sent by the user terminal, check whether a user account management list identified by the login name is saved by using the login name, and send a login failure notification to the user terminal if the user account management list identified by the login name is not saved; if the user account management list with the login name as the identification is stored, extracting the login password in the login request, comparing the login password with the login password recorded in the user account management list, if the login password and the login password are the same, the verification result is that the login is successful, and if the login password and the login password are different, sending a notification of login failure with wrong passwords to the user terminal;
correspondingly, the user terminal is further configured to receive a login failure notification sent by the third-party account management device.
In the above scheme, the third party account management device is further configured to extract a name of the integrated software and user account information in the login request, view a self-stored integrated software data list according to the name of the integrated software in the login request, extract account information of each service that the user has stored from the user account management list according to login information of each service that is recorded in the integrated software data list and needs to obtain, and obtain related information of logging in the integrated software according to the account information of each service.
In the foregoing solution, the system further includes: the service providing terminal is used for sending the registration information of the developer to the third-party account management equipment;
correspondingly, the third-party account management device is further configured to receive registration information sent by the service providing terminal, and determine whether the developer is successfully registered.
In the foregoing solution, the third party account management device further includes: the system comprises a database module, a registration login module and a service processing module; wherein,
the database module is used for providing a comprehensive software data list and a user account management list stored by the database module for the service processing module;
the registration login module is used for sending a received login request for the integrated software sent by the user terminal to the service processing module;
and the service processing module is used for providing the information for logging in the integrated software for the user terminal by utilizing the integrated software data list and the user account management list in the database module after receiving the login request for the integrated software sent by the login registration module.
In the foregoing solution, the third party account management device further includes: a verification module and an interface module; wherein,
the verification module is used for receiving the registration information of the user terminal sent by the registration login module, verifying the registration information, sending the registration information to the service processing module when the verification result is that the registration is passed, and sending a registration failure notice to the interface module when the verification result is that the registration is failed;
the interface module is used for receiving the notice of the registration failure sent by the verification module and returning the notice of the registration failure to the user terminal;
correspondingly, the registration login module is further configured to determine whether registration information sent by the user terminal is received, and if so, send the registration information of the user terminal to the authentication module to authenticate the registration information, otherwise, continue to determine whether the registration information sent by the user terminal is received;
the service processing module is also used for receiving the registration information sent by the registration module.
The invention provides a method for managing accounts in a unified way.A third-party account management device stores a comprehensive software data list and a user account management list; the method further comprises the following steps:
and after receiving a login request for the integrated software sent by the user terminal, the third-party account management equipment provides information for the user terminal to login the integrated software by using the integrated software data list and the user account management list.
In the above scheme, the comprehensive software data list is: and taking the identifier of the integrated software, the service to be used by the integrated software, whether the service to be used by the integrated software needs to acquire the login information of the service, and the specific content of the related information required to be provided after the login information of the service is acquired as a content list.
In the above scheme, the user account management list is: a list consisting of user basic data, login password and login information of other services required to be provided.
In the above solution, after the third party account management device receives a login request for the integrated software from the user terminal, the method further includes: the third party account management equipment extracts the login name in the login request, checks whether a user account management list with the login name as an identifier is stored by the third party account management equipment by using the login name, and sends a login failure notification without registration to the user terminal if the user account management list with the login name as the identifier is not stored; if the user account management list with the login name as the identification is stored, the login password in the login request is extracted and compared with the login password recorded in the user account management list, if the login password and the login password are the same, the verification result is that the login is successful, and if the login password and the login password are different, a notification of login failure with wrong passwords is sent to the user terminal.
In the above solution, the providing information for logging in the integrated software for the user terminal by using the integrated software data list and the user account management list includes: the third-party account management system extracts the name and the user account information of the integrated software in the login request, looks up the integrated software data list stored in the third-party account management system according to the login request, extracts the user account information of each service which is stored by the user from the user account management list according to the login information of each service which is recorded in the integrated software data list and needs to be acquired, and acquires the related information for logging in the integrated software according to the user account information of each service.
The method for managing the accounts in a unified manner and the third-party account management system provided by the invention have the advantages that the information of the service to be used by the comprehensive software is bound by using the comprehensive software data list, and the login information of the service to be used by the comprehensive software is bound by using the user account management list, so that when a user logs in any one comprehensive software through a user terminal, the login information does not need to be input again in a plurality of integrated services of the comprehensive software, the comprehensive software data list in the third-party account management equipment is directly associated with the user account management list, and all information after logging in the comprehensive software is fed back to the user terminal, so that the purpose of logging in through one unified account and using the comprehensive software integrating a plurality of services is realized, and the user operation is reduced.
Drawings
FIG. 1 is a schematic diagram of the structure of a third-party account management system according to the present invention;
FIG. 2 is a schematic diagram of a component structure of a third-party account management device in the third-party account management system according to the present invention;
fig. 3 is a flowchart illustrating a method for managing accounts in a unified manner according to the present invention.
Detailed Description
The basic idea of the invention is: the third-party account management equipment saves a comprehensive software data list and a user account management list; and after receiving a login request for any integrated software sent by the user terminal, the third-party account management equipment provides information for logging in the integrated software for the user terminal by utilizing the integrated software data list and the user account management list.
Wherein, the comprehensive software data list is as follows: a list is composed of the service to be used by the integrated software, whether the service to be used by the integrated software needs to obtain the login information of the service, and the content of the relevant information provided for the user terminal initiating the login request after obtaining the login information of the service by the identification of the integrated software;
the user account management list is: a list consisting of user basic data, login password and login information of other services required to be provided.
The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
The invention provides a third party account management system, as shown in fig. 1, comprising: a user terminal 11, a third party account management device 12; wherein,
the third-party account management equipment 12 is used for storing a comprehensive software data list and a user account management list; after receiving a login request for any integrated software sent by the user terminal 11, providing information for logging in the integrated software for the user terminal 11 by using the integrated software data list and the user account management list;
and the user terminal 11 is configured to send a login request for any one piece of integrated software to the third-party account management device 12, and receive information provided by the third-party account management device 12 for logging in the integrated software.
The user terminal 11 is further configured to connect to the third-party account management device 12 according to a website of the third-party account management system input by the user in the web browser, receive a web interface returned by the third-party account management device 12, fill in registration information in the registration submenu, and send the registration information to the third-party account management device 12; correspondingly, the third-party account management device 12 is further configured to determine whether registration information sent by the user terminal 11 is received, and if so, verify the registration information, otherwise, continue to determine whether registration information sent by the user terminal 11 is received;
wherein the registration information may include: login name, user basic information and login password; the login name can be a character and/or a number defined by the user; the user basic information can be the birthday, the common mailbox and the like of the user.
The third-party account management device 12 is further configured to verify the registration information, store the registration information if the verification result is that the registration is passed, and send a notification of user registration failure to the user terminal 11 if the verification result is that the registration is passed; correspondingly, the user terminal 11 is further configured to receive a notification of registration failure sent by the third party account management device 12.
The third-party account management device 12 is specifically configured to extract a login name in the registration information, detect whether the login name meets the filling requirement, and detect whether a user account management list with the same login name is already stored in the third-party account management device, if the account name meets the filling requirement and the user account management list with the same login name is not already stored in the third-party account management device, the verification result is that registration is passed, and otherwise, the verification result is that registration is failed;
the filling requirement is a requirement of a filling format preset according to an actual situation, for example, the filling requirement may be preset as follows: the length is more than six bits, and Chinese characters cannot be included.
The third-party account management device 12 is specifically configured to extract a login name in the registration information, establish a user account management list, store user basic data and a login password in the registration information in the user account management list, send a prompt to the user terminal 11 to request the user to fill in service login information provided in the user account management list, and store the service login information returned by the user terminal 11 in the user account management list; correspondingly, the user terminal 11 is further configured to receive a prompt sent by the third-party account management device 12 to request the user to fill in the login information of the other services in the user account management list, and send the login information of the other services filled in by the user to the third-party account management device 12;
wherein, the service login information is: user login information of all services to be used by the integrated software, submitted by the integrated software developer, signed with the third party account management device 12.
The third-party account management device 12 is further configured to determine whether a login request sent by the user terminal 11 for any one of the integrated software is received, and if so, verify the login request, otherwise, end the processing flow; correspondingly, the user terminal 11 is further configured to send a login request for any one piece of integrated software to the third-party account management device 12;
wherein the login request to any one of the integrated software comprises: integrating the name of the software and the user account information; the user account information includes a login name and a login password.
The third-party account management device 12 is further configured to verify the login request, provide relevant information for the user terminal 11 to log in the integrated software if the verification result is that the login is successful, and notify the user terminal 11 of a login failure if the verification result is that the login is not successful; correspondingly, the user terminal 11 is further configured to receive related information provided by the third-party account management device 12 for logging in the integrated software, or receive a notification of login failure of the user terminal 11 sent by the third-party account management device 12.
The third-party account management device 12 is specifically configured to extract user account information in the login request, check whether a user account management list corresponding to the user account information is stored by the third-party account management device itself by using the login name, and send a login failure notification that is not registered to the user terminal 11 if the user account management list is not stored; if the password is stored, the login password in the login request is extracted and compared with the login password recorded in the user account management list, if the password is the same as the login password, the authentication result is that the login is successful, and if the password is different from the login password, a notification of login failure with a wrong password is sent to the user terminal 11.
The third-party account management device 12 is specifically configured to extract the name and the user account information of the integrated software in the login request, view a comprehensive software data list corresponding to the name of the integrated software stored in the third-party account management device according to the name of the integrated software in the login request, and extract the user account information of each service that the user has stored from the user account management list according to the login information of each service that needs to be acquired and is recorded in the comprehensive software data list and the user account information in the login request; acquiring related information for logging in the integrated software according to the user account information of each service;
the acquiring method is the prior art and is not described herein any more, wherein the acquiring method is used for acquiring the related information for logging in the integrated software, the related information is different due to different integrated software, and is related to an agreement signed by a developer of the integrated software and a third-party account management system.
The user terminal 11 is further configured to continue to use the integrated software by using the obtained related information for logging in the integrated software, and a specific method for using the integrated software is the prior art and is not described herein.
The third party account management system further comprises: the service providing terminal 13 is configured to connect to the third-party account management device 12 according to the website of the third-party account management system input by the developer in the web browser, receive a web interface returned by the third-party account management device 12, fill registration information in the registration submenu, and send the registration information to the third-party account management device 12; correspondingly, the third-party account management device 12 is further configured to receive registration information sent by the service providing terminal 13, determine whether the developer has successfully registered, notify the service providing terminal 13 to fill in any protocol of the integrated software using the third-party account management system if the developer has successfully registered, and notify the service providing terminal 13 of a failure in registration if the developer has not successfully registered;
wherein the registration information may include: login name, developer basic information and login password; the login name can be a character and/or a number defined by a developer; the basic information of the developer can be the company name, the company mailbox and the like of the developer.
The third-party account management device 12 is specifically configured to extract a login name in the registration information, detect whether the login name meets the filling requirement, and detect whether the developer data list with the same login name is already stored in the third-party account management device, if the login name meets the filling requirement and the developer data list with the same login name is not already stored in the third-party account management device, the registration is successful, and otherwise, the registration is failed.
The third-party account management device 12 is further configured to receive a protocol of the third-party account management system used by the filled-in integrated software sent by the service providing terminal 13, audit the developer according to the protocol, if the audit is passed, establish an integrated software data list, and if the audit is not passed, audit and send a non-passing notification to the service providing terminal 13;
the integrated software uses a protocol of a third-party account management system, and the information of the integrated software, which is required to be filled by a developer according to actual conditions, may include: the name of the integrated software, the service to be used by the integrated software, whether the service to be used by the integrated software needs to obtain the login information of the service, and the specific content of the related information which needs to be provided after the login information of the service is obtained.
The third-party account management device 12 is specifically configured to establish a comprehensive software data list using the name of the comprehensive software in the protocol in which the comprehensive software uses the third-party account management system, the service to be used by the comprehensive software, and whether the service to be used by the comprehensive software needs to acquire login information of the service, where the comprehensive software data list uses the service to be used by the comprehensive software, whether the service to be used by the comprehensive software needs to acquire the login information of the service, and specific content of related information that needs to be provided after the login information of the service is acquired as content.
The service providing terminal 13, the user sends the integrated service requested to be downloaded by the user to the user terminal 11; correspondingly, the user terminal 11 is further configured to send a request for downloading the integrated service to the service providing terminal 13, and receive the integrated service sent by the service providing terminal.
As shown in fig. 2, the third party account management device 12 further includes: a database module 121, a registration login module 122 and a service processing module 123; wherein,
the database module 121 is used for providing a self-storage comprehensive software data list and a user account management list for the service processing module 123;
a registration login module 122, configured to send a login request for any one piece of integrated software received from a user terminal to the service processing module 123;
and the service processing module 123 is configured to, after receiving a login request for any one of the integrated software sent by the login registration module 122, provide information for logging in the integrated software for the user terminal by using the integrated software data list and the user account management list in the database module 121.
The third party account management device 12 further comprises: a verification module 124 and an interface module 125; wherein,
a verification module 124, configured to receive the registration information of the user terminal sent by the registration login module 122, verify the registration information, send the registration information to the service processing module 123 when the verification result is that the registration is passed, and send a notification of the registration failure to the interface module 125 when the verification result is that the registration is failed;
an interface module 125, configured to receive the notification of registration failure sent by the verification module 124, and return the notification of registration failure to the user terminal;
correspondingly, the registration login module 122 is further configured to determine whether registration information sent by the user terminal is received, and if so, send the registration information of the user terminal to the verification module 124 to verify the registration information, otherwise, continue to determine whether registration information sent by the user terminal is received;
the service processing module 123 is further configured to receive registration information sent by the registration module.
The verification module 124 is specifically configured to extract a login name in the registration information of the user terminal, detect whether the login name meets the filling requirement, and detect whether the user terminal itself has stored the user account management list with the same login name, where if the account name meets the filling requirement and the user terminal itself has not stored the user account management list with the same login name, the verification result is that the registration is passed, and otherwise, the verification result is that the registration is failed.
The service processing module 123 is specifically configured to extract a login name in the registration information, establish a user account management list corresponding to the login name, store user basic data and a login password in the registration information in the user account management list, send a prompt to the user terminal to request the user to fill in service login information in the user account management list, store service login information returned by the user terminal in the user account management list, and send the user account management list to the database module 121; correspondingly, the database module 121 is specifically configured to receive and store the user account management list sent by the service processing module 123.
The login registering module 122 is further configured to determine whether a login request sent by the user terminal for any one of the integrated software is received, and if so, send the login request sent by the user terminal for any one of the integrated software to the verifying module 124 to verify the login request, otherwise, continue to determine whether a login request sent by the user terminal for any one of the integrated software is received;
correspondingly, the verification module 124 is further configured to receive a login request for any one of the integrated software from the user terminal sent by the login registration module 122, verify the login request, send the login request for the integrated software to the service processing module 123 if the verification result is that the login is successful, and send a login failure notification to the interface module 125 if the verification result is that the login is not successful;
the interface module 125 is further configured to send a notification of login failure sent by the authentication module 124 to the user terminal;
the service processing module 123 is further configured to receive a login request sent by the authentication module 124.
The verification module 124 is specifically configured to extract user account information in the login request, check whether the database module 121 stores the corresponding user account management list by using the user account information, and send a login failure notification that the user terminal is not registered to the interface module 125 if the corresponding user account management list is not stored; if the user account management list corresponding to the user account information is stored, the login password in the login request is extracted and compared with the login password recorded in the user account management list in the database module 121, if the two are the same, the verification result is that the login is successful, and if the two are different, a notification of login failure that the user terminal password is wrong is sent to the interface module 125.
The service processing module 123 is further configured to, after receiving the login request sent by the verification module 124, extract the name and the user account information of the integrated software in the login request, view the integrated software profile list, which is stored in the database module 121 and identified by the name of the integrated software, according to the login information of each service, which is recorded in the integrated software profile list and needs to be acquired, and extract the login information of each service, which is already stored by the user, from the user account management list corresponding to the user account information in the login request, and provide specific content of relevant information, which needs to be provided after the login information of the service is acquired, to the user terminal.
The registration login module 122 is further configured to receive registration information sent by the service providing terminal, and send the registration information to the verification module 124; correspondingly, the verification module 124 is further configured to receive the registration information sent by the registration login module 122, extract the login name in the registration information, detect whether the login name meets the filling requirement, and detect whether the developer data list with the same login name is already stored in the database module 121, if the login name meets the filling requirement and the developer data list with the same login name is not already stored in the database module, the registration is successful, otherwise, the registration is failed.
The verification module 124 is further configured to send the registration result to the interface module 125; correspondingly, the interface module 125 is further configured to receive a registration result sent by the verification module 124, notify the service providing terminal to fill in a protocol of the integrated software using the third party account management system when the registration result is successful, and send a notification of registration failure when the registration result is registration failure.
The interface module 125 is further configured to receive a protocol of the third-party account management system used by the filled-in integrated software sent by the service providing terminal, audit the developer according to the protocol, if the audit is passed, establish an integrated software data list, and if the audit is not passed, send a notification of failing to pass to the service providing terminal.
The interface module 125 is specifically configured to establish a comprehensive software data list using the name of the comprehensive software in the protocol for using the third-party account management system by the comprehensive software, the service to be used by the comprehensive software, and whether the service to be used by the comprehensive software needs to acquire the login information of the service, where the comprehensive software data list uses the service to be used by the comprehensive software, whether the service to be used by the comprehensive software needs to acquire the login information of the service, and the specific content of the relevant information that needs to be provided after the login information of the service is acquired as the content, and sends the finally established comprehensive software data list to the database module 121; correspondingly, the database module 121 is specifically configured to receive and store the comprehensive software document list sent by the interface module 125.
As shown in fig. 3, the method for unified account management provided by the present invention includes the following steps:
step 301: the third party account management device judges whether the registration information sent by the user terminal is received, if so, step 302 is executed, otherwise, step 301 is repeatedly executed.
Step 302: the third party account management equipment verifies the received registration information, and if the verification result is that the registration is passed, step 303 is executed; otherwise, the user terminal is informed of the registration failure, and the processing flow is ended.
Here, the verification is: and extracting the login name in the registration information, detecting whether the login name meets the filling requirement, detecting whether a user account management list with the same login name is stored per se, if the account name meets the filling requirement and the user account management list with the same login name is not stored per se, judging that the registration is passed as a verification result, and otherwise, judging that the registration is failed as the verification result.
Step 303: the third party account management equipment stores the registration information and stores the service login information bound by the user.
Here, the storage registration information is: extracting a login name in the registration information, establishing a user account management list with the login name as an identifier, and storing user basic data and a login password in the registration information in the user account management list;
the service login information for saving the user binding is as follows: the third-party account management equipment prompts a user to fill in service login information in the user account management list, and the login information filled in by the user is stored in the user account management list;
wherein, the service login information is: and the user login information of all services to be used by the comprehensive software is submitted by the comprehensive software developer signed in the third-party account management equipment.
Step 304: the third party account management device judges whether a login request for any one integrated software is received, and if so, executes step 305; otherwise, the process flow is ended.
Step 305: the third party account management equipment verifies the login request, and if the verification result is that the login is successful, step 306 is executed; otherwise, the user terminal is informed of the login failure, and the processing flow is ended.
Here, the verifying the login request is: extracting user account information in the login request, checking whether a corresponding user account management list is stored by the user account information, and if not, sending a login failure notification without registration to the user; if the password is saved, the login password in the login request is extracted and compared with the login password recorded in the user account management list, if the password is the same as the login password, the verification result is that the login is successful, and if the password is different from the login password, a notification of login failure with wrong password is sent to the user.
Step 306: and the third-party account management equipment provides the relevant information for logging in the integrated software for the user according to the login request.
Specifically, the method comprises the following steps: the third-party account management equipment extracts the name and the user account information of the integrated software in the login request, looks up an integrated software data list which is stored by the third-party account management equipment and takes the name of the integrated software as an identifier according to the name of the integrated software in the login request, extracts the user account information of each service which is stored by the user from a user account management list corresponding to the user account information in the login request according to the login information of each service which is recorded in the integrated software data list and needs to be acquired, and acquires the related information for logging in the integrated software according to the user account information of each service;
the acquiring method is the prior art and is not described herein any more, wherein the acquiring method is used for acquiring the related information for logging in the integrated software, the related information is different due to different integrated software, and is related to an agreement signed by a developer of the integrated software and third-party account management equipment.
After the step 306 is completed, the user equipment may continue to use the integrated software by using the obtained related information for logging in the integrated software, and the specific method for using the integrated software is the prior art and is not described herein again.
In addition, before step 301, the third-party account management device further needs to sign an agreement with a developer of each piece of integrated software, and after the agreement is approved, the user can use the integrated software through the third-party account management device, which specifically includes:
step a: b, registering the developer of the integrated software in third-party account management equipment, judging whether the developer is successfully registered by the third-party account management equipment, and executing the step b if the developer is successfully registered; otherwise, informing the developer of the registration failure and ending the processing flow.
Here, the registration is: the integrated software developer registers according to the information filled by the third party account management requirement, and the filled information may include: login name, developer basic information and login password; the login name can be a character and/or a number defined by a developer; the basic information of the developer can be the company name, the company mailbox and the like of the developer;
the developer is registered in the third-party account management device, and the registration may be: the method comprises the steps that a developer inputs a website of third-party account management equipment in a webpage browser of terminal equipment used by the developer, the website is connected to a webpage interface of the third-party account management equipment, and registration information is filled in a developer registration submenu on the webpage interface.
The judgment of whether the developer is successfully registered is as follows: and extracting the login name in the registration information, detecting whether the login name meets the filling requirement and detecting whether a developer data list with the same login name is stored per se, if the login name meets the filling requirement and the developer data list with the same login name is not stored per se, the registration is successful, and otherwise, the developer is informed that the registration fails.
Step b: the third party account management equipment receives a protocol of any one piece of comprehensive software filled by the developer using the third party account management equipment, then the developer is checked according to the protocol, and if the check is passed, the step c is executed; and if the audit is not passed, informing the developer that the audit is not passed, and ending the processing flow.
Here, the any one of the integrated software may use a protocol of the third party account management device, and the information of the integrated software that the developer is required to fill according to the actual situation may include: the name of the integrated software, the service to be used by the integrated software, whether the service to be used by the integrated software needs to obtain the login information of the service, and the specific content of the related information which needs to be provided after the login information of the service is obtained.
Step c: and the third-party account management equipment establishes a comprehensive software data list.
Here, the creating of the comprehensive software material list is: the name of the integrated software in a protocol of any integrated software using the third-party account management equipment, the service to be used by the integrated software and whether the service to be used by the integrated software needs to acquire the login information of the service are utilized to establish an integrated software data list with the name of the integrated software as an identifier, wherein the integrated software data list takes the service to be used by the integrated software, whether the service to be used by the integrated software needs to acquire the login information of the service and the specific content of the related information required to be provided after the login information of the service is acquired as the content.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (13)
1. A third party account management system, the system comprising: the system comprises a user terminal and third-party account management equipment; wherein,
the third-party account management equipment is used for storing a comprehensive software data list and a user account management list; after receiving a login request for the integrated software sent by a user terminal, providing information for logging in the integrated software for the user terminal by using an integrated software data list and a user account management list;
and the user terminal is used for sending a login request for the integrated software to the third-party account management equipment and receiving the information for logging in the integrated software, which is provided by the third-party account management equipment.
2. The system of claim 1,
the third-party account management equipment is specifically used for establishing a comprehensive software data list according to the identification of the comprehensive software, the service to be used by the comprehensive software, whether the service to be used by the comprehensive software needs to acquire the login information of the service, and the related information provided for the user terminal initiating the login request after acquiring the login information of the service.
3. The system of claim 1,
the third-party account management equipment is specifically used for forming a user account management list by using user basic data, login passwords and other login information of services required to be provided.
4. The system of claim 1,
the third party account management equipment is also used for extracting a login name in a login request sent by the user terminal, checking whether a user account management list with the login name as an identifier is stored by the third party account management equipment by using the login name, and sending a login failure notification without registration to the user terminal if the user account management list with the login name as the identifier is not stored; if the user account management list with the login name as the identification is stored, extracting the login password in the login request, comparing the login password with the login password recorded in the user account management list, if the login password and the login password are the same, the verification result is that the login is successful, and if the login password and the login password are different, sending a notification of login failure with wrong passwords to the user terminal;
correspondingly, the user terminal is further configured to receive a login failure notification sent by the third-party account management device.
5. The system of claim 1,
the third-party account management equipment is further used for extracting the name and the user account information of the integrated software in the login request, viewing the integrated software data list stored by the third-party account management equipment according to the name of the integrated software in the login request, extracting the account information of each service which is stored by the user from the user account management list according to the login information of each service which is recorded in the integrated software data list and needs to be acquired, and acquiring the related information for logging in the integrated software according to the account information of each service.
6. The system of claim 1, further comprising: the service providing terminal is used for sending the registration information of the developer to the third-party account management equipment;
correspondingly, the third-party account management device is further configured to receive registration information sent by the service providing terminal, and determine whether the developer is successfully registered.
7. The system of claim 6, wherein the third party account management device further comprises: the system comprises a database module, a registration login module and a service processing module; wherein,
the database module is used for providing a comprehensive software data list and a user account management list stored by the database module for the service processing module;
the registration login module is used for sending a received login request for the integrated software sent by the user terminal to the service processing module;
and the service processing module is used for providing the information for logging in the integrated software for the user terminal by utilizing the integrated software data list and the user account management list in the database module after receiving the login request for the integrated software sent by the login registration module.
8. The system of claim 7, wherein the third party account management device further comprises: a verification module and an interface module; wherein,
the verification module is used for receiving the registration information of the user terminal sent by the registration login module, verifying the registration information, sending the registration information to the service processing module when the verification result is that the registration is passed, and sending a registration failure notice to the interface module when the verification result is that the registration is failed;
the interface module is used for receiving the notice of the registration failure sent by the verification module and returning the notice of the registration failure to the user terminal;
correspondingly, the registration login module is further configured to determine whether registration information sent by the user terminal is received, and if so, send the registration information of the user terminal to the authentication module to authenticate the registration information, otherwise, continue to determine whether the registration information sent by the user terminal is received;
the service processing module is also used for receiving the registration information sent by the registration module.
9. A method for managing accounts in a unified way is characterized in that third-party account management equipment stores a comprehensive software data list and a user account management list; the method further comprises the following steps:
and after receiving a login request for the integrated software sent by the user terminal, the third-party account management equipment provides information for the user terminal to login the integrated software by using the integrated software data list and the user account management list.
10. The method of claim 9, wherein the integrated software profile list is: and taking the identifier of the integrated software, the service to be used by the integrated software, whether the service to be used by the integrated software needs to acquire the login information of the service, and the specific content of the related information required to be provided after the login information of the service is acquired as a content list.
11. The method of claim 9, wherein the user account management list is: a list consisting of user basic data, login password and login information of other services required to be provided.
12. The method of claim 9, wherein after the third party account management device receives a login request for the integrated software from the user terminal, the method further comprises: the third party account management equipment extracts the login name in the login request, checks whether a user account management list with the login name as an identifier is stored by the third party account management equipment by using the login name, and sends a login failure notification without registration to the user terminal if the user account management list with the login name as the identifier is not stored; if the user account management list with the login name as the identification is stored, the login password in the login request is extracted and compared with the login password recorded in the user account management list, if the login password and the login password are the same, the verification result is that the login is successful, and if the login password and the login password are different, a notification of login failure with wrong passwords is sent to the user terminal.
13. The method of claim 9, wherein providing the user terminal with information for logging into the integrated software using the integrated software profile list and the user account management list comprises: the third-party account management system extracts the name and the user account information of the integrated software in the login request, looks up the integrated software data list stored in the third-party account management system according to the login request, extracts the user account information of each service which is stored by the user from the user account management list according to the login information of each service which is recorded in the integrated software data list and needs to be acquired, and acquires the related information for logging in the integrated software according to the user account information of each service.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110440776.1A CN102546770B (en) | 2011-12-26 | 2011-12-26 | Unified account management method and third-party account management system |
| PCT/CN2012/074999 WO2013097392A1 (en) | 2011-12-26 | 2012-05-02 | Method for unified account management and third-party account management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110440776.1A CN102546770B (en) | 2011-12-26 | 2011-12-26 | Unified account management method and third-party account management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102546770A true CN102546770A (en) | 2012-07-04 |
| CN102546770B CN102546770B (en) | 2015-05-27 |
Family
ID=46352717
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110440776.1A Expired - Fee Related CN102546770B (en) | 2011-12-26 | 2011-12-26 | Unified account management method and third-party account management system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102546770B (en) |
| WO (1) | WO2013097392A1 (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103023875A (en) * | 2012-11-21 | 2013-04-03 | 北京荣之联科技股份有限公司 | Account management system and method |
| CN103347084A (en) * | 2013-07-10 | 2013-10-09 | 上海斐讯数据通信技术有限公司 | Multi-account unifying interacted system and interacted method |
| CN104392368A (en) * | 2014-10-21 | 2015-03-04 | 中国建设银行股份有限公司 | Method and device for user system management in e-commerce platform |
| CN104518876A (en) * | 2013-09-29 | 2015-04-15 | 腾讯科技（深圳）有限公司 | Service login method and device |
| CN105516166A (en) * | 2015-12-22 | 2016-04-20 | 北京奇虎科技有限公司 | Method and system for realizing login by using other account |
| CN105871958A (en) * | 2015-01-21 | 2016-08-17 | 中兴通讯股份有限公司 | Method for managing account information in centralized manner and terminal |
| CN105975845A (en) * | 2016-07-04 | 2016-09-28 | 深圳市游云龙科技有限公司 | Method and device for logging into mechanisms |
| CN105989485A (en) * | 2015-02-16 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Business management method and device |
| CN107277066A (en) * | 2017-08-11 | 2017-10-20 | 中国银行股份有限公司 | Account management method, portable electric appts and account management system |
| CN107483477A (en) * | 2017-09-08 | 2017-12-15 | 上海宝库信息技术有限公司 | Account management method and account management system |
| CN107508835A (en) * | 2017-09-25 | 2017-12-22 | 咪咕文化科技有限公司 | Account verification method and device and computer readable storage medium |
| CN107832592A (en) * | 2017-10-30 | 2018-03-23 | 北京小米移动软件有限公司 | Right management method, device and storage medium |
| CN107979569A (en) * | 2016-10-24 | 2018-05-01 | 中国移动通信有限公司研究院 | A kind of registered information managing device of the Internet, applications, method and system |
| TWI695290B (en) * | 2017-07-14 | 2020-06-01 | 香港商阿里巴巴集團服務有限公司 | Login information processing method and equipment |
| CN111541546A (en) * | 2020-04-24 | 2020-08-14 | 前海乔希(深圳)教育科技有限公司 | Multi-platform login method, device, equipment and readable medium |
| CN111614641A (en) * | 2020-05-11 | 2020-09-01 | 北京电信易通信息技术股份有限公司 | Cloud account management system and application method |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109543372A (en) * | 2018-10-26 | 2019-03-29 | 深圳壹账通智能科技有限公司 | Service authority data processing method, device, computer equipment and storage medium |
| CN114553504B (en) * | 2022-01-29 | 2024-03-08 | 重庆华唐云树科技有限公司 | Third party secure login method |
| CN114640511B (en) * | 2022-03-04 | 2024-01-19 | 上海医栗医疗科技有限公司 | Application interface monitoring platform |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1588853A (en) * | 2004-07-13 | 2005-03-02 | 中国工商银行 | Uniform identication method and system based on network |
| CN1627683A (en) * | 2003-12-09 | 2005-06-15 | 鸿富锦精密工业（深圳）有限公司 | Unitary authentication authorization management system and method |
| US20070239870A1 (en) * | 2006-04-10 | 2007-10-11 | Square D Company | Network-enabled electrical power equipment with integrated content management system |
| CN102111347A (en) * | 2011-02-28 | 2011-06-29 | 东南大学 | Multi-protocol instant message-based processing method and system in unified communication system |
| CN102222200A (en) * | 2011-06-24 | 2011-10-19 | 宇龙计算机通信科技(深圳)有限公司 | Application program logging method and logging management system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100931326B1 (en) * | 2008-09-09 | 2009-12-11 | 주식회사 로그 | ID / Password Search History and Login History Management System and Method |
| CN102073928A (en) * | 2010-12-30 | 2011-05-25 | 天津市国瑞数码安全系统有限公司 | Interface definition-based synchronous management method of resource accounts |
-
2011
- 2011-12-26 CN CN201110440776.1A patent/CN102546770B/en not_active Expired - Fee Related
-
2012
- 2012-05-02 WO PCT/CN2012/074999 patent/WO2013097392A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1627683A (en) * | 2003-12-09 | 2005-06-15 | 鸿富锦精密工业（深圳）有限公司 | Unitary authentication authorization management system and method |
| CN1588853A (en) * | 2004-07-13 | 2005-03-02 | 中国工商银行 | Uniform identication method and system based on network |
| US20070239870A1 (en) * | 2006-04-10 | 2007-10-11 | Square D Company | Network-enabled electrical power equipment with integrated content management system |
| CN102111347A (en) * | 2011-02-28 | 2011-06-29 | 东南大学 | Multi-protocol instant message-based processing method and system in unified communication system |
| CN102222200A (en) * | 2011-06-24 | 2011-10-19 | 宇龙计算机通信科技(深圳)有限公司 | Application program logging method and logging management system |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103023875A (en) * | 2012-11-21 | 2013-04-03 | 北京荣之联科技股份有限公司 | Account management system and method |
| CN103347084A (en) * | 2013-07-10 | 2013-10-09 | 上海斐讯数据通信技术有限公司 | Multi-account unifying interacted system and interacted method |
| CN103347084B (en) * | 2013-07-10 | 2017-11-21 | 上海斐讯数据通信技术有限公司 | A kind of more accounts unify interconnected system and correlating method |
| CN104518876A (en) * | 2013-09-29 | 2015-04-15 | 腾讯科技（深圳）有限公司 | Service login method and device |
| CN104392368A (en) * | 2014-10-21 | 2015-03-04 | 中国建设银行股份有限公司 | Method and device for user system management in e-commerce platform |
| CN104392368B (en) * | 2014-10-21 | 2018-12-14 | 中国建设银行股份有限公司 | User's system management method and device in a kind of e-commerce platform |
| CN105871958A (en) * | 2015-01-21 | 2016-08-17 | 中兴通讯股份有限公司 | Method for managing account information in centralized manner and terminal |
| CN105989485A (en) * | 2015-02-16 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Business management method and device |
| CN105516166A (en) * | 2015-12-22 | 2016-04-20 | 北京奇虎科技有限公司 | Method and system for realizing login by using other account |
| CN105516166B (en) * | 2015-12-22 | 2019-02-12 | 北京奇虎科技有限公司 | A method and system for logging in by borrowing another person's account |
| CN105975845A (en) * | 2016-07-04 | 2016-09-28 | 深圳市游云龙科技有限公司 | Method and device for logging into mechanisms |
| CN105975845B (en) * | 2016-07-04 | 2020-03-27 | 深圳市游云龙科技有限公司 | Mechanism login method and login device |
| CN107979569A (en) * | 2016-10-24 | 2018-05-01 | 中国移动通信有限公司研究院 | A kind of registered information managing device of the Internet, applications, method and system |
| US10698997B2 (en) | 2017-07-14 | 2020-06-30 | Alibaba Group Holding Limited | Login information data processing |
| TWI695290B (en) * | 2017-07-14 | 2020-06-01 | 香港商阿里巴巴集團服務有限公司 | Login information processing method and equipment |
| US10789348B2 (en) | 2017-07-14 | 2020-09-29 | Alibaba Group Holding Limited | Login information data processing |
| CN107277066A (en) * | 2017-08-11 | 2017-10-20 | 中国银行股份有限公司 | Account management method, portable electric appts and account management system |
| CN107483477A (en) * | 2017-09-08 | 2017-12-15 | 上海宝库信息技术有限公司 | Account management method and account management system |
| CN107483477B (en) * | 2017-09-08 | 2020-07-10 | 上海宝库信息技术有限公司 | Account management method and account management system |
| CN107508835A (en) * | 2017-09-25 | 2017-12-22 | 咪咕文化科技有限公司 | Account verification method and device and computer readable storage medium |
| CN107508835B (en) * | 2017-09-25 | 2020-07-10 | 咪咕文化科技有限公司 | Account verification method, device and computer-readable storage medium |
| CN107832592A (en) * | 2017-10-30 | 2018-03-23 | 北京小米移动软件有限公司 | Right management method, device and storage medium |
| CN111541546A (en) * | 2020-04-24 | 2020-08-14 | 前海乔希(深圳)教育科技有限公司 | Multi-platform login method, device, equipment and readable medium |
| CN111541546B (en) * | 2020-04-24 | 2020-11-27 | 前海乔希(深圳)教育科技有限公司 | Multi-platform login method, device, equipment and readable medium |
| CN111614641A (en) * | 2020-05-11 | 2020-09-01 | 北京电信易通信息技术股份有限公司 | Cloud account management system and application method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102546770B (en) | 2015-05-27 |
| WO2013097392A1 (en) | 2013-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102546770B (en) | Unified account management method and third-party account management system | |
| CN105592065B (en) | A kind of website login method and login system based on mobile phone short message | |
| CN105306733A (en) | Third-party login mobile phone number binding method based on mobile phone APP | |
| CN106453414B (en) | Third party login authentication method, proxy server, client and system | |
| CN103840944B (en) | A short message authentication method, server and system | |
| CN102324004A (en) | Verification method for webpage form input information and device | |
| CN109039987A (en) | A kind of user account login method, device, electronic equipment and storage medium | |
| CN107241336B (en) | Identity verification method and device | |
| CN104579671B (en) | Auth method and system | |
| CN109992940B (en) | Authentication method, device, system and authentication server | |
| CN104348802A (en) | Quick registration method, device, and system, cell phone, and register server | |
| CN109995748B (en) | Verification code processing method, device and system | |
| CN105162802B (en) | Portal authentication method and certificate server | |
| CN106789924A (en) | The method and system that a kind of digital certificate protection web site of use mobile terminal is logged in | |
| CN108990047A (en) | Test method, device and the medium of contract signing relationship management data preparation platform | |
| CN110149629A (en) | A kind of method and system of fast registration and login application program based on mobile phone | |
| CN103581881B (en) | Comprehensive number-obtaining device as well as system and method for obtaining cell phone number of user on network side | |
| CN104348613B (en) | User verification method, apparatus and system | |
| CN103124260B (en) | The login method of a kind of Web page and device | |
| CN103001934A (en) | Terminal application login method and terminal application login system | |
| CN105656649A (en) | Service opening method and device for terminal equipment | |
| CN105554136A (en) | Backup data restoration method, device and system | |
| CN109525588B (en) | Verification code processing method, device and system | |
| CN104796263B (en) | User ID authentication method and device | |
| CN105577621B (en) | Business operation verification method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150527 Termination date: 20201226 |