WO2024139311A1 - User identifier processing method, apparatus and device, user information processing method, apparatus and device, and medium - Google Patents

Abstract

Embodiments of the present description disclose a user identifier processing method, apparatus and device, a user information processing method, apparatus and device, and a medium. A solution comprises: obtaining trigger information generated on the basis of a first preset operation of a user on a terminal; on the basis of the trigger information, generating a first user identifier suitable for a first application, wherein the terminal has a second user identifier suitable for a second application; and establishing a correspondence between the first user identifier and the second user identifier, so as to perform secure information exchange between different applications according to the correspondence.

Description

User identification and user information processing method, device, equipment and medium Technical Field

The present application relates to the field of computer technology, and in particular to a method, device, equipment and medium for processing user identification and user information.

Background technique

One of the key factors in improving people's life experience in the information age is the exchange of information. The digital transmission and sharing of information has greatly improved business efficiency and brought incremental value, such as personalized advertising, product and service recommendations, etc. Typical life scenarios include product recommendations and same-day delivery in online shopping, and one-stop service and online processing in digital government affairs. Since the information exchange process may be related to user privacy, there may be a risk of user data leakage. Therefore, how to protect personal information while continuing to achieve effective information exchange is a technical problem that needs to be solved urgently.

Summary of the invention

The embodiments of this specification provide a method, apparatus, device and medium for processing user identification and user information to improve the security of information interaction.

To solve the above technical problems, the embodiments of this specification are implemented as follows: A method for processing a user identifier provided in the embodiments of this specification includes: obtaining trigger information generated based on a first preset operation of a user on a terminal; based on the trigger information, generating a first user identifier suitable for a first application; the terminal has a second user identifier suitable for a second application; the first user identifier is different from the second user identifier; establishing a correspondence between the first user identifier and the second user identifier so as to perform security information interaction between different applications according to the correspondence.

A method for processing user information provided in an embodiment of the present specification includes: obtaining user information corresponding to a first user identifier; the first user identifier is a user identifier suitable for a first application; the first user identifier is generated based on a first preset operation of a user on a terminal; determining a second user identifier corresponding to a second application; the second user identifier is a user identifier suitable for a second application; and sending the user information and the second user identifier to the second application.

A user identification processing device provided in an embodiment of the present specification includes: a trigger acquisition module, used to obtain trigger information generated based on a first preset operation of a user on a terminal; an identification generation module, used to generate a first user identification suitable for a first application based on the trigger information; the terminal has a second user identification suitable for a second application; the first user identification is different from the second user identification; a relationship establishment module, used to establish a corresponding relationship between the first user identification and the second user identification, so as to perform security information interaction between different applications according to the corresponding relationship.

A user information processing device provided in an embodiment of the present specification includes: an information acquisition module, used to acquire user information corresponding to a first user identifier; the first user identifier is a user identifier suitable for a first application; the first user identifier is generated based on a first preset operation of a user on a terminal; an identifier determination module, used to determine a second user identifier corresponding to a second application; the second user identifier is a user identifier suitable for a second application; and an information sending module, used to send the user information and the second user identifier to the second application.

A user identification processing device provided in an embodiment of the present specification includes: at least one processor; and a memory connected to the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can The invention is capable of: obtaining trigger information generated based on a first preset operation of a user on a terminal; generating a first user identifier applicable to a first application based on the trigger information; the terminal has a second user identifier applicable to a second application; the first user identifier is different from the second user identifier; establishing a correspondence between the first user identifier and the second user identifier so as to perform security information interaction between different applications according to the correspondence.

A user information processing device provided in an embodiment of the present specification includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: obtain user information corresponding to a first user identifier; the first user identifier is a user identifier suitable for a first application; the first user identifier is generated based on a first preset operation of the user on the terminal; determine a second user identifier corresponding to a second application; the second user identifier is a user identifier suitable for a second application; and send the user information and the second user identifier to the second application.

An embodiment of the present specification provides a computer-readable medium on which computer-readable instructions are stored. The computer-readable instructions can be executed by a processor to implement a method for processing a user identification or a method for processing user information.

An embodiment of the present specification realizes the following beneficial effects: In the embodiment of the present specification, the terminal system can generate different user identifiers for different applications, and establish a correspondence between different user identifiers, so as to realize information interaction between different applications participated by the terminal system based on the correspondence. During the information interaction process, the terminal system can convert the user information corresponding to the first user identifier sent by the first application, and send the user information and the second user identifier to the second application, so as to realize information interaction between different applications. Since the correspondence between different user identifiers is managed by the terminal system, the first application and the second application cannot identify each other's user identifiers, so that even if information leakage occurs in the first application, illegal users cannot find the corresponding user information in the second application based on the first user identifier of the first application, thereby ensuring the security of information interaction.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of this specification, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a schematic diagram of an overall solution flow of a method for processing user information in an embodiment of this specification.

FIG. 2 is a flow chart of a method for processing a user identification provided in an embodiment of this specification.

FIG. 3 is a flow chart of a method for processing user information provided in an embodiment of this specification.

FIG. 4 is a swim-lane diagram of a method for processing a user identification and user information provided in an embodiment of this specification.

FIG. 5 is a schematic diagram of the structure of a user identification processing device corresponding to FIG. 2 provided in an embodiment of this specification.

FIG. 6 is a schematic diagram of the structure of a user identification processing device corresponding to FIG. 3 provided in an embodiment of this specification.

FIG. 7 is a schematic diagram of the structure of a device for processing user identification and user information provided in an embodiment of this specification.

Detailed ways

In order to make the purpose, technical solutions and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in this specification, ordinary technicians in this field can obtain the following without creative work. All other embodiments fall within the scope of protection of one or more embodiments of this specification.

The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

In order to more clearly explain the technical solutions provided by the embodiments of this specification, some terms are introduced first: Information exchange: It can refer to the information exchange between APP applications or systems for the same user. In an exchange interaction, there is usually a sender and a receiver of the information. User information is shared from the sender to the receiver.

Anchor point: It can represent the key connection point that the intercommunication system relies on. Through the anchor point information, the sender and receiver of the information can associate the information of multiple communications to the same subject.

Advertising ID: It can be used to represent the ID associated with a user by an APP developer in order to track the effectiveness of advertising. It is usually mapped one-to-one with the user's device, rather than the user itself. Usually, the user of multiple APPs on a device is the same user, so the advertising ID can be regarded as the user ID. For example, the IDFA of the Apple system and the ADID of the Android system.

At present, the common information exchange method mainly relies on an identifier to represent the same subject. For example, in scenarios such as one-account access and passes, the subject ID is used as an anchor to ensure that the two parties in communication are targeting the same subject. Among them, a user ID-based model is adopted, and different applications establish an intercommunication mechanism by identifying the same user account. For example, in scenarios such as cross-screen operations and APP recommendations, the device ID model is mainly used, including the advertising IDs of Apple and Android systems. Different applications identify the same device and infer that the user using different services on the device is the same, and then exchange information. For example, in the scenarios of automatic APP linkage and scene intelligence supported by mobile operating systems, it is mainly based on the device itself, and there is no need to explicitly identify the device ID. Different applications running on the same operating system can achieve intercommunication locally on the client.

The solutions in related technologies are essentially single-anchor, centralized systems, and intercommunication control and risk control are limited to a single system. Both parties can directly identify the user through the same anchor information, and associate all the user's intercommunication information and local information based on the anchor information. If any of the two parties is involved in information leakage, it will endanger the other party, and there are certain information security risks.

In order to solve the defects in the related art, the present solution provides the following embodiments: Figure 1 is a schematic diagram of the overall solution flow of a method for processing user information in an embodiment of this specification. As shown in Figure 1, the user can be a user in application 1 and application 2, the terminal system can be a system or system server of a terminal used by the user, and application 1 and application 2 can represent terminal clients that provide services to users, or servers that provide services to users. Among them, the terminal system can generate corresponding user identifiers for application 1 and application 2. Assuming that application 2 needs to obtain certain user information of the user in application 1, for example, the user's mobile phone number, the terminal system can obtain information sent by application 1 or server 1 containing user information and a first user identifier applicable to application 1. The first user identifier can be used by application 1 to find the user's information in application 1. The terminal system saves the correspondence between user identifiers corresponding to different applications. After obtaining the user information of the user in application 1, the terminal system can determine the second user identifier corresponding to application 2, and send the user information and the second user identifier to application 2, so that application 2 can obtain the user information of the user in application 1. In addition, the information sent by the terminal system to application 2 does not include the first user identifier of application 1, so that application 2 cannot obtain the user's information in application 1 based on the first user identifier. Even if information leakage is involved in application 2, it will not endanger application 1, which can improve the security of information.

Next, a method for processing a user identification and user information provided in an embodiment of the specification will be specifically described in conjunction with the accompanying drawings: Figure 2 is a flowchart of a method for processing a user identification provided in an embodiment of the specification. From a program perspective, the execution subject of the process can be a program or terminal system installed on a system server.

As shown in FIG. 2 , the process may include steps 202 to 206 .

Step 202: Acquire trigger information generated based on a first preset operation of the user on the terminal.

Step 204: Based on the trigger information, a first user identifier applicable to the first application is generated; the terminal has a second user identifier applicable to the second application; the first user identifier is different from the second user identifier.

In the embodiments of this specification, the terminal system can generate a corresponding user identifier for the application used by the user, and different user identifiers can be generated for different applications. Specifically, different user identifiers can be generated for different applications based on the user's operation on the terminal.

The terminal system can be a system running in the terminal used by the user, or it can be a system server corresponding to the terminal. The application can represent an application client in the terminal, or it can represent a server corresponding to the application client, or it can be a server corresponding to a business service when the user authorizes the use of the business service, or it can be a system application of the user to the terminal system, such as an application in the terminal settings. The first preset operation can be an operation of the user on the first application. In actual applications, the terminal system can obtain the user's operation information on the terminal and generate a user identifier based on the user operation.

Step 206: Establish a correspondence between the first user identifier and the second user identifier, so as to perform security information exchange between different applications according to the correspondence.

The terminal system can establish a correspondence between user identifiers corresponding to different applications. This correspondence can be managed or saved only by the terminal system. This correspondence does not exist in each application. In the process of information interaction, the user identifier corresponding to the information recipient is used to send information to the information recipient, thereby improving the security of information interaction.

Among them, the user identifier generated by the terminal system is an identifier used for information exchange between different applications. The user identifier is different from the application identifier used to manage the user's information in the application. The application identifier is an identifier generated by the server corresponding to the application to manage the information of the user using the application in the application, such as the user account, user UID, etc. For example, after a user registers as a user of a certain application, the server of the application can generate a UID corresponding to the user and associate the user's information in the application with the UID, such as the user's registration information, browsing information, transaction information, etc.

It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted.

In the method in FIG. 2 , the terminal system can generate different user identifiers for different applications and establish a correspondence between different user identifiers, so as to realize information interaction between different applications participated by the terminal system based on the correspondence. Since the correspondence between different user identifiers is managed by the terminal system, the first application and the second application cannot identify each other's user identifiers. In this way, even if information leakage occurs in the first application, an illegal user cannot find the corresponding user information in the second application based on the first user identifier of the first application, thereby ensuring the security of information interaction.

Based on the method of FIG. 2 , the examples of this specification also provide some specific implementation plans of the method, which are described below.

The user identification in the embodiments of this specification may be a character string randomly generated by the terminal system, or a character string generated according to the terminal identification of the terminal. Optionally, the generating of the first user identification applicable to the first application based on the trigger information in the embodiments of this specification may specifically include: obtaining the terminal identification of the terminal based on the trigger information; generating the first user identification applicable to the first application using a first preset algorithm based on the terminal identification.

The terminal identifier may be an identifier that uniquely represents the terminal, the terminal system, or the user of the terminal, such as the International Mobile Equipment Identity (IMEI) or the Mobile Equipment Identifier (MEID). The first preset algorithm may be an encryption algorithm, a hash algorithm, or a Algorithms, etc.

In actual applications, a preset algorithm can be used to calculate part or all of the characters in the terminal identifier to obtain the user identifier; a random string can also be added to the terminal identifier and then calculated using the preset algorithm. For different applications, the same algorithm or different algorithms can be used. The specific algorithm is not specifically limited here, as long as it can ensure that different user identifiers can be generated for different applications.

In actual applications, the terminal system server can also check the generated user IDs for duplication to avoid using duplicate user IDs. The terminal system server can save historical user IDs generated in a preset time period. When a new user ID is generated, it can be determined whether it is the same as the historical user ID. If it is the same, the user ID is regenerated until a user ID different from the historical user ID is generated.

In the embodiments of this specification, the terminal system may not have relevant information about the application identifier corresponding to the user, and the terminal system may send the generated user identifier to the corresponding application server, and the application server may save the correspondence between the application identifier of the user in the application and the user identifier, and then the application server may determine the information of the user corresponding to the application identifier in the application server according to the correspondence. Optionally, the method in the embodiments of this specification may also include: sending the first user identifier to the first application, so that the first application sends the user information to other applications based on the first user identifier; the first user identifier is different from the application identifier generated by the first application for managing the user information of the user in the first application.

In actual applications, the terminal system can send information to the application server based on the generated user identifier, and the application server can determine the corresponding application identifier based on the user identifier, and then obtain the user's information in the application server, and the application server can send the obtained information to the terminal system based on the user identifier. Assuming that the application server is the server of the first application, if the information obtained is information that needs to be sent to the second application, the terminal system can send the information to be sent to the second application in the name of the second user identifier. Similarly, the second application can also save the correspondence between the second user identifier and the second application identifier used to manage the user's information in the second application, and then the second application or the second application server can determine which user's information in this application the obtained information belongs to.

The first preset operation in the embodiment of the present specification may specifically include: at least one of an operation of enabling a recommended service in a terminal, an operation of installing a terminal application, an operation of accessing a terminal application, and an operation of logging into a terminal application.

The recommendation service may include an advertisement recommendation service. For example, when a user turns on the advertisement recommendation service in a terminal, the terminal system may generate a corresponding user identifier for each application participating in the advertisement recommendation service.

In actual applications, user identifiers may also be generated based on user operations on applications. For example, when a user downloads an application and installs it in a terminal, the terminal system may generate a user identifier for the application, or after the user opens and accesses the application or registers as a user of the application, a user identifier for the application may be generated.

In the embodiment of this specification, the corresponding relationship between the user identifiers can also be cancelled based on the user's operation, which can better meet the user's needs. Optionally, the method in the embodiment of this specification can also include: obtaining service termination information generated based on the user's second preset operation on the terminal; based on the service termination information, canceling the corresponding relationship between the first user identifier and the second user identifier.

The second preset operation may include at least one of an operation of shutting down a recommended service in the terminal, an operation of uninstalling a terminal application, and an operation of logging out of a terminal application.

In actual applications, the terminal system may also mark user identifiers that do not have a corresponding relationship as invalid identifiers.

For example, if a user does not want to receive advertising recommendations, he can turn off the advertising recommendation service, and the terminal system can cancel the participation The correspondence between user identifiers of the application of the advertising recommendation service. For another example, user A provides the terminal to user B for use, user A logs out of the terminal application, and user B can use his own information to log in to the terminal application. The terminal system can cancel the correspondence between the user identifiers previously generated for user A according to the operation of user A logging out of the terminal application, and can also generate a new user identifier according to user B's login. This can prevent user B from receiving information related to user A, for example, the recommendation information related to user A does not meet the needs of user B, causing disturbance to user B, and can also prevent user A's information from being leaked to user B, and can also improve the security of information. Based on the same idea, a method for processing user information is also provided in an embodiment of this specification, which can interact with user information based on the user identifier obtained by the above-mentioned user identifier management method. Figure 3 is a flow chart of a method for processing user information provided in an embodiment of this specification. From a program perspective, the execution subject of the process can be a program or terminal system mounted on a system server.

As shown in FIG. 3 , the method may include steps 302 to 306 .

Step 302: Obtain user information corresponding to a first user identifier; the first user identifier is a user identifier applicable to a first application; the first user identifier is generated based on a first preset operation of the user on the terminal.

In the embodiments of this specification, the user information may be sent by the first application, and the user information may be information related to the user generated by the user in the process of using the first application. Among them, the first application or the server of the first application may send information including the user information and the first user identifier to the terminal system. The first user identifier may be generated in the manner described in the above-mentioned method for processing the user identifier, which will not be described in detail here.

The first application here can refer to a terminal application client in a user terminal, or a server corresponding to the client; it can also refer to a system application that provides services based on a terminal system, or a server that provides services based on a terminal system. User information can be information related to the user stored in the terminal during the user's use of the first application, or it can be relevant information about the user stored in the server corresponding to the first application.

Step 304: Determine a second user identifier corresponding to the second application according to a preset corresponding relationship; the second user identifier is a user identifier suitable for the second application.

Similarly, the second application can represent an application client, a system application, or a corresponding server. In the embodiments of this specification, the second application can be the demander of user information, and the terminal system can store the corresponding relationship between the application identifiers of each application. After obtaining the user information, the user identifier corresponding to the second application can be determined, so that the user information can be sent to the second application as the user information corresponding to the second application.

Step 306: Send the user information and the second user identifier to the second application.

In the embodiments of the present specification, the terminal system can send the user information provided by the information provider to the information requester in the name of the user identifier of the information requester, thereby realizing multi-anchor information interaction and improving information security.

It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted.

Through the above method, during the information interaction process, the terminal system can convert the user information corresponding to the first user identifier sent by the first application, and send the user information and the second user identifier to the second application, thereby realizing information interaction between different applications. Since different user identifiers are managed by the terminal system, the first application and the second application cannot know each other's user identifiers, so even if information leakage occurs in the first application, illegal users cannot find the corresponding user information in the second application based on the first user identifier of the first application, thereby ensuring the security of information interaction.

Based on the method of FIG. 3 , the examples of this specification also provide some specific implementation plans of the method, which are described below.

The user information in the embodiments of this specification may be information fed back to the data demander based on the request after the data demander sends an information acquisition request; or it may be data actively pushed to the data demander by the data provider. As an implementation mode, before obtaining the user information corresponding to the first user identifier, the embodiments of this specification may also include: obtaining a first information acquisition request sent by the second application for obtaining the user information generated by the user in the first application; the first information acquisition request includes the second user identifier; according to the preset corresponding relationship, the first information acquisition request is converted into a user identifier to obtain a second information acquisition request for obtaining the user information generated by the user in the first application; the second information acquisition request includes the first user identifier; sending the second information acquisition request to the first application so that the first application obtains the user information of the user in the first application based on the first user identifier.

In the example of this specification, the terminal system can obtain the first information acquisition request containing the second user identifier sent by the second application, and then determine the first user identifier corresponding to the second user identifier and applicable to the first application based on the correspondence between the first user identifier and the second user identifier, and can perform a sign conversion on the first information acquisition request to obtain a second information acquisition request containing the first user identifier, and send it to the first application. The first application can obtain the user information generated by the user in the first application based on the received second information acquisition request, and feedback it to the terminal system based on the first user identifier. The terminal system can further change the first user identifier in the feedback information to the second user identifier, and send the user information to the second application based on the second user identifier.

Optionally, the first information acquisition request is subjected to user identification processing according to a preset correspondence to obtain a second information acquisition request for obtaining user information generated by the user in the first application, which may specifically include: determining the first user identification corresponding to the first application according to the preset correspondence; obtaining demand information in the first information acquisition request; the demand information can be used to represent information attributes of the user information requested to be obtained; and generating the second information acquisition request based on the demand information and the first user identification.

Among them, the terminal system can parse the first information acquisition request sent by the second application, obtain the demand information requested by the second application, and generate a second information acquisition request based on the determined demand information and the first user identifier and send it to the first application. The demand information can be used to represent the information attributes of the user information requested to be obtained. For example, the second application wants to obtain the mobile phone number of the user in the first application. The first information acquisition request can include information representing the information attributes of the mobile phone number. The terminal system can generate a second information request including the first user identifier and the information attribute to request the first application to obtain the mobile phone number corresponding to the first user identifier. In actual applications, user information can be regarded as the information attribute value corresponding to the information attribute, for example, the specific mobile phone number of the user obtained.

In the embodiments of this specification, the terminal system can also generate different identifiers for different applications based on the user's operation, and establish a correspondence between different identifiers so as to exchange information based on the correspondence. Optionally, before obtaining the user information corresponding to the first user identifier in the embodiments of this specification, it can also include: obtaining trigger information generated based on the user's first preset operation on the terminal; generating a first user identifier suitable for the first application based on the trigger information; the terminal has a second user identifier suitable for the second application; the first user identifier is different from the second user identifier; and establishing a correspondence between the first user identifier and the second user identifier.

The establishment of the corresponding relationship may be the same as that of the method for processing the user identification introduced above, and will not be repeated here.

Optionally, the method in the embodiment of this specification may further include: sending the first user identifier to the first application so that the first application sends user information to other applications based on the first user identifier; the first user identifier and the application identifier generated by the first application for managing the user information of the user in the first application different.

The first application may maintain a relationship between the first user identifier and the application identifier of the user in the first application, so that after obtaining information including the first user identifier, it can correspond to the user in the first application.

The user identifier generated by the terminal system in the embodiments of this specification may also be an identifier with a specific function. For example, for the scenario of an advertisement recommendation server, the generated user identifier may be an advertisement ID. Different applications may correspond to different advertisement IDs. The applications may communicate with each other according to a preset protocol. After receiving an information acquisition request containing an advertisement ID, the application may send specific user information determined according to a preset protocol. The preset protocol may be a user authorization protocol, an agreement for the user to agree to use recommendation services, and the like.

In actual applications, in order to further ensure the security of information interaction, the user information may be processed before being sent to the second application in the embodiments of this specification. Optionally, sending the user information and the second user identifier to the second application in the embodiments of this specification may specifically include: encrypting or desensitizing the user information to obtain processed user information; and sending the processed user information and the second user identifier to the second application.

The user information in the embodiments of this specification may be information related to user privacy, and may specifically include at least one of the user's browsing information, order information, and identity information. The identity information may include user account, mobile phone number, location information, network information used, terminal information, etc.

To more clearly illustrate the method provided in the embodiments of this specification, Figure 4 is a swim lane diagram of a method for processing a user identifier and user information provided in the embodiments of this specification. As shown in Figure 4, the method in the embodiments of this specification may include an identifier generation phase, an identifier relationship management phase, an information acquisition phase, an information processing phase, and an information sending phase, and may include steps 402 to 420.

Step 402: The terminal system obtains trigger information generated based on a first preset operation of the user on the terminal. For example, the user activates the advertisement recommendation service in the terminal, downloads, accesses or logs in to the terminal client, and the terminal system can obtain trigger information for generating a user identification.

Step 404: The terminal system may generate a first user identifier applicable to the first application according to the trigger information.

Step 406: The terminal system has a second user identifier suitable for a second application, and a corresponding relationship between the first user identifier and the second user identifier is established.

The second user identifier may be generated before or after the first user identifier is generated, which is not specifically limited here.

For example, when a user activates an advertisement recommendation service in a terminal, the second application may represent a recommendation server corresponding to the advertisement recommendation service, and the first application may be a terminal client or a server of a client that the user has used and that participates in the advertisement recommendation service. In actual applications, the second application may also be a terminal client or a server of a client that the user has used and that participates in the advertisement recommendation service, and the first application and the second application may obtain user information owned by the other party.

For another example, in a scenario where user-authorized information is used, such as authorizing a second application to use information in a first application to log in or register the second application, the first application and the second application may be a terminal client used by the user or a server of the client.

The following is an example of using a user's mobile phone number in a first terminal application to log in and register a second terminal application. Assuming that a user registers as a user of the first terminal application, the first terminal application server can generate an application identifier ID1 for the user in the first terminal application based on the user's registration information, such as mobile phone number, email account, etc. This identifier is used by the first terminal application or server to manage the user's related information in the first terminal application; After the user accesses the second terminal application or downloads the first terminal application or opens the first terminal application, the terminal system will generate a user identification ID-A for the user for information interaction; the terminal system can also send the user identification ID-A to the first terminal application or server, so that the first terminal application or server knows that the user identification ID-A and the application identification ID1 of the user in the first terminal application are the same user; assuming that the user has not registered and used the second terminal application before, similarly, when the user downloads or opens the second terminal application, the terminal system can generate a user identification ID-B suitable for the second terminal application and establish a corresponding relationship between the user identification ID-A and ID-B. The terminal system can determine the user identifications with corresponding relationships as the same user.

In the process of information interaction, information interaction can be performed based on the corresponding relationship managed in the terminal system. Specifically, the process may include: Step 408: the second application may generate a first information acquisition request based on the user's operation on the second application. The first information acquisition request includes a second user identifier.

For example, when a user wants to register or log in to a second application using an account of a first application, a selection control that can be selected by the user may be included in the registration or login page of the second application. If the user selects the control, it may indicate that the user authorizes the second application to obtain certain information in the first application. The operation for the second application may be an operation of registering or logging in to the second application after the user authorizes it. Based on the operation, the second application may generate a first information acquisition request for obtaining the user information generated by the user in the first application.

Step 410: The terminal system may obtain the first information acquisition request sent by the second application.

Step 412: The terminal system performs user identification processing on the first information acquisition request according to the previously generated correspondence, obtains a second information acquisition request for acquiring user information generated by the user in the first application, and sends it to the first application.

Step 414: The first application may obtain the second information acquisition request, and may also obtain information generated by the user in the first application based on the second information acquisition request, and send the first user identifier and user information to the terminal system.

Step 416: The terminal system obtains user information corresponding to the first user identifier.

Step 418: The terminal system may determine the second user identifier corresponding to the second application according to the corresponding relationship, and generate information including the user information and the second user identifier, and may also send the information to the second application.

Step 420: The second application may obtain information including the second user identification and user information.

Continuing with the above example, assuming that the user authorizes the second application to obtain the user information of the user in the first application, the terminal system can initiate a request to the first application, and the request includes the user identifier ID-A; after the first application receives the request, it can determine based on the user identifier ID-A that it needs to obtain the account information of the user with the application identifier ID1 in the first application, such as the mobile phone number, and then the user information and the user identifier ID-A can be sent to the terminal system, so that the terminal system knows that the user information is the information of the user with the user identifier ID-A.

The terminal system can send the acquired account information of the user and user identifier ID-B to the second application; the second application can complete the user's registration or login based on the received account information, and the second application can also generate an application identifier ID2 for the user in the second application; the second application manages the correspondence between the user identifier ID-B and the application identifier ID2, which can indicate that the two identifiers correspond to the same user.

Subsequently, assuming that the second application needs to recommend content of interest to the user based on the user's browsing information, purchase information, etc. in the first application, the first application can send the user information carrying the user identifier ID-A to the terminal system; the terminal system can replace the user identifier ID-A with the user identifier ID-B, and can also desensitize the user information and generate information carrying the desensitized user information of the user identifier ID-B, and send the information to the second application.

The second application can determine that the user information is the application identifier ID2 of the second application according to the interactive identity identifier ID-B. For a user, the recommended information determined according to the user information can also be recommended to the user.

In actual applications, if the first application can actively push information to the second application, the second application may not generate an information acquisition request, and steps 408 to 412 in FIG. 4 may be omitted.

Based on the same idea, the embodiments of this specification also provide a device corresponding to the above-mentioned user identification processing method. Figure 5 is a schematic diagram of the structure of a user identification processing device corresponding to Figure 2 provided in the embodiments of this specification. As shown in Figure 5, the device may include: a trigger acquisition module 502, used to obtain trigger information generated based on a first preset operation of the user on the terminal; an identification generation module 504, used to generate a first user identification suitable for a first application based on the trigger information; the terminal has a second user identification suitable for a second application; wherein the first user identification is different from the second user identification; a relationship establishment module 506, used to establish a corresponding relationship between the first user identification and the second user identification, so as to perform security information interaction between different applications according to the corresponding relationship.

Based on the same idea, the embodiments of this specification also provide a device corresponding to the above-mentioned user information processing method. Figure 6 is a structural diagram of a user identification processing device corresponding to Figure 3 provided in the embodiments of this specification. As shown in Figure 6, the device may include: an information acquisition module 602, used to obtain user information corresponding to a first user identification; the first user identification is a user identification suitable for a first application; the first user identification is generated based on a first preset operation of the user on the terminal; an identification determination module 604, used to determine a second user identification corresponding to a second application; the second user identification is a user identification suitable for a second application; an information sending module 606, used to send the user information and the second user identification to the second application.

Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

FIG7 is a schematic diagram of the structure of a user identification and user information processing device provided in an embodiment of this specification. As shown in FIG7, the device 700 may include: at least one processor 710; and a memory 730 connected to the at least one processor in communication; wherein the memory 730 stores instructions 720 executable by the at least one processor 710; corresponding to the user identification processing method shown in FIG2 in the embodiment of this specification, the instructions are executed by the at least one processor 710 so that the at least one processor 710 can: obtain trigger information generated based on a first preset operation of the user on the terminal; based on the trigger information, generate a first user identification applicable to the first application; the terminal has a second user identification applicable to the second application; the first user identification is different from the second user identification; establish a corresponding relationship between the first user identification and the second user identification, so as to perform security information interaction between different applications according to the corresponding relationship.

Corresponding to the user information processing method shown in Figure 3 of the embodiment of this specification, the instruction is executed by the at least one processor 710 so that the at least one processor 710 can: obtain user information corresponding to a first user identifier; the first user identifier is a user identifier suitable for a first application; the first user identifier is generated based on a first preset operation of the user on the terminal; determine a second user identifier corresponding to a second application; the second user identifier is a user identifier suitable for a second application; and send the user information and the second user identifier to the second application.

Based on the same idea, the embodiment of this specification also provides a computer-readable medium corresponding to the above method. The computer-readable medium stores computer-readable instructions, which can be executed by a processor to implement the above method for processing user identification and user information.

Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the device shown in FIG7, since it is basically similar to the method embodiment, the description is relatively simple. Please refer to the partial description of the method embodiment.

In the 1990s, it was very clear whether the improvement of a technology was hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or software improvement (improvement of the method flow). However, with the development of technology, many of the improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with hardware entity modules. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing programs. The original code before compilation must also be written in a specific programming language, which is called Hardware Description Language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., and the most commonly used ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that realizes the logic method flow.

The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer readable medium storing a computer readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that in addition to implementing the controller in a purely computer readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the means for implementing various functions included therein may also be considered as a structure within the hardware component. Or even, the means for implementing various functions may be considered as both a software module for implementing the method and a structure within the hardware component.

The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For the convenience of description, the above device is described in terms of functions and is divided into various units and described separately. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and/or hardware.

Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

The present application is described with reference to the flowchart and/or block diagram of the method, device (system) and computer program product according to the embodiment of the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, and the combination of the process and/or box in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

In a typical configuration, a computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in a computer-readable medium, in the form of random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

The above is an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims (18)

A method for processing a user identification, applied to a terminal system, comprising: Acquire trigger information generated based on a first preset operation of the user on the terminal; Based on the trigger information, a first user identifier applicable to the first application is generated; the terminal has a second user identifier applicable to the second application; A correspondence between the first user identifier and the second user identifier is established so as to perform security information interaction between different applications according to the correspondence. According to the method of claim 1, generating a first user identifier applicable to the first application based on the trigger information comprises: Based on the trigger information, obtaining a terminal identification of the terminal; Based on the terminal identifier, a first user identifier suitable for a first application is generated using a first preset algorithm. The method according to claim 1, further comprising: The first user identifier is sent to the first application so that the first application sends user information to other applications based on the first user identifier; the first user identifier is different from an application identifier generated by the first application for managing user information of the user in the first application. According to the method according to claim 1, the first preset operation specifically includes: at least one of an operation of enabling a recommended service in a terminal, an operation of installing a terminal application, an operation of accessing a terminal application, and an operation of logging into a terminal application. The method according to claim 1, further comprising: Acquire service termination information generated based on a second preset operation of the user on the terminal; Based on the service termination information, the correspondence between the first user identifier and the second user identifier is released. According to the method of claim 5, the second preset operation includes at least one of an operation of shutting down a recommended service in the terminal, an operation of uninstalling a terminal application, and an operation of logging out of a terminal application. A method for processing user information, the method being applied to a terminal system, comprising: Acquire user information corresponding to a first user identifier; the first user identifier is a user identifier applicable to a first application; the first user identifier is generated based on a first preset operation of the user on the terminal; Determine, according to the preset corresponding relationship, a second user identifier corresponding to the second application; the second user identifier is a user identifier applicable to the second application; The user information and the second user identifier are sent to the second application. The method according to claim 7, Before obtaining the user information corresponding to the first user identifier, the method further includes: Obtaining a first information acquisition request sent by the second application for acquiring user information generated by the user in the first application; the first information acquisition request includes the second user identifier; According to the preset corresponding relationship, the first information acquisition request is processed with a user identifier to obtain a second information acquisition request for obtaining user information generated by the user in the first application; the second information acquisition request includes the first user identifier; The second information acquisition request is sent to the first application, so that the first application acquires the user information of the user in the first application based on the first user identifier. The method according to claim 8, wherein the first information acquisition request is sent according to a preset corresponding relationship. The request for performing user identification processing to obtain a second information acquisition request for acquiring user information generated by the user in the first application includes: Determining the first user identifier corresponding to the first application according to the preset corresponding relationship; Obtaining the demand information in the first information acquisition request; the demand information is used to indicate the information attribute of the user information requested to be obtained; Based on the demand information and the first user identifier, the second information acquisition request is generated. The method according to claim 7, Before obtaining the user information corresponding to the first user identifier, the method further includes: Acquire trigger information generated based on a first preset operation of the user on the terminal; Based on the trigger information, a first user identifier applicable to a first application is generated; the terminal has a second user identifier applicable to a second application; the first user identifier is different from the second user identifier; A correspondence between the first user identifier and the second user identifier is established. The method according to claim 10, further comprising: The first user identifier is sent to the first application so that the first application sends user information to other applications based on the first user identifier; the first user identifier is different from an application identifier generated by the first application for managing user information of the user in the first application. According to the method of claim 7, sending the user information and the second user identifier to the second application comprises: Encrypting or desensitizing the user information to obtain processed user information; The processed user information and the second user identifier are sent to the second application. According to the method of claim 7, the user information includes at least one of the user's browsing information, order information, and identity information. A user identification processing device, comprising: A trigger acquisition module, used to acquire trigger information generated based on a first preset operation of a user on a terminal; an identification generating module, configured to generate a first user identification applicable to a first application based on the trigger information; the terminal has a second user identification applicable to a second application; The relationship establishing module is used to establish a corresponding relationship between the first user identifier and the second user identifier so as to perform security information interaction between different applications according to the corresponding relationship. A user information processing device, comprising: An information acquisition module, used to acquire user information corresponding to a first user identifier; the first user identifier is a user identifier applicable to a first application; the first user identifier is generated based on a first preset operation of the user on the terminal; An identification determination module, used to determine a second user identification corresponding to the second application; the second user identification is a user identification applicable to the second application; An information sending module is used to send the user information and the second user identifier to the second application. A user identification processing device, comprising: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Acquire trigger information generated based on a first preset operation of the user on the terminal; Based on the trigger information, a first user identifier applicable to the first application is generated; the terminal has a second user identifier applicable to the second application; A correspondence between the first user identifier and the second user identifier is established so as to perform security information interaction between different applications according to the correspondence. A user information processing device, comprising: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Acquire user information corresponding to a first user identifier; the first user identifier is a user identifier applicable to a first application; the first user identifier is generated based on a first preset operation of the user on the terminal; Determine a second user identifier corresponding to the second application; the second user identifier is a user identifier applicable to the second application; The user information and the second user identifier are sent to the second application. A computer-readable medium having computer-readable instructions stored thereon, wherein the computer-readable instructions can be executed by a processor to implement the method for processing a user identification as described in any one of claims 1 to 6 or the method for processing user information as described in any one of claims 7 to 13.