Application login methods, devices, storage media and electronic devices

Abstract

This disclosure provides an application login method, application login device, computer storage medium, and electronic device, relating to the field of game technology. The application login method includes: for a login request from an application to be logged in, determining the target interface address corresponding to the login request from a pre-configured plurality of interface addresses; wherein the plurality of interface addresses correspond to service interfaces of a plurality of third-party applications; determining the target third-party application based on the service interface corresponding to the target interface address, wherein the target third-party application is any one of the plurality of third-party applications; obtaining first account information corresponding to the target third-party application; generating a first authorization token based on the first account information, so that the target third-party application synchronizes the first authorization token to the application to be logged in through a constructed inter-process communication channel for login. This disclosure can reduce system lag or even restarts during application login, improving the smoothness of game operation.

Description

Technical Field

[0001] This disclosure relates to the field of game technology, and more particularly to an application login method, an application login device, a computer storage medium, and an electronic device. Background Technology

[0002] In most online games, when players enter the game application through a mobile client, they usually switch the game interface to landscape mode to display the game screen horizontally. Landscape mode not only presents a larger game screen with the optimal aspect ratio but also allows for two-handed operation, similar to a game controller. Upon entering the game interface, players are first redirected to a third-party application page to authorize and log in to their account.

[0003] Currently, during the process of the game application redirecting to a third-party application for account authorization login, the system will switch from the landscape display mode of the game application to the portrait display mode of the third-party authorization login page. After the player selects the third-party account authorization login, it will switch back to the landscape display mode of the game application to enter the game.

[0004] However, during the login process of the aforementioned applications, the repeated switching between portrait and landscape modes poses a challenge to system performance, which can easily lead to system lag or even restarts, thereby affecting the smoothness of game operation. Summary of the Invention

[0005] This disclosure provides an application login method, application login device, computer storage medium, and electronic device, thereby reducing abnormal issues such as system lag or even restart during application login and improving the smoothness of game operation.

[0006] In a first aspect, one embodiment of this disclosure provides an application login method, the method comprising: for a login request of an application to be logged in, determining a target interface address corresponding to the login request from a plurality of pre-configured interface addresses; wherein the plurality of interface addresses correspond to service interfaces of a plurality of third-party applications; determining a target third-party application based on the service interface corresponding to the target interface address, wherein the target third-party application is any one of the plurality of third-party applications; obtaining first account information corresponding to the target third-party application, and generating a first authorization token based on the first account information, so that the target third-party application synchronizes the first authorization token to the application to be logged in through the Android Interface Definition Language for login.

[0007] Secondly, one embodiment of this disclosure provides an application login device, which includes: an interface address determination module for determining a target interface address corresponding to a login request from a plurality of pre-configured interface addresses for a login request of an application to be logged in; wherein the plurality of interface addresses correspond to service interfaces of a plurality of third-party applications; an application determination module for determining a target third-party application based on the service interface corresponding to the target interface address, wherein the target third-party application is any one of the plurality of third-party applications; and a token generation module for obtaining first account information corresponding to the target third-party application and generating a first authorization token based on the first account information, so that the target third-party application can synchronize the first authorization token to the application to be logged in through the Android Interface Definition Language for login.

[0008] Thirdly, one embodiment of this disclosure provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the application login method described above.

[0009] Fourthly, one embodiment of this disclosure provides an electronic device, including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the application login method described above by executing the executable instructions.

[0010] The technical solution disclosed herein has the following beneficial effects:

[0011] The above application login method determines the target interface address corresponding to the login request from a pre-configured pool of multiple interface addresses for the login request of the application to be logged in; wherein, the multiple interface addresses correspond to the service interfaces of multiple third-party applications; the target third-party application is determined based on the service interface corresponding to the target interface address, and the target third-party application can be any one of the multiple third-party applications; the first account information corresponding to the target third-party application is obtained, and a first authorization token is generated based on the first account information, so that the target third-party application can synchronize the first authorization token to the application to be logged in through the Android Interface Definition Language to log in.

[0012] On the one hand, this method provides a service interface for each third-party application. By pre-synchronizing the service address of each third-party application's service interface on the platform server, process communication between the application to be logged in and the third-party application can be quickly achieved. Furthermore, a communication channel is established between the application to be logged in and the third-party application through an inter-process communication mechanism. This allows the authorization token to directly exchange data through the established inter-process communication channel, avoiding the need for page redirection to obtain relevant data in related technologies. Simultaneously, the third-party application's account information is converted into an authorization token instead of a password on the platform server, allowing the third-party application to obtain authorization permissions without starting up. This avoids the technical problems of system lag or even restarts caused by page redirection in related technologies, thus improving the smoothness of game operation. On the other hand, the above method achieves silent login of the application to be logged in without page switching, thereby reducing the time users spend waiting to log in and further improving the efficiency of application login.

[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0014] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0015] Figure 1 (a)- Figure 1 (c) A schematic diagram illustrating a game application login scenario in this exemplary embodiment;

[0016] Figure 2 This schematic diagram illustrates a system architecture diagram of an application login system in this exemplary embodiment;

[0017] Figure 3 This schematically illustrates a flowchart of an application login method in this exemplary embodiment;

[0018] Figure 4 This schematically illustrates a flowchart of a process for reapplying for a second authorization token in this exemplary embodiment;

[0019] Figure 5 This schematically illustrates a flowchart of a process for reapplying for a third authorization token in this exemplary embodiment;

[0020] Figure 6This schematically illustrates a flowchart of a complete application login method in this exemplary embodiment;

[0021] Figure 7 This schematic diagram illustrates the structure of an application login device in this exemplary embodiment.

[0022] Figure 8 This schematic diagram illustrates another application login device structure in this exemplary embodiment;

[0023] Figure 9 The schematic diagram illustrates the structure of an electronic device in this exemplary embodiment. Detailed Implementation

[0024] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this disclosure more comprehensive and complete, and to fully convey the concept of exemplary embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0025] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0026] The flowchart shown in the attached diagram is merely an illustrative example and does not necessarily include all steps. For example, some steps may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0027] To help those skilled in the art better understand the technical solutions of this disclosure, the relevant content involved in the technical solutions of this disclosure will be introduced below.

[0028] (1) Android Interface Definition Language (AIDL): Each application corresponds to a process. Since different processes cannot share memory, mechanisms are needed to enable data communication between different processes. AIDL is an IDL language used to generate code that enables inter-process communication (IPC) between two processes on an Android device, thereby establishing an inter-process communication channel and realizing data exchange between applications. If an operation of an object in another process (e.g., a Service) needs to be called from one process (e.g., an Activity), serializable parameters can be generated using the AIDL mechanism.

[0029] (2) Authorization token: Used to replace password as login credentials.

[0030] (3) Inter-process communication (IPC): Techniques or methods for transferring data or signals between at least two processes or threads. Each process has independent system resources and is isolated from others. IPC enables different processes to access computer resources and coordinate their work. For example, two applications using IPC can be classified as client and server (master-slave architecture). The client process requests data, and the server responds to the client's data request. Some applications are both servers and clients. IPC techniques include message passing, synchronization, shared memory, and remote procedure calls, and are a standard Unix communication mechanism.

[0031] The application login method provided by the exemplary embodiments of this disclosure can be applied to application scenarios where any application client uses the account information of a third-party application to log in to the application.

[0032] With the rapid development of internet technology, in order to ensure the security of systems and network data and to distinguish the identity information of each user, users usually need to be authenticated when performing certain online operations. For example, taking a game application as an example, in order to distinguish and authenticate the identities of each player, players usually need to authorize login through the account information corresponding to the third-party application after entering the game page.

[0033] It should be noted that the application to be logged in can be any type of application, such as a game application, a shopping application, a short video application, a medical application, or other functional applications. This embodiment of the disclosure does not impose any special restrictions on the type of application to be logged in.

[0034] This disclosure uses a game application as an example. Figure 1This illustration schematically depicts a game application login scenario in this exemplary embodiment. For online games within a game client, to display a larger game screen and provide the best gaming experience to players in the game client's graphical user interface, while also facilitating two-handed operation, the game screen is typically displayed in landscape mode. When a player enters the game, the screen will be displayed first, as shown below. Figure 1 (a) shows the game login page.

[0035] Reference Figure 1 (a) The game's login page can contain multiple third-party application login controls for authorized login. When a player clicks any of these controls, they are redirected to the corresponding third-party application's login page, which typically looks like this: Figure 1 (b) is a portrait-oriented display mode, and the login page includes information such as the login account, the image corresponding to the login account, the name of the application to be logged in, login controls, and controls for switching to other accounts. After confirming that the third-party account information is correct, the player can click as follows: Figure 1 (b) After logging in, you will be redirected again to [the login page / location]. Figure 1 (c) shows the game login page in landscape mode and generates a successful login message so that players can successfully log in and enter the game scene.

[0036] It should be noted that the above prompt message can also be generated when login fails, so that players can re-authorize and log in.

[0037] Therefore, when authorizing login to a game application through a third-party account on a third-party application page, the system generates multiple page switches and screen rotations between landscape and portrait display modes, resulting in a poor visual experience for players. Furthermore, on mobile devices with slightly lower performance, these multiple page jumps and landscape / portrait switching pose a challenge to game performance, potentially causing game page errors or even game application restarts. In addition, third-party application pages typically offer multiple third-party applications for authorization login. Players must manually select one for authorization login, and the game application launches with a splash screen, requiring a wait before accessing the third-party application page for authorization login. This makes the authorization login process cumbersome and time-consuming.

[0038] This disclosure, taking into account the aforementioned problems, proposes an application login method. During the authorization login process of the application client to be logged in using the account information of a third-party application, this method typically provides one or more third-party applications for the player to choose from. Once the player selects a third-party application, they can launch that application through its client. Each third-party application corresponds to a third-party account (which may include an identity document (ID) and a password).

[0039] The platform server pre-configures multiple interface addresses, each corresponding to a service interface of a third-party application. When a login request from an application to be logged in is received, the target interface address corresponding to the login request is determined from the pre-configured multiple interface addresses. Based on the service interface corresponding to the target interface address, the target third-party application is identified. The first account information corresponding to the target third-party application is obtained, and a first authorization token is generated based on the first account information. This allows the target third-party application to synchronize the first authorization token to the application to be logged in via an inter-process communication channel to log in.

[0040] On the one hand, this method provides a service interface for each third-party application. By pre-synchronizing the service address of each third-party application's service interface on the platform server, process communication between the application to be logged in and the third-party application can be quickly achieved. Furthermore, a communication channel is established between the application to be logged in and the third-party application through an inter-process communication mechanism. This allows the authorization token to directly exchange data through the established inter-process communication channel, avoiding the need for page redirection to obtain relevant data in related technologies. Simultaneously, the third-party application's account information is converted into an authorization token instead of a password on the platform server, allowing the third-party application to obtain authorization permissions without starting up. This avoids the technical problems of system lag or even restarts caused by page redirection in related technologies, thus improving the smoothness of game operation. On the other hand, the above method achieves silent login of the application to be logged in without page switching, thereby reducing the time users spend waiting to log in and further improving the efficiency of application login.

[0041] To address the aforementioned problems, this disclosure proposes an application login method and apparatus, which can be applied to... Figure 2 In the system architecture of the exemplary application environment shown.

[0042] Figure 2 This diagram schematically illustrates a system architecture diagram of an application login system in this exemplary embodiment. Figure 2As shown, the system architecture 200 includes a terminal device 201, a network 204, and a platform server 205. The terminal device 201 includes a client application to be logged in 202 and a third-party application client 203. The client application to be logged in 202 can run an application that requires authorization to log in, such as a game application, a shopping application, or a short video application. The third-party application client 203 runs a third-party application with corresponding account information. The third-party application authorizes the application to be logged in, allowing the application to verify the user's identity using the account information corresponding to the third-party application.

[0043] The number of the aforementioned application client 202 to be logged in and third-party application client 203 can be one or more. The network 204 serves as the medium for providing a communication link between the application client 201 to be logged in, the third-party application client 202, and the platform server 205. The network 204 can include various connection types, such as wired or wireless communication links or fiber optic cables. The terminal device 201 integrated with the application client 202 to be logged in and the third-party application client 203 can be, for example, an application running on a smartphone, a PDA, a laptop, a server, a desktop computer, or any other network-enabled computing device, but is not limited to these.

[0044] It should be understood that Figure 2 The terminal device 201, network 204, and platform server 205, as well as the number of application clients 202 and third-party application clients 203 waiting to log in within terminal device 201, are merely illustrative. Depending on implementation needs, there can be any number of terminal devices, networks, and servers. For example, platform server 204 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0045] The application login method provided in this embodiment can be executed on the platform server 204, and correspondingly, the application login device can be configured on the platform server 204. The application login method provided in this embodiment can also be executed on a terminal device, and correspondingly, the application login device can also be configured on the terminal device. The application login method provided in this embodiment can also be partially executed on the platform server 204 and partially on the terminal device; correspondingly, some modules of the application login device can be configured on the platform server 204, and some modules can be configured on the terminal device.

[0046] For example, in one exemplary embodiment, the terminal device integrates at least one application client to be logged in and a third-party application client. The application to be logged in can be run through the application client to be logged in, and the third-party application can be run through the third-party application client. Each of the aforementioned third-party applications corresponds to account information, wherein the account information includes at least the username and password of the account.

[0047] For login requests from applications awaiting login, the platform server 204 determines the target interface address from a pool of pre-configured interface addresses. These multiple interface addresses correspond to service interfaces of multiple third-party applications. The target third-party application is determined based on the service interface corresponding to the target interface address. The target third-party application can be any one of the multiple third-party applications. The server obtains the first account information corresponding to the target third-party application and generates a first authorization token based on the first account information. This allows the target third-party application to synchronize the first authorization token to the application awaiting login via a constructed inter-process communication channel.

[0048] It should be noted that the number of application clients and third-party application clients mentioned above is merely exemplary. Depending on implementation needs, there can be any number of application clients and third-party application clients. For example, when a player enters the game through any of the aforementioned terminal devices, they need to authorize login to the game application using the account information corresponding to the third-party application.

[0049] Specifically, players can run an application to be logged in through the client. After the user triggers the login confirmation control on the graphical user interface provided by the client, a login request is sent to the platform server. Upon receiving the login request, the platform server calls the remote service interface of the target application. This allows the platform server to generate and send a first authorization token to the third-party application client based on the target account information of the target application. The first authorization token is then returned to the client to be logged in through a constructed inter-process communication channel, enabling the application to log in using the target account information based on the first authorization token.

[0050] However, those skilled in the art will readily understand that the above application scenarios are merely illustrative and are not intended to limit the scope of this exemplary embodiment.

[0051] The following example uses the aforementioned platform server 204 as the execution subject, and illustrates how the application login method is applied to the aforementioned platform server 204. Figure 3 A flowchart illustrating an application login method in this exemplary embodiment is shown schematically. See also... Figure 3 The application login method provided in this embodiment includes the following steps S301-S303:

[0052] Step S301: For the login request of the application to be logged in, determine the target interface address corresponding to the login request from multiple pre-configured interface addresses; wherein, the multiple interface addresses correspond to the service interfaces of multiple third-party applications.

[0053] Step S302: Determine the target third-party application based on the service interface corresponding to the target interface address. The target third-party application is any one of multiple third-party applications.

[0054] Step S303: Obtain the first account information corresponding to the target third-party application, and generate a first authorization token based on the first account information, so that the target third-party application can synchronize the first authorization token to the application to be logged in through the constructed inter-process communication channel.

[0055] In some embodiments of the present disclosure, the technical solutions provided involve determining the target interface address corresponding to the login request from a plurality of pre-configured interface addresses for the login request of the application to be logged in; wherein the plurality of interface addresses correspond to the service interfaces of a plurality of third-party applications; determining the target third-party application based on the service interface corresponding to the target interface address, wherein the target third-party application is any one of the plurality of third-party applications; obtaining the first account information corresponding to the target third-party application, and generating a first authorization token based on the first account information, so that the target third-party application can synchronize the first authorization token to the application to be logged in through the Android Interface Definition Language for login.

[0056] On the one hand, this method provides a service interface for each third-party application. By pre-synchronizing the service address of each third-party application's service interface on the platform server, process communication between the application to be logged in and the third-party application can be quickly achieved. Furthermore, a communication channel is established between the application to be logged in and the third-party application through an inter-process communication mechanism. This allows the authorization token to directly exchange data through the established inter-process communication channel, avoiding the need for page redirection to obtain relevant data in related technologies. Simultaneously, the third-party application's account information is converted into an authorization token instead of a password on the platform server, allowing the third-party application to obtain authorization permissions without starting up. This avoids the technical problems of system lag or even restarts caused by page redirection in related technologies, thus improving the smoothness of game operation. On the other hand, the above method achieves silent login of the application to be logged in without page switching, thereby reducing the time users spend waiting to log in and further improving the efficiency of game application login.

[0057] The following will describe in conjunction with specific embodiments Figure 3 The specific implementation methods of each step in the illustrated embodiment are described in detail below:

[0058] In step S301, for the login request of the application to be logged in, the target interface address corresponding to the login request is determined from a plurality of pre-configured interface addresses; wherein, the plurality of interface addresses correspond to the service interfaces of a plurality of third-party applications.

[0059] This includes running applications awaiting authorization through the application client to be logged in, and running third-party applications through the third-party application client.

[0060] Taking a game application as an example, after a player enters the game application page through the game client, the following is usually displayed: Figure 1 The game login page shown in (a) allows players to authorize login using a third-party account associated with the third-party application, enabling them to play the game with their real names using the account information associated with that third-party account. Therefore, after a player launches the game application through the game client and triggers the login operation, the game application needs to send a login request to the platform server in order to call the service interface provided by the corresponding target third-party application for authorization.

[0061] It should be noted that the number of game applications and third-party applications can be arbitrary, and this disclosure does not impose any special restrictions on this.

[0062] In some example embodiments of this disclosure, when the application client to be logged in responds to the login confirmation operation for the third-party application, it sends a login request to the platform server so that the platform server can determine the target interface address corresponding to the login request from a plurality of pre-configured interface addresses, so as to realize the process of inter-process communication according to the service interface corresponding to the target interface address.

[0063] For example, third-party applications can exchange data with other applications through the provided service interfaces. Therefore, third-party applications define interface addresses through the provided service interfaces and synchronize the defined interface addresses to the platform server through the AIDL mechanism.

[0064] For example, if the platform server is connected to three third-party applications: application client A (running third-party application A, corresponding to the remote service interface address a), application client B (running third-party application B, corresponding to the remote service interface address b), and application client C (running third-party application C, corresponding to the remote service interface address c), then each third-party application client will upload interface address a, interface address b, and interface address c to the platform server through the AIDL mechanism. This allows the platform server to call the remote service interface through the interface address of a third-party application when it receives a login request for a specific third-party application.

[0065] When the client application to be logged in responds to the login confirmation operation for the third-party application B, it sends a login request for the third-party application B to the platform server. The platform server obtains the interface address b through the third-party information interface, and then calls the remote service interface provided by the third-party application B so that data can be exchanged subsequently through the remote service interface provided by the third-party application B.

[0066] When there is only one third-party application, the interface address corresponding to that third-party application is directly determined as the target interface address; when there are multiple third-party applications, it is necessary to determine the interface address corresponding to one of the third-party applications as the target interface address.

[0067] The following will describe the process of determining the interface address of a third-party application as the target interface address from multiple third-party applications, using specific embodiments.

[0068] When performing step S301 to determine the target interface address corresponding to the login request from multiple pre-configured interface addresses, the authorization weights of multiple third-party applications are determined based on the historical login data of multiple third-party applications corresponding to multiple interface addresses; the interface address with the highest authorization weight is determined as the target interface address.

[0069] Historical login data can include login frequency, most recent login time, login duration, and other data.

[0070] In some example embodiments of this disclosure, when third-party application A is logging into other applications while third-party application B is not logged in, it can be determined that the weight value of third-party application B is greater than that of third-party application A.

[0071] In some example embodiments of this disclosure, the total number of times the application to be logged in uses each third-party application to log in is counted, and the third-party application with the largest total number of logins is determined as having the largest weight value, thereby determining the third-party application with the largest weight value as the target application.

[0072] If multiple third-party applications are available, each application can be evaluated by determining its weight value. Prioritizing applications with higher weights can improve the effectiveness of authorized login and increase the success rate of game applications logging in using account information from third-party applications.

[0073] In step S302, the target third-party application is determined based on the service interface corresponding to the target interface address. The target third-party application is any one of multiple third-party applications.

[0074] For example, multiple third-party applications provide service interfaces to the outside world to carry out data exchange processes based on the provided service interfaces.

[0075] In step S303, the first account information corresponding to the target third-party application is obtained, and a first authorization token is generated based on the first account information, so that the target third-party application can synchronize the first authorization token to the application to be logged in through the constructed inter-process communication channel.

[0076] The inter-process communication channel can be constructed based on the AIDL mechanism.

[0077] For example, third-party applications typically have multi-device usage restrictions for the first account information, meaning that an account can only log in to one application at the same time.

[0078] In one optional embodiment of this disclosure, it is determined whether the first account information corresponding to the target third-party application is logged into other applications; if the first account information is logged into other applications, the first account information is logged out of other applications.

[0079] Other applications are those that, besides the application to be logged in, are other applications that authorize login through the account information of a third-party application.

[0080] For example, if an account information of a third-party application has already been logged in on application A, and then the account information is logged in again on another application B that supports login, the login status of application A will become invalid. This process is generally applied to application scenarios with strict account security.

[0081] Meanwhile, to ensure data security during data transmission, authentication of the application to be logged in is required during step 303. If the application is legitimate, data exchange with the third-party application is permitted. Otherwise, data exchange between the application to be logged in and the third-party application is rejected.

[0082] The following will provide an exemplary description of the authentication process for the application to be logged in, using specific embodiments as examples.

[0083] In some example embodiments of this disclosure, the application identifier of the application to be logged in is obtained; the application to be logged in is authenticated based on the application identifier to obtain the authentication result for the application to be logged in; if the authentication result is valid, the first account information corresponding to the target third-party application is obtained and a first authorization token is generated based on the first account information.

[0084] The application identifier is the application's package name. The package name is a unique identifier for the application, meaning there is a one-to-one correspondence between the package name and the application. One package name represents one application, and two applications are not allowed to use the same package name.

[0085] Authenticating the application to be logged in based on its unique identifier can improve the accuracy of authentication.

[0086] When performing the above steps of authenticating the application to be logged in based on the application identifier and obtaining the authentication result for the application to be logged in, in some example embodiments of this disclosure, the application identifier of the application to be logged in is searched from the pre-configured application whitelist; if the application whitelist contains the application identifier of the application to be logged in, the authentication result is valid.

[0087] The application whitelist contains one or more legitimate application identifiers, meaning that the applications corresponding to the application identifiers in the application whitelist can exchange data with third-party applications.

[0088] For example, when multiple third-party applications exist, the server can predefine a third-party login protocol so that all third-party applications can be authorized according to this protocol, and an application whitelist can be defined through the third-party login protocol. When a third-party application client receives an application login request, it can authenticate the game application according to the application whitelist.

[0089] If the application whitelist contains the game application's application identifier, the game application is deemed legitimate, meaning the third-party application allows the game application to authorize login using account information. At this point, the first account information corresponding to the target third-party application can be obtained, and a first authorization token can be generated based on this first account information. This first authorization token can replace the third-party application's password, allowing the game application to access authorized resources without using the third-party application's username and password.

[0090] Conversely, if the application's identifier is not in the application whitelist, a login failure message is sent to the client of the application to be logged in, and displayed on the game client's graphical user interface. The message may include the reason for the login failure (e.g., the game application is illegitimate or unauthorized), allowing the user to make timely adjustments.

[0091] In one optional embodiment of this disclosure, an application authentication method is defined through a service interface provided by a third application, and application authentication is performed using the aforementioned authentication method. For example, the authentication method may be determined by comparison using random numbers, hashes, or other methods to prevent unauthorized modification of the authentication method.

[0092] By authenticating game applications through a pre-configured application whitelist, a first authorization token can be generated after successful authentication, thereby improving account information security.

[0093] In an optional embodiment of this disclosure, a first authorization token is generated based on account information. The target third-party application then encrypts the first authorization token to obtain an encrypted first authorization token. This encrypted first authorization token is then synchronized to the application to be logged in via a constructed inter-process communication channel. For example, a data encryption method can be defined through a service interface provided by the third-party application. When the application to be logged in uses the first authorization token and the target third-party application's first account information to log in, the first authorization token can be encrypted using the aforementioned data encryption method to obtain the encrypted first authorization token.

[0094] It should be noted that, in addition to encrypting the first authorization token mentioned above, third-party applications may also need to encrypt data such as interface parameters.

[0095] In some example embodiments of this disclosure, the first authorization token is encrypted to obtain an encrypted first authorization token, and the encrypted first authorization token is synchronized to the application client to be logged in through the AIDL mechanism.

[0096] The third-party application client obtains an encrypted first authorization token by encrypting the first authorization token, and then synchronizes it to the application client to be logged in through the AIDL mechanism, which can improve the security of data during transmission.

[0097] After step S303 is executed and the user terminates the application, when the player authorizes login again using the account information corresponding to the target application, they can directly use the generated first authorization token for automatic login without regenerating the first authorization token.

[0098] However, in some cases, it is impossible to continue using the first authorization token for login, and a new one must be applied for. The following will explain the situations where the first authorization token cannot be used with specific examples.

[0099] See Figure 4 In an optional embodiment of this disclosure, after the game application logs in using the account information corresponding to the third-party application based on the first authorization token in step S303, the following steps S401-S404 may also be included:

[0100] Step S401: Receive a login request from the application client to be logged in.

[0101] Step S402: Determine whether the duration of the first authorization token is greater than the preset duration.

[0102] If the duration of the first authorization token exceeds the preset duration, then step S403 is executed to obtain the account information corresponding to the target third-party application and generate a second authorization token based on the account information, so as to log in based on the second authorization token.

[0103] For example, a second authorization token is generated so that the target third-party application can synchronize the second authorization token to the application to be logged in through a constructed inter-process communication channel to log in.

[0104] The above process enables the application to log in using the second authorization token and the first account information.

[0105] The second authorization token can be an authorization token generated by re-initiating a login request using the first account information.

[0106] For example, the authorization token has an expiration time. It should be understood that the preset duration can be adjusted in real time according to actual needs, or it can be pre-configured by the developers, and this disclosure does not impose any special limitations on this.

[0107] If the duration of the first authorization token is less than or equal to the preset duration, that is, the first authorization token is within the token validity period, then step S404 is executed, and the application to be logged in logs in based on the first authorization token and the first account information.

[0108] Adding an expiration date to the authorization token allows players to log in directly with their primary account information for the target application within a short period without needing to reapply for an authorization token, reducing user login waiting time; while regenerating the authorization token after the expiration date can improve the security of account information.

[0109] See Figure 5 In another optional embodiment of this disclosure, after the game application logs in using the first account information based on the first authorization token in step S303, the following steps S501-S503 may also be included:

[0110] Step S501: Receive a login request from the application client to be logged in.

[0111] Step S502: Determine whether the first account information has been updated to the second account information.

[0112] If the first account information corresponding to the third-party application is updated to the second account information, then step S503 is executed to obtain the second account information corresponding to the target third-party application and generate a third authorization token based on the second account information, so as to log in based on the third authorization token.

[0113] This enables the target third-party application to synchronize a third-party authorization token to the application to be logged in via a constructed inter-process communication channel.

[0114] The above process facilitates the login process for the application to be logged in using the third authorization token and the second account information. The third authorization token can be an authorization token generated by re-initiating a login request using the second account information.

[0115] If the account information corresponding to the target third-party application has not changed, then step S504 is executed, and the application to be logged in logs in using the first account information based on the first authorization token.

[0116] When the account information corresponding to the target application changes, it is necessary to re-apply for authorization to log in, so as to update the login account in a timely manner when the account information changes and to ensure the security of the login information of the application to be logged in.

[0117] The following will refer to Figure 6 The entire login process of the application login method according to an exemplary embodiment of this disclosure will be described in detail.

[0118] Suppose that the third-party applications that can be authorized for login include third-party application A, third-party application B, and third-party application C, and their corresponding remote service interfaces are remote service interface a, remote service interface b, and remote service interface c, respectively.

[0119] First, in step S601, the interface address is synchronized in advance via the network.

[0120] Each third-party application client connected to the platform server provides a remote service interface to facilitate data exchange with other applications. Each remote service interface corresponds to an interface address, allowing the platform server to quickly invoke the remote service interfaces of each third-party application to exchange data.

[0121] For example, when third-party application A, third-party application B, and third-party application C log in using their respective account information a1, a2, and a3, the interface addresses of the remote service interfaces corresponding to the aforementioned third-party applications A, B, and C will be synchronized to the platform server in advance via the network.

[0122] If third-party application A does not log in using account information a1, while third-party applications B and C log in using account information a2 and account information a3 respectively, then the interface addresses of the remote service interfaces corresponding to third-party applications B and C will be synchronized to the platform server in advance via the network; however, the interface address of third-party application A will not be synchronized to the platform server.

[0123] In step S602, a login request is sent.

[0124] In other words, the application client to be logged in sends a login request to the platform server. According to some embodiments of this disclosure, after the user performs a login confirmation operation from the page of the application to be logged in, the application client sends a login request to the platform server.

[0125] After receiving a login request from the client of the application to be logged in, the platform server executes step S603, determines the weight value of each third-party application based on historical login data, and identifies the third-party application with the highest weight value as the target application.

[0126] Historical login data can include the number of times and duration of authorized logins for each third-party application, as well as whether the user is currently logged into other applications. For example, the weight values ​​of third-party applications A, B, and C are determined based on the historical login data collected by the platform server, and the third-party application with the highest weight value is identified as the target application. For instance, if the weight values ​​of the third-party applications are in the order of A > B > C, then the target application is A.

[0127] At the same time, after the target application is determined, the platform server executes step S604 and sends the interface address corresponding to the target application.

[0128] For example, once the client of the application to be logged in receives the interface address corresponding to the target application, it can call the remote service interface corresponding to the target application to directly interact with the third-party application client.

[0129] In step S605, the remote service interface corresponding to the target application is called through the interface address, and a login request is sent through the remote service interface.

[0130] For example, the application client to be logged in sends a login request to the third-party application client through the remote service interface corresponding to the target application. During the data transmission between the application to be logged in and the third-party application client, the login request is encrypted.

[0131] After receiving the login request, the third-party application client executes step S606, which authenticates the target application package name of the application to be logged in based on the pre-configured whitelist.

[0132] For example, the platform server pre-configures a whitelist, and the third-party application client also configures a whitelist. The whitelist contains the application package names that third-party applications are allowed to authorize login. That is, the multiple application package names included in the whitelist correspond to the applications to be logged in that are authorized by the third-party applications.

[0133] Taking the above weighted order as follows: Third-party application A > Third-party application B > Third-party application C, if authentication of third-party application A fails (i.e., the application package name of third-party application A is not included in the whitelist), then the next third-party application with the highest weight, B, is identified as the target application. The platform server then sends a login request to third-party application B via remote service interface b for re-authentication. Similarly, if third-party application B also fails authentication, authentication continues with the application package name of third-party application C until authentication succeeds.

[0134] If authentication is successful, the third-party application client executes step S607 and sends account information.

[0135] For example, if the target application is a third-party application A, and the third-party application A logs in using account information a1, then the client corresponding to the third-party application A will send the account information a1 to the platform server after the application to be logged in is authenticated.

[0136] Then, after receiving the account information sent by the third-party application client, the platform server executes step S608 to generate and send the first authorization token based on the account information.

[0137] For example, when the platform server sends the first authorization token to a third-party application client through a remote service interface, the first authorization token and other data can be transmitted in encrypted form.

[0138] In step S609, the first authorization token is decrypted to obtain the second authorization token.

[0139] For example, the remote service interface of a third-party application defines a data encryption method, and encrypts and decrypts data based on this method. Simultaneously, the remote service interface of the third-party application also defines a data protocol format to convert data into a specific data format for transmission. For example, data decryption can be based on JSON.

[0140] The third-party application client executes step S610, transmitting the second authorization token via AIDL.

[0141] Finally, after the login application client receives the second authorization token, it executes step S611 to log in using the target account information corresponding to the target application based on the second authorization token.

[0142] To implement the above-described application login method, one embodiment of this disclosure provides an application login device. Figure 7 The schematic diagram illustrates the architecture of the application login device.

[0143] The application login device 700 includes an interface address determination module 701, an application determination module 702, and a token generation module 703.

[0144] The interface address determination module 701 is used to determine the target interface address corresponding to the login request from a plurality of pre-configured interface addresses for the login request of the application to be logged in; wherein, the plurality of interface addresses correspond to the service interfaces of a plurality of third-party applications; the application determination module 702 is used to determine the target third-party application according to the service interface corresponding to the target interface address, wherein the target third-party application is any one of the plurality of third-party applications; the token generation module 703 is used to obtain the first account information corresponding to the target third-party application, and generate a first authorization token according to the first account information, so that the target third-party application can synchronize the first authorization token to the application to be logged in through the constructed inter-process communication channel for login.

[0145] Furthermore, in order to implement the above application login method, one embodiment of this disclosure also provides another application login device. Figure 8 The schematic diagram illustrates the architecture of the application login device.

[0146] In an optional embodiment of this disclosure, the token generation module 703 is used to obtain the application identifier of the application to be logged in; to authenticate the application to be logged in based on the application identifier, and to obtain the authentication result for the application to be logged in; if the authentication result is valid, to obtain the first account information corresponding to the target third-party application and to generate a first authorization token based on the first account information.

[0147] In an optional embodiment of this disclosure, the token generation module 703 is used to search for the application identifier of the application to be logged in from a pre-configured application whitelist; if the application whitelist contains the application identifier of the application to be logged in, the authentication result is valid.

[0148] In an optional embodiment of this disclosure, the interface address determination module 701 is used to determine the authorization weight of multiple third-party applications based on the historical login data of multiple third-party applications corresponding to multiple interface addresses; and to determine the interface address with the highest authorization weight as the target interface address.

[0149] In an optional embodiment of this disclosure, the application login device 800 may further include a login status determination module 704 and an account logout module 705. The login status determination module 704 is used to determine whether the first account information corresponding to the target third-party application is logged into other applications; the account logout module 705 is used to log the first account information out of other applications if the first account information is logged into other applications.

[0150] In an optional embodiment of this disclosure, the token generation module 703 is used to generate a first authorization token based on account information, so that the target third-party application can encrypt the first authorization token to obtain an encrypted first authorization token, and synchronize the encrypted first authorization token to the application to be logged in through the constructed inter-process communication channel for login.

[0151] In an optional embodiment of this disclosure, the token generation module 703 is used to receive a login request from the application to be logged in; if the duration of the first authorization token is longer than a preset duration, the account information corresponding to the target third-party application is obtained and a second authorization token is generated based on the account information, so that the target third-party application can synchronize the second authorization token to the application to be logged in through the constructed inter-process communication channel.

[0152] In an optional embodiment of this disclosure, the token generation module 703 is used to obtain the second account information corresponding to the target third-party application and generate a third authorization token based on the second account information if the first account information of the target third-party application is updated to the second account information, so that the target third-party application can synchronize the third authorization token to the application to be logged in through the constructed inter-process communication channel.

[0153] The application login device 700 or application login device 800 provided in this embodiment can execute the technical solution of the application login method in any of the above embodiments. Its implementation principle and beneficial effects are similar to those of the application login method. Please refer to the implementation principle and beneficial effects of the application login method. It will not be repeated here.

[0154] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the present invention may also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of the present invention described in the "Exemplary Methods" section above.

[0155] According to embodiments of the present invention, a program product for implementing the above-described method may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0156] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0157] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0158] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0159] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0160] In an exemplary embodiment of this disclosure, an electronic device capable of implementing the above-described method is also provided.

[0161] Those skilled in the art will understand that various aspects of the present invention can be implemented as systems, methods, or program products. Therefore, various aspects of the present invention can be specifically implemented in the following forms: entirely hardware implementations, entirely software implementations (including firmware, microcode, etc.), or implementations combining hardware and software aspects, collectively referred to herein as “circuits,” “modules,” or “systems.”

[0162] The following reference Figure 9 To describe an electronic device 900 according to this embodiment of the present invention. Figure 9 The electronic device 900 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0163] like Figure 9 As shown, the electronic device 900 is presented in the form of a general-purpose computing device. The components of the electronic device 900 may include, but are not limited to: at least one processing unit 910, at least one storage unit 920, a bus 930 connecting different system components (including storage unit 920 and processing unit 910), and a display unit 940.

[0164] The storage unit stores program code, which can be executed by the processing unit 910 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 910 can perform actions such as... Figure 3 Steps S301 to S303 are shown in the diagram.

[0165] Storage unit 920 may include readable media in the form of volatile storage units, such as random access memory (RAM) 9201 and / or cache memory 9202, and may further include read-only memory (ROM) 9203.

[0166] Storage unit 920 may also include a program / utility 9204 having a set (at least one) of program modules 9205, such program modules 9205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0167] Bus 930 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0168] Electronic device 900 can also communicate with one or more external devices 1000 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 900, and / or with any device that enables electronic device 900 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 950. Furthermore, electronic device 900 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 960. As shown, network adapter 960 communicates with other modules of electronic device 900 via bus 930. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0169] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0170] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0171] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0172] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0173] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is defined only by the appended claims.

Claims

1. An application login method, characterized by, The application is applied to a platform server, and comprises the following steps: For a login request of a to-be-logged-in application, a target interface address corresponding to the login request is determined from a plurality of pre-configured interface addresses; wherein the plurality of interface addresses correspond to service interfaces of a plurality of third-party applications, a login page of the to-be-logged-in application is in a landscape display mode, and login pages of the plurality of third-party applications are in a portrait display mode; A target third-party application is determined according to a service interface corresponding to the target interface address, and the target third-party application is any one of the plurality of third-party applications; First account information corresponding to the target third-party application is acquired, a first authorization token is generated according to the first account information, the first authorization token is synchronized to the to-be-logged-in application by an inter-process communication channel constructed by the target third-party application to log in, and the to-be-logged-in application does not need to switch the login page between the landscape display mode and the portrait display mode. After the first authorization token is generated, in response to receiving a login request from the to-be-logged-in application, if the first authorization token exists for a time period longer than a preset time period, account information corresponding to the target third-party application is acquired, a second authorization token is generated according to the account information, the second authorization token is synchronized to the to-be-logged-in application by the inter-process communication channel constructed by the target third-party application to log in, and the to-be-logged-in application does not need to switch the login page between the landscape display mode and the portrait display mode.

2. The application login method according to claim 1, wherein The first account information corresponding to the target third-party application is acquired, and the first authorization token is generated according to the first account information, and the method comprises the following steps: An application identifier of the to-be-logged-in application is acquired; The to-be-logged-in application is authenticated based on the application identifier, and an authentication result for the to-be-logged-in application is obtained; If the authentication result is legal, the first account information corresponding to the target third-party application is acquired, and the first authorization token is generated according to the first account information.

3. The application login method according to claim 2, wherein The to-be-logged-in application is authenticated based on the application identifier, and an authentication result for the to-be-logged-in application is obtained, and the method comprises the following steps: An application identifier of the to-be-logged-in application is searched from a pre-configured application white list; If the application identifier of the to-be-logged-in application is contained in the application white list, the authentication result is legal.

4. The application login method according to claim 1, wherein The target interface address corresponding to the login request is determined from the plurality of pre-configured interface addresses, and the method comprises the following steps: According to historical login data of a plurality of third-party applications corresponding to the plurality of interface addresses, authorization weights of the plurality of third-party applications are determined; The interface address with the largest authorization weight is determined as the target interface address.

5. The application login method according to claim 1, wherein Before the first authorization token is generated according to the first account information, the method further comprises the following steps: It is judged whether the first account information corresponding to the target third-party application logs into other applications; If the first account information logs into the other applications, the first account information is logged out of the other applications.

6. The application login method of claim 1, wherein The first authorization token is generated according to the account information, so that the target third-party application synchronizes the first authorization token to the application to be logged in through the constructed inter-process communication channel for login. The first authorization token is generated according to the account information, so that the target third-party application synchronizes the first authorization token to the application to be logged in through the constructed inter-process communication channel for login.

7. The application login method of claim 1, wherein After the first account information of the target third-party application is obtained and the first authorization token is generated according to the first account information, so that the target third-party application synchronizes the first authorization token to the application to be logged in through the constructed inter-process communication channel for login, the method further comprises: If the first account information of the target third-party application is updated to second account information, the second account information corresponding to the target third-party application is obtained, and a third authorization token is generated according to the second account information, so that the target third-party application synchronizes the third authorization token to the application to be logged in through the constructed inter-process communication channel for login.

8. An application login apparatus characterized by comprising: The device is applied to a third-party application client, and comprises: An interface address determination module is configured to determine a target interface address corresponding to a login request of an application to be logged in from a plurality of interface addresses pre-configured, wherein the plurality of interface addresses correspond to service interfaces of a plurality of third-party applications, a login page of the application to be logged in is in a landscape display mode, and login pages of the plurality of third-party applications are in a portrait display mode; An application determination module is configured to determine a target third-party application according to a service interface corresponding to the target interface address, the target third-party application being any one of the plurality of third-party applications; A token generation module is configured to obtain first account information corresponding to the target third-party application, generate a first authorization token according to the first account information, so that the target third-party application synchronizes the first authorization token to the application to be logged in through a constructed inter-process communication channel for login, so that the application to be logged in does not need to perform login page switching between the landscape display mode and the portrait display mode; After the first authorization token is generated, in response to receiving a login request from the application to be logged in, if the first authorization token exists for a time period longer than a preset time period, the account information corresponding to the target third-party application is obtained, and a second authorization token is generated according to the account information, so that the target third-party application synchronizes the second authorization token to the application to be logged in through the constructed inter-process communication channel for login, so that the application to be logged in does not need to perform login page switching between the landscape display mode and the portrait display mode.

9. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by a processor to implement the application login method of any one of claims 1 to 7.

10. An electronic device, comprising: Comprise: A processor; And A memory for storing executable instructions of the processor; The processor is configured to execute the application login method of any one of claims 1 to 7 by executing the executable instructions. The processor is configured to execute the application login method of any one of claims 1 to 7 by executing the executable instructions.

Images