Account login method, device, equipment, storage medium and program product

Abstract

The application relates to an account login method and device, equipment, a storage medium and a program product, and relates to the technical field of information interaction. The method comprises the following steps: receiving a first authentication request sent by a login device, wherein the first authentication request comprises the identification of an authorization platform and user identity information; obtaining an authorized user account corresponding to the user identity information stored in an authentication management device; sending a second authentication request to the authorization platform based on the identification of the authorization platform, wherein the second authentication request comprises the authorized user account; receiving authorization authentication information sent by the authorization platform based on the authorized user account; and sending the authorization authentication information to the login device, wherein the authorization authentication information is information used for the login device to perform account login in a target application program. Through the above method, multiple jumps between clients in the authorization login process are avoided, the operation process of the authorization login is simplified, the data interaction process is reduced, and therefore, the operation efficiency of the authorization login is improved.

Description

Technical Field

[0001] This application relates to the field of information interaction technology, and in particular to an account login method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the development of computer technology, when using applications, users can often log in to accounts in other account systems outside the application's own account system through authorized login. For example, a user can log in to a game application using an account from a communication application.

[0003] In related technologies, when a user logs into an account belonging to a second application within a first application's account system via authorized login, the first application needs to launch the second application on the terminal, causing the terminal to redirect to the second application's authorization interface. Based on the authorization operation performed by the user on the authorization interface, the second application returns authorization authentication information to the first application, simultaneously triggering the terminal to redirect back to the first application's application interface. Subsequently, the first application completes the authorized login using the aforementioned authorization authentication information.

[0004] However, the authorization login process in related technologies involves multiple jumps between the interfaces of two applications, and if the second application is not installed, it is necessary to install a second application. The operation is cumbersome, resulting in low efficiency of authorization login. Summary of the Invention

[0005] This application provides an account login method, apparatus, device, storage medium, and program product, which can avoid multiple redirects between clients during the authorization login process, simplify the authorization login operation, reduce data interaction during the authorization login process, and thus improve the efficiency of authorization login. The technical solution is as follows:

[0006] On one hand, an account login method is provided, the method being executed by an authentication management device, the authentication management device storing the relationship between user identity information in a first account system and authorized user accounts in a second account system; the method includes:

[0007] The system receives a first authentication request sent by the login device. The first authentication request includes the identifier of the authorized platform and the user's identity information. The authorized platform corresponds to the second account system.

[0008] Obtain the authorized user account stored in the authentication management device that corresponds to the user identity information;

[0009] Based on the identifier of the authorization platform, a second authentication request is sent to the authorization platform, the second authentication request containing the authorized user account;

[0010] Receive authorization authentication information sent by the authorization platform based on the authorized user account;

[0011] The authorization and authentication information is sent to the login device, and the authorization and authentication information is used by the login device to log in to the target application.

[0012] On the other hand, an account login method is provided, the method being executed by a login device, the method comprising:

[0013] A first authentication request is sent to the authentication management device. The first authentication request includes the identifier of the authorized platform and the user's identity information. The authentication management device stores the relationship between the user's identity information in a first account system and the authorized user account in a second account system. The authorized platform corresponds to the second account system.

[0014] The system receives authorization authentication information sent by the authentication management device. The authorization authentication information is obtained by the authentication management device based on the first authentication request, which retrieves the authorized user account stored in the authentication management device that corresponds to the user identity information. After the authentication management device sends a second authentication request to the authorization platform based on the identifier of the authorization platform, the authorization platform sends the information to the authentication management device based on the authorized user account. The second authentication request includes the authorized user account.

[0015] Log in to the target application based on the authorization and authentication information.

[0016] On the other hand, an account login method is provided, which is executed by an authorized platform, and the method includes:

[0017] The system receives a second authentication request from an authentication management device. The authentication management device stores the relationship between user identity information in a first account system and authorized user accounts in a second account system. The second authentication request is sent by the authentication management device based on the identifier of an authorization platform. The identifier of the authorization platform is carried in the first authentication request sent by the login device. The second authentication request includes an authorized user account stored in the authentication management system that corresponds to the user identity information in the first authentication request. The user identity information is the user identity information in the first account system. The authorization platform corresponds to the second account system.

[0018] Generate authorization authentication information based on the authorized user account;

[0019] The authorization and authentication information is sent to the authentication management device so that the authentication management device can pass the authorization and authentication information to the login device. The authorization and authentication information is used by the login device to log in to the target application.

[0020] On the other hand, an account login device is provided, which is applied in an authentication management device, the authentication management device storing the relationship between user identity information in a first account system and authorized user accounts in a second account system; the device includes:

[0021] The first request receiving module is used to receive a first authentication request sent by the login device. The first authentication request includes the identifier of the authorization platform and the user's identity information. The authorization platform corresponds to the second account system.

[0022] The account acquisition module is used to acquire the authorized user account corresponding to the user identity information stored in the authentication management device;

[0023] The first request sending module is used to send a second authentication request to the authorization platform based on the identifier of the authorization platform, wherein the second authentication request contains the authorized user account;

[0024] The first information receiving module is used to receive authorization authentication information sent by the authorization platform based on the authorized user account;

[0025] The first information sending module is used to send the authorization and authentication information to the login device, wherein the authorization and authentication information is used by the login device to log in to the target application.

[0026] In one possible implementation, the account acquisition module is used to query the association information stored in the authentication management device based on the user identity information to obtain the authorized user account; the association information includes the association relationship between the user identity information and the authorized user account.

[0027] In one possible implementation, the device further includes:

[0028] The third request receiving module is used to receive the first authorization request sent by the login device; the first authorization request includes the authorized user account, the account verification information of the authorized user account, and the user identity information;

[0029] The third request sending module is used to send a verification request to the authorization platform, wherein the verification request includes the authorized user account and the account verification information;

[0030] The association setting module is used to respond to receiving the verification result returned by the authorization platform, and the verification result indicates that the authorized user account matches the account verification information, and to set the association relationship between the user identity information and the authorized user account in the association relationship information.

[0031] In one possible implementation, the user identity information includes at least one of the following:

[0032] Facial information, fingerprint information, account password information, and verified user accounts;

[0033] The account password information includes the authenticated user account and the verification password of the authenticated user account; the authenticated user account is a user account in the first account system.

[0034] In one possible implementation, the login device is a terminal device with a management application installed; the management application includes a launch entry for at least one application, and the target application is one of the at least one application;

[0035] Alternatively, the login device is the application server of the management application;

[0036] Alternatively, the login device is a terminal device with the target application installed.

[0037] On the other hand, an account login device is provided, which is applied to a login device, and the device includes:

[0038] The second request sending module is used to send a first authentication request to the authentication management device. The first authentication request includes the identifier of the authorization platform and user identity information. The authentication management device stores the relationship between the user identity information in the first account system and the authorized user accounts in the second account system. The authorization platform corresponds to the second account system.

[0039] The second information receiving module is used to receive authorization authentication information sent by the authentication management device; the authorization authentication information is obtained by the authentication management device based on the first authentication request, which retrieves the authorized user account stored in the authentication management device corresponding to the user identity information, and sends a second authentication request to the authorization platform based on the identifier of the authorization platform, and then the authorization platform sends it to the authentication management device based on the authorized user account; the second authentication request includes the authorized user account;

[0040] The program login module is used to log in to the target application based on the authorization and authentication information.

[0041] In one possible implementation, the device further includes:

[0042] The interface display module is used to display the authorization login interface, which displays at least one platform control.

[0043] An identifier determination module is used to determine the identifier of the authorized platform in response to receiving a selection operation on a target platform control; the target platform control is any one of the at least one platform control;

[0044] The request generation module is used to generate the first authentication request based on the identifier of the authorization platform.

[0045] In one possible implementation, the device further includes:

[0046] The fourth request sending module is used to send a first authorization request to the authentication management device. The first authorization request includes the authorized user account, the account verification information of the authorized user account, and the user identity information. The first authorization request is used to trigger the authentication management device to send a verification request to the authorization platform. When the verification result returned by the authorization platform is received, and the verification result indicates that the authorized user account matches the account verification information, the module sets the association relationship between the user identity information and the authorized user account in the association relationship information. The verification request includes the authorized user account and the account verification information.

[0047] On the other hand, an account login device is provided, which is used in an authorization platform, and the device includes:

[0048] The second request receiving module is used to receive a second authentication request sent by the authentication management device; the authentication management device stores the relationship between user identity information in the first account system and authorized user accounts in the second account system; the second authentication request is sent by the authentication management device based on the identifier of the authorization platform; the identifier of the authorization platform is carried by the first authentication request sent by the login device; the second authentication request contains the authorized user account stored in the authentication management system that corresponds to the user identity information in the first authentication request; the user identity information is the user identity information in the first account system; the authorization platform corresponds to the second account system;

[0049] The information generation module is used to generate authorization authentication information based on the authorized user account;

[0050] The second information sending module is used to send the authorization and authentication information to the authentication management device, so that the authentication management device can pass the authorization and authentication information to the login device. The authorization and authentication information is used by the login device to log in to the target application.

[0051] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one computer program, the at least one computer program being loaded and executed by the processor to implement the above-described account login method.

[0052] On the other hand, a computer-readable storage medium is provided, wherein at least one computer program is stored in the computer program, which is loaded and executed by a processor to implement the account login method described above.

[0053] On the other hand, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the account login method provided in the various optional implementations described above.

[0054] The technical solution provided in this application may include the following beneficial effects:

[0055] The account login method provided in this application adds an authentication management device between the login device and the authorization platform of the target application. In scenarios requiring authorized login, the login device can send the user's identity information in the first account system and the identifier of the authorization platform to the authentication management device. The authentication management device then queries the authorized user account in the second account system corresponding to the authorization platform based on the user's identity information, and obtains authorization authentication information from the authorization platform through the authorized user account. This enables information exchange between the respective account systems of the login device and the authorization platform, and completes the transparent transmission of authorization authentication information on the network side. This avoids multiple client jumps during the authorization login process, simplifies the authorization login operation, reduces the data interaction process during authorization login, and thus improves the efficiency of authorization login. At the same time, due to the reduction in data interaction, the amount of data exchanged during authorization login is also reduced, thereby saving bandwidth usage.

[0056] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

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

[0058] Figure 1 A schematic diagram of the architecture of an authorization login system illustrated in an exemplary embodiment of this application is shown;

[0059] Figure 2 A schematic diagram of the structure of a cloud gaming system illustrated in an exemplary embodiment of this application is shown;

[0060] Figure 3 A flowchart illustrating an account login method according to an exemplary embodiment of this application is shown;

[0061] Figure 4 A flowchart illustrating an account login method according to an exemplary embodiment of this application is shown;

[0062] Figure 5 A flowchart illustrating an account login method according to an exemplary embodiment of this application is shown;

[0063] Figure 6 An interactive schematic diagram illustrating an exemplary embodiment of the account login process of this application is shown;

[0064] Figure 7 An interactive schematic diagram of an account login method illustrated in an exemplary embodiment of this application is shown;

[0065] Figure 8 A schematic diagram illustrating a user authorization process as shown in an exemplary embodiment of this application is provided.

[0066] Figure 9 A schematic diagram of an authorized login interface provided in an exemplary embodiment of this application is shown;

[0067] Figure 10 A schematic diagram of the display interface of a login device shown in an exemplary embodiment of this application is illustrated;

[0068] Figure 11 A schematic diagram illustrating an account login method in a cloud gaming scenario, as shown in an exemplary embodiment of this application, is presented.

[0069] Figure 12 This illustration shows a schematic diagram of an account login method in a PC game scenario, as illustrated in an exemplary embodiment of this application.

[0070] Figure 13 A block diagram of an account login device illustrated in an exemplary embodiment of this application is shown;

[0071] Figure 14 A block diagram of an account login device illustrated in an exemplary embodiment of this application is shown;

[0072] Figure 15 A block diagram of an account login device illustrated in an exemplary embodiment of this application is shown;

[0073] Figure 16 This is a structural block diagram of a computer device according to an exemplary embodiment;

[0074] Figure 17 This is a structural block diagram of a computer device according to an exemplary embodiment. Detailed Implementation

[0075] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0076] This application provides an account login method that can be used in the field of cloud application technology, such as cloud gaming technology, cloud payment technology, etc., or it can be applied to the field of local application technology.

[0077] Cloud gaming, also known as gaming on demand, is an online gaming technology based on cloud computing. It enables thin clients with relatively limited graphics processing and data processing capabilities to run high-quality games. In cloud gaming, the game client does not run on the player's terminal but on a cloud gaming server. The cloud gaming server renders the game scene as a streaming media file, which is then transmitted over the network to the player's terminal or other terminals with display capabilities. The player's terminal or other terminal with display capabilities does not need powerful graphics processing and data processing capabilities; it only needs basic streaming media playback capabilities. Furthermore, the player's terminal must be able to receive player input commands and send them to the cloud gaming server. Optionally, the cloud gaming server can be an Android container. An Android container is a complete Android system with strong compatibility, which can perform the initialization work of Android games. The rendering technology of the Android container can adopt in-container rendering technology, that is, by directly accessing the GPU (Graphics Processing Unit) within the container, the high-concurrency computing power of the GPU is utilized to complete the rendering within the container, thereby greatly reducing the latency caused by rendering and improving rendering performance.

[0078] The player's gaming terminal or other terminal with display capabilities is used to display the scene screen of a virtual scene running on a client running on a cloud gaming server. The virtual scene refers to the virtual scene displayed (or provided) by the client during runtime. This cloud gaming server client can be implemented as an application or as hardware within the cloud gaming server. The virtual scene can be a simulation of a real-world environment, a semi-simulated / semi-fictional 3D environment, or a purely fictional 3D environment. The virtual scene can be any of the following: 2D virtual scene, 2.5D virtual scene, or 3D virtual scene.

[0079] The account login method provided in this application can be applied to scenarios where a user account from one account system logs into an application belonging to another account system by means of authorized login. Figure 1 A schematic diagram of the architecture of an authorization login system illustrated in an exemplary embodiment of this application is shown. Figure 1 As shown, the authorized login system 100 may include: a login device 110, an authentication management device 120, and an authorization platform 130.

[0080] The login device can be a terminal or a server used to launch the target application. For example... Figure 1 As shown, when the login device 110 is a terminal device used to launch the target application, the login device 110 and the authentication management device 120 are connected through the server of the target application. At this time, the login device 110 can be a mobile phone, tablet computer, laptop computer, e-book reader, MP4 (Moving Picture Experts Group Audio Layer IV) player, laptop computer and desktop computer, etc.

[0081] In local application scenarios, the target application can be a locally installed application run by the terminal device. In cloud application scenarios, the target application can be a cloud application managed by a cloud application platform. For example, the terminal device may have a platform application installed on the cloud application platform, and this platform application's interface may contain at least one launch entry point for the cloud application. The user can trigger the cloud application server to launch the cloud application through the launch entry point provided by the cloud application platform, and then the terminal device can display the corresponding screen of the cloud application. Illustratively, when the cloud application scenario is a cloud gaming scenario, the target application can be a cloud gaming application within a cloud gaming platform, and the cloud application platform's server can be the corresponding server for the cloud gaming platform. That is, in a cloud gaming application scenario, the login device 110 can be either a terminal device for the platform application of the cloud gaming platform or a server for the cloud gaming platform.

[0082] The authentication management device 120 maintains the relationship between user identity information in the first account system and user accounts in other account systems. The authentication management device 120 is connected to both the login device 110 and the authorization platform 130 to complete the transparent transmission of authorization authentication information on the network side, enabling account login in the target application using existing accounts from the authorization platform.

[0083] When the login device is a server used to launch the target application, the login device can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a server that provides 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 (Content Delivery Network), and big data and artificial intelligence platforms.

[0084] The authentication management device 120 and the authorization platform 130 can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or servers that provide 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 (Content Delivery Network), and big data and artificial intelligence platforms.

[0085] The login device, authentication management device, and authorization platform can be implemented in the same or different ways.

[0086] The login device 110 and the authentication management device 120, as well as the authentication management device 120 and the authorization platform 130, can be connected via a communication network 140. Optionally, the communication network 140 can be a wired network or a wireless network.

[0087] Optionally, the aforementioned wireless or wired networks use standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to Local Area Networks (LANs), Metropolitan Area Networks (MANs), Wide Area Networks (WANs), mobile, wired or wireless networks, private networks, or any combination of virtual private networks. In some embodiments, technologies and / or formats, including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network. Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Networks (VPNs), and Internet Protocol Security (IPsec) can be used to encrypt all or some links. In other embodiments, custom and / or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies.

[0088] Taking the account login method provided in this application as an example in a cloud gaming scenario, Figure 2 A schematic diagram of the structure of a cloud gaming system illustrated in an exemplary embodiment of this application is shown, such as... Figure 2 As shown, the cloud gaming system includes a cloud gaming server 210 and a terminal 220.

[0089] Among them, the cloud gaming server 210 is a server that supports the cloud gaming operating environment. The cloud gaming server 210 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a server that provides 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.

[0090] Terminal 220 and cloud gaming server 210 can be connected via communication network 230.

[0091] The terminal 220 can be implemented as follows: Figure 1 The login device 110 in the authorized login system shown; the terminal 220 runs an application of a cloud gaming platform, which is a system platform that supports cloud gaming. For example, the cloud gaming platform application can be used to display the scene screen corresponding to the cloud game; the cloud gaming platform application can also receive the user's game control operations, generate game control instructions corresponding to the game control operations, and send the game control instructions to the cloud gaming server 210; correspondingly, the cloud gaming server 210 receives the game control instructions through the communication network 230, and performs calculations on the game logic and renders the game screen according to the game control instructions. The cloud gaming server 210 obtains the audio and video stream corresponding to the game screen, and encodes and sends the audio and video stream. The cloud gaming platform application receives the encoded audio and video stream through the communication network 230, and decodes the encoded audio and video stream to update the game screen corresponding to the audio and video stream.

[0092] Figure 3 A flowchart illustrating an exemplary embodiment of this application is shown. This method can be executed by an authentication management device, which stores the relationship between user identity information in a first account system and authorized user accounts in a second account system. The authentication management device can be implemented as follows: Figure 1 The authentication management device 120 in the authorized login system 100 shown; such as Figure 3 As shown, the account login method may include the following steps:

[0093] Step 310: Receive a first authentication request sent by the login device. The first authentication request contains the identifier of the authorized platform and the user's identity information. The authorized platform corresponds to the second account system.

[0094] The first authentication request sent by the login device may be sent by the login device upon receiving an authorized login operation for the target application.

[0095] For example, when the login device is a terminal device, the login device can directly send the first authentication request to the authentication management device.

[0096] Alternatively, when the login device is a terminal device, the login device can send the first authentication request to the intermediate server; after receiving the first authentication request, the intermediate server will pass the first authentication request to the authentication management device.

[0097] Alternatively, when the login device is a server, the first authentication request sent by the login device to the authentication management device may be sent to the server by the terminal device corresponding to the server when it receives an authorization login operation for the target application.

[0098] The identifier of the authorized platform included in the first authentication request indicates the authorized platform for the authorized user account used to log in to the target application. In other words, after receiving the first authentication request, the authentication management device can determine the authorized platform for information exchange based on the first authentication request. For example, the authorized platform could be a communication application platform, or it could be a platform with a payment application, etc.

[0099] The user identity information in the first authentication request can be used to find the user account in the second account system corresponding to the authorized platform. Optionally, the user identity information can also be used to verify the identity information of the user who triggered the authorization login process.

[0100] Optionally, the first authentication request can be generated based on the target application. Different target applications correspond to different first authentication requests, enabling the device or platform that receives the first authentication request to determine the target application for authorization login based on the first authentication request. For example, the first authentication requests corresponding to different applications can have different message structures, which can be used to indirectly indicate the corresponding application.

[0101] Alternatively, the first authentication request may include a program identifier for the target application, which enables the device or platform receiving the first authentication request to determine the target application for authorized login based on the program identifier.

[0102] Optionally, the authentication management system may store the relationship between at least two user identity information in the first account system and at least two authorized user accounts in the second account system, with each user identity information corresponding one-to-one with each authorized user account.

[0103] In this embodiment of the application, when multiple authorized platforms exist, each authorized platform has its own account system, and the account systems corresponding to different authorized platforms are different. Furthermore, the account systems of each authorized platform are also different from the first account system.

[0104] Step 320: Obtain the authorized user account corresponding to the user identity information stored in the authentication management device.

[0105] After obtaining user identity information, the authentication management device can query the authorized user account corresponding to the user identity information based on the relationship between the user identity information and the authorized user account stored in the authentication management system.

[0106] Step 330: Based on the identifier of the authorized platform, send a second authentication request to the authorized platform, which contains the authorized user account.

[0107] After obtaining the identifier of the authorized platform, the authentication management device can determine the authorized platform to be interacted with based on the identifier of the authorized platform, and send an authentication request containing the authorized user account, i.e., a second authentication request, to the authorized platform so that the authorized platform can perform the authorization authentication operation based on the second authentication request, and generate authorization authentication information after completing the authorization authentication operation.

[0108] Step 340: Receive authorization authentication information sent by the authorization platform based on the authorized user account.

[0109] Step 350: Send the authorization and authentication information to the login device. This authorization and authentication information is used by the login device to log in to the target application.

[0110] Optionally, in a local authorization login scenario, after obtaining authorization and authentication information, the login device can use this information and the authorized user account corresponding to the authorization platform to log in to and run the target application. For example, the aforementioned authorization platform could be a cloud platform for a communication application; after obtaining authorization and authentication information, the login device can use the user account from the communication application to log in to a game application.

[0111] Taking cloud application scenarios as an example, after obtaining authorization and authentication information, the logging-in device can send this information to the cloud application server, allowing the server to verify its legitimacy. Once the verification is successful, the cloud application server uses this authorization and authentication information to log in to the authorized user account within the target application launched in the cloud. This verification process can include the cloud application server interacting with the authorization platform to determine the legitimacy of the authorization and authentication information.

[0112] Taking a local application scenario as an example, after obtaining the authorization and authentication information, the terminal device sends the authorization and authentication information to the target application's server through the target application launched locally. The target application's server then performs a validity verification. After the validity verification is successful, the authorized user account logs in within the target application launched on the terminal device.

[0113] In summary, the account login method provided in this application adds an authentication management device between the login device and the authorization platform of the target application. In scenarios requiring authorized login, the login device can send the user's identity information in the first account system and the identifier of the authorization platform to the authentication management device. The authentication management device then queries the authorized user account in the second account system corresponding to the authorization platform based on the user's identity information. It then obtains authorization authentication information from the authorization platform through the authorized user account, thereby achieving information exchange between the respective account systems of the login device and the authorization platform. This transparent transmission of authorization authentication information is completed on the network side, avoiding multiple client jumps during the authorization login process, simplifying the authorization login operation, reducing data interaction during the authorization login process, and thus improving the efficiency of the authorization login operation. Simultaneously, due to the reduction in data interaction, the amount of data exchanged during the authorization login process is also reduced, thereby saving bandwidth usage.

[0114] Figure 4 A flowchart illustrating an exemplary embodiment of this application is shown. This account login method can be executed by a login device, which can be implemented as follows: Figure 1 The login device 110 in the authorized login system 100 shown; such as Figure 4 As shown, the account login method may include the following steps:

[0115] Step 410: Send a first authentication request to the authentication management device. The first authentication request contains the identifier of the authorized platform and the user identity information. The authentication management device stores the relationship between the user identity information in the first account system and the authorized user accounts in the second account system. The authorized platform corresponds to the second account system.

[0116] In this embodiment of the application, the authorization login process can be a process triggered based on the user's authorization login operation for the target application.

[0117] Optionally, the first authentication request may be generated based on the target application; illustratively, the first authentication request itself may be used to indirectly indicate the target application; or, the first authentication request may carry the program identifier of the target application to indicate that the first authentication request is a request issued based on an authorized login operation for the target application.

[0118] Step 420: Receive authorization authentication information sent by the authentication management device; the authorization authentication information is obtained by the authentication management device based on the first authentication request, which obtains the authorized user account stored in the authentication management device corresponding to the user identity information, and sends a second authentication request to the authorization platform based on the identifier of the authorization platform, and then the authorization platform sends it to the authentication management device based on the authorized user account; the second authentication request contains the authorized user account.

[0119] The interaction between the login device, authentication management device, and authorization platform involved in this step can be found in [reference needed]. Figure 3 The relevant content in the illustrated embodiments will not be repeated here.

[0120] Step 430: Log in to the account in the target application based on the authorization and authentication information.

[0121] Optionally, in cloud application scenarios, after obtaining authorization information, the login device instructs the cloud application server to log in to the account based on the authorized login information.

[0122] The process of a cloud application server logging into a target application may include: the cloud application server starting an Android container internally to launch the target application within the Android container and simultaneously starting screen rendering; and sending the rendered streaming media data to a terminal device with screen display capabilities so that the terminal device can display the screen of the cloud application.

[0123] For example, the login device mentioned above can be a terminal device or another server device other than the cloud application server.

[0124] In summary, the account login method provided in this application adds an authentication management device between the login device and the authorization platform of the target application. In scenarios requiring authorized login, the login device can send the user's identity information in the first account system and the identifier of the authorization platform to the authentication management device. The authentication management device then queries the authorized user account in the second account system corresponding to the authorization platform based on the user's identity information. It then obtains authorization authentication information from the authorization platform through the authorized user account, thereby achieving information exchange between the respective account systems of the login device and the authorization platform. This transparent transmission of authorization authentication information is completed on the network side, avoiding multiple client jumps during the authorization login process, simplifying the authorization login operation, reducing data interaction during the authorization login process, and thus improving the efficiency of the authorization login operation. Simultaneously, due to the reduction in data interaction, the amount of data exchanged during the authorization login process is also reduced, thereby saving bandwidth usage.

[0125] Figure 5A flowchart illustrating an exemplary embodiment of this application is shown. This account login method can be executed by an authorization platform, which can be implemented as follows: Figure 1 The authorized platform 130 shown is as follows: Figure 5 As shown, the account login method may include the following steps:

[0126] Step 510: Receive a second authentication request sent by the authentication management device; the authentication management device stores the relationship between user identity information in the first account system and authorized user accounts in the second account system; the second authentication request is sent by the authentication management device based on the identifier of the authorization platform; the identifier of the authorization platform is carried by the first authentication request sent by the login device; the second authentication request contains the authorized user account stored in the authentication management system that corresponds to the user identity information in the first authentication request; the user identity information is the user identity information in the first account system; the authorization platform corresponds to the second account system.

[0127] The authorization platform is a platform for information exchange determined by the authentication management device based on the identifier of the authorization platform in the first authentication request received.

[0128] Step 520: Generate authorization authentication information based on the authorized user account.

[0129] Optionally, the authorization platform, based on the obtained authorized user account, queries the platform's database to obtain the basic registration information of the authorized user account in the target application; then, it uses an authorization encryption algorithm to convert the authorization information into authorization authentication information (token); the authorization information may include the authorized user account, current time information, and basic registration information, etc.

[0130] The authorized encryption algorithm can be an encryption algorithm corresponding to the authorized platform. Different authorized platforms may use different encryption algorithms. Optionally, the authorized encryption algorithm can be implemented as MD5 (Message-Digest Algorithm 5), AES (Advanced Encryption Standard), Base64, or other algorithms.

[0131] Step 530: Send the authorization and authentication information to the authentication management device so that the authentication management device can pass the authorization and authentication information to the login device. This authorization and authentication information is used by the recording device to log in to the authorized user account of the target application.

[0132] In this embodiment, the authorization platform transmits authorization and authentication information to the login device through the authentication management device to complete the transparent transmission of authorization and authentication information on the network side, so that the login device can log in to the target application based on the authorized user account based on the authorization and authentication information.

[0133] In summary, the account login method provided in this application adds an authentication management device between the login device and the authorization platform of the target application. In scenarios requiring authorized login, the login device can send the user's identity information in the first account system and the identifier of the authorization platform to the authentication management device. The authentication management device then queries the authorized user account in the second account system corresponding to the authorization platform based on the user's identity information. It then obtains authorization authentication information from the authorization platform through the authorized user account, thereby achieving information exchange between the respective account systems of the login device and the authorization platform. This transparent transmission of authorization authentication information is completed on the network side, avoiding multiple client jumps during the authorization login process, simplifying the authorization login operation, reducing data interaction during the authorization login process, and thus improving the efficiency of the authorization login operation. Simultaneously, due to the reduction in data interaction, the amount of data exchanged during the authorization login process is also reduced, thereby saving bandwidth usage.

[0134] The account login method provided in this application embodiment can be derived from, for example, Figure 1 The authorization login system shown interacts with the login device, authentication management device, and authorization platform. Taking the above solution as an example of a cloud gaming scenario, the login device can be a cloud gaming platform, and the authorization platform can be an instant messaging platform. Figure 6 This application illustrates an exemplary embodiment of the account login process with an interactive diagram, such as... Figure 6 As shown, the login process for this account can be as follows:

[0135] S1, the user clicks the launch entry of Cloud Game A (corresponding to the target application mentioned above) in the cloud gaming platform 610 on the terminal device, and selects to authorize login through the instant messaging platform 630.

[0136] S2, the cloud gaming platform 610 sends a first authentication request to the authentication management device 620. The first authentication request may include the user's identity information in the first account system corresponding to the cloud gaming platform 610 (such as the user's user account in the cloud gaming platform) and the identifier of the instant messaging platform 630.

[0137] S3, after receiving the first authentication request, the authentication management device 620 searches for the authorized user account corresponding to the user's identity information from the pre-stored association information in the authentication management system. This authorized user account is a user account in the second account system corresponding to the instant messaging platform 630. Then, based on the identifier of the instant messaging platform 630, the authentication management device 620 sends second authentication information containing the authorized user account to the instant messaging platform 630.

[0138] S4, after receiving the second authentication information, the instant messaging platform 630 generates authorization authentication information based on the first account information in the second authentication request and the cloud game A indicated by the second authentication information.

[0139] S5, the instant messaging platform 630 sends the authorization and authentication information to the authentication management device 620.

[0140] S6, the authentication management device 620 sends the authorization and authentication information to the cloud gaming platform 610.

[0141] After obtaining the authorization and authentication information, the cloud gaming platform 610 uses the authorized user account to log in to cloud gaming A based on the authorization and authentication information.

[0142] In this embodiment of the application, before the authorization login process, the user can first perform a user authorization process, that is, authorize the user's account information in the second account system and the user identity information in the first account system to the authentication management system, thereby allowing the authentication management system to directly interact with the authorization platform to obtain the user's authorization authentication information.

[0143] Figure 7 This illustration shows an interactive diagram of an account login method according to an exemplary embodiment of this application. This account login method can be executed interactively by a login device, an authentication management device, and an authorization platform, such as... Figure 7 As shown, the account login method includes the following steps:

[0144] Step 701: The login device sends a first authorization request to the authentication management device; correspondingly, the authentication management device receives the first authorization request; the first authorization request includes the authorized user account, the account verification information of the authorized user account, and the user identity information.

[0145] This authorized user account is a user account within the second account system corresponding to the authorized platform.

[0146] Optionally, the login device can be a terminal device or a server.

[0147] Indicatively, the login device can be a terminal device with a management application installed; the management application contains a launch entry for at least one application, and the target application is one of at least one application; for example, in a cloud gaming scenario, the login device can be a terminal device with a platform application corresponding to the cloud gaming platform installed, and the cloud gaming platform can contain a launch entry for at least one cloud game.

[0148] Alternatively, the login device may be an application server that manages the application.

[0149] Alternatively, the login device is a terminal device with the target application installed.

[0150] The way the first authorization request is sent can also differ depending on the implementation of the login device.

[0151] As an illustration, when the login device is a terminal device, it can directly send the first authorization request to the authentication management device; or when the login device is a terminal device, it can send the first authorization request to the authentication management device through an intermediate server; the intermediate server can be an application server for the management application installed on the login device, or the intermediate server can be an application server for the target application installed on the login device.

[0152] When the login device is a server, it can send the first authorization request to the authentication management device after receiving it from the corresponding terminal device. For example, when the login device is an application server for a management application, the terminal device corresponding to the login device is a terminal device with the management application installed. When the login device is a server for a target application, the terminal device corresponding to the login device is a terminal device with the target application installed.

[0153] Optionally, in response to receiving a user authorization operation, the login device sends a first authorization request to the authentication management device. This user authorization operation can be an authorization operation performed by the user based on a management application; alternatively, it can be an authorization operation performed by the user after launching an application within the management application. This user authorization operation authorizes the authentication management device to access the user's account information in the second account system and the user's identity information in the first account system, thereby enabling the authentication management device to establish a link between account information and user identity information across different account systems.

[0154] If the user authorization operation is an application-based authorization operation performed by the user, when the login device is a terminal device with the target application installed, the first authorization request can directly carry the identifier of the target application. Alternatively, the first authorization request itself can indirectly indicate (e.g., through the request structure) the target application. When the login device is a terminal device with a management application installed, since the management application contains the launch entry point of at least one application, when generating the first authorization request, the management application can generate different first authorization requests corresponding to different applications, or carry the program identifier of each application in the first authorization request corresponding to different applications, in order to distinguish the first authorization requests of different applications.

[0155] Optionally, if the user authorization operation is an authorization operation performed by the user based on the management application, and the first authorization request does not indicate a specific application, then after the authorization process is completed, the user can authorize the login of the application containing the launch entry in the management application based on the authorized user account.

[0156] Taking the user authorization operation as an example where the user launches the application in the management application and initiates the authorization prompt page displayed on the terminal device, the authorization prompt page may display an authorization confirmation control; in response to receiving the selection operation of the authorization confirmation control, the terminal device with the management application installed initiates the following user authorization process:

[0157] Based on the authorization operation in the above-mentioned user authorization process, the terminal device authorizes the user's authorized user account in the second account system, the account verification information corresponding to the authorized user account, and the user's identity information in the first account system to the authentication management device. This establishes a relationship between the authorized user account and the user's identity information in the authentication management device, so that the authorization login process can be automatically completed based on the user's identity information in subsequent operations.

[0158] Figure 8 A schematic diagram illustrating a user authorization process according to an exemplary embodiment of this application is shown, such as... Figure 8 As shown, in the user authorization process, when the terminal device receives a selection operation on the authorization confirmation control in the authorization prompt page 810, it displays the first acquisition page 820; this first acquisition page may include at least one method selection control 830, which is used to determine the method of obtaining user identity information based on the user's selection operation. Figure 8 As shown, the method selection control 830 may include at least one of the following: face authorization control, fingerprint authorization control, password authorization control, and passwordless authorization control.

[0159] Optionally, in response to receiving a user's selection of any of the face authorization control, fingerprint authorization control, or password authorization control, the terminal device displays an identity information entry page corresponding to the selected control, through which user identity information is obtained. At this time, the user identity information includes face information, fingerprint information, or account password information; wherein, the account password information includes an authenticated user account and a verification password for the authenticated user account, and the authenticated user account is a user account in the first account system. Optionally, after the user identity information is obtained, the system returns to the first acquisition page.

[0160] If the terminal device receives the user's selection of the passwordless authorization control, it means that when logging into the user account in the application through the authorized login method, no identity verification is required. For example, when logging in with an authorized user account in the authorization platform, there is no need to switch to the identity verification page. Optionally, at this time, the user identity information can be implemented as the user's certified user account in the first account system mentioned above.

[0161] In response to receiving the "Next" setting operation performed on the first acquisition page 820, the terminal device displays a second selection page 840; the second selection page 840 may display at least one platform selection control, and different platform controls correspond to different authorized platforms.

[0162] In response to receiving a selection operation for a target platform selection control, the terminal device displays an account information retrieval page for the authorized platform corresponding to the target platform selection control; the target platform selection control is any one of at least one platform selection control.

[0163] Optionally, the account information retrieval page can be an input interface for account information and account verification information in the account system corresponding to the platform; illustratively, the account information can be a user identity account in the account system corresponding to the authorized platform, and the account verification information can be a login password; or, the account information can be a communication account in the account system, and the account verification information can be a login verification code received in real time by the communication account; or, in response to the terminal device having a platform application corresponding to the target platform selection control installed locally, the account information retrieval page can also be an account authorization page displayed after jumping to the authorized platform application, and in response to receiving an authorization operation based on the account authorization interface, the platform server corresponding to the authorized platform program sends the account information and the account verification information to the terminal device.

[0164] In this embodiment, the login device can obtain the authorized user account and the corresponding account verification information of the authorized platform based on the account information and account verification information obtained from the account information acquisition page. For example, the account information and account verification information obtained from the account information acquisition page can be directly obtained as the authorized user account and the corresponding account verification information of the authorized platform; alternatively, the authorized user account and the corresponding account verification information of the authorized platform can be obtained from the authorized platform based on the account information and account verification information obtained from the account information acquisition page.

[0165] Optionally, after obtaining the authorized user account, account verification information, and user identity information, the terminal device displays the agreement signing page 850; after receiving the agreement confirmation operation based on the agreement signing page 850, the terminal device sends a first authorization request containing the authorized user account, account verification information, and user identity information to the authentication management device.

[0166] Step 702: The authentication management device sends a verification request to the authorization platform, and the authorization platform receives the verification request accordingly; the verification request contains the authorized user account and account verification information.

[0167] Optionally, after receiving the verification request, the authorization platform may check whether the authorized user account and the account verification information match based on the relationship between the authorized user account and the account verification information recorded in the platform's database, in order to verify the legality of the user authorization process.

[0168] Step 703: The authorization platform returns the verification result to the authentication management device, and the authentication management device receives the verification result accordingly.

[0169] The verification result is used to indicate whether the authorized user account matches the account verification information.

[0170] Step 704: In response to the verification result indicating that the authorized user account matches the account verification information, the authentication management device sets the association relationship between the user identity information and the authorized user account in the association relationship information.

[0171] In other words, when the verification result indicates that the authorized user account and the account verification information are valid, the authentication management device establishes an association between the user identity information and the authorized user account, and stores this association in the association information of the authentication management device.

[0172] Optionally, the authentication management device can also store the user identity information obtained in the user authorization process as an identity verification template to verify the legitimacy of the identity of the user who subsequently initiates the authorization login process.

[0173] Optionally, when the first authorization request indirectly indicates the target application, or when the first authorization request contains the identifier of the target application, the authentication management device may establish an association between the user identity information, the authorized user account, and the identifier of the target application.

[0174] Optionally, when the first authorization request indirectly indicates the target application, or when the first authorization request contains the identifier of the target application, the authentication management device can store the association between the user identity information and the authorized user account in the association information corresponding to the target application after establishing the association relationship; accordingly, different applications may have different association information in the authentication management device.

[0175] Step 705: The authentication management device returns the authorization request result to the login device. Correspondingly, the login device receives the authorization request result, which is generated by the authentication management device based on the verification result returned by the authorization platform.

[0176] Step 706: The logged-in device displays an authorization result prompt page based on the authorization request result.

[0177] In response to the authorization request result indicating that the first authorization request was approved, the authorization result display page may be as follows: Figure 8 The authorization result prompt page 860 shown displays authorization completion information, which indicates that the current user's authorization process was successful.

[0178] Optionally, the authorization result prompt page may also display information about the authorized platforms to indicate the currently authorized platforms.

[0179] Optionally, the authorization result prompt page also displays a platform addition control, which is used to trigger a new user authorization process. That is, after a user completes the user authorization process for a platform selection control, if the user needs to authorize other platforms, they can restart the user authorization process for the new platform by selecting the platform addition control displayed on the authorization result prompt page; or, the user can also start a new user authorization process through the settings control in the management application.

[0180] Step 707: The login device displays an authorization login interface through the terminal device, which displays at least one platform control.

[0181] If the login device is a terminal device, the above process can display the authorized login interface for the login device.

[0182] In response to the login device being a server, the above process can be implemented as follows: a terminal device installed with an application corresponding to the login device displays the above authorization login interface.

[0183] Optionally, in response to receiving a startup operation for a target application, the terminal device displays an authorization login interface corresponding to the target application.

[0184] It should be noted that the startup operation of the target application and the above user authorization process may be independent processes, that is, they do not have temporal continuity. For example, after the user triggers and completes the user authorization process through a setting control of a management application, the user may not perform the authorization login operation for the target application, and perform the authorization login operation after a period of time.

[0185] In a possible implementation, the at least one platform control displayed on the authorization login interface is a platform control corresponding to an authorization platform supported by the target application, that is, the number and type of platform authorization controls that can be displayed on the authorization login interface corresponding to the target application are determined based on relevant settings of the target application. For example, if the target application supports n authorization platforms, n platform controls respectively corresponding to the n authorization platforms are displayed on the authorization login interface, where n is a positive integer; optionally, the number and type of authorization platforms supported by different applications may be the same or different.

[0186] Alternatively, in another possible implementation, the at least one platform control displayed on the authorization login interface is a control corresponding to an authorization platform that has been authorized to the authentication management device; for example, if the target application supports n authorization platforms, and in the user authorization process, the number of authorization platforms that have been authorized to the authentication management system is m, then m platform controls respectively corresponding to the m authorization platforms are displayed on the authorization login interface, where m < n and m is a positive integer.

[0187] Figure 9 shows a schematic diagram of an authorization login interface provided by an exemplary embodiment of the present application, as Figure 9 shown, the authorization login interface is an authorization login interface 910 of the target application displayed in the terminal device in response to a user's program startup operation for the target application (the third application in the application list as shown in Figure 9 ); the authorization login interface may include at least one platform control 920 for logging into the target application; the at least one platform control 920 may be a platform control of an authorization platform supported by the target application, or may also be a control corresponding to an authorization platform that has been authorized to the authentication management device. The at least one platform control 920 is used to trigger an authorization login process, for example, trigger generation of a first authentication request.

[0188] Optionally, in response to at least one platform control being a platform control of an authorized platform supported by the target application, and the authorized platform corresponding to the first platform control selected by the user during the selection operation is not an authorized platform that has already been authorized to the authentication management device, that is, the authentication management device does not pre-store the association relationship between the authorized user account and the user identity information under the account system of the platform corresponding to the first platform control, then the authorization login process initiated based on the first platform control cannot be completed; in this case, when it is determined that the first platform control is not an authorized platform that has already been authorized to the authentication management device, the terminal device can display an authorization prompt page so that the user can trigger the user authorization process based on the authorization prompt page, and store the association relationship between the authorized user account and the user identity information under the account system of the platform corresponding to the first platform control in the authentication management device, so that the authorization login process can be completed based on the first platform control in subsequent operations.

[0189] Alternatively, in another possible implementation, in response to the fact that the authorization platform corresponding to the first platform control is not an authorization platform that has been authorized to the authentication management device, the terminal device can set the first platform control in the authorization login interface to an unavailable state.

[0190] Step 708: In response to receiving a selection operation for a target platform control, the login device determines the identifier of the authorized platform; the target platform control is any one of at least one platform control.

[0191] Step 709: The login device generates a first authentication request based on the identifier of the authorized platform.

[0192] Optionally, the login device generates a first authentication request based on the authorized platform identifier and the user's identity information.

[0193] The user identity information includes at least one of the following: facial information, fingerprint information, account password information, and authenticated user account;

[0194] The account password information includes the authenticated user account and the verification password for the authenticated user account; the authenticated user account is a user account in the first account system.

[0195] Optionally, the identifier of the authorization platform and the user identity information are obtained in the same stage. For example, in response to the user identity information being an authenticated user account, when the login device receives the user's selection operation on the target platform control, it can generate a first authentication request based on the known authenticated user account and the identifier of the authorization platform. This method can correspond to scenarios where the user chooses passwordless login in the authorization process. The aforementioned known authenticated user account can be a user account logged in on the terminal device.

[0196] Alternatively, in response to the user's identity information being any one of facial information, fingerprint information, or account password information, the terminal device needs to enter information acquisition mode to obtain the corresponding user identity information when it receives the user's selection operation on the target platform control.

[0197] Optionally, in response to the user setting at least two methods for obtaining identity information during the user authorization process, the user identity information can be determined to be obtained after obtaining the user identity information corresponding to one of the methods; and a first authentication request can be generated based on the obtained user identity information and the identifier of the authorization platform.

[0198] In this embodiment of the application, the way the terminal device enters the information acquisition mode may include displaying an identity information acquisition page on the display interface of the terminal device, or setting the hardware device in the terminal device used to acquire user identity information to a working mode, at least one of the following:

[0199] Figure 10 A schematic diagram illustrating the display interface of a terminal device according to an exemplary embodiment of this application is shown, such as... Figure 10 As shown, the terminal device displays an authorization login interface 1010 for the target application, which includes at least one platform control. In response to a selection operation on the target platform control 1020, the terminal device displays an identity information acquisition page, which corresponds to the required user identity information. Illustratively, when the required user identity information is facial information, the identity information acquisition page displays a facial information acquisition page 1031. After facial verification is successful and the authorization login process is completed, the target application interface 1040 based on the authorized user account login is displayed. When the required user identity information is fingerprint information, the identity information acquisition page displays a fingerprint information acquisition page 1032. After fingerprint verification is successful and the authorization login process is completed, the target application interface 1040 based on the authorized user account login is displayed. When the required user identity information is account password information, the identity information acquisition page displays a password input page 1033. After password verification is successful and the authorization login process is completed, the target application interface 1040 based on the authorized user account login is displayed.

[0200] Optionally, when a user has set multiple methods for obtaining user identity information, and page switching occurs during the process of obtaining user identity information, the system can display the identity information acquisition pages corresponding to different methods based on the user's pre-set priority and the user's switching operation, until the user's identity information is obtained. It should be noted that the above descriptions of user identity information and the first acquisition page are for illustrative purposes only.

[0201] In some possible implementations, the display interface of the login device may remain unchanged during the process of obtaining user identity information. For example, when obtaining facial information, the facial information can be collected directly by calling the camera of the login device; when obtaining fingerprint information, fingerprint information can be obtained by calling the fingerprint sensor, and so on.

[0202] Optionally, in the scenario of passwordless login, after receiving the selection operation of the target platform control, the authorization login process is entered. After the authorization login process is completed, the interface 1040 of the target application logged in based on the authorized user account is displayed.

[0203] Step 710: The login device sends a first authentication request to the authentication management device. The first authentication request contains the identifier of the authorized platform and the user's identity information. Correspondingly, the authentication management device receives the first authentication request.

[0204] The login device and the authentication management device each have their own open interfaces to enable information exchange between them.

[0205] Step 711: The authentication management device obtains the authorized user account corresponding to the user identity information stored in the authentication management device.

[0206] Optionally, the authentication management device may query the association information stored in the authentication management device based on the user's identity information to obtain the authorized user account; the association information includes the association between the user's identity information and the authorized user account.

[0207] This association information is pre-stored in the authentication management device during the user authorization process.

[0208] In one possible implementation, if the association information in the authentication management device corresponds to different applications, and the first authentication request indirectly indicates the target application or directly carries the identifier of the target application, the authentication management device can also query the association information corresponding to the target application based on the first authentication request to obtain the authorized user account.

[0209] In another possible implementation, if the association information in the authentication management device contains the association relationship between the identity information, user account, and application identifier, and the first authentication request indirectly indicates the target application or directly carries the identifier of the target application, the authentication management device can also query the above association information based on the user identity identifier and the identifier of the target application to obtain the above authorized user account.

[0210] Optionally, the identifier of the authorized platform and the user identity information included in the first authentication request are obtained and sent to the authentication management device at different stages. In this case, the sending process of the first authentication request can be as follows:

[0211] In response to receiving a selection operation for the target platform control, a first authentication sub-request is generated and sent to the authentication management device. The first authentication sub-request contains the authorized platform identifier and the authentication user account.

[0212] In response to receiving an information acquisition request from the authentication management device, the user's identity information is obtained based on the information acquisition request.

[0213] Based on the user's identity information, a second authentication sub-request is generated and sent to the authentication management device.

[0214] In other words, the first authentication request includes a first authentication sub-request and a second authentication sub-request obtained in stages. Specifically, when the login device receives an information retrieval request from the authentication management device, it controls the terminal device to enter information retrieval mode to obtain the user identity information indicated in the information retrieval request. At this time, the user identity information is matched against the identity verification template in the authentication management device, enabling the authentication management device to verify the legitimacy of the user initiating the authorization login process. After verifying the user's legitimacy, the authentication management device obtains the authorized user account based on the authenticated user account or the user identity information.

[0215] Step 712: The authentication management device sends a second authentication request to the authorization platform based on the identifier of the authorization platform, and the authorization platform receives the second authentication request accordingly.

[0216] The second authentication request contains the authorized user account.

[0217] The authentication management device and the authorization platform each have corresponding open interfaces to enable information exchange between them.

[0218] Step 713: The authorization platform generates authorization authentication information based on the authorized user account.

[0219] Step 714: The authorization platform sends the authorization and authentication information to the authentication management device, and the authentication management device receives the authorization and authentication information accordingly.

[0220] Step 715: The authentication management device sends the authorization authentication information to the login device, and the login device receives the authorization authentication information accordingly.

[0221] Step 716: The login device logs into the target application based on the authorization and authentication information.

[0222] Optionally, in cloud application scenarios, after receiving the authorization and authentication information, the login device sends the authorization and authentication information to the cloud application server; the cloud application server verifies the legality of the obtained authorization and authentication information, and after the verification is successful, performs account login in the target application running on the cloud application server based on the authorization and authentication information.

[0223] The cloud application server can verify the legality of the authorization and authentication information by interacting with the authorization platform to determine the legality of the authorization and authentication information.

[0224] Optionally, the process of logging into the target application on the cloud application server can involve the cloud application server internally starting an Android container to launch the target application within that container, simultaneously initiating screen rendering, and then transmitting the rendered streaming media data in real-time to a terminal device with display capabilities via a long-lived connection established between the cloud application server and the logged-in device. This allows the terminal device with display capabilities to display the cloud application's screen. An Android container refers to packaging Android into a container image and then distributing it using a standard container image. The carrier can be any container shell supporting the OCI (Open Container Initiative) standard. Therefore, it can be maintained using Kubernetes (k8s). Leveraging k8s' powerful operational tools, a large number of server clusters can be deployed in the cloud.

[0225] During the execution of the target application by the cloud application, the cloud application server interacts with the target application server to obtain basic information about the user in the target application, such as the user's account, level, virtual assets, friend list, etc.

[0226] Optionally, when the cloud application server interacts with the server of the target application, since the cloud application server has obtained the authorization and authentication information, the cloud application server can interact with the server of the target application through the authorization and authentication information, or the cloud application server can interact with the server of the target application through the program identifier of the target application.

[0227] Optionally, during the operation of the target application, the cloud application server also interacts in real time with the application server that manages the application to record and process relevant user data in the cloud application server. For example, the relevant data may include user usage time, user remaining usage time, etc.

[0228] In summary, the account login method provided in this application adds an authentication management device between the login device and the authorization platform of the target application. In scenarios requiring authorized login, the login device can send the user's identity information in the first account system and the identifier of the authorization platform to the authentication management device. The authentication management device then queries the authorized user account in the second account system corresponding to the authorization platform based on the user's identity information. It then obtains authorization authentication information from the authorization platform through the authorized user account, thereby achieving information exchange between the respective account systems of the login device and the authorization platform. This transparent transmission of authorization authentication information is completed on the network side, avoiding multiple client jumps during the authorization login process, simplifying the authorization login operation, reducing data interaction during the authorization login process, and thus improving the efficiency of authorization login. Simultaneously, due to the reduction in data interaction, the amount of data exchanged during the authorization login process is also reduced, thereby saving bandwidth usage.

[0229] Meanwhile, the solution shown in the embodiments of this application also avoids frequent interactions between clients and between clients and servers, reduces the time occupied during the interaction process and the waste of processing resources, thereby improving the efficiency of authorized login operations;

[0230] In addition, the solution shown in the embodiments of this application can avoid the program installation process during the authorization login process, thus simplifying the authorization login process, provided that no second application corresponding to the authorized platform is installed on the terminal device.

[0231] To illustrate, taking a cloud gaming scenario as an example, the login device in the above scheme can be a terminal device in the cloud gaming platform or an application server of the cloud gaming platform, and the authorization platform can be an instant messaging platform. Figure 11 This illustration shows a schematic diagram of an account login method in a cloud gaming scenario, as shown in an exemplary embodiment of this application. This account login method is executed interactively by the cloud gaming platform, the authentication management system, and the instant messaging platform. Figure 11 As shown, the account login process includes a user authorization process and an authorization login process;

[0232] When a user launches a cloud gaming application through the cloud gaming platform, or when a user performs settings operations on the cloud gaming platform, a user authorization process is initiated, which may include the following steps:

[0233] S1, the terminal device 1110 in the cloud gaming platform sends a first authorization request containing the authorized user account in the instant messaging platform 1140, the account verification information of the authorized user account, and the user identity information corresponding to the authorization method to the authentication management device 1130.

[0234] The terminal device has the cloud gaming platform's application installed.

[0235] Users can determine the authorization method, authorization platform, authorized user account in the authorization platform, and account verification information of the authorized user account based on the first acquisition page, second selection page, and agreement signing page displayed on the terminal device 1110.

[0236] S2, the authentication management device 1130 sends the authorized user account in the first authorization request and the account verification information of the authorized user account to the instant messaging platform 1140 to verify whether the two match.

[0237] S3, the instant messaging platform 1140 returns the verification result to the authentication management device 1130.

[0238] S4, in response to the verification result indicating that the authorized user account and the account verification information of the authorized user account match, the authentication management device 1130 sends the authorization request result of the first authorization request to the terminal device 1110.

[0239] When the authentication management device 1130 responds to the verification result indicating that the authorized user account and the account verification information of the authorized user account match, it sets up the association between the user identity information and the authorized user account within the authentication management device.

[0240] After receiving the authorization request result, the terminal device 1110 displays an authorization result prompt page. Based on the authorization completion indication information displayed on the authorization result prompt page, the user confirms that the user authorization process has ended.

[0241] After the user authorization process is completed, when the user launches the cloud game through the cloud gaming platform's application, the terminal device displays an authorization login interface. When the user selects a target platform control on this authorization login interface, the authorization login process is triggered. This authorization login process may include the following steps:

[0242] S5, terminal device 1110 sends the first authentication request to application server 1120 of cloud gaming platform.

[0243] The first authentication request may be generated by the terminal device 1110 based on the identifier of the instant messaging platform determined by the target platform control, and combined with the user identity information obtained by the terminal device 1110 (such as face, fingerprint, password, and authenticated user account, which is the user's account in the corresponding account system of the cloud gaming platform).

[0244] S6, after receiving the first authentication request, the application server 1120 of the cloud gaming platform sends the first authentication request to the authentication management device 1130.

[0245] S7, after receiving the first authentication request, the authentication management device 1130 sends a second authentication request containing the first account information to the instant messaging platform 1140.

[0246] The instant messaging platform 1140 is the platform through which the authentication management device 1130 interacts with information based on the identifier of the instant messaging platform in the first authentication request; the first account information is the account information corresponding to the user identity information obtained by the authentication management device 1130 based on the user identity information in the first authentication request and the association information stored locally.

[0247] S8, the instant messaging platform 1140 sends authorization authentication information (token) back to the authentication management device 1130 based on the first account information.

[0248] The instant messaging platform 1140 queries the platform database of the authorized platform based on the first account information, and performs authorization authentication based on the user's basic registration information found in the query; after the instant messaging platform 1140 completes the authorization authentication, it generates and sends the authorization authentication information back to the authentication management device 1130.

[0249] S9, the authentication management device 1130 sends the authorization and authentication information to the application server 1120 of the cloud gaming platform.

[0250] The application server 1120 of the cloud gaming platform can, based on the authorization and authentication information, instruct the cloud gaming server 1150 to log in to the cloud game using the authorized user account, thereby completing the authorization login between different account systems in the cloud gaming scenario. The interaction process between the cloud gaming server and the terminal device can be referenced. Figure 2 The relevant details of the illustrated embodiments will not be repeated here.

[0251] The timing of the user authorization process and the authorization login process may be discontinuous.

[0252] To illustrate, taking a PC game scenario as an example, the login device in the above scheme can be a terminal device in the PC game platform, or the application server of the PC game application, and the authorization platform can be an instant messaging platform. Figure 12 This illustration shows a schematic diagram of an account login method in a client-side game scenario, as shown in an exemplary embodiment of this application. This account login method is executed interactively by the client-side game platform, the authentication management system, and the instant messaging platform. Figure 12 As shown, the account login process includes a user authorization process and an authorization login process;

[0253] When a user launches the PC game application, or when a user performs a settings operation on the PC game application, a user authorization process is initiated, which may include the following steps:

[0254] S1, the terminal device 1210 sends a first authorization request containing the authorized user account in the instant messaging platform 1240, the account verification information of the authorized user account, and the user identity information corresponding to the authorization method to the authentication management device 1230.

[0255] The terminal device has a PC game application installed.

[0256] Users can determine the authorization method, authorization platform, authorized user account in the authorization platform, and account verification information of the authorized user account based on the first acquisition page, the second selection page, and the agreement signing page displayed on the terminal device 1210.

[0257] S2, the authentication management device 1230 sends the authorized user account in the first authorization request and the account verification information of the authorized user account to the instant messaging platform 1240 to verify whether the two match.

[0258] S3, the instant messaging platform 1240 returns the verification result to the authentication management device 1230.

[0259] S4, in response to the verification result indicating that the authorized user account and the account verification information of the authorized user account match, the authentication management device 1230 sends the authorization request result of the first authorization request to the terminal device 1210.

[0260] When the authentication management device 1230 responds to the verification result indicating that the authorized user account and the account verification information of the authorized user account match, it sets up the association between the user identity information and the authorized user account within the authentication management device.

[0261] After receiving the authorization request result, the terminal device 1210 displays an authorization result prompt page. Based on the authorization completion indication information displayed on the authorization result prompt page, the user confirms that the user authorization process has ended.

[0262] After the user authorization process has been completed, when the local login of the client game application expires and the user needs to log in again, in response to the terminal device 1210 receiving the user's selection operation on the target platform control in the authorization login interface, the authorization login process is triggered. The authorization login process may include the following steps:

[0263] S5, terminal device 1210 sends the first authentication request to application server 1220 of client game application.

[0264] The first authentication request may be generated by the login device 1110 based on the identifier of the authorized platform determined by the target platform control, and combined with the user identity information obtained by the login device 1110 (such as face, fingerprint, password, and authenticated user account, which is the user's account in the account system corresponding to the client game application).

[0265] S6, after receiving the first authentication request, the application server 1220 of the client game application sends the first authentication request to the authentication management device 1230.

[0266] S7, after receiving the first authentication request, the authentication management device 1230 sends a second authentication request containing the first account information to the instant messaging platform 1240.

[0267] Among them, the instant messaging platform 1240 is the platform for information interaction determined by the authentication management device 1230 based on the identifier of the instant messaging platform in the first authentication request; the first account information is the account information corresponding to the user identity information obtained by the authentication management device 1230 based on the user identity information in the first authentication request and the association information stored locally.

[0268] S8, the instant messaging platform 1240 sends authorization authentication information (token) to the authentication management device 1230 based on the first account information.

[0269] The instant messaging platform 1240 queries the platform database of the authorized platform based on the first account information, and performs authorization authentication based on the user's basic registration information found in the query; after the instant messaging platform 1240 completes the authorization authentication, it generates and sends the authorization authentication information back to the authentication management device 1230.

[0270] S9, the authentication management device 1230 sends the authorization and authentication information to the application server 1220 of the client game application.

[0271] The application server 1220 of the PC game application can complete the authorized login between different account systems in the PC game scenario based on the authorization and authentication information.

[0272] In one possible implementation, to ensure the security and accuracy of user information during the authorization login process, the data in the platform database of the authorization platform involved in the account login method disclosed in this application, as well as the account information and user identity information obtained by the authentication management device, can all be stored on the blockchain.

[0273] It is understood that the specific implementation of this application involves data such as facial information, fingerprint information, password information and account information. When the above implementation of this application is applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0274] Figure 13 The diagram illustrates a block diagram of an account login device according to an exemplary embodiment of this application. The device is applied in an authentication management device, which maintains the relationship between user identity information in a first account system and user accounts in other account systems, wherein the other account systems are account systems outside the first account system. The device includes:

[0275] The first request receiving module 1310 is used to receive a first authentication request sent by the login device. The first authentication request includes the identifier of the authorization platform and the user identity information. The authorization platform corresponds to the second account system.

[0276] The account acquisition module 1320 is used to acquire the authorized user account stored in the authentication management device that corresponds to the user identity information;

[0277] The first request sending module 1330 is used to send a second authentication request to the authorization platform based on the identifier of the authorization platform, wherein the second authentication request contains the authorized user account;

[0278] The first information receiving module 1340 is used to receive authorization authentication information sent by the authorization platform based on the authorized user account;

[0279] The first information sending module 1350 is used to send the authorization and authentication information to the login device, wherein the authorization and authentication information is information used by the login device to log in to the target application.

[0280] In one possible implementation, the account acquisition module 1320 is used to query the association information stored in the authentication management device based on the user identity information to obtain the authorized user account; the association information includes the association relationship between the user identity information and the authorized user account.

[0281] In one possible implementation, the device further includes:

[0282] The third request receiving module is used to receive the first authorization request sent by the login device; the first authorization request includes the authorized user account, the account verification information of the authorized user account, and the user identity information;

[0283] The third request sending module is used to send a verification request to the authorization platform, wherein the verification request includes the authorized user account and the account verification information;

[0284] The association setting module is used to respond to receiving the verification result returned by the authorization platform, and the verification result indicates that the authorized user account matches the account verification information, and to set the association relationship between the user identity information and the authorized user account in the association relationship information.

[0285] In one possible implementation, the user identity information includes at least one of the following:

[0286] Facial information, fingerprint information, account password information, and verified user accounts;

[0287] The account password information includes the authenticated user account and the verification password of the authenticated user account; the authenticated user account is a user account in the first account system.

[0288] In one possible implementation, the login device is a terminal device with a management application installed; the management application includes a launch entry for at least one application, and the target application is one of the at least one application;

[0289] Alternatively, the login device is the application server of the management application;

[0290] Alternatively, the login device is a terminal device with the target application installed.

[0291] In summary, the account login device provided in this application adds an authentication management device between the login device and the authorization platform of the target application. In scenarios requiring authorized login, the login device can send the user's identity information in the first account system and the identifier of the authorization platform to the authentication management device. The authentication management device then queries the authorized user account in the second account system corresponding to the authorization platform based on the user's identity information. It then obtains authorization authentication information from the authorization platform through the authorized user account, thereby achieving information exchange between the respective account systems of the login device and the authorization platform. This transparent transmission of authorization authentication information is completed on the network side, avoiding multiple client jumps during the authorization login process, simplifying the authorization login operation, reducing data interaction during the authorization login process, and thus improving the efficiency of authorization login. Simultaneously, due to the reduced data interaction process, the amount of data exchanged during the authorization login process is also reduced, thereby saving bandwidth usage.

[0292] Figure 14 A block diagram of an account login apparatus illustrated in an exemplary embodiment of this application is shown. The apparatus is applied in a login device and includes:

[0293] The second request sending module 1410 is used to send a first authentication request to the authentication management device. The first authentication request includes the identifier of the authorization platform and user identity information. The authentication management device stores the relationship between the user identity information in the first account system and the authorized user account in the second account system. The authorization platform corresponds to the second account system.

[0294] The second information receiving module 1420 is used to receive authorization authentication information sent by the authentication management device; the authorization authentication information is obtained by the authentication management device based on the first authentication request, which retrieves the authorized user account stored in the authentication management device corresponding to the user identity information, and sends a second authentication request to the authorization platform based on the identifier of the authorization platform, and then the authorization platform sends it to the authentication management device based on the authorized user account; the second authentication request includes the authorized user account;

[0295] The program login module 1430 is used to log in to the target application based on the authorization and authentication information.

[0296] In one possible implementation, the device further includes:

[0297] The interface display module is used to display the authorization login interface, which displays at least one platform control.

[0298] An identifier determination module is used to determine the identifier of the authorized platform in response to receiving a selection operation on a target platform control; the target platform control is any one of the at least one platform control;

[0299] The request generation module is used to generate the first authentication request based on the identifier of the authorization platform.

[0300] In one possible implementation, the device further includes:

[0301] The fourth request sending module is used to send a first authorization request to the authentication management device. The first authorization request includes the authorized user account, the account verification information of the authorized user account, and the user identity information. The first authorization request is used to trigger the authentication management device to send a verification request to the authorization platform. When the verification result returned by the authorization platform is received, and the verification result indicates that the authorized user account matches the account verification information, the module sets the association relationship between the user identity information and the authorized user account in the association relationship information. The verification request includes the authorized user account and the account verification information.

[0302] In summary, the account login device provided in this application adds an authentication management device between the login device and the authorization platform of the target application. In scenarios requiring authorized login, the login device can send the user's identity information in the first account system and the identifier of the authorization platform to the authentication management device. The authentication management device then queries the authorized user account in the second account system corresponding to the authorization platform based on the user's identity information. It then obtains authorization authentication information from the authorization platform through the authorized user account, thereby achieving information interaction between the respective account systems of the login device and the authorization platform. This transparent transmission of authorization authentication information is completed on the network side, avoiding multiple client jumps during the authorization login process, simplifying the authorization login operation, reducing data interaction during the authorization login process, and thus improving the efficiency of the authorization login operation. Simultaneously, due to the reduced data interaction process, the amount of data exchanged during the authorization login process is also reduced, thereby saving bandwidth usage.

[0303] Figure 15 A block diagram of an account login device illustrated in an exemplary embodiment of this application is shown. The device is applied in an authorization platform and includes:

[0304] The second request receiving module 1510 is used to receive a second authentication request sent by the authentication management device; the authentication management device stores the relationship between user identity information in the first account system and authorized user accounts in the second account system; the second authentication request is sent by the authentication management device based on the identifier of the authorization platform; the identifier of the authorization platform is carried by the first authentication request sent by the login device; the second authentication request includes the authorized user account stored in the authentication management system that corresponds to the user identity information in the first authentication request; the user identity information is the user identity information in the first account system; the authorization platform corresponds to the second account system;

[0305] Information generation module 1520 is used to generate authorization authentication information based on the authorized user account;

[0306] The second information sending module 1530 is used to send the authorization and authentication information to the authentication management device, so that the authentication management device can pass the authorization and authentication information to the login device. The authorization and authentication information is information used by the login device to log in to the target application.

[0307] In summary, the account login device provided in this application adds an authentication management device between the login device and the authorization platform of the target application. In scenarios requiring authorized login, the login device can send the user's identity information in the first account system and the identifier of the authorization platform to the authentication management device. The authentication management device then queries the authorized user account in the second account system corresponding to the authorization platform based on the user's identity information. It then obtains authorization authentication information from the authorization platform through the authorized user account, thereby achieving information interaction between the respective account systems of the login device and the authorization platform. This transparent transmission of authorization authentication information is completed on the network side, avoiding multiple client jumps during the authorization login process, simplifying the authorization login operation, reducing data interaction during the authorization login process, and thus improving the efficiency of the authorization login operation. Simultaneously, due to the reduced data interaction process, the amount of data exchanged during the authorization login process is also reduced, thereby saving bandwidth usage.

[0308] Figure 16A structural block diagram of a computer device 1600 illustrating an exemplary embodiment of this application is shown. This computer device can be implemented as various servers described in the above-described schemes of this application. The computer device 1600 includes a Central Processing Unit (CPU) 1601, a system memory 1604 including Random Access Memory (RAM) 1602 and Read-Only Memory (ROM) 1603, and a system bus 1605 connecting the system memory 1604 and the CPU 1601. The computer device 1600 also includes a mass storage device 1606 for storing an operating system 1609, a client 1610, and other program modules 1611.

[0309] The mass storage device 1606 is connected to the central processing unit 1601 via a mass storage controller (not shown) connected to the system bus 1605. The mass storage device 1606 and its associated computer-readable media provide non-volatile storage for the computer device 1600. That is, the mass storage device 1606 may include computer-readable media (not shown) such as a hard disk or a compact disc read-only memory (CD-ROM) drive.

[0310] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include RAM, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other solid-state storage technologies, CD-ROM, digital versatile disc (DVD) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer storage media are not limited to the above-mentioned types. The system memory 1604 and mass storage device 1606 described above can be collectively referred to as memory.

[0311] According to various embodiments of this disclosure, the computer device 1600 can also be connected to a remote computer on a network, such as the Internet. That is, the computer device 1600 can be connected to a network 1608 via a network interface unit 1607 connected to the system bus 1605, or it can use the network interface unit 1607 to connect to other types of networks or remote computer systems (not shown).

[0312] The memory also includes at least one instruction, at least one program, code set, or instruction set, which are stored in the memory. The central processing unit 1601 executes the at least one instruction, at least one program, code set, or instruction set to implement all or part of the steps in the account login method shown in the above embodiments.

[0313] Figure 17 A structural block diagram of a computer device 1700 illustrating an exemplary embodiment of this application is shown. The computer device 1700 can be implemented as the aforementioned terminal, such as a smartphone, tablet computer, laptop computer, or desktop computer. The computer device 1700 may also be referred to as user equipment, portable terminal, laptop terminal, desktop terminal, or other names.

[0314] Typically, computer device 1700 includes a processor 1701 and a memory 1702.

[0315] Processor 1701 may include one or more processing cores, such as a 4-core processor, a 17-core processor, etc. Processor 1701 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1701 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1701 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, processor 1701 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0316] Memory 1702 may include one or more computer-readable storage media, which may be non-transitory. Memory 1702 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in memory 1702 is used to store at least one instruction, which is executed by processor 1701 to implement all or part of the steps in the account login method shown in the method embodiments of this application.

[0317] In some embodiments, the computer device 1700 may also optionally include a peripheral device interface 1703 and at least one peripheral device. The processor 1701, memory 1702, and peripheral device interface 1703 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1703 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 1704, a display screen 1705, a camera assembly 1706, an audio circuit 1707, and a power supply 1708.

[0318] In some embodiments, the computer device 1700 further includes one or more sensors 1709. The one or more sensors 1709 include, but are not limited to: an accelerometer 1710, a gyroscope 1711, a pressure sensor 1712, a fingerprint sensor 1713, an optical sensor 1714, and a proximity sensor 1715.

[0319] Those skilled in the art will understand that Figure 17 The structure shown does not constitute a limitation on the computer device 1700, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0320] In one exemplary embodiment, a computer-readable storage medium is also provided for storing at least one computer program, which is loaded and executed by a processor to implement all or part of the steps in the account login method described above. For example, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, or optical data storage device, etc.

[0321] In one exemplary embodiment, a computer program product or computer program is also provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned actions. Figure 3 , Figure 4 , Figure 5 , Figure 7 , Figure 11 or Figure 12 All or part of the steps of the method shown in any embodiment.

[0322] Other embodiments of this application 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 application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0323] It should be understood that this application is not limited to the precise structure 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 application is limited only by the appended claims.

Claims

1. An account login method, characterized in that, The method is executed by an authentication management device located between the login device and the authorization platform of the target application. The authentication management device stores the relationship between user identity information in a first account system and authorized user accounts in a second account system. The method includes: The system receives a first authentication request sent by the login device. The first authentication request includes the identifier of the authorized platform and the user's identity information. The authorized platform corresponds to the second account system. Obtain the authorized user account corresponding to the user identity information stored in the authentication management device; Based on the identifier of the authorization platform, a second authentication request is sent to the authorization platform, the second authentication request containing the authorized user account; Receive authorization authentication information sent by the authorization platform based on the authorized user account; The authorization and authentication information is sent to the login device, and the authorization and authentication information is used by the login device to log in to the target application; The step of obtaining the authorized user account corresponding to the user identity information stored in the authentication management device includes: querying the association information stored in the authentication management device based on the user identity information to obtain the authorized user account; the association information includes the association relationship between the user identity information and the authorized user account; Before receiving the first authentication request sent by the login device, the method further includes: receiving a first authorization request sent by the login device; the first authorization request includes the authorized user account, the account verification information of the authorized user account, and the user identity information; sending a verification request to the authorization platform, the verification request including the authorized user account and the account verification information; in response to receiving a verification result returned by the authorization platform, and the verification result indicating that the authorized user account matches the account verification information, setting an association relationship between the user identity information and the authorized user account in the association relationship information; The startup operation of the target application and the user authorization process are independent of each other.

2. The method according to claim 1, characterized in that, The user identity information includes at least one of the following: Facial information, fingerprint information, account password information, and verified user accounts; The account password information includes the authenticated user account and the verification password of the authenticated user account; the authenticated user account is a user account in the first account system.

3. The method according to claim 1, characterized in that, The login device is a terminal device with a management application installed; the management application contains a startup entry for at least one application, and the target application is one of the at least one application; Alternatively, the login device is the application server of the management application; Alternatively, the login device is a terminal device with the target application installed.

4. An account login method, characterized in that, The method is executed by the login device, and the method includes: A first authentication request is sent to the authentication management device. The first authentication request includes the identifier of the authorization platform and the user's identity information. The authentication management device is located between the login device and the authorization platform. The authentication management device stores the relationship between the user's identity information in the first account system and the authorized user account in the second account system. The authorization platform corresponds to the second account system. The system receives authorization authentication information sent by the authentication management device. The authorization authentication information is obtained by the authentication management device based on the first authentication request, which retrieves the authorized user account stored in the authentication management device that corresponds to the user identity information. After the authentication management device sends a second authentication request to the authorization platform based on the identifier of the authorization platform, the authorization platform sends the information to the authentication management device based on the authorized user account. The second authentication request includes the authorized user account. Log in to the target application based on the authorization and authentication information; Before sending the first authentication request to the authentication management device, the method further includes: sending a first authorization request to the authentication management device, wherein the first authorization request includes the authorized user account, the account verification information of the authorized user account, and the user identity information; the first authorization request is used to trigger the authentication management device to send a verification request to the authorization platform, and upon receiving a verification result returned by the authorization platform, and the verification result indicating that the authorized user account matches the account verification information, setting an association relationship between the user identity information and the authorized user account in the association relationship information; the verification request includes the authorized user account and the account verification information; The startup operation of the target application and the user authorization process are independent of each other.

5. The method according to claim 4, characterized in that, In response to the login device being a terminal device with a management application installed, wherein the management application contains the launch entry point of the target application, the method further includes, before sending the first authentication request to the authentication management device: The authorization login interface is displayed, and the authorization login interface displays at least one platform control; In response to receiving a selection operation for a target platform control, the identifier of the authorized platform is determined; the target platform control is any one of the at least one platform control. The first authentication request is generated based on the identifier of the authorized platform.

6. An account login method, characterized in that, The method is executed by an authorized platform, and the method includes: The system receives a second authentication request from an authentication management device located between the login device of the target application and the authorization platform. The authentication management device stores the relationship between user identity information in a first account system and authorized user accounts in a second account system. The second authentication request is sent by the authentication management device based on the identifier of the authorization platform. The identifier of the authorization platform is carried in the first authentication request sent by the login device. The second authentication request includes the authorized user account stored in the authentication management device that corresponds to the user identity information in the first authentication request. The user identity information is the user identity information in the first account system. The authorization platform corresponds to the second account system. Generate authorization authentication information based on the authorized user account; The authorization and authentication information is sent to the authentication management device so that the authentication management device can pass the authorization and authentication information to the login device. The authorization and authentication information is used by the login device to log in to the target application. The method further includes: The system receives a verification request sent by the authentication management device, the verification request including an authorized user account and account verification information; based on the relationship between the authorized user account and the account verification information, it detects whether the authorized user account and the account verification information match, and returns a verification result to the authentication management device, the verification result indicating whether the authorized user account and the account verification information match; The startup operation of the target application and the user authorization process are independent of each other.

7. An account login device, characterized in that, The device is used in an authentication management device located between the login device and the authorization platform of the target application. The authentication management device stores the relationship between user identity information in a first account system and authorized user accounts in a second account system. The device includes: The first request receiving module is used to receive a first authentication request sent by the login device. The first authentication request includes the identifier of the authorization platform and the user's identity information. The authorization platform corresponds to the second account system. The account acquisition module is used to acquire the authorized user account corresponding to the user identity information stored in the authentication management device; The first request sending module is used to send a second authentication request to the authorization platform based on the identifier of the authorization platform, wherein the second authentication request contains the authorized user account; The first information receiving module is used to receive authorization authentication information sent by the authorization platform based on the authorized user account; The first information sending module is used to send the authorization and authentication information to the login device, wherein the authorization and authentication information is information used by the login device to log in to the target application; The account acquisition module is used for: Based on the user identity information, the association information stored in the authentication management device is queried to obtain the authorized user account; the association information includes the association relationship between the user identity information and the authorized user account; The device further includes: The third request receiving module is used to receive a first authorization request sent by the login device; the first authorization request includes the authorized user account, the account verification information of the authorized user account, and the user identity information; The third request sending module is used to send a verification request to the authorization platform, wherein the verification request includes the authorized user account and the account verification information; The association setting module is used to respond to receiving a verification result returned by the authorization platform, and the verification result indicates that the authorized user account matches the account verification information, and to set the association relationship between the user identity information and the authorized user account in the association relationship information; The startup operation of the target application and the user authorization process are independent of each other.

8. The apparatus according to claim 7, characterized in that, The user identity information includes at least one of the following: Facial information, fingerprint information, account password information, and verified user accounts; The account password information includes the authenticated user account and the verification password of the authenticated user account; the authenticated user account is a user account in the first account system.

9. The apparatus according to claim 7, characterized in that, The login device is a terminal device with a management application installed; the management application contains a startup entry for at least one application, and the target application is one of the at least one application; Alternatively, the login device is the application server of the management application; Alternatively, the login device is a terminal device with the target application installed.

10. An account login device, characterized in that, The device is used in a login device, and the device includes: The second request sending module is used to send a first authentication request to the authentication management device. The first authentication request includes the identifier of the authorization platform and user identity information. The authentication management device is located between the login device and the authorization platform. The authentication management device stores the relationship between the user identity information in the first account system and the authorized user accounts in the second account system. The authorization platform corresponds to the second account system. The second information receiving module is used to receive authorization authentication information sent by the authentication management device; the authorization authentication information is obtained by the authentication management device based on the first authentication request, which retrieves the authorized user account stored in the authentication management device corresponding to the user identity information, and sends a second authentication request to the authorization platform based on the identifier of the authorization platform, and then the authorization platform sends it to the authentication management device based on the authorized user account; the second authentication request includes the authorized user account; The program login module is used to log in to the target application based on the authorization and authentication information. The device further includes: The fourth request sending module is used to send a first authorization request to the authentication management device. The first authorization request includes the authorized user account, the account verification information of the authorized user account, and the user identity information. The first authorization request is used to trigger the authentication management device to send a verification request to the authorization platform. When the verification result returned by the authorization platform is received, and the verification result indicates that the authorized user account matches the account verification information, the module sets the association relationship between the user identity information and the authorized user account in the association relationship information. The verification request includes the authorized user account and the account verification information. The startup operation of the target application and the user authorization process are independent of each other.

11. The apparatus according to claim 10, characterized in that, The device further includes: The interface display module is used to display the authorization login interface, which displays at least one platform control. An identifier determination module is used to determine the identifier of the authorized platform in response to receiving a selection operation on a target platform control; the target platform control is any one of the at least one platform control; The request generation module is used to generate the first authentication request based on the identifier of the authorization platform.

12. An account login device, characterized in that, The device is used in an authorized platform, and the device includes: The second request receiving module is used to receive a second authentication request sent by the authentication management device; the authentication management device is located between the login device of the target application and the authorization platform, and the authentication management device stores the relationship between user identity information in the first account system and authorized user accounts in the second account system; the second authentication request is sent by the authentication management device based on the identifier of the authorization platform; the identifier of the authorization platform is carried by the first authentication request sent by the login device; the second authentication request includes the authorized user account stored in the authentication management device that corresponds to the user identity information in the first authentication request; the user identity information is the user identity information in the first account system; the authorization platform corresponds to the second account system; The information generation module is used to generate authorization authentication information based on the authorized user account; The second information sending module is used to send the authorization and authentication information to the authentication management device, so that the authentication management device can pass the authorization and authentication information to the login device. The authorization and authentication information is information used by the login device to log in to the target application. The device is also used for: The system receives a verification request sent by the authentication management device, the verification request including an authorized user account and account verification information; based on the relationship between the authorized user account and the account verification information, it detects whether the authorized user account and the account verification information match, and returns a verification result to the authentication management device, the verification result indicating whether the authorized user account and the account verification information match; The startup operation of the target application and the user authorization process are independent of each other.

13. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one computer program, which is loaded and executed by the processor to implement the account login method as described in any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one computer program, which is loaded and executed by a processor to implement the account login method as described in any one of claims 1 to 6.

15. A computer program product, characterized in that, The computer program product includes at least one computer program, which is loaded and executed by a processor to implement the account login method as described in any one of claims 1 to 6.

Images