Unified user management method, device and equipment for data transaction system

Abstract

The invention discloses a unified user management method, device and equipment oriented to a data transaction system, and relates to the technical field of data information management.The method comprises the steps that registration and login of various source accounts on the data transaction system are carried out, and login information is stored in Redis after login succeeds; based on an externally exposed account information synchronization API interface of the data transaction system, registration and login of a third-party system account in the data transaction system are realized, and login information is stored; based on a cluster mode, deployment of login information, data transaction system business data, account registration login and account information synchronization is carried out, and account login access traffic balance is realized through a load balancing strategy. Unification and sharing of user data can be realized, the problem of respective management of Internet users and enterprise users in a traditional mode is avoided, and the management efficiency is improved.

Description

Technical Field

[0001] The present application relates to the technical field of data information management, and in particular to a unified user management method, device and equipment for a data transaction system. Background Art

[0002] With the rapid development of information technology, the number of Internet users and enterprise users has exploded. The traditional user management method usually manages Internet users and enterprise users in different systems. This method not only leads to low management efficiency, but also increases maintenance costs, and it is difficult to unify and share user data.

[0003] For example, for a data trading system, it must simultaneously meet the registration and login requirements of Internet users, the registration and login requirements of mini programs, and the registration and login requirements of the backend management system. At the same time, it may also need to be interconnected with a third-party business system, so it is necessary to manage all different types of users in a unified manner. Therefore, how to achieve unified management of Internet users, corporate users, and other users has become an urgent problem to be solved. Summary of the invention

[0004] The present application provides a unified user management method, device and equipment for a data transaction system, which can achieve the unification and sharing of user data, avoid the problem of separate management of Internet users and enterprise users in the traditional way, and improve management efficiency.

[0005] In a first aspect, an embodiment of the present application provides a unified user management method for a data transaction system, the unified user management method for a data transaction system comprising:

[0006] Register and log in accounts from various sources on the data trading system, and save the login information to Redis after successful login;

[0007] Based on the account information synchronization API interface exposed by the data trading system, the third-party system account is registered and logged in to the data trading system, and the login information is saved;

[0008] Login information, data transaction system business data, account registration and login, and account information synchronization are deployed in a cluster-based manner, and account login access traffic is balanced through load balancing strategies.

[0009] In combination with the first aspect, in one implementation, the registration and login of multiple source accounts on the data trading system specifically includes the registration and login of mini program accounts, the registration and login of buyer and seller accounts on the web page, and the registration and login of backend management accounts.

[0010] In conjunction with the first aspect, in one implementation, registering and logging into a mini program account specifically includes:

[0011] When opening the applet of the data trading system, obtain the mobile phone number bound to the user logged in to the application where the applet is located;

[0012] Log in to the Mini Program based on the obtained mobile phone number, and determine whether the obtained mobile phone number has been registered in the Mini Program during login:

[0013] If yes, the user will log in to the Mini Program based on the obtained mobile phone number, and save the login credentials to Redis after the login is successful.

[0014] If not, register an account based on the obtained mobile phone number, bind the account of the user logging in to the application where the mini program is located, perform the login operation, and save the login credentials to Redis after the login is successful.

[0015] In conjunction with the first aspect, in one implementation, registering and logging in to a buyer and seller account on a web page specifically includes:

[0016] Use the mobile phone verification code method or account password method to log in and verify whether the current user exists:

[0017] If yes, complete the login operation and save the login credentials to Redis after successful login;

[0018] If not, register the account using the account name and perform real-name authentication after successful registration, then log in using the account and password, and save the login credentials to Redis after successful login. Alternatively, obtain the verification code through the mobile phone number to register the account, then use the mobile phone verification code to log in, and save the login credentials to Redis after successful login.

[0019] In conjunction with the first aspect, in one implementation, registering and logging into a backend management account specifically includes:

[0020] The backend management system presets the system super administrator's account and password, and synchronizes the account and password through offline distribution;

[0021] Log in to the background management system based on the issued account and password, and save the login credentials to Redis after successful login.

[0022] In combination with the first aspect, in one implementation,

[0023] After the login credentials are saved to Redis: When you log in again, if the login credentials are valid, you can directly complete the login operation. If the login credentials are invalid, you need to log in again and save the login credentials after the re-login is successful.

[0024] After successfully logging in, if the account information is changed, the login credentials will become invalid.

[0025] In combination with the first aspect, in one implementation, the account information synchronization API interface exposed externally by the data transaction system is used to realize the registration and login of the third-party system account in the data transaction system, and the login information is saved, specifically including:

[0026] When a third-party system account needs to log in to the data trading system, the third-party system connects to the account information synchronization API interface exposed by the data trading system and jumps to the data trading system;

[0027] Determine whether the third-party system account already exists in the data transaction system:

[0028] If yes, log in to the data trading system directly through the third-party system account;

[0029] If not, synchronize the third-party system account to the data transaction system through the account information synchronization API interface, register the account and log in, and save the login credentials to Redis after successful login.

[0030] In combination with the first aspect, in one implementation, when a third-party system account successfully logs in to the data trading system and the login credentials are saved to Redis:

[0031] During the validity period of the login credentials, the third-party system can directly access the data transaction system. When the login credentials expire or the information of the third-party system account changes, the third-party system account must be logged in to the data transaction system again.

[0032] In a second aspect, an embodiment of the present application provides a unified user management device for a data transaction system, wherein the unified user management device for a data transaction system:

[0033] Data trading system, which supports registration and login of mini program accounts, web buyer and seller accounts, and backend management accounts;

[0034] A third-party system is used to synchronize account information with the data trading system, and to limit the registration and login of the third-party system account in the data trading system;

[0035] The user center is used to deploy login information, data transaction system business data, account registration and login, and account information synchronization based on a cluster approach, and to achieve balance of account login access traffic through load balancing strategies.

[0036] In a third aspect, an embodiment of the present application provides a unified user management device for a data trading system, wherein the unified user management device for a data trading system comprises a processor, a memory, and a unified user management program for a data trading system stored in the memory and executable by the processor, wherein when the unified user management program for a data trading system is executed by the processor, the steps of the unified user management method for a data trading system described above are implemented.

[0037] The beneficial effects brought by the technical solution provided in the embodiments of the present application include:

[0038] (1) It can unify and share user data, avoiding the problem of separate management of Internet users and corporate users in traditional methods, and improving management efficiency;

[0039] (2) It can easily communicate user information with third-party systems, has good scalability, and can be flexibly configured and expanded according to different business needs;

[0040] (3) Supports concurrent access and data processing by multiple users, and can meet the needs of large-scale users online at the same time;

[0041] (4) It provides a variety of user interaction methods and improves the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 This is a flowchart of a unified user management method for a data transaction system in this application;

[0043] Figure 2 This is a functional module diagram of a unified user management device for a data transaction system of the present application;

[0044] Figure 3 This is a schematic diagram of the hardware structure of a unified user management device for a data transaction system in this application. DETAILED DESCRIPTION

[0045] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0046] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0047] On the first aspect, the embodiments of the present application provide a unified user management method for a data transaction system, which is of great significance for improving management efficiency and reducing maintenance costs.

[0048] In one embodiment, referring to Figure 1 , Figure 1 This is a flowchart of a unified user management method for a data transaction system in this application. Figure 1 As shown, the unified user management method for the data transaction system includes:

[0049] S1: Register and log in multiple source accounts on the data trading system, and save the login information to Redis after successful login;

[0050] For the data trading system in this application, data trading is the key support for promoting the development of the digital economy. In the era of digital economy, data has become a new key production factor. The establishment and development of the data trading system is conducive to releasing data dividends and promoting the rapid growth of the digital economy. Through a series of services such as data trading, data asset management, data services and data technical support, an open, transparent and compliant market is provided for enterprises and individuals, so that the sale and exchange of data can be completed in a benign competition environment, thereby maximizing the value of data. For example, some companies can use the data trading system to reasonably use and realize the data generated by users within their control, especially in the fields of advertising, marketing, and Internet finance, where data is used very frequently. The data trading system not only solves the problem of data sharing and information islands, but also promotes the circulation and value realization of data, optimizes market strategies and product services, supports business decisions, and promotes the development of the digital economy. At the same time, it also strengthens data security and privacy protection, bringing more commercial value and social benefits.

[0051] In this application, Redis is an open source, in-memory data structure storage system that can be used as a database, cache, and message middleware. In this application, it is used as a cache database to store data such as account login authentication information.

[0052] In this application, registration and login of accounts from various sources are performed on the data trading system, specifically, registration and login of mini program accounts, registration and login of buyer and seller accounts on the web page, and registration and login of backend management accounts.

[0053] Furthermore, the registration and login of the Mini Program account specifically includes:

[0054] S101: when a mini program of the data trading system is opened, obtaining a mobile phone number bound to a user who logs in to the application where the mini program is located; the application where the mini program is located may be WeChat;

[0055] S102: Perform a mini program login operation based on the obtained mobile phone number, and determine whether the obtained mobile phone number has been registered in the mini program during login:

[0056] If yes, the user will log in to the Mini Program based on the obtained mobile phone number, and save the login credentials to Redis after the login is successful.

[0057] If not, register an account based on the obtained mobile phone number, bind the account of the user logging in to the application where the mini program is located, perform the login operation, and save the login credentials to Redis after the login is successful.

[0058] Specifically, when a user opens the mini-program client of the data trading system, the mobile phone number bound to the current WeChat user will be obtained, and the login operation will be performed through the mobile phone number. When logging in, it will be determined whether the mobile phone number has been registered. If it is an existing account, then you can log in; if the account does not exist, then register the account through the mobile phone number, and then log in after binding the corresponding WeChat account. After logging in, the login information will be saved in Redis, which is convenient for login validity verification when logging in for the second time. If the login credentials are valid, you can log in to the data trading system directly. If the login credentials are invalid, the login credential information will be saved after successfully logging in again. If the user information is changed after logging in, the login credentials will be invalid immediately and the data trading system will redirect to the login page.

[0059] Furthermore, the registration and login of the buyer and seller accounts on the web page specifically include:

[0060] Use the mobile phone verification code method or account password method to log in and verify whether the current user exists:

[0061] If yes, complete the login operation and save the login credentials to Redis after successful login;

[0062] If not, register the account using the account name and perform real-name authentication after successful registration, then log in using the account and password, and save the login credentials to Redis after successful login. Alternatively, obtain the verification code through the mobile phone number to register the account, then use the mobile phone verification code to log in, and save the login credentials to Redis after successful login.

[0063] That is, the buyer and seller systems on the web page support two login methods: mobile phone number + verification code and account + password.

[0064] When using the account + password method to log in to the data trading system, it will first verify whether the user account exists. If it exists, it will log in directly and generate login credentials and save them in Redis for direct login next time. If the user account does not exist, the account will be registered by the account name. After the registration is successful, the real-name information authentication (mobile phone number, ID number, email address, unified social credit code, etc.) will be performed. When you log in later, it will determine whether the login credentials are valid. If they are invalid, you will log in again and generate new login credentials. When the user's account information is changed, the login credentials will immediately become invalid and redirect to the login page.

[0065] When logging in to the data trading system using the mobile phone number + password login method, after filling in the mobile phone number, the data trading system will send a verification code with a specified validity period to the corresponding mobile phone number; after filling in the verification code and clicking login, it will also first determine whether the mobile phone number has been registered. If it has been registered, the login will be completed and the login credentials will be generated and stored in Redis; if it has not been registered, you need to redirect to the corresponding registration page to register and then log in.

[0066] Furthermore, the registration and login of the backend management account specifically include:

[0067] S121: The backend management system presets the account and password of the system super administrator, and synchronizes the account and password through offline distribution;

[0068] S122: Log in to the backend management system based on the issued account and password, and save the login credentials to Redis after successful login.

[0069] Specifically, the backend management system uses an account + password method for login. First, the backend management system will preset a system super administrator's account and password, which is responsible for initializing all account information of the backend management system, and synchronizing the account information to each user through offline distribution. Then, when the user logs in with the assigned account information, a login credential will be generated and stored in Redis. The next time you visit the backend management system, if the login credential is still valid, you can access it directly. If the login credential is invalid, you will be redirected to the login page to log in and then jump to the access address page. When the account information is changed after the login is successful (including user name, password, etc.), the current login credential will immediately become invalid and redirect to the login page.

[0070] It should be noted that after the login credentials are saved to Redis: when you log in again, if the login credentials are valid, the login operation is completed directly; if the login credentials are invalid, the login operation is performed again, and the login credentials are saved after the re-login is successful;

[0071] After successfully logging in, if the account information is changed, the login credentials will become invalid.

[0072] S2: Based on the account information synchronization API interface exposed by the data trading system, the third-party system account is registered and logged in to the data trading system, and the login information is saved;

[0073] Furthermore, in one embodiment, based on the account information synchronization API interface exposed by the data transaction system, the registration and login of the third-party system account in the data transaction system is realized, and the login information is saved, which specifically includes:

[0074] S201: When a third-party system account needs to log in to the data trading system, the third-party system connects to the account information synchronization API interface exposed by the data trading system and jumps to the data trading system;

[0075] S202: Determine whether the third-party system account already exists in the data transaction system:

[0076] If yes, log in to the data trading system directly through the third-party system account;

[0077] If not, synchronize the third-party system account to the data transaction system through the account information synchronization API (Application Programming Interface), register the account and log in, and save the login credentials to Redis after successful login.

[0078] Specifically, when a third-party system needs to log in to the data trading system, it needs to synchronize the corresponding account information to the data trading system. The third-party system needs to connect to the account information synchronization API interface exposed by the data trading system. When jumping to access the data trading system, it will determine whether the current third-party system account exists in the data trading system. If it does, it will directly log in to access the corresponding functional module; if it does not exist, it is necessary to synchronize the user's account information to the data trading system according to the requirements of the account information synchronization API to register the account and log in, and then access the corresponding functional module of the data trading system. The first successful login will generate a login credential and store it in the Redis cache. The corresponding address can be directly accessed during the validity period of the credential. When the credential expires or the account information changes, the account needs to be logged in again.

[0079] It should be noted that when a third-party system account successfully logs in to the data trading system and the login credentials are saved to Redis: during the validity period of the login credentials, the third-party system can directly access the data trading system, and when the login credentials expire or the information of the third-party system account changes, the third-party system account needs to log in to the data trading system again.

[0080] S3: Deploy login information, data transaction system business data, account registration and login, and account information synchronization in a cluster-based manner, and balance account login access traffic through load balancing strategies.

[0081] Specifically, relevant deployment is achieved by setting up a user center. The user center is deployed in a cluster manner, which can dynamically adjust the capacity according to the access volume of Internet users. At the same time, the traffic load of user login access can be balanced to each node of the cluster, which can support simultaneous online access by a large number of users.

[0082] Furthermore, this application meets the user management needs of different sources and different login methods of WeChat applets, web clients, backend management systems, and third-party business systems by designing a unified account table. For the key information of the logical structure, please see the description in Table 1 below.

[0083] Table 1

[0084]

[0085]

[0086] The account under the same account category and account type is unique. The account status is divided into authenticated and unauthenticated status. In the unauthenticated state, there is no authentication information, and the public pages and data can only be browsed as a visitor. The account authentication process is carried out in different authentication processes according to account category, account type, login method and other information. For example: personal accounts need to be logged in with mobile phone numbers and account passwords. When authenticating personal identity, it is necessary to authenticate the mobile phone number, ID number and other mandatory information. If it is a social account login, then it is necessary to pull the corresponding real-name authentication information from the social media API; enterprises need to authenticate the unified social credit code and other mandatory information. These authentication information can only be bound to one account.

[0087] The unified user management method for the data transaction system in the embodiment of the present application can achieve the unification and sharing of user data, avoid the problem of separate management of Internet users and enterprise users in the traditional way, and improve management efficiency; it can easily complete the user information exchange with the third-party system, has good scalability, and can be flexibly configured and expanded according to different business needs; it supports multi-user concurrent access and data processing, and can meet the needs of large-scale users online at the same time; it provides a rich user interaction method and improves the user experience.

[0088] In a second aspect, an embodiment of the present application also provides a unified user management device for a data transaction system.

[0089] In one embodiment, referring to Figure 2, Figure 2 This is a functional module diagram of the unified user management device for the data transaction system of this application. Figure 2 As shown, the unified user management device for the data transaction system includes: a data transaction system, a third-party system, and a user center.

[0090] The data trading system supports the registration and login of mini program accounts, web buyer and seller accounts, and backend management accounts; the backend management system is located in the data trading system.

[0091] The third-party system is used to synchronize account information with the data trading system, and to limit the registration and login of third-party system accounts in the data trading system; the user center is used to deploy login information, data trading system business data, account registration and login, and account information synchronization based on a cluster approach, and to achieve balance of account login access traffic through load balancing strategies.

[0092] For more information, see Figure 2 As shown, the data trading system supports the login of mini-programs, buyer systems, seller systems, and backend management systems. The third-party system includes third-party web frontend and third-party backend management. The user center includes account services, account synchronization, user logs, Mysql database, and Redis cache.

[0093] The Mysql database stores all user information, Redis caches user login information, the account service supports registration and login functions for all types of users, account synchronization provides API interface capabilities for synchronizing user information with third-party systems, and user logs record user operations and login logs.

[0094] On the third aspect, an embodiment of the present application provides a unified user management device for a data transaction system. The unified user management device for a data transaction system may be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.

[0095] Reference Figure 3 , Figure 3 The hardware structure diagram of the unified user management device for the data transaction system involved in the embodiment of the present application is shown in FIG. In the embodiment of the present application, the unified user management device for the data transaction system may include a processor, a memory, a communication interface, and a communication bus.

[0096] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0097] The communication interface includes input / output (I / O) interface, physical interface and logical interface, etc., which are used to realize the interconnection of devices inside the unified user management device for data transaction system, and the interface used to realize the interconnection between the unified user management device for data transaction system and other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.

[0098] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0099] The processor may be a general-purpose processor, and the general-purpose processor may call the unified user management program for the data transaction system stored in the memory, and execute the unified user management method for the data transaction system provided by the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the unified user management program for the data transaction system is called may refer to the various embodiments of the unified user management method for the data transaction system of the present application, which will not be repeated here.

[0100] Those skilled in the art will understand that Figure 3 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0101] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0102] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0103] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0104] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0105] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0106] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A unified user management method for data transaction systems, It is characterized in that The unified user management method for the data transaction system includes: Register and log in accounts from various sources on the data trading system, and save the login information to Redis after successful login; Based on the account information synchronization API interface exposed by the data trading system, the third-party system account is registered and logged in to the data trading system, and the login information is saved; Login information, data transaction system business data, account registration and login, and account information synchronization are deployed in a cluster-based manner, and account login access traffic is balanced through load balancing strategies.

2. A unified user management method for a data transaction system as claimed in claim 1, It is characterized in that The registration and login of multiple source accounts on the data transaction system specifically includes the registration and login of mini program accounts, the registration and login of buyer and seller accounts on the web page, and the registration and login of backend management accounts.

3. A unified user management method for a data transaction system as claimed in claim 2, It is characterized in that For the registration and login of the Mini Program account, it specifically includes: When opening the applet of the data trading system, obtain the mobile phone number bound to the user logged in to the application where the applet is located; Log in to the Mini Program based on the obtained mobile phone number, and determine whether the obtained mobile phone number has been registered in the Mini Program during login: If yes, the user will log in to the Mini Program based on the obtained mobile phone number, and save the login credentials to Redis after the login is successful. If not, register an account based on the obtained mobile phone number, bind the account of the user logging in to the application where the mini program is located, perform the login operation, and save the login credentials to Redis after the login is successful.

4. A unified user management method for a data transaction system as claimed in claim 2, It is characterized in that For the registration and login of the buyer and seller accounts on the web page, it specifically includes: Use the mobile phone verification code method or account password method to log in and verify whether the current user exists: If yes, complete the login operation and save the login credentials to Redis after successful login; If not, register the account using the account name and perform real-name authentication after successful registration, then use the account and password to log in, and save the login credentials to Redis after successful login. Alternatively, obtain the verification code through the mobile phone number to register the account, then use the mobile phone verification code to log in, and save the login credentials to Redis after successful login.

5. A unified user management method for a data transaction system as claimed in claim 2, It is characterized in that For the registration and login of the backend management account, it specifically includes: The backend management system presets the system super administrator's account and password, and synchronizes the account and password through offline distribution; Log in to the background management system based on the issued account and password, and save the login credentials to Redis after successful login.

6. A unified user management method for a data transaction system according to any one of claims 3 to 5, Features: After the login credentials are saved to Redis: When you log in again, if the login credentials are valid, you can directly complete the login operation. If the login credentials are invalid, you need to log in again and save the login credentials after the re-login is successful. After successfully logging in, if the account information is changed, the login credentials will become invalid.

7. A unified user management method for a data transaction system as claimed in claim 1, It is characterized in that The account information synchronization API interface exposed by the data transaction system realizes the registration and login of the third-party system account in the data transaction system and saves the login information, which specifically includes: When a third-party system account needs to log in to the data trading system, the third-party system connects to the account information synchronization API interface exposed by the data trading system and jumps to the data trading system; Determine whether the third-party system account already exists in the data transaction system: If yes, log in to the data trading system directly through the third-party system account; If not, synchronize the third-party system account to the data transaction system through the account information synchronization API interface, register the account and log in, and save the login credentials to Redis after successful login.

8. A unified user management method for a data transaction system as claimed in claim 7, It is characterized in that When the third-party system account successfully logs in to the data trading system and the login credentials are saved to Redis: During the validity period of the login credentials, the third-party system can directly access the data transaction system. When the login credentials expire or the information of the third-party system account changes, the third-party system account must be logged in to the data transaction system again.

9. A unified user management device for a data transaction system, It is characterized in that The unified user management device for the data transaction system: Data trading system, which supports registration and login of mini program accounts, web buyer and seller accounts, and backend management accounts; A third-party system is used to synchronize account information with the data trading system, and to limit the registration and login of the third-party system account in the data trading system; The user center is used to deploy login information, data transaction system business data, account registration and login, and account information synchronization based on a cluster approach, and to achieve balance of account login access traffic through load balancing strategies.

10. A unified user management device for data transaction systems, It is characterized in that The unified user management device for a data transaction system comprises a processor, a memory, and a unified user management program for a data transaction system stored in the memory and executable by the processor, wherein when the unified user management program for a data transaction system is executed by the processor, the steps of the unified user management method for a data transaction system as described in any one of claims 1 to 8 are implemented.

Images