CN110704501B - User account correlation method and device - Google Patents
User account correlation method and device Download PDFInfo
- Publication number
- CN110704501B CN110704501B CN201910862456.1A CN201910862456A CN110704501B CN 110704501 B CN110704501 B CN 110704501B CN 201910862456 A CN201910862456 A CN 201910862456A CN 110704501 B CN110704501 B CN 110704501B
- Authority
- CN
- China
- Prior art keywords
- user registration
- service system
- user
- account information
- center
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2462—Approximate or statistical queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Probability & Statistics with Applications (AREA)
- Tourism & Hospitality (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Mathematical Physics (AREA)
- Fuzzy Systems (AREA)
- Health & Medical Sciences (AREA)
- Economics (AREA)
- General Health & Medical Sciences (AREA)
- Human Resources & Organizations (AREA)
- Marketing (AREA)
- Primary Health Care (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a user account correlation method and device. The method comprises the steps of judging the type of a service system according to a data statistics request initiated by the service system, wherein the data statistics request comprises user registration account information of the service system; inquiring user registration account information of the service system in a user registration center according to the type of the service system, wherein the user registration center is a center for storing the user registration account information; and determining whether a user account association request needs to be sent to the user side according to the query result. The method and the device solve the technical problem that data association cannot be carried out between different accounts of the same user in the related technology. By the method and the device, the purpose of associating different account numbers of the same user is achieved, and the technical effect of facilitating statistics of data of different service systems is achieved.
Description
Technical Field
The application relates to the field of data processing, in particular to a user account association method and device.
Background
With the rapid development of information technology, most information technology companies need to use various systems, such as office automation systems (OA systems), operation and maintenance systems, work order systems, demand management systems, distribution systems, and mailbox systems, to complete various tasks within the companies and to store various data of the companies in a statistical manner. Some systems may be developed by companies, some may use an external open source framework, or perform statistics on the storage of data related to the company through the services of the external company.
For a system independently developed in a company, a unified user center can be used for realizing related functions of user registration, login verification and the like of each subsystem. However, for a system built by an external open source framework or a service of an external company used by the system, usually, because the system has corresponding user registration and login modules, when a user registers, because the limitation of the system on the related information such as a user name and a mailbox is different from the limitation of a unified user center inside the company, an account registered by the user may be inconsistent with an account of the unified user center inside the company, and at this time, when data in a plurality of systems is required to be associated, the data cannot be associated.
Aiming at the problem that data association can not be carried out between different accounts of the same user in the related technology, an effective solution is not provided at present.
Disclosure of Invention
The application mainly aims to provide a user account association method and device so as to solve the problem that data association cannot be performed between different accounts of the same user in the related technology.
In order to achieve the above object, according to one aspect of the present application, a user account association method is provided.
The user account association method comprises the following steps: judging the type of a service system according to a data statistics request initiated by the service system, wherein the data statistics request comprises user registration account information of the service system; inquiring user registration account information of the service system in a user registration center according to the type of the service system, wherein the user registration center is a center for storing the user registration account information; and determining whether a user account association request needs to be sent to a user side according to the query result, wherein the user account association request is a request for associating the user registration account information of the service system with the user registration account information of the user registration center.
Further, the determining the type of the service system according to the data statistics request initiated by the service system includes: if the type of the service system is a first preset type, calling user registration account information of the user registration center corresponding to the user registration account information of the service system; acquiring data information corresponding to the called user registration account information of the user registration center in a first preset database; and sending the data information to the service system for statistics according to the data statistics request of the service system.
Further, the determining the type of the service system according to the data statistics request initiated by the service system includes: if the type of the service system is a second preset type, inquiring whether user registration account information of the service system exists in the user registration center; if the user registration account information of the service system exists, calling the user registration account information of the user registration center corresponding to the user registration account information of the service system; acquiring data information corresponding to the called user registration account information of the user registration center from a second preset database; and sending the data information to the service system for statistics according to the data statistics request of the service system.
Further, if the type of the service system is a second preset type, querying whether the user registration account information of the service system exists in the user registration center includes: if the user registration account information of the service system does not exist in the user registration center, determining whether a user registration account information association table of the service system and the user registration center exists in the user registration center; and judging whether a user account association request needs to be sent to the user side or not according to the determination result.
Further, the determining the type of the service system according to the data statistics request initiated by the service system includes: if the type of the service system is a third preset type, inquiring whether registration information of the service system exists in the user registration center; if the service system does not exist, performing similarity association on the user registration account information of the service system and the registration account information in the user registration center according to a preset rule; sending the similarity correlation result to a user side for confirmation; and judging whether a user account association request needs to be sent to the user side or not according to the confirmation result.
Further, if the type of the service system is a third preset type, after querying whether registration information of the service system exists in the user registration center, the method includes: if the registration information of the service system exists in the user registration center, determining whether a user registration account information association table of the service system and the user registration center exists in the user registration center; if the user registration account information does not exist, comparing the user registration account information of the service system with the user registration account information of a user registration center to obtain the user registration account information of the service system associated with the user to be used; sending the user registration account information of the service system to be associated with the user to the user side for association; and storing the association relationship between the user registration account information of the service system and the user registration account information of the user registration center according to the association result.
In order to achieve the above object, according to another aspect of the present application, there is provided a user account associating apparatus.
The user account association device comprises: the first judging module is used for judging the type of the service system according to a data statistics request initiated by the service system, wherein the data statistics request comprises user registration account information of the service system; the first query module is used for querying the user registration account information of the service system in a user registration center according to the type of the service system, wherein the user registration center is a center for storing the user registration account information; and the determining module is used for determining whether a user account association request needs to be sent to the user side according to the query result, wherein the user account association request is a request for associating the user registration account information of the service system with the user registration account information of the user registration center.
Further, the apparatus further comprises: the first calling module is used for calling the user registration account information of the user registration center corresponding to the user registration account information of the service system if the type of the service system is a first preset type; the first acquisition module is used for acquiring data information corresponding to the called user registration account information of the user registration center from a first preset database; and the first sending module is used for sending the data information to the service system for statistics according to the data statistics request of the service system.
Further, the apparatus further comprises: the second query module is used for querying whether the user registration account information of the service system exists in the user registration center if the type of the service system is a second preset type; the second calling module is used for calling the user registration account information of the user registration center corresponding to the user registration account information of the service system if the user registration account information of the service system exists; the second acquisition module is used for acquiring data information corresponding to the called user registration account information of the user registration center from a second preset database; and the second sending module is used for sending the data information to the service system for statistics according to the data statistics request of the service system.
Further, the apparatus further comprises: a third query module, configured to query whether registration information of the service system exists in the user registration center if the type of the service system is a third preset type; the association module is used for performing similarity association on the user registration account information of the service system and the registration account information in the user registration center according to a preset rule if the user registration account information does not exist; a third sending module, configured to send the similarity association result to a user side for confirmation; and the second judgment module is used for judging whether a user account association request needs to be sent to the user side according to the confirmation result.
In the embodiment of the application, the type of the service system is judged according to a data statistics request initiated by the service system, and the user registration account information of the service system is inquired in a user registration center according to the type of the service system; whether a user account association request needs to be sent to a user side is determined according to the query result, and the purpose of associating different accounts of the same user is achieved, so that the technical effect of conveniently counting data of different service systems is achieved, and the technical problem that data association cannot be performed between different accounts of the same user in the related technology is solved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this application, serve to provide a further understanding of the application and to enable other features, objects, and advantages of the application to be more apparent. The drawings and their description illustrate the embodiments of the invention and do not limit it. In the drawings:
fig. 1 is a flowchart illustrating a user account association method according to a first embodiment of the present application;
fig. 2 is a flowchart illustrating a user account association method according to a second embodiment of the present application;
fig. 3 is a flowchart illustrating a user account association method according to a third embodiment of the present application;
fig. 4 is a flowchart illustrating a user account association method according to a fourth embodiment of the present application;
fig. 5 is a flowchart illustrating a user account association method according to a fifth embodiment of the present application;
fig. 6 is a flowchart illustrating a user account association method according to a sixth embodiment of the present application;
fig. 7 is a schematic structural diagram of a user account association apparatus according to a first embodiment of the present application;
fig. 8 is a schematic structural diagram of a user account association apparatus according to a second embodiment of the present application;
fig. 9 is a schematic structural diagram of a user account association apparatus according to a third embodiment of the present application; and
fig. 10 is a schematic structural diagram of a user account association apparatus according to a fourth embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the accompanying drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances in order to facilitate the description of the embodiments of the application herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
According to an embodiment of the present invention, a method for associating user accounts is provided, as shown in fig. 1, the method includes the following steps S101 to S103:
step S101, judging the type of the service system according to a data statistics request initiated by the service system, wherein the data statistics request comprises user registration account information of the service system.
In specific implementation, an application scenario of the embodiment of the present application may be to count data of various systems based on registered account information of a user in various systems such as an oa system, an operation and maintenance system, a work order system, a demand management system, a distribution system, and a mailbox system of a company. However, the registered account information of the users in different types of systems is not completely consistent, so that the difficulty of data statistics is increased. For example, an internal system of a company, an open source building system and an external service system are different in naming rules and restriction types of the different systems, so that a set of accounts cannot be uniformly used for registration, and the accounts registered by a user in the systems are different. In a plurality of systems, because account numbers are different, association cannot be effectively performed, and therefore, when mutual statistical summarization is performed on data in the plurality of systems, statistics on data corresponding relations cannot be performed.
Therefore, in order to solve the above problems, in the user account association method according to the embodiment of the present application, first, a data statistics request sent by different business systems is received, and a specific type of the business system is determined according to the data statistics request, for example, the specific type may be a system developed by a company itself, or an external open-source framework system built by the company, or a service system provided by an external company, where different types of business systems correspond to different user account association rules. Specifically, the user registration account information in the service system sending the request is further identified according to the data statistics request, and is used as a basis for performing data association based on the user registration account.
Step S102, inquiring user registration account information of the service system in a user registration center according to the type of the service system, wherein the user registration center is a center for storing the user registration account information.
In specific implementation, a unified user registration center is constructed in the embodiment of the application, the user registration center provides services of various user operations such as user registration, login and authentication in a company, and mapping tables corresponding to user accounts of other systems are stored. Meanwhile, the user is supported to manually set the account number of the related service system, and the user registration center confirms whether the submitted data exists. And after the specific type of the service system is judged, searching and inquiring in the user registration center according to the type of the service system so as to determine whether the user registration center contains user registration information in the service system.
Step S103, determining whether a user account association request is required to be sent to the user side according to the query result, wherein the user account association request is a request for associating the user registration account information of the service system with the user registration account information of the user registration center.
In specific implementation, if the user registration account information of the service system is inquired in the user registration center, the account information of the user to be counted by the service system already exists in the user registration center, and at this time, the user registration account information in the user registration center is directly called without sending an account association request to a user side; if the user registration account information of the service system is not inquired in the user registration center, a user account association request needs to be sent to the user side, the user self associates the user registration account information of the service system with the user registration account information of the user registration center, and whether the user account association request is sent to the user side is determined according to the inquiry result.
As a preferred implementation of the embodiment of the present application, as shown in fig. 2, after determining the type of the service system according to the data statistics request initiated by the service system, the following steps S201 to S203 are included:
step S201, if the type of the service system is a first preset type, calling user registration account information of the user registration center corresponding to the user registration account information of the service system.
In specific implementation, if the type of the service system is judged to be a service system developed by the user in a company, the user registration account information of the service system is stored in the user registration center, and the corresponding user registration account information is directly pulled in the user registration center.
Step S202, acquiring data information corresponding to the called user registration account information of the user registration center in a first preset database.
In specific implementation, after the user registration account information is acquired in the user registration center, the related data is pulled according to the data system corresponding to the user registration account information.
Step S203, sending the data information to the service system for statistics according to the data statistics request of the service system.
In specific implementation, data is called in the database according to specific information in a data statistics request sent by a service system, such as a statistical data type, and the data is sent to the service system for subsequent statistics.
As a preferred implementation of the embodiment of the present application, as shown in fig. 3, after determining the type of the service system according to the data statistics request initiated by the service system, the following steps S301 to S304 are included:
step S301, if the type of the service system is a second preset type, querying whether user registration account information of the service system exists in the user registration center.
In specific implementation, if it is determined that the service system is an external open source framework system built in a company, user registration account information generated in the external open source framework system is not necessarily stored in a user registration center, and therefore, it is necessary to further determine whether the user registration account information of the service system exists in the user registration center.
Step S302, if the user registration account information of the service system exists, the user registration account information of the user registration center corresponding to the user registration account information of the service system is called.
In specific implementation, if the user registration account information of the service system can be queried in the user registration center, the corresponding user registration account information is directly pulled in the user registration center in the same way as the processing mode of the service system which is self-developed in a company.
Step S303, acquiring data information corresponding to the called user registration account information of the user registration center from a second preset database.
In specific implementation, after the user registration account information is acquired in the user registration center, the related data is pulled according to the data system corresponding to the user registration account information in the same way as the processing mode of a business system which is automatically developed in a company.
Step S304, sending the data information to the service system for statistics according to the data statistics request of the service system.
In specific implementation, as in a processing mode of a business system developed by a company, data is called in the database according to specific information in a data statistics request sent by the business system, such as a statistical data type, and the data is sent to the business system for subsequent statistics.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 4, if the type of the service system is a second preset type, after querying whether user registration account information of the service system exists in the user registration center, the following steps S401 to S402 are included:
step S401, if it is queried in the user registration center that the user registration account information of the service system does not exist, determining whether a user registration account information association table between the service system and the user registration center exists in the user registration center.
In specific implementation, if it is determined that the service system is an external open-source framework system built in a company and the user registration account information of the service system cannot be queried in the user registration center, it needs to further determine whether a relationship mapping table between the user registration account information of the service system and the user registration account information of the user registration center exists in the user registration center.
Step S402, judging whether a user account association request needs to be sent to the user side according to the determination result.
In specific implementation, if a corresponding relation mapping table exists in the user registration center, data of the service system which needs to be counted currently is continuously read, then user registration account information corresponding to the data of the current service system is matched with the relation mapping table, the user registration account information matched with the user registration account information of the current service system is called, and then the data pulled by the current service system is added into a data set corresponding to the user registration account information in the user registration center matched with the user registration account information.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 5, after determining the type of the service system according to the data statistics request initiated by the service system, the following steps S501 to S504 are included:
step S501, if the type of the service system is a third preset type, querying whether registration information of the service system exists in the user registration center.
In specific implementation, if it is determined that the type of the service system is a service system provided by an external company, it is first determined whether the external service system is registered in the user registration center.
Step S502, if not, the user registration account information of the service system is subjected to similarity association with the registration account information in the user registration center according to a preset rule.
In specific implementation, if the registration information of the external service system does not exist in the user registration center, the similarity association of the user names is firstly required.
Step S503, sending the similarity association result to the user side for confirmation.
When the method is specifically implemented, the result of the similarity association of the user name is sent to the user in the user registration center, and the user confirms whether the result of the similarity association is correct or not.
Step S504, whether a user account association request needs to be sent to the user side is judged according to the confirmation result.
In specific implementation, if the user confirms that the result of the similarity association is correct, a user account association request does not need to be sent to the user, and subsequent data reading and statistics are directly carried out according to the result of the similarity association; if the user confirms that the result of the similarity association is incorrect, a user account association request needs to be further sent to the user, the user manually inputs a corresponding account, then whether the account exists is inquired in a user registered account center, if so, the association relation is added into a user registered account information association table, and if not, the user is prompted to re-input.
As a preferred implementation manner of the embodiment of the present application, as shown in fig. 6, if the type of the service system is a third preset type, after querying whether registration information of the service system exists in the user registration center, the following steps S601 to S604 are included:
step S601, if the registration information of the service system is found in the user registration center, determining whether a user registration account information association table between the service system and the user registration center exists in the user registration center.
In a specific implementation, if the registration information of the external service system is queried in the user registration center, it needs to further determine whether a relationship mapping table between the user registration account information of the external service system and the user registration account information of the user registration center exists in the user registration center.
Step S602, if not, comparing the user registration account information of the service system with the user registration account information of the user registration center to obtain the user registration account information of the service system associated with the user to be used.
In specific implementation, if the account exists in the two corresponding systems and data are generated, but the relation mapping table cannot be queried in the user registration center, the user registration account information existing in the user registration center in the external service system is filtered to obtain the remaining user registration account information, namely the registration account information to be associated with the user.
Step S603, sending the user registration account information of the service system to be associated with the user to the user side for association.
In specific implementation, the information of the rest accounts of the internally-built open source frame system or the external service system is sent to the enterprise IM or mailbox corresponding to the rest accounts, and the user selects the account corresponding to the open source frame system or the external service system in the user registration center, namely, the association relationship between the rest accounts and the user registration account in the user registration center is built.
Step S604, storing the association relationship between the user registration account information of the service system and the user registration account information of the user registration center according to the association result.
In specific implementation, the association relationship between the remaining account and the user registration account in the user registration center is stored in a relationship mapping table of the open-source framework system or the external service system for the next query.
From the above description, it can be seen that the present invention achieves the following technical effects: the method comprises the steps that the type of a service system is judged according to a data statistics request initiated by the service system, and user registration account information of the service system is inquired in a user registration center according to the type of the service system; whether a user account association request needs to be sent to a user side is determined according to the query result, the purpose of associating different accounts of the same user is achieved, and therefore the technical effect of facilitating statistics of data of different service systems is achieved.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowcharts, in some cases, the steps illustrated or described may be performed in an order different than presented herein.
According to an embodiment of the present invention, there is also provided an apparatus for implementing the user account association method, where as shown in fig. 7, the apparatus includes: the device comprises a first judgment module 1, a first query module 2 and a determination module 3.
The first determining module 1 in the embodiment of the present application is configured to determine a type of a service system according to a data statistics request initiated by the service system, where the data statistics request includes information of a user registration account of the service system.
The user account association method of the embodiment of the application firstly receives data statistics requests sent by different business systems, and judges the specific type of the business system through the data statistics requests, for example, the specific type can be a system developed by a company, or an external open-source framework system built by the company, or a service system provided by an external company, and different types of business systems correspond to different user account association rules. Specifically, the first judgment module is further used for identifying the user registration account information in the service system sending the request according to the data statistics request, and the information is used as a basis for performing data association based on the user registration account.
The first query module 2 in the embodiment of the application is configured to query, according to the type of the service system, user registration account information of the service system in a user registration center, where the user registration center is a center for storing the user registration account information.
In specific implementation, a unified user registration center is constructed in the embodiment of the application, the user registration center provides services operated by various users such as user registration, login and authentication in a company, and mapping tables corresponding to user accounts of other systems are stored. Meanwhile, the user is supported to manually set the account number of the related service system, and the user registration center confirms whether the submitted data exists. And after the specific type of the service system is judged, searching and inquiring in the user registration center through the first inquiring module according to the type of the service system so as to determine whether the user registration center contains user registration information in the service system.
The determining module 3 in this embodiment is configured to determine whether a user account association request needs to be sent to a user side according to a query result, where the user account association request is a request for associating user registration account information of the service system with user registration account information of the user registration center.
In specific implementation, if the user registration account information of the service system is inquired in the user registration center, the account information of the user to be counted by the service system already exists in the user registration center, and at this time, an account association request is not required to be sent to a user side, and the user registration account information in the user registration center is directly called; if the user registration account information of the service system is not inquired in the user registration center, a user account association request needs to be sent to the user side, the user self associates the user registration account information of the service system with the user registration account information of the user registration center, and whether the user account association request is sent to the user side is determined through a determination module according to the inquiry result.
As a preferred implementation of the embodiment of the present application, as shown in fig. 8, the apparatus further includes: a first retrieving module 4, a first obtaining module 5 and a first sending module 6.
The first retrieving module 4 in the embodiment of the application is configured to, if the type of the service system is a first preset type, retrieve user registration account information of the user registration center corresponding to the user registration account information of the service system.
In specific implementation, if the type of the service system is judged to be a service system developed by the user in a company, the user registration account information of the service system is stored in the user registration center, and the corresponding user registration account information is directly pulled in the user registration center.
The first obtaining module 5 of the embodiment of the application is configured to obtain, in a first preset database, data information corresponding to the called user registration account information of the user registration center.
In specific implementation, after the user registration account information is acquired in the user registration center, the first acquisition module pulls the related data according to the data system corresponding to the user registration account information.
The first sending module 6 in the embodiment of the present application is configured to send the data information to the service system for statistics according to the data statistics request of the service system.
In specific implementation, data is called in the database according to specific information in a data statistics request sent by a service system, such as a statistical data type, and the data is sent to the service system through a first sending module for subsequent statistics.
As a preferred implementation of the embodiment of the present application, as shown in fig. 9, the apparatus further includes: a second query module 7, a second retrieving module 8, a second obtaining module 9 and a second sending module 10.
The second query module 7 in this embodiment is configured to query whether the user registration account information of the service system exists in the user registration center if the type of the service system is a second preset type.
In specific implementation, if it is determined that the service system is an external open source framework system built in a company, user registration account information generated in the external open source framework system is not necessarily stored in a user registration center, and therefore it is further required to determine whether the user registration account information of the service system exists in the user registration center through a second query module.
The second retrieving module 8 in the embodiment of the present application is configured to, if the user registration account information of the service system exists, retrieve the user registration account information of the user registration center corresponding to the user registration account information of the service system.
In specific implementation, if the user registration account information of the service system can be queried in the user registration center, the corresponding user registration account information is directly pulled in the user registration center through the second calling module in the same way as the processing mode of the service system which is self-developed in a company.
The second obtaining module 9 in the embodiment of the application is configured to obtain, in a second preset database, data information corresponding to the called user registration account information of the user registration center.
In specific implementation, after the user registration account information is acquired in the user registration center, the second acquisition module pulls the related data according to the data system corresponding to the user registration account information, in the same way as the processing mode of a business system which is automatically developed in a company.
The second sending module 10 in the embodiment of the present application is configured to send the data information to the service system for statistics according to the data statistics request of the service system.
In specific implementation, as in a processing mode of a business system developed by a company, data is called in the database according to specific information, such as statistical data types, in a data statistical request sent by the business system, and the data is sent to the business system through the second sending module for subsequent statistics.
As a preferred implementation of the embodiment of the present application, as shown in fig. 10, the apparatus further includes: a third query module 11, an association module 12, a third sending module 13 and a second judgment module 14.
A third query module 11, configured to query, if the type of the service system is a third preset type, whether registration information of the service system exists in the user registration center.
In specific implementation, if the type of the service system is determined to be a service system provided by an external company, it is first determined whether the external service system is registered in the user registration center through the third query module.
And the association module 12 is configured to, if the user registration account information does not exist, perform similarity association on the user registration account information of the service system and the registration account information in the user registration center according to a preset rule.
In specific implementation, if the registration information of the external service system does not exist in the user registration center, the similarity association of the user names needs to be performed through the association module.
A third sending module 13, configured to send the similarity association result to the user side for confirmation.
When the method is specifically implemented, the result of the similarity association of the user name is sent to the user in the user registration center through the third sending module, and the user confirms whether the result of the similarity association is correct or not.
The second determining module 14 is configured to determine whether a user account association request needs to be sent to the user side according to the confirmation result.
In specific implementation, if the user confirms that the result of the similarity association is correct, a user account association request does not need to be sent to the user, and subsequent data reading and statistics are directly carried out according to the result of the similarity association; if the user confirms that the result of the similarity association is incorrect, a user account association request needs to be further sent to the user, the user manually inputs a corresponding account, then whether the account exists is inquired in a user registration account center, if yes, the association relation is added into a user registration account information association table, if not, the user is prompted to input again, namely, the second judgment module judges whether the user account association request needs to be sent to the user side according to the confirmation result.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and they may alternatively be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or fabricated separately as individual integrated circuit modules, or fabricated as a single integrated circuit module from multiple modules or steps. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (8)
1. A user account association method is characterized by comprising the following steps:
judging the type of a service system according to a data statistics request initiated by the service system, wherein the data statistics request comprises user registration account information of the service system;
if the type of the service system is a first preset type, calling user registration account information of a user registration center corresponding to the user registration account information of the service system, wherein the user registration center is a center for storing the user registration account information;
acquiring data information corresponding to the called user registration account information of the user registration center in a first preset database;
sending the data information to the service system for statistics according to the data statistics request of the service system;
if the type of the service system is a second preset type or a third preset type, inquiring user registration account information of the service system in a user registration center according to the type of the service system;
and determining whether a user account association request needs to be sent to a user side according to the query result, wherein the user account association request is a request for associating the user registration account information of the service system with the user registration account information of the user registration center.
2. The method according to claim 1, wherein the determining the type of the service system according to the data statistics request initiated by the service system comprises:
if the type of the service system is a second preset type, inquiring whether user registration account information of the service system exists in the user registration center;
if the user registration account information of the service system exists, calling the user registration account information of the user registration center corresponding to the user registration account information of the service system;
acquiring data information corresponding to the called user registration account information of the user registration center from a second preset database;
and sending the data information to the service system for statistics according to the data statistics request of the service system.
3. The method of claim 2, wherein, if the type of the service system is a second preset type, after querying whether the user registration account information of the service system exists in the user registration center, the method includes:
if the user registration account information of the service system does not exist in the user registration center, determining whether a user registration account information association table of the service system and the user registration center exists in the user registration center;
and judging whether a user account association request needs to be sent to the user side or not according to the determination result.
4. The method according to claim 1, wherein the determining the type of the service system according to the data statistics request initiated by the service system comprises:
if the type of the service system is a third preset type, inquiring whether registration information of the service system exists in the user registration center;
if the user registration account information does not exist in the service system, performing similarity association on the user registration account information of the service system and the registration account information in the user registration center according to a preset rule;
sending the similarity correlation result to a user side for confirmation;
and judging whether a user account association request needs to be sent to the user side or not according to the confirmation result.
5. The method according to claim 4, wherein, if the type of the service system is a third preset type, after querying whether registration information of the service system exists in the user registration center, the method includes:
if the registration information of the service system exists in the user registration center, determining whether a user registration account information association table of the service system and the user registration center exists in the user registration center;
if the user registration account information does not exist, comparing the user registration account information of the service system with the user registration account information of a user registration center to obtain the user registration account information of the service system associated with the user to be used;
sending the user registration account information of the service system to be associated with the user to the user side for association;
and storing the association relationship between the user registration account information of the service system and the user registration account information of the user registration center according to the association result.
6. A user account association apparatus, comprising:
the first judging module is used for judging the type of the service system according to a data statistics request initiated by the service system, wherein the data statistics request comprises user registration account information of the service system;
the first calling module is used for calling user registration account information of a user registration center corresponding to the user registration account information of the service system if the type of the service system is a first preset type, wherein the user registration center is a center for storing the user registration account information;
the first acquisition module is used for acquiring data information corresponding to the called user registration account information of the user registration center from a first preset database;
the first sending module is used for sending the data information to the service system for statistics according to the data statistics request of the service system;
the first query module is used for querying user registration account information of the service system in a user registration center according to the type of the service system if the type of the service system is a second preset type or a third preset type;
and the determining module is used for determining whether a user account association request needs to be sent to the user side according to the query result, wherein the user account association request is a request for associating the user registration account information of the service system with the user registration account information of the user registration center.
7. The user account association apparatus according to claim 6, further comprising:
the second query module is used for querying whether the user registration account information of the service system exists in the user registration center if the type of the service system is a second preset type;
the second calling module is used for calling the user registration account information of the user registration center corresponding to the user registration account information of the service system if the user registration account information of the service system exists;
the second acquisition module is used for acquiring data information corresponding to the called user registration account information of the user registration center from a second preset database;
and the second sending module is used for sending the data information to the service system for statistics according to the data statistics request of the service system.
8. The apparatus for associating user accounts according to claim 6, further comprising:
a third query module, configured to query whether registration information of the service system exists in the user registration center if the type of the service system is a third preset type;
the association module is used for performing similarity association on the user registration account information of the service system and the registration account information in the user registration center according to a preset rule if the user registration account information does not exist;
a third sending module, configured to send the similarity association result to a user side for confirmation;
and the second judgment module is used for judging whether a user account association request needs to be sent to the user side or not according to the confirmation result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910862456.1A CN110704501B (en) | 2019-09-11 | 2019-09-11 | User account correlation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910862456.1A CN110704501B (en) | 2019-09-11 | 2019-09-11 | User account correlation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110704501A CN110704501A (en) | 2020-01-17 |
| CN110704501B true CN110704501B (en) | 2022-07-12 |
Family
ID=69194779
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910862456.1A Active CN110704501B (en) | 2019-09-11 | 2019-09-11 | User account correlation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110704501B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111475683A (en) * | 2020-04-07 | 2020-07-31 | 一节好课(北京)科技有限公司 | User binding method and device for extracurricular training, learning management method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104700277A (en) * | 2013-12-05 | 2015-06-10 | 华为技术有限公司 | Electronic accounting method and device and terminal equipment |
| CN104954322A (en) * | 2014-03-25 | 2015-09-30 | 腾讯科技（深圳）有限公司 | Account binding method, device and system |
| CN104978383A (en) * | 2015-02-12 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Data interworking method and data interworking equipment |
| CN109597640A (en) * | 2018-07-27 | 2019-04-09 | 北京字节跳动网络技术有限公司 | A kind of account management method of application program, device, equipment and medium |
-
2019
- 2019-09-11 CN CN201910862456.1A patent/CN110704501B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104700277A (en) * | 2013-12-05 | 2015-06-10 | 华为技术有限公司 | Electronic accounting method and device and terminal equipment |
| CN104954322A (en) * | 2014-03-25 | 2015-09-30 | 腾讯科技（深圳）有限公司 | Account binding method, device and system |
| CN104978383A (en) * | 2015-02-12 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Data interworking method and data interworking equipment |
| CN109597640A (en) * | 2018-07-27 | 2019-04-09 | 北京字节跳动网络技术有限公司 | A kind of account management method of application program, device, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110704501A (en) | 2020-01-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109597853B (en) | Business scene element serial number generation method, device, medium and computer equipment | |
| WO2019051946A1 (en) | Node task data display method and apparatus, storage medium and computer equipment | |
| CN106951773B (en) | User role distribution checking method and system | |
| US8620946B2 (en) | Storage and searching of temporal entity information | |
| US20180077157A1 (en) | Method and system for identifying user information in social network | |
| US20160300310A1 (en) | System and method for efficient processing of tax preparation services by centralized and distributed tax resources | |
| CN113254969B (en) | Business data processing method and device, electronic equipment and storage medium | |
| US20060161550A1 (en) | System and method for distributing customer relationship management information | |
| CN110781183A (en) | Method and device for processing incremental data in Hive database and computer equipment | |
| CN107659450A (en) | Distribution method, distributor and the storage medium of big data cluster resource | |
| CN107633386B (en) | Method, system, equipment and storage medium for managing network terminal information | |
| US11151088B2 (en) | Systems and methods for verifying performance of a modification request in a database system | |
| CN110704501B (en) | User account correlation method and device | |
| CN109583615B (en) | Conference room booking method, conference room booking system, conference room booking server and computer readable storage medium | |
| US20130066828A1 (en) | Scale-out system to acquire event data | |
| CN109672721B (en) | Media file pushing method and device, server and computer readable storage medium | |
| WO2019223598A1 (en) | Method and device for fusing data table | |
| KR101614890B1 (en) | Method of creating multi tenancy history, server performing the same and storage media storing the same | |
| JP2015052811A (en) | Information management system, information management program, information management method, information management device, and recording medium | |
| CN109190946A (en) | Business revenue data determination method, device, electronic equipment and storage medium | |
| CN111582831B (en) | Government affair mailbox management method, system and storage medium | |
| CN110851512B (en) | Data configuration method and device for open source framework | |
| AU2017371238A1 (en) | Method of inputting document information, device, server, and storage medium | |
| CN113901046A (en) | Virtual dimension table construction method and device | |
| CN112019364B (en) | Information management method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 200125, Room 325, 3rd Floor, Unit 2, No. 231, Shibocun Road, China (Shanghai) Pilot Free Trade Zone, Pudong New Area, Shanghai Patentee after: Wheel interconnection technology (Shanghai) Co.,Ltd. Address before: 200125 Room 501, 5 / F, building 3, 3601 Dongfang Road, Pudong New Area, Shanghai Patentee before: SHANGHAI YIDIAN SPACE NETWORK Co.,Ltd. |
|
| CP03 | Change of name, title or address |