Authorization methods, apparatuses, computing devices, and storage media

Abstract

The application discloses an authorization method and device, a computing device and a storage medium. The method comprises the following steps: assigning, to a user in a first application, identification information required by the user for using a second application; receiving a target data acquisition request initiated by the second application; the target data acquisition request comprises to-be-verified identification information and application information of the second application; verifying whether a binding relationship exists between the to-be-verified identification information and the application information of the second application; and if it is verified that the binding relationship exists, authorizing the second application to use target data in the first application. In the above manner, the authorization method is easy to implement and has low development difficulty, and the time for verifying application permissions can be saved.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to an authorized method, apparatus, computing device, and storage medium. Background Technology

[0002] In practical applications, there are often situations where one application needs to access specific data from another application. For example, when a streamer in a live streaming application uses a game application, the game application may need to access the streamer's live streaming data. Authorization is required for the game application to access the streamer's live streaming data. However, existing authorization methods have high technical barriers and are difficult to develop. Summary of the Invention

[0003] The purpose of this application is to provide an authorized method apparatus, computing device, and storage medium to solve the problems of high technical threshold and great development difficulty in the prior art.

[0004] According to one aspect of this application, a licensing method is provided, comprising:

[0005] Assign the identification information required for the user to use the second application to the user in the first application;

[0006] Receive a target data acquisition request initiated by a second application; wherein the target data acquisition request includes the identification information to be verified and the application information of the second application;

[0007] Verify whether there is a binding relationship between the identification information to be verified and the application information of the second application;

[0008] If a binding relationship is detected, the second application is authorized to use the target data in the first application.

[0009] Optionally, the target data acquisition request may also include: the developer information of the second application; verifying whether there is a binding relationship between the identifier information to be verified and the application information of the second application further includes: verifying whether there is a binding relationship between the identifier information to be verified, the application information of the second application, and the developer information of the second application.

[0010] Optionally, after receiving the target data acquisition request initiated by the second application, the method further includes: querying the authorization status of the user in the first application corresponding to the identification information to be verified to the second application; authorizing the second application to use the target data in the first application further includes: if the authorization status is found to be authorized and a binding relationship is verified, authorizing the second application to use the target data in the first application.

[0011] Optionally, the method further includes: if the authorization status is found to be "authorization off", returning a response indicating data retrieval failure to the second application.

[0012] Optionally, allocating the identification information required for a user to use the second application to the user in the first application further includes: receiving an authorization request from a user in the first application for the second application, and allocating the identification information required for a user to use the second application to the user in the first application;

[0013] Establish a binding relationship between the application information and identification information of the second application, and set the user's authorization status for the second application to the authorized state.

[0014] Optionally, after establishing the binding relationship between the application information and the identification information of the second application, the method further includes: receiving a user's identification information update request for the second application, and updating the identification information of the user that is bound to the application information of the second application.

[0015] Optionally, after establishing the binding relationship between the application information and the identification information of the second application, the method further includes: receiving a user's request to close the authorization for the second application; and changing the user's authorization status for the second application from the authorization enabled state to the authorization disabled state.

[0016] Optionally, after allocating the identification information required for a user to use the second application to the user in the first application, the method further includes: receiving a user's request to invalidate the identification information for the second application, and invalidating the identification information.

[0017] Optionally, after verifying the binding relationship between the identification information to be verified and the application information of the second application, the method further includes: obtaining the frequency information and / or time information of the identification information to be verified being called;

[0018] Authorizing the second application to use the target data in the first application further includes: if it is determined that the call is normal based on frequency information and / or time information, authorizing the second application to use the target data in the first application.

[0019] Optionally, the method further includes: if a call exception is determined based on frequency information and / or time information, returning a response indicating data retrieval failure to the second application.

[0020] Optionally, authorizing the second application to use the target data in the first application further includes: authorizing the second application to use the target data in the first application to log in.

[0021] Optionally, the method further includes: receiving a registration request from an application developer; assigning developer information to the application developer and assigning application information to each application belonging to the application developer.

[0022] Optionally, the method further includes: receiving a user's request to view call records; and returning to the user the frequency and / or time information of the call to the identification information.

[0023] According to another aspect of this application, a licensed device is provided, the device comprising:

[0024] The allocation module is adapted to allocate identification information required by a user to use a second application to a user in the first application.

[0025] The receiving module is adapted to receive a target data acquisition request initiated by a second application; wherein the target data acquisition request includes the identification information to be verified and the application information of the second application;

[0026] The verification module is suitable for verifying whether there is a binding relationship between the identification information to be verified and the application information of the second application.

[0027] The authorization module is suitable for authorizing a second application to use the target data in the first application if a binding relationship is detected.

[0028] Optionally, the target data acquisition request may also include: developer information of the second application; and a verification module, further adapted to verify whether there is a binding relationship between the identification information to be verified, the application information of the second application, and the developer information of the second application.

[0029] Optionally, the device further includes: a query module, adapted to query the authorization status of a user in the first application corresponding to the identification information to be verified for the second application;

[0030] The authorization module is suitable for authorizing a second application to use the target data in the first application if the authorization status is found to be enabled and a binding relationship is verified.

[0031] Optionally, the device further includes a feedback module, adapted to return a data retrieval failure response to the second application if the queried authorization status is an authorization closed status.

[0032] Optionally, the allocation module is further adapted to: receive an authorization request from a user in the first application to the second application, allocate identification information required for the user to use the second application to the user in the first application; establish a binding relationship between the application information of the second application and the identification information, and set the user's authorization status for the second application to the authorization enabled state.

[0033] Optionally, the receiving module is further adapted to: receive a user's request to update the identification information of the second application; the device further includes: an updating module, adapted to update the identification information of the user that is bound to the application information of the second application.

[0034] Optionally, the receiving module is further adapted to: receive a user's request to close the authorization for the second application; the allocation module is further adapted to: change the user's authorization status for the second application from the authorization enabled state to the authorization disabled state.

[0035] Optionally, the receiving module is further adapted to: receive a user's request for invalidation of identification information for the second application; the allocation module is further adapted to: perform invalidation processing on the identification information.

[0036] Optionally, the device further includes: an acquisition module, adapted to acquire frequency information and / or time information of the identification information to be verified being called; and an authorization module, further adapted to: if it is determined that the call is normal based on the frequency information and / or time information, authorize the second application to use the target data in the first application.

[0037] Optionally, the feedback module is further adapted to: if a call exception is determined based on frequency information and / or time information, return a response indicating data retrieval failure to the second application.

[0038] Optionally, the authorization module is further adapted to: authorize a second application to log in using the target data in the first application.

[0039] Optionally, the receiving module is further adapted to: receive registration requests from application developers; the allocation module is further adapted to: allocate developer information to application developers and allocate application information to each application belonging to the application developer.

[0040] Optionally, the receiving module is further adapted to: receive a user's request to view the call record; the feedback module is further adapted to: return to the user the frequency information and / or time information of the call to the identification information.

[0041] According to another aspect of this application, a computing device is provided, comprising: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other through the communication bus;

[0042] The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the above-authorized method.

[0043] According to another aspect of this application, a computer storage medium is provided, wherein the storage medium stores at least one executable instruction that causes a processor to perform an operation corresponding to the above-described authorized method.

[0044] According to the authorization method, apparatus, computing device, and storage medium of this application, on the one hand, by assigning identification information required for an application user (i.e., a user in the first application) to use other third-party applications (the second application), the third-party application can be authorized to use the target data in the application as long as it makes a request using the correct identification information. This authorization method is easy to implement, has low development difficulty, and can save time in verifying application permissions. On the other hand, it supports application users actively refreshing the identification information required for using third-party applications, which can prevent third-party applications from saving identification information to steal application data. Furthermore, it supports application users to enable or cancel authorization for third-party applications and close the identification information corresponding to third-party applications, which greatly facilitates application users in managing authorization for third-party applications. On the other hand, application users can easily and quickly obtain information on the access status of their identification information, which facilitates application users in deciding whether to authorize third-party applications based on the access status of identification information. On the other hand, by combining the authorization status of third-party applications and / or the access status of identification information, it is determined whether to authorize the third-party application to use the data in the application, which can ensure the security of the data in the application and prevent malicious theft by third-party applications.

[0045] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0046] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0047] Figure 1 A flowchart of the authorization method provided in an embodiment of this application is shown;

[0048] Figure 2 A flowchart illustrating another embodiment of the licensing method provided in this application is shown;

[0049] Figure 3 An interactive schematic diagram of the licensing method provided in another embodiment of this application is shown;

[0050] Figure 4 A schematic diagram of the structure of the authorized device provided in an embodiment of this application is shown;

[0051] Figure 5 A schematic diagram of the structure of a computing device provided in an embodiment of this application is shown. Detailed Implementation

[0052] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0053] Figure 1 A flowchart of the authorization method provided in an embodiment of this application is shown. This method is applied to any device with computing capabilities, such as... Figure 1 As shown, the method includes the following steps:

[0054] Step S110: Assign the identification information required for the user to use the second application to the user in the first application.

[0055] In this context, the first application and the second application are different applications. For the first application and its users, the second application is a third-party application. It should be noted that, unless otherwise specified, all users mentioned in the following description refer to users within the first application. Users within the first application can be registered users within the first application. For each registered user of the first application, an identification information required for using the second application is assigned. For example, when a user in the first application authorizes the second application, the identification information required for using the second application is generated for that user.

[0056] Step S120: Receive a target data acquisition request initiated by the second application; wherein the target data acquisition request includes the identification information to be verified and the application information of the second application.

[0057] In this process, the target data acquisition request initiated by the second application is used to obtain target data from other applications, and the identification information to be verified is input by the user. For example, after receiving the input identification information to be verified, the second application initiates a target data acquisition request containing the identification information to be verified and its application information.

[0058] Step S130: Verify whether there is a binding relationship between the identification information to be verified and the application information of the second application.

[0059] After receiving the target data acquisition request from the second application, the identification information to be verified and the application information are parsed out. Based on the corresponding identification information and application information already stored in the database, the binding relationship between the two is verified.

[0060] Step S140: If a binding relationship is verified, authorize the second application to use the target data in the first application.

[0061] If the verification determines that there is a binding relationship between the identification information to be verified and the information of the second application, then the second application is allowed to use the data in the first application.

[0062] According to the authorization method provided in the embodiments of this application, by assigning the identification information required for the user of the first application to use the second application, the second application can be authorized to use the data in the first application as long as it makes a request using the correct identification information. This authorization method is easy to implement, has low development difficulty, and can save time in verifying application permissions.

[0063] Figure 2 A flowchart illustrating another embodiment of the authorization method provided in this application is shown. This method is applied to a service platform with computing capabilities, but is not limited thereto. Figure 2 As shown, the method includes the following steps:

[0064] Step S210: Receive the authorization request from the user in the first application for the second application, and assign the user the identification information required for the user to use the second application in the first application.

[0065] Optionally, a list of second applications may be presented on a designated page within the first application. In response to a user's authorization request for any second application in the first application, the first application may generate that user's authorization request for the second application. Alternatively, a list of second applications may be presented on the gateway page of the service platform. In response to a user's authorization request for any second application in the first application, the first application may generate that user's authorization request for the second application.

[0066] Based on the user's authorization request for the second application in the first application, the user in the first application is assigned the identification information required to use the second application. Specifically, the identification code is generated by the snowflake algorithm and a base-36 conversion, and then maintained in the database. The identification code assigned to the user of the first application is different for different second applications. For the same user of the first application, there will be a unique identification code for each second application authorized by that user.

[0067] Step S220: Establish the binding relationship between the application information and the identification information of the second application, and set the user's authorization status for the second application to the authorization enabled state.

[0068] The application information and identification information of the second application are bound together and stored in the database. At the same time, the user's authorization status for the second application is set to the authorized state.

[0069] In this embodiment, after a user of the first application authorizes a second application, the method also supports the user of the first application canceling authorization for the second application. Specifically, it receives a user's request to close authorization for the second application and adjusts the user's authorization status for the second application from an authorized-on state to an authorized-off state. For example, in response to a user's authorization-closing operation for any second application in the second application list within the first application, a request to close authorization for the second application from the user within the first application is triggered. In this way, application users can flexibly adjust the authorization status for third-party applications according to their own needs.

[0070] Step S230: Receive the user's request to update the identification information of the second application, and update the identification information of the user that is bound to the application information of the second application.

[0071] In this embodiment, after assigning the required identification information for a user of the first application to use the second application, the method also supports the user manually refreshing this identification information. For example, when a user of the first application authorizes the second application for the first time, an identification code corresponding to the user in the second application is generated as ID1. Then, app_id_a (the application information of the second application) is bound to ID1. Subsequently, when the user of the first application requests to refresh the identification code corresponding to the second application, the identification code corresponding to the user in the second application is refreshed to ID2, and app_id_a is bound to ID2. Through the above method, application users can actively refresh the identification information required to use third-party applications according to their own needs, which can prevent the identification information from being saved, thereby ensuring the security of data in the application.

[0072] Furthermore, the method in this embodiment also supports application users disabling their identification information corresponding to third-party applications. Specifically, it receives a user's request to invalidate identification information for a second application and performs invalidation processing on the identification information. For example, if a user of a first application wants to completely revoke authorization for a second application, they can perform an identification invalidation operation on any second application in the second application list, thereby invalidating the identification information required for the user of the first application to use the second application. Through this method, application users can invalidate the identification information generated by authorizing third-party applications according to their own needs.

[0073] The method in this embodiment also allows application users to view the usage of their identification information in third-party applications. Specifically, it receives a user's request to view call records and returns to the user the frequency and / or time information of the identification information being called. Specifically, it statistically analyzes the frequency and / or time information of received target data retrieval requests containing identification information to obtain the frequency and / or time information of the identification information being called. In this way, application users can know the usage of their identification information corresponding to third-party applications, facilitating their decision-making regarding whether any abnormalities have occurred during the call.

[0074] Step S240: Receive a target data acquisition request initiated by the second application. The target data acquisition request includes the identification information to be verified and the application information of the second application.

[0075] The application information for the second application is pre-registered and generated on the service platform. Specifically, it receives registration requests from application developers, assigns developer information to the application developers, and assigns application information to each application belonging to the application developers. Application developers register on the service platform, which assigns them unique developer information (access_key_id) for network request verification, enabling the service platform to verify the identity of third parties. Simultaneously, it assigns unique application information (app_id) to each application of the application developer.

[0076] The second application initiates a target data acquisition request to obtain target data from other applications. The second application receives a verification identifier code through a preset entry point and simultaneously obtains its own application information (app_id). The second application then sends a target data acquisition request carrying the verification identifier code and application information to the service platform. The second application can read the application information from a local file or request it from the server; this application does not limit the specific method used.

[0077] Step S250: Query the authorization status of the user in the first application corresponding to the identifier information to be verified for the second application.

[0078] If the authorization status is found to be "authorization enabled", proceed to step S260; if the authorization status is found to be "authorization cancelled", proceed to step S280.

[0079] Specifically, when assigning identification information required for a user to use the second application to a user in the first application, the correspondence between the identification information and the user in the first application is saved. Then, the user in the first application is found through the identification information to be verified, and the authorization status of the user in the first application for the second application is obtained.

[0080] Step S260: Verify whether there is a binding relationship between the identification information to be verified and the application information of the second application.

[0081] If a binding relationship is found, proceed to step S270; if no binding relationship is found, proceed to step S280.

[0082] If the user's authorization status for the second application is enabled, the system compares the bound identifiers and application information stored in the database to determine if any identifier in the application information carried in the target data retrieval request matches the identifier to be verified. If yes, it is determined that the application information of the second application has a binding relationship with the identifier to be verified, and the second application requesting data retrieval is authorized to use the target data in the first application. If no, it is determined that the identifier to be verified and the application information of the second application do not have a binding relationship, and the second application requesting data retrieval is not authorized to use the target data in the first application.

[0083] In one alternative approach, the step of querying the user's authorization status for the second application in the first application corresponding to the identifier information to be verified is performed after the step of verifying the binding relationship.

[0084] In one optional approach, a binding relationship is established between the application information, developer information, and identification information of the second application. The target data retrieval request initiated by the second application includes the identification information to be verified, the information of the second application, and the developer information of the second application. During verification, the identification information, application information, and application developer information carried in the target data retrieval request are parsed out, and the existence of a binding relationship among the three is verified. In this way, third-party applications must provide correct identification information, application identification, and application developer identification simultaneously to use the data of another application, increasing the difficulty of passing the verification and preventing malicious theft of application data.

[0085] In one optional approach, firstly, matching target developer information is found in the service platform based on the developer information of the second application. Then, matching target application information is found among the application information bound to the target developer information based on the application information of the second application. Finally, it is checked whether the target application information is bound to identification information that matches the identification information to be verified. This step-by-step comparison improves verification efficiency.

[0086] In one optional approach, after verifying the binding relationship between the identifier information to be verified and the application information of the second application, the frequency and / or time information of the identifier information to be verified being called is obtained. If the call is determined to be normal based on the frequency and / or time information, the second application is authorized to use the target data in the first application. Specifically, the frequency and / or time information of receiving target data acquisition requests containing the identifier information to be verified are statistically analyzed to obtain the frequency and / or time information of the identifier information to be verified being called. The call is determined to be normal based on the frequency and / or time of the identifier information to be verified being called, for example, whether the frequency is within a normal range and / or the time is within a normal time period. If so, the call is determined to be normal, and the second application is allowed to obtain the target data in the first application. In this way, it is possible to automatically determine whether the identifier information is called normally, which is equivalent to determining whether the use of in-application data by a third party is normal. Only when the call is normal is the third party allowed to use in-application data, thus ensuring the security of application data.

[0087] Step S270: Authorize the second application to use the target data in the first application.

[0088] For example, retrieve the target data from the first application and return it to the second application.

[0089] The method in this embodiment can be applied to an authorized login scenario. Specifically, this step involves authorizing a second application to log in using the user's login verification information from the first application.

[0090] Step S280: Return a response indicating that data retrieval failed to the second application.

[0091] If the user's authorization status for the second application is closed, or if the user's authorization status for the second application is open but the identification information to be verified is not bound to the application information of the second application, or if an abnormal call is determined based on frequency information and / or time information, then a data retrieval failure response will be returned to the second application.

[0092] According to the authorization method provided in the embodiments of this application, on the one hand, by assigning the identification information required for the application user (i.e., the user in the first application) to use other third-party applications (the second application), the third-party application can be authorized to use the target data in the application as long as it makes a request using the correct identification information. This authorization method is easy to implement, has low development difficulty, and can save time in verifying application permissions. On the other hand, it supports the application user to actively refresh the identification information required for using the third-party application, which can prevent the third-party application from saving the identification information to steal data in the application. Furthermore, it supports the application user to enable or cancel the authorization of the third-party application and close the identification information corresponding to the third-party application, which greatly facilitates the application user in managing the authorization of the third-party application. On the other hand, the application user can easily and quickly obtain the status of its identification information being called, which makes it easier for the application user to decide on the authorization of the third-party application based on the status of the identification information being called. On the other hand, it also combines the authorization status of the third-party application and / or the status of the identification information to determine whether to authorize the third-party application to use the data in the application, which can ensure the security of the data in the application and prevent the malicious theft by the third-party application.

[0093] Figure 3 An interactive schematic diagram of the authorized method provided in another embodiment of this application is shown, such as... Figure 3 As shown, the specific steps include the following:

[0094] Step 1: The user requests an identification code from the open platform gateway. Here, "user" refers to a user in an application different from the third-party application, such as a user of a live streaming application. The third-party application refers to a game application, which is a third-party application of the live streaming application. The user of the live streaming application requests authorization for the game application from the open platform gateway to obtain an identification code corresponding to that game application.

[0095] Step 2: The open platform gateway returns the assigned identifier code to the user of the live streaming application.

[0096] Steps 1 and 2 above describe the implementation method in the scenario where a user requests to obtain an identification code.

[0097] Step 3: The third-party application uses the identifier code to request activation from the open platform gateway. The identifier code is entered by the user.

[0098] Step 4: The open platform gateway verifies whether the identifier is valid and whether there is a binding relationship between the identifier and the third-party application. Specifically, it verifies the relationship by checking the bound identifiers and application identifiers already stored in the database.

[0099] Step 5: After successful verification, the open platform gateway records the frequency and timing of third-party applications calling this identifier code to determine if the calls are abnormal. Whenever a third-party application requests startup using this identifier code, the time and frequency of the code being called are recorded.

[0100] Step 6: Return the application launch result. Specifically, if the call is determined to be abnormal, a launch failure result is returned to the third-party application, indicating that the third-party application should not be launched; if the call is determined to be normal, a launch success result is returned to the third-party application, indicating that the third-party application should be launched.

[0101] Steps 3-6 describe the specific implementation methods for scenarios where third-party applications use identifier codes to launch.

[0102] Step 7: The third-party application uses the identifier code to request the target data from the live streaming application from the open gateway platform. The request carries the identifier code and its application identifier.

[0103] Step 8: The open platform gateway verifies whether the identifier is valid and whether there is a binding relationship between the identifier and the third-party application. Specifically, it verifies the relationship by checking the stored bound identifiers and application identifiers.

[0104] Step 9: After successful verification, the open platform gateway records the frequency and timing of third-party applications calling this identifier code to determine if the calls are abnormal. Whenever a third-party application uses this identifier code to request data, the time and frequency of its use are recorded.

[0105] Step 10: If the call is successful, the open platform gateway returns the target data of the live streaming application to the third-party application, such as the streamer's nickname, live stream comments, live stream interaction information, etc.

[0106] Steps 7-10 describe the specific implementation methods by which third-party applications use identifier codes to obtain target data in live streaming applications.

[0107] Step 11: The live streaming application user requests the open platform gateway to view the identifier call record.

[0108] Step 12: The open platform gateway returns the frequency and time of the identification code being called to the live streaming application user.

[0109] Step 13: The live streaming application user requests the open platform gateway to refresh or disable the identifier code.

[0110] Step 14: The open platform gateway refreshes the user's identifier code according to the refresh request, and invalidates the existing identifier code according to the close identifier code request.

[0111] Step 15: The open platform gateway returns the refreshed identifier code or failure handling result to the live streaming application user.

[0112] Steps 11-14 describe the specific implementation methods for users to view call records, refresh, and close the identifier code.

[0113] Figure 4 A schematic diagram of the structure of the authorized device provided in an embodiment of this application is shown. For example... Figure 4 As shown, the device includes:

[0114] The allocation module 41 is adapted to allocate identification information required by the user to use the second application to the user in the first application;

[0115] The receiving module 42 is adapted to receive a target data acquisition request initiated by the second application; wherein the target data acquisition request includes the identification information to be verified and the application information of the second application;

[0116] Verification module 43 is adapted to verify whether there is a binding relationship between the identification information to be verified and the application information of the second application;

[0117] The authorization module 44 is adapted to authorize the second application to use the target data in the first application if a binding relationship is detected.

[0118] In one alternative approach, the target data acquisition request further includes: developer information of the second application; and verification module 43, which is further adapted to verify whether there is a binding relationship between the identification information to be verified, the application information of the second application, and the developer information of the second application.

[0119] In one alternative embodiment, the device further includes: a query module, adapted to query the authorization status of a user in the first application corresponding to the identification information to be verified for the second application; and an authorization module 44, adapted to authorize the second application to use the target data in the first application if the authorization status is found to be enabled and a binding relationship is verified.

[0120] In one alternative embodiment, the apparatus further includes a feedback module adapted to return a data retrieval failure response to the second application if the queried authorization status is an authorization-off state.

[0121] In an alternative embodiment, the allocation module 41 is further adapted to: receive an authorization request from a user in the first application to the second application, allocate identification information required for the user to use the second application to the user in the first application; establish a binding relationship between the application information of the second application and the identification information, and set the user's authorization status for the second application to the authorization enabled state.

[0122] In one alternative embodiment, the receiving module 42 is further adapted to: receive a user's request to update the identification information of the second application; the device further includes: an updating module, adapted to update the identification information of the user that is bound to the application information of the second application.

[0123] In one alternative embodiment, the receiving module 42 is further adapted to: receive a user's request to close the authorization for the second application; and the allocation module 41 is further adapted to: change the user's authorization status for the second application from the authorization open state to the authorization closed state.

[0124] In an alternative embodiment, the receiving module 42 is further adapted to: receive a user's request for invalidation of identification information for the second application; and the allocation module 41 is further adapted to: perform invalidation processing on the identification information.

[0125] In one alternative embodiment, the apparatus further includes: an acquisition module, adapted to acquire frequency information and / or time information of the verification identifier information being invoked; and an authorization module 44, further adapted to: if it is determined that the invocation is normal based on the frequency information and / or time information, authorize the second application to use the target data in the first application.

[0126] In one alternative approach, the feedback module is further adapted to: if a call exception is determined based on frequency information and / or time information, return a response indicating data retrieval failure to the second application.

[0127] In an alternative manner, the authorization module 44 is further adapted to: authorize the second application to log in using the target data in the first application.

[0128] In one alternative embodiment, the receiving module 42 is further adapted to: receive a registration request from an application developer; and the allocation module 41 is further adapted to: allocate developer information to the application developer and allocate application information to each application belonging to the application developer.

[0129] In an alternative embodiment, the receiving module 42 is further adapted to: receive a user's request to view the call record; the feedback module is further adapted to: return to the user the frequency information and / or time information of the call to the identification information.

[0130] This application provides a non-volatile computer storage medium storing at least one executable instruction that can execute the authorized method in any of the above method embodiments.

[0131] Figure 5 The diagram shows a structural schematic of an embodiment of the computing device of this application. The specific embodiments of this application do not limit the specific implementation of the computing device.

[0132] like Figure 5As shown, the computing device may include: a processor 502, a communications interface 504, a memory 506, and a communications bus 508.

[0133] The processor 502, communication interface 504, and memory 506 communicate with each other via communication bus 508. Communication interface 504 is used to communicate with other network elements such as clients or other servers. The processor 502 executes program 510, specifically performing the relevant steps described in the above-described embodiment of the licensing method for computing devices.

[0134] Specifically, program 510 may include program code that includes computer operation instructions.

[0135] Processor 502 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. The computing device includes one or more processors, which may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0136] Memory 506 is used to store program 510. Memory 506 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0137] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used in conjunction with the teachings herein. The required structure for constructing such systems is apparent from the above description. Furthermore, the embodiments of this application are not directed to any particular programming language. It should be understood that the content of this application described herein can be implemented using various programming languages, and the above description of specific languages ​​is for the purpose of disclosing the best mode of implementation of this application.

[0138] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of this application may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0139] Similarly, it should be understood that, in order to simplify this application and aid in understanding one or more of the various inventive aspects, features of the embodiments of this application are sometimes grouped together in a single embodiment, figure, or description thereof in the above description of exemplary embodiments of this application. However, this method of disclosure should not be construed as reflecting an intention that the claimed application requires more features than expressly recited in each claim. Rather, as reflected in the following claims, inventive aspects lie in fewer than all features of a single foregoing disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into that detailed description, wherein each claim itself is a separate embodiment of this application.

[0140] Those skilled in the art will understand that modules in the device of the embodiments can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiments can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0141] Furthermore, those skilled in the art will understand that although some embodiments herein include certain features included in other embodiments but not others, combinations of features from different embodiments are intended to be within the scope of this application and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[0142] The various component embodiments of this application can be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will understand that microprocessors or digital signal processors (DSPs) can be used in practice to implement some or all of the functions of some or all of the components according to the embodiments of this application. This application can also be implemented as a device or apparatus program (e.g., a computer program and computer program product) for performing part or all of the methods described herein. Such an implementation of this application can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0143] It should be noted that the above embodiments are illustrative of this application and not restrictive, and those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. This application can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be construed as limiting the order of execution.

Claims

1. An authorization method, comprising: Assign the identification information required for the user to use the second application to the user in the first application; Receive a target data acquisition request initiated by a second application; wherein the target data acquisition request includes a verification identifier and application information of the second application, and the second application receives the input verification identifier; Verify whether there is a binding relationship between the identification information to be verified and the application information of the second application; If a binding relationship is detected, the second application is authorized to use the target data in the first application.

2. The method according to claim 1, wherein, The target data acquisition request also includes: developer information of the second application; The step of verifying whether there is a binding relationship between the identification information to be verified and the application information of the second application further includes: Verify whether there is a binding relationship between the identification information to be verified, the application information of the second application, and the developer information of the second application.

3. The method according to claim 1, wherein, After receiving the target data acquisition request initiated by the second application, the method further includes: Query the authorization status of the user in the first application corresponding to the identifier information to be verified for the second application; The authorization of the second application to use the target data in the first application further includes: If the authorization status is found to be enabled and a binding relationship is verified, the second application is authorized to use the target data in the first application.

4. The method according to claim 3, wherein, The method further includes: If the authorization status is found to be closed, a data retrieval failure response is returned to the second application.

5. The method according to claim 1, wherein, The step of allocating the identification information required for a user to use the second application to the user in the first application further includes: Receive the authorization request from the user in the first application for the second application, and assign the user in the first application the identification information required for the user to use the second application; Establish a binding relationship between the application information of the second application and the identification information, and set the user's authorization status for the second application to the authorization enabled state.

6. The method according to claim 5, wherein, After establishing the binding relationship between the application information of the second application and the identification information, the method further includes: Receive the user's request to update the identification information of the second application, and update the identification information of the user that is bound to the application information of the second application.

7. The method according to claim 5 or 6, wherein, After establishing the binding relationship between the application information of the second application and the identification information, the method further includes: Receive the user's request to disable authorization for the second application; Change the user's authorization status for the second application from authorized to enabled to authorized to disabled.

8. The method according to any one of claims 1-5, wherein, After allocating the identification information required for a user to use the second application to the user in the first application, the method further includes: Receive the user's request to invalidate the identification information for the second application, and perform invalidation processing on the identification information.

9. The method according to any one of claims 1-5, wherein, After verifying the binding relationship between the identifier information to be verified and the application information of the second application, the method further includes: Obtain the frequency and / or time information of the call to the identifier information to be verified; The authorization of the second application to use the target data in the first application further includes: If the call is determined to be normal based on the frequency information and / or time information, the second application is authorized to use the target data in the first application.

10. The method according to claim 9, wherein, The method further includes: If a call anomaly is determined based on the frequency information and / or time information, a data retrieval failure response is returned to the second application.

11. The method according to any one of claims 1-5, wherein, The authorization of the second application to use the target data in the first application further includes: Authorize the second application to use the target data in the first application to log in.

12. The method according to claim 2, wherein, The method further includes: Receive registration requests from application developers; Assign developer information to the application developer and assign application information to each application belonging to the application developer.

13. The method according to any one of claims 1-5, wherein, The method further includes: Receive the user's request to view call records; Return to the user the frequency and / or time information of when the identification information is invoked.

14. A licensing device, comprising: The allocation module is adapted to allocate identification information required by a user to use a second application to a user in the first application. The receiving module is adapted to receive a target data acquisition request initiated by a second application; wherein the target data acquisition request includes a verification identifier and application information of the second application, and the second application receives the input verification identifier; The verification module is adapted to verify whether there is a binding relationship between the identification information to be verified and the application information of the second application; The authorization module is adapted to authorize the second application to use the target data in the first application if a binding relationship is detected.

15. A computing device, comprising: The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus. The memory is used to store at least one executable instruction that causes the processor to perform the operation corresponding to the authorized method as described in any one of claims 1-13.

16. A computer storage medium storing at least one executable instruction that causes a processor to perform an operation corresponding to the authorized method as described in any one of claims 1-13.

17. A computer program product comprising at least one executable instruction that causes a processor to perform an operation corresponding to the authorized method as described in any one of claims 1-13.

Images