An application login control method, device, electronic device, and storage medium

Abstract

An application login control method, apparatus, electronic device, and storage medium are disclosed to improve the efficiency of application login in a sandbox virtualization environment. The method includes: receiving a login request from a third-party application to log in to a target application, wherein the target application runs in the sandbox environment and the third-party application runs outside the sandbox environment; receiving first login state information associated with an authorization confirmation operation sent by the third-party application in response to the authorization confirmation operation; obtaining second login state information of the target object logging into the target application based on the first login state information; and sending the second login state information to the target application, causing the target application to set the target object to a logged-in state according to the second login state information. This application completes signature verification through a third-party application outside the sandbox environment, eliminating the need to install the third-party application in the sandbox, thus improving the efficiency of application login in the sandbox virtualization environment when using a third-party application.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an application login control method, apparatus, electronic device, and storage medium. Background Technology

[0002] In related technologies, before logging into a target application through a third-party application in a sandbox environment, it is necessary to clone the third-party application within the sandbox environment, that is, to install the third-party application within the sandbox environment. This ensures that the target application and the third-party application are in the same environment, so that the third-party application recognizes that the target application is already installed, thus completing the signature verification and enabling the target application to log in within the sandbox environment.

[0003] However, this method requires obtaining the third-party application's installation package and installing it in a sandbox environment when login activity is detected. This results in a lengthy installation wait time. Furthermore, after installing the third-party application in the sandbox, since the application is brand new and without data, the user needs to log in again, and the account logged into the third-party application installed on the system will be logged out, making the process overly cumbersome. Summary of the Invention

[0004] This application provides an application login control method, apparatus, electronic device, and storage medium to improve the efficiency of logging into applications in a sandbox virtualization environment.

[0005] The first application login control method provided in this application embodiment is applied to sandbox-hosted applications, including:

[0006] Receive a login request for a target application through a third-party application, wherein the target application runs in a sandbox environment and the third-party application runs outside the sandbox environment;

[0007] Receive first login status information sent by the third-party application in response to the authorization confirmation operation, wherein the first login status information is the login status information of the target object associated with the authorization confirmation operation logging into the third-party application;

[0008] Based on the first login status information, the second login status information of the target object logging into the target application is obtained;

[0009] The second login status information is sent to the target application, thereby enabling the target application to set the target object to a logged-in state based on the second login status information.

[0010] The second application login control method provided in this application embodiment is applied to a target application that runs in a sandbox environment, including:

[0011] Upon receiving a login request from a third-party application, a login request is sent to the sandbox host application, wherein the third-party application is running outside the sandbox environment;

[0012] The application receives the second login status information of the target object when it logs in, returned by the sandbox host application, and sets the target object to a logged-in state. The second login status information is obtained by the sandbox host application based on the first login status information of the target object when it logs in to the third-party application. The first login status information is obtained by the sandbox host application from the third-party application based on the login request. The target object is the target object associated with the authorization confirmation operation performed by the third-party application.

[0013] The first application login control device provided in this application embodiment is applied to a sandbox host application and includes:

[0014] The first receiving unit is used to receive a login request for logging into the target application through a third-party application, wherein the target application runs in a sandbox environment and the third-party application runs outside the sandbox environment;

[0015] The second receiving unit is used to receive the first login status information sent by the third-party application in response to the authorization confirmation operation. The first login status information is the login status information of the target object associated with the authorization confirmation operation logging into the third-party application.

[0016] The information acquisition unit is used to obtain, based on the first login status information, the second login status information of the target object logging into the target application;

[0017] The sending unit sends the second login status information to the target application, thereby enabling the target application to set the target object to a logged-in state based on the second login status information.

[0018] The second application login control device provided in this application embodiment is applied to a target application that runs in a sandbox environment, including:

[0019] The request unit is used to send a login request to the sandbox host application when a login request is received through a third-party application, wherein the third-party application runs outside the sandbox environment;

[0020] The login unit is used to receive the second login status information of the target object returned by the sandbox host application when the target object logs in, and set the target object to a login status. The second login status information is obtained by the sandbox host application based on the first login status information of the target object when logging into the third-party application. The first login status information is obtained by the sandbox host application from the third-party application based on the login request. The target object is the target object associated with the authorization confirmation operation performed by the third-party application.

[0021] Optionally, the request unit is specifically used for:

[0022] When the sandbox environment starts, a pre-configured monitoring module is invoked, so that when the monitoring module is invoked, the login request is generated and sent to the sandbox host application; or

[0023] Upon startup, the login request is generated in response to a trigger operation of the login control for login via the third-party application, so that the monitoring module intercepts the login request and sends it to the sandbox host application.

[0024] Optionally, the device further includes:

[0025] The second resource transfer unit is used to respond to the resource transfer operation triggered by the target object and send a resource transfer request to the sandbox host application so that the sandbox host application can perform resource transfer processing according to the resource transfer request after receiving the resource transfer request.

[0026] Receive the resource transfer results returned by the sandbox host application.

[0027] Optionally, the second resource transfer unit is specifically used for:

[0028] In response to the resource transfer operation triggered by the target object, a resource transfer request is obtained. The resource transfer mode indicator parameter in the resource transfer request is the request parameter corresponding to the third-party mode, which is determined based on the third-party application.

[0029] After modifying the request parameters corresponding to the third-party mode to the request parameters corresponding to the guest mode, the request is sent to the sandbox host application; and

[0030] The resource transfer result is obtained by the sandbox host application through resource transfer processing based on the resource transfer interface corresponding to the guest mode.

[0031] An electronic device provided in this application embodiment includes a processor and a memory, wherein the memory stores program code, and when the program code is executed by the processor, the processor performs the steps of any of the above-described application login control methods.

[0032] This application provides a computer program product or computer program that 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 steps of any of the above-described application login control methods.

[0033] This application provides a computer-readable storage medium including program code. When the program product is run on an electronic device, the program code is used to cause the electronic device to perform the steps of any of the above-described application login control methods.

[0034] The beneficial effects of this application are as follows:

[0035] This application provides an application login control method, apparatus, electronic device, and storage medium. Because this application expands the functionality of the sandbox host application, when a target application running in the sandbox environment determines that a target object is logging in through a third-party application, the login request is transferred to the sandbox host application for processing, thus enabling the target application to log in within the sandbox environment. Since the sandbox host obtains login status information from the third-party application located outside the sandbox environment (i.e., locally on the terminal device) upon receiving the login request, it does not need to download and install the third-party application within the sandbox environment, eliminating the need to wait for downloads. Furthermore, because no third-party application needs to be installed in the sandbox environment, there is no risk of kicking out accounts of third-party applications installed locally on the terminal device, effectively improving the efficiency of logging into the target application within the sandbox virtualization environment.

[0036] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0037] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0038] Figure 1This is an optional schematic diagram of an application scenario in an embodiment of this application;

[0039] Figure 2 This is a flowchart of the first application login control method in the embodiments of this application;

[0040] Figure 3 This is a schematic diagram of an authorization interface in an embodiment of this application;

[0041] Figure 4 This is a schematic diagram of a game interface in an embodiment of this application;

[0042] Figure 5 This is a flowchart illustrating a payment method in an embodiment of this application;

[0043] Figure 6 This is a schematic diagram of a payment interface in an embodiment of this application;

[0044] Figure 7 This is a flowchart of the second application login control method in the embodiments of this application;

[0045] Figure 8 This is a schematic diagram of an optional interactive implementation timing process in an embodiment of this application;

[0046] Figure 9 This is a schematic diagram of the composition structure of the first application login control method in this application embodiment;

[0047] Figure 10 This is a schematic diagram of the composition structure of the second application login control method in this application embodiment;

[0048] Figure 11 This is a schematic diagram of the composition structure of an electronic device using an embodiment of this application. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments of this application. Obviously, the described embodiments are only some embodiments of the technical solutions of this application, and not all embodiments. Based on the embodiments recorded in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the technical solutions of this application.

[0050] The following describes some of the concepts involved in the embodiments of this application.

[0051] A sandbox (also called a sandbox environment) is a virtual system program that allows users to run browsers or other programs within a sandbox environment, so that changes made during the run can be subsequently deleted. It creates a sandbox-like independent operating environment where programs running within it do not have a permanent impact on the hard drive. It is an independent virtual environment that can be used to test untrusted applications or online behavior. In this application embodiment, sandbox technology can be used to build an Android virtual machine within an APP (application) to run other APPs.

[0052] Sandbox Environment: The API (Application Programming Interface) capability open platform sandbox environment is an auxiliary environment provided to customers for developing interface functions and debugging key functions. The sandbox environment provides the main functions of the open platform. Customers can understand, combine, and debug various open interfaces in the sandbox environment according to their own needs, thus helping them to conduct online debugging and acceptance testing more quickly and smoothly.

[0053] Login State and Login State Conversion Interface: With the increasing prevalence of service-oriented architecture, directly maintaining sessions is becoming increasingly difficult. Therefore, a token (an object representing the right to perform certain operations) is generally used to represent a user's login state and identify the user's identity; this is the login state. In this embodiment, login state information can be represented by an OpenId (login state, a unique user identifier), which refers to a user's unique ID (identifier) ​​on application platforms such as social applications. Each user is assigned an OpenId upon entering an application, similar to an ID card number, used for unique identification. The login state conversion interface can be used to convert OpenIds between multiple applications. The OIDB service in this embodiment is a commonly used login state conversion interface provided by social applications, also known as an OpenId conversion interface.

[0054] Third-party applications: These are software developed for specific devices, such as mobile phones and cameras. While manufacturers typically develop their own software for these devices, many programming enthusiasts or organizations also create applications specifically for these devices; these are called third-party applications. Social applications are a common type of third-party application. "Social" refers to social interaction, and applications that achieve this through the internet are called social applications.

[0055] Resource transfer: refers to the transfer of resources from one place to another. In the embodiments of this application, it refers to the transfer of electronic resources from one platform or application to another when a target object requests resource transfer in a target application, such as when a target object purchases a game item and requests payment.

[0056] Resource transfer mode, third-party mode, and guest mode: Resource transfer mode refers to the mode in which resources are transferred when the target object triggers a resource transfer request in the target application, and it is related to the login state of the target object. In the embodiments of this application, resource transfer modes include third-party mode and guest mode. Third-party mode refers to the situation where the target object logs into the target application through a third-party application and triggers a resource transfer request in the target application. At this time, the target object is in a third-party login state, and the corresponding resource transfer mode is third-party mode. This means that when the target object logs into the target application through a third-party application, the target object makes payment as a third-party logged-in user. In this mode, the target object's login state also needs to be verified. Guest mode refers to the situation where the target object makes payment as a guest. In this mode, the target object's login state does not need to be verified.

[0057] Signature verification: This refers to the process when logging into a target application through a third-party account. In other words, when the target application logs in through authorization from a third-party application, the third-party application will reverse-verify whether the signature of the requesting application matches the signature registered on the platform by obtaining the signature of the applications already installed on the system.

[0058] SDK (Software Development Kit): Generally, these are collections of development tools used by software engineers to create application software for specific software packages, software frameworks, hardware platforms, operating systems, etc. Software development tools, broadly speaking, refer to a collection of related documents, examples, and tools that assist in developing a particular type of software. Generally, an SDK is the SDK used to develop applications for the Windows (Windows operating system) platform. It can be simply some files providing an application programming interface (API) for a programming language, but may also include complex hardware capable of communicating with an embedded system. Common tools include utilities for debugging and other purposes. SDKs also often include sample code, supporting technical annotations, or other supporting documentation to clarify ambiguities in basic reference materials. In this embodiment, an SDK can be pre-embedded in the target application to obtain login requests, receive login results, and establish communication with the sandbox host application. Specifically, pre-embedding the SDK in the target application can be achieved by adding a Maven dependency during the application's coding process and then calling a few lines of code.

[0059] Communication components: ContentProviders (CPs), running separately in the sandbox host application and the target application's SDK, are used to enable communication between the two (the sandbox host application and the SDK). The CP is the interface for sharing data between applications. Android's Content Provider mechanism supports storing and retrieving data across multiple applications, and ContentProvider provides a more unified data sharing interface. In the Android system, there is no single public memory area for multiple applications to share data storage.

[0060] Cloud technology refers to a hosting technology that unifies hardware, software, and network resources within a wide area network (WAN) or local area network (LAN) to achieve data computing, storage, processing, and sharing. Cloud technology is a collective term for network technologies, information technologies, integration technologies, management platform technologies, and application technologies applied to cloud computing business models. It can form resource pools, providing flexible and convenient on-demand access. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to backend systems for logical processing. Data at different levels will be processed separately, and various industry data will require robust system support, which can only be achieved through cloud computing.

[0061] This application primarily relates to cloud computing and cloud security within cloud technology. Cloud computing is a computing model that distributes computing tasks across a resource pool comprised of numerous computers, enabling various application systems to access computing power, storage space, and information services as needed. The network providing these resources is called the "cloud." From the user's perspective, resources in the "cloud" are infinitely scalable, readily available, and can be used on demand, expanded at any time, and paid for based on usage. Cloud security refers to the collective term for security software, hardware, users, organizations, and secure cloud platforms based on the cloud computing business model. Cloud security integrates emerging technologies and concepts such as parallel processing, grid computing, and unknown virus behavior detection. Through a network of numerous clients, it monitors abnormal software behavior on the network, obtains the latest information on Trojans and malware on the internet, sends it to the server for automatic analysis and processing, and then distributes solutions for viruses and Trojans to each client.

[0062] This application primarily relates to the research direction of cloud computing security within cloud security, mainly including how to ensure the security of the cloud itself and various applications on the cloud, including cloud computer system security, secure storage and isolation of user data, user access authentication, information transmission security, network attack protection, and compliance auditing. In this application's embodiments, when authorizing login to a target application through a third-party application, signature verification is required to ensure application security; this process involves the aforementioned user access authentication, etc.

[0063] The design concept of the embodiments of this application is briefly introduced below:

[0064] With the continuous development of science and technology, electronic technology has also developed rapidly, and the variety of electronic products has increased dramatically. People have enjoyed the various conveniences brought about by technological advancements. Now, people can enjoy a comfortable life through various types of mobile devices. For example, smartphones, tablets, and other mobile devices have become an important part of people's lives. Users can use smartphones, tablets, and other mobile devices to listen to music, play games, and so on, to alleviate the pressure brought about by the fast pace of modern life.

[0065] Typically, with the continuous development of mobile internet and the constant improvement of smart terminals, current terminal devices equipped with the Android system no longer only have communication functions. Various terminal applications can be installed on these devices to provide users with functionality, allowing them to perform various operations such as work, entertainment, and daily life. However, these applications need to be tested before going live or during online debugging.

[0066] A sandbox environment is a virtual environment that can be used to test applications. In related technologies, when logging into a target application through a third-party application in a sandbox environment, the third-party application is mainly cloned within the sandbox environment. This ensures that the target application and the third-party application are in the same environment, thereby completing signature verification.

[0067] However, in this approach, when the sandbox-hosted application detects login activity from the target application, it needs to first obtain and install the third-party application's installation package, resulting in a lengthy installation wait time. Furthermore, even if a third-party application is installed within the sandbox environment, it is entirely new and without data. When a user needs to log in or make a payment, they must log in again, and the third-party application account installed in the system will be logged out, which is overly cumbersome.

[0068] Considering that the above methods would severely impact user experience, this application proposes an application login control method, apparatus, electronic device, and storage medium. Because this application expands the functionality of the sandbox host application, when a target application running in the sandbox environment determines that a target object is logging in through a third-party application, it transfers the login request to the sandbox host application for processing, thus enabling the target application to log in within the sandbox environment. Since the sandbox host obtains login status information from the third-party application located outside the sandbox environment (i.e., locally on the terminal device) upon receiving the login request, it does not need to download and install the third-party application within the sandbox environment, thus eliminating the need to wait for downloads. Furthermore, since no third-party application needs to be installed in the sandbox environment, there is no risk of kicking out accounts of third-party applications installed locally on the terminal device, effectively improving the efficiency of logging into the target application within the sandbox environment.

[0069] The preferred embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application. Furthermore, the embodiments and features in the embodiments of this application can be combined with each other without conflict.

[0070] like Figure 1 The diagram shown illustrates an application scenario according to an embodiment of this application. The application scenario includes two terminal devices 110 and one server 130. Users can log in to the application-related interface 120 via the terminal devices 110. The terminal devices 110 and the server 130 can communicate via a communication network.

[0071] In one alternative implementation, the communication network is either a wired network or a wireless network. The terminal device 110 and the server 130 can be directly or indirectly connected via wired or wireless communication, and this application does not impose any limitations on this.

[0072] In this embodiment, the terminal device 110 is an electronic device used by a user. This electronic device can be a personal computer, mobile phone, tablet computer, laptop, e-book reader, smart home device, or other computer device with a certain computing power that runs instant messaging software and websites or social networking software and websites. Each terminal device 110 connects to the server 130 via a wireless network. The server 130 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server 130 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.

[0073] Each terminal device may have third-party applications, sandbox host applications, etc. installed. The applications involved in this application embodiment may be software, web pages, mini programs, etc., and the server is the application server corresponding to the software, web pages, mini programs, etc., without limiting the specific type of client.

[0074] In this embodiment of the application, a third-party application refers to an application that runs outside the sandbox environment. That is, both the third-party application and the sandbox host application are installed on the terminal device 110, while the target application runs within the sandbox environment and is an APP that runs within the sandbox host application.

[0075] See Figure 2 The diagram shown is an implementation flowchart of an application login control method provided in this application embodiment. The specific implementation flow of this method applied to a sandbox host application is as follows:

[0076] Step S21: Receive a login request from a third-party application to log in to the target application. The target application runs in a sandbox environment, while the third-party application runs outside the sandbox environment.

[0077] In this context, a third-party application refers to an application that can be authorized to log in to the target application. Some common target applications support login using third-party accounts. When a user logs in using a third-party account, the application corresponding to that account is the third-party application. For example, a third-party application could be a social application, and a user could log in to a game app, video app, etc., using their social application account. Furthermore, it should be noted that the third-party application in this embodiment runs outside the sandbox environment, meaning it runs on the local system of the terminal device; while the target application is an application running in the sandbox environment, such as a game app or video app.

[0078] In this embodiment, the sandbox host application is used to provide a sandbox environment. Therefore, a virtual runtime environment can be provided based on the sandbox host application, in which other apps can run. Programs running inside the sandbox do not have a permanent impact on the hard drive and can be used to test the target application. Of course, third-party applications can also run in the sandbox environment, as listed in related technologies. However, logging into the target application through a third-party application running in the sandbox environment requires installing the third-party application within the sandbox environment, reducing the login efficiency of the target application. In this embodiment, the third-party application authorized to log into the target application refers to one running outside the sandbox environment, requiring no installation within the sandbox environment. Therefore, logging into the target application in the sandbox environment saves the waiting time for installation.

[0079] For example, if a third-party application X1 and a sandbox host application X2 are installed on a terminal device, when a user needs to log in to the target application X3 through the third-party application X1 in the sandbox host application X2, the target application X3 sends a login request to the sandbox host application X2, which then processes the request. This eliminates the need to install the third-party application X1 in the sandbox environment and eliminates the need to wait, thus improving the login efficiency of the target application X2.

[0080] Upon receiving a login request, the sandbox host application can forward the request to a third-party application, enabling the third-party application to display an authorization interface and obtain login status information. See steps S22 to S24 for details.

[0081] Step S22: Receive the first login status information sent by the third-party application in response to the authorization confirmation operation. The first login status information is the login status information of the target object associated with the authorization confirmation operation logging into the third-party application.

[0082] For example, when a user discovers a game they like in the sandbox and clicks "Play Now" to start playing, the sandbox host application will first initiate a login process to obtain the OpenId of the third-party application the user logged into, i.e., the initial login state information. The detailed process of the sandbox host application initiating the login is as follows:

[0083] The sandbox host application forwards the login request to the third-party application. Upon receiving the login request, the third-party application displays an authorization interface. The target user can select a third-party account on the authorization interface through clicks or other actions, triggering an authorization confirmation operation. The third-party application then sends the third-party account selected by the target user through the authorization confirmation operation to the sandbox host application as its initial login state information.

[0084] See Figure 3 As shown, where Figure 3 The left-hand interface S31 is the user interface for the target application within the sandbox environment. When the user clicks "Play Now," the sandbox host application will launch the login process and display the interface. Figure 3 The authorization interface shown on the right side of interface S32 is an authorization interface for a third-party application as listed in the embodiments of this application. This authorization interface displays at least one third-party account information of the user and includes a confirmation button. Figure 3 As we know, the third-party application is application A, and the nickname of the third-party account currently selected by the user is "Bingbingbang," with the avatar shown in the image. When the user triggers the authorization confirmation operation through the "Authorize Login with Application A" confirmation button, the third-party application sends the third-party account information corresponding to the user's authorization confirmation operation, namely the account information of the "Bingbingbang" account, as the user's login state information when logging into the third-party application, to the sandbox host application. Here, "Bingbingbang" is the target object associated with the authorization confirmation operation.

[0085] Step S23: Based on the first login state information, obtain the second login state information of the target object logging into the target application;

[0086] Step S24: Send the second login state information to the target application, so that the target application sets the target object to the login state based on the second login state information.

[0087] In this embodiment, after the sandbox host application obtains the first login state information, it can obtain the second login state information by conversion or unique ID binding, and return the second login state information to the target application. The target application then executes the corresponding logic to set the target object to a login state. The second login state information is the login state information of the target object when logging into the target application.

[0088] Let's take a game app running in a sandbox environment as an example. Figure 4 As shown, for example, if a user selects the account "Bingbingbang" and clicks "App A Authorization Login," after successfully authorizing login through the third-party application account, the third-party application will send the corresponding first login state information to the sandbox host application. Upon receiving the first login state information, the sandbox host application can convert or generate the game app's login state information based on it and return it to the game app, completing the game login, entering the game, and displaying the following... Figure 4 The interface S40 shown on the right is the game interface after entering the game.

[0089] Because this application extends the functionality of the sandbox host application, when a target application running in the sandbox environment determines that a target object is logging in through a third-party application, it transfers the login request to the sandbox host application for processing, thus enabling the target application to log in within the sandbox environment. Since the sandbox host obtains login status information from the third-party application located outside the sandbox environment (i.e., locally on the terminal device) upon receiving the login request, it does not need to download and install the third-party application within the sandbox environment, eliminating the need to wait for downloads. Furthermore, because no third-party application needs to be installed in the sandbox environment, there is no risk of kicking out accounts of third-party applications installed locally on the terminal device outside the sandbox, effectively improving the efficiency of logging into the target application within the sandbox environment. Moreover, this application provides a seamless user experience, so much so that users are unaware of the difference, achieving the same experience as local operation.

[0090] Optionally, in order to monitor login requests and ensure that the target application sends login requests to the sandbox host application, a monitoring module can be pre-installed in the target application in this embodiment of the application. When the target object determines that it is logging into the target application through a third-party application, the monitoring module sends a login request to the sandbox host application.

[0091] In this embodiment, the monitoring module can be implemented based on an SDK pre-embedded in the target application, and the sandbox host application has a communication component that communicates with the SDK. Therefore, in this embodiment, when the monitoring module sends a login request to the sandbox host application, it does so in the following two ways:

[0092] Method 1: Login is initiated automatically by the SDK. This method is suitable for applications that require strong login, i.e., target applications that require login to run.

[0093] Specifically, when the target application starts in the sandbox environment, it calls a pre-built monitoring module so that when the monitoring module is called, it generates a login request and sends the login request to the sandbox host application through a communication component.

[0094] Taking a game app running in a sandbox environment as an example, since the game app will call the SDK's login interface after integrating the SDK, the login interface can be actively called directly when the game app process starts, automatically initiate login, generate a login request, and send the login request to the sandbox host application through the communication component.

[0095] In this embodiment of the application, the SDK requests the sandbox host application to initiate login through the communication component in the sandbox host application in order to obtain the first login status information of the target object logging into the third-party application, and actively initiates login behavior after entering the game APP to achieve login.

[0096] Method 2: The SDK can intercept login requests. This method is suitable for target applications that can run without requiring login.

[0097] After the target application starts, it responds to the target object's triggered operation for the login control of the third-party application, generates a login request, so that the monitoring module can intercept the login request and send the intercepted login request to the sandbox host application through the communication component.

[0098] For target applications that do not require strong login, in this embodiment of the application, the target application can be started first. After entering the target application, when the user performs a trigger operation for the login control of a third-party application, such as when the user clicks to authorize login for application A, a login request is generated. The SDK then intercepts the login request, launches the sandbox host application to log in, and then the sandbox host application returns the second login state information (referring to the login result) to the SDK accessed by the target application through the communication component. The SDK then returns the second login state information as a response to the login request to the target application.

[0099] In the above implementation, the SDK can obtain login requests and receive login status information, and then enter the login process, so that the target application can be logged in without installing third-party applications in the sandbox, thus improving the efficiency of application login.

[0100] It should be noted that, in this embodiment of the application, the communication between the monitoring module of the target application and the sandbox host application is implemented based on a communication component. The communication component can be a ContentProvider running in the sandbox host application and the target application SDK respectively, used to realize the mutual communication between the sandbox host application and the SDK.

[0101] In one optional implementation, when a sandbox-hosted application obtains the target application's second login state information based on the third-party application's first login state information, it can be done in the following two ways:

[0102] Method 1: By calling the login state conversion interface of the third-party application, the first login state information of the third-party application is converted into the second login state information of the target application.

[0103] Taking the login state conversion interface as the OIDB service in third-party application A1 as an example, in the login process of third-party application A1, after the sandbox host successfully logs in, it can obtain the second login state information through conversion. Specifically, the sandbox host application calls the OIDB service in third-party application A1 to convert the first login state information of the target object logging into third-party application A1 into the second login state information of the target object logging into the game APP.

[0104] For some third-party applications that do not have the permission to convert OpenId, the login state conversion interface of Method 1 cannot be used to obtain the second login state information. In this case, Method 2, as listed below, can be used to generate the second login state information.

[0105] Method 2: Based on the first login state information of the third-party application, generate a new OpenId account by binding a unique identifier, and use this OpenId account as the second login state information of the target application.

[0106] The unique identifier can be a unique ID for the terminal device. For example, if the terminal device is a mobile phone, the unique identifier is the mobile phone's unique ID. After successfully logging into the sandbox host, the login status information of the game app can be obtained through the unique ID binding method.

[0107] For example, when logging in through a third-party application A2, the sandbox host application generates a new OpenId account based on the first login state information obtained from the target object's login to the third-party application A2. This new OpenId account serves as the target object's second login state information for the target application. The login record is also saved using the phone's unique ID. If the target application is subsequently installed on the terminal device's local system, the newly generated OpenId account can be retrieved using the phone's unique ID.

[0108] In the above implementation, the sandbox host application can obtain the second login state information of the target application by conversion or unique ID binding, and return it to the target application. The login process is mainly handled by the sandbox host application to realize the function of logging into the target application in the sandbox environment.

[0109] In an optional implementation, after describing the method of logging into the target application through a third-party application, this application embodiment also provides a method for transferring resources through a third-party application using a sandbox host application. When using a sandbox host application to transfer resources, the sandbox host application also possesses related resource transfer functions, such as QR code payment.

[0110] In a sandbox host application, the module that completes the payment function can be called a resource transfer component (also referred to as a payment component below). For the target application side, after the payment-related request is transferred to the sandbox host application, the resource transfer component and the third-party application interact to complete the resource transfer process and obtain the resource transfer result.

[0111] Furthermore, in this embodiment, the monitoring module pre-installed in the target application can also monitor resource transfer requests (hereinafter also referred to as payment requests). See also Figure 5 As shown, the specific operations on the target application side include the following steps:

[0112] Step S51: The target application responds to the resource transfer operation triggered by the target object, initiates a resource transfer request, and the monitoring module intercepts the resource transfer request initiated by the target application;

[0113] Step S52: The target application calls the monitoring module to modify the target request parameter in the resource transfer request to the request parameter corresponding to the guest mode, and then the monitoring module sends the modified resource transfer request to the sandbox host application through the communication component;

[0114] When a sandbox host application receives a resource transfer request, it forwards the request to the resource transfer component. The resource transfer component then interacts with the third-party application based on the resource transfer interface corresponding to the guest mode to complete the resource transfer process. Finally, it sends the resource transfer result to the monitoring module of the target application through the communication component.

[0115] Step S53: The target application receives the resource transfer result through the monitoring module.

[0116] Taking resource transfer as an example of payment, the resource transfer component in a sandbox host application includes a payment component. (See also...) Figure 6 As shown, where Figure 6 The left-hand interface S61 shown is a schematic diagram of a game store interface in a game app provided in this application embodiment. Interface S61 displays three game items: "Money Cow," "Task Mule," and "Resurrection Raven," along with information such as the function and price of each item. For example, the Money Cow's function is to grant double coins each time a door is opened, priced at 6 electronic resources; the Task Mule's function is to instantly refresh tasks without waiting, priced at 8 electronic resources; and the Resurrection Raven's function is to provide one free resurrection per week, priced at 15 electronic resources.

[0117] For example, when a user clicks the payment control for "6 electronic resources," triggering a resource transfer operation (i.e., when a payment operation is triggered), the following will be displayed: Figure 6 The interface S62 shown is a payment interface provided in this embodiment of the application. Interface S62 displays four payment methods: Method A, Method B, Method C, and Method D. Users can select a payment method on this interface, with different payment methods corresponding to different third-party applications. Therefore, when a user selects a different payment method, the payment component of the sandbox host application will call the corresponding third-party application to recharge the target application and complete the payment.

[0118] For example, if you choose to pay with application A, then the sandbox host application will use application A to recharge the target application. When recharging, electronic resources in the balance of application A or electronic resources in the payment card bound to application A can be used to recharge the game app and complete the payment.

[0119] It should be noted that the third-party applications involved in the login and payment processes in this application embodiment can be different. For example, applications A, B, C, D, and E are all third-party applications outside the sandbox environment. When logging into the game app within the sandbox environment, login can be authorized through application A. When making payments within the sandbox environment, payments can also be made through third-party applications, i.e., third-party payment. Furthermore, if applications B, C, D, and E also have payment functions, payments can be made through any of these applications; it is not necessary to use application A, the same application used to log into the game app, for payment.

[0120] In this embodiment, the guest payment interface of the sandbox host application's payment component supports recharging any app. Therefore, when the target application initiates a third-party payment request, the SDK intercepts the payment request and modifies the resource transfer mode indicator parameters `sessionid` (session identifier) ​​and `sessionType` (session type) in the payment request from third-party mode to guest mode. The third-party mode is related to the third-party application used for authorized login to the target application. For example, when authorized login is through application A, the third-party mode is represented as the payment mode in application A's login state; when authorized login is through application B, the third-party mode is represented as the payment mode in application B's login state. Payments in third-party mode require verification of the login state, while guest payment does not. Therefore, the resource transfer mode indicator parameters in the payment request can be modified to the request parameters corresponding to guest mode through the above process.

[0121] Afterwards, the target application can delegate payment to the sandbox host application via the SDK. Specifically, the sandbox host application tops up the target application's account through the guest payment interface of the payment component, completing the payment. Since the sandbox host application's payment component uses the target application's offerId as the unified receipt ID, the payment will be received regardless of the user's payment method. Here, offerId refers to the target application's ID under the payment platform.

[0122] In this embodiment, the guest payment interface of the payment component of the sandbox host application supports recharging any APP. When the target application initiates a payment, it will entrust the sandbox host application to make the payment. The sandbox host application recharges the application through the guest payment of the payment component and completes the payment.

[0123] In the above embodiments, the payment process can be implemented without installing or logging into third-party applications in the sandbox environment. The payment process can be achieved through the payment component of the sandbox host, improving the efficiency of payment applications in the sandbox environment. Furthermore, the guest payment function of the payment component in this embodiment supports topping up any app, using offerId as the unified receipt ID. Therefore, regardless of the third-party payment method used, the payment can be received, realizing the payment process of the target application in the sandbox environment.

[0124] See Figure 7 The diagram shown is an implementation flowchart of an application login control method provided in this application embodiment. The method is applied to the target application side, which runs in a sandbox environment. The specific implementation flow of this method is as follows:

[0125] S71: When a login request is received from a third-party application, a login request is sent to the sandbox host application, where the third-party application is running outside the sandbox environment;

[0126] S72: Receive the second login state information of the target object when it logs in, returned by the sandbox host application, and set the target object to the login state. The second login state information is obtained by the sandbox host application based on the first login state information of the target object when it logs in to the third-party application. The first login state information is obtained by the sandbox host application from the third-party application based on the login request. The target object is the target object associated with the authorization confirmation operation performed by the third-party application.

[0127] Optionally, upon receiving a login request from a third-party application, a login request is sent to the sandbox host application, specifically including:

[0128] When starting up in the sandbox environment, a pre-built monitoring module is invoked, so that when the monitoring module is invoked, a login request is generated and sent to the sandbox host application; or

[0129] Upon startup, a login request is generated in response to a login control triggered by a third-party application, so that the monitoring module can intercept the login request and send it to the sandbox host application.

[0130] Optionally, the method also includes:

[0131] In response to the resource transfer operation triggered by the target object, a resource transfer request is sent to the sandbox host application so that the sandbox host application can perform resource transfer processing according to the resource transfer request after receiving it.

[0132] Receive resource transfer results returned by the sandbox host application.

[0133] Optionally, in response to a resource transfer operation triggered by the target object, a resource transfer request is sent to the sandbox host application, specifically including:

[0134] Responding to the resource transfer operation triggered by the target object, a resource transfer request is obtained. The resource transfer mode indicator parameter in the resource transfer request is the request parameter corresponding to the third-party mode, which is determined based on the third-party application.

[0135] After modifying the request parameters corresponding to the third-party mode to those corresponding to the guest mode, send them to the sandbox host application; and

[0136] The resource transfer result is obtained by the sandbox host application through resource transfer processing based on the resource transfer interface corresponding to the guest mode.

[0137] See Figure 8 The diagram shown is an optional interaction sequence diagram. The specific implementation flow of this method is as follows:

[0138] Step S801: When the target object determines that it is logging into the target application through a third-party application, the target application sends a login request to the sandbox host application;

[0139] Step S802: The sandbox host application forwards the login request to the third-party application;

[0140] Step S803: The third-party application displays the authorization interface;

[0141] Step S804: The third-party application responds to the authorization confirmation operation of the target object through the authorization interface and sends the first login status information of the target object to the sandbox host application.

[0142] Step S805: The sandbox host application obtains the second login state information of the target object based on the first login state information.

[0143] Step S806: The sandbox host application sends the second login state information to the target application;

[0144] Step S807: The target application sets the target object to a logged-in state based on the second login state information.

[0145] Since an SDK is provided in this application embodiment, the target application only needs to simply integrate the SDK to complete the login and payment process of the target application, transfer the request to the sandbox host application for processing, and delegate the sandbox host application to cleverly pass the signature verification of the third-party application, so as to realize the third-party login and third-party payment functions of the target application in the sandbox environment, thereby improving the efficiency of application login and payment.

[0146] like Figure 9 As shown, this is a structural schematic diagram of the first type of application control device 900 in this application embodiment, applied to a sandbox host application, and may include:

[0147] The first receiving unit 901 is used to receive a login request for logging into the target application through a third-party application. The target application runs in a sandbox environment, while the third-party application runs outside the sandbox environment.

[0148] The second receiving unit 902 is used to receive the first login status information sent by the third-party application in response to the authorization confirmation operation. The first login status information is the login status information of the target object associated with the authorization confirmation operation logging into the third-party application.

[0149] The information acquisition unit 903 is used to obtain the second login status information of the target object logging into the target application based on the first login status information;

[0150] The sending unit 904 sends the second login status information to the target application, thereby enabling the target application to set the target object to a login status based on the second login status information.

[0151] Optionally, the device also includes:

[0152] The third receiving unit 905 is used to receive a resource transfer request sent by the target application, wherein the resource transfer request is sent by the target application after responding to the resource transfer operation triggered by the target object;

[0153] The first resource transfer unit 906 is used to obtain the resource transfer result according to the resource transfer request and return the resource transfer result to the target application.

[0154] Optionally, the resource transfer request includes a resource transfer mode indication parameter that corresponds to the guest mode request. The resource transfer request is sent by the target application after modifying the resource transfer mode indication parameter in the resource transfer request triggered by the target object from the third-party mode to the guest mode. The third-party mode is determined based on the third-party application.

[0155] The first resource transfer unit 906 is specifically used for:

[0156] When a resource transfer result is obtained based on a resource transfer request, the resource transfer result is obtained based on the resource transfer interface corresponding to the guest mode, and the resource transfer result is returned to the target application.

[0157] Optionally, the information acquisition unit 903 is specifically used for:

[0158] By calling the login state conversion interface of the third-party application, the first login state information of the third-party application is converted into the second login state information of the target application; or

[0159] Based on the first login state information of the third-party application, an OpenId account is generated through a unique identifier binding method, and the OpenId account is used as the second login state information of the target application.

[0160] like Figure 10 As shown, this is a schematic diagram of the structure of the second type of application control device 1000 in this application embodiment, applied to a target application running in a sandbox environment, and may include:

[0161] The request unit 1001 is used to send a login request to the sandbox host application when a login request is received through a third-party application, wherein the third-party application is running outside the sandbox environment;

[0162] The login unit 1002 is used to receive the second login state information of the target object when it logs in, returned by the sandbox host application, and set the target object to the login state. The second login state information is obtained by the sandbox host application based on the first login state information of the target object when it logs in to the third-party application. The first login state information is obtained by the sandbox host application from the third-party application based on the login request. The target object is the target object associated with the authorization confirmation operation performed by the third-party application.

[0163] Optionally, request unit 1001 is specifically used for:

[0164] When starting up in the sandbox environment, a pre-built monitoring module is invoked, so that when the monitoring module is invoked, a login request is generated and sent to the sandbox host application; or

[0165] Upon startup, a login request is generated in response to a login control triggered by a third-party application, so that the monitoring module can intercept the login request and send it to the sandbox host application.

[0166] Optionally, the device also includes:

[0167] The second resource transfer unit 1003 is used to respond to the resource transfer operation triggered by the target object and send the resource transfer request to the sandbox host application so that the sandbox host application can perform resource transfer processing according to the resource transfer request after receiving the resource transfer request.

[0168] Receive resource transfer results returned by the sandbox host application.

[0169] Optionally, the second resource transfer unit 1003 is specifically used for:

[0170] Responding to the resource transfer operation triggered by the target object, a resource transfer request is obtained. The resource transfer mode indicator parameter in the resource transfer request is the request parameter corresponding to the third-party mode, which is determined based on the third-party application.

[0171] After modifying the request parameters corresponding to the third-party mode to those corresponding to the guest mode, send them to the sandbox host application; and

[0172] The resource transfer result is obtained by the sandbox host application through resource transfer processing based on the resource transfer interface corresponding to the guest mode.

[0173] For ease of description, the above sections are divided into modules (or units) according to their functions and described separately. Of course, in implementing this application, the functions of each module (or unit) can be implemented in one or more software or hardware components.

[0174] Having introduced the application login control method and apparatus according to exemplary embodiments of this application, we will now introduce an electronic device according to another exemplary embodiment of this application.

[0175] Those skilled in the art will understand that various aspects of this application can be implemented as a system, method, or program product. Therefore, various aspects of this application can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, collectively referred to herein as a "circuit," "module," or "system."

[0176] Figure 11 This is a block diagram illustrating an electronic device 1100 according to an exemplary embodiment, the device comprising:

[0177] Processor 1110;

[0178] Memory 1120 is used to store executable instructions of processor 1110;

[0179] The processor 1110 is configured to execute instructions to implement the application login control method in this embodiment.

[0180] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 1120 including instructions, which can be executed by a processor 1110 of an electronic device 1100 to perform the above-described method. Optionally, the storage medium may be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device.

[0181] In some possible implementations, embodiments of this application provide a computer program product or computer program that 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 steps of any of the above-described application login control methods.

[0182] In some possible implementations, various aspects of the application login control method provided in this application can also be implemented as a program product, which includes program code. When the program product is run on a computer device, the program code is used to cause the computer device to perform the steps of the application login control method according to the various exemplary embodiments of this application described above. For example, the computer device can perform actions such as... Figure 2 or Figure 7 The steps are shown in the figure.

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

[0184] The program product of the embodiments of this application may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a computing device. However, the program product of this application is not limited thereto. In this document, the readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with a command execution system, apparatus, or device.

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

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

[0187] Furthermore, those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application can take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code.

[0188] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0189] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0190] The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. The terminal and server can be connected directly or indirectly through wired or wireless communication methods, which is not limited herein.

[0191] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0192] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A login control method, characterized in that, For sandbox-hosted applications, this method includes: Receive a login request for a target application through a third-party application, wherein the target application runs in a sandbox environment and the third-party application runs outside the sandbox environment; Receive first login status information sent by the third-party application in response to the authorization confirmation operation, wherein the first login status information is the login status information of the target object associated with the authorization confirmation operation logging into the third-party application; Based on the first login status information, the second login status information of the target object logging into the target application is obtained; The second login status information is sent to the target application, so that the target application sets the target object to a logged-in state based on the second login status information; The system receives a resource transfer request sent by the target application. The resource transfer request includes a resource transfer mode indication parameter that corresponds to the guest mode. The resource transfer request is sent by the target application after modifying the resource transfer mode indication parameter in the resource transfer request triggered by the target object from the third-party mode to the guest mode. The third-party mode is determined based on the third-party application. The resource transfer is performed according to the resource transfer interface corresponding to the guest mode, the resource transfer result is obtained, and the resource transfer result is returned to the target application.

2. The method as described in claim 1, characterized in that, The step of obtaining the second login status information of the target object logging into the target application based on the first login status information specifically includes: By calling the login state conversion interface of the third-party application, the first login state information of the third-party application is converted into the second login state information of the target application; or Based on the first login state information of the third-party application, a login state OpenId account is generated by binding a unique identifier, and the OpenId account is used as the second login state information of the target application.

3. An application login control method, characterized in that, Applied to a target application running in a sandbox environment, the method includes: upon receiving a login request from a third-party application, sending a login request to the sandbox host application, wherein the third-party application runs outside the sandbox environment; The application receives the second login status information of the target object when it logs in, returned by the sandbox host application, and sets the target object to a logged-in state. The second login status information is obtained by the sandbox host application based on the first login status information of the target object when it logs in to the third-party application. The first login status information is obtained by the sandbox host application from the third-party application based on the login request. The target object is the target object associated with the authorization confirmation operation performed on the third-party application. In response to the resource transfer operation triggered by the target object, a resource transfer request is obtained. The resource transfer mode indicator parameter in the resource transfer request is the request parameter corresponding to the third-party mode, which is determined based on the third-party application. After modifying the request parameters corresponding to the third-party mode to the request parameters corresponding to the guest mode, send them to the sandbox host application. Receive the resource transfer result returned by the sandbox host application; the resource transfer result is obtained by the sandbox host application through resource transfer processing according to the resource transfer interface corresponding to the guest mode.

4. The method as described in claim 3, characterized in that, The step of sending a login request to the sandbox host application upon receiving a login request from a third-party application specifically includes: When the sandbox environment starts, a pre-configured monitoring module is invoked, so that when the monitoring module is invoked, the login request is generated and sent to the sandbox host application; or Upon startup, the login request is generated in response to a trigger operation of the login control for login via the third-party application, so that the monitoring module intercepts the login request and sends it to the sandbox host application.

5. An application login control device, characterized in that, Applied to sandbox-hosted applications, including: The first receiving unit is used to receive a login request for logging into the target application through a third-party application, wherein the target application runs in a sandbox environment and the third-party application runs outside the sandbox environment; The second receiving unit is used to receive the first login status information sent by the third-party application in response to the authorization confirmation operation. The first login status information is the login status information of the target object associated with the authorization confirmation operation logging into the third-party application. The information acquisition unit is used to obtain, based on the first login status information, the second login status information of the target object logging into the target application; The sending unit sends the second login status information to the target application, thereby enabling the target application to set the target object to a logged-in state based on the second login status information; The third receiving unit is used to receive a resource transfer request sent by the target application. The resource transfer request includes a resource transfer mode indication parameter that is the request parameter corresponding to the guest mode. The resource transfer request is sent by the target application after modifying the resource transfer mode indication parameter in the resource transfer request triggered by the target object from the third-party mode to the guest mode. The third-party mode is determined based on the third-party application. The first resource transfer unit is used to perform resource transfer processing according to the resource transfer interface corresponding to the guest mode, obtain the resource transfer result, and return the resource transfer result to the target application.

6. The apparatus as claimed in claim 5, characterized in that, The information acquisition unit is specifically used for: By calling the login state conversion interface of the third-party application, the first login state information of the third-party application is converted into the second login state information of the target application; or Based on the first login state information of the third-party application, an OpenId account is generated through a unique identifier binding method, and the OpenId account is used as the second login state information of the target application.

7. An application login control device, characterized in that, Applied to a target application that runs in a sandbox environment, including: The request unit is used to send a login request to the sandbox host application when a login request is received through a third-party application, wherein the third-party application runs outside the sandbox environment; The login unit is used to receive the second login status information of the target object returned by the sandbox host application when the target object logs in, and set the target object to a login status. The second login status information is obtained by the sandbox host application based on the first login status information of the target object when logging into the third-party application. The first login status information is obtained by the sandbox host application from the third-party application based on the login request. The target object is the target object associated with the authorization confirmation operation performed on the third-party application. The second resource transfer unit is used to respond to the resource transfer operation triggered by the target object, obtain a resource transfer request, wherein the resource transfer mode indicator parameter in the resource transfer request is the request parameter corresponding to the third-party mode, and the third-party mode is determined based on the third-party application; modify the request parameter corresponding to the third-party mode to the request parameter corresponding to the guest mode and send it to the sandbox host application; receive the resource transfer result returned by the sandbox host application; the resource transfer result is obtained by the sandbox host application through resource transfer processing according to the resource transfer interface corresponding to the guest mode.

8. The apparatus as claimed in claim 7, characterized in that, The request unit is specifically used for: When the sandbox environment starts, a pre-configured monitoring module is invoked so that when the monitoring module is invoked, the login request is generated and sent to the sandbox host application. or Upon startup, the login request is generated in response to a trigger operation of the login control for login via the third-party application, so that the monitoring module intercepts the login request and sends it to the sandbox host application.

9. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory stores program code that, when executed by the processor, causes the processor to perform the steps of any of the methods of claims 1-2 or any of the methods of claims 3-4.

10. A computer-readable storage medium, characterized in that, It includes program code that, when the program product is run on an electronic device, causes the electronic device to perform the steps of any of the methods described in claims 1-2 or any of the methods described in claims 3-4.

11. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium; when the processor of the electronic device reads the computer instructions from the computer-readable storage medium, the processor executes the computer instructions, causing the electronic device to perform the steps of any of the methods of claims 1-2 or any of the methods of claims 3-4.

Images