WO2013097392A1 - 一种统一管理账户的方法及第三方账户管理系统 - Google Patents

一种统一管理账户的方法及第三方账户管理系统 Download PDF

Info

Publication number
WO2013097392A1
WO2013097392A1 PCT/CN2012/074999 CN2012074999W WO2013097392A1 WO 2013097392 A1 WO2013097392 A1 WO 2013097392A1 CN 2012074999 W CN2012074999 W CN 2012074999W WO 2013097392 A1 WO2013097392 A1 WO 2013097392A1
Authority
WO
WIPO (PCT)
Prior art keywords
login
account management
information
integrated software
user
Prior art date
Application number
PCT/CN2012/074999
Other languages
English (en)
French (fr)
Inventor
唐欢亮
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2013097392A1 publication Critical patent/WO2013097392A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations

Definitions

  • the present invention relates to account management technologies in a network, and more particularly to a method for uniformly managing accounts and a third party account management system. Background technique
  • a third-party account management system for managing accounts including a user terminal, a third-party account management device, and a service providing terminal, which are specifically: After the user terminal registers with the third-party account management device, the registration can be used. The account is logged into any business that is contracted with the third-party account management system; the third-party account management device will review the developer of the business, and the third-party account management system can be used to verify the business provided by the developer who has reached the agreement. Account login.
  • this kind of third-party account management system is not suitable for the existing integrated software that integrates multiple business services; the integrated software that integrates multiple services requires not only its own login name and login password, but also any arbitrary call in the integrated software itself.
  • the third-party account management system can only provide a login interface for a single service, and cannot use the third-party account management system to log in and use the integration.
  • Comprehensive software for a business is not suitable for the existing integrated software that integrates multiple business services; the integrated software that integrates multiple services requires not only its own login name and login password, but also any arbitrary call in the integrated software itself.
  • an object of the present invention is to provide a method for uniformly managing accounts and a third party account management system, which can log in and use a unified software that integrates multiple services through a unified account, thereby reducing user operations.
  • the present invention provides a third party account management system, the system comprising: a user terminal and a third party account management device;
  • a third-party account management device configured to save the comprehensive software data list and the user account management list; after receiving the login request to the integrated software sent by the user terminal, using the integrated software data list and the user account management list to provide the user terminal with the login Integrated software information;
  • the user terminal is configured to send a login request for the integrated software to the third-party account management device, and receive information about logging in the integrated software provided by the third-party account management device.
  • the third-party account management device is specifically configured to use the identifier of the integrated software, whether the service to be used by the integrated software, the service to be used by the integrated software needs to obtain the login information of the service, and obtain the login information of the service.
  • a comprehensive software profile is created for the related information provided by the user terminal that initiated the login request.
  • the third-party account management device is specifically configured to form a user account management list by using login information of the user basic data, the login password, and other services required to be provided.
  • the third-party account management device is further configured to extract a login name in the login request sent by the user terminal, and use the login name to check whether the user account management list identified by the login name is saved, if not If the user account management list identified by the login name is saved, the notification of the login failure that is not registered is sent to the user terminal; if the user account management list identified by the login name is saved, the login password in the login request is extracted. And compare with the login password recorded in the user account management list. If the two are the same, the verification result is that the login is successful. If the two are different, the login with the wrong password is sent to the user terminal. Notice of failure;
  • the user terminal is further configured to receive a notification of a login failure sent by a third-party account management device.
  • the third-party account management device is further configured to extract the name of the integrated software and the user account information in the login request, and view the comprehensive software data list saved by the user according to the name of the integrated software in the login request, according to the integrated software.
  • the login information of each service that needs to be obtained recorded in the data list, the account information in the login request is used to extract the account information of each service that the user has saved from the user account management list, and the login to the integrated software is obtained according to the account information of each service.
  • Related Information is further configured to extract the name of the integrated software and the user account information in the login request, and view the comprehensive software data list saved by the user according to the name of the integrated software in the login request, according to the integrated software.
  • system further includes: a service providing terminal, configured to send the registration information of the developer to the third party account management device;
  • 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.
  • the third-party account management device further includes: a database module, a registration login module, and a service processing module;
  • a database module configured to provide a business software module with a list of integrated software materials and a user account management list
  • the service processing module is configured to: after receiving the login request for the integrated software sent by the registration login module, use the integrated software profile list and the user account management list in the database module to provide the user terminal with information for logging in the integrated software.
  • the third-party account management device further includes: a verification module and an interface module;
  • a verification module configured to receive registration information of the user terminal sent by the registration login module, The information is verified.
  • the registration information is sent to the service processing module.
  • the registration failure notification is sent to the interface module; the interface module is used to receive the verification module. The notification of registration failure, returning the notification of registration failure to the user terminal;
  • the registration and login module is further configured to determine whether the registration information sent by the user terminal is received, and if received, send the registration information of the user terminal to the verification module to verify the registration information, otherwise, continue to determine whether Receiving registration information sent by the user terminal;
  • the service processing module is further configured to receive registration information sent by the registration module.
  • the present invention provides a method for uniformly managing an account, and the third party account management device saves the integrated software material list and the user account management list; the method further includes:
  • the third-party account management device After receiving the login request for the integrated software sent by the user terminal, the third-party account management device provides the user terminal with the information for logging in to the integrated software by using the integrated software data list and the user account management list.
  • the comprehensive software data list is: after the integrated software is identified, whether the service to be used by the integrated software, the service to be used by the integrated software needs to obtain the login information of the service, and the login information of the service is obtained.
  • the specific content of the relevant information to be provided is a list of contents.
  • 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 method further includes: the third-party account management device extracting the login name in the login request, and viewing the login name by using the login name Whether the user account management list identified by the login name is saved, and if the user account management list identified by the login name is not saved, the notification of the unregistered login failure is sent to the user terminal; if the login is saved The name is the user account management list of the identifier, and the login password in the login request is extracted, and The login passwords recorded in the user account management list are compared. If the two are the same, the verification result is that the login is successful. If the two are different, the login failure notification of the password error is sent to the user terminal.
  • the using the integrated software data list and the user account management list to provide the user terminal with the information for logging in to the integrated software including: the third party account management system extracting the name of the integrated software and the user account information in the login request, according to the login
  • the list of the comprehensive software materials saved in the request is viewed, and the login information of each service acquired in the comprehensive software data list is used, and the user account information in the login request is used to extract the services that the user has saved from the user account management list.
  • the method for uniformly managing an account and the third-party account management system use the integrated software material list to bind the information of the service to be used by the integrated software, and bind the login information of the service to be used by the integrated software by using the user account management list.
  • the comprehensive software data list in the third party account management device is directly associated with the user account management list. All the information after logging in to the integrated software is fed back to the user terminal, thereby realizing login through a unified account and using integrated software integrating multiple services, thereby reducing user operations.
  • FIG. 1 is a schematic structural diagram of a third party account management system according to the present invention.
  • FIG. 2 is a schematic diagram showing the structure of a third-party account management device in a third-party account management system of the present invention
  • FIG. 3 is a schematic flowchart of a method for uniformly managing an account according to the present invention. detailed description
  • the third party account management device saves the comprehensive software data list and the user account management list; the third party account management device receives the login request for any integrated software sent by the user terminal, and uses the integrated software data.
  • the list and user account management list provides the user terminal with information to log in to the integrated software.
  • the comprehensive software data list is: the identifier of the integrated software, whether the service to be used by the integrated software, the service to be used by the integrated software needs to obtain the login information of the service, and obtain the login information of the service, and then initiate the login request. a list of the contents of the related information provided by the user terminal;
  • the user account management list is: a list consisting of user basic data, login password, and other login information of services requested.
  • the present invention provides a third-party account management system, as shown in FIG. 1, including: a user terminal 11, a third-party account management device 12;
  • the third-party account management device 12 is configured to save the integrated software data list and the user account management list; after receiving the login request for any integrated software sent by the user terminal 11, using the integrated software data list and the user account management list as the user The terminal 11 provides information for logging in to the integrated software;
  • the user terminal 11 is configured to send a login request to any of the integrated software to the third party account management device 12, and receive information of the integrated software provided by the third party account management device 12.
  • the user terminal 11 is further configured to connect to the third-party account management device 12 according to the website address of the third-party account management system entered by the user in the web browser, and receive the webpage interface returned by the third-party account management device 12, in the registration sub-
  • the registration information is filled in the menu, and the registration information is sent to the third-party account management device 12; correspondingly, the third-party account management device 12 is further configured to determine whether the registration information sent by the user terminal 11 is received, and if received, Then enter the registration information If the registration information is received, the login information may be: the login name, the user basic information, and the login password; wherein the login name may be defined by the user. Characters and/or numbers; the user basic information may be a user's birthday, a common mailbox, and the like.
  • the third-party account management device 12 is further configured to verify the registration information, and if the verification result is the registration, the registration information is saved, otherwise, the user terminal 11 is notified that the user registration failed; correspondingly, the user terminal 11 .
  • the method is further configured to receive a notification that the registration failure sent by the third-party account management device 12 is failed.
  • 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 user account management list having the same login name has been saved, if the account name is consistent If the user account management list of the same login name is not required, the verification result is the registration, otherwise the verification result is registration failure;
  • the filling requirement is a requirement for filling in a format according to an actual situation.
  • the preset filling requirement is: The length is greater than six digits, and the Chinese character may not 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, save the user basic data and the login password in the registration information in the user account management list, and then send the user account to the user terminal 11 Sending a prompt for the user to fill in the service login information provided in the user account management list, and storing 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 the third party account.
  • the management device 12 sends a request for the user to fill in the login information of the other service in the user account management list, and the login information of the other service filled in by the user is sent to the third party account management device 12;
  • the service login information is: a user login submitted by the integrated software developer and signed by the third-party account management device 12, using all the services to be used by the integrated software. Information.
  • the third-party account management device 12 is further configured to determine whether a login request for any integrated software sent by the user terminal 11 is received, and if received, the login request is verified; otherwise, the processing flow ends;
  • the user terminal 11 is further configured to send a login request to any one of the integrated software to the third party account management device 12;
  • the login request for any one of the integrated software includes: a name of the integrated software, and user account information; and 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. If the verification result is that the login is successful, the user terminal 11 is provided with related information for logging in to the integrated software, and the user terminal 11 is notified that the login fails. Correspondingly, the user terminal 11 is further configured to receive the related information of the integrated software provided by the third-party account management device 12, or receive the notification that the user terminal 11 fails to log in from 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, and use the login name to check whether the user account management list corresponding to the user account information is saved, and if not saved, to the user terminal 11 Send a notification that the login failure has not been registered; if it is saved, extract the login password in the login request and compare it with the login password recorded in the user account management list. If the two are the same, the verification result is successful login, if both Differently, a notification of a login failure of a password error is transmitted to the user terminal 11.
  • the third-party account management device 12 is specifically configured to extract the name of the integrated software and the user account information in the login request, and view the comprehensive software data corresponding to the name of the integrated software saved by the third-party account management device according to the name of the integrated software in the login request. a list, according to the login information of each service that needs to be obtained recorded in the comprehensive software data list, and extracting user account information of each service that the user has saved from the user account management list by using the user account information in the login request; Account information to obtain information related to logging in to the integrated software;
  • the obtaining related information of the integrated software is obtained, and the related information is integrated software.
  • the difference is different, and is related to the agreement between the developer of the integrated software and the third-party account management system, and the method of obtaining is a prior art, and is not mentioned here.
  • the user terminal 11 is further configured to continue to use the integrated software by using the acquired related information of the integrated software, and the method for using the integrated software is a prior art, and is not mentioned here.
  • the third-party account management system further includes: a service providing terminal 13 configured to connect to the third-party account management device 12 according to the website address of the third-party account management system entered by the developer in the web browser, and receive the third-party account management device 12 returned web interface, fill in the registration information in the registration sub-menu, 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 the service delivery terminal 13
  • the registration information is used to determine whether the developer is successfully registered. If the registration is successful, the service providing terminal 13 is notified to fill in any agreement of the integrated software using the third party account management system. Otherwise, the notification service providing terminal 13 fails to register;
  • the registration information may include: a login name, a developer basic information, and a login password; wherein the login name may be a character and/or a number defined by the developer; the developer basic information may be a developer's Company name, company mailbox, etc.
  • 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 information list of the same login name has been saved, and if the login name matches If the developer information list that requires and does not have the same login name is registered, the registration is successful. Otherwise, the registration fails.
  • the third-party account management device 12 is further configured to receive an agreement of the completed integrated software sent by the service providing terminal 13 to use the third-party account management system, and review the developer according to the agreement, and if the audit is approved, establish a comprehensive a software material list, if the audit fails, the service providing terminal 13 reviews the notification that the transmission fails;
  • the integrated software uses the protocol of the third-party account management system, and the information of the integrated software that the developer fills in according to the actual situation may include: the name of the integrated software, comprehensive Whether the service to be used by the software or 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 that needs to be provided after the login information of the service has been obtained.
  • the third-party account management device 12 is specifically configured to use the name of the integrated software in the protocol of the third-party account management system using the integrated software, the service to be used by the integrated software, and whether the service to be used by the integrated software needs to obtain the login of the service.
  • the specific content of the relevant information that needs to be provided after the information is the content.
  • the service providing terminal 13 further transmits a comprehensive service that the user requests to download 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 service providing terminal.
  • the third-party account management device 12 further includes: a database module 121, a registration login module 122, and a service processing module 123;
  • the database module 121 is configured to provide the business processing module 123 with a self-storing integrated software data list and a user account management list;
  • the registration and registration module 122 is configured to send a login request to any one of the integrated software sent by the user terminal to the service processing module 123;
  • the service processing module 123 is configured to: after receiving the login request for any integrated software sent by the registration and login module 122, use the integrated software profile list and the user account management list in the database module 121 to provide the user terminal with the login to the integrated software. information.
  • the third party account management device 12 further includes: a verification module 124 and an interface module 125;
  • the verification module 124 is configured to receive the registration information of the user terminal sent by the registration and login module 122, and verify the registration information.
  • the registration information is sent to the service processing module 123, and the verification result is a registration failure.
  • the notification of registration failure is sent to the interface module Block 125;
  • the interface module 125 is configured to receive the notification of the registration failure sent by the verification module 124, and return the notification of the registration failure to the user terminal;
  • the registration and registration module 122 is further configured to determine whether the registration information sent by the user terminal is received, and if received, send the registration information of the user terminal to the verification module 124 to verify the registration information, otherwise, continue
  • the service processing module 123 is further configured to receive the registration information sent by the registration module.
  • the verification module 124 is specifically configured to: extract the login name in the registration information of the user terminal, detect whether the login name meets the filling requirement, and detect whether the user account management list having the same login name has been saved, if the account name is consistent If the user account management list of the same login name is not required, the verification result is the registration, otherwise the verification result is registration failure.
  • 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, and save the user basic data and the login password in the registration information in the user account management list, and then The user terminal sends a prompt for the user to fill in the service login information in the user account management list, saves the service login information returned by the user terminal in the user account management list, and sends the user account management list to the database module 121; correspondingly, the user terminal
  • the database module 121 is specifically configured to receive and save a user account management list sent by the service processing module 123.
  • the registration and registration module 122 is further configured to determine whether a login request for any integrated software sent by the user terminal is received, and if received, send a login request of the user terminal to any integrated software to the verification module 124. Verification of the login request, otherwise, continue to determine whether a login request to any of the integrated software sent by the user terminal is received;
  • the verification module 124 is further configured to receive a user sent by the registration login module 122.
  • the login request to any integrated software sent by the terminal is used to verify the login request. If the verification result is successful, the login request to the integrated software is sent to the service processing module.
  • the interface module 125 is further configured to send a notification that the verification module 124 sends a login failure to the user terminal;
  • the service processing module 123 is further configured to receive a login request sent by the verification module 124.
  • the verification module 124 is specifically configured to extract user account information in the login request, and use the user account information to check whether the database module 121 saves the corresponding user account management list. If not, the user terminal is sent to the interface module 125. If there is no registered login failure notification, if the user account management list corresponding to the user account information is saved, 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 two If the result is the same, the verification result is that the login is successful. If the two are different, the notification of the login failure of the user terminal password error 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 of the integrated software and the user account information in the login request, and view the database module 121 according to the name of the integrated software in the login request.
  • the saved comprehensive software material list identified by the name of the integrated software, according to the login information of each service acquired in the comprehensive software data list, and the user account management list corresponding to the user account information in the login request.
  • the saved login information of each service provides the specific content of the related information that needs to be provided after the login information of the service has been obtained to the user terminal.
  • the registration and registration module 122 is further configured to receive the registration information sent by the service providing terminal, and send the registration information to the verification module 124.
  • the verification module 124 is further configured to receive the registration sent by the registration login module 122. The information, extracting the login name in the registration information, detecting whether the login name meets the filling requirement, and detecting whether the database module 121 has the same developer name list in the database module 121, if the login name meets the filling requirement, and the user does not have the insurance If the developer profile with the same login name is saved, the registration is successful. Otherwise, the registration fails.
  • the verification module 124 is further configured to send the registration result to the interface module 125.
  • the interface module 125 is further configured to receive the registration result sent by the verification module 124, and notify the service providing when the registration result is successful registration.
  • the terminal fills in the comprehensive software to use the protocol of the third-party account management system.
  • the service providing terminal sends a notification of the registration failure.
  • the interface module 125 is further configured to receive a protocol for using the third-party account management system by the completed integrated software sent by the service providing terminal, and review the developer according to the agreement, and if the audit is approved, establish a comprehensive software data list. If the audit fails, the terminal is notified of the failure to send a notification to the service.
  • the interface module 125 is specifically configured to use the name of the integrated software in the protocol of the third-party account management system by using the integrated software, the service to be used by the integrated software, and whether the service to be used by the integrated software needs to obtain the login information of the service, and establish A comprehensive software material list identified by the name of the integrated software.
  • the comprehensive software data list is based on the business to be used by the integrated software, whether the business to be used by the integrated software needs to obtain the login information of the service, and the login information of the acquired service.
  • the specific content of the related information to be provided is the content, and the final integrated software information list is sent to the database module 121.
  • the database module 121 is specifically configured to receive and save the comprehensive software data list sent by the interface module 125. .
  • Step 301 The third-party account management device determines whether the registration information sent by the user terminal is received, and if yes, step 302 is performed; otherwise, , repeat step 301.
  • Step 302 The third-party account management device verifies the received registration information. If the verification result is that the registration is passed, step 303 is performed; otherwise, the user terminal is notified that the registration fails, and the processing flow is ended.
  • the verification is: extracting the login name in the registration information, detecting whether the login name meets the filling requirement, and detecting whether the user account having the same login name has been saved. If the account name meets the user account management list that fills in the requirements and does not have the same login name, the verification result is the registration, otherwise the verification result is registration failure.
  • Step 303 The third-party account management device saves the registration information, and saves the service login information bound by the user.
  • the saving registration information is: extracting a login name in the registration information, establishing a user account management list identified by the login name, and saving the user basic information and the login password in the registration information in the user account management list;
  • the service login information bound by the user is: the third-party account management device prompts the user to fill in the service login information in the user account management list, and saves the login information filled in by the user in the user account management list;
  • the service login information is: user login information submitted by the integrated software developer signed by the third-party account management device, using all the services used by the integrated software.
  • Step 304 The third-party account management device determines whether a login request for any integrated software is received. If yes, step 305 is performed; otherwise, the processing flow ends.
  • Step 305 The third-party account management device verifies the login request. If the verification result is that the login is successful, step 306 is performed; otherwise, the user terminal is notified that the login fails, and the processing process ends.
  • the verifying the login request is: extracting user account information in the login request, using the user account information to check whether the user account management list is saved by the user account information, and if not saved, sending the unregistered login to the user If the save is successful, the login password in the login request is extracted and compared with the login password recorded in the user account management list. If the two are the same, the verification result is that the login is successful, and if the two are different, the user is Send a notification that the password failed to log in.
  • Step 306 The third-party account management device provides the user with relevant information for logging in to the integrated software according to the login request. Specifically: the third-party account management device extracts the name of the integrated software and the user account information in the login request, and browses the comprehensive software data list saved by the name of the integrated software according to the name of the integrated software in the login request, according to The login information of each service that needs to be obtained recorded in the integrated software data list, and the user account information of each service that the user has saved are extracted from the user account management list corresponding to the user account information in the login request, according to the user account information of each service. Obtain information about logging in to the integrated software;
  • the obtaining the related information of the integrated software, the related information is different according to the integrated software, and is related to the agreement between the developer of the integrated software and the third-party account management device, and the obtaining method is Technology, do not make a comment here.
  • the user equipment can continue to use the integrated software by using the obtained information about logging in the integrated software, and the method of using the integrated software is the prior art, and details are not described herein.
  • the third-party account management device also needs to sign an agreement with the developer of each integrated software. After the agreement is approved, the user can use the integrated software through the third-party account management device, specifically:
  • Step a The developer of the integrated software registers with the third-party account management device, and the third-party account management device determines whether the developer is successfully registered. If the registration is successful, step b is performed; otherwise, the developer is notified that the registration has failed, and the processing flow is ended.
  • the registration is: the developer of the integrated software registers according to the information filled in by the third party account management requirement, and the filled information may include: a login name, a developer basic information, a login password; wherein, the login name The character and/or number that can be defined by the developer itself; the basic information of the developer may be the company name of the developer, the company mailbox, etc.; wherein the developer is registered in the third party account management device, The developer connects to the web interface of the third-party account management device by entering the URL of the third-party account management device in the web browser of the terminal device used by the developer, and registering with the developer according to the web interface Fill in the registration information in the submenu.
  • the determining whether the developer is successfully registered is: extracting the login name in the registration information, detecting whether the login name meets the filling requirement, and detecting whether the user has saved the same developer name list with the same login name, and if the login name meets the filling requirement, If there is no developer profile that has saved the same login name, the registration is successful. Otherwise, the developer is notified that the registration failed.
  • Step b The third-party account management device receives an agreement of any integrated software that the developer fills in using the third-party account management device, and then reviews the developer according to the agreement. If the audit is passed, step C is performed; if the audit fails, Then notify the developer that the review failed, and the process is terminated.
  • the any integrated software uses the protocol of the third-party account management device, and the information of the integrated software required by the developer according to the actual situation may include: the name of the integrated software, the service to be used by the integrated software, and the integrated software to be used. Whether the service needs to obtain the login information of the service, and the specific inner valley of the related information that needs to be provided after the login information of the service has been obtained.
  • Step c The third party account management device establishes a comprehensive software profile list.
  • the list of the integrated software materials is: the name of the integrated software in the protocol using the third-party account management device by using any integrated software, the service to be used by the integrated software, and whether the service to be used by the integrated software needs to acquire the service.
  • the login information establishes a comprehensive software material list identified by the name of the integrated software, and the comprehensive software material list is to use the business to be used by the integrated software, whether the business to be used by the integrated software needs to obtain the login information of the service, and the acquired business.
  • the specific content of the relevant information that needs to be provided after logging in is Neigu.

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

本发明公开了一种第三方账户管理系统,包括:第三方账户管理设备,用于保存综合软件资料列表及用户账户管理列表,接收到用户终端发来的对综合软件的登录请求后,利用综合软件资料列表及用户账户管理列表为用户终端提供登录该综合软件的信息;用户终端,用于向第三方账户管理设备发送对综合软件的登录请求,接收第三方账户管理设备提供的登录该综合软件的信息。本发明还同时公开了一种统一管理账户的方法,采用本发明能通过提供一个统一的账户,登录并使用整合多个业务的综合软件,进而减少用户操作。

Description

一种统一管理账户的方法及第三方账户管理系统 技术领域
本发明涉及网络中的账号管理技术, 尤其涉及一种统一管理账户的方 法及第三方账户管理系统。 背景技术
随着互联网和移动网络的高速发展和完善, 带动了各种业务运营而生。 很多业务需要输入登录名称和登录密码才能使用, 用户需要经常变换自己 的登录名称和登录密码才能使用不同的业务, 如此, 在访问不同的业务时 给用户带来不便。
为了解决上述问题, 提出了一种统一管理账户的第三方账户管理系统, 包括用户终端、 第三方账户管理设备和业务提供终端, 具体为: 用户终端 在第三方账户管理设备注册后, 可以使用注册的账号登录任意一个与第三 方账户管理系统签约的业务; 该第三方账户管理设备会对业务的开发商进 行审核, 通过审核并签约达成协议的开发商所提供的业务才能使用第三方 账户管理系统的账号登录。
但是, 这种第三方账户管理系统不适用于目前已有的整合多个业务业 务的综合软件; 整合多个业务的综合软件除了需要自身的登录名称和登录 密码, 还要在综合软件自身调用任意一个需要用户登录信息的业务时, 由 用户输入该业务的登录名称和登录密码, 而上述第三方账户管理系统仅能 提供单一业务的登录接口, 无法使用该第三方账户管理系统登录并使用整 合多个业务的综合软件。
可见, 现有的第三方账户管理系统无法通过提供一个统一的账户登录 并使用整合多个业务的综合软件, 如此, 会使用户的操作繁多、 复杂化。 发明内容
有鉴于此, 本发明的目的在于提供一种统一管理账户的方法及第三方 账户管理系统, 能通过一个统一的账户登录并使用整合多个业务的综合软 件, 进而减少用户操作。
为达到上述目的, 本发明的技术方案是这样实现的:
本发明提供了一种第三方账户管理系统, 该系统包括: 用户终端和第 三方账户管理设备; 其中,
第三方账户管理设备, 用于保存综合软件资料列表及用户账户管理列 表; 接收到用户终端发来的对综合软件的登录请求后, 利用综合软件资料 列表及用户账户管理列表为用户终端提供登录该综合软件的信息;
用户终端, 用于向第三方账户管理设备发送对综合软件的登录请求, 接收第三方账户管理设备提供的登录该综合软件的信息。
上述方案中, 所述第三方账户管理设备, 具体用于以综合软件的标识, 综合软件所要使用的业务、 综合软件所要使用的业务是否需要获取该业务 的登录信息、 以及获取业务的登录信息后为发起登录请求的用户终端提供 的相关信息建立综合软件资料列表。
上述方案中, 所述第三方账户管理设备, 具体用于以用户基本资料、 登录密码及其他要求提供的业务的登录信息组成用户账户管理列表。
上述方案中, 所述第三方账户管理设备, 还用于提取用户终端发来的 登录请求中的登录名称, 利用登录名称查看自身是否保存过以该登录名称 为标识的用户账户管理列表, 如果没有保存过以该登录名称为标识的用户 账户管理列表, 则向用户终端发送没有注册的登录失败的通知; 如果保存 有以该登录名称为标识的用户账户管理列表, 则提取登录请求中的登录密 码, 与用户账户管理列表中记录的登录密码进行比较, 如果两者相同, 则 验证结果为登录成功, 如果两者不同, 则向用户终端发送密码错误的登录 失败的通知;
相应的, 所述用户终端, 还用于接收第三方账户管理设备发来的登录 失败的通知。
上述方案中, 所述第三方账户管理设备, 还用于提取登录请求中的综 合软件的名称和用户账户信息, 根据登录请求中的综合软件的名称查看自 身保存的综合软件资料列表, 根据综合软件资料列表中记录的需要获取的 各个业务的登录信息、 利用登录请求中的账户信息从用户账户管理列表中 提取用户已经保存的各个业务的账户信息, 根据各个业务的账户信息获取 登录该综合软件的相关信息。
上述方案中, 所述系统, 还包括: 业务提供终端, 用于将开发商的注 册信息发送给第三方账户管理设备;
相应的, 所述第三方账户管理设备, 还用于接收业务提供终端发来的 注册信息, 判断开发商是否注册成功。
上述方案中, 所述第三方账户管理设备, 进一步包括: 数据库模块、 注册登录模块和业务处理模块; 其中,
数据库模块, 用于为业务处理模块提供自身保存的综合软件资料列表 及用户账户管理列表;
注册登录模块, 将接收到用户终端发来的对综合软件的登录请求发送 给业务处理模块;
业务处理模块, 用于接收到注册登录模块发来的对综合软件的登录请 求后, 利用数据库模块中的综合软件资料列表及用户账户管理列表为用户 终端提供登录该综合软件的信息。
上述方案中, 所述第三方账户管理设备, 进一步包括: 验证模块和接 口模块; 其中,
验证模块, 用于接收注册登录模块发来的用户终端的注册信息, 对注 册信息进行验证, 当验证结果为注册通过时, 将注册信息发送给业务处理 模块, 当验证结果为注册失败时, 将注册失败的通知发送给接口模块; 接口模块, 用于接收验证模块发来的注册失败的通知, 将注册失败的 通知返回给用户终端;
相应的, 所述注册登录模块, 还用于判断是否接收到用户终端发来的 注册信息, 如果接收到, 则将用户终端的注册信息发送到验证模块对注册 信息进行验证, 否则, 继续判断是否接收到用户终端发来的注册信息; 所述业务处理模块, 还用于接收注册模块发来的注册信息。
本发明该提供了一种统一管理账户的方法, 第三方账户管理设备保存 综合软件资料列表及用户账户管理列表; 该方法还包括:
所述第三方账户管理设备接收到用户终端发来的对综合软件的登录请 求后, 利用综合软件资料列表及用户账户管理列表为用户终端提供登录该 综合软件的信息。
上述方案中, 所述综合软件资料列表, 为: 以综合软件的标识, 以综 合软件所要使用的业务、 综合软件所要使用的业务是否需要获取该业务的 登录信息、 以及获取业务的登录信息后所需提供的相关信息的具体内容为 内容的列表。
上述方案中, 所述用户账户管理列表为: 以用户基本资料、 登录密码 及其他要求提供的业务的登录信息组成的列表。
上述方案中, 所述该第三方账户管理设备接收到用户终端发来的对综 合软件的登录请求之后, 该方法还包括: 第三方账户管理设备提取登录请 求中的登录名称, 利用登录名称查看自身是否保存过以该登录名称为标识 的用户账户管理列表, 如果没有保存过以该登录名称为标识的用户账户管 理列表, 则向用户终端发送没有注册的登录失败的通知; 如果保存有以该 登录名称为标识的用户账户管理列表, 则提取登录请求中的登录密码, 与 用户账户管理列表中记录的登录密码进行比较, 如果两者相同, 则验证结 果为登录成功, 如果两者不同, 则向用户终端发送密码错误的登录失败的 通知。
上述方案中, 所述利用综合软件资料列表及用户账户管理列表为用户 终端提供登录该综合软件的信息, 包括: 第三方账户管理系统提取登录请 求中的综合软件的名称和用户账户信息, 根据登录请求中的查看自身保存 的综合软件资料列表, 根据综合软件资料列表中记录的需要获取的各个业 务的登录信息、 利用登录请求中用户账户信息从用户账户管理列表中提取 用户已经保存的各个业务的用户账户信息, 根据各个业务的用户账户信息 获取登录该综合软件的相关信息。
本发明所提供的统一管理账户的方法及第三方账户管理系统, 使用综 合软件资料列表绑定综合软件所要使用的业务的信息, 并使用用户账户管 理列表绑定综合软件所要使用的业务的登录信息, 如此, 用户通过用户终 端登录任意一个综合软件时, 不必在综合软件的多个整合业务中再次输入 登录信息, 而由第三方账户管理设备中的综合软件资料列表和用户账户管 理列表直接关联, 将登录该综合软件后的所有信息反馈给用户终端, 从而 实现通过一个统一的账户登录并使用整合多个业务的综合软件, 进而减少 用户操作。 附图说明
图 1为本发明第三方账户管理系统的组成结构示意图;
图 2为本发明第三方账户管理系统中第三方账户管理设备的组成结构 示意图;
图 3为本发明统一管理账户的方法流程示意图。 具体实施方式
本发明的基本思想是: 第三方账户管理设备保存综合软件资料列表及 用户账户管理列表; 该第三方账户管理设备接收到用户终端发来的对任意 一个综合软件的登录请求后, 利用综合软件资料列表及用户账户管理列表 为用户终端提供登录该综合软件的信息。
其中, 所述综合软件资料列表为: 以综合软件的标识, 以综合软件所 要使用的业务、 综合软件所要使用的业务是否需要获取该业务的登录信息、 及获取业务的登录信息后为发起登录请求的用户终端提供的相关信息的内 容组成的列表;
所述用户账户管理列表为: 以用户基本资料、 登录密码及其他要求提 供的业务的登录信息组成的列表。
下面结合附图及具体实施例对本发明再作进一步详细的说明。
本发明提供了一种第三方账户管理系统, 如图 1 所示, 包括: 用户终 端 11、 第三方账户管理设备 12; 其中,
第三方账户管理设备 12, 用于保存综合软件资料列表及用户账户管理 列表; 接收到用户终端 11发来的对任意一个综合软件的登录请求后, 利用 综合软件资料列表及用户账户管理列表为用户终端 11提供登录该综合软件 的信息;
用户终端 11 ,用于向第三方账户管理设备 12发送对任意一个综合软件 的登录请求, 接收第三方账户管理设备 12提供的登录该综合软件的信息。
所述用户终端 11 , 还用于根据用户在网页浏览器中输入的第三方账户 管理系统的网址, 连接到第三方账户管理设备 12, 接收第三方账户管理设 备 12返回的网页界面, 在注册子菜单中填写注册信息, 将注册信息发送给 第三方账户管理设备 12; 相应的, 所述第三方账户管理设备 12, 还用于判 断是否接收到用户终端 11发来的注册信息, 如果接收到, 则对注册信息进 行验证, 否则, 继续判断是否接收到用户终端 11发来的注册信息; 其中, 所述注册信息可以包括: 登录名称、 用户基本信息、 登录密码; 其中, 所述登录名称可以为用户自己定义的字符和 /或数字; 所述用户基本 信息可以为用户的生日、 常用邮箱等。
所述第三方账户管理设备 12, 还用于对注册信息进行验证, 如果验证 结果为注册通过, 则保存注册信息, 否则, 向用户终端 11发送用户注册失 败的通知; 相应的, 所述用户终端 11 , 还用于接收第三方账户管理设备 12 发来的注册失败的通知。
所述第三方账户管理设备 12, 具体用于提取注册信息中的登录名称, 检测登录名称是否符合填写要求, 并检测自身是否已经保存有相同的登录 名称的用户账户管理列表, 如果账户名称符合填写要求、 且自身没有保存 过相同的登录名称的用户账户管理列表, 则验证结果为注册通过, 否则验 证结果为注册失败;
其中, 所述填写要求为根据实际情况预置的填写格式的要求, 比如, 可以预置填写要求为: 长度大于六位, 不得包括中文字符。
所述第三方账户管理设备 12, 具体用于提取注册信息中的登录名称, 建立用户账户管理列表, 将注册信息中的用户基本资料和登录密码保存在 用户账户管理列表中, 然后向用户终端 11发送要求用户填写用户账户管理 列表中提供的业务登录信息的提示, 将用户终端 11返回的业务登录信息保 存在用户账户管理列表中; 相应的, 所述用户终端 11 , 还用于接收第三方 账户管理设备 12发来的要求用户填写用户账户管理列表中的其他业务的登 录信息的提示, 将用户填写的其他业务的登录信息发送给第三方账户管理 设备 12;
其中, 所述业务登录信息为: 综合软件开发商所提交的、 与第三方账 户管理设备 12中签约的, 使用综合软件所要使用到的所有业务的用户登录 信息。
所述第三方账户管理设备 12,还用于判断是否接收到用户终端 11发来 的对任意一个综合软件的登录请求, 如果接收到, 则对该登录请求进行验 证, 否则, 结束处理流程; 相应的, 所述用户终端 11 , 还用于向第三方账 户管理设备 12发送对任意一个综合软件的登录请求;
其中, 所述对任意一个综合软件的登录请求, 包括: 综合软件的名称、 用户账户信息; 所述用户账户信息包括登录名称和登录密码。
所述第三方账户管理设备 12, 还用于对登录请求进行验证, 如果验证 结果为登录成功,则为用户终端 11提供登录该综合软件的相关信息,否贝' J , 通知用户终端 11登录失败; 相应的, 所述用户终端 11 , 还用于接收第三方 账户管理设备 12提供的登录该综合软件的相关信息, 或接收第三方账户管 理设备 12发来的用户终端 11登录失败的通知。
所述第三方账户管理设备 12, 具体用于提取登录请求中的用户账户信 息, 利用登录名称查看自身是否保存过该用户账户信息对应的用户账户管 理列表, 如果没有保存过, 则向用户终端 11发送没有注册的登录失败的通 知; 如果保存过, 则提取登录请求中的登录密码, 与用户账户管理列表中 记录的登录密码进行比较, 如果两者相同, 则验证结果为登录成功, 如果 两者不同, 则向用户终端 11发送密码错误的登录失败的通知。
所述第三方账户管理设备 12, 具体用于提取该登录请求中的综合软件 的名称和用户账户信息, 根据登录请求中的综合软件的名称查看自身保存 的该综合软件的名称对应的综合软件资料列表, 根据该综合软件资料列表 中记录的需要获取的各个业务的登录信息、 利用登录请求中用户账户信息 从用户账户管理列表中提取用户已经保存的各个业务的用户账户信息; 根 据各个业务的用户账户信息获取登录该综合软件的相关信息;
其中, 所述获取登录该综合软件的相关信息, 其相关信息因综合软件 的不同而不同, 并且与综合软件的开发商与第三方账户管理系统签订的协 议相关, 所述获取的方法为已有技术, 这里不做赞述。
所述用户终端 11 , 还用于利用获取的登录该综合软件的相关信息继续 使用综合软件, 具体使用综合软件的方法为已有技术, 这里不做赞述。
所述第三方账户管理系统还包括: 业务提供终端 13, 用于根据开发商 在网页浏览器中输入的第三方账户管理系统的网址, 连接到第三方账户管 理设备 12,接收第三方账户管理设备 12返回的网页界面,在注册子菜单中 填写注册信息, 将注册信息发送给第三方账户管理设备 12; 相应的, 所述 第三方账户管理设备 12,还用于接收业务提供终端 13发来的注册信息, 判 断开发商是否注册成功, 如果注册成功, 则通知业务提供终端 13填写任意 一个综合软件使用第三方账户管理系统的协议, 否则, 通知业务提供终端 13注册失败;
其中, 所述注册信息可以包括: 登录名称、 开发商基本信息、 登录密 码; 其中, 所述登录名称可以为开发商自己定义的字符和 /或数字; 所述开 发商基本信息可以为开发商的公司名称、 公司邮箱等。
所述第三方账户管理设备 12, 具体用于提取注册信息中的登录名称, 检测登录名称是否符合填写要求, 并检测自身是否已经保存有相同的登录 名称的开发商资料列表, 如果登录名称符合填写要求、 且自身没有保存过 相同的登录名称的开发商资料列表, 则注册成功, 否则, 注册失败。
所述第三方账户管理设备 12,还用于接收业务提供终端 13发来的填写 好的综合软件使用第三方账户管理系统的协议, 根据该协议对开发商进行 审核, 如果审核通过, 则建立综合软件资料列表, 如果审核不通过, 则向 业务提供终端 13审核发送不通过的通知;
其中, 所述综合软件使用第三方账户管理系统的协议, 为根据实际情 况要求开发商填写的综合软件的信息, 可以包括: 综合软件的名称、 综合 软件所要使用的业务、 综合软件所要使用的业务是否需要获取该业务的登 录信息、 已获取业务的登录信息后所需提供的相关信息的具体内容。
所述第三方账户管理设备 12, 具体用于利用综合软件使用第三方账户 管理系统的协议中综合软件的名称、 综合软件所要使用的业务、 及综合软 件所要使用的业务是否需要获取该业务的登录信息, 建立以综合软件的名 称为标识的综合软件资料列表, 该综合软件资料列表以综合软件所要使用 的业务、 综合软件所要使用的业务是否需要获取该业务的登录信息、 以及 已获取业务的登录信息后所需提供的相关信息的具体内容为内容。
所述业务提供终端 13,还用户向用户终端 11发送用户请求下载的综合 业务; 相应的, 所述用户终端 11 , 还用于向业务提供终端 13发送下载综合 业务的请求, 并接收业务提供终端发来的综合业务。
如图 2所示,所述第三方账户管理设备 12进一步包括:数据库模块 121、 注册登录模块 122和业务处理模块 123; 其中,
数据库模块 121 ,用于为业务处理模块 123提供自身保存综合软件资料 列表及用户账户管理列表;
注册登录模块 122,用于将接收到用户终端发来的对任意一个综合软件 的登录请求发送给业务处理模块 123;
业务处理模块 123 ,用于接收到注册登录模块 122发来的对任意一个综 合软件的登录请求后, 利用数据库模块 121 中的综合软件资料列表及用户 账户管理列表为用户终端提供登录该综合软件的信息。
所述第三方账户管理设备 12进一步包括: 验证模块 124和接口模块 125; 其中,
验证模块 124,用于接收注册登录模块 122发来的用户终端的注册信息, 对注册信息进行验证, 当验证结果为注册通过时, 将注册信息发送给业务 处理模块 123 , 当验证结果为注册失败时, 将注册失败的通知发送给接口模 块 125;
接口模块 125, 用于接收验证模块 124发来的注册失败的通知,将注册 失败的通知返回给用户终端;
相应的, 所述注册登录模块 122,还用于判断是否接收到用户终端发来 的注册信息, 如果接收到, 则将用户终端的注册信息发送到验证模块 124 对注册信息进行验证, 否则, 继续判断是否接收到用户终端发来的注册信 所述业务处理模块 123, 还用于接收注册模块发来的注册信息。
所述验证模块 124, 具体用于用户终端的提取注册信息中的登录名称, 检测登录名称是否符合填写要求, 并检测自身是否已经保存有相同的登录 名称的用户账户管理列表, 如果账户名称符合填写要求、 且自身没有保存 过相同的登录名称的用户账户管理列表, 则验证结果为注册通过, 否则验 证结果为注册失败。
所述业务处理模块 123, 具体用于提取注册信息中的登录名称, 建立该 登录名称对应的用户账户管理列表, 将注册信息中的用户基本资料和登录 密码保存在用户账户管理列表中, 然后向用户终端发送要求用户填写用户 账户管理列表中的业务登录信息的提示, 将用户终端返回的业务登录信息 保存在用户账户管理列表中, 将用户账户管理列表发送给数据库模块 121; 相应的, 所述数据库模块 121 , 具体用于接收并保存业务处理模块 123发来 的用户账户管理列表。
所述注册登录模块 122,还用于判断是否接收到用户终端发来的对任意 一个综合软件的登录请求, 如果接收到, 则将用户终端的对任意一个综合 软件的登录请求发送到验证模块 124对登录请求进行验证, 否则, 继续判 断是否接收到用户终端发来的对任意一个综合软件的登录请求;
相应的, 所述验证模块 124,还用于接收注册登录模块 122发来的用户 终端发来的对任意一个综合软件的登录请求, 对登录请求进行验证, 如果 验证结果为登录成功, 则将该对综合软件的登录请求发送给业务处理模块
123, 否则, 将登录失败的通知发送给接口模块 125;
所述接口模块 125,还用于将验证模块 124发来登录失败的通知发送给 用户终端;
所述业务处理模块 123 , 还用于接收验证模块 124发来的登录请求。 所述验证模块 124, 具体用于提取登录请求中的用户账户信息, 利用用 户账户信息查看数据库模块 121 是否保存过对应的用户账户管理列表, 如 果没有保存过, 则向接口模块 125发送该用户终端没有注册的登录失败的 通知; 如果保存有该用户账户信息对应的用户账户管理列表, 则提取登录 请求中的登录密码, 与数据库模块 121 中的用户账户管理列表记录的登录 密码进行比较, 如果两者相同, 则验证结果为登录成功, 如果两者不同, 则向接口模块 125发送该用户终端密码错误的登录失败的通知。
所述业务处理模块 123 , 还用于接收验证模块 124发来的登录请求后, 提取该登录请求中的综合软件的名称和用户账户信息, 根据登录请求中的 综合软件的名称查看数据库模块 121 中保存的以综合软件的名称为标识的 综合软件资料列表, 根据综合软件资料列表中记录的需要获取的各个业务 的登录信息、 从以登录请求中用户账户信息对应的用户账户管理列表中提 取用户已经保存的各个业务的登录信息, 提供已获取业务的登录信息后所 需提供的相关信息的具体内容给用户终端。
所述注册登录模块 122,还用于接收业务提供终端发来的注册信息,将 注册信息发送给验证模块 124; 相应的, 所述验证模块 124, 还用于接收注 册登录模块 122发来的注册信息, 提取注册信息中的登录名称, 检测登录 名称是否符合填写要求、 并检测数据库模块 121 中是否已经保存有相同的 登录名称的开发商资料列表, 如果登录名称符合填写要求、 且自身没有保 存过相同的登录名称的开发商资料列表, 则注册成功, 否则, 注册失败。 所述验证模块 124, 还用于向接口模块 125向发送注册结果; 相应的, 所述接口模块 125 ,还用于接收验证模块 124发来注册结果, 当注册结果为 注册成功时, 通知业务提供终端填写综合软件使用第三方账户管理系统的 协议, 当注册结果为注册失败时, 业务提供终端发送注册失败的通知。
所述接口模块 125 ,还用于接收业务提供终端发来的填写好的综合软件 使用第三方账户管理系统的协议, 根据该协议对开发商进行审核, 如果审 核通过, 则建立综合软件资料列表, 如果审核不通过, 则向业务提供终端 审核发送不通过的通知。
所述接口模块 125 ,具体用于利用综合软件使用第三方账户管理系统的 协议中综合软件的名称、 综合软件所要使用的业务、 以及综合软件所要使 用的业务是否需要获取该业务的登录信息, 建立以综合软件的名称为标识 的综合软件资料列表, 该综合软件资料列表以综合软件所要使用的业务、 综合软件所要使用的业务是否需要获取该业务的登录信息、 以及已获取业 务的登录信息后所需提供的相关信息的具体内容为内容, 将最终建立的综 合软件资料列表发送给数据库模块 121 ; 相应的, 所述数据库模块 121 , 具 体用于接收并保存接口模块 125发来的综合软件资料列表。
如图 3所示, 本发明提供的统一管理账户的方法, 包括以下步驟: 步驟 301 :第三方账户管理设备判断是否接收到用户终端发来的注册信 息, 如果接收到, 则执行步驟 302; 否则, 重复执行步驟 301。
步驟 302: 第三方账户管理设备对收到的注册信息进行验证, 如果验证 结果为注册通过, 则执行步驟 303; 否则, 通知用户终端注册失败, 结束处 理流程。
这里, 所述验证为: 提取注册信息中的登录名称, 检测登录名称是否 符合填写要求, 并检测自身是否已经保存有相同的登录名称的用户账户管 理列表, 如果账户名称符合填写要求、 且自身没有保存过相同的登录名称 的用户账户管理列表, 则验证结果为注册通过, 否则验证结果为注册失败。
步驟 303: 第三方账户管理设备保存注册信息, 并保存用户绑定的业务 登录信息。
这里, 所述保存注册信息为: 提取注册信息中的登录名称, 建立以该 登录名称为标识的用户账户管理列表, 将注册信息中的用户基本资料和登 录密码保存在用户账户管理列表中;
所述保存用户绑定的业务登录信息为: 第三方账户管理设备提示用户 填写用户账户管理列表中的业务登录信息, 将用户填写的登录信息保存在 用户账户管理列表中;
其中, 所述业务登录信息为: 第三方账户管理设备中签约的综合软件 开发商所提交的, 使用综合软件所要使用到的所有业务的用户登录信息。
步驟 304:第三方账户管理设备判断是否接收到对任意一个综合软件的 登录请求, 如果接收到, 则执行步驟 305; 否则, 结束处理流程。
步驟 305: 第三方账户管理设备对该登录请求进行验证,如果验证结果 为登录成功, 则执行步驟 306; 否则, 通知用户终端登录失败, 结束处理流 程。
这里, 所述对登录请求进行验证为: 提取登录请求中的用户账户信息, 利用用户账户信息查看自身是否保存过以对应的用户账户管理列表, 如果 没有保存过, 则向用户发送没有注册的登录失败的通知; 如果保存过, 则 提取登录请求中的登录密码, 与用户账户管理列表中记录的登录密码进行 比较, 如果两者相同, 则验证结果为登录成功, 如果两者不同, 则向用户 发送密码错误的登录失败的通知。
步驟 306:第三方账户管理设备根据该登录请求为用户提供登录该综合 软件的相关信息。 具体的: 第三方账户管理设备提取该登录请求中的综合软件的名称和 用户账户信息, 根据登录请求中的综合软件的名称查看自身保存的以综合 软件的名称为标识的综合软件资料列表, 根据综合软件资料列表中记录的 需要获取的各个业务的登录信息、 从以登录请求中用户账户信息对应的用 户账户管理列表中提取用户已经保存的各个业务的用户账户信息, 根据各 个业务的用户账户信息获取登录该综合软件的相关信息;
其中, 所述获取登录该综合软件的相关信息, 其相关信息因综合软件 的不同而不同, 并且与综合软件的开发商与第三方账户管理设备签订的协 议相关, 所述获取的方法为已有技术, 这里不做赞述。
上述步驟 306 完成后, 用户设备就可以利用获取的登录该综合软件的 相关信息继续使用综合软件, 具体使用综合软件的方法为已有技术, 这里 不做赘述。
另外, 在上述步驟 301之前, 第三方账户管理设备还需要同各个综合 软件的开发商签订协议, 在协议审核通过后, 用户才能够通过第三方账户 管理设备使用综合软件, 具体为:
步驟 a: 综合软件的开发商在第三方账户管理设备中注册, 第三方账户 管理设备判断开发商是否注册成功, 如果注册成功, 则执行步驟 b; 否则, 通知开发商注册失败, 结束处理流程。
这里, 所述注册为: 综合软件的开发商根据第三方账户管理要求填写 的信息进行注册, 所述填写的信息, 可以包括: 登录名称、 开发商基本信 息、 登录密码; 其中, 所述登录名称, 可以为开发商自己定义的字符和 /或 数字; 所述开发商基本信息, 可以为开发商的公司名称、 公司邮箱等; 其中, 所述开发商在第三方账户管理设备中注册, 可以为: 开发商通 过在开发商使用的终端设备的网页浏览器中输入第三方账户管理设备的网 址, 连接到第三方账户管理设备的网页界面, 根据网页界面上开发商注册 子菜单中填写注册信息。
所述判断开发商是否注册成功为: 提取注册信息中的登录名称, 检测 登录名称是否符合填写要求、 并检测自身是否已经保存有相同的登录名称 的开发商资料列表, 如果登录名称符合填写要求、 且自身没有保存过相同 的登录名称的开发商资料列表, 则注册成功, 否则, 通知开发商注册失败。
步驟 b:第三方账户管理设备接收开发商填写的任意一个综合软件使用 第三方账户管理设备的协议, 然后根据该协议对开发商进行审核, 如果审 核通过, 则执行步驟 C; 如果审核不通过, 则通知开发商审核不通过, 结束 处理流程。
这里, 所述任意一个综合软件使用第三方账户管理设备的协议, 为根 据实际情况要求开发商填写的综合软件的信息, 可以包括: 综合软件的名 称、 综合软件所要使用的业务、 综合软件所要使用的业务是否需要获取该 业务的登录信息、 已获取业务的登录信息后所需提供的相关信息的具体内 谷。
步驟 c: 第三方账户管理设备建立综合软件资料列表。
这里, 所述建立综合软件资料列表为: 利用任意一个综合软件使用第 三方账户管理设备的协议中综合软件的名称、 综合软件所要使用的业务、 以及综合软件所要使用的业务是否需要获取该业务的登录信息, 建立以综 合软件的名称为标识的综合软件资料列表, 该综合软件资料列表以综合软 件所要使用的业务、 综合软件所要使用的业务是否需要获取该业务的登录 信息、 以及已获取业务的登录信息后所需提供的相关信息的具体内容为内 谷。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种第三方账户管理系统, 其特征在于, 该系统包括: 用户终端和 第三方账户管理设备; 其中,
第三方账户管理设备, 用于保存综合软件资料列表及用户账户管理列 表; 接收到用户终端发来的对综合软件的登录请求后, 利用综合软件资料 列表及用户账户管理列表为用户终端提供登录该综合软件的信息;
用户终端, 用于向第三方账户管理设备发送对综合软件的登录请求, 接收第三方账户管理设备提供的登录该综合软件的信息。
2、 根据权利要求 1所述的系统, 其特征在于,
所述第三方账户管理设备, 具体用于以综合软件的标识, 综合软件所 要使用的业务、 综合软件所要使用的业务是否需要获取该业务的登录信息、 以及获取业务的登录信息后为发起登录请求的用户终端提供的相关信息建 立综合软件资料列表。
3、 根据权利要求 1所述的系统, 其特征在于,
所述第三方账户管理设备, 具体用于以用户基本资料、 登录密码及其 他要求提供的业务的登录信息组成用户账户管理列表。
4、 根据权利要求 1所述的系统, 其特征在于,
所述第三方账户管理设备, 还用于提取用户终端发来的登录请求中的 登录名称, 利用登录名称查看自身是否保存过以该登录名称为标识的用户 账户管理列表, 如果没有保存过以该登录名称为标识的用户账户管理列表, 则向用户终端发送没有注册的登录失败的通知; 如果保存有以该登录名称 为标识的用户账户管理列表, 则提取登录请求中的登录密码, 与用户账户 管理列表中记录的登录密码进行比较, 如果两者相同, 则验证结果为登录 成功, 如果两者不同, 则向用户终端发送密码错误的登录失败的通知; 相应的, 所述用户终端, 还用于接收第三方账户管理设备发来的登录 失败的通知。
5、 根据权利要求 1所述的系统, 其特征在于,
所述第三方账户管理设备, 还用于提取登录请求中的综合软件的名称 和用户账户信息, 根据登录请求中的综合软件的名称查看自身保存的综合 软件资料列表, 根据综合软件资料列表中记录的需要获取的各个业务的登 录信息、 利用登录请求中的账户信息从用户账户管理列表中提取用户已经 保存的各个业务的账户信息, 根据各个业务的账户信息获取登录该综合软 件的相关信息。
6、 根据权利要求 1所述的系统, 其特征在于, 所述系统还包括: 业务 提供终端, 用于将开发商的注册信息发送给第三方账户管理设备;
相应的, 所述第三方账户管理设备, 还用于接收业务提供终端发来的 注册信息, 判断开发商是否注册成功。
7、 根据权利要求 6所述的系统, 其特征在于, 所述第三方账户管理设 备包括: 数据库模块、 注册登录模块和业务处理模块; 其中,
数据库模块, 用于为业务处理模块提供自身保存的综合软件资料列表 及用户账户管理列表;
注册登录模块, 将接收到用户终端发来的对综合软件的登录请求发送 给业务处理模块;
业务处理模块, 用于接收到注册登录模块发来的对综合软件的登录请 求后, 利用数据库模块中的综合软件资料列表及用户账户管理列表为用户 终端提供登录该综合软件的信息。
8、 根据权利要求 7所述的系统, 其特征在于, 所述第三方账户管理设 备, 进一步包括: 验证模块和接口模块; 其中,
验证模块, 用于接收注册登录模块发来的用户终端的注册信息, 对注 册信息进行验证, 当验证结果为注册通过时, 将注册信息发送给业务处理 模块, 当验证结果为注册失败时, 将注册失败的通知发送给接口模块; 接口模块, 用于接收验证模块发来的注册失败的通知, 将注册失败的 通知返回给用户终端;
相应的, 所述注册登录模块, 还用于判断是否接收到用户终端发来的 注册信息, 如果接收到, 则将用户终端的注册信息发送到验证模块对注册 信息进行验证, 否则, 继续判断是否接收到用户终端发来的注册信息; 所述业务处理模块, 还用于接收注册模块发来的注册信息。
9、 一种统一管理账户的方法, 其特征在于, 第三方账户管理设备保存 综合软件资料列表及用户账户管理列表; 该方法还包括:
所述第三方账户管理设备接收到用户终端发来的对综合软件的登录请 求后, 利用综合软件资料列表及用户账户管理列表为用户终端提供登录该 综合软件的信息。
10、 根据权利要求 9所述的方法, 其特征在于, 所述综合软件资料列 表, 为: 以综合软件的标识, 以综合软件所要使用的业务、 综合软件所要 使用的业务是否需要获取该业务的登录信息、 以及获取业务的登录信息后 所需提供的相关信息的具体内容为内容的列表。
11、 根据权利要求 9所述的方法, 其特征在于, 所述用户账户管理列 表为: 以用户基本资料、 登录密码及其他要求提供的业务的登录信息组成 的列表。
12、 根据权利要求 9所述的方法, 其特征在于, 所述该第三方账户管 理设备接收到用户终端发来的对综合软件的登录请求之后, 该方法还包括: 第三方账户管理设备提取登录请求中的登录名称, 利用登录名称查看自身 是否保存过以该登录名称为标识的用户账户管理列表, 如果没有保存过以 该登录名称为标识的用户账户管理列表, 则向用户终端发送没有注册的登 录失败的通知; 如果保存有以该登录名称为标识的用户账户管理列表, 则 提取登录请求中的登录密码, 与用户账户管理列表中记录的登录密码进行 比较, 如果两者相同, 则验证结果为登录成功, 如果两者不同, 则向用户 终端发送密码错误的登录失败的通知。
13、 根据权利要求 9所述的方法, 其特征在于, 所述利用综合软件资 料列表及用户账户管理列表为用户终端提供登录该综合软件的信息, 包括: 第三方账户管理系统提取登录请求中的综合软件的名称和用户账户信息, 根据登录请求中的查看自身保存的综合软件资料列表, 根据综合软件资料 列表中记录的需要获取的各个业务的登录信息、 利用登录请求中用户账户 信息从用户账户管理列表中提取用户已经保存的各个业务的用户账户信 息, 根据各个业务的用户账户信息获取登录该综合软件的相关信息。
PCT/CN2012/074999 2011-12-26 2012-05-02 一种统一管理账户的方法及第三方账户管理系统 WO2013097392A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110440776.1A CN102546770B (zh) 2011-12-26 2011-12-26 一种统一管理账户的方法及第三方账户管理系统
CN201110440776.1 2011-12-26

Publications (1)

Publication Number Publication Date
WO2013097392A1 true WO2013097392A1 (zh) 2013-07-04

Family

ID=46352717

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/074999 WO2013097392A1 (zh) 2011-12-26 2012-05-02 一种统一管理账户的方法及第三方账户管理系统

Country Status (2)

Country Link
CN (1) CN102546770B (zh)
WO (1) WO2013097392A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109543372A (zh) * 2018-10-26 2019-03-29 深圳壹账通智能科技有限公司 业务权限数据处理方法、装置、计算机设备及存储介质
CN111541546A (zh) * 2020-04-24 2020-08-14 前海乔希(深圳)教育科技有限公司 多平台登陆方法、装置、设备及可读介质
CN114553504A (zh) * 2022-01-29 2022-05-27 重庆华唐云树科技有限公司 一种第三方安全登录方法
CN114640511A (zh) * 2022-03-04 2022-06-17 上海医栗医疗科技有限公司 应用接口监控平台

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103023875B (zh) * 2012-11-21 2015-09-02 北京荣之联科技股份有限公司 一种账户管理系统及方法
CN103347084B (zh) * 2013-07-10 2017-11-21 上海斐讯数据通信技术有限公司 一种多账号统一关联系统及关联方法
CN104518876B (zh) * 2013-09-29 2019-01-04 腾讯科技(深圳)有限公司 服务登录方法及装置
CN104392368B (zh) * 2014-10-21 2018-12-14 中国建设银行股份有限公司 一种电子商务平台中用户体系管理方法及装置
CN105871958B (zh) * 2015-01-21 2021-05-18 中兴通讯股份有限公司 集中管理账户信息的方法和终端
CN105989485B (zh) * 2015-02-16 2020-06-05 阿里巴巴集团控股有限公司 一种业务管理方法和装置
CN109787967B (zh) * 2015-12-22 2021-09-24 北京奇虎科技有限公司 一种借用他人账户实现登录的方法及系统
CN105975845B (zh) * 2016-07-04 2020-03-27 深圳市游云龙科技有限公司 一种机构的登录方法及登录装置
CN107979569B (zh) * 2016-10-24 2021-04-27 中国移动通信有限公司研究院 一种互联网应用的注册信息管理装置、方法及系统
CN107370730B (zh) 2017-07-14 2020-06-02 创新先进技术有限公司 一种登录信息处理方法及设备
CN107277066A (zh) * 2017-08-11 2017-10-20 中国银行股份有限公司 账户管理方法、便携式电子设备以及账户管理系统
CN107483477B (zh) * 2017-09-08 2020-07-10 上海宝库信息技术有限公司 账户管理方法及账户管理系统
CN107508835B (zh) * 2017-09-25 2020-07-10 咪咕文化科技有限公司 一种账户的验证方法、装置及计算机可读存储介质
CN107832592B (zh) * 2017-10-30 2020-11-10 北京小米移动软件有限公司 权限管理方法、装置及存储介质
CN111614641A (zh) * 2020-05-11 2020-09-01 北京电信易通信息技术股份有限公司 一种云账号管理系统及运用方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100931326B1 (ko) * 2008-09-09 2009-12-11 주식회사 로그 아이디/패스워드 찾기 이력 및 로그인 이력 관리 시스템 및 그 방법
CN102073928A (zh) * 2010-12-30 2011-05-25 天津市国瑞数码安全系统有限公司 基于接口定义的资源账号同步管理方法
CN102111347A (zh) * 2011-02-28 2011-06-29 东南大学 融合通信系统中基于多协议即时消息的处理方法和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1627683A (zh) * 2003-12-09 2005-06-15 鸿富锦精密工业(深圳)有限公司 单一认证授权管理系统及方法
CN100397814C (zh) * 2004-07-13 2008-06-25 中国工商银行股份有限公司 一种基于网络的统一认证方法及系统
US7421352B2 (en) * 2006-04-10 2008-09-02 Square D Company Network-enabled electrical power equipment with integrated content management system
CN102222200B (zh) * 2011-06-24 2015-07-22 宇龙计算机通信科技(深圳)有限公司 一种应用程序登录方法及登录管理系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100931326B1 (ko) * 2008-09-09 2009-12-11 주식회사 로그 아이디/패스워드 찾기 이력 및 로그인 이력 관리 시스템 및 그 방법
CN102073928A (zh) * 2010-12-30 2011-05-25 天津市国瑞数码安全系统有限公司 基于接口定义的资源账号同步管理方法
CN102111347A (zh) * 2011-02-28 2011-06-29 东南大学 融合通信系统中基于多协议即时消息的处理方法和系统

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109543372A (zh) * 2018-10-26 2019-03-29 深圳壹账通智能科技有限公司 业务权限数据处理方法、装置、计算机设备及存储介质
CN111541546A (zh) * 2020-04-24 2020-08-14 前海乔希(深圳)教育科技有限公司 多平台登陆方法、装置、设备及可读介质
CN114553504A (zh) * 2022-01-29 2022-05-27 重庆华唐云树科技有限公司 一种第三方安全登录方法
CN114553504B (zh) * 2022-01-29 2024-03-08 重庆华唐云树科技有限公司 一种第三方安全登录方法
CN114640511A (zh) * 2022-03-04 2022-06-17 上海医栗医疗科技有限公司 应用接口监控平台
CN114640511B (zh) * 2022-03-04 2024-01-19 上海医栗医疗科技有限公司 应用接口监控平台

Also Published As

Publication number Publication date
CN102546770A (zh) 2012-07-04
CN102546770B (zh) 2015-05-27

Similar Documents

Publication Publication Date Title
WO2013097392A1 (zh) 一种统一管理账户的方法及第三方账户管理系统
JP6781296B2 (ja) クラウドサーバ、クラウドプリントシステム、クラウドプリンタ及びクラウドプリンタ共有方法
KR101488268B1 (ko) 푸시 메시지 서비스 방법 및 시스템
US9641513B2 (en) Methods and systems for controlling mobile terminal access to a third-party server
CN105592065B (zh) 一种基于手机短信的网站登录方法及其登录系统
US8892885B2 (en) System and method for delivering a challenge response in an authentication protocol
EP2307982B1 (en) Method and service integration platform system for providing internet services
CN105306733A (zh) 基于手机app的第三方登录绑定手机号方法
WO2017074822A1 (en) Resolving authenticating issues with a second device
CN102324004A (zh) 一种网页表单输入信息验证方法及装置
WO2013143343A1 (zh) 账号登录方法、装置和系统以及网络服务器
US9178874B2 (en) Method, device and system for logging in through a browser application at a client terminal
TW201203140A (en) Online service providing system, method, server and mobile device thereof, and computer program product
WO2019174354A1 (zh) 认证方法及装置
JP2014215620A (ja) 認証システムおよび認証方法
WO2009009968A1 (fr) Procédé, dispositif et système pour acquérir des informations d'ouverture de session
WO2020073538A1 (zh) 一种消息发送方法、装置及系统
WO2017092385A1 (zh) 一种 portal 认证方法、 portal 服务器及终端
WO2016074397A1 (zh) 一种终端设备的业务开通方法及装置
CN104348613A (zh) 用户校验方法、装置及系统
CN101594240B (zh) 一种基于网络的软件登录方法及其系统
JP5456842B2 (ja) ユーザ確認装置、方法及びユーザ認証システム
CN104301285B (zh) 用于web系统的登录方法
TWI527419B (zh) Method and System of Integrating Backend Service Authentication with Proxy Servo
CN104734934A (zh) 一种关注公众账号的方法、装置和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12861990

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12861990

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 12861990

Country of ref document: EP

Kind code of ref document: A1