A user information management method and related device

Abstract

The present application provides a user information management method and related devices, which can be used in the field of data processing. The method includes: a user center receives first information from an application server, and determines whether the user is a user in the first application based on the first login number of the user to be registered in the second application in the first information. If no user has become a user in the first application using the first login number in the first information, the user to be registered is registered as a user of the user center according to the first login number, and the user to be registered is registered as a user of the first application. In the technical solution of the present application, the user can log in and access the first application according to the first login number, which can realize cross-platform user diversion, and then realize user information sharing, user management and user communication between platforms.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a method and related device for managing user information. Background Art

[0002] The group's internal ecosystem may include one or more application software (APP), and at least one APP in the group's internal ecosystem can exchange users with multiple third-party APPs, thereby achieving cross-platform user traffic.

[0003] Currently, those skilled in the art have proposed a method for realizing user exchange between an APP in a group's ecosystem and a third-party APP. That is, when a user needs to access an APP in the group's ecosystem, he or she can use the user's login credentials in the third-party APP to log in to the APP in the group's ecosystem with the user's authorization.

[0004] However, this field does not further specify how to provide users with services of APPs in the group's ecosystem based on the user's login credentials in the third-party APP when the user authorizes the service.

[0005] Therefore, how to provide users with the services of APPs in the group's ecosystem based on their login credentials in third-party APPs has become a technical problem that needs to be solved urgently. Summary of the Invention

[0006] The present application provides a user information management method and related devices to solve the problem of how to provide users with APP services in the group's ecosystem based on the user's login credentials in a third-party APP.

[0007] In a first aspect, the present application provides a method for managing user information, including: a user center receives first information from an application server, the first information requests registration of a user in a first application based on user information in a second application, and the user information includes a first login number of the user to be registered in the second application, identification information of the first application, and identification information of the second application, the application server is a back-end server of the first application, and the second application is a third-party application of the first application; the user center determines whether a user has registered as a user of the user center using the first login number; if no user has registered as a user of the user center using the first login number, the user center registers the user to be registered as a user of the user center based on the first login number, and registers the user to be registered as a user of the first application.

[0008] The user center determines whether the user corresponding to the first login number is a user of the user center based on the first login number. When the user corresponding to the first login number is not a user of the user center, the user is registered as a user of the user center and a user of the first application, so that the user can access the first application according to the first login number.

[0009] In combination with the method described in the first aspect, the user center determines whether a user has registered as a user of the user center using the first login number, including: the user center determines whether there is first user login element information with the login number being the first login number in the historical user login element information database; if so, it is determined that a user has registered as a user of the user center using the first login number; if not, it is determined that no user has registered as a user of the user center using the first login number.

[0010] The user center judges the first login number based on the historical user login element information database to determine whether the user corresponding to the first login number is a user of the user center. Only when the user corresponding to the first login number is a user of the user center, the user is allowed to use the first login number to access the user center.

[0011] In combination with the method described in the first aspect, the method also includes: when a user has already used the first login number to register as a user of the user center, the user center determines whether a user has already used the first login number to register as a user of the first application; when no user has used the first login number to register as a user of the first application, the user registers the user to be registered as a user of the first application.

[0012] The user center can determine whether the user corresponding to the first login number is a user of the first application by judging the first login number. Only when the user corresponding to the first login number is a user of the first application, the user is allowed to access the user center using the first login number.

[0013] In this method, the user center determines whether a user has registered as a user of the first application using the first login number, including: the user center determines whether there is a first ecological user registration information in the historical ecological user registration information library whose user number is the first user number in the first user login element information, and each ecological user registration information in the historical ecological user registration information library includes the ecological platform user number, ecological number, authentication type, user number and service contract number; if it exists, it is determined that a user has registered as a user of the first application using the first login number; if it does not exist, it is determined that no user has registered as a user of the first application using the first login number.

[0014] The first user number in the first user login element information is compared with the user number in the historical ecological user registration information database. Only when the first user number exists in the user number in the historical ecological user registration information database, the user corresponding to the first user number is determined to be the user of the first application, and the user is allowed to log in and access the first application.

[0015] In combination with the method described in the first aspect, the method also includes: when a user has already registered as a user of the first application using the first login number, the user center determines whether a user has already registered as a user of the first application using the first login number in the second application; when no user has registered as a user of the first application using the first login number in the second application, the user center generates record information, and the record information indicates that a user has already registered as a user of the first application using the first login number in the second application.

[0016] The user center will only generate record information if the user has not used the first login number in the second application to register as a user of the first application. This can ensure that when the user uses the first login number to register as a user of the first application, duplication and redundancy of the record information can be avoided, thereby avoiding waste of storage resources.

[0017] In this method, the user center determines whether a user has registered as a user of the first application using the first login number in the second application, including: the user center determines whether there is first user exchange information in the historical user exchange information library whose ecological platform user number is the same as the first ecological platform user number in the first ecological user registration information, and each user exchange information in the historical user exchange information library includes the ecological platform user number, source channel, source user number, source real-name information, service contract number and source login number; if so, it is determined that a user has registered as a user of the first application using the first login number in the second application; if not, it is determined that no user has registered as a user of the first application using the first login number in the second application.

[0018] When the user center generates a joint membership for the first application and the second application, the first user exchange information and the first ecological user registration information corresponding to the first application will be generated. The first user exchange information and the first ecological user registration information corresponding to the first application are associated through the ecological platform user number. According to the ecological platform user number, it can be determined whether there is a user who uses the first login number in the second application to register as a user of the first application.

[0019] Optionally, the method also includes: the user center receives second information from the application server, the second information is used to indicate that the login number of the user whose login number is the first login number in the second application has been changed; and the first user exchange information is deleted based on the second information.

[0020] After the user's login number in the second application is changed, the first user exchange information is deleted, and the user cannot continue to log in and access the first application according to the first login number.

[0021] In this method, the user information also includes the first real-name authentication information of the user in the second application; accordingly, before the user center determines whether a user has registered as a user of the first application using the first login number, the method also includes: determining whether the real-name authentication information in the basic information of the first user whose user number is the first user number is the same as the first real-name authentication information; if the real-name authentication information in the first user basic information is different from the first real-name authentication information, a prompt message is sent to the application server, and the prompt message is used to indicate that the real-name authentication information in the first user basic information is different from the first real-name authentication information.

[0022] The user center can also associate user information based on real-name authentication information, so that when the user changes the login number, only the user's login element needs to be changed. The user can also access the first application based on the changed login element.

[0023] In the second aspect, the present application provides a user information management device, including: a receiving module, a judgment module and a registration module. The receiving module is used for the user center to receive the first information from the application server, the first information requesting to register the user in the first application based on the user information in the second application, and the user information includes the first login number of the user to be registered in the second application, the identification information of the first application and the identification information of the second application, the application server is the backend server of the first application, and the second application is a third-party application of the first application; the judgment module is used for the user center to determine whether a user has registered as a user of the user center using the first login number; the registration module is used for the user center to register the user to be registered as a user of the user center based on the first login number, and to register the user to be registered as a user of the first application when no user has registered as a user of the user center using the first login number.

[0024] In addition, the judgment module is also used to determine whether there is first user login element information with the login number being the first login number in the historical user login element information database; the judgment module is also used to determine whether a user has registered as a user of the first application using the first login number, and the judgment module is also used by the user center to determine whether there is first ecological user registration information with the user number being the first user number in the first user login element information in the historical ecological user registration information database; the judgment module is also used to determine whether the real-name authentication information in the basic information of the first user with the user number being the first user number is the same as the first real-name authentication information.

[0025] The receiving module is further configured to receive second information from the application server, where the second information is configured to indicate that the login number of the user whose login number is the first login number in the second application has been changed.

[0026] In a third aspect, the present application provides a user information management device, which may include various functional modules for implementing the method of the first aspect. For example, the device may include a memory and a processor coupled to the memory.

[0027] The processor is used to execute program instructions to implement the instructions executed by the method in the first aspect; the memory is used to store the instructions executed by the processor or the input data required by the processor to run the instructions or the data generated after the processor runs the instructions.

[0028] In a fourth aspect, the present application provides a computer-readable storage medium, which stores a program code for execution by a processor, wherein the program code includes instructions for implementing the method in the first aspect.

[0029] In a fifth aspect, the present application provides a computer program product, which, when executed on a processor, enables a user information management device to implement the method in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0031] Figure 1 A schematic diagram of a user exchange scenario applicable to an embodiment of the present application;

[0032] Figure 2 A schematic diagram of the user exchange system architecture according to an embodiment of the present application;

[0033] Figure 3This is a flowchart of a method for registering a user as a user of an APP in a group's ecosystem using the user information of the user in a third-party APP according to one embodiment of the present application;

[0034] Figure 4 A flowchart of a method for registering as a user of an APP in a group's ecosystem based on user information input by a user, provided in one embodiment of the present application;

[0035] Figure 5 A schematic diagram of a user information management device provided in one embodiment of the present application;

[0036] Figure 6 A schematic diagram of a user information management device provided in another embodiment of the present application.

[0037] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0038] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0039] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data involved comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0040] The following is an explanation of the terms involved in this application:

[0041] Intra-group ecological platform: includes one or more apps and the server of each app, and these apps and servers belong to the same legal entity group.

[0042] Third-party APP: refers to an APP that belongs to a different legal entity group than the above-mentioned ecological platform within the group.

[0043] Joint Membership Agreement: This is a joint agreement signed by the group's ecological platform and the platform to which the third-party APP belongs. When this joint agreement exists between the group's ecological platform and the platform to which the third-party APP belongs, users can access the APP in the group's ecology through the third-party APP, or they can access the third-party APP through the APP in the group's ecology.

[0044] Figure 1 This is a schematic diagram of a user exchange scenario applicable to the embodiment of the present application. Figure 1 As shown, the terminal device may include APP1 and APP2. APP1 is an APP within the group's ecosystem, and APP2 is a third-party APP. The terminal device can be a smartphone, tablet, or personal computer. APP1 and APP2 have signed a joint agreement.

[0045] In some example scenarios, an access interface of APP1 is provided in the user interface of APP2, and a user can access APP1 through the access interface.

[0046] For example, if a user needs to log in to APP1 but has not yet registered in APP1, the user can authorize the terminal device to log in to APP1 using the user's login credentials in APP2.

[0047] In response to the technical problem of how to log in to APP1 based on the user's login credentials in APP2 in the above exemplary scenario, this application proposes a corresponding technical solution.

[0048] Figure 2 This is a schematic diagram of the user exchange system architecture of an embodiment of the present application. Figure 2 As shown, the user exchange system may include: a terminal device, a user center and an internal ecological server of the group. The user center and the internal ecological server of the group are computing devices with computing capabilities.

[0049] APP1 and APP2 are deployed on the terminal device. APP1 and APP2 have signed a joint agreement.

[0050] The group's internal ecological server is the backend server of APP1. Terminal devices can communicate with the group's internal ecological server, and the group's internal ecological server can communicate with the user center.

[0051] The following combination Figure 3 This application introduces the technical solution proposed by this application to register users as users of APPs in the group's ecosystem through their user information in third-party APPs. Figure 3 As shown, the method may include S301, S302, S303, S304, S305, S306 and S307.

[0052] S301, the user center receives first information from the application server, where the first information is used to request registration of a user in the first application based on user information in the second application, and the user information includes the first login number of the user to be registered in the second application, identification information of the first application, and identification information of the second application. The application server is the backend server of the first application, and the second application is a third-party application of the first application.

[0053] The user center can be Figure 2 In the user center of the system architecture shown, the application server can be Figure 2 In the group's internal ecological server in the system architecture shown, the first application can be Figure 2 The second application can be APP1 shown in Figure 2 APP2 shown in .

[0054] As an example, the first login number may include the first user's login number in the second application (eg, a mobile phone number).

[0055] For example, the user Figure 2 By clicking the access interface of APP1 in the first user interface of APP2 of the terminal device shown, the terminal device can send a first message to the ecological server within the group. The first login number in the first message includes the login number of the first user in the second application.

[0056] For example, users need to log in Figure 2 If the terminal device has APP1 but has not yet registered as a user of APP1, or the user has logged into APP2 but does not want to enter APP1's login information in APP1, the user can authorize APP2 to use the user's user information in APP2 as the login information for APP1. In this case, the terminal device can send a first message to the ecological server within the group, where the first message includes the user's first login number in the second application, the identifier of the first application, and the identifier of the second application.

[0057] S302: The user center determines whether a user has registered as a user of the user center using the first login number. If yes, S304 is executed; if no, S303 is executed.

[0058] In other words, the user center determines whether there is information in the user center recording that the first login number has been registered in the user center.

[0059] As an example, one implementation method for the user center to determine whether a user has registered as the first user of the user center using the first login number includes: the user center determines whether there is first user login element information with the login number being the first login number in the historical user login element information database; if so, it can be determined that a user has registered in the user center using the first login number; if not, it can be determined that no user has registered in the user center using the first login number.

[0060] The historical user login element information database includes one or more user login element information, wherein each user login element information is user login element information generated before this step, and each user login element information includes a login number and a user number.

[0061] The user ID is the user's ID in the user center. Optionally, the user login element information may also include the login type. The login type indicates whether the user logged in through the group's internal ecological app or a third-party app.

[0062] S303: The user center registers the user to be registered as a user of the user center based on the first login number.

[0063] In other words, the user center generates information to record that the user to be registered is a user of the user center.

[0064] An implementation method for the user center to register the user to be registered as a user of the user center based on the first login number includes: the user center generates a first user number based on the first login number, and generates first user login element information based on the first login number and the first user number, the user number in the first user login element information is the first user number, and the login number in the first user login element information is the first login number.

[0065] Optionally, the user center registering the user to be registered as a user of the user center based on the first login number may further include: the user center generating a first user number for the user to be registered based on the first login number, and generating first user basic information based on the first user number, wherein the first user basic information includes a user number, lifecycle status, real-name authentication information, and other information, and the user number in the first user basic information is the first user number. Other information may include information such as age, gender, or address. The real-name authentication information and other information in the first user basic information may be empty.

[0066] S304: The user center determines whether a user has registered as a user of the first application using the first login number. If not, S305 is executed; if yes, S306 is executed.

[0067] In other words, the user center determines whether there is an information record in the user center and whether the first login number has registered a user in the first application.

[0068] As an example, one implementation method for the user center to determine whether a user has registered as a user of the first application using the first login number includes: the user center determines whether there is a first ecological user registration information in the historical ecological user registration information database with the user number being the first user number in the first user login element information, where each ecological user registration information in the historical ecological user registration information database includes the ecological platform user number, ecological number, authentication type, user number, and service contract number. If so, it can be determined that a user has registered as a user of the first application using the first login number; if not, it can be determined that no user has registered as a user of the first application using the first login number.

[0069] Among them, the ecological platform user number is the user's identifier in the first application; the ecological number is used to represent the first application; the authentication type is used to indicate whether the user has been authenticated; and the service contract status is used to indicate whether the user is a normal user or a logged-out user.

[0070] S305: The user center registers the user to be registered as a user of the first application.

[0071] In other words, the user center generates information to record that the user to be registered is a user of the first application, and associates the information with the first user login element information and the user's first user basic information, which includes user number, life cycle status, real-name information and other information.

[0072] As an example, the user center generates first ecological user registration information, which includes the ecological platform user ID, ecological ID, authentication type, user ID, and service contract number. The user ID in the first ecological user registration information is the first user ID in the first user login element information. Accordingly, the user ID in the first user's basic information is the first user ID.

[0073] S306: The user center determines whether a user has registered as a user of the first application using the first login number in the second application. If not, execute S307.

[0074] One implementation method for the user center to determine whether a user has registered as a user of the first application using the first login number in the second application includes: the user center determines whether there is a first user exchange information in the historical user exchange information library with an ecological platform user number that is the same as the first ecological platform user number in the first ecological user registration information, and each user exchange information in the historical user exchange information library includes the ecological platform user number, source channel, source user number, source real-name information, service contract number and source login number.

[0075] Among them, the source channel is used to indicate which third-party APP the access comes from; the source user number indicates the user's user number in the third-party APP, the source real-name information is used to indicate the user's real-name information in the third-party APP, and the source login number is the user's login number in the third-party APP; the service contract number is used to indicate the identifier of the first user in the second application in the user center.

[0076] If there is first user exchange information in the historical user exchange information database whose ecological platform user number is the same as the first ecological platform user number in the first ecological user registration information, it is determined that a user has registered as a user of the first application using the first login number in the second application; otherwise, it is determined that no user has registered as a user of the first application using the first login number in the second application.

[0077] S307: The user center records that a user has registered as a user of the first application using the first login number in the second application.

[0078] For example, the user center generates the first user exchange information.

[0079] In the embodiment of the present application, optionally, the first information may also include the user's first real-name authentication information in the second application.

[0080] In this case, the real-name authentication information in the first user basic information generated for the user to be registered in S303 is the first real-name authentication information.

[0081] In this case, in S304, before the user center determines whether a user has registered as a user of the first application using the first login number, the user center can first determine whether the real-name authentication information in the user basic information associated with the user who has registered using the first login number is the same as the first real-name authentication information. If they are the same, S304 is executed. If they are not the same, a prompt message can be sent to the application server. The prompt message is used to prompt that the first real-name authentication information is inconsistent with the real-name authentication information associated with the first login number.

[0082] In this way, the application server can send the first prompt information to the terminal device, and the terminal device can input the first prompt information to the user.

[0083] In this embodiment, the user center registers the user in the first application based on the user information of the user in the second application, which can be understood as: the user center generates a joint membership for the first application and the second application.

[0084] In this embodiment, when the user center creates a joint membership for the first application and the second application, it generates first user exchange information corresponding to the first application and first ecological platform registration information corresponding to the second application. The first user exchange information and the first ecological platform registration information are linked via the ecological platform user number. Therefore, the user service data of the first user in the first application and the user service data of the first user in the second application can be linked via the first ecological platform registration information and the first user exchange information.

[0085] Furthermore, the first user's service data in the first application is associated only with the first ecological platform registration information, and the first user's service data in the second application is associated only with the first user's exchange information. This ensures that the user service data of the joint member in the second application and the user service data of the joint member in the first application do not affect each other. For example, if a user cancels their joint membership, they only need to cancel the association between the first user's exchange information and the first ecological platform registration information, without affecting the first user's service data in the first application.

[0086] In addition, in this embodiment, before generating the first ecological platform registration information, it is first determined whether the first ecological platform registration information already exists. This can avoid duplication and redundancy of the ecological platform registration information when the first user has already generated the first ecological platform registration information through user registration through any APP in the group's ecology, thereby avoiding waste of storage resources; or it can avoid duplication and redundancy of the ecological platform registration information when the first user has already generated the first ecological platform registration information during joint membership registration in other scenarios, thereby avoiding waste of storage resources.

[0087] In addition, in this embodiment, before generating the first user exchange information, it is first determined whether the first user exchange information already exists. This can avoid duplication and redundancy of user exchange information when the first user has already registered as a joint member of the third-party APP and other APPs in the group's ecology and has generated the first ecological platform registration information, thereby avoiding waste of storage resources.

[0088] At the same time, in this embodiment, before generating the basic information of the first user, it is first determined whether the basic information of the first user already exists. This can avoid duplication and redundancy of registration information on the ecological platform when the first user has already generated the basic information of the first user through user registration through any APP in the group's ecosystem, thereby avoiding waste of storage resources; or it can avoid duplication and redundancy of user basic information when the first user has already generated the basic information of the first user during joint membership registration in other scenarios, thereby avoiding waste of storage resources.

[0089] Optionally, after the user center registers the first user as a joint member, it can send the first user's service contract number to the group's internal ecological server. The group's internal ecological server sends the service contract number to the terminal device, and the terminal device records the service contract number in the relevant information of the second application. In this way, when the first user accesses the first application from the second application, they can use the service contract number as the login number, or they can use the first user's login number in the second application as the login number to log in to the first application.

[0090] In this embodiment, after the first user registers to become a joint member, when directly accessing the ecological server within the group in the first application, the first user can log in using the login number entered when registering as a joint member.

[0091] In this embodiment, after the first user registers to become a joint member, when accessing the ecological server within the group through the access interface in the second application, he can log in using the login number entered by the first user when registering as a joint member or use the login number or service contract number of the first user in the second application to log in.

[0092] In this embodiment, optionally, after a user changes their login number (mobile phone number) on a third-party platform, according to the joint membership agreement, if the association is only through the login number (mobile phone number), the joint membership will be cancelled after the login number is changed. This does not affect the user data of the ecological platform within the group. If the association is based on real-name, it is equivalent to only changing the login elements, and it does not affect the joint membership and user exchange.

[0093] The following combination Figure 4 This article introduces how to register as a user of an APP in the group's ecosystem based on the user information entered by the user. Figure 4 As shown, the method includes S401, S402, S403, S404, S405, S406, S407 and S408.

[0094] S401, the user center receives the second information from the application server, the second information is used to request to register a user for the first application, and the second information includes the identification information of the first application and the second login number and second real-name authentication information of the user to be registered. The application server is the back-end server of the first application.

[0095] The user center can be Figure 2 In the user center of the system architecture shown, the application server can be Figure 2 The group's internal ecological server in the system architecture shown.

[0096] As an example, the second login number may include a mobile phone number entered by the user in the user interface of the first application and used as a login account.

[0097] For example, the user Figure 2 After entering the login number (eg, mobile phone number) in the registration user interface of APP1 of the terminal device and clicking the registration button, the terminal device sends the second information to the ecological server within the group.

[0098] S402: The user center determines whether a user has registered as a user of the user center using the second login number. If not, S403 is executed; if so, S404 is executed.

[0099] In other words, the user center determines whether there is information in the user center recording that the second login number has been registered in the user center.

[0100] As an example, one implementation method for the user center to determine whether a user has registered as the first user of the user center using the second login number includes: the user center determines whether there is second user login element information with the login number of the second login number in the historical user login element information database; if so, it can be determined that a user has registered in the user center using the second login number; if not, it can be determined that no user has registered in the user center using the second login number.

[0101] The historical user login element information database includes one or more user login element information, wherein each user login element information is user login element information generated before this step, and each user login element information includes a login number and a user number.

[0102] The user ID is the user's ID in the user center. Optionally, the user login element information may also include the login type. The login type indicates whether the user logged in through the group's internal ecological app or a third-party app.

[0103] S403: The user center registers the user to be registered as a user of the user center based on the second login number.

[0104] In other words, the user center generates information to record that the user to be registered is a user of the user center.

[0105] An implementation method in which the user center registers the user to be registered as a user of the user center based on the second login number includes: the user center generates a second user number based on the second login number, and generates second user login element information based on the second login number and the second user number, the user number in the second user login element information is the second user number, and the login number in the second user login element information is the second login number.

[0106] Optionally, the user center registers the user to be registered as a user of the user center based on the second login number, and may also include: the user center generates a second user number for the user to be registered based on the second login number, and generates second user basic information based on the second user number, the second user basic information includes the user number, life cycle status, real-name information and other information, and the user number in the second user basic information is the second user number, and the real-name authentication information in the second user basic information is the second real-name authentication information.

[0107] Other information may include information such as age, gender or address.

[0108] S404, the user center determines whether the real-name authentication information in the basic information of the second user whose user number is the second login number is the same as the second real-name authentication information, if they are the same, execute S405, otherwise execute S407.

[0109] S405: The user center determines whether a user has registered as a user of the first application using the second login number. If not, S406 is executed; if yes, S408 is executed.

[0110] In other words, the user center determines whether there is an information record in the user center and whether the second login number has been used to register a user in the first application.

[0111] As an example, one implementation method for the user center to determine whether a user has registered as a user of the first application using the second login number includes: the user center determines whether there is a second ecological user registration information in the historical ecological user registration information database with the user number being the second user number in the second user login element information, where each ecological user registration information in the historical ecological user registration information database includes the ecological platform user number, ecological number, authentication type, user number, and service contract number. If so, it can be determined that a user has registered as a user of the first application using the second login number; if not, it can be determined that no user has registered as a user of the first application using the second login number.

[0112] Among them, the ecological platform user number is the user's identifier in the first application; the ecological number is used to represent the first APP; the authentication type is used to indicate whether the user has been authenticated; and the service contract status is used to indicate whether the user is a normal user or a logged-out user.

[0113] S406: The user center registers the user to be registered as a user of the first application.

[0114] In other words, the user center generates information to record that the user to be registered is a user of the first application, and associates the information with the second user login element information and the second user basic information of the user, the user basic information including user number, life cycle status, real name information and other information.

[0115] As an example, the user center generates second-user ecological registration information, which includes the ecological platform user ID, ecological ID, authentication type, user ID, and service contract number. The user ID in the second-user ecological registration information is the second user ID in the second user login element information. Accordingly, the user ID in the second user basic information is the second user ID.

[0116] S407: The user center sends a first prompt message to the application server, where the first prompt message is used to prompt that the second real-name authentication information is inconsistent with the real-name authentication information associated with the second login number.

[0117] In this way, the application server can send the first prompt information to the terminal device, and the terminal device can input the first prompt information to the user.

[0118] S408: The user center sends a second prompt message to the application server. The second prompt message is used to remind the user that he has registered the first application using the second login number.

[0119] In this way, the application server can send the second prompt information to the terminal device, and the terminal device can input the second prompt information to the user.

[0120] It is understandable that the embodiments of the present application may include more or fewer steps, for example, S407 and S408 may not be included.

[0121] User Center Execution Figure 4 After the operations included in the method, it can be understood that the first user has completed the registration in the user center and has become a registered user of the first application.

[0122] In the technical solution of the present application, the user center can generate joint memberships for the group's ecological APP and third-party APP, so that users can directly access the group's ecological APP from the access interface of the third-party APP through the user's registered joint membership identity information, or use the user's registered joint membership identity information as the login information of the group's ecological APP, thereby realizing cross-platform user diversion.

[0123] In the technical solution of the present application, when the user center generates joint members for the ecological APP within the group and the third-party APP, it generates user exchange information of the ecological APP within the group and the ecological platform registration information of the third-party APP respectively. The user exchange information and the ecological platform registration information both include the ecological platform user number. The two can be linked according to the ecological platform user number, thereby realizing user information sharing, user management and user communication between the ecological APP within the group and the third-party APP.

[0124] In the technical solution of the present application, before generating the user's ecological platform registration information, user exchange information and user basic information, the user center first determines whether the user has this information. When the user does not exist, the user center generates the corresponding information, which can avoid the waste of storage resources.

[0125] Figure 5 A schematic diagram of a user information management device provided in one embodiment of the present application is shown as follows: Figure 5 As shown, the user information management device 500 may include a receiving module 501 , a judging module 502 and a registration module 503 .

[0126] As an example, the user information management device 500 can be used to implement the following Figure 3 The method flow diagram of the embodiment shown is as follows: wherein the receiving module 501 can be used to execute step S301; the judging module 502 can be used to execute steps S302, S304 and S306; and the registering module 503 can be used to execute steps S303 and S305.

[0127] As another example, the user information management device 500 can be used to implement the following Figure 4The method flow diagram of the embodiment shown is as follows: wherein the receiving module 501 can be used to execute step S401; the judging module 502 can be used to execute steps S402, S404 and S405; and the registering module 503 can be used to execute steps S403 and S406.

[0128] Optionally, the user information management device 500 may further include a sending module 504 , which may be used to execute steps S407 and S408 .

[0129] Figure 6 A schematic diagram of a user information management device provided in another embodiment of the present application is shown as follows: Figure 6 As shown, the user information management device 600 may include a processor 601 and an interface circuit 602. The processor 601 and the interface circuit 602 are coupled to each other. It is understood that the interface circuit 602 may be a transceiver or an input / output interface.

[0130] Optionally, the user switching device 600 may further include a memory 603 for storing instructions executed by the processor 601 or storing input data required by the processor 601 to run instructions or storing data generated after the processor 601 runs instructions.

[0131] As an example, the processor 601 is used to implement the functions of the above-mentioned determination module 502 and registration module 503 , and the interface circuit 602 is used to implement the functions of the above-mentioned receiving module 501 and sending module 504 .

[0132] It is understood that the processor in the embodiments of the present application may be a central processing unit, or may be other general-purpose processors, digital signal processors, application-specific integrated circuits, field programmable gate arrays or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0133] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a read-only compact disc (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC). In addition, the application specific integrated circuit can be located in a network device or a terminal device. Of course, the processor and the storage medium can also be present in a network device or a terminal device as discrete components.

[0134] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive.

[0135] In the various embodiments of the present application, unless otherwise specified or logically conflicting, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships. The term "multiple" herein refers to two or more. The term "and / or" herein is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " herein generally indicates that the previous and next associated objects are in an "or" relationship; in a formula, the character " / " indicates that the previous and next associated objects are in a "division" relationship.

[0136] It will be understood that the various numerical numbers involved in the embodiments of the present application are merely distinctions for the convenience of description and are not intended to limit the scope of the embodiments of the present application.

[0137] It will be appreciated that, in the embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution, and the order of execution of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. Those skilled in the art will easily think of other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary technical means in the art that are not disclosed in the present application. The specification and embodiments are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the claims below.

[0138] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for managing user information, characterized in that: include: The user center receives first information from an application server, the first information requesting registration of a user in the first application based on user information in the second application, wherein the user information includes a first login number of the user to be registered in the second application, identification information of the first application, and identification information of the second application, the application server being a backend server of the first application, and the second application being a third-party application of the first application; The user center determines whether a user has registered as a user of the user center using the first login number; If no user has registered as a user of the user center using the first login number, the user center registers the user to be registered as a user of the user center based on the first login number, and registers the user to be registered as a user of the first application; If a user has registered as a user of the user center using the first login number, the user center determines whether a user has registered as a user of the first application using the first login number; If a user has registered as a user of the first application using the first login number, the user center determines whether a user has registered as a user of the first application using the first login number in the second application; If no user has registered as a user of the first application using the first login number in the second application, the user center generates record information, which indicates that a user has registered as a user of the first application using the first login number in the second application.

2. The method according to claim 1, characterized in that The user center determines whether a user has registered as a user of the user center using the first login number, including: The user center determines whether there is first user login element information with the login number of the first login number in the historical user login element information database; If so, it is determined that a user has registered as a user of the user center using the first login number; If not, it is determined that no user has used the first login number to register as a user of the user center.

3. The method according to claim 2, characterized in that The method further comprises: If no user has registered as a user of the first application using the first login number, the user registers the user to be registered as a user of the first application.

4. The method according to claim 3, characterized in that The user center determines whether a user has registered as a user of the first application using the first login number, including: The user center determines whether there is a first ecological user registration information with a user number equal to the first user number in the first user login element information in the historical ecological user registration information database, where each ecological user registration information in the historical ecological user registration information database includes an ecological platform user number, an ecological number, an authentication type, a user number, and a service contract number; If so, it is determined that a user has registered as a user of the first application using the first login number; If not, it is determined that no user has registered as a user of the first application using the first login number.

5. The method according to claim 4, characterized in that The user center determines whether a user has registered as a user of the first application using the first login number in the second application, including: The user center determines whether there is a first user exchange information in the historical user exchange information database with an ecological platform user number identical to the first ecological platform user number in the first ecological user registration information, where each user exchange information in the historical user exchange information database includes the ecological platform user number, source channel, source user number, source real-name information, service contract number, and source login number; If so, it is determined that a user has registered as a user of the first application using the first login number in the second application; If not, it is determined that no user has used the first login number in the second application to register as a user of the first application.

6. The method according to claim 5, characterized in that The method further comprises: The user center receives second information from the application server, where the second information is used to indicate that the login number of the user whose login number is the first login number in the second application has been changed; The first user exchange information is deleted based on the second information.

7. The method according to any one of claims 3 to 6, characterized in that The user information also includes the user's first real-name authentication information in the second application; Accordingly, before the user center determines whether a user has registered as a user of the first application using the first login number, the method further includes: Determining whether the real-name authentication information in the basic information of a first user whose user number is the first user number is the same as the first real-name authentication information; When the real-name authentication information in the first user basic information is different from the first real-name authentication information, a prompt message is sent to the application server, where the prompt message is used to indicate that the real-name authentication information in the first user basic information is different from the first real-name authentication information.

8. A user information management device, characterized in that: include: a receiving module, configured to receive, at a user center, first information from an application server, the first information requesting registration of a user in a first application based on user information in a second application, the user information including a first login number of the user to be registered in the second application, identification information of the first application, and identification information of the second application, the application server being a backend server of the first application, and the second application being a third-party application of the first application; A judgment module, configured for the user center to judge whether a user has registered as a user of the user center using the first login number; a registration module, configured to, if no user has registered as a user of the user center using the first login number, register the user to be registered as a user of the user center based on the first login number, and register the user to be registered as a user of the first application; The determination module is further configured to, when a user has registered as a user of the user center using the first login number, determine by the user center whether a user has registered as a user of the first application using the first login number; If a user has registered as a user of the first application using the first login number, the user center determines whether a user has registered as a user of the first application using the first login number in the second application; If no user has registered as a user of the first application using the first login number in the second application, the user center generates record information, which indicates that a user has registered as a user of the first application using the first login number in the second application.

9. A user information management device, characterized in that: include: including a memory, and a processor coupled to the memory; The memory is used to store program instructions; The processor is configured to execute the program instructions to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores program codes for computer execution, wherein the program codes include codes for implementing the method according to any one of claims 1 to 7.

11. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 7 when being executed by a processor.

Images