CN116308377A

CN116308377A - Account management method, device, equipment and storage medium

Info

Publication number: CN116308377A
Application number: CN202211634927.1A
Authority: CN
Inventors: 李峰; 童贞理; 王柯; 刘琴
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2022-12-19
Filing date: 2022-12-19
Publication date: 2023-06-23

Abstract

The application discloses an account management method, an account management device, account management equipment and a storage medium, which relate to the technical field of communication and are used for improving the management efficiency of user accounts. Comprising the following steps: acquiring identity information of a target user, and creating a management account corresponding to the target user based on the identity information of the target user, wherein the management account is used for managing a plurality of accounts corresponding to the target user on an account management platform, and the accounts are accounts for logging in different application programs; acquiring basic information of a target user based on a management account corresponding to the target user, and constructing an information database corresponding to the target user, wherein the basic information comprises at least one of the following: account information, location information, parent information, consumption information, and point information; under the condition of logging in the account management platform, logging in the account management platform through a third party account based on the information database, wherein the third party account is an account corresponding to the third party application program. The method and the device are applied to the scene of user account management.

Description

Account management method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for account management.

Background

In the process of ecological operation, point-to-point cooperation cannot be used for resource sharing, so that a unified account operation platform is needed in order to have richer selection and more convenient service when consumers consume, and accordingly experience of consumers is improved. By means of the unified account operation platform, consumers can share benefits brought by growth of the consumers, the benefits are obtained as a naturally generated result, the benefits of each consumer on the platform are obtained, and the value can be created for other people, so that the value of the platform can be fully reflected.

Under the traditional point-to-point cooperation mode, the ecological capability is insufficient, the accounts of consumers are not uniformly managed, and ecological integration cannot be performed on the account level. The current account number is registered by taking the communication number as an identifier, a user account is established, and identity information corresponding to the user account is acquired so as to log in, authenticate and authorize through the communication number. And the operator acquires a plurality of user accounts registered by the account system through the communication number, and manually compares and analyzes data generated under the plurality of user accounts.

In the method, a plurality of different accounts which are established by taking the communication number of the user as the identification and exist in the account system cannot be used for unified management of the different accounts of the user in the account system, and a plurality of accounts corresponding to each account in the account system cannot be managed in a unified manner, so that the management efficiency of the user accounts is low.

Disclosure of Invention

The application provides an account management method, device, equipment and storage medium, which are used for improving the management efficiency of user accounts.

In order to achieve the above purpose, the present application adopts the following technical scheme:

in a first aspect, there is provided an account management method, the method comprising: acquiring identity information of a target user, and creating a management account corresponding to the target user based on the identity information of the target user, wherein the management account is used for managing a plurality of accounts corresponding to the target user on an account management platform, and the accounts are accounts for logging in different application programs; acquiring basic information of a target user based on a management account corresponding to the target user, and constructing an information database corresponding to the target user, wherein the basic information comprises at least one of the following: account information, location information, parent information, consumption information, and point information; under the condition of logging in the account management platform, logging in the account management platform through a third party account based on the information database, wherein the third party account is an account corresponding to the third party application program.

In one possible implementation, the method further includes: under the condition that an account management platform is logged in based on a management account corresponding to a target user, binding a first account with the management account to authorize the login of the account management platform through the first account, wherein the first account is an account for logging in a third party application program; or under the condition that the account management platform is logged in based on the management account corresponding to the target user, unbinding the second account and the management account so as to prohibit the account management platform from being logged in through the second account, wherein the second account is an account for logging in the third party application program.

In one possible implementation manner, the obtaining basic information of the target user based on the management account corresponding to the target user, and constructing the information database corresponding to the target user, includes: based on a management account corresponding to the target user, carrying out combined management on account information of the target user through a first preset model; analyzing the position information of the target user through a second preset model based on the management account corresponding to the target user, and determining the position track of the target user; and analyzing the friendly information of the target user through a third preset model based on the management account corresponding to the target user, and determining the friendly ring corresponding to the target user.

In one possible implementation, the method further includes: determining a first parameter and a second parameter corresponding to the management account, wherein the first parameter is a parameter corresponding to the management account in an account management platform, and the second parameter is a parameter corresponding to the management account in a third party application program; when the target user makes shopping on the account management platform, deducting the consumption amount through the first parameter; when the target user makes a purchase at the third party application, the amount of the consumption is deducted by the second parameter.

In one possible implementation, the method further includes: creating a plurality of labels for managing accounts, wherein the value of the managed accounts is indicated by the plurality of labels, and any label in the plurality of labels is respectively used for indicating any one of the following: rights to manage an account, a level to manage an account, a relationship to manage an account, a third party application to manage an account authorization.

In a second aspect, there is provided an account management apparatus, comprising: an acquisition unit and a processing unit; the acquisition unit is used for acquiring the identity information of the target user; the processing unit is used for creating a management account corresponding to the target user based on the identity information of the target user, wherein the management account is used for managing a plurality of accounts corresponding to the target user on the account management platform, and the accounts are accounts used for logging in different application programs; the acquisition unit is further used for acquiring basic information of the target user based on the management account corresponding to the target user, wherein the basic information comprises at least one of the following items: account information, location information, parent information, consumption information, and point information; the processing unit is also used for constructing an information database corresponding to the target user; and the processing unit is also used for logging in the account management platform through a third party account based on the information database under the condition of logging in the account management platform, wherein the third party account is an account corresponding to the third party application program.

In one possible implementation, the management account has multiple accounts of different applications bound to it; the processing unit is further used for binding the first account with the management account under the condition that the account management platform is logged in based on the management account corresponding to the target user so as to authorize the login of the account management platform through the first account, wherein the first account is an account for logging in a third party application program; and the processing unit is further used for unbinding the second account number and the management account under the condition that the account management platform is logged in based on the management account corresponding to the target user, so as to prohibit the account management platform from being logged in through the second account number, wherein the second account number is an account number for logging in the third party application program.

In one possible implementation manner, the processing unit is further configured to perform, based on a management account corresponding to the target user, combined management on account information of the target user through a first preset model; the processing unit is further used for analyzing the position information of the target user through a second preset model based on the management account corresponding to the target user and determining the position track of the target user; the processing unit is further used for analyzing the friendly information of the target user through a third preset model based on the management account corresponding to the target user, and determining the friendly ring corresponding to the target user.

In one possible implementation manner, the processing unit is further configured to determine a first parameter and a second parameter corresponding to the management account, where the first parameter is a parameter corresponding to the management account in the account management platform, and the second parameter is a parameter corresponding to the management account in the third party application program; the processing unit is also used for deducting the consumption amount through the first parameter when the target user makes shopping on the account management platform; the processing unit is further used for deducting the consumption amount through the second parameter when the target user makes shopping in the third-party application program.

In one possible implementation, the processing unit is further configured to create a plurality of labels for the management account, where the value of the management account is indicated by the plurality of labels, and any one of the plurality of labels is used to indicate any one of the following respectively: rights to manage an account, a level to manage an account, a relationship to manage an account, a third party application to manage an account authorization.

In a third aspect, an electronic device, comprising: a processor and a memory; wherein the memory is configured to store one or more programs, the one or more programs comprising computer-executable instructions that, when executed by the electronic device, cause the electronic device to perform an account management method as in the first aspect.

In a fourth aspect, there is provided a computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computer, cause the computer to perform an account management method as in the first aspect.

The application provides an account management method, device, equipment and storage medium, which are applied to a scene of user account management. When the user account needs to be managed, the identity information of the target user can be acquired, and a management account corresponding to the target user and used for managing a plurality of accounts corresponding to the target user on an account management platform is created based on the identity information of the target user, wherein the accounts are accounts used for logging in different application programs. Further, based on the management account corresponding to the target user, basic information including at least one of account information, position information, parent information, consumption information and point information of the target user is obtained to construct an information database corresponding to the target user. Under the condition of logging in the account management platform, the account management platform is logged in through a third party account corresponding to the third party application program based on the information database. According to the method, when the user account is required to be managed, the management account of the target user can be created to obtain the basic information of the target user, an information database corresponding to the target user is built, and then the account management platform is logged in through the third party account based on the information database. Therefore, when the user accounts are managed, the problems that a plurality of accounts used for logging in different application programs exist in an account system of the user, the plurality of accounts in the account system cannot be managed in a unified mode, and different accounts of the user corresponding to the different accounts in the account system cannot be managed in a unified mode are solved. Therefore, the management efficiency of the user account is improved.

Drawings

Fig. 1 is a schematic structural diagram of an account management system according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of an account management system according to an embodiment of the present application;

FIG. 3 is a schematic flow chart of an account management method according to an embodiment of the present application;

FIG. 4 is a schematic flow chart of user registration login on an account management platform according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a multi-level architecture of user management accounts according to an embodiment of the present application;

FIG. 6 is a business flow diagram for managing account authentication provided by an embodiment of the present application;

FIG. 7 is a schematic flow chart of cross-platform login of a user according to an embodiment of the present application;

fig. 8 is a schematic flow chart of system access by a third party using authentication of a management account according to an embodiment of the present application;

fig. 9 is a second schematic flow chart of an account management method according to an embodiment of the present application;

FIG. 10 is a schematic flow chart of a third party authorized login account management platform according to an embodiment of the present application;

fig. 11 is a schematic diagram of a mobile phone and mailbox binding procedure of an account management platform according to an embodiment of the present application;

Fig. 12 is a schematic diagram of a third party account authorization binding procedure of an account management platform according to an embodiment of the present application;

fig. 13 is a schematic diagram of a mobile phone number replacement binding procedure of an account management platform according to an embodiment of the present application;

fig. 14 is a schematic diagram of a third party account authorization unbinding procedure of an account management platform according to an embodiment of the present application;

fig. 15 is a schematic diagram of a mailbox unbinding flow of an account management platform according to an embodiment of the present application;

fig. 16 is a flowchart of a third account management method according to an embodiment of the present application;

fig. 17 is a flowchart of an account management method according to an embodiment of the present application;

FIG. 18 is a schematic diagram of a procedure for increasing Z values in a small store according to an embodiment of the present application;

fig. 19 is a schematic diagram of a small store return Z-value flow provided in an embodiment of the present application;

FIG. 20 is a schematic diagram of a small store Z-value deduction flow provided in an embodiment of the present application;

FIG. 21 is a schematic diagram of a frozen Z-value list processing flow for a small store in an incomplete state according to an embodiment of the present application;

FIG. 22 is a schematic diagram of a real-time calculation flow of Z value generation according to an embodiment of the present application;

fig. 23 is a schematic diagram of a non-operator Z-value auditing flow of a small store according to an embodiment of the present application;

Fig. 24 is a schematic diagram of a non-operator Z-value settlement process for a small store according to an embodiment of the present application;

fig. 25 is a flowchart fifth of an account management method according to an embodiment of the present application;

fig. 26 is a schematic structural diagram of an account management device according to an embodiment of the present application;

fig. 27 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

In the description of the present application, "/" means "or" unless otherwise indicated, for example, a/B may mean a or B. "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. Further, "at least one", "a plurality" means two or more. The terms "first," "second," and the like do not limit the number and order of execution, and the terms "first," "second," and the like do not necessarily differ.

With the increase of external competition, the traditional communication service is newly increased to be weak, the user boundary is urgently required to be expanded, and the product mode is innovated to form new development kinetic energy. Under the background of digitalization and ecology, the problems of reduced user value and risk of customer loss caused by policy changes such as accelerating and reducing fees, carrying numbers and converting networks and the like and the newly increased debilitation of traditional communication services are solved. The operators are required to make adjustments in aspects of resource aggregation, product innovation, internetwork platform construction, ecological integration and the like, optimize the traditional racetrack, construct a new racetrack, expand users and product boundaries, and form new development kinetic energy.

In the process of ecological operation, point-to-point cooperation in the traditional operation mode cannot form ecological aggregation so as to share resources. In order to make the consumer have richer choices and enjoy more convenient services, thereby further improving the user experience, and urgent needs are to get through each ecological partner system to realize sharing user resources and intercommunication user data and services. Thus, an ecological operation platform with unified accounts as bases can be created. There are many participants on this platform, which are held together by a benign circulatory system. By means of the circulation system, all participants on the platform share the benefits brought by the growth of the participants. Each participant on the platform holds the purpose of interest and creates value for others, so that the value of the platform can be fully revealed while the participants of each party obtain benefits.

The traditional point-to-point cooperation mode has insufficient ecology capability, serious homogeneity of communication products, poor differentiated experience of users, unified definition of natural person accounts and unified management of account resources are not realized, so that ecology integration cannot be realized at an account level, ecology and omnibearing image of natural persons or families cannot be realized at the account level due to lack of effective means, combined pricing cannot be realized based on consumer products (main business is only a part of pricing factors), and continuous and effective competitiveness of the traditional communication products is not realized.

Compared with the traditional operation mode, the current heterogeneous (i.e. non-operator) ecological cooperation mode has changes in business, information technology (internet technology, IT), finance, tax, audit and the like, so that an operation path which can be matched with each other for each module in a new business mode needs to be explored.

The current global mainstream standard operators all adopt an open account registration mode to open an internal system so as to unify consumption accounts of clients and identify multi-account consumption, thereby providing extreme services for users in different scenes. Meanwhile, a member grade and point system is built for the unified account, and online and offline resource ecological aggregation is promoted to become a member operation mode of global mainstream. Global benchmarking operators have reached consensus on creating differentiated advantages of the communication industry, creating consumer member systems independent of communication members. The leading business within and outside of the global industry has accumulated a series of successful experiences in unifying account management.

Specifically, through unifying the consumption accounts of the clients, the weak association of the user interaction to the bottom data is realized, the multi-account consumption is uniquely identified based on the client ID (i.e. the identity card number) of the background system, and the consumption requirement of the main ID of the front-end user is identified, so that the marketing interaction is realized. The marker post operators establish a consumer member system independent of communication members to perform member operation, and the viscosity and backward income of customers are improved through offline life circles and online digital rights and interests products. And a member system is established by taking the consumer as a unit, rights and interests are operated, the effectiveness of rights and interests resources is improved, and the ecological aggregation of online and offline resources is effectively promoted. The communication main industry differentiation advantage is created through experience, communication enabling is carried out, the customer value and the user preservation are promoted, and the family digital business development is promoted.

The account management capability based on the unified account of the natural person is not separated when the construction of natural person data, the coupling of internal and external resources, the promotion of deep value exchange with external alliances and polygonal ecological cooperation are perfected. The unified account (i.e. management account) takes natural people (i.e. users) as a core, serves the fields of communication and Internet, and has a multi-level account architecture for unified management. Based on unified account of each natural person, basic information, communication and internet account information and the like of the natural person are managed, collected and applied, and the system is expanded into a multi-member and multi-layer account system centering on family and friend circles, and an open account service is provided for ecological partners so as to promote free circulation of product elements, resource elements, price elements and the like in the account system.

The natural person unified account can integrate ecological resources inside and outside enterprises through account intercommunication, resource scheduling and other modes, and a new product ecological system is constructed. Meanwhile, the unified account is identified by natural personal uniqueness, and the characteristics of product information, payment accounts, behavior preferences and the like under natural people are highly collected, so that the dimension of the natural people is seen completely, and then the conversion from communication product operation to digital member product operation and the conversion from communication account consumption to member account consumption are realized based on ecological aggregation of natural people consumption accounts. By ecologically combining account resources at the account level, the design of innovative products is realized, the consumption experience of users is improved, and the range of the consumption users is enlarged. The operation boundary is continuously expanded from the aspects of a three-network user range, an ecological product marketing range and the like, the consumption mode of the customer is rebuilt by utilizing the new mode and tools, the consumption requirement of the customer is met, the consumption potential is released, the corresponding benefit is obtained, and a new income increasing point is formed.

For implementing a 'digital new IT' strategic blueprint of a group, an intelligent operation brain is constructed, and a platform-type, digital, intelligent and ecological enterprise is created. The new digital IT is required to be used as a core element and an important driving force for transformation, the actual operation conditions of the new digital IT are combined, key business, key products and key markets are focused, the operation mode and channel transformation upgrading are promoted, the information technology is used for creating value, the market demand is responded quickly, innovation and service capability are continuously built, the digital transformation foundation is tamped, and new vitality elements are injected for high-quality development of enterprises.

Specifically, the unified account is taken as platform capability, the member is taken as a communication carrier, and the point is taken as virtual currency, so that internal and external resources are coupled, the transformation of the Internet operation mode from the communication inside to the communication outside, from the communication to the digitalization and from the single number to the individual and family is realized, and the deep value exchange and multilateral ecological cooperation with the external alliance are promoted. The system solves the problems that information and data are isolated and capability cannot be aggregated and data resources are shared due to an IT system built through chimney construction, and a natural person unifies accounts with the capability open sharing as a target, so that a product platform operation system, a multi-channel collaborative operation system, a full-quantity customer value operation system and a 2P ecological compound operation system are built. Meanwhile, the current heavy-cost operation means are not suitable for an Internet consumption mode, intelligent operation brains are built on the basis of unified accounts, intelligent agile operation of enterprises driven by data and technologies is realized, business operation transformation is quickened, and the treatment level of the enterprises is improved.

Based on a unified account system of natural people, an ecological aggregation mode can be innovated. Specifically, based on the unified pass of the unified account system of the natural person as the basic access capability, the multi-dimensional and multi-application seamless connection between the person and the ecological platform is established. By means of a resource scheduling system of the unified account system, application barriers and resource barriers among ecological partners are broken, polygonal ecological value aggregation and free circulation of production elements and product elements are achieved, seamless connection of demands and smooth information among consumers, operators and ecological partners are achieved, and ecological operation of cross-domain, cross-boundary and cross-time is achieved.

Based on a natural person unified account system, a traditional operator consumption mode can be innovated. Specifically, based on a natural person unified account system and a family account and friend circle account system generated based on the natural person unified account, the traditional communication consumption mode depending on communication numbers is broken, more flexible product design and pricing modes are realized, the consumption constraint depending on operator numbers is eliminated, and the customer groups and product forms of companies are amplified.

Based on a natural person unified account system, an enabling mode can be innovated. Specifically, ecology is energized through a palace deployment and multi-tenant sharing system, a tenant mode and a channel resident mode are externally provided, and the maximized sharing of resource elements is realized. Through ecological operation, the limitation of user labels of traditional operators is broken through, the ecological labels of users are enriched and perfected, and more accurate big data energization is realized.

The application provides an account management method, when user accounts are required to be managed, identity information of a target user can be obtained, and a management account corresponding to the target user and used for managing a plurality of accounts corresponding to the target user on an account management platform is created based on the identity information of the target user, wherein the accounts are accounts used for logging in different application programs. Further, based on the management account corresponding to the target user, basic information including at least one of account information, position information, parent information, consumption information and point information of the target user is obtained to construct an information database corresponding to the target user. Under the condition of logging in the account management platform, the account management platform is logged in through a third party account corresponding to the third party application program based on the information database. According to the method, when the user account is required to be managed, the management account of the target user can be created to obtain the basic information of the target user, an information database corresponding to the target user is built, and then the account management platform is logged in through the third party account based on the information database. Therefore, when the user accounts are managed, the problems that a plurality of accounts used for logging in different application programs exist in an account system of the user, the plurality of accounts in the account system cannot be managed in a unified mode, and different accounts of the user corresponding to the different accounts in the account system cannot be managed in a unified mode are solved. Therefore, the management efficiency of the user account is improved.

The account management method provided by the embodiment of the application can be applied to an account management system. Fig. 1 shows a schematic diagram of the structure of an account management system. As shown in fig. 1, the account management system 20 includes: a server 21 and an electronic device 22. Wherein, the server 21 is used for storing data information and performing information interaction with the electronic device 22; the electronic device 22 is used for performing information interaction with the server 21 to manage the user account.

Fig. 2 shows another schematic configuration of the account management system. As shown in fig. 2, the front-end layer of the account management system 30 includes an application 31 and an interface (application programming interface, api) 32. The middle tier of the account management system 30 includes: a membership module 33, a Z-value module 34, a privileges module 35, a unified account module 36, and a pass module 37. Unified account module 36 includes user module 361, account module 362, account module 363, and ledger module 364.

Wherein, the application (which may be a personal computer (personal computer, PC), a 5 th generation internet hypertext markup language (H5) interface or a program public number) 31 is a fast-stay channel for an enabler (i.e. a partner, a third party platform), and creates new channel codes and developer information through a centralized channel, thereby realizing commission and settlement localized management. Specifically, the account management system 30 automatically constructs marketing grids and store capabilities according to the newly added channel and developer information system, and the resident uses the marketing capabilities and management capabilities by logging in the corresponding application 31. When the application 31 is H5, the account management system 30 may output information to a partner without development capability through H5, and the partner may pay attention to only marketing without considering technology development.

The interface 32 is used for enabling the third party platform independently, and when the interface 32 is an authentication interface, an account system synchronization interface, a Z-value operation interface or a member operation interface, the third party platform performs the business handling and the operation of the third party platform through the interface 32. Specifically, the third party platform sends a call request to the account management system 30 through the interface 32, the account management system 30 verifies the digital signature in the call request, and after the verification is passed, the corresponding service data is returned to the third party platform, so that the service data is prevented from being tampered and repudiated, and the service data operation is ensured.

The member module 33 is used for managing various members (such as personal members, family members and non-operator members), performing security audit, and managing the relationship between the members and rights, points and privileges; the Z-value module 34 is configured to formulate a Z-value rule (e.g., Z-value account-arriving and deducting rule, Z-value settlement rule, Z-value wind control rule) and manage Z-value application (e.g., Z-value addition, Z-value return, Z-value exchange, Z-value deduction, processing of non-frozen Z-value forms, real-time calculation of Z-value generation, and Z-value audit); the privilege module 35 is used to manage privilege combinations, privilege releases, card packages, privilege acceptors, privilege audits, privilege categories, and privilege validity checks.

The unified account module 36 is used for acquiring user information (including user basic information, account information and account book information), collecting user information to construct an information database and providing a solution for flexible scheduling of resources; the user module 361 is used for maintaining basic information of a user, and specifically, the user module 361 is used for managing the basic information of the user, constructing a family relationship between the user in a home network and a different network, synchronizing with headquarter user data and authorizing unique codes of the user through the unified account module 36; the account module 362 is configured to maintain an account of the user, and specifically, the account module 362 is configured to manage account information of the user at each source contact; the account module 363 is used for maintaining the user's account, and in particular, the account module 363 is used for managing the user's operator account, member account, Z-value account, financial account, and equity account.

Ledger module 364 is used to maintain Z-valued ledgers, membership ledgers, and equity ledgers for users. Specifically, maintaining a Z-value account book of a user includes recording an activity track of an operator Z value and a non-operator Z value; maintaining a member account book of the user comprises recording various member information and activity tracks of the user under a unified account; maintaining the user's equity ledger includes recording the equity information of the user under the unified account and its activity tracks. The pass module 37 is used for account management, authentication management, and authorization management.

An account management method provided in the embodiments of the present application is described below with reference to the accompanying drawings. As shown in fig. 3, the method for managing accounts provided in the embodiment of the present application is applied to an electronic device, and the method includes S201-S203:

s201, acquiring identity information of a target user, and creating a management account corresponding to the target user based on the identity information of the target user.

The management account is used for managing a plurality of accounts corresponding to the target user on the account management platform, wherein the accounts are accounts for logging in different application programs.

It can be understood that when the target user registers the account corresponding to the account management platform, the electronic device may acquire identity information of the target user, create a management account corresponding to the target user based on the identity information of the target user, and then acquire a plurality of accounts corresponding to different application programs by the target user based on the management account corresponding to the target user, and manage the plurality of accounts corresponding to the target user in the account management platform.

For example, the identity information of the target user may be an identification card number of the target user. The application may be a mailbox number or a third party application.

Optionally, when registering through the account management platform and logging in the account corresponding to the account management platform, the user can register and log in through a user-defined account, an identity card number real name, a mailbox number, a mobile phone number and a third party account (account corresponding to a third party application). In the registration login interaction, acquiring user identity information through a real-name authentication mode, and then completing login authorization according to identity information comparison; and when single sign-on is performed, user identity confirmation is performed through the credit bill to complete sign-on authorization.

In one design, as shown in FIG. 4, a flow diagram of a user registration login on an account management platform is shown. When a user registers an account through an account management platform, the user starts registration, enters a real-name registration page at the front end (the front end of the account management platform), inputs a name and an identity card number for real-name authentication, and shoots a user face through the front end so as to perform face recognition on the user. Then, the face, the name and the ID card number of the user are called through the back end (the back end of the account management platform) during real-name authentication so as to carry out H5 video living body analysis and living body detection of the api, and then the api is verified through three elements of public security. If the police three-element verification api passes, the user enters a registration information page at the front end, the user inputs an account number, a password, a confirmation password and submits registration at the registration information page, and then the rear end determines whether the account number of the user exists; if the three elements of public security verify api fails, the real name registration page at the front end is returned. If the back end determines that the account number of the user exists, the back end indicates that the account number exists and registration is unsuccessful, the front end prompts the account number to repeat and input again, and then the user inputs the account number, the password and the confirmation password again on a registration information page and submits the registration; if the back end determines that the account number of the user does not exist, the account number registration is successful, a main account (i.e. a management account) is created and stored, then the front end prompts the client to carry out mobile phone number binding, and the client determines whether to skip the mobile phone number binding. If the client determines to skip the mobile phone number binding, the registration is finished; if the client determines not to skip the mobile phone number binding, entering a mobile phone number binding flow through the back end.

When a user logs in an account through the account management platform, the user logs in and enters a login page at the front end (the user can quickly log in through a mobile phone number or log in through the mobile phone number, the account or an identity card number and a password). When the user logs in through the mobile phone number, the user inputs the mobile phone number and the verification code on the login page, and then the user verifies whether the mobile phone number exists through the rear end. If the mobile phone number exists, inquiring whether the main account is already real-named or not; if the mobile phone number does not exist, a main account (not real name) is created and associated according to the mobile phone number, the front end displays that login is successful, real name authentication is prompted, and a user determines whether to skip the real name authentication. If the main account is already real-named, the login is successful; if the main account is not real-name, prompting real-name authentication, displaying that login is successful at the front end, and prompting the user to perform real-name authentication. If the user determines to skip real-name authentication, ending the user login flow; if the user determines not to skip real-name authentication, the real-name authentication flow is entered through the back end.

When a user logs in through the mobile phone number, the account number or the identity card number and the password, the user inputs the mobile phone number, the account number or the identity card number and the password on a login page, and further verifies whether the account number and the password exist or not through the rear end. If the account number and the password exist, the verification is passed, and whether the main account is already real-named or not is inquired; if the account number and the password do not exist, the verification is not passed, and the login account number and the password are displayed by the front end, so that the user is prompted to input the mobile phone number, the account number or the identity card number and the password again on the login page.

S202, acquiring basic information of a target user based on a management account corresponding to the target user, and constructing an information database corresponding to the target user.

Wherein the base information includes at least one of: account information, location information, parent information, consumption information, and point information.

It can be understood that the electronic device may acquire the basic information of the target user based on the management account corresponding to the target user, further gather the basic information of the target user to construct an information database corresponding to the target user, and model the basic information of the target user in the information database corresponding to the target user to obtain a corresponding preset model, and manage and analyze based on the preset model.

Alternatively, the basic information of the target user may be divided into basic information, extension information, and reservation information. The basic information includes basic user profile information (e.g., user's credentials, account numbers corresponding to user's administrative account, user's status, user's real name identification, and user identification during or after cleaning); the extension information includes non-key user information (e.g., social information of the user, family information of the user (including relationship circles and relationship types), preference information of the user, work information of the user, business information (e.g., credit score, number information) of the user) extended in addition to the basic information; the reservation information is user information (e.g., consumption situation of the user, living situation of the user, tax situation of the user, and dispute situation of the user) provided by the external institution to the operator.

It should be noted that, the management account is a multi-level account architecture which uses the user as a core, serves the communication and internet fields, manages uniformly, and provides open account service for the partner in the ecology by the matched management account platform. Based on the data model design spirit of the management account, the business and transaction data such as user information, communication user information, relations among different users, user tag models, user consumption information, user families, relatives and friends networks, user points, rights and interests and the like which are scattered in each application system of headquarters and branch companies can be acquired, synchronized, converted and integrated into the corresponding information database of the user in real time, so that a basis of unified view of the user is formed.

Specifically, the management account is a multi-level and extensible account system taking a user model as a core, and a series of consumer accounts facing users, such as a membership account, a point account, a equity account, a communication account, a financial account and the like, are established based on the management account on the design thought. Modeling the relatives and friends information of the user through the big data application to obtain relationship accounts (including family accounts and friend circle accounts); the consumer accounts may also be subdivided, each of which is divided into multiple sub-accounts (e.g., member accounts into 5Gn future members, wovens, internet members, and non-carrier members; points accounts into Z-values, communications points, internet points, and non-carrier points; equity accounts into member equity, carrier's equity, cooperative equity, and ecological combined equity; communications accounts into wide moves, merges, universal terminals, and resource packages; financial accounts into wovens, card packages, electronic coupons, internet finance, and payment applications.) to construct sub-account models, to achieve hierarchical unified nano-tubes for accounts, and with scalability.

As shown in fig. 5, a multi-level architectural diagram of a user managing accounts is shown. The user management account multi-level structure comprises a main account layer, a combined account layer and a multi-dimensional sub-account layer. The main account layer comprises a management account, a family account and a friend circle account; the combined account layer comprises a member account, a point account, a equity account, a communication account and a financial account; the multi-dimensional sub-account layer includes 5Gn future members, wok members, internet members, non-carrier members, Z values, communication points, internet points, non-carrier points, member interests, carrier interests, collaboration interests, ecological combination interests, wide fixed movement, fusion, universal terminals, resource packages, wok accounts, card packages, electronic coupons, internet finance and payment type applications.

Optionally, based on the management account, data collection can be performed on the basic information of the user in each application system on the account management platform, and the basic information (such as communication data, rights and interests products, financial consumption, terminal contracts, members, and fusion services) of the user in each application system can be integrated, so that comprehensive and accurate image analysis can be performed on the user.

Specifically, an account number and a user data relationship of a management account taking a user unique identification (unit_id) as a main body are constructed through basic information of a user. And (3) completing basic information expansion of the user (such as indexes of real name, home network, registration time, contact system and the like). Finishing the collection of account information (such as communication account information, external application account information and internal-external open application account information) of a user; the collection of account information (e.g., financial, equity, membership, and communication accounts) for the user is completed.

S203, under the condition of logging in the account management platform, logging in the account management platform through a third party account based on the information database.

The third party account is an account corresponding to the third party application program.

It will be appreciated that in the case of logging into an account management platform, the electronic device may log into the account management platform via a third party account number based on the information database.

It should be noted that, the unified pass design of the present invention uses the user's ID card number as the unique identifier, and penetrates through the whole unified account (i.e. the account corresponding to the management account) system, the user with the unified account can directly log in and use in the application and service of joining the unified account ecological circle, and the complicated steps of repeated registration and repeated login of the user are avoided. On the premise of guaranteeing information security and providing better service for users, the method helps the users store and record the basic information, asset information and behavior information of the account. User management services such as unified account number, unified authentication, single sign-on everywhere authentication and the like are provided for partners (i.e., third party applications).

In one design, a business flow diagram for managing account authentication is shown in FIG. 6. When logging in the account management platform through the third party account, the user inputs the third party account for man-machine verification, calls the ID card number of the user corresponding to the terminal to log in the third party application program A, and logs in the third party application program B through skip-free login.

Specifically, when logging in the account management platform through the third party account, unified identity authentication (such as user-oriented real-name authentication, mobile phone number authentication, mailbox authentication, merchant entity authentication and bank card authentication of a merchant) is required to be used as a main basis for managing account binding association. After accessing the management account system, when the user jumps to a member mall at other contacts (namely, the user logs in across platforms), the management account standard is used for authentication and authentication, whether the user supports no-login or not is requested through the platform ID, the unit_id and the mobile phone number request interface, and if the user is verified to be the same user, the user can realize no-login.

As shown in fig. 7, a flow diagram of a user login across platforms is shown. The user clicks a member mall (external link), the platform side (member mall) requests login-free authentication, the platform ID (the ID distributed by the management account for the platform side) is checked through the back end (the back end of the account management platform), and the access token is returned to the platform side after the check. The platform side carries an access token request to jump to a member mall, login analysis is then requested to the back end through the front end (the front end of the account management platform), and the back end analyzes login information according to the access token to determine whether a unit_id (the unique identifier of a user on the platform side) exists. If the unit_id exists, directly logging in a main account (i.e. a management account) of the associated user according to the unit_id, and displaying that the logging in is successful at the front end; if the unit_id does not exist, it is determined whether the mobile phone number of the user exists. If the mobile phone number of the user exists, the main account is found through the mobile phone number, the association of the unit_id and the main account is carried out, the login is directly carried out, and the front end shows that the login is successful; if the mobile phone number of the user does not exist, a (un-real name) main account of the user is created, then the unit_id is associated with the main account, and the mobile phone number quick login process is entered.

It should be noted that, for cross-platform authorization of the internal platform application, only consideration is currently given to the member center, and when the member center is not logged in by other application access requests, association and binding of the unique identification of the application and the management account are performed. When a user logs in another application from one application, identity authentication (confirming the identity of an accessing party, which is the first step interception point of authentication) and access authentication (authenticating the accessing party passing through the identity authentication, limiting the resources accessible and operated by the accessing party) are needed to be specific, the identity authentication is an authentication mode used for login authentication among different applications, a management account returns a corresponding token (namely an access token) according to the ID of the application or platform registered by the user, a unique user identification (unit_id) and user identity information, and checks regression service according to the token, so that a cross-application login-free scene is realized.

Optionally, the step of generating the token digital signature comprises: firstly, performing dictionary ascending arrangement on all system parameters according to keys; then splicing all system parameters in a key+value form according to a sequencing result, and then applying a key (appKey) on the head-to-tail splicing to obtain a string to be signed in the shape of appKey+ke1+value1+ … keyn+valuen+appKey; finally, carrying out HmacSHA256 algorithm encryption (the key is an application key) on the string to be signed, and generating a token digital signature.

Optionally, in order to quickly interface with the third party application and realize authentication, the management account establishes two sets of processes according to different service application scenarios (authentication of the third party using the management account and authentication of the third party using the original system). In the case that the third party has an independent authentication system, the management account can perform system access without affecting the independent authentication system of the third party (i.e., the third party performs system access using authentication of the management account). Specifically, the management account is abutted with the authentication information of the third party application system, and the management account obtains the information of the user from the third party application system through the authentication information of the third party. And then storing the user information by the management account, and establishing the account information of the user in the management account. When a user uses the service interface through the management account, the management account provides a unified authentication bill of the unique time limit times of the user, and the service interface providing system acquires the user identity information from the management account through the unified authentication bill and provides the use authority of the user.

As shown in fig. 8, a flow diagram of system access by a third party using authentication of a management account is shown. The user logs in the application system of the third party and triggers the service, the application system of the third party sends a third party token and a service code to the management account, the management account carries out third party service authentication, and the third party token is sent to the application system of the third party. And the application system of the third party makes legal judgment according to the third party token and analyzes the user information. And the application system of the third party sends the analyzed user information to a management account, the management account acquires the user information, then performs user authentication, user authorization and account generation, acquires a service path, integrates the service path into a uniform resource location system (uniform resource locator, URL) and sends the uniform resource location system to the application system of the third party. User access is performed through the application system of the third party, the service interface providing system obtains the call URL request, and user authentication is performed through the management account, so that the service interface of the service interface providing system is realized.

Under the condition that the third party does not have an independent authentication system, the management account can provide a series of interface capability and use scenes, and an application system of the third party is helped to finish user authentication. Specifically, the application system of the third party applies for distributing the appId and the appKey to the application system of the third party by managing the account, and provides interface participation (comprising two parts of public parameters and business parameters) according to the interface request requirement. Wherein, all relevant interfaces need to be imported with public parameters, and business parameters are imported according to specific interface description when user authentication of management account is carried out.

In one design, as shown in fig. 9, an account management method provided in an embodiment of the present application manages an account bound with a plurality of account numbers of different applications, where the method includes S301 or S302:

s301, under the condition that an account management platform is logged in based on a management account corresponding to a target user, binding a first account number and the management account to authorize the login of the account management platform through the first account number.

The first account is an account for logging in a third party application program.

It can be appreciated that in the case of logging into the account management platform based on the management account corresponding to the target user, the first account number may be bound with the management account first to authorize the logging into the account management platform through the first account number, and then the first account number for logging into the third party application program is used to log into the account management platform directly.

Optionally, before logging into the account management platform through the account number of the third party application program, the third party authorization binding (i.e. binding the account number of the third party application program with the management account) needs to be performed through unified authorization management. Specifically, when the user logs in, a third party login is selected, then a third party authorization page is called to confirm the authorized login, and the back end (the back end of the account management platform) carries out association and binding of management accounts according to the returned open-id. Yet another way is to make silent log-ins when a third party application initializes a page.

As shown in fig. 10, a flow diagram of a third party authorized login account management platform is shown. The user selects a third party login through a login page at the front end (the front end of the account management platform) and enters a third party authorization page. The user confirms the authorized login through the third party authorization page and transmits an open-id to the back end (the back end of the account management platform). The back end inquires whether the user registers and has a unique test through the open-id, if so, the user logs in directly, the login is successful through the front end, and then whether the user is real-name is determined through the back end; if not, returning to the binding mobile phone page, and selecting whether to skip the binding mobile phone by the user through the binding mobile phone page at the front end. If the back end determines the real name of the user, ending the flow; if the back end determines that the user does not have the real name, the front end reminds the user to carry out real name authentication, and the user determines whether to skip the real name authentication. If the user selects to skip the binding mobile phone, the back end creates a current according to the open-id, registers and logs in, then the front end displays that the login is successful, and the back end determines whether the user is real; if the user chooses not to skip the bound mobile phone, the process of the bound mobile phone is entered through the back end. If the back end determines the real name of the user, ending the flow; if the back end determines that the user does not have the real name, the front end reminds the user to carry out real name authentication, and the user determines whether to skip the real name authentication. If the user determines to skip real-name authentication, ending the flow; if the user determines not to skip the real-name authentication, the real-name authentication process is entered.

Optionally, as shown in fig. 11, a handset and mailbox binding flow diagram of the account management platform is shown. The user selects to bind the mobile phone number (or mailbox account number) through the personal center information page of the front end (the front end of the account management platform). Then, a binding mobile phone page (or mailbox page) at the front end is entered, a user inputs a mobile phone number (or mailbox number) through the binding mobile phone page (or mailbox page), the legality of the mobile phone number (or mailbox number) is determined, and a verification code is acquired through the back end (the back end of the account management platform). The user inputs the verification code on the binding mobile phone page (or mailbox number) and verifies the verification code through the back end. The back end inquires whether a verification code exists in the mobile phone account (or the mailbox account), if the mobile phone account (or the mailbox account) exists, the registered mobile phone account (or the registered mailbox account) fails in binding, the front end prompts that the mobile phone number (or the mailbox number) fails in binding, and the mobile phone number (or the mailbox number) is rebindd after the registered mobile phone account (or the mailbox account) is logged in for unbinding; if the mobile phone account (or the mailbox account) does not exist, the mobile phone account (or the mailbox account) is created, the mobile phone account (or the mailbox account) is associated with the management account and stored, and the front end prompts that the mobile phone number (or the mailbox number) is successfully bound.

Optionally, as shown in fig. 12, a third party account authorization binding flow diagram of the account management platform is shown. The user selects and binds a third party account number (namely, the account number of the user in a third party application program) through a personal center information page of the front end (the front end of the account management platform), enters a third party authorization page, confirms authorized login through the third party authorization page, and transmits an open-id to the back end (the back end of the account management platform). The back end inquires whether a third party account exists according to the open-id, if the third party account exists, the binding fails, the front end prompts the bound third party account, and the client confirms whether to replace the bound third party account; if the third party account number does not exist, the open-id association management account is authorized and stored, and the binding success is prompted through the front end. If the client confirms that the binding third party account is replaced, the open-id association management account is authorized and stored, and the binding success is prompted through the front end. If the customer confirms that the bound third party account is not replaced, the process is ended.

S302, unbinding the second account number and the management account under the condition that the account management platform is logged in based on the management account corresponding to the target user, so as to prohibit the account management platform from being logged in through the second account number.

The second account is an account for logging in the third party application program.

It can be appreciated that in the case of logging into the account management platform based on the management account corresponding to the target user, the second account may be unbinding from the management account, so as to prohibit logging into the account management platform through the second account.

It should be noted that, generally, the user actively initiates the third party authorization unbinding, and the third party authorization unbinding process and the third party binding authorization process just perform the disassociation operation of the management account according to the returned open-id and the unit-id.

Optionally, as shown in fig. 13, a mobile phone number replacement binding flow diagram of the account management platform is shown. The user selects to change the unbound mobile phone number through the personal center information page of the front end (the front end of the account management platform). And then entering a front-end verification old mobile phone number page, inputting a bound old mobile phone number by a user through the verification old mobile phone number page, determining the legality of the old mobile phone number, acquiring a verification code by a rear end (the rear end of the account management platform), inputting the verification code by the user on the verification old mobile phone number page, and verifying the verification code by the rear end. When verification code verification passes, the front end jumps to the replacement binding mobile phone page, a user inputs a binding new mobile phone number by replacing the binding mobile phone page, the verification code is acquired through the rear end, and the user inputs the verification code on the replacement binding mobile phone page and verifies the verification code through the rear end. The back end inquires whether the mobile phone account exists, if the mobile phone account exists, the registered mobile phone account fails to bind, the front end prompts that the binding of the new mobile phone number fails, and the new mobile phone number is bound again after logging in the registered mobile phone account to unbind; if the mobile phone account does not exist, the mobile phone account is replaced, the replaced mobile phone account is associated with the management account and stored, and the front end prompts that the replacement binding is successful.

As shown in fig. 14, a schematic diagram of a third party account authorization unbinding procedure of the account management platform is shown. The user selects to unbind the third party account number through the personal center information page of the front end (the front end of the account management platform), and transmits an open-id to the back end (the back end of the account management platform). And the back end inquires whether the third party account is bound according to the open-id. If the third party account is bound, deleting the third party account corresponding to the open-id, and prompting that the unbinding is successful through the front end; if the third party account is not bound, it is determined whether other accounts are bound. If the other accounts are bound, inquiring whether the bound other accounts are accounts authorized by a third party; if other account numbers are not bound, the account numbers cannot be unbound, and the user is requested to bind the mobile phone numbers and then unbound through the front-end prompt. If the other account number bound is the account number authorized by the third party, entering a third party authorization page, inputting a third party account number and a password by a user through the third party authorization page, performing login authorization, deleting the third party account number corresponding to the open-id through the rear end, and prompting that the unbinding is successful through the front end; if the other account number bound is not the account number authorized by the third party, deleting the account number of the third party corresponding to the open-id through the back end, and prompting that the unbinding is successful through the front end.

As shown in fig. 15, a schematic diagram of a mailbox unbinding flow for an account management platform is shown. The user selects to unbind the mailbox account through a personal center information page of the front end (the front end of the account management platform). Then, entering an unbinding mailbox page at the front end, inputting a mailbox number by a user through the unbinding mailbox page, determining the legality of the mailbox number, acquiring a verification code by the rear end (the rear end of the account management platform), inputting the verification code by the user at the unbinding mailbox page, and checking the verification code by the rear end. The back end inquires whether a mailbox account exists, if so, the mailbox account is deleted, unbinding is successful, and unbinding is successful through the front end prompt; if the mailbox account number does not exist, unbinding is impossible, and the user is requested to bind the mailbox number and unbinding through the front-end prompt.

In one design, as shown in fig. 16, the method in step S202 of the present application specifically includes S401-S403:

s401, based on a management account corresponding to the target user, carrying out combined management on account information of the target user through a first preset model.

It can be understood that the basic information of the target user can be obtained based on the management account corresponding to the target user, and then account information in the basic information of the target user is collected through the first preset model, so that account information of the target user is managed in a combined mode.

Optionally, the first preset model (i.e. the account aggregation model) may be configured to manage a series of accounts facing the target user (i.e. account information of the target user) such as a member account, a point account, a equity account, a communication account, and a financial account based on the management account. And the relationship account modeling can be performed according to the account information of the target user so as to expand the dimension of the advocacy relationship and realize the unified management of the user account.

S402, analyzing the position information of the target user through a second preset model based on the management account corresponding to the target user, and determining the position track of the target user.

It can be understood that the basic information of the target user can be obtained based on the management account corresponding to the target user, and then the position information in the basic information of the target user is analyzed through the second preset model to determine the position track of the target user.

Optionally, based on big data processing and analyzing means, the historical position of the user can be pulled through the base station position information in the voice use detail list and the flow use detail list of the local network user, the user position information is obtained, a second preset model (namely a behavior track model) with the position as granularity is established for the user, the position information of the target user is further analyzed through the second preset model, the position track of the target user is determined, and the representation of the position track of the user is realized.

S403, based on the management account corresponding to the target user, the friendly information of the target user is analyzed through a third preset model, and the friendly ring corresponding to the target user is determined.

It can be understood that the friendly information of the target user can be obtained based on the management account corresponding to the target user, and then the friendly information in the basic information of the target user is analyzed through a third preset model, so that the friendly ring corresponding to the target user is determined.

Optionally, home subscriber identification (or home subscriber identification based on a family group of future members, or sharing group member and friend circle user identification based on a future member sharing group, and grouping identification of users of the same family or sharing group) can be performed through a home relationship identification model according to the aspects of account closing relationship, fusion package, same certificate number, same certificate address, same night call base station+high-frequency call, account closing payment, mobile phone main and auxiliary card slots, and the like, so as to obtain parent and friend information of a target user; and then, the parent-friend information in the basic information of the target user is analyzed through a third preset model (namely, a personnel relationship model), and the parent-friend ring corresponding to the target user is determined.

In one design, three algorithms (logistic regression, gradient descent and L1 regularization) are used to perform model training to obtain a first preset model, a second preset model and a third preset model, and iterative optimization is performed continuously to improve model accuracy.

The main body of the model uses a logistic regression algorithm, and the regression parameters are iterated through training positive and negative samples, so that the probability of existence of personnel relations (family relations and sharing group relations) is calculated for the numbers of which the personnel relations (family relations and sharing group relations) are unknown; the logistic regression model is a nonlinear model, and the sigmoid function (a two-classification method) is shown in the formula one:

the gradient descent method is used for realizing coefficient iteration of logistic regression, firstly, an initial value (can be given to a random value or can be given to 0) is given to a vector theta, then the value of J (theta) is changed, so that J (theta) is carried out in the direction of the fastest gradient descent, and finally, a local minimum value is obtained after iteration is continued, and the function form is shown as a formula II:

the L1 regularization is used for performing linear fitting on input fields when calculating logistic regression parameters, the L1 regularization can iterate unimportant tag coefficients into 0, overfitting caused by excessive input tags is prevented, and therefore a model is simplified, and a functional form is shown as a formula III:

/>

l1 regularization amounts to adding a priori knowledge to the model (w obeys zero-mean laplace distribution). Laplace distribution: l1 regularization is the sum of the absolute values of the individual elements in the weight vector w. The L1 regularization increases the sum of absolute values of all weight w parameters to force more w to be zero, namely sparseness is achieved, and one key reason of the sparseness rule is that the sparseness rule can achieve automatic selection of the features. The introduction of L1 regularization is to complete the light mission of feature automatic selection, which learns to remove the unwanted features, i.e., resets the weights corresponding to the features to 0.

In one design, as shown in fig. 17, an account management method provided in an embodiment of the present application includes S501-S503:

s501, determining a first parameter and a second parameter corresponding to the management account.

The first parameter is a parameter corresponding to the management account in the account management platform, and the second parameter is a parameter corresponding to the management account in the third-party application program.

It is understood that the first parameter and the second parameter corresponding to the management account on the account management platform may be determined.

It should be noted that, the Z value (i.e. the parameter corresponding to the management account in the account management platform) is a virtual token for realizing free circulation exchange of the customer resources of multiple applications, multiple merchants and multiple channels in the operator and the ecological circle in the user management account ecosystem. Considering non-operator billing and external settlement risk, the non-operator billing is classified into an operator Z value (i.e., a first parameter) and a non-operator Z value (i.e., a second parameter) according to the Z value attribute. The Z value of the operator is a token generated according to a certain proportion after the user purchases a terminal and interests in an intelligent cloud hall and a self-service hall of the operator for a 5Gn future member system user for network shifting and broadband user communication consumption. The non-operator Z value is a token generated according to a certain proportion after non-operator online or offline scene consumption for a 5Gn future member system user.

Z value account-arriving and deduction rule: the Z value is immediately checked out, and the Z value can be used after checking out (a return rule is set for the Z value of an operator, and the generated and consumed Z value is returned after returning; the default validity period of the Z value is one year (365 days); the intelligent cloud terminal can be withheld when being used in an on-line scene (such as withholding when a smart cloud hall purchases a terminal or a commodity such as a universal terminal, rights and interests and the like); the terminal can be withheld when being used in an on-line scene (such as withheld when an operator purchases the terminal or the universal terminal (only bare metal) in a self-service hall); the Z value can be deducted on-line and off-line consumption of non-operator commercial tenant; the Z value withholding sequence is to withhold the Z value of the operator preferentially, and withhold the Z value of the non-operator, and each Z value withholds the part with short expiration time preferentially; the Z value deduction range is that only the terminal batch homodyne/commodity gross profit part can be deducted, and the temporary deduction proportion is set to be 5% of commodity selling price by adopting a full subtraction mode. (to ensure user perception and product management, thousands of thousands are implemented, which products are specifically included in the Z-value deduction system and the specific deduction amount).

Z value settlement rules: the Z value of the operator is deducted in the communication consumption, and settlement is not needed; the Z value of the operator is deducted when the non-operator consumes, and the operator settles the payment to the non-operator (the initial communication releases true gold and silver, the non-operator is driven to participate, and finally the non-operator is driven to cooperate by means of flow); the Z value of the non-operator is deducted when the operator and the non-operator consume the Z value, settlement is not needed (the situation that the non-operator cannot radically get rid of the behavior of the bill is avoided, and the case of the bill is not effectively avoided at present); the Z-value settlement period is monthly settlement.

Z value wind control rule: the Z value risk is controlled to be Z value account (namely integral account), when Z value generation is carried out, the system can carry out key monitoring on the content such as release quantity, generation face value, validity period and the like (for example, the Z value is limited to be acquired by a user every day to be not more than 2 ten thousand); the Z value risk is controlled to be the Z value account which should support an automatic monitoring function, abnormal transactions are monitored timely and prevented in advance (e.g. transaction limit is that the Z value consumption of a user per day must not exceed 10 ten thousand, the accumulated consumption of the user per day reaches a threshold value, and the Z value exchange can not be used any more per day).

The operator Z value comprises a consumption Z value, a presentation Z value and a conversion Z value, wherein the consumption Z value can be divided into an online terminal Z value, an offline terminal Z value, an online equity Z value and an offline equity Z value; the gifting Z value can be divided into an active Z value and a compensation Z value; the transfer Z values include a telephone bill sales Z value and a communication credit Z value. The non-operator Z-value includes a consumption Z-value.

By dividing the Z values into non-operators and operators, 4Z value generation flow lines are established in total, so that visual participation experience of users is provided when service operation is met. Z value generation flow of operator consumption type business: the Z value is generated mainly through the business operation activities of the corresponding terminal and the purchase of rights and interests on line and off line; z value generation flow of operator giving class business: mainly aiming at the situations of active operation, user complaint compensation and the like, the perception of a user is improved through a Z value; z value generation flow of operator exchange type business: the Z value operation is mainly carried out by converting communication points and consumption of users such as broadband, mobile network and fixed telephone per month, and the service of the users is provided through Z value conversion; z value generation flow of non-operator consumption business: the method mainly provides contact surfaces and behavioral ecologies of users and operators in a non-operator ecology system through non-operator partners of value-added services of Z values in cooperation with the non-operators.

S502, deducting the consumption amount through the first parameter when the target user makes shopping on the account management platform.

It will be appreciated that the amount of consumption may be deducted by the first parameter when the target user makes a purchase at the account management platform.

S503, deducting the consumption amount through the second parameter when the target user makes shopping in the third party application program.

It will be appreciated that the amount of consumption may be deducted by the second parameter when the target user makes a purchase at the third party application.

It should be noted that in the ecological cooperation scenario of the operators and the non-operators, the value exchange and mutual drainage of the operators and the non-operators can be realized through the Z values, so that a small store for managing the ecological cooperation of the accounts is taken as a research object, and a set of complete non-operator Z value application flow is designed for the business scenario, and the capability is decoupled and precipitated, thereby laying a foundation for the open sharing of the capability in the future.

Optionally, the Z-value increasing process is mainly used for the user to purchase goods in a small store, based on the actual payment amount, 1:1 generates a Z value. Specifically, after a user purchases goods and pays in a small store, the goods can be sent to a management account through order information, real-time Z value generation of a non-operator is performed, and real-time Z value calculation is performed by means of account management capability of a large data platform. As shown in fig. 18, a schematic diagram of a small store Z-value increasing flow is shown. The user selects commodity through a small store (namely a third party application program), pays commodity amount through a payment company, and completes order placement (big data can be subjected to payment order data synchronization through the payment company). The management account receives orders through a service order synchronization interface (api-0015), when order data is completed, the Z value to be newly added is complemented, and a message of the completed order data is sent to big data. And comparing the actual payment amount of the order with the gear, calculating through a Z value calculation rule, and converting the Z value to be newly added into a formal Z value through a management account.

The Z value return flow is used in a scene that a user purchases goods in a small store and acquires Z value and returns the list. Specifically, after the user returns the order in the small store, the management account determines whether the order back information is valid or not through real-time order comparison and payment order inquiry, and carries out deduction Z value back and gift Z value deduction. And the data is transmitted to the unified operation system in real time, so that support is provided for the data report tabulation. As shown in fig. 19, a schematic diagram of a small store return Z-value flow is shown. The user returns a refund and returns a bill through a small shop, the small bill carries out refund and returns a bill to audit, then a management account carries out order return through a service order return synchronous interface (api-0016), the deduction Z value is complemented back, the Z value is generated and deducted (can be deducted into a negative value) (the returned deduction Z value and the deduction Z value generated can be synchronized to a return order list of a unified operation system), and the returned deduction Z value and the deduction Z value generated are sent to the small shop for full refund. When refund is carried out by a payment company, the refund amount can be returned to the user in an original way; the refund amount may be synchronized to a payment manifest of the unified operating system; the refund result may be pushed to the small store. The unified operating system may generate a reconciliation file based on the order back list and the payment list and synchronize the reconciliation file period to the store.

The small store Z value exchange flow is used for users with Z values, and in the scene that the small store purchases commodity to withhold cash. Specifically, when the small store performs the Z value deduction flow, the commodity price and the total amount information of commodity information and order information contained in the order are compared with the total amount of the order commodity (or commodity) in the management account, and the Z value is frozen by the commodity Z value deduction proportion. And if the user order is not paid, releasing the frozen Z value, and converting the frozen Z value into actual consumption after the order is paid.

As shown in fig. 20, a schematic diagram of a small store Z-value deduction flow is shown. The user purchases the commodity through the store and obtains the token through the management account based on the interface 1 (api-0001). The store queries the redeemable Z-value based on the acquired token (re-acquires the token if the token is found to be invalid), and then checks the redeemed order value based on the order redeemable Z-value and the business redeemable Z-value query interface (api-0013). The Z-value used by the user is calculated by the administrative account and the maximum frozen Z-value requested at this time is frozen. Order handling is performed by the store to determine whether to use Z-value deduction (reacquire token if token failure is found). If the Z value is determined to be used for deduction, submitting the order (when submitting the order, the order can be synchronized to a management account based on a business order synchronization interface (api-0015), checking the order through the management account, and consuming the Z value or releasing the frozen Z value); if it is determined that Z-value deduction is not used, then the frozen Z-value is released through the management account based on the traffic release Z-value capability interface (api-0014).

The unfinished frozen Z value list processing flow is suitable for the situation that the available Z value is frozen and an order is required to be waited because of the inquiry before the user purchases the commodity, and the corresponding Z value processing can be carried out according to the order effective rule within 30 minutes. Specifically, the store will display the available Z value to the user before paying the order, facilitating the user to choose to withhold cash. If the user completes the payment within 30 minutes, the Z-value thaws and normally withholds, and if 30 minutes is exceeded, the order voides releasing the Z-value. In addition, the management account rechecks the unused frozen Z value of yesterday at 0 a.m. every day, and returns the order inquiry interface of the small store through the frozen order in the order of the small store. And checking according to order information, converting the needed to be actually consumed into the actual consumed, and releasing the frozen Z value needed to be released.

As shown in fig. 21, a schematic diagram of a frozen Z-value list process flow is shown for a small store at an outstanding end. The order state is provided by the small store, and when the Z value is used for the order state, the management account is handed over to perform order state processing. The management account determines whether the order is finished, if yes, whether a Z value is used in the order is determined; if it is determined that the order is outstanding, it is determined whether the order has timed out (e.g., over 30 minutes). If the Z value is used in the order, comparing the data to be withheld with the frozen Z value, and processing the data by a system to consume the Z value; if it is determined that the Z value is not used in the order, the system processes the Z value and returns the unused Z value. If the order is overtime, the order is abnormal data, rule auditing is carried out through early warning, and consumption of Z values and return of unused Z values are carried out through manual intervention; and if the order is determined not to be overtime, carrying out frozen Z-value order inspection every preset time period (such as 5 minutes), if the frozen Z-value order is inspected, inquiring order information through a third party order number provided by a small store to carry out order status review, determining the order status, and sending the order status to the small store, and if the frozen Z-value order is not inspected, continuing inspecting every preset time period. After the consumption of the Z-value and the return of the unused Z-value are performed, the final filing is performed.

When the real-time calculation of generating the Z value is performed, the Z value is performed in the back-end bin, but since the management account application is deployed in the palace and the back-end bin is locally placed, delay in data transmission and delay in Z value generation may occur. The Z value calculation can be completed by placing the Z value calculation in a management account, so that the instantaneity of Z value generation is improved.

Alternatively, as shown in fig. 22, a schematic diagram of a real-time calculation flow of Z-value generation is shown. And the upper system acquires the non-operator order data, the non-operator member information and the Z value information table through the message service. Through the non-operator order data and the non-operator member information, order rule analysis is carried out, rule check is generated, and then payment flow verification and order information check are carried out; and updating the Z value information table through the Z value information table. During payment flow verification, performing third-party payment inquiry through the payment inquiry; and when order information is checked, performing third-party order inquiry through the order inquiry. Then, the Z value generation calculation is performed, and the Z value information table is updated. And sending the updated result to the upper-level system through the message service.

And the management account calculates and generates a Z value in real time according to the order data and the payment data, then sends the order data, the payment data and the generated Z value to a rear-end number bin for auditing, and if abnormal data are audited, the Z value is frozen. As shown in fig. 23, a schematic diagram of a non-operator Z-value auditing flow for a small store is shown. And sending non-operator order data, third party payment order, management account Z value data and future member information to an auditing module (the auditing module comprises order amount auditing, order total amount and actual amount auditing, order consumption Z value auditing, order freezing Z value auditing, order generation Z value auditing and Z value abnormal auditing) for auditing through a message service, and obtaining abnormal auditing and full quantity data. And then, the abnormal audit is sent to a short message platform, and an audit report is generated through the full data.

It should be noted that, the auditing module is used for performing real-time postterm auditing work. Specifically, when the order data and the Z value data generate marketing, the auditing module completes real-time auditing work according to an actual payment rule (such as Z value 1 to 1 generation), an order freezing rule and an order transferring consumption rule, and performs timing inspection on whether the current Z value of the member has an order. When the problems are checked, the information is pushed to developers and auditing management staff in time, and an auditing report is generated so as to support the inquiry and positioning of the problems.

Optionally, when settling the non-operator order, a checking mechanism is established to realize that the system generates a non-operator deduction report at the beginning of each month, the non-operator deduction report provides the relation details between the deduction of each order and the order, and an auditor can check and review manually through the non-operator deduction report. When the auditor determines that the report passes, archiving and photographing report data; when the auditor determines that the report fails, the auditor triggers a data rechecking process, and the calculation is restarted after the data rechecking is carried out.

As shown in fig. 24, a schematic diagram of a non-operator Z-value settlement flow for a small store is shown. And calculating and executing the Z value consumption of the operator, comparing the Z value consumption with the non-operator order to generate a non-operator deduction report, and then checking and rechecking the non-operator deduction report manually. If the non-operator withholds report review pass, data archiving and report settlement are carried out; if the report audit and review of the non-operator withholding is not passed, the data is repaired, and the repaired data is recalculated.

In one design, as shown in fig. 25, an account management method provided in an embodiment of the present application includes S601:

S601, creating a plurality of labels for the management account, and indicating the value of the management account through the labels.

Wherein any one of the plurality of labels is used to indicate any one of the following, respectively: rights to manage an account, a level to manage an account, a relationship to manage an account, a third party application to manage an account authorization.

It can be appreciated that a management account tag library can be created based on an information database corresponding to the target user, tags in the management account tag library are divided into a plurality of tags, and then the value of the management account is indicated through the plurality of tags.

Alternatively, the management account tag library may include a user base tag, a user-extensible data tag (having the capability of extending a dynamic data segment and reserving a corresponding space), a user-home base tag, and a user-home-extensible data tag. The user base label may include an identification number, gender, age, home address, user business attribute, terminal network type, authorization response ciphertext (authorization response cryptogram, APRC), master number ID, multiple associated number IDs, woth credit, also UC guard length income for the user's lower number card, number terminal type for the user's lower number card, existing star rating for the user's lower number card, number subscription relationship for the user's lower number card, number cross-domain attribute for the user's lower number card, and average income per user for the user's lower number card (average revenue per user, ARPU); the user-extensible data tag may include a number of ubiquitous intelligent terminals, a type of ubiquitous intelligent terminal, a rights code, channel contact liveness, resident location information, extraordinary location information, a resident location stamp, an extraordinary location stamp, a payment method, and a rights collection; the user home base tag may include a home user main account ID, a home member ID, a home address (resident/temporary), a home character tag, a child terminal network type, and an old man terminal network type; the user family extensible data tag may include family type judgment (family-like/family), family membership judgment, authentication credential repository and processing functions (authentication credential repository and processing function, ARPF), broadband number in family unit, terminal type in family unit, general intelligent terminal type in family unit, and general intelligent terminal number in family unit.

It should be noted that, the labels in the management account label library may be divided into resource class labels and relationship class labels. The resource class labels are used for labeling the resources under the management account. The main labels of the resource class labels are a member label, a privilege label, a rights label (i.e. the authority of the management account), a payment label, a Z-value label, a user star label (i.e. the level of the management account), and the like. The resource class labels are used for carrying out resource calling class division, resource class division and operation value class division of users, and the data support is provided for service and sales upgrading by combining the operator primary service and the ecological cooperation class service.

The relationship type labels are used for labeling construction of composition relationships, social relationships and application relationships of users under management accounts. The main labels of the relationship class labels are family relationships, friends and relatives (i.e. the friends and relatives of the management account), friends circles, common application relationships (i.e. the third party application of the management account authorization), non-operation shop relationships and the like. Information such as interpersonal network construction, touch border construction, daily life preference construction and the like of the user is carried out through tagging, and data support is provided for touch and user conversion of the user by combining operator camping business and ecological service business.

The embodiment of the application provides an account management method, breaks through the limitation of taking numbers as cores in the traditional method, and provides an account management operation system architecture taking users as cores. Based on the unified pass of the user management account system as the base access capability, establishing multi-dimensional and multi-application seamless connection between the person and the ecological platform; and constructing a management account resource scheduling system through the Z value, breaking application barriers and resource barriers among ecological partners, so as to realize value aggregation of multilateral ecology and free circulation exchange of production elements and product elements among multiple applications in an ecological circle, realize seamless connection of demands and smooth information among consumers, operators and ecological partners, and realize cross-domain, cross-boundary and cross-time ecological operation. Specifically, a management account system using an identity card number as a unique identifier is established, the complex steps of repeated registration and repeated login of a user are avoided through unified authentication, unified authentication and unified authorization, and client service perception and service deep embedding are provided through non-perception and multi-system multi-service linkage marketing to the user. And the user basic information sharing under the multi-contact is realized by combining the resource endowment and complementary advantages of all the parties. The common cooperation mode of point-to-point, off-line and loose coupling is an internetwork ecological cooperation mode of deep embedding, real-time interaction and tight coupling.

The method can realize a more flexible consumption mode. Specifically, based on management account, the fusion of the operator home network product and the cross-regional non-operator product is built, the combination mode and the operation mode of the product are enriched, the practicability and the high value of the product are provided, the marketing is assisted, the requirement of customers on the cross-border innovative product is met, and the customer experience is improved. Based on the sharing mode, the user experience is improved, the user interaction is promoted, the emotion of the user is increased, through the construction of family relations and relatives and friends, the sharing and communicating service is provided through the attributes such as privileges, Z values and rights and interests, the sharing, updating and emotion value improvement are carried out for the user, the service and assistance are carried out, the habit of the user is cultivated, and the viscosity of the user is improved. And the method can also integrate and collect resources by combining the capabilities of the partner such as privileges, Z values, rights and interests, and the like, construct a resource path, construct the inquiry and the call of non-operator resources, and provide more services and rights for users. Constructing a resource center through the Z value, opening up islands of each resource point, exchanging the equivalent value of the resources, constructing a resource network taking an operator as the center, integrating scattered resources to maximize the utilization of the resources, forming an ecological linkage trend, and constructing cross-domain, cross-boundary and cross-time combined service capability and marketing capability.

Through ecological operation, the limitation of the user labels of the traditional operators can be broken through, the ecological labels of the users are enriched and perfected, and more accurate big data energization is realized. Specifically, based on the data model and the code of the management account, the user information, the communication user information, the relations among the users, the user tag model, the user consumption information, the user family and relatives and friends network, the user points, rights and interests and other business and transaction data scattered in the headquarter and province systems are collected, synchronized, converted and integrated into the management account user database in real time, and the system has the capability of forming a unified view basis of the users so as to improve the service capability. The method uses the user management account as a core, enhances the construction of bottom data, establishes a complete, flexible and three-dimensional data tag system which is suitable for users, builds a user data model under multiple scenes, realizes one-point full view and image analysis of the full-volume business of the clients, innovates the application scene design, meets the consumption requirements of the clients, enables the full-volume clients, and maintains the improvement of value.

The foregoing description of the solution provided in the embodiments of the present application has been mainly presented in terms of a method. To achieve the above functions, it includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The embodiment of the application may divide functional modules according to the above method example for an account management method, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated in one processing module. The integrated modules may be implemented in hardware or in software functional modules. Optionally, the division of the modules in the embodiments of the present application is schematic, which is merely a logic function division, and other division manners may be actually implemented.

Fig. 26 is a schematic structural diagram of an account management device according to an embodiment of the present application. As shown in fig. 26, an account management apparatus 40 is used to improve the efficiency of managing user accounts, for example, to perform an account management method shown in fig. 3. The account management device 40 includes: an acquisition unit 401 and a processing unit 402;

an obtaining unit 401, configured to obtain identity information of a target user;

the processing unit 402 is configured to create a management account corresponding to the target user based on identity information of the target user, where the management account is used to manage multiple accounts corresponding to the target user on the account management platform, where the multiple accounts are accounts used to log in different application programs;

The obtaining unit 401 is further configured to obtain, based on the management account corresponding to the target user, basic information of the target user, where the basic information includes at least one of the following: account information, location information, parent information, consumption information, and point information;

the processing unit 402 is further configured to construct an information database corresponding to the target user;

the processing unit 402 is further configured to log in to the account management platform through a third party account based on the information database, where the third party account is an account corresponding to the third party application.

In one possible implementation, the management account has multiple accounts of different applications bound to it; the processing unit 402 is further configured to bind the first account with the management account to authorize the login of the account management platform through the first account, where the first account is an account for logging in a third party application, when the account management platform is logged in based on the management account corresponding to the target user; the processing unit 402 is further configured to unbind the second account from the management account when the account management platform is logged in based on the management account corresponding to the target user, so as to prohibit the account management platform from being logged in through the second account, where the second account is an account for logging in the third party application.

In a possible implementation manner, the processing unit 402 is further configured to perform, based on a management account corresponding to the target user, combined management on account information of the target user through a first preset model; the processing unit 402 is further configured to analyze, based on a management account corresponding to the target user, the location information of the target user through a second preset model, and determine a location track of the target user; the processing unit 402 is further configured to analyze, based on the management account corresponding to the target user, friend information of the target user through a third preset model, and determine a friend circle corresponding to the target user.

In a possible implementation manner, the processing unit 402 is further configured to determine a first parameter and a second parameter corresponding to the management account, where the first parameter is a parameter corresponding to the management account in the account management platform, and the second parameter is a parameter corresponding to the management account in the third party application program; the processing unit 402 is further configured to deduct the amount of consumption through the first parameter when the target user makes a purchase on the account management platform; the processing unit 402 is further configured to deduct the amount of the consumption by the second parameter when the target user makes a purchase in the third party application.

In a possible implementation manner, the processing unit 402 is further configured to create a plurality of labels for the management account, where the value of the management account is indicated by the plurality of labels, and any one of the plurality of labels is used to indicate any one of the following respectively: rights to manage an account, a level to manage an account, a relationship to manage an account, a third party application to manage an account authorization.

In the case of implementing the functions of the integrated modules in the form of hardware, another possible structural schematic diagram of the electronic device involved in the foregoing embodiment is provided in the embodiments of the present application. As shown in fig. 27, an electronic device 60 is provided for improving the efficiency of managing user accounts, for example, for performing an account management method as shown in fig. 3. The electronic device 60 comprises a processor 601, a memory 602 and a bus 603. The processor 601 and the memory 602 may be connected by a bus 603.

The processor 601 is a control center of the communication device, and may be one processor or a collective term of a plurality of processing elements. For example, the processor 601 may be a general-purpose central processing unit (central processing unit, CPU), or may be another general-purpose processor. Wherein the general purpose processor may be a microprocessor or any conventional processor or the like.

As one example, processor 601 may include one or more CPUs, such as CPU 0 and CPU 1 shown in fig. 27.

The memory 602 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), magnetic disk storage or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

As a possible implementation, the memory 602 may exist separately from the processor 601, and the memory 602 may be connected to the processor 601 through the bus 603 for storing instructions or program codes. The processor 601, when calling and executing instructions or program code stored in the memory 602, is capable of implementing an account management method provided in the embodiments of the present application.

In another possible implementation, the memory 602 may also be integrated with the processor 601.

Bus 603 may be an industry standard architecture (industry standard architecture, ISA) bus, a peripheral component interconnect (peripheral component interconnect, PCI) bus, or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 27, but not only one bus or one type of bus.

Note that the structure shown in fig. 27 does not constitute a limitation of the electronic apparatus 60. The electronic device 60 may include more or fewer components than shown in fig. 27, or may combine certain components or a different arrangement of components.

As an example, in connection with fig. 26, the acquisition unit 401 and the processing unit 402 in the electronic device realize the same functions as those of the processor 601 in fig. 27.

Optionally, as shown in fig. 27, the electronic device 60 provided in the embodiment of the present application may further include a communication interface 604.

Communication interface 604 for connecting with other devices via a communication network. The communication network may be an ethernet, a radio access network, a wireless local area network (wireless local area networks, WLAN), etc. The communication interface 604 may include a receiving unit for receiving data and a transmitting unit for transmitting data.

In one design, the electronic device provided in the embodiments of the present application may further include a communication interface integrated into the processor.

From the above description of embodiments, it will be apparent to those skilled in the art that the foregoing functional unit divisions are merely illustrative for convenience and brevity of description. In practical applications, the above-mentioned function allocation may be performed by different functional units, i.e. the internal structure of the device is divided into different functional units, as needed, to perform all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.

The embodiment of the application further provides a computer readable storage medium, in which instructions are stored, and when the computer executes the instructions, the computer executes each step in the method flow shown in the method embodiment.

Embodiments of the present application provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform an account management method as in the method embodiments described above.

The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: electrical connections having one or more wires, portable computer diskette, hard disk. Random access memory (random access memory, RAM), read-only memory (ROM), erasable programmable read-only memory (erasable programmable read only memory, EPROM), registers, hard disk, optical fiber, portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any other form of computer-readable storage medium suitable for use by a person or combination of the foregoing, or as a value in the art.

An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (application specific integrated circuit, ASIC).

In the context of the present application, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Since the electronic device, the computer readable storage medium, and the computer program product in the embodiments of the present application may be applied to the above-mentioned method, the technical effects that can be obtained by the electronic device, the computer readable storage medium, and the computer program product may also refer to the above-mentioned method embodiments, and the embodiments of the present application are not repeated herein.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application.

Claims

1. A method of account management, the method comprising:

acquiring identity information of a target user, and creating a management account corresponding to the target user based on the identity information of the target user, wherein the management account is used for managing a plurality of accounts corresponding to the target user on an account management platform, and the accounts are accounts for logging in different application programs;

acquiring basic information of the target user based on the management account corresponding to the target user, and constructing an information database corresponding to the target user, wherein the basic information comprises at least one of the following items: account information, location information, parent information, consumption information, and point information;

And under the condition of logging in the account management platform, logging in the account management platform through a third party account based on the information database, wherein the third party account is an account corresponding to a third party application program.

2. The method of claim 1, wherein the management account has a plurality of account numbers of different applications bound thereto, the method further comprising:

under the condition that a management account corresponding to the target user is logged in the account management platform, a first account number is bound with the management account so as to authorize the login of the account management platform through the first account number, wherein the first account number is an account number for logging in a third party application program;

or under the condition that the account management platform is logged in based on the management account corresponding to the target user, unbinding a second account number and the management account so as to prohibit the account management platform from being logged in through the second account number, wherein the second account number is an account number for logging in a third party application program.

3. The method according to claim 1 or 2, wherein the obtaining the basic information of the target user based on the management account corresponding to the target user, and constructing the information database corresponding to the target user, includes:

Based on the management account corresponding to the target user, carrying out combined management on account information of the target user through a first preset model;

analyzing the position information of the target user through a second preset model based on the management account corresponding to the target user, and determining the position track of the target user;

and analyzing the friendly information of the target user through a third preset model based on the management account corresponding to the target user, and determining the friendly ring corresponding to the target user.

4. The method according to claim 1 or 2, characterized in that the method further comprises:

determining a first parameter and a second parameter corresponding to the management account, wherein the first parameter is a parameter corresponding to the management account in the account management platform, and the second parameter is a parameter corresponding to the management account in a third party application program;

when the target user makes shopping on the account management platform, deducting the consumption amount through the first parameter;

and when the target user makes shopping in the third party application program, deducting the consumption amount through the second parameter.

5. The method according to claim 1 or 2, characterized in that the method further comprises:

Creating a plurality of labels for the management account, wherein the value of the management account is indicated by the labels, and any label in the plurality of labels is respectively used for indicating any one of the following: the authority of the management account, the grade of the management account, the relatives and friends of the management account and the third party application authorized by the management account.

6. An account management apparatus, the account management apparatus comprising: an acquisition unit and a processing unit;

the acquisition unit is used for acquiring the identity information of the target user;

the processing unit is used for creating a management account corresponding to the target user based on the identity information of the target user, wherein the management account is used for managing a plurality of accounts corresponding to the target user on an account management platform, and the accounts are accounts used for logging in different application programs;

the obtaining unit is further configured to obtain basic information of the target user based on a management account corresponding to the target user, where the basic information includes at least one of the following: account information, location information, parent information, consumption information, and point information;

the processing unit is also used for constructing an information database corresponding to the target user;

The processing unit is further configured to log in the account management platform through a third party account based on the information database under the condition of logging in the account management platform, where the third party account is an account corresponding to a third party application program.

7. The account management apparatus of claim 6, wherein the management account is bound with account numbers of a plurality of different applications;

the processing unit is further configured to bind a first account with the management account to authorize the login of the account management platform through the first account when the account management platform is logged in based on the management account corresponding to the target user, where the first account is an account for logging in a third party application;

and the processing unit is further configured to unbind a second account from the management account under the condition that the account management platform is logged in based on the management account corresponding to the target user, so as to prohibit the account management platform from being logged in through the second account, where the second account is an account for logging in a third party application program.

8. The account management device according to claim 6 or 7, wherein the processing unit is further configured to perform, based on a management account corresponding to the target user, combined management on account information of the target user through a first preset model;

The processing unit is further used for analyzing the position information of the target user through a second preset model based on the management account corresponding to the target user and determining the position track of the target user;

the processing unit is further configured to analyze, based on the management account corresponding to the target user, friend information of the target user through a third preset model, and determine a friend circle corresponding to the target user.

9. The account management apparatus according to claim 6 or 7, wherein the processing unit is further configured to determine a first parameter and a second parameter corresponding to the management account, where the first parameter is a parameter corresponding to the management account on the account management platform, and the second parameter is a parameter corresponding to the management account on a third party application;

the processing unit is further used for deducting the consumption amount through the first parameter when the target user makes shopping on the account management platform;

the processing unit is further configured to withhold the consumption amount through the second parameter when the target user makes a purchase in the third party application.

10. The account management apparatus according to claim 6 or 7, wherein the processing unit is further configured to create a plurality of labels for the management account, the value of the management account being indicated by the plurality of labels, any one of the plurality of labels being respectively used to indicate any one of: the authority of the management account, the grade of the management account, the relatives and friends of the management account and the third party application authorized by the management account.

11. An electronic device, comprising: a processor and a memory; wherein the memory is configured to store one or more programs, the one or more programs comprising computer-executable instructions that, when executed by the electronic device, cause the electronic device to perform an account management method of any of claims 1-5.

12. A computer readable storage medium storing one or more programs, wherein the one or more programs comprise instructions, which when executed by a computer, cause the computer to perform an account management method as claimed in any of claims 1-5.