Apparatus and method for logging into an application

Abstract

An apparatus for logging into a target application is provided. The apparatus includes a first device. The first device communicates with a second device. The first device is configured to: receive an instruction to decode authentication input for logging into the target application, and receive a confirmation login instruction from the second device; and log into the target application on the first device. The second device is configured to: launch the target application; decode the authentication input; and send a confirmation login instruction to the first device.

Description

Technical Field

[0001] This invention relates to display technology, and more particularly to an apparatus and a method for logging into an application. Background Technology

[0002] In recent years, virtual reality (VR) and mixed reality (MR) technologies have experienced rapid development with their application in various industries, including entertainment, education, and professional fields. As these technologies have evolved, users are increasingly interacting with virtual environments and applications through head-mounted displays (HMDs) and other immersive devices. These devices provide users with highly interactive and immersive experiences by displaying virtual content directly in their field of vision. Summary of the Invention

[0003] On one hand, this disclosure provides an apparatus for logging into an application, including a first device; wherein the first device communicates with a second device; the first device is configured to receive an instruction for decoding authentication input for logging into the target application;

[0004] Wherein, after the first device receives the instruction to decode the authentication input for logging into the target application:

[0005] The first device is further configured to obtain data containing the authentication input and send the data containing the authentication input to the second device; and the second device is further configured to identify the target application linked to the authentication input;

[0006] or,

[0007] The first device is further configured to: send the instruction to the second device to decode the authentication input for logging into the target application; and display the interface of the second device when the second device receives the instruction to decode the authentication input for logging into the target application;

[0008] Wherein, after the second device identifies the target application linked to the authentication input, or after the first device displays the interface of the second device: the second device is configured to: launch the target application; decode the authentication input; and send a confirmation login instruction to the first device; and the first device is configured to receive the confirmation login instruction from the second device and log in to the target application on the first device.

[0009] Optionally, the first device is configured to receive an instruction to scan a QR code for logging into the target application.

[0010] Optionally, the first device is configured to receive instructions to detect and display a URL or an interface of an application that requires scanning a QR code to log in.

[0011] Optionally, the first device is further configured to capture an image containing a QR code, send the image containing the QR code to the second device; and the second device is configured to identify the target application linked to the QR code, launch the target application, decode the QR code, and send a login confirmation command to the first device.

[0012] Optionally, the first device is configured to send the instruction to the second device to scan a QR code for logging into the target application, or to detect and display a URL or an interface of an application that requires scanning the QR code to log in; and when the second device receives the instruction to scan the QR code for logging into the target application, or the instruction to detect and display a URL or an interface of an application that requires scanning the QR code to log in, it displays the interface of the second device; and the second device is configured to launch the target application, decode the QR code, and send the login confirmation instruction to the first device.

[0013] Optionally, the first device is configured to establish a communication link with the second device and send a screen sharing instruction to the second device; the second device is configured to: upon receiving the screen sharing instruction, capture image display data of the second device; encode the image display data of the second device into a video stream; and send the video stream to the first device; and the first device is further configured to: receive the video stream; decode the video stream into frames of image data; and display the frames of image data on the first device.

[0014] Optionally, before the first device sends the screen sharing instruction to the second device, the second device is configured to: determine whether the second device is in a locked screen state; and when it is determined that the second device is in the locked screen state, unlock the second device and activate the display on the second device.

[0015] Optionally, after each frame of image data is displayed by the first device on the first device, the first device is configured to send a subsequent instruction to the second device; and upon receiving the subsequent instruction, the second device is configured to restore screen lock logic that allows the second device to re-enter sleep mode.

[0016] Optionally, the second device is configured to: identify the authentication input; extract a URL prefix from the authentication input; compare the URL prefix extracted from the authentication input with an application information database; and launch the target application associated with an entry in the application information database that matches the URL prefix extracted from the authentication input.

[0017] Optionally, the second device includes a trusted device database, which includes the MAC addresses of all trusted first devices; wherein the second device is configured to perform a pre-authentication check; wherein the second device is configured to allow an authentication input verification process if a security request from the first device matches an entry in the trusted list of the trusted device database on the second device; wherein the second device is configured to return a rejection message, stop the authentication input verification process, and prevent any further interaction between the second device and the untrusted first device if the security request from the first device does not match an entry in the trusted list of the trusted device database on the second device.

[0018] Optionally, the second device is configured to compare account information on the target application of the first device with account information on the target application of the second device; wherein the second device is configured to: allow an authentication input verification process if the account information on the target application of the first device matches the account information on the target application of the second device; and the second device is configured to: generate an alarm on the first device if the account information on the target application of the first device does not match the account information on the target application of the second device.

[0019] Optionally, after logging into the target application on the first device, the first device is configured to: determine whether the current account is the same as the account previously logged into the target application; and send a notification to the second device associated with the account previously logged into the target application; wherein the second device is configured to prompt one or more options, thereby allowing the user of the second device associated with the account previously logged into the target application to choose between logging out of the target application on the first device and remaining logged into the target application on the first device.

[0020] Optionally, the first device includes a biometric identification service and a database containing biometric data of trusted individuals; wherein the biometric identification service of the first device is configured to compare the user's biometric data with the biometric data of trusted individuals stored in the database; wherein the second device is configured to: if the confidence level of the match between the user's biometric data and the biometric data of trusted individuals stored in the database exceeds a set threshold, then confirm that the current user is trusted and continue the login process.

[0021] Optionally, the first device includes a multi-user database, which includes biometric data of each user and the IP address of the second device belonging to each user; wherein, the first device is configured to perform biometric identification on the user to determine whether the current user is the same as a previous user who previously logged into the target application; wherein, when it is determined that the current user is not the same as the previous user who previously logged into the target application, the first device is configured to: log out of the account associated with the previous user who previously logged into the target application; and prompt the current user to re-authenticate using the verification process.

[0022] Optionally, the first device is further configured to: select an IP address associated with an account associated with the current user from the multi-user database; and send the instruction to the second device having the IP address.

[0023] Optionally, when it is determined that the current user is not the same as the previous user who previously logged into the target application, the first device is configured to: send a notification to the second device associated with the account associated with the previous user who previously logged into the target application; and prompt one or more options on the second device associated with the account associated with the current user to allow the current user to choose between a first option and a second option; wherein, when the first option is selected, the first device is configured to log out of all accounts associated with the current user on the first device; and wherein, when the second option is selected, the first device is configured to allow the current user to continue using all applications on the first device.

[0024] Optionally, the first device further includes a multi-user database; wherein the multi-user database includes biometric data of each user and the IP address of the second device belonging to each user; wherein the first device is configured to: perform biometric identification on the user to determine whether the current user is the same as a previous user who previously logged into the target application; and when it is determined that the current user is not the same as the previous user who previously logged into the target application, send a notification to the second device associated with the account associated with the previous user who previously logged into the target application; wherein, upon receiving the notification, the second device associated with the account associated with the current user is configured to prompt one or more options to allow the current user to choose between a first option and a second option; wherein, when the first option is selected, the first device is configured to log out of all accounts associated with the current user on the first device; and wherein, when the second option is selected, the first device is configured to allow the current user to continue using all applications on the first device.

[0025] Optionally, the second device is configured to: generate an exit interface on the second device when the one-click exit option is selected, so as to allow the user to exit each application; when an exit selection is made on the exit interface of the application, send an exit command to the background service of the first device via a network connection; wherein, upon receiving the exit command, the first device is configured to: identify the application associated with the exit command; and exit the application associated with the exit command.

[0026] On the other hand, this disclosure provides a method for logging into an application, comprising: receiving, by a first device, an instruction for decoding authentication input for logging into the target application;

[0027] The method further includes, after the first device receives the instruction for decoding the authentication input used to log in to the target application:

[0028] The first device obtains data containing the authentication input; the first device sends the data containing the authentication input to a second device communicating with the first device; the second device identifies the target application linked to the authentication input;

[0029] or,

[0030] The first device sends the instruction to the second device to decode the authentication input for logging into the target application; when the second device receives the instruction to decode the authentication input for logging into the target application, the first device displays the interface of the second device;

[0031] The method further includes, after the second device identifies the target application linked to the authentication input, or after the first device displays the interface of the second device, the method further includes: the second device launching the target application; the second device decoding the authentication input; the second device sending a confirmation login instruction to the first device; the first device receiving the confirmation login instruction; and the first device logging into the target application on the first device.

[0032] On the other hand, this disclosure provides a computer program product including a non-transitory tangible computer-readable medium having computer-readable instructions thereon, the computer-readable instructions being executable by a processor to cause the processor to perform: receiving instructions for decoding authentication input for logging into a target application by a first device, wherein the first device communicates with a second device;

[0033] Wherein, after the first device receives the instruction for decoding the authentication input used to log in to the target application, the computer-readable instruction may be executed by one or more processors to cause the one or more processors to perform further actions:

[0034] The first device obtains data containing the authentication input; the first device sends the data containing the authentication input to the second device; the second device identifies the target application linked to the authentication input;

[0035] or,

[0036] The first device sends the instruction to the second device to decode the authentication input for logging into the target application; when the second device receives the instruction to decode the authentication input for logging into the target application, the first device displays the interface of the second device;

[0037] Wherein, after the second device identifies the target application linked to the authentication input, or after the first device displays the interface of the second device, the computer-readable instructions may be executed by one or more processors to cause the one or more processors to further perform: launching the target application by the second device; decoding the authentication input by the second device; sending a confirmation login instruction to the first device by the second device; receiving the confirmation login instruction by the first device; and logging into the target application on the first device by the first device. Attached Figure Description

[0038] The following figures are merely illustrative examples based on various disclosed embodiments and are not intended to limit the scope of the invention.

[0039] Figure 1 This is a flowchart illustrating the process for logging into an application according to this disclosure.

[0040] Figure 2 This is a schematic diagram illustrating the structure of a device for logging into an application according to the present disclosure.

[0041] Figure 3 This is a flowchart illustrating the process for logging into an application according to this disclosure.

[0042] Figure 4 This is a flowchart illustrating the process for logging into an application according to this disclosure.

[0043] Figure 5 This is a flowchart illustrating the process for logging into an application according to this disclosure.

[0044] Figure 6 This is a flowchart illustrating the process for logging into an application according to this disclosure.

[0045] Figure 7 This is a flowchart illustrating the process for logging into an application according to this disclosure. Detailed Implementation

[0046] This disclosure will now be described in more detail with reference to the following embodiments. It should be noted that the following description of some embodiments presented herein is for illustrative and descriptive purposes only. It is not exhaustive or limited to the precise forms disclosed.

[0047] Currently, the virtual reality (VR) and mixed reality (MR) industries are developing rapidly, and some applications require users to scan QR codes (Quick Response Codes) to confirm login. For example, applications like WeChat, cloud storage, Zhihu, and Taobao allow users to log in to other terminals (such as iPads or computers) by using their smartphones to scan QR codes displayed on other devices.

[0048] However, when using VR devices, virtual images are displayed directly in front of the user's eyes, and smartphones cannot scan QR codes displayed in the virtual environment, making it difficult for users to log in to these applications through VR devices. This causes inconvenience to users. The apparatus and method disclosed herein allow users to directly log in to applications on HMD (Head-Mounted Display) devices, providing a solution for logging in through VR systems without scanning physical QR codes.

[0049] Therefore, this disclosure provides, in particular, an apparatus for logging into an application, a method for logging into an application, and a computer program product that substantially eliminates one or more problems caused by the limitations and disadvantages of the prior art. In one aspect, this disclosure provides an apparatus for logging into an application. In some embodiments, the apparatus for logging into an application includes a first device. Optionally, the first device communicates with a second device. Optionally, the first device is configured to receive instructions for decoding authentication input for logging into a target application.

[0050] Optionally, after the first device receives the instruction to decode the authentication input used to log in to the target application:

[0051] The first device is also configured to: obtain data containing authentication input and send the data containing authentication input to the second device; and the second device is also configured to identify the target application linked to the authentication input;

[0052] or,

[0053] The first device is also configured to: send an instruction to a second device communicating with the first device to decode authentication input for logging into the target application; and display the interface of the second device when the second device receives the instruction to decode authentication input for logging into the target application;

[0054] Optionally, after the second device identifies the target application linked to the authentication input, or after the first device displays the interface of the second device, the second device is configured to: launch the target application; decode the authentication input; and send a confirmation login instruction to the first device; the first device is configured to receive the confirmation login instruction from the second device and log in to the target application on the first device.

[0055] Figure 1 This is a flowchart illustrating a process for logging into an application according to this disclosure. (See also...) Figure 1 In some embodiments, the method for logging into an application includes: receiving, by a first device, an instruction to decode authentication input for logging into the application; obtaining, by the first device, data containing the authentication input; sending, by the first device, the data containing the authentication input to a second device communicating with the first device; identifying, by the second device, a target application linked to the authentication input; launching, by the second device, the target application; decoding, by the second device, the authentication input; sending, by the second device, a confirmation login instruction to the first device; receiving, by the first device, the confirmation login instruction; and logging into the target application on the first device.

[0056] Figure 2 This is a schematic diagram illustrating the structure of a device for logging into an application according to the present disclosure. (Refer to...) Figure 2 In some embodiments, the apparatus for logging into an application includes a first device D1 and a second device D2 communicating with each other. In some embodiments, the first device D1 is configured to receive an instruction to decode authentication input for logging into the application, obtain data containing the authentication input, and send the data containing the authentication input to the second device D2, which communicates with the first device D1. In some embodiments, the second device D2 is configured to identify a target application linked to the authentication input, launch the target application, decode the authentication input, and send a confirmation login instruction to the first device D1. In some embodiments, the first device D1 is configured to receive the confirmation login instruction and log into the target application on the first device D1.

[0057] In this disclosure, various suitable devices can be implemented as a first device D1 or a second device D2. Examples of suitable first devices include: head-mounted displays (HMDs); virtual reality (VR) headsets; augmented reality (AR) glasses; smartwatches; smart TVs; game consoles; laptops or desktop computers; in-vehicle entertainment systems; smart speakers with displays; and smart home hubs. Examples of suitable second devices include: smartphones; tablets; laptops or desktop computers; smartwatches; IoT controllers; remote control devices (for smart homes or TVs); fitness trackers; and wearable devices (e.g., smart glasses). In a particular example, the first device is a head-mounted display device, and the second device is a mobile phone.

[0058] Various suitable authentication inputs may be used in this disclosure. Examples of suitable authentication inputs include QR codes (e.g., NFC (Near Field Communication) tags, one-time passwords (OTPs), fingerprint scans, facial recognition, iris scans, voice recognition, Bluetooth signals, encrypted URLs or links, PIN codes or passwords, biometric data such as palm scans, security tokens or key cards, proximity-based signals such as Wi-Fi or Bluetooth proximity authentication, gesture inputs on the device such as specific movements or postures, eye-tracking data, digital certificates, RFID (Radio Frequency Identification) signals, SMS-based verification codes, email-based verification links, behavioral biometrics such as typing patterns, heart rate data, environmental data such as ambient sound recognition, location-based authentication using GPS, CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) inputs for human authentication, device-based authentication using unique hardware identifiers, push notifications for two-factor authentication, and time-based dynamic QR codes. In a particular example, the authentication input is a QR code.

[0059] Various suitable instructions may be used in this disclosure. Examples of suitable instructions include a login request (an instruction sent to initiate a login process), a QR code scanning request (an instruction to obtain or decode a QR code displayed on a device), an authentication initiation (an instruction to begin a process of verifying a user's credentials), a password input request (an instruction to prompt a user to enter a password), a token generation request (an instruction to instruct the system to generate an authentication token (such as an OTP), a device pairing request (an instruction to establish a connection between two devices (e.g., via Bluetooth or Wi-Fi), a facial recognition input (an instruction to initiate facial recognition to verify a user's identity), a fingerprint verification request (an instruction to trigger a fingerprint scanning process), a two-factor authentication request (an instruction to send or verify a two-factor authentication method), a push notification prompt (an instruction to send a login verification push notification to a device), and a screen sharing request (an instruction to share a screen with another device). Instructions for the device screen, proximity detection activation (instructions verifying whether the user is within a specific distance used for proximity-based authentication), Bluetooth activation (instructions to turn on Bluetooth to communicate between devices), data decryption (instructions to decrypt encrypted data packets or tokens), session termination (instructions to end or exit an active session), application launch request (instructions to open or run a specific application on the device), biometric data request (instructions to collect biometric data (such as iris or voice recognition), password reset (instructions issued to reset a user's password), permission request (instructions seeking approval to access certain device functions (such as camera or location services)), screen unlock (instructions sent to remotely unlock the device screen), and authentication confirmation (instructions to complete and confirm the authentication process).

[0060] As used herein, the term "decoding authentication input" refers to the process of interpreting or converting encoded or formatted data fragments (authentication input) into a usable form that can be understood and processed by a device for authentication purposes. In one example, the decoding process includes converting an encrypted QR code, token, or signal into readable information (such as a Uniform Resource Locator (URL), user credentials, or authentication key) that a device can then use to facilitate the login process. Decoding typically involves identifying the format, extracting the relevant data, and converting it into a format that an application can work with.

[0061] The first device can acquire a variety of appropriate data containing authentication input. Examples of appropriate data containing authentication input include: images of QR codes or barcodes, which can be displayed on a screen or physical object for scanning; NFC signals, which are sent when devices are very close to initiate contactless authentication; and Bluetooth signals, which enable secure device pairing over short distances. Encrypted digital tokens that can be exchanged between devices or servers to verify user credentials are also common. Biometric data such as fingerprint scans, facial recognition, or iris scans can be acquired for user identification. Voice commands processed by voice recognition software can be used as authentication input, while dynamic security codes for verification are provided based on text or one-time passwords (OTPs) generated via the application. Additionally, proximity-based signals (such as Wi-Fi or Bluetooth proximity detection) allow authentication based on the distance between devices involved in the login process. These different data types ensure flexible and secure authentication methods across a variety of scenarios. In a specific example, the data containing authentication input acquired by the first device is an image of a QR code.

[0062] Various appropriate login confirmation instructions may be used in this disclosure. Examples of appropriate login confirmation instructions include direct instructions confirming successful authentication (e.g., messages indicating that a user's credentials have been verified) or token-based confirmations, where an encrypted token is sent to verify the login session. Other examples include: one-time password (OTP) verification results; biometric verification results confirming a match between a fingerprint, facial recognition, or iris scan and a registered user; and secure handshake protocols ensuring that two devices recognize each other as authorized. Along with proximity-based confirmations (e.g., when a second device confirms it is within a specific range of a first device), push notifications or encrypted messages containing digital signatures may also be used as confirmation instructions. These instructions are used to instruct the first device to complete the login process and grant access to the relevant application.

[0063] The inventors of this disclosure have discovered that the methods and apparatus according to this disclosure solve several problems, including enabling application login on devices such as head-mounted displays (HMDs), addressing privacy concerns, and enhancing security mechanisms. The beneficial technical effects achieved by this disclosure include making it easier for users to log in to applications on HMDs while improving privacy protection and strengthening overall security. This ensures a seamless and secure login process that protects user data in virtual or augmented reality environments.

[0064] Figure 3 This is a flowchart illustrating a process for logging into an application according to this disclosure. (See also...) Figure 3In some embodiments, receiving instructions for decoding authentication input for logging into an application by the first device includes: receiving instructions for scanning a QR code for logging into the application, or detecting instructions to display a URL or an interface of an application requiring QR code scanning for login. In some embodiments, obtaining data containing authentication input by the first device includes: capturing an image containing a QR code by the first device. In some embodiments, sending data containing authentication input by the first device to a second device communicating with the first device includes: sending an image containing a QR code by the first device to the second device communicating with the first device. In some embodiments, identifying a target application linked to the authentication input by the second device includes: identifying a target application linked to the QR code by the second device. In some embodiments, decoding authentication input by the second device includes: decoding the QR code by the second device. (See also...) Figure 3 In some embodiments, the method for logging into an application includes: receiving, by a first device, an instruction to scan a QR code for logging into the application, or detecting an instruction to display a URL or an interface of an application that requires scanning a QR code to log in; capturing, by the first device, an image containing the QR code; sending, by the first device, the image containing the QR code to a second device communicating with the first device; identifying, by the second device, a target application linked to the QR code; launching, by the second device, the target application; decoding, by the second device, the QR code; sending, by the second device, a login confirmation instruction to the first device; receiving, by the first device, the login confirmation instruction; and logging into the target application on the first device.

[0065] In some embodiments, the apparatus for logging into an application includes a first device and a second device communicating with each other. In some embodiments, the first device is configured to: receive an instruction to scan a QR code for logging into the application, or detect an instruction to display a URL or an interface of an application requiring QR code scanning for login; capture an image containing the QR code; and send the image containing the QR code to a second device communicating with the first device. In some embodiments, the second device is configured to identify a target application linked to the QR code, launch the target application, decode the QR code, and send a login confirmation instruction to the first device. In some embodiments, the first device is configured to receive the login confirmation instruction and log into the target application on the first device.

[0066] The inventors of this disclosure have discovered that the methods and apparatus according to this disclosure solve several problems, including enabling application login on devices such as head-mounted displays (HMDs), addressing privacy concerns, and enhancing security mechanisms. The beneficial technical effects achieved by this disclosure include making it easier for users to log in to applications on HMDs while improving privacy protection and strengthening overall security. This ensures a seamless and secure login process that protects user data in virtual or augmented reality environments.

[0067] Figure 4 This is a flowchart illustrating a process for logging into an application according to this disclosure. (See also...) Figure 4 In some embodiments, the method for logging into an application includes: a first device receiving an instruction to decode authentication input for logging into the application; the first device sending the instruction to decode authentication input for logging into the application to a second device communicating with the first device; when the second device receives the instruction to decode authentication input for logging into the application, the first device displaying the interface of the second device; the second device launching the target application; the second device decoding the authentication input; the second device sending a login confirmation instruction to the first device; the first device receiving the login confirmation instruction; and the first device logging into the target application on the first device.

[0068] In some embodiments, the apparatus for logging into an application includes a first device and a second device communicating with each other. In some embodiments, the first device is configured to: receive an instruction to decode authentication input for logging into the application; send the instruction to decode the authentication input for logging into the application to a second device communicating with the first device; and display the interface of the second device when the second device receives the instruction to decode the authentication input for logging into the application. In some embodiments, the second device is configured to: launch a target application; decode authentication input; and send a login confirmation instruction to the first device. In some embodiments, the first device is further configured to: receive a login confirmation instruction; and log into the target application on the first device.

[0069] In this disclosure, various suitable devices can be implemented as either a first device or a second device. Examples of suitable first devices include: head-mounted displays (HMDs); virtual reality (VR) headsets; augmented reality (AR) glasses; smartwatches; smart TVs; game consoles; laptops or desktop computers; in-vehicle entertainment systems; smart speakers with displays; and smart home hubs. Examples of suitable second devices include: smartphones; tablets; laptops or desktop computers; smartwatches; IoT controllers; remote control devices (for smart homes or TVs); fitness trackers; and wearable devices (e.g., smart glasses). In a particular example, the first device is a head-mounted display device, and the second device is a mobile phone.

[0070] Various suitable authentication inputs may be used in this disclosure. Examples of suitable authentication inputs include QR codes (e.g., NFC (Near Field Communication) tags, one-time passwords (OTPs), fingerprint scans, facial recognition, iris scans, voice recognition, Bluetooth signals, encrypted URLs or links, PIN codes or passwords, biometric data such as palm scans, security tokens or key cards, proximity-based signals such as Wi-Fi or Bluetooth proximity authentication, gesture inputs on the device such as specific movements or postures, eye-tracking data, digital certificates, RFID (Radio Frequency Identification) signals, SMS-based verification codes, email-based verification links, behavioral biometrics such as typing patterns, heart rate data, environmental data such as ambient sound recognition, location-based authentication using GPS, CAPTCHA inputs for human verification, device-based authentication using unique hardware identifiers, push notifications for two-factor authentication, and time-based dynamic QR codes. In a particular example, the authentication input is a QR code.

[0071] Various appropriate instructions may be used in this disclosure. Examples of appropriate instructions include a login request (an instruction sent to initiate a login process), a QR code scanning request (an instruction to obtain or decode a QR code displayed on a device), an authentication initiation (an instruction to begin a process of verifying a user's credentials), a password input request (an instruction to prompt a user to enter a password), a token generation request (an instruction to instruct the system to generate an authentication token (such as an OTP), a device pairing request (an instruction to establish a connection between two devices (e.g., via Bluetooth or Wi-Fi), a facial recognition input (an instruction to initiate facial recognition to verify a user's identity), a fingerprint verification request (an instruction to trigger a fingerprint scanning process), a two-factor authentication request (an instruction to send or verify a two-factor authentication method), a push notification prompt (an instruction to send a login verification push notification to a device), and a screen sharing request (an instruction to share screens with another device). Instructions to a device's screen include: proximity detection activation (an instruction to verify that a user is within a specific distance for proximity-based authentication), Bluetooth activation (an instruction to turn on Bluetooth to enable communication between devices), data decryption (an instruction to decrypt encrypted data packets or tokens), session termination (an instruction to end or exit an active session), application launch request (an instruction to open or run a specific application on the device), biometric data request (an instruction to collect biometric data (such as iris or voice recognition), password reset (an instruction issued to reset a user's password), permission request (an instruction seeking approval to access certain device functions (such as a camera or location services)), screen unlock (an instruction sent to remotely unlock the device screen), and authentication confirmation (an instruction to complete and confirm the authentication process).

[0072] Various appropriate login confirmation instructions may be used in this disclosure. Examples of appropriate login confirmation instructions include direct instructions confirming successful authentication (e.g., messages indicating that a user's credentials have been verified) or token-based confirmations, where an encrypted token is sent to verify the login session. Other examples include: one-time password (OTP) verification results; biometric verification results confirming a match between a fingerprint, facial recognition, or iris scan and a registered user; and secure handshake protocols ensuring that two devices recognize each other as authorized. Along with proximity-based confirmations (e.g., when a second device confirms it is within a specific range of a first device), push notifications or encrypted messages containing digital signatures may also be used as confirmation instructions. These instructions are used to instruct the first device to complete the login process and grant access to the relevant application.

[0073] The inventors of this disclosure have discovered that the methods and apparatus according to this disclosure solve several problems, including enabling application login on devices such as head-mounted displays (HMDs), addressing privacy concerns, and enhancing security mechanisms. The beneficial technical effects achieved by this disclosure include making it easier for users to log in to applications on HMDs while improving privacy protection and strengthening overall security. This ensures a seamless and secure login process that protects user data in virtual or augmented reality environments.

[0074] Figure 5 This is a flowchart illustrating a process for logging into an application according to this disclosure. (See also...) Figure 5 In some embodiments, receiving an instruction to decode authentication input for logging into an application by the first device includes: receiving an instruction to scan a QR code for logging into the application, or detecting an instruction to display a URL or an interface of an application requiring QR code scanning for login. In some embodiments, sending an instruction to decode authentication input for logging into an application by the first device to a second device communicating with the first device includes: sending an instruction to scan a QR code for logging into the application by the first device to the second device communicating with the first device, or detecting an instruction to display a URL or an interface of an application requiring QR code scanning for login. In some embodiments, when the second device receives an instruction to decode authentication input for logging into the application, displaying the interface of the second device by the first device includes: when the second device receives an instruction to scan a QR code for logging into the application, or detects an instruction to display a URL or an interface of an application requiring QR code scanning for login, the first device displays the interface of the second device.

[0075] Reference Figure 5In some embodiments, the method for logging into an application includes: a first device receiving an instruction to scan a QR code for logging into the application, or detecting an instruction to display a URL or an interface of an application requiring QR code scanning for login; the first device sending the instruction to scan a QR code for logging into the application, or detecting an instruction to display a URL or an interface of an application requiring QR code scanning for login, to a second device communicating with the first device; when the second device receives the instruction to scan a QR code for logging into the application, or detects an instruction to display a URL or an interface of an application requiring QR code scanning for login, the first device displaying the interface of the second device; the second device launching the target application; the second device decoding the QR code; the second device sending a login confirmation instruction to the first device; the first device receiving the login confirmation instruction; and the first device logging into the target application on the first device.

[0076] In some embodiments, the apparatus for logging into an application includes a first device and a second device communicating with each other. In some embodiments, the first device is configured to: receive an instruction to scan a QR code for logging into the application, or detect an instruction to display a URL or an interface of an application requiring QR code scanning for login; send the instruction to the second device to scan a QR code for logging into the application, or detect an instruction to display a URL or an interface of an application requiring QR code scanning for login; and display the interface of the second device when the second device receives the instruction to scan a QR code for logging into the application or detects an instruction to display a URL or an interface of an application requiring QR code scanning for login. In some embodiments, the second device is configured to launch a target application, decode a QR code, and send a login confirmation instruction to the first device. In some embodiments, the first device is further configured to receive the login confirmation instruction and log into the target application on the first device.

[0077] Figure 6 This is a flowchart illustrating a process for logging into an application according to this disclosure. (See also...) Figure 6 In some embodiments, when the second device receives an instruction to decode authentication input for logging into the application, the first device displays the interface of the second device, which includes: establishing a communication link between the first and second devices (e.g., via a handshake); the first device sending a screen sharing instruction to the second device; upon receiving the screen sharing instruction, the second device capturing image display data of the second device; the second device encoding the image display data of the second device into a video stream; the second device sending the video stream to the first device; the first device receiving the video stream; the first device decoding the video stream into frames of image data; and the first device displaying the frames of the image data on the first device.

[0078] In some embodiments, the first device is configured to: establish a communication link with the second device (e.g., via a handshake); and send a screen sharing instruction to the second device. In some embodiments, the second device is configured to: upon receiving the screen sharing instruction, capture image display data of the second device; encode the image display data of the second device into a video stream; and send the video stream to the first device. In some embodiments, the first device is further configured to: receive the video stream; decode the video stream into frames of image data; and display the frames of image data on the first device.

[0079] In some embodiments, before sending a screen sharing command from the first device to the second device, the method further includes: determining, by a background service on the second device, whether the second device is in a locked state; and when the background service determines that the second device is in a locked state, sending a local unlock code to unlock the second device and activate the display on the second device. Optionally, the method further includes: configuring the second device by the background service to prevent the second device from entering sleep mode or dimming the display during a screen sharing session.

[0080] In some embodiments, before sending a screen sharing instruction to the second device, the second device is configured to: determine whether the second device is in a locked state by a background service on the second device; and when the background service determines that the second device is in a locked state, send a local unlock code to unlock the second device and activate the display on the second device.

[0081] In some embodiments, after each frame of image data is displayed on the first device by the first device, the method further includes: sending a subsequent instruction from the first device to the second device; and, upon receiving the subsequent instruction, restoring screen lock logic that allows the second device to re-enter sleep mode.

[0082] In some embodiments, after each frame of image data is displayed on the first device, the first device is configured to send a subsequent instruction to the second device. Upon receiving the subsequent instruction, the second device is configured to restore screen lock logic that allows the second device to re-enter sleep mode.

[0083] Various suitable methods can be used to establish a communication link between the first and second devices. In a specific example, pairing between the first and second devices can be established via Bluetooth or direct Wi-Fi during the initial connection. During the pairing process, the two devices exchange unique encryption keys. For example, the second device is configured to send a connection request to the first device, which generates a random 6-digit code. The user enters this code on the second device, and if the code matches, pairing is successful. Furthermore, the second device's identification code is stored in the first device's list of authorized devices, enabling encrypted communication for subsequent interactions.

[0084] Various appropriate methods can be used to disconnect the communication link between the first and second devices. In one specific example, the communication link between the first and second devices can be disconnected manually, where the user can actively disconnect via an interface on either the first or second device. In another example, the communication link between the first and second devices can be disconnected automatically, where the system can automatically terminate the connection if there has been no communication between the first and second devices for an extended period of time, in order to save energy and prevent unauthorized access.

[0085] To prevent a lost or stolen second device (e.g., a mobile phone or virtual reality device) from connecting to an unauthorized first device (e.g., an HMD), remote locking or device binding restrictions can be implemented. Through a mobile app or web interface, a user can remotely lock the second device (e.g., a virtual reality device), preventing it from connecting to any first device (e.g., an HMD) until the user unlocks it. Alternatively, the second device (e.g., a virtual reality device) can maintain a whitelist of authorized first devices (e.g., authorized HMDs), ensuring that even if the second device is lost, unauthorized first devices (e.g., unauthorized HMDs) cannot connect.

[0086] The first and second devices can determine their proximity by detecting the strength of Bluetooth or Wi-Fi signals. If the signal drops below a certain threshold, the system can automatically disconnect the devices. Alternatively, the first device can use accelerometer and gyroscope data to assess whether the user is still wearing the second device (e.g., an HMD) or has removed it. If the user remains inactive for an extended period, the system can automatically disconnect. Before disconnecting, the system can send a notification to the user requesting confirmation to prevent unnecessary disconnections due to erroneous signals.

[0087] After the first successful connection between the first and second devices, the MAC address (Media Access Control address) of the second device is stored in the whitelist of the first device. This MAC address is a unique hardware identifier used by network devices. During subsequent connections, the first device compares the incoming connection information with the MAC address list, and if the address is recognized, it will automatically re-establish the connection.

[0088] In some embodiments, launching a target application by a second device includes: recognizing an authentication input (e.g., a QR code); and extracting a URL prefix from the authentication input. In a particular example, the second device (e.g., a mobile phone) identifies the authentication input (e.g., a QR code) as corresponding to a specific application. In one example, the authentication input is a QR code, which is typically encoded as a text-based URL. A background recognition algorithm on the second device can decode the QR code into a text URL.

[0089] In some embodiments, launching the target application by the second device further includes comparing a URL prefix extracted from the authentication input with an application information database. Once the URL is decoded, the second device extracts the URL prefix, which includes all characters preceding the third " / ". This prefix is ​​then compared with the application information database. If the extracted prefix matches an entry in the database, the target application is launched.

[0090] In one example, the QR code prefix is ​​https: / / login.app1.com / *****, and the second device will launch the first application. In another example, the QR code prefix is ​​https: / / api.app2.com / *****, and the second device will launch the second application. This method is repeated for different applications based on their specific URL structures.

[0091] After launching the target application, the second device's background service will call the API for the app's QR code scanning function. The QR code data will be passed to the target application to complete login authentication. Once the second device successfully authenticates, the first device will automatically log in to the application, completing the process.

[0092] In some embodiments, to prevent unauthorized users from connecting to the second device, a background security service is installed on the second device. In some embodiments, the method further includes: establishing a trusted device database in the second device; and performing a pre-authentication check. In one example, a database (trust list) is created on the second device, pre-entering the MAC addresses (globally unique hardware identifiers) of all trusted first devices. Before recognizing a QR code, the second device is configured to perform a pre-authentication check. If a security request from the first device (e.g., HMD) matches an entry in the trust list on the second device, the second device is configured to allow the next step of the QR code verification process. If the request does not match an entry in the trust list, the second device returns a rejection message, stops the verification process, and prevents any further interaction between the second device and the untrusted first device. This ensures that only pre-approved first devices can connect to the second device, thus providing an additional layer of security to prevent unauthorized access. In some embodiments, the method further includes: generating an alert on the first device when a request does not match an entry in the trust list, thereby notifying that verification has not been approved.

[0093] In an alternative embodiment, the method further includes comparing account information on a target application of the first device with account information on a target application of the second device. If the account credentials match, the system confirms that the first device and the second device belong to the same user, thereby allowing the process to continue smoothly. This embodiment ensures an additional layer of verification to prevent unauthorized access, confirming that the same user is operating the two devices before proceeding to further authentication steps. In some embodiments, the method further includes generating an alert on the first device when the account information on the target application of the first device does not match the account information on the target application of the second device, thereby notifying that the verification has not been approved.

[0094] In some embodiments, after a first device logs into the target application on a first device, the method further includes: the first device determining whether the current account is the same as an account previously logged into the target application; and the first device sending a notification to a second device associated with the account previously logged into the target application. In some embodiments, the method further includes: prompting one or more options on the second device, allowing a user of the second device to choose between logging out of the target application on the first device and remaining logged into the target application on the first device. This provides security measures to ensure that only the correct user remains logged into the application on the first device, thereby providing flexibility and control over user sessions from smartphones.

[0095] In some embodiments, performing a pre-authentication check includes performing biometric identification on the user. In one example, a facial recognition service (e.g., an eye recognition service) is installed on a first device, and biometric data of a trusted individual (e.g., eye data) is pre-recorded in a database on the first device. When a user needs to securely log in to the application, the facial recognition service (e.g., the eye recognition service) is automatically activated. The system scans the user's eye data and compares it with trusted individuals stored in the database. If the confidence level of the match exceeds a set threshold, the system confirms that the current user is trusted and continues the login process. This method provides an additional layer of security, ensuring that only pre-authorized users can access the application on the first device based on their unique biometric data.

[0096] In some embodiments, the method further includes: generating a selection interface on the first device to allow selection of a second device from a list of second devices. When different users use the first device, they can select different second devices to log in. In one example, there is a first second device (belonging to user A) and a second second device (belonging to user B), both connected to the first device. When user A uses the first device, they can select the first second device to log in to their personal account. A login confirmation instruction is sent to the first second device to process the authentication and login process. When user B starts using the first device, user B can manually log out of user A's session, or the first device can automatically recognize that user B is now using the device. At this time, a notification is sent to the first second device, asking whether to log out of user A's account. Alternatively, user B can manually log out of user A's account on the selection interface displayed on the first device, or user A can receive a remote logout prompt. In the case of logging into multiple applications simultaneously, the system allows users to selectively log out of certain applications or select a "one-click logout" option to log out of all applications simultaneously.

[0097] In some embodiments, the method further includes: establishing a multi-user database on a first device. Optionally, the multi-user database includes biometric data for each user and the IP address of a second device belonging to each user. Each user's biometric data and the IP address of the second device belonging to each user are associated with each user's profile.

[0098] In some embodiments, the method further includes performing biometric identification (e.g., eye recognition) on the user to determine whether the current user is the same as a previous user who previously logged into the target application. If it is determined that the current user is not the same as a previous user who previously logged into the target application, the method further includes: logging out of the account associated with the previous user who previously logged into the target application; and prompting the current user to re-authenticate using the verification process.

[0099] In some embodiments, before sending an instruction to a second device communicating with the first device to decode authentication input for logging into the application, the method further includes: selecting an IP address associated with an account associated with the current user from a multi-user database on the first device, wherein the instruction is sent to the second device having that IP address. This ensures that the second device belonging to a previous user who previously logged into the target application remains unaffected. This multi-user scenario ensures a smooth transition between users, maintaining security by binding each user's biometric data and IP address, while preventing unintentional interaction with another user's device or application.

[0100] In some embodiments, the method further includes: establishing a multi-user database on a first device. Optionally, the multi-user database includes biometric data for each user and the IP address of a second device belonging to each user. Each user's biometric data and the IP address of the second device belonging to each user are associated with each user's profile.

[0101] In some embodiments, the method further includes: performing biometric identification (e.g., eye recognition) on the user to determine whether the current user is the same as a previous user who previously logged into the target application. If it is determined that the current user is not the same as a previous user who previously logged into the target application, the method further includes: sending a notification from the first device to a second device associated with an account associated with the previous user who previously logged into the target application; and prompting one or more options on the second device associated with the account associated with the current user, allowing the current user to choose between a first option and a second option.

[0102] In some embodiments, when selecting the first option, the method further includes: logging out of all accounts associated with the current user on the first device. The current user needs to re-authenticate through an authentication process.

[0103] In some embodiments, when selecting the second option, the method further includes allowing the current user to continue using all applications on the first device.

[0104] In some embodiments, the second device includes a management application configured to perform at least one of binding the first device and one-click logout.

[0105] In some embodiments, the method further includes: after selecting the one-click exit option, generating an exit interface on the second device, allowing the user to exit various applications (e.g., WeChat, cloud storage, Douyin, etc.) on the first device. In some embodiments, the method further includes: when an exit selection is made on the application's exit interface, the second device sends an exit command to the background service of the first device via a network connection; the first device receives the exit command; the first device identifies the application associated with the exit command; and the first device exits the application associated with the exit command. This method allows users to exit various applications such as WeChat or cloud storage, or exit all applications simultaneously. This one-click exit function provides users with flexibility, allowing them to selectively exit specific applications or use a single command to effectively exit all accounts on the first device.

[0106] In some embodiments, the method further includes: sending an unlock command from the first device to the second device; receiving the unlock command from the second device; determining whether the second device is in an unlocked state; and unlocking the second device when it is determined that the second device is in an unlocked state. In one example, an API interface (e.g., a power manager) is used to perform the unlocking of the second device. If the unlocking attempt fails, it indicates that the phone is password protected. To ensure successful unlocking, the background service of the second device must pre-store the user's password. In the case where the phone is password protected, the background service first uses the API interface to wake up the screen, thereby displaying a password input interface. Then, the accessibility service is activated to automatically enter the pre-stored password and complete the unlocking process. Alternatively, the phone's screen can be mirrored to the first device, allowing the wearer to enter the corresponding password via gesture or swipe unlock. Once the password is entered, the phone's background service compares the input with the stored password to complete the unlocking. Additionally, if the phone supports facial recognition, the user's facial data can be sent from the first device to the second device. The second device compares this data with stored facial recognition information. If they match, the second device unlocks. Once unlocked, the screen of the second device can be displayed on the first device for further interaction.

[0107] Figure 7 This is a flowchart illustrating a process for logging into an application according to this disclosure. (See also...) Figure 7In some embodiments, the method for logging into an application includes: receiving, by a first device, an instruction to decode authentication input for logging into a target application; launching the target application by a second device; decoding the authentication input by the second device; sending a confirmation login instruction to the first device by the second device; receiving the confirmation login instruction by the first device; and logging into the target application by the first device on the first device. In some embodiments, before launching the target application by the second device and after receiving the instruction to decode the authentication input for logging into the target application by the first device, the method further includes:

[0108] The first device obtains data containing authentication input; the first device sends the data containing authentication input to a second device communicating with the first device; the second device identifies the target application linked to the authentication input;

[0109] or,

[0110] The first device sends an instruction to the second device, which communicates with the first device, to decode the authentication input used to log in to the target application; when the second device receives the instruction to decode the authentication input used to log in to the target application, the first device displays the interface of the second device.

[0111] In some embodiments, the apparatus for logging into an application includes a first device and a second device communicating with each other. In some embodiments, the first device is configured to receive an instruction to decode authentication input for logging into the application. In some embodiments, the second device is configured to: launch the target application; decode the authentication input; and send a confirmation login instruction to the first device. In some embodiments, the first device is further configured to: receive the confirmation login instruction; and log into the target application on the first device. In some embodiments, before the target application is launched by the second device, and after the first device receives the instruction to decode the authentication input for logging into the application:

[0112] The first device is also configured to acquire data containing authentication input and send the data containing authentication input to the second device; the second device is also configured to identify the target application linked to the authentication input;

[0113] or,

[0114] The first device is also configured to: send an instruction to a second device that communicates with the first device to decode authentication input for logging into the application; and display the interface of the second device when the second device receives the instruction to decode authentication input for logging into the application.

[0115] On the other hand, this disclosure provides a computer program product including a non-transitory tangible computer-readable medium having computer-readable instructions thereon. In some embodiments, the computer-readable instructions may be executed by one or more processors to cause one or more processors to perform: receiving, by a first device, an instruction for decoding authentication input for logging into a target application, wherein the first device communicates with a second device; launching the target application by the second device; decoding the authentication input by the second device; sending a confirmation login instruction to the first device by the second device; receiving the confirmation login instruction by the first device; and logging into the target application by the first device on the first device. In some embodiments, before the target application is launched by the second device, and after the first device receives the instruction for decoding authentication input for logging into the target application, the computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform:

[0116] The first device obtains data containing authentication input; the first device sends the data containing authentication input to a second device communicating with the first device; the second device identifies the target application linked to the authentication input;

[0117] or,

[0118] The first device sends an instruction to the second device, which communicates with the first device, to decode the authentication input used to log in to the target application; when the second device receives the instruction to decode the authentication input used to log in to the target application, the first device displays the interface of the second device.

[0119] In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to perform: receiving instructions from a first device to scan a QR code for logging into an application.

[0120] In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to perform: receiving instructions from the first device to detect an interface displaying a URL or requiring a QR code to be scanned for login to an application.

[0121] In some embodiments, before the target application is launched by the second device, and after the first device receives instructions to decode authentication input for logging into the application, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: obtaining data containing the authentication input by the first device; sending the data containing the authentication input by the first device to a second device communicating with the first device; and identifying the target application linked to the authentication input by the second device.

[0122] In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: capturing an image containing a QR code by a first device, sending the image containing the QR code to a second device communicating with the first device; and identifying a target application linked to the QR code by the second device, launching the target application, decoding the QR code, and sending a login confirmation instruction to the first device.

[0123] In some embodiments, before the target application is launched by the second device, and after the first device receives the instruction to decode the authentication input for logging into the application, the computer-readable instruction may be executed by one or more processors to cause one or more processors to further perform: the first device sends the instruction to decode the authentication input for logging into the application to the second device in communication with the first device; and when the second device receives the instruction to decode the authentication input for logging into the application, the first device displays the interface of the second device.

[0124] In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: sending an instruction from the first device to the second device to scan a QR code for logging into an application, or detecting an instruction to display a URL or an interface of an application that requires scanning a QR code to log in; when the second device receives the instruction to scan a QR code for logging into an application, or the instruction to display a URL or an interface of an application that requires scanning a QR code to log in, the first device displays the interface of the second device; the second device launches the target application; the second device decodes the QR code; and the second device sends a login confirmation instruction to the first device.

[0125] In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: establishing a communication link between the first device and the second device; sending a screen sharing instruction to the second device by the first device; upon receiving the screen sharing instruction, capturing image display data of the second device by the second device; encoding the image display data of the second device into a video stream by the second device; sending the video stream to the first device by the second device; receiving the video stream by the first device; decoding the video stream into frames of image data by the first device; and displaying the frames of image data on the first device by the first device.

[0126] In some embodiments, prior to sending a screen sharing instruction from the first device to the second device, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: determining whether the second device is in a locked state; and, if it is determined that the second device is in a locked state, unlocking the second device and activating the display on the second device.

[0127] In some embodiments, after each frame of image data is displayed by the first device on the first device, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: sending subsequent instructions from the first device to the second device; and, upon receiving the subsequent instructions, restoring screen lock logic that allows the second device to re-enter sleep mode.

[0128] In some embodiments, the second device includes a trusted device database that includes the MAC addresses of all trusted first devices. In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform a pre-authentication check by the second device. In some embodiments, the computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: if a security request from the first device matches an entry in the trust list of the trusted device database on the second device, the second device allows the authentication input verification process; if the security request from the first device does not match an entry in the trust list of the trusted device database on the second device, the second device returns a rejection message; the second device stops the authentication input verification process; and the second device blocks any further interaction between the second device and the untrusted first device.

[0129] In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: comparing account information on a target application of the first device with account information on a target application of the second device by the second device; if the account information on the target application of the first device matches the account information on the target application of the second device, then the second device allows an authentication input verification process; and when the account information on the target application of the first device does not match the account information on the target application of the second device, the second device generates an alarm on the first device.

[0130] In some embodiments, after logging into the target application on a first device, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: the first device determines whether the current account is the same as the account previously logged into the target application; the first device sends a notification to a second device associated with the account previously logged into the target application; and the second device prompts one or more options, allowing the user of the second device associated with the account previously logged into the target application to choose between logging out of the target application on the first device and remaining logged into the target application on the first device.

[0131] In some embodiments, the first device includes a biometric identification service and a database containing biometric data of trusted individuals. In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: the biometric identification service of the first device compares the user's biometric data with the biometric data of trusted individuals stored in the database; if the confidence level of the match between the user's biometric data and the biometric data of trusted individuals stored in the database exceeds a set threshold, then the second device confirms that the current user is trusted and continues the login process.

[0132] In some embodiments, the first device includes a selection interface to allow selection of a second device from a list of second devices.

[0133] In some embodiments, the first device includes a multi-user database that includes biometric data for each user and IP addresses of second devices belonging to each user. In some embodiments, computer-readable instructions may be executed by one or more processors to cause the one or more processors to further perform: biometric identification of the user by the first device to determine whether the current user is the same as a previous user who previously logged into the target application; and, if it is determined that the current user is not the same as a previous user who previously logged into the target application, logging out of the account associated with the previous user who previously logged into the target application by the second device; and prompting the current user to re-authenticate using an authentication process.

[0134] In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: selecting, by a first device, an IP address associated with an account associated with the current user from a multi-user database; and sending instructions by the first device to a second device having the IP address.

[0135] In some embodiments, when it is determined that the current user is not the same as a previous user who previously logged into the target application, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: sending a notification by a first device to a second device associated with an account associated with the previous user who previously logged into the target application; and prompting one or more options by the first device on the second device associated with the account associated with the current user, allowing the current user to choose between a first option and a second option. In some embodiments, computer-readable instructions may be executed by one or more processors to cause one or more processors to further perform: upon selecting the first option, logging out of all accounts associated with the current user on the first device; and upon selecting the second option, allowing the current user to continue using all applications on the first device.

[0136] All or some steps of the methods disclosed above, the functional modules / units in the system, and the devices can be implemented as software, firmware, hardware, or a suitable combination thereof. In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division between physical components. For example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software can be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). The term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data, as known to those skilled in the art. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible by a computer. Additionally, communication media are typically embodied as computer-readable instructions, data structures, program modules, or other data in modulated data signals, such as carrier waves or other transmission mechanisms, and include any information transmission medium as is known to those skilled in the art.

[0137] For illustrative and descriptive purposes, the foregoing description of embodiments of the invention has been provided. It is not exhaustive, nor is it intended to limit the invention to the precise forms or exemplary embodiments disclosed. Therefore, the foregoing description should be considered illustrative rather than restrictive. Clearly, many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described to explain the principles of the invention and its best mode of practical application, thereby enabling those skilled in the art to understand the various embodiments of the invention and the various modifications suitable for the particular use or implementation contemplated. The scope of the invention is intended to be defined by the appended claims and their equivalents, wherein, unless otherwise stated, all terms are to be interpreted in their broadest reasonable sense. Therefore, the terms “the invention,” “the present invention,” etc., do not necessarily limit the scope of the claims to the specific embodiments, and references to exemplary embodiments of the invention do not imply limitation of the invention, nor should such limitation be inferred. The invention is defined only by the spirit and scope of the appended claims. Furthermore, these claims may involve the use of “first,” “second,” etc., followed by nouns or elements. These terms should be understood as nomenclature and should not be construed as limiting the number of elements modified by these nomenclatures unless a specific number has been given. Any advantages and benefits described may not apply to all embodiments of the invention. It should be understood that changes to the described embodiments can be made by those skilled in the art without departing from the scope of the invention as defined by the appended claims. Furthermore, the elements and components in this disclosure are not intended for public distribution, whether or not they are expressly recited in the appended claims.

Claims

1. An apparatus for logging into a target application, comprising a first device; in, The first device communicates with the second device; The first device is configured to receive instructions for decoding authentication input used to log in to the target application; Wherein, after the first device receives the instruction to decode the authentication input for logging into the target application: The first device is further configured to obtain data containing the authentication input and send the data containing the authentication input to the second device; and the second device is further configured to identify the target application linked to the authentication input; or, The first device is further configured to: send the instruction to the second device to decode the authentication input for logging into the target application; and display the interface of the second device when the second device receives the instruction to decode the authentication input for logging into the target application; Specifically, this occurs after the second device identifies the target application linked to the authentication input, or after the first device displays the interface of the second device: The second device is configured to: launch the target application; decode the authentication input; and send a confirmation login command to the first device; and The first device is configured to receive the confirmation login instruction from the second device and log in to the target application on the first device.

2. The apparatus according to claim 1, wherein, The first device is configured to receive instructions to scan a QR code used to log in to the target application.

3. The apparatus according to claim 1, wherein, The first device is configured to receive instructions to detect and display a URL or an interface of an application that requires scanning a QR code to log in.

4. The apparatus according to claim 1, wherein, The first device is also configured to capture an image containing a QR code and send the image containing the QR code to the second device; and The second device is configured to identify the target application linked to the QR code, launch the target application, decode the QR code, and send a confirmation login command to the first device.

5. The apparatus according to claim 1, wherein, The first device is configured to send the instruction to the second device to scan a QR code for logging into the target application, or to detect and display a URL or an interface of an application that requires scanning the QR code to log in; and to display the interface of the second device when the second device receives the instruction to scan the QR code for logging into the target application, or the instruction to detect and display a URL or an interface of an application that requires scanning the QR code to log in; as well as The second device is configured to launch the target application, decode the QR code, and send the login confirmation command to the first device.

6. The apparatus according to claim 1, wherein, The first device is configured to establish a communication link with the second device and send a screen sharing command to the second device; The second device is configured to: upon receiving the screen sharing instruction, capture image display data of the second device; encode the image display data of the second device into a video stream; and send the video stream to the first device; as well as The first device is further configured to: receive the video stream; decode the video stream into frames of image data; and display the frames of image data on the first device.

7. The apparatus according to claim 6, wherein, Before the screen sharing command is sent from the first device to the second device, the second device is configured to: Determine whether the second device is in a locked state; as well as When it is determined that the second device is in the locked screen state, the second device is unlocked and the display on the second device is activated.

8. The apparatus according to claim 6, wherein, After each frame of image data is displayed by the first device on the first device, the first device is configured to send subsequent instructions to the second device; and Upon receiving the subsequent instruction, the second device is configured to restore the screen lock logic that allows the second device to re-enter sleep mode.

9. The apparatus according to claim 1, wherein, The second device is configured as follows: Identify the authentication input; Extract the URL prefix from the authentication input; The URL prefix extracted from the authentication input is compared with the application information database; as well as Launch the target application associated with the entry in the application information database that matches the URL prefix extracted from the authentication input.

10. The apparatus according to claim 1, wherein, The second device includes a trusted device database, which contains the MAC addresses of all trusted first devices; The second device is configured to perform a pre-authentication check; The second device is configured to allow an authentication input verification process if a security request from the first device matches an entry in the trust list of the trusted device database on the second device. The second device is configured to return a rejection message, stop the authentication input verification process, and prevent any further interaction between the second device and the untrusted first device if the security request from the first device does not match an entry in the trust list of the trusted device database on the second device.

11. The apparatus according to claim 1, wherein, The second device is configured to compare account information on the target application of the first device with account information on the target application of the second device; The second device is configured to: allow an authentication input verification process if the account information on the target application of the first device matches the account information on the target application of the second device; and The second device is configured to generate an alert on the first device when the account information on the target application of the first device does not match the account information on the target application of the second device.

12. The apparatus according to claim 1, wherein, After logging into the target application on the first device, the first device is configured as follows: Determine whether the current account is the same as the account previously logged into the target application; and Send a notification to the second device associated with the account that was previously logged into the target application; The second device is configured to prompt one or more options, thereby allowing a user of the second device associated with the account previously logged into the target application to choose between logging out of the target application on the first device and remaining logged into the target application on the first device.

13. The apparatus according to claim 1, wherein, The first device includes a biometric identification service and a database containing biometric data of trusted individuals; The biometric identification service of the first device is configured to compare the user's biometric data with the biometric data of a trusted individual stored in the database. The second device is configured to: if the confidence level of the match between the user's biometric data and the biometric data of a trusted individual stored in the database exceeds a set threshold, then confirm that the current user is trustworthy and continue the login process.

14. The apparatus according to claim 1, wherein, The first device includes a multi-user database, which includes biometric data of each user and the IP address of the second device belonging to each user; The first device is configured to perform biometric identification on the user to determine whether the current user is the same as a previous user who previously logged into the target application; Specifically, when it is determined that the current user is not the same as the previous user who previously logged into the target application, the first device is configured to: log out of the account associated with the previous user who previously logged into the target application; and prompt the current user to re-authenticate using the verification process.

15. The apparatus according to claim 14, wherein, The first device is also configured to: Select the IP address associated with the account associated with the current user from the multi-user database; and The instruction is sent to the second device that has the IP address.

16. The apparatus according to claim 14, wherein, When it is determined that the current user is not the same as the previous user who previously logged into the target application, the first device is configured to: Send a notification to the second device associated with the account of the previous user who previously logged into the target application; as well as On the second device associated with the account associated with the current user, one or more options are presented to allow the current user to choose between a first option and a second option; When the first option is selected, the first device is configured to log out of all accounts associated with the current user on the first device; When the second option is selected, the first device is configured to allow the current user to continue using all applications on the first device.

17. The apparatus according to claim 1, wherein, The first device also includes a multi-user database; The multi-user database includes biometric data for each user and the IP address of the second device belonging to each user; The first device is configured as follows: Perform biometric identification on the user to determine whether the current user is the same as a previous user who previously logged into the target application; and When it is determined that the current user is not the same as the previous user who previously logged into the target application, a notification is sent to a second device associated with the account associated with the previous user who previously logged into the target application; Upon receiving the notification, the second device associated with the account associated with the current user is configured to prompt one or more options to allow the current user to choose between a first option and a second option. When the first option is selected, the first device is configured to log out of all accounts associated with the current user on the first device; and When the second option is selected, the first device is configured to allow the current user to continue using all applications on the first device.

18. The apparatus according to claim 1, wherein, The second device is configured as follows: When the one-click exit option is selected, an exit interface is generated on the second device to allow the user to exit each application; When an exit option is selected on the application's exit screen, an exit command is sent to the background service of the first device via a network connection; Upon receiving the exit command, the first device is configured to: Identify the application associated with the exit instruction; and Exit the application associated with the exit command.

19. A method for logging into a target application, comprising: The first device receives and decodes the authentication input used to log in to the target application; The method further includes, after the first device receives the instruction for decoding the authentication input used to log in to the target application: The first device obtains data containing the authentication input; the first device sends the data containing the authentication input to a second device communicating with the first device; the second device identifies the target application linked to the authentication input; or, The first device sends the instruction to the second device to decode the authentication input for logging into the target application; when the second device receives the instruction to decode the authentication input for logging into the target application, the first device displays the interface of the second device; The method further includes, after the second device identifies the target application linked to the authentication input, or after the first device displays the interface of the second device: The target application is launched by the second device; The authentication input is decoded by the second device; The second device sends a login confirmation command to the first device; The first device receives the login confirmation command; and The target application is logged in on the first device.

20. A computer program product comprising a non-transitory tangible computer-readable medium having computer-readable instructions thereon, the computer-readable instructions being executable by a processor to cause the processor to perform: The first device receives and decodes the authentication input used to log in to the target application, wherein... The first device communicates with the second device; Wherein, after the first device receives the instruction for decoding the authentication input used to log in to the target application, the computer-readable instruction may be executed by one or more processors to cause the one or more processors to perform further actions: The first device obtains data containing the authentication input; the first device sends the data containing the authentication input to the second device; the second device identifies the target application linked to the authentication input; or, The first device sends the instruction to the second device to decode the authentication input for logging into the target application; when the second device receives the instruction to decode the authentication input for logging into the target application, the first device displays the interface of the second device; Wherein, after the second device identifies the target application linked to the authentication input, or after the first device displays the interface of the second device, the computer-readable instructions may be executed by one or more processors to cause the one or more processors to perform further actions: The target application is launched by the second device; The authentication input is decoded by the second device; The second device sends a login confirmation command to the first device; The first device receives the login confirmation command; and The target application is logged in on the first device.

Images