METHOD, EQUIPMENT, DEVICE AND MEDIUM FOR MARKING ACQUISITION

Abstract

The invention relates to a method, a device, a mechanism, and a medium for identification acquisition. If the identity token carried by the main application client in the received authentication request has been successfully authenticated, the application management terminal sends a first user identification registered in the main application client by a target user corresponding to the user information carried by the authentication request to the main application client. The first user identification and the identity token can then be sent by the main application client to the micro application client, so that the micro application client can send a identification acquisition request containing the first user identification and the identity token to a micro application client.When the identity token in the tag acquisition request is successfully authenticated, the application management terminal acquires the second user tag corresponding to the first user tag in the micro-application client and sends the second user tag to the micro-application client to realize the user system interoperability of the main application and the micro-application, so that the data sharing between the main application and the micro-application can be realized based on the interoperated user system.

Description

FIELD OF THE INVENTION

[0001] The present invention relates to the field of computer technology and, more particularly, to a method, apparatus, device and medium for tag acquisition. BACKGROUND OF THE INVENTION

[0002] As a technical means that can aggregate multiple independent applications and provide a unified gateway for accessing these multiple applications, micro-frontends are increasingly used in the software development process. Among these, the application that provides a unified gateway can be referred to as the master application, and any independent application integrated into the master application can be used as a slave application.

[0003] In related technologies, the data between the master application and the slave applications, as well as between the slave applications, is isolated from each other and this data cannot be shared, which makes it impossible to perform comprehensive data analysis of the data of the master applications and the slave applications. SUMMARY OF THE INVENTION

[0004] The present invention provides a method, apparatus, device, and medium for tag acquisition to overcome the deficiencies in related technologies.

[0005] According to a first aspect of the present invention, a method for acquiring a label executed by an application management terminal is provided. The method comprises: in response to receiving the authentication request from the main application client, sending a first user identifier corresponding to the user information carried by the authentication request to the main application client if the identity token carried by the authentication request has been successfully authenticated, wherein the first user identifier represents a user identifier registered by a target user corresponding to the user information in the main application client, wherein the main application client is used to send the first user identifier and the identity token to the micro application client upon receiving the first user identifier, wherein the micro-application client is used to send a tag acquisition request to the main application management terminal based on the first user tag and the identity token; in response to receiving the label acquisition request from the micro-application client, acquiring a second user label corresponding to the first user label entrained by the label acquisition request if the identity token entrained by the label acquisition request has been successfully authenticated, wherein the second user label represents a user label registered by the target user in the micro-application client; Send the second user identifier to the micro-application client.

[0006] In the present invention, upon receiving the authentication request from the main application client, the application management terminal sends to the main application client a first user identifier registered in the main application client by a target user corresponding to the user information carried by the authentication request, if the identity token carried by the authentication request has been successfully authenticated, so that upon receiving the first user identifier, the main application client sends the first user identifier and the identity token to the micro application client, whereby the micro application client can send a identifier acquisition request including the first user identifier and the identity token to a micro application client;Upon receiving the tag acquisition request, the application management terminal acquires the second user tag corresponding to the first user tag in the micro-application client, and sends the second user tag to the micro-application client when the identity token is successfully authenticated, so as to realize the interoperability of the user system between the main application and the micro-application, so that data sharing between the main application and the micro-application can be realized based on the interoperated user system.

[0007] In some embodiments, the identity token comprises at least signature information; the step of, in response to receiving the authentication request from the main application client, sending a first user identifier corresponding to the user information carried by the authentication request to the main application client if the identity token carried by the authentication request has been authenticated, comprises: in response to receiving an authentication request from the main application client, authenticating the identity token based on the signature information contained in the identity token; Acquiring the first user identifier based on the user information carried by the authentication request if the signature information has been successfully authenticated; Sending the first user identification to the main application client.

[0008] In some embodiments, the method further comprises, prior to the step of, in response to receiving the authentication request from the main application client, sending a first user identifier corresponding to the user information carried by the authentication request to the main application client if the identity token carried by the authentication request has been authenticated, at least one of the following steps: in response to receiving an application registration request from the main application client, generating a main application identifier and a main application key for the main application client and sending the main application identifier and the main application key to the main application client in response to receiving an application registration request from the micro-application client, generating a micro-application identifier and a micro-application key for the micro-application client and sending the micro-application identifier and the micro-application key to the micro-application client.

[0009] In some embodiments, the method further comprises, prior to the step of, in response to receiving the authentication request from the main application client, sending a first user identifier corresponding to the user information carried by the authentication request to the main application client if the identity token carried by the authentication request has been authenticated, at least one of the following steps: in response to receiving a first application verification request from the main application client, checking the validity of the main application client based on the main application identifier and the main application key carried by the first application verification request; Send the identity token to the main application client if the main application client's validity check is successful; otherwise, send a notice to the main application client that is used to indicate that the main application client's validity check failed.

[0010] In some embodiments, after the step of sending the identity token to the main application client if the validity check of the main application client is successful, the method further comprises: in response to receiving a second application verification request from the micro-application client, verifying the usage rights of the main application client against the micro-application client based on the micro-application identifier, micro-application key, main application identifier, and identity token entailed by the second application verification request; Sending usage permission information to the micro-application client if it is confirmed that the main application client has the permission to use the micro-application client; otherwise, sending usage prohibition information to the micro-application client.

[0011] In some embodiments, the method further comprises, prior to the step of, in response to receiving a second application verification request from the micro-application client, verifying the usage rights of the main application client against the micro-application client based on the micro-application identifier, micro-application key, main application identifier, and identity token entailed by the second application verification request: in response to receiving an authorization acquisition request from the main application client, setting the authorization information of the main application client such that it has the authorization to use the micro application client.

[0012] According to a second aspect of the present invention, a method for tag acquisition executed by the main application client is provided. The method comprises: Sending an authentication request to an application management terminal, the authentication request including an identity token and user information, the application management terminal being used to acquire a first user identifier corresponding to the user information if authentication of the identity token is successful, the first user identifier representing a user identifier registered by a target user corresponding to the user information in the main application client;

[0013] Sending the first user identifier to the micro-application client when the first user identifier has been received, wherein the micro-application client is used to send a identifier acquisition request to the application management terminal upon receipt of the first user identifier, the identifier acquisition request taking the identity token and the first user identifier, wherein the identifier acquisition request is used to acquire the user identifier registered in the micro-application client by the target user.

[0014] In the present invention, an authentication request including an identity token and user information is sent by the main application client to the application management terminal, so that when the authentication of the identity token is successful, the application management terminal acquires a first user identifier already registered in the main application client by a target user corresponding to the user information, so that the first user identifier is returned to the main application client;then, upon receipt of the first user identifier by the main application client, the first user identifier and the identity token can be sent to the micro-application client, so that upon receipt of the first user identifier by the micro-application client, a identifier acquisition request including the first user identifier and the identity token is sent to the application management terminal, whereby the identifier acquisition request acquires the user identifier already registered by the target user in the micro-application client to realize the interoperability of the user system for the main application and the micro-application, so that data sharing between the main application and the micro-application can be realized based on the interoperated user system.

[0015] In some embodiments, the method further comprises, prior to the step of sending the authentication request to the application management terminal: sending an application registration request to the application management terminal, wherein the application management terminal is used to generate a master application identifier and a master application key for the master application client in response to the application registration request; Receive the main application label and main application key returned from the application management terminal.

[0016] In some embodiments, the method further comprises, prior to the step of sending the authentication request to the application management terminal: sending a first application verification request to the application management terminal, wherein the first application verification request brings the main application identifier and the main application key, wherein the application management terminal is used to verify the validity of the main application client based on the main application identifier and the main application key and to send an identity token to the main application client if the validity check of the main application client is successful.

[0017] In some embodiments, after the step of sending the first application verification request to the application management terminal, the method further comprises: Sending the main application identifier and the identity token to the micro-application client when the identity token is received, wherein the micro-application client is used to send a second authentication request including a micro-application identifier, a micro-application key, a main application identifier, and an identity token to the main application management terminal, wherein the main application management terminal is used to verify the usage rights of the main application client against the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier, and the identity token, and return the verification result to the micro-application client.

[0018] In some embodiments, the method further comprises, prior to the step of sending the authentication request to the application management terminal: sending an authorization acquisition request to the application management terminal, wherein the application management terminal is used to, in response to the authorization acquisition request, set the authorization information of the main application client so that it has the authorization to use the micro application client.

[0019] According to a third aspect of the present invention, a method for tag acquisition executed by a microapplication client is provided. The method comprises: Receiving a first user identifier sent from the main application client, the first user identifier representing a user identifier registered by a target user in the main application client; Sending a label acquisition request with an identity token and the first user label to the application management terminal, wherein the label acquisition request is used to acquire a second user label registered by the target user in the micro-application client; Receiving the second user identifier sent from the application management terminal.

[0020] In the present invention, the micro-application client receives the first user identifier sent from the main application client and registered by the target user in the main application client, and thus sends a identifier acquisition request including the identity token and the first user identifier to the application management terminal, so that the second user identifier already registered by the target user in the micro-application client is acquired through the identifier acquisition request to realize the interoperability of the user system for the main application and the micro-application, so that data sharing by the main application and the micro-application can be realized based on the interoperated user system.

[0021] In some embodiments, the method further comprises, prior to the step of receiving a first user identifier sent from the main application client: Sending an application registration request to the application management terminal, wherein the application management terminal is used to generate a micro-application identifier and a micro-application key for the micro-application client in response to the application registration request; Receive the micro-application identifier and micro-application key returned from the application management terminal.

[0022] In some embodiments, the method further comprises, prior to the step of receiving a first user identifier sent from the main application client: in response to receiving the main application identifier and the identity token of the main application client, sending a second application verification request to the application management terminal, the second application verification request bringing the micro-application identifier, the micro-application key, the main application identifier, and the identity token, wherein the application management terminal is used to verify the usage rights of the main application client to the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier, and the identity token, and return the verification result to the micro-application client.

[0023] According to a fourth aspect of the present invention, a label acquisition device is provided that is applied to the application management terminal. This device comprises: a sending module used to send a first user identifier corresponding to the user information carried by the authentication request to the main application client in response to receiving the authentication request from the main application client if the identity token carried by the authentication request has been successfully authenticated, wherein the first user identifier represents a user identifier registered by a target user corresponding to the user information in the main application client, wherein the main application client is used to, upon receiving the first user identifier, send the first user identifier and send the identity token to the micro-application client, wherein the micro-application client is used to send a tag acquisition request to the main application management terminal based on the first user tag and the identity token; an acquisition module used to acquire, in response to receiving the label acquisition request from the micro-application client, a second user label corresponding to the first user label entrained by the label acquisition request if the identity token entrained by the label acquisition request has been successfully authenticated, wherein the second user label represents a user label registered by the target user in the micro-application client; wherein the sending module is further used to send the second user identifier to the micro-application client.

[0024] In some embodiments, the identity token comprises at least signature information; If, in response to receiving the authentication request from the main application client, a first user identifier corresponding to the user information carried by the authentication request is sent to the main application client, if the identity token carried by the authentication request has been authenticated, the sending module is used to: in response to receiving the authentication request from the main application client, authenticate the identity token based on the signature information contained in the identity token; to acquire the first user identifier based on the user information carried by the authentication request if the signature information has been successfully authenticated; to send the first user identification to the main application client.

[0025] In some embodiments, the device further comprises: a generation module used to generate a main application identifier and a main application key for the main application client in response to receiving an application registration request from the main application client; wherein the generation module is further used to generate a micro-application identifier and a micro-application key for the micro-application client in response to receiving an application registration request from the micro-application client.

[0026] In some embodiments, the device further comprises: Verification module used to, in response to receiving a first application verification request from the main application client, check the validity of the main application client based on the main application identifier and the main application key carried by the first application verification request; wherein the sending module is also used to send the identity token to the main application client if the validity check of the main application client is successful, otherwise, to send an indication information to the main application client which is used to indicate that the validity check of the main application client has failed.

[0027] In some embodiments, the verification module is also used to, in response to receiving a second application verification request from the micro-application client, verify the usage rights of the main application client against the micro-application client based on the micro-application identifier, micro-application key, main application identifier, and identity token entrained by the second application verification request; wherein the sending module is also used to send usage permission information to the micro application client when it is confirmed that the main application client has permission to use the micro application client, otherwise, to send usage prohibition information to the micro application client.

[0028] In some embodiments, the device further comprises: a setting module used to set the authorization information of the main application client so that it has the authorization to use the micro application client in response to receiving the authorization acquisition request from the main application client.

[0029] According to a fifth aspect of the present invention, a label acquisition device is provided that is applied to a main application client. This device comprises: a sending module used to send an authentication request to an application management terminal, the authentication request entailing an identity token and user information, the application management terminal being used to acquire a first user identifier corresponding to the user information if the authentication of the identity token is successful, the first user identifier representing a user identifier registered by a target user corresponding to the user information in the main application client; wherein the sending module is further used to send the first user identifier to the micro-application client upon receiving the first user identifier, wherein the micro-application client is used to send a identifier acquisition request including the identity token and the first user identifier to the application management terminal upon receiving the first user identifier, wherein the identifier acquisition request is used to acquire the user identifier already registered in the micro-application client by the target user.

[0030] In some embodiments, the sending module is also used to send an application registration request to the application management terminal, wherein the application management terminal is used to generate a master application identifier and a master application key for the master application client in response to the application registration request; The facility also includes: a receiving module used to receive the main application identifier and the main application key returned from the application management terminal.

[0031] In some embodiments, the sending module is also used to send a first application verification request to the application management terminal, wherein the first application verification request takes the main application identifier and the main application key, wherein the application management terminal is used to check the validity of the main application client based on the main application identifier and the main application key, and upon successful verification of the validity of the main application client, send the identity token to the main application client.

[0032] In some embodiments, the sending module is also used to send the main application identifier and the identity token to the micro-application client upon receiving the identity token, wherein the micro-application client is used to send a second authentication request including a micro-application identifier, a micro-application key, a main application identifier, and an identity token to the main application management terminal, wherein the main application management terminal is used to verify the usage rights of the main application client to the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier, and the identity token, and to return the verification result to the micro-application client.

[0033] In some embodiments, the sending module is also used to send an authorization acquisition request to the application management terminal, wherein the application management terminal is used to set the authorization information of the main application client so that it has the authorization to use the micro application client in response to the authorization acquisition request.

[0034] According to a sixth aspect of the embodiment of the present invention, there is provided a label acquisition device applied to a micro-application client, the device comprising: a receiving module used to receive a first user identifier sent from the main application client, the first user identifier representing a user identifier registered by a target user corresponding to the user information in the main application client; a sending module used to send a label acquisition request including an identity token and the first user label to the application management terminal, wherein the label acquisition request is used to acquire a second user label registered by the target user in the micro-application client; wherein the receiving module is also used to receive the second user identification sent from the application management terminal.

[0035] In some embodiments, the sending module is also used to send an application registration request to the application management terminal, wherein the application management terminal is used to generate a micro-application identifier and a micro-application key for the micro-application client in response to the application registration request; The receiving module is also used to receive the micro-application identifier and the micro-application key returned by the application management terminal.

[0036] In some embodiments, the sending module is also used to send a second application verification request to the application management terminal in response to receiving the main application identifier and the identity token of the main application client, wherein the second application verification request entails the micro-application identifier, the micro-application key, the main application identifier, and the identity token, wherein the application management terminal is used to verify the usage rights of the main application client to the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier, and the identity token, and to return the verification result to the micro-application client.

[0037] According to a seventh aspect of the embodiment of the present invention, a computing device is provided. The computing device comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein, when the program is executed by the processor, the operation performed by the method for tag acquisition provided according to the first aspect or any of the first aspects is implemented.

[0038] According to an eighth aspect of the embodiment of the present invention, a computing device is provided. The computing device comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein, when the program is executed by the processor, the operation performed by the method for tag acquisition provided according to the second aspect or any of the second aspects is implemented.

[0039] According to a ninth aspect of the present invention, a computing device is provided. The computing device comprises a memory, a processor, and a computer program stored in the memory and executable on the processor. When the program is executed by the processor, the operation performed by the method for tag acquisition provided according to the third aspect or any of the third aspects is implemented.

[0040] According to a tenth aspect of the embodiment of the present invention, there is provided a computer-readable storage medium, wherein a program is stored on the computer-readable storage medium, wherein, when the program is executed by a processor, the operation performed by the method for tag acquisition provided according to the first aspect or any of the first aspects is implemented.

[0041] According to an eleventh aspect of the embodiment of the present invention, there is provided a computer-readable storage medium, wherein a program is stored on the computer-readable storage medium, wherein, when the program is executed by a processor, the operation performed by the method for tag acquisition provided according to the second aspect or any of the second aspects is implemented.

[0042] According to a twelfth aspect of the embodiment of the present invention, there is provided a computer-readable storage medium, wherein a program is stored on the computer-readable storage medium, wherein, when the program is executed by a processor, the operation performed by the method for tag acquisition provided according to the third aspect or any one of the third aspects is implemented.

[0043] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and the present invention is not limited thereto. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0045] It shows Fig. 1 is a flowchart of a method for tag acquisition according to an embodiment of the present invention; Fig. 2 is a flowchart of a registration process for a main application client according to an embodiment of the present invention; Fig. 3 is a flowchart of a registration process for a micro-application client according to an embodiment of the present invention; Fig. 4 is a flowchart of an initialization verification process of a main application client according to an embodiment of the present invention; Fig. 5 is a flowchart of an initialization verification process of a micro-application client according to an embodiment of the present invention; Fig. 6 is a flowchart of a process for acquiring a first user identifier according to an embodiment of the present invention; Fig. 7 is a flowchart of a process for acquiring a second user identifier according to an embodiment of the present invention; Fig. 8 is a block diagram of a label acquisition device according to an embodiment of the present invention; Fig. 9 is a block diagram of a label acquisition apparatus according to an embodiment of the present invention; Fig. 10 is a block diagram of a label acquisition apparatus according to an embodiment of the present invention; Fig. 11 is a schematic structural diagram of a computing device according to an embodiment of the present invention; Fig. 12 is a schematic structural diagram of a computing device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0046] Reference is made in detail herein to embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings, in which the same numbers in different drawings represent the same or similar elements unless otherwise noted. The embodiments set forth in the following description of embodiments do not represent all embodiments consistent with the disclosure. Instead, they are merely examples of devices and methods consistent with aspects related to the disclosure, as set forth in the appended claims.

[0047] The present invention provides a label acquisition method used to acquire, based on user information, a first user label registered by a corresponding target user in the main application client and a second user label registered by the target user in the micro application client, thereby realizing user system interoperability for the main application and the micro application, so that data sharing by the main application and the micro application can be realized based on the interoperated user system.

[0048] The main application can be any type of application, such as an instant messaging program, a multimedia data processing program, a shopping application, etc., and the micro-application can be any type of custom application based on a website (web) / mobile device. Micro-applications do not need to be downloaded from the app store; instead, the micro-application is embedded directly into the main application, allowing the main application to call the micro-application and thus use the services provided by the micro-application.

[0049] Taking the main application as an instant messaging program, for example, the micro-applications may be game programs embedded in the instant messaging program, programs for medical services, information retrieval programs for government agencies and businesses, etc. The application type is not limited in the present invention.

[0050] After introducing the application scenarios of the present invention, the method for label acquisition provided by the present invention is presented in detail below.

[0051] With reference to Fig. 1, shows Fig. 1 is a flowchart of a method for tag acquisition according to an embodiment of the present invention. As in Fig. 1, the method includes: Step 101: A main application client sends an authentication request to an application management terminal, with the authentication request carrying an identity token and user information.

[0052] The user information may include the user name, user ID number, contact information, etc. The present invention does not restrict the specific content of the user information and only needs to ensure that the user information is information authorized by the user.

[0053] Step 102: In response to receiving the authentication request from the main application client, the application management terminal sends a first user identifier corresponding to the user information carried by the authentication request to the main application client when the identity token carried by the authentication request has been successfully authenticated, wherein the first user identifier represents a user identifier registered by a target user corresponding to the user information in the main application client.

[0054] Step 103: Upon receiving the first user identifier, the main application client sends the first user identifier to the micro application client.

[0055] Step 104: The micro-application client receives the first user identifier sent by the main application client.

[0056] Step 105: The micro-application client sends a label acquisition request containing the identity token and the first user label to the application management terminal, and the label acquisition request is used to acquire the user label registered by the target user in the micro-application client.

[0057] Step 106: In response to receiving the label acquisition request from the micro-application client, if the identity token carried by the label acquisition request has been successfully authenticated, the application management terminal generates a second user label corresponding to the first user label carried by the label acquisition request, wherein the second user label represents a user label registered by the target user in the micro-application client.

[0058] Step 107: The application management terminal sends the second user identifier to the micro-application client.

[0059] Step 108: The micro-application client receives the second user identifier sent from the application management terminal.

[0060] In this invention, the main application client sends an authentication request including the identity token and the user information to the application management terminal, so that the application management terminal acquires the first user identifier registered in the main application client by a target user corresponding to the user information when the identity token is successfully authenticated, thereby returning the first user identifier to the main application client, so that upon receiving the first user identifier, the main application client sends the first user identifier and the identity token to the micro application client, whereby the micro application client can send a identifier acquisition request including the first user identifier and the identity token to a micro application client;Upon receiving the tag acquisition request from the micro-application client, the application management terminal acquires the second user tag corresponding to the first user tag in the micro-application client, and sends the second user tag to the micro-application client when the identity token is successfully authenticated, so that the micro-application client can acquire the second user tag registered by the target user in the micro-application client, thereby realizing user system interoperability between the main application and the micro-application, and realizing data sharing between the main application and the micro-application based on the interoperated user system.

[0061] After explaining the basic implementation process of the label acquisition method according to the present invention, various optional embodiments of the present invention are presented below.

[0062] Please note that to achieve user system interoperability between the main application and the micro-application through the solution provided in steps 101 to 107 above, the main application and the micro-application must be registered in the application management terminal, and the application management terminal must perform an initialization verification for the main application and the micro-application. Only after the verification is successful can the user system interoperate between the main application and the micro-application through steps 101 to 107.

[0063] First, the registration process of the main application client and the micro application client in the application management terminal is introduced: For the main application client registration process, the main application client can send an application registration request to the application management terminal, and the application management terminal can receive the application registration request sent by the main application client. In response to receiving the application registration request from the main application client, the application management terminal generates a main application identifier and a main application key for the main application client and sends the main application identifier (also called the main AppID) and the main application key (also called the main AppSecret) to the main application client.The main application client receives the main application identifier and the main application key returned by the application management terminal so that the main application client can be registered in the application management terminal.

[0064] For the micro-application client registration process, the micro-application client can send an application registration request to the application management terminal, and the application management terminal can receive the application registration request sent by the micro-application client. In response to receiving the application registration request from the micro-application client, the application management terminal generates a micro-application identifier (also referred to as a micro-application ID) and a micro-application key (also referred to as a micro-application secret) for the micro-application client and sends the micro-application identifier and micro-application key to the micro-application client.The micro-application client receives the micro-application identifier and the micro-application key returned by the application management terminal so that the micro-application client can be registered in the application management terminal.

[0065] It should be noted that the application identifier, whether it is a main application identifier or a micro-application identifier, can be generated based on the 32-bit UUID (Universally Unique Identifier) ​​native to the Java programming language.

[0066] In one possible implementation, a 32-bit UUID can be randomly generated. Since the UUID is generally hexadecimal, the UUID can be divided into 8 groups of 4 characters each, and then the result can be obtained by the modulo-62 operation as an index to retrieve the characters, thus obtaining 8 characters, which can then be used as application identifiers.

[0067] The above is only one example of how to generate an application identifier. In other embodiments, other ways of generating application identifiers may be used, which are not limited by the present invention.

[0068] Furthermore, it should be noted that both the main application key and the micro application key can be generated based on the application identifier and the UUID by the key generation algorithm. For example, the application key can be generated based on the application identifier and the UUID using Secure Hash Algorithm 1 (SHA-1). Optionally, other algorithms can also be used to generate the application key, which is not limited by the present invention.

[0069] The above is only one example of how to generate an application key. In other embodiments, other methods may be used to generate application keys, which are not limited by the present invention.

[0070] It should be noted that after the application management terminal generates the main application identifier and the main application key for the main application client, the application management terminal can save the generated main application identifier and the main application key so that the validity of the main application client can be checked later based on the saved main application identifier and the main application key; and that after the application management terminal generates the micro application identifier and the micro application key for the micro application client, the application management terminal can save the generated micro application identifier and the micro application key so that the validity of the micro application client can be checked later based on the saved micro application identifier and the micro application key.

[0071] In addition, the main application client can also request the use authorization for the micro application client on the application client after registering in the application management terminal.

[0072] In some embodiments, the main application client sends an authorization acquisition request to the application management terminal. In response to receiving the authorization acquisition request from the main application client, the application management terminal deploys the authorization information of the main application client to authorize the use of the micro-application client by the main application client.

[0073] In one possible implementation, the application management terminal may store the application identifiers of the micro-application client and the main application client that has the authorization to use that micro-application client, so that the authorization information of the main application client can be used to have the authorization to use the micro-application client.

[0074] It should be noted that the application management terminal may include a micro-application management platform and a main index platform, wherein the micro-application management platform may perform the following operations: generating the application labels and application keys for the main application client and the micro-application client, and assigning the permissions for using the micro-application client to the main application client.

[0075] With reference to Fig. 2, shows Fig. 2 is a flowchart of a registration process for a main application client according to an embodiment of the present invention. As in Fig. As shown in Figure 2, the main application client requests registration on the micro-application management platform, and the micro-application management platform generates the main App ID and the main App Secret for the main application client and returns them to the main application client. Furthermore, the main application client can also request permission to use the micro-application client from the micro-application management platform.

[0076] With reference to Fig. 3, shows Fig. 3 is a flowchart of a registration process for a microapplication client according to an embodiment of the present invention. As in Fig. 3, the micro-application client requests registration on the micro-application management platform, and the micro-application management platform generates the micro-app ID and the micro-app secret for the micro-application client and returns them to the micro-application client.

[0077] After the application management terminal completes the registration and authorization assignment of the main application client and the registration of the micro application client, it can perform the initialization verification of the main application client and the micro application client to check the validity of the main application client and the micro application client.

[0078] Next, the initialization verification process of the main application client and the micro application client on the application management terminal is introduced: For the initial verification process of the main application client on the application management terminal, the main application client sends the first application verification request containing the main application identifier and key to the application management terminal. Then, in response to receiving the first application verification request from the main application client, the application management terminal verifies the validity of the main application client based on the main application identifier and key included in the application verification request. If the validity verification of the main application client is successful, the application management terminal sends the identity token to the main application client; otherwise, a notification message, such as "Failed," is displayed.Error code sent to the main application client, where the hint information is used to inform the main application client of the unsuccessful validity check.

[0079] In one possible implementation, the application management terminal can compare the main application identifier and main application key retrieved from the first application verification request with the stored main application identifier and main application key. If the main application identifier and main application key retrieved from the first application verification request are present in the stored main application identifier and main application key, it can be determined that the validity check of the main application client was successful.

[0080] It should be noted that the application management terminal can generate an identity token for the main application client and return the generated identity token to the main application client if the validity check of the main application client is successful.

[0081] Optionally, the Java Web Token (JWT) method can be used to generate the identity token. Furthermore, other methods for generating the identity token can also be used, which are not limited by the present invention.

[0082] The identity token can include expiration time, user information, main application identifier, and signature information. Optionally, the identity token can also include more or less content, which is not restricted by the present invention.

[0083] It should be noted that after the identity token is generated for the main application client, the application management terminal can store the generated identity token and then perform the validity check of the micro-application client based on the stored identity token.

[0084] The initialization verification process of the micro-application client on the application management terminal requires that this process be performed after the successful validity check of the main application client.

[0085] After acquiring the identity token, the main application client sends the main application identifier and the identity token to the micro-application client. In response to receiving the main application identifier and the identity token from the main application client, the micro-application client submits the second application verification request to the application management terminal, which includes the micro-application identifier, the micro-application key, the main application identifier, and the identity token.Then, in response to receiving the second application verification request from the micro-application client, the application management terminal verifies the use rights of the main application client against the micro-application client based on the micro-application identifier, micro-application key, main application identifier, and identity token included in the second application verification request. If it is determined that the main application client has the authorization to use the micro-application client, the application management terminal sends usage permission information to the micro-application client; otherwise, usage prohibition information is sent to the micro-application client.

[0086] It should be noted that when the main application client sends the main application identifier and identity token to the micro-application client, the main application identifier and identity token may be transmitted to the micro-application client's software development kit (SDK), and the micro-application client's SDK may send a second application verification request to the application management terminal.

[0087] In one possible implementation, after the application management terminal acquires the second application verification request, the micro-application identifier, micro-application key, and main application identifier carried by the second application verification request may be compared with the stored micro-application identifier, micro-application key, and main application identifier, and the identity token is authenticated based on the signature information contained in the identity token.If the micro-application identifier, micro-application key, and main application identifier carried by the second application verification request are present in the stored micro-application identifier, micro-application key, and main application identifier, and the authentication of the signature information is successful, it can be determined that the micro-application client has passed the validity verification of the micro-application client.

[0088] It should be noted that the above-mentioned initialization verification process of the main application client and the micro-application client can be performed by the micro-application management platform.

[0089] Fig. 4 shows a flowchart of an initialization verification process of a main application client according to an embodiment of the present invention. As in Fig. As shown in Figure 4, the main application client can send an initial application verification request containing a main AppID and a main AppSecret to the micro-application management platform. If the main AppID and the main AppSecret are successfully authenticated (i.e., authentication is successful), the micro-application management platform can return the identity token (i.e., token) to the main application client.

[0090] Fig. 5 shows a flowchart of an initialization verification process of a microapplication client according to an embodiment of the present invention. As in Fig. As shown in Figure 5, the main application client can send a token to the micro-application client, and only then can the micro-application client send a second application verification request containing a token and a micro-appID to the micro-application management platform. If this is the case, only then can the micro-application management platform return information about the successful verification to the micro-application client. If a validity check of the token and the micro-appID is unsuccessful, the micro-application management platform can return an error code to the micro-application client.

[0091] After the initialization verification process of the main application client and the micro application client is implemented through the above process, the process of subsequent execution and interoperability of the user system can then proceed.

[0092] In some embodiments, in response to receiving an authentication request from the main application client, the application management terminal may send an authentication request to the main application client, if the identity token carried by the authentication request has been authenticated by in response to receiving an authentication request from the main application client, authenticating the identity token based on the signature information contained in the identity token; and acquiring the first user identifier based on the user information entailed by the authentication request if the signature information has been successfully authenticated; and sending the first user identifier to the main application client.

[0093] It should be noted that the process of running and interoperating the user system can be realized based on the interaction between the micro-application management platform and the main index platform.

[0094] Assuming the initialization verification of the main application client is successful, in one possible implementation, the main application client can send an authentication request containing an identity token and user credentials to the main index platform. The main index platform then requests a validation request for the main application client to the micro-application management platform. The micro-application management platform returns the result of the main application client's validity check to the main index platform. After the main application client's validity check is successful, the main index platform searches for the first user identifier (referred to as globalId) registered by the target user in the main application client, which corresponds to the user credentials included in the authentication request.After receiving the first user identifier, the main application client transmits it to the micro-application client. The micro-application client sends a identifier acquisition request containing the first user representation and the main application client's identity token to the main index platform. After receiving the identity token and the first user identifier, the micro-application management platform requests the main index platform to verify the validity of the identity token. The micro-application management platform returns the result of the identity token validity check to the main index platform. If the identity token validity check is successful, the main index platform returns a second user identifier registered by the target user in the micro-application client to the micro-application client.Previously, the first user identifier of the target user can be acquired in the main application client and the second user identifier of the target user in the micro-application client based on the same user information. Furthermore, the user information and user data of the target user can be acquired in the main application client based on the first user identifier, and the user information and user data of the target user can be acquired in the micro-application client based on the second user identifier. Through the main index platform and the micro-application management platform, the user systems for the main application and the micro-application are interoperated, allowing the main application and the micro-application to share user information and data.

[0095] Fig. 6 shows a flowchart of a first user tag acquisition process according to an embodiment of the present invention. As in Fig. As shown in Figure 6, the main application client sends an authentication request containing a token and user information to the main index platform, and the main index platform then transmits the token to the micro-application management platform. The micro-application management platform checks the validity of the token. If the validity check is successful, the micro-application management platform returns information about the successful check to the main index platform. If the main index platform receives information about the successful check, the main index platform can return the first user identification to the main application client. If the validity check is unsuccessful, the micro-application management platform returns an error code to the main index platform.If the main index platform receives the error code, the main index platform can return the error code to the main application client.

[0096] Fig. Figure 7 shows a flowchart of a process for acquiring the second user identifier according to an embodiment of the present invention. As shown in Fig. As shown in Figure 7, the micro-application client sends a tag acquisition request containing a token and a first user tag to the main index platform, and the main index platform then transmits the token to the micro-application management platform. The micro-application management platform checks the validity of the token. If the validity check is successful, the micro-application management platform returns information about the successful check to the main index platform. If the main index platform receives information about the successful check, the main index platform can return the second user tag to the main application client. If the validity check is unsuccessful, the micro-application management platform returns an error code to the main index platform.If the main index platform receives the error code, the main index platform can return the error code to the main application client.

[0097] According to the embodiments of the above-mentioned methods, the present invention also provides embodiments of corresponding label acquisition devices and a computing device to which they are applied.

[0098] Fig. Figure 8 shows a block diagram of a label acquisition device according to an embodiment of the present invention, which is applied to the application management terminal. This device includes: a transmission module 801 used to transmit, in response to receiving an authentication request from the main application client, a first user identifier corresponding to the user information carried by the authentication request to the main application client when an identity token carried by the authentication request has been successfully authenticated, wherein the first user identifier represents the same user identifier registered by a target user corresponding to the user information in the main application client, wherein the main application client is used to transmit, through it, the first user identifier and the identity token to the micro application client upon receiving the first user identifier, wherein the micro application client is used tosend a tag acquisition request to the main application management terminal based on the first user tag and the identity token; an acquisition module 802 configured to, in response to receiving the tag acquisition request from the micro-application client, acquire a second user tag corresponding to the first user tag entrained by the tag acquisition request if the identity token entrained by the tag acquisition request has been successfully authenticated, wherein the second user tag represents a user tag registered by the target user in the micro-application client; wherein the transmitting module 801 is further used to transmit the second user identifier to the micro-application client.

[0099] In some embodiments, the identity token comprises at least signature information; When, in response to receiving the authentication request from the main application client, a first user identifier corresponding to the user information carried by the authentication request is sent to the main application client when the identity token carried by the authentication request has been authenticated, the sending module 801 is used to: in response to receiving an authentication request from the main application client, authenticate the identity token based on the signature information contained in the identity token; to acquire the first user identifier based on the user information carried by the authentication request if the signature information has been successfully authenticated; to send the first user identification to the main application client.

[0100] In some embodiments, this device further comprises: a generation module used to generate a main application identifier and a main application key for the main application in response to receiving an application registration request from the main application client; the generation module is further used to generate a micro-application identifier and a micro-application key for the micro-application in response to receiving an application registration request from the micro-application client.

[0101] In some embodiments, this device further comprises: Verification module used to, in response to receiving an authentication request from the main application client, check the validity of the main application client based on the main application identifier and the main application key carried by the first application verification request; wherein the sending module 801 is also used to send the identity token to the main application client if the validity check of the main application client is successful, otherwise, to send an indication information to the main application client which is used to indicate that the validity check of the main application client has failed.

[0102] In some embodiments, the verification module is also used to, in response to receiving the second application verification request from the micro-application client, verify the usage rights of the main application client against the micro-application client based on the micro-application identifier and micro-application key, main application identifier, and identity token entrained by the second application verification request; wherein the transmission module 801 is also used to transmit usage permission information to the micro-application client when it is confirmed that the main application client has the permission to use the micro-application client, otherwise, to transmit usage prohibition information to the micro-application client.

[0103] In some embodiments, the device further comprises: a setting module used to set the authorization information of the main application client so that it has the authorization to use the micro application client in response to receiving the authorization acquisition request from the main application client.

[0104] Fig. Figure 9 shows a block diagram of a label acquisition device according to an embodiment of the present invention applied to the main application client. This device comprises: a sending module 901 used to send an authentication request to an application management terminal, the authentication request entailing the identity token and the user information, the application management terminal being used to acquire a first user identifier corresponding to the user information if the authentication of the identity token is successful, the first user identifier being the same user identifier registered by a target user corresponding to the user information in the main application client; wherein the sending module 901 is further used to send the first user identifier to the micro-application client when the first user identifier has been received thereby, and sending a identifier acquisition request to the application management terminal by the micro-application client when the first user identifier has been received thereby, the identifier acquisition request taking the identity token and the first user identifier, the identifier acquisition request being used to acquire the user identifier registered in the micro-application client by the target user.

[0105] In some embodiments, the sending module 901 is also used to generate a master application identifier and a master application key for the master application client in response to the application registration request; The facility also includes: a receiving module used to receive the main application identifier and the main application key returned from the application management terminal.

[0106] In some embodiments, the sending module 901 is also used to send a first application verification request to the application management terminal, wherein the first application verification request takes the main application identifier and the main application key, wherein the application management terminal is used to verify the validity of the main application client based on the main application identifier and the main application key and to send an identity token to the main application client if the validity check of the main application client is successful.

[0107] In some embodiments, the sending module 901 is also used to send the main application identifier and the identity token to the micro-application client when the identity token has been received, wherein the micro-application client is configured to send a second authentication request carrying the micro-application identifier, the micro-application key, the main application identifier, and the identity token to the main application management terminal, wherein the main application management terminal is used to verify the usage rights of the main application client to the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier, and the identity token, and to return the verification result to the micro-application client.

[0108] In some embodiments, the sending module 901 is also used to send an authorization acquisition request to the application management terminal, wherein the application management terminal is used to set the authorization information of the main application client so that it has the authorization to use the micro application client in response to the authorization acquisition request.

[0109] Fig. Figure 10 shows a block diagram of a tag acquisition device according to an embodiment of the present invention applied to a microapplication client. This device includes: a receiving module 1001 used to receive the first user identifier sent from the main application client, the first user identifier representing a user identifier registered by a target user in the main application client; a sending module 1002 used to send a tag acquisition request including an identity token and the first user tag to the application management terminal, the tag acquisition request being used to acquire the second user tag registered by the target user in the micro-application client; wherein the receiving module 1001 is also used to receive the second user identification sent from the application management terminal.

[0110] In some embodiments, the sending module 1002 is also used to send an application registration request to the application management terminal, wherein the application management terminal generates a micro-application identifier and a micro-application key for the micro-application client in response to the application registration request;

[0111] The receiving module is also used to receive the micro-application identifier and the micro-application key returned from the application management terminal.

[0112] In some embodiments, the sending module 1002 is also used to send a second application verification request to the application management terminal in response to receiving the main application identifier and the identity token of the main application client, wherein the second application verification request entails the micro-application identifier, the micro-application key, the main application identifier, and the identity token, wherein the application management terminal is used to verify the usage rights of the main application client to the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier, and the identity token, and to return the verification result to the micro-application client.

[0113] The specific implementation processes of the functions and effects of each module in the above facilities can be found in the implementation process of the corresponding steps in the above procedure and will not be described again here.

[0114] With regard to the embodiments of the device, reference can be made to the partial description of the embodiments of the method, since they basically correspond to the embodiments of the method. The embodiments of the device described above are merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components indicated as modules may or may not be physical modules, i.e., may be arranged in one location or distributed across multiple network modules. Some or all of the modules may be selected as needed to achieve the objectives of the present description. Those of ordinary skill in the art can understand and implement the present application without creative effort.

[0115] The present invention also provides a computing device as described in Fig. 11 shown. Fig. Figure 11 shows a schematic structural diagram of a computing device according to an embodiment of the present invention. The application management platform may be executed on the computing device. The computing device may be a server, multiple servers, a server cluster, etc. As shown in Fig. As shown in Figure 11, the computing device includes a processor 1110, a memory 1120, and a network interface 1130. Memory 1120 is used to store computer instructions executable on processor 1110. Processor 1110 is used in executing the computer instructions to implement the tag acquisition method according to one embodiment of the present invention. Network interface 1130 is used to implement input and output functions. In other possible implementations, the computing device may also include other hardware, which is not limited by the present invention.

[0116] The present invention also provides a computing device as described in Fig. 12 shown. Fig. Figure 12 shows a schematic structural diagram of a computing device according to an embodiment of the present invention, on which both the main application client and the micro-application client can be executed. The computing device may be a desktop computer, a portable computer, a notebook, a smartphone, a tablet computer, etc. As shown in Fig. As shown in Figure 12, the computing device includes a processor 1210, a memory 1220, and a network interface 1230. Memory 1220 is used to store computer instructions executable on processor 1210. Processor 1210 is used in executing the computer instructions to implement the method for tag acquisition according to one embodiment of the present invention. Network interface 1230 is used to implement input and output functions. In other possible implementations, a computing device may also include other hardware, which is not limited in the present application.

[0117] The present invention also provides a computer-readable storage medium that can be embodied in various forms. In various examples, the computer-readable storage medium can be, for example, a RAM (Random Access Memory), a volatile memory, a non-volatile memory, a flash memory, a storage drive (such as a hard disk drive), a solid-state hard disk, any type of storage disk (such as an optical disk or a DVD), or a similar storage medium, or a combination thereof. In particular, the computer-readable medium can be paper or another suitable medium on which programs can be printed. A computer program is stored on the computer-readable storage medium, and when the computer program is executed by a device as described in Fig. 11 or Fig. 12, the method for label acquisition provided by any embodiment of the present application is implemented.

[0118] The present application also provides a computer program product comprising a computer program implementing the method for label acquisition provided by any embodiment of the present application when the computer program is executed by a computer program as described in Fig. 11 or Fig. 12 shown processor.

[0119] Those skilled in the art should understand that one or more embodiments of the present description may be provided as a method, apparatus, computing device, computer-readable storage media, or computer program products. Accordingly, one or more embodiments of the present description may be embodied as hardware-only implementations, software-only implementations, or combinations of software and hardware implementations. Furthermore, one or more embodiments of the present description may be embodied as computer program products implemented on one or more computer-readable storage media (including, but not limited to, disk storage, compact disc read-only memories (CD-ROMs), optical storage, etc.) and comprising computer-readable program code.

[0120] Various examples in the present description will be described progressively one after the other. Identical or similar parts in the various embodiments may be referred to one another, and each embodiment focuses on the differences from other embodiments. In particular, for the embodiments relating to the computing device, the description is simplified because its embodiment is fundamentally similar to the embodiments of the method, and reference may be made to some of the descriptions of the embodiments of the method.

[0121] Specific embodiments of the present specification are described above. Other embodiments are within the scope of the present application. In some cases, actions or steps recorded in the present invention may be performed in a different order than in the embodiments and the desired results may still be achieved. Furthermore, processes depicted in the drawings do not necessarily have to be performed in a particular or sequential order to achieve the desired results. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0122] The embodiments of the subject matter and functional acts described in this specification may be implemented in a digital electronic circuit, tangible computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or a combination of one or more thereof. The embodiments of the subject matter described in this specification may be implemented as one or more computer programs, i.e., as one or more modules in computer program instructions encoded on a tangible, non-temporary program carrier to be executed by a tag acquisition device or to control operations of the tag acquisition device. Alternatively or additionally, program instructions may be encoded on artificially generated propagation signals, such asMachine-generated electrical, optical, or electromagnetic signals generated to encode information and transmit it to a suitable receiving device for execution by the tag acquisition device. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random access or serial storage device, or a combination of one or more thereof.

[0123] The processes and logic steps described in this specification may be performed by one or more programmable computers executing one or more computer programs to implement corresponding functions by operating on input data and generating outputs. The processes and logic steps may be performed by a dedicated logic circuit, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the device may be implemented as a dedicated logic circuit.

[0124] Computers suitable for executing computer programs include, for example, general-purpose and / or dedicated microprocessors or any other type of central processing unit. Typically, the central processing unit receives instructions and data from ROM and / or RAM. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more storage devices for storing instructions and data. Generally, the computer also includes one or more mass storage devices for storing data, such as a magnetic disk, a magneto-optical disk, an optical disk, etc., or the computer is operatively coupled to the mass storage devices to receive or send data to or from them, or both. However, the computer need not include such devices.In addition, the computer may be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (such as a Universal Serial Bus (USB) flash drive), to name a few.

[0125] Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, such as semiconductor storage devices (such as EPROMs, EEPROMs, and flash memory devices), magnetic disks (such as internal hard disks or portable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and memory may be supplemented by or integrated with dedicated logic circuitry.

[0126] Although the present description contains many specific implementation details, rather than being interpreted as limiting the scope of an invention or the scope of protection claimed, these details are primarily used to describe features of specific embodiments of a particular invention. Some features described in multiple embodiments of the present description may be combined in a single embodiment. In another aspect, various features described in a single embodiment may be implemented separately in multiple embodiments or in any suitable subcombination.Although features may be effective in some combinations as described above and may even be initially claimed as such, in some cases one or more features may be deleted from the claimed combinations, and the claimed combinations may refer to sub-combinations or variants of the sub-combinations.

[0127] Although the operations in the drawings are described in a particular order, this should not be understood to mean that these operations must be performed in a particular or sequential order, or that all of the illustrated operations must be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system modules and components in the embodiments described above should not be understood to mean that such separation is required in all embodiments, and it should be understood that the described program components and the system in general may be integrated into a single software product or packaged into multiple software products.

[0128] Therefore, the specific embodiments of the subject matter have been described. Other embodiments are within the scope of the present application. In some cases, the actions described in the present application may be performed in a different order and the desired results may still be achieved. Furthermore, the processes depicted in the drawings do not necessarily have to be performed in a particular or sequential order to achieve the desired results. In some implementations, multitasking and parallel processing may be advantageous.

[0129] Other embodiments of the present description will be readily apparent to those skilled in the art after reviewing the description and implementing the contents disclosed herein. This description is intended to cover any variations, uses, or adaptations of the present description that follow the general principle of the present description and incorporate common knowledge or conventional technical means in the art not disclosed in the present description. That is, the present description is not limited to the precise structures already described and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof.

[0130] The above-mentioned embodiments are merely optional embodiments of the present description and are not intended to limit the description. Any modification, equivalent replacement, improvement, etc., made within the spirit and principle of the description will be considered within the scope of the description.

Claims

[1] Procedure for acquiring labelling, characterized by that it is executed by an application management terminal, comprising the following: in response to receiving an authentication request from the main application client, sending a first user identifier corresponding to the user information carried by the authentication request to the main application client if the identity token carried by the authentication request has been successfully authenticated, wherein the first user identifier represents a user identifier registered by a target user corresponding to the user information in the main application client, wherein the main application client is used to send the first user identifier and the identity token to the micro application client upon receiving the first user identifier, wherein the micro application client is used to send a identifier acquisition request to the main application management terminal based on the first user identifier and the identity token; in response to receiving the label acquisition request from the micro-application client, acquiring a second user label corresponding to the first user label entrained by the label acquisition request if the identity token entrained by the label acquisition request has been successfully authenticated, wherein the second user label represents a user label registered by the target user in the micro-application client; Send the second user identifier to the micro-application client. [2] Method according to claim 1, characterized by that the identity token includes at least signature information; the step of, in response to receiving the authentication request from the main application client, sending a first user identifier corresponding to the user information carried by the authentication request to the main application client if the identity token carried by the authentication request has been authenticated, comprises: in response to receiving an authentication request from the main application client, authenticating the identity token based on the signature information contained in the identity token; Acquiring the first user identifier based on the user information carried by the authentication request if the signature information has been successfully authenticated; Sending the first user identification to the main application client. [3] Method according to claim 1, characterized bythat the method, prior to the step of, in response to receiving the authentication request from the main application client, sending a first user identifier corresponding to the user information carried by the authentication request to the main application client if the identity token carried by the authentication request has been authenticated, further comprises at least one of the following steps: in response to receiving an application registration request from the main application client, generating a main application identifier and a main application key for the main application client and sending the main application identifier and the main application key to the main application client; in response to receiving an application registration request from the micro-application client, generating a micro-application identifier and a micro-application key for the micro-application client and sending the micro-application identifier and the micro-application key to the micro-application client. [4] Method according to claim 3, characterized by that the method, prior to the step of, in response to receiving the authentication request from the main application client, sending a first user identifier corresponding to the user information carried by the authentication request to the main application client if the identity token carried by the authentication request has been authenticated, further comprises: in response to receiving a first application verification request from the main application client, checking the validity of the main application client based on the main application identifier and the main application key carried by the first application verification request; Send the identity token to the main application client if the main application client's validity check is successful; otherwise, send a notice to the main application client that is used to indicate that the main application client's validity check failed. [5] Method according to claim 4, characterized by that after the step of sending the identity token to the main application client if the validity check of the main application client is successful, the procedure further comprises the following: in response to receiving a second application verification request from the micro-application client, verifying the usage rights of the main application client against the micro-application client based on the micro-application identifier, micro-application key, main application identifier, and identity token entailed by the second application verification request; Sending usage permission information to the micro-application client if it is confirmed that the main application client has the permission to use the micro-application client; otherwise, sending usage prohibition information to the micro-application client. [6] Method according to claim 5, characterized bythat the method, prior to the step of, in response to receiving a second application verification request from the micro-application client, verifying the usage rights of the main application client against the micro-application client based on the micro-application identifier, micro-application key, main application identifier and identity token entailed by the second application verification request, further comprises: in response to receiving an authorization acquisition request from the main application client, setting the authorization information of the main application client such that it has the authorization to use the micro application client. [7] Procedure for acquiring labelling, characterized by that it is executed by the main application client, comprising the following: Sending an authentication request to an application management terminal, the authentication request including an identity token and user information, the application management terminal being used to acquire a first user identifier corresponding to the user information if authentication of the identity token is successful, the first user identifier representing a user identifier registered by a target user corresponding to the user information in the main application client; Sending the first user identifier to the micro-application client when the first user identifier has been received, wherein the micro-application client is used to send a identifier acquisition request to the application management terminal upon receipt of the first user identifier, wherein the label acquisition request takes the identity token and the first user label, wherein the label acquisition request is used to acquire the user label registered in the micro-application client by the target user. [8] Method according to claim 7, characterized by that the procedure, prior to the step of sending the authentication request to the application management terminal, also includes: Sending an application registration request to the application management terminal, wherein the application management terminal is used to generate a main application identifier and a main application key for the main application client in response to the application registration request; Receive the main application label and main application key returned from the application management terminal. [9] Method according to claim 7, characterized by that the procedure prior to the step of sending the authentication request to the application management terminal also includes: Sending a first application verification request to the application management terminal, wherein the first application verification request takes the main application identifier and the main application key, wherein the application management terminal is used to verify the validity of the main application client based on the main application identifier and the main application key and to send an identity token to the main application client if the validity check of the main application client is successful. [10] Method according to claim 9, characterized by that the method, after the step of sending the first application verification request to the application management terminal, further comprises: Sending the main application identifier and the identity token to the micro-application client when the identity token is received, wherein the micro-application client is used to send a second authentication request including a micro-application identifier, a micro-application key, a main application identifier, and an identity token to the main application management terminal, wherein the main application management terminal is used to verify the usage rights of the main application client against the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier, and the identity token, and return the verification result to the micro-application client. [11] Method according to claim 7, characterized by that the procedure prior to the step of sending the authentication request to the application management terminal also includes: Sending an authorization acquisition request to the application management terminal, wherein the application management terminal is used to set the authorization information of the main application client so that it has the authorization to use the micro application client in response to the authorization acquisition request. [12] Procedure for acquiring labelling, characterized by that it is executed by a micro-application client, comprising the following: Receiving a first user identifier sent from the main application client, the first user identifier representing a user identifier registered by a target user in the main application client; Sending a label acquisition request with an identity token and the first user label to the application management terminal, wherein the label acquisition request is used to acquire a second user label registered by the target user in the micro-application client; Receiving the second user identifier sent from the application management terminal. [13] Method according to claim 12, characterized by that the method, prior to the step of receiving a first user identification sent by the main application client, further comprises: Sending an application registration request to the application management terminal, wherein the application management terminal is used to generate a micro-application identifier and a micro-application key for the micro-application client in response to the application registration request; Receive the micro-application identifier and micro-application key returned from the application management terminal. [14] Method according to claim 13, characterized by that the method, prior to the step of receiving a first user identification sent by the main application client, further comprises: in response to receiving the main application identifier and the identity token of the main application client, sending a second application verification request to the application management terminal, the second application verification request bringing the micro-application identifier, the micro-application key, the main application identifier, and the identity token, wherein the application management terminal is used to verify the usage rights of the main application client to the micro-application client based on the micro-application identifier, the micro-application key, the main application identifier, and the identity token, and return the verification result to the micro-application client. [15] Marking acquisition facility, characterized by that it is executed by the application management terminal, comprising: a sending module used to send a first user identifier corresponding to the user information carried by the authentication request to the main application client in response to receiving an authentication request from the main application client if an identity token carried by the authentication request has been successfully authenticated, wherein the first user identifier represents a user identifier registered by a target user corresponding to the user information in the main application client, wherein the main application client is used to send the first user identifier and the identity token to the micro application client upon receiving the first user identifier, wherein the micro-application client is used to send a tag acquisition request to the main application management terminal based on the first user tag and the identity token; an acquisition module used to acquire, in response to receiving the label acquisition request from the micro-application client, a second user label corresponding to the first user label entrained by the label acquisition request if the identity token entrained by the label acquisition request has been successfully authenticated, wherein the second user label represents a user label registered by the target user in the micro-application client; wherein the sending module is further used to send the second user identifier to the micro-application client. [16] Marking acquisition facility, characterized bythat it is executed by the main application client, including: a sending module used to send an authentication request to an application management terminal, the authentication request entailing an identity token and user information, the application management terminal being used to acquire a first user identifier corresponding to the user information if the authentication of the identity token is successful, the first user identifier representing a user identifier registered by a target user corresponding to the user information in the main application client; wherein the sending module is further used to send the first user identifier to the micro-application client upon receiving the first user identifier, wherein the micro-application client is used to send a identifier acquisition request including the identity token and the first user identifier to the application management terminal upon receiving the first user identifier, wherein the identifier acquisition request is used to acquire the user identifier already registered in the micro-application client by the target user. [17] Marking acquisition facility, characterized by that it is executed by a micro-application client, comprising: a receiving module used to receive the first user identifier sent from the main application client, wherein the first user identifier represents a user identifier registered by a target user in the main application client; a sending module used to send a tag acquisition request including an identity token and the first user tag to the application management terminal, wherein the tag acquisition request is used to acquire the second user tag registered by the target user in the micro-application client; wherein the receiving module is also used to receive the second user identification sent from the application management terminal. [18] computing device, characterized byin that the computing device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein, when the program is executed by the processor, the operation performed by the method for acquiring a label according to any one of claims 1 to 14 is implemented. [19] Computer-readable storage medium, characterized by that a program is stored on the computer-readable storage medium, wherein, when the program is executed by a processor, the operation performed by the method for acquiring a label according to any one of claims 1 to 14 is implemented.

Images