Page display method, electronic device, and computer program product

Abstract

The present disclosure provides a page display method, an electronic device and a computer program product. The page display method of the present disclosure is applied to a second device, and the method comprises: parsing an address label contained in a field of view of the second device into an entry address, the address label being provided by a first device and recording an entry address of a target system; and sending the entry address to a third device, wherein the entry address is used to trigger the third device to send login credentials to the first device through the entry address.

Description

Technical Field

[0001] This disclosure relates to the technical fields of instant messaging, and more particularly to a page display method, electronic device, and computer program product. Background Technology

[0002] In business service scenarios, computers used to display service content or contracts to customers are often shared by multiple people, and business personnel need to scan a QR code to log in each time they use them. The current mainstream QR code login method relies on handheld devices, which involves cumbersome steps, takes a long time, and can easily interrupt the service process, resulting in an overall inefficient experience and making it difficult to meet the high-frequency, short-term login needs. Summary of the Invention

[0003] This disclosure provides a page display method, an electronic device, and a computer program product.

[0004] According to one aspect of this disclosure, a page display method is provided, applied to a second device, the method comprising: parsing an address label contained in the field of view of the second device into an entry address, the address label being provided by a first device and containing an entry address of a target system; and sending the entry address to a third device, wherein the entry address is used to trigger the third device to send login credentials to the first device through the entry address.

[0005] In some implementations, before resolving the address tags contained within the field of view into an entry address, the method includes: in response to receiving a voice command from a first subject regarding the address tags, sending the voice command to the third device, wherein the voice command is used to trigger the third device to compare the voiceprint features in the voice command with the voiceprint features of the account subject of the target account bound to the login credentials, and obtaining the authentication result of the first subject.

[0006] In some implementations, after sending the voice command to the third device, the method includes: in response to the authentication result being passed, determining the address tag within the field of view and resolving the address tag to the entry address.

[0007] In some embodiments, the second device is in the form of eyeglasses that can be worn by the first subject, and the second device has the same field of vision as the first subject after being worn by the first subject.

[0008] In some embodiments, the second device and the third device are the same device.

[0009] According to another aspect of this disclosure, a page display method is provided, applied to a first device, the method comprising: providing an address label, the address label recording an entry address of a target system; in response to receiving a login credential sent by a third device through the entry address, verifying the validity of the login credential, wherein the entry address is provided to the third device by a second device, the second device being a device whose field of view includes the address label, and the second device being capable of resolving the address label in the field of view to the entry address; and in response to the validity verification result being valid, displaying an accessible page of the target system.

[0010] In some implementations, after verifying the validity of the login credentials, the method further includes: in response to the invalidity of the validity verification result, sending a login failure alarm message to the third device, wherein the login failure alarm message is used to trigger the third device to generate a new login credential for the target system.

[0011] In some implementations, after sending a login failure alarm message to the third device, the process includes: monitoring for new login credentials sent by the third device through the entry address; and verifying the validity of the new login credentials after obtaining them.

[0012] In some implementations, in response to the validity verification result being valid, displaying the accessible page of the target system includes: determining the login status of the target account bound to the login credential from the login management platform of the third device, wherein in response to the validity verification result being valid, it can trigger the client running on the target system of the third device to log in to the target system, and write the login success status of the target account to the login management platform; and in response to the query finding that the login status of the target account is a successful login status, the first device jumps from the page displaying the address label to the page displaying the accessible page of the target system.

[0013] According to another aspect of this disclosure, a page display method is provided, applied to a third device, the method comprising: receiving an entry address provided by a second device, the second device being a device whose field of view includes an address tag provided by a first device, the second device being capable of resolving the address tag in the field of view into an entry address, the address tag recording the entry address of a target system; and sending login credentials applicable to the target system to the first device through the entry address, wherein the login credentials are used to trigger the first device to perform validity verification on the login credentials, and if the validity verification result is valid, displaying an accessible page of the target system on the first device.

[0014] In some implementations, the method further includes: after receiving a login failure alarm message from the first device, generating a new login credential for the target system, wherein the login failure alarm message is generated by the first device when the validity verification result is invalid.

[0015] In some implementations, generating new login credentials for the target system includes: a client of the target system running on the third device sending a credential request to a login management platform on the third device, the credential request containing the client's target account information; based on the credential request, the login management platform authenticating the target account information; and after successful authentication of the target account information, the login management platform providing the new login credentials to the client and configuring a validity period for the new login credentials, the new login credentials indicating that the target account described by the target account information has permission to log in to the target system during the validity period.

[0016] According to another aspect of this disclosure, an electronic device is provided, comprising: a memory storing execution instructions; and a processor executing the execution instructions stored in the memory, causing the processor to perform a page display method according to any embodiment of this disclosure.

[0017] According to another aspect of this disclosure, a readable storage medium is provided that stores executable instructions, which, when executed by a processor, implement the page display method described in any embodiment of this disclosure.

[0018] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the page display method described in any embodiment of this disclosure. Attached Figure Description

[0019] The accompanying drawings illustrate exemplary embodiments of the present disclosure and, together with the description thereof, serve to explain the principles of the present disclosure. These drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification.

[0020] Figure 1 This is a flowchart of a page display method according to an embodiment of the present disclosure.

[0021] Figure 2 This is a flowchart of multi-terminal interaction according to the embodiments of this disclosure.

[0022] Figure 3This is a flowchart of another page display method according to an embodiment of the present disclosure.

[0023] Figure 4 This is a flowchart of the login failure handling process according to the embodiments of this disclosure.

[0024] Figure 5 This is a flowchart of another page display method according to an embodiment of the present disclosure.

[0025] Figure 6 This is a schematic block diagram of the structure of a page display device according to an embodiment of the present disclosure.

[0026] Figure 7 This is a block diagram illustrating the structure of an electronic device according to one embodiment of the present disclosure. Detailed Implementation

[0027] The present disclosure will now be described in further detail with reference to the accompanying drawings and examples. It should be understood that the specific examples described herein are for illustrative purposes only and are not intended to limit the scope of the disclosure. Furthermore, it should be noted that, for ease of description, only the parts relevant to the present disclosure are shown in the accompanying drawings.

[0028] It should be noted that, where there is no conflict, the embodiments and features described in this disclosure can be combined with each other. The technical solutions of this disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0029] In face-to-face business service scenarios such as real estate brokerage and financial services, sales personnel often need to use shared computers to present key information to clients in real time. For example, when real estate agents show properties to clients, they access property details, floor plans, price comparisons, or electronic contracts through shared devices in the store or showroom. Currently, these devices generally use a QR code login mechanism: each salesperson must take out their personal mobile phone, open the business service system client, and scan the QR code on the screen to complete identity authentication before each use. This process seems secure, but in reality, it is cumbersome and time-consuming, especially in the on-site environment where clients are waiting. Frequent scanning can easily disrupt the communication rhythm and lengthen the service chain. Obviously, for high-frequency, short-duration interaction scenarios (such as multiple viewings within a day, multiple people taking turns using the same device), the existing login method not only reduces work efficiency but also weakens the professional and smooth service experience, making it difficult to meet the needs of efficient and seamless business collaboration.

[0030] Therefore, this disclosure proposes a page display method.

[0031] In one embodiment of this solution, the page display method operates primarily on the first device and relies on the visual perception capabilities of the second device to trigger the process, achieving seamless and efficient shared device login and page display. The first device is a terminal capable of running the target system and supporting sharing by multiple business personnel, such as a desktop computer.

[0032] Figure 1 This is a flowchart of a page display method according to an embodiment of the present disclosure. Figure 1 As shown, this disclosure provides a page display method M100, which introduces a second device, such as AI (Artificial Intelligence) glasses, that is synchronized with the field of vision of business personnel. The device automatically identifies the address label on the first device and triggers a seamless login process, enabling business personnel to quickly and seamlessly access the target system without manual operation, significantly improving service efficiency and experience.

[0033] Step S110: Provide address labels.

[0034] The address tag, provided by the first device, records the entry address of the target system. It can take the form of a QR code, barcode, or other machine-readable visual identifier. In practice, this address tag is typically displayed graphically on the screen of the first device or affixed to its body, allowing the primary user (usually a business person) wearing AI glasses or other second devices to naturally capture it within their normal line of sight. The entry address carried by the address tag serves as the unique guiding path to the target system, ensuring not only secure routing of the login process but also providing a crucial trigger for subsequent seamless authentication mechanisms based on field-of-view awareness.

[0035] The target system refers to the business service platform that the primary entity needs to access and operate, typically carrying specific business functions and data services. In the context of this disclosure, the target system could be a property management system used by a real estate agency, a policy configuration tool displayed by an insurance consultant, or other internal business applications facing customers. The target system requires the primary entity to complete identity authentication before accessing its functional pages or data. The identity authentication process will be described later and will not be elaborated here.

[0036] The first type of equipment refers to shared terminal devices deployed at service sites to display business content and run target systems. Examples include fixed or semi-fixed devices such as desktop computers and touchscreens in stores or reception areas. This equipment is not tied to a specific user but is used in rotation by multiple business personnel in different service scenarios.

[0037] Step S120: In response to receiving the login credentials sent by the third device through the entry address, verify the validity of the login credentials.

[0038] The third device is typically a mobile terminal owned by a business personnel, such as a smartphone or tablet, which has the target system's client and login management platform installed on it. As the core carrier of identity authentication, the third device supports various local verification methods, such as entering an account password, fingerprint recognition, and facial recognition, with the business personnel initiating a login request on the client. Specifically, when the identity information provided by the business personnel matches the pre-stored identity information for the target account on the login management platform, it indicates that the business personnel are the legitimate owner of the target account (i.e., the account holder), and a login credential is returned to the client.

[0039] The login credentials not only represent that the account holder has completed identity verification on the login management platform, but can also be used for subsequent secure authorization across devices. In this solution, the third device will push this login credential to the first device through a secure channel via the entry address parsed by the second device, thereby achieving a seamless login experience without having to repeatedly enter account information, balancing security and operational efficiency.

[0040] Login credentials are temporary, secure identity tokens issued by the target system after a user has completed identity verification. These tokens, such as access tokens or session tokens, prove that the user has been properly authenticated and has the right to access the target system. Login credentials are typically generated by the login management platform and contain information such as the account holder's identifier, the scope of permissions to the target system, and the validity period. They are transmitted and stored in encrypted form to avoid repeatedly entering usernames and passwords.

[0041] It should be noted that the entry address obtained by the third device is provided by the second device, which is a device whose field of view contains address tags and can resolve the address tags in the field of view into an entry address. The second device can be a device with visual recognition capabilities, such as AI glasses or a camera, and there are no restrictions here.

[0042] Furthermore, the validity verification process is performed by the first device. The purpose of validity verification is to confirm whether the received login credentials currently have legitimate permissions to access the target system. Specifically, the first device parses the metadata (such as the validity period) contained in the login credentials and then verifies whether the current time is within the validity period.

[0043] In some implementations, the first device can also verify the legitimacy of the login credential issuer (e.g., a login management platform), the validity of the digital signature, and whether it has been revoked in advance, among other security attributes.

[0044] In step S130, in response to the validity verification result being valid, the accessible page of the target system is displayed.

[0045] Specifically, if the login credentials are still valid within the validity period, the validity verification result is determined to be valid, and the first device immediately authorizes the loading of the accessible page of the target system; otherwise, access is denied and a login failure alarm message is sent to the second device.

[0046] In some implementations, if the current time is within the valid period of the login credentials and they have not been tampered with (i.e., the digital signature of the login credentials is valid), the first device displays an accessible page of the target system. This mechanism ensures that even if the login credentials are intercepted during transmission, they cannot be misused after expiration, thereby improving convenience while ensuring system security.

[0047] An accessible page refers to the user interface or information content that a first device loads from the target system and presents to the first user after the login credentials have been verified, based on the user's authorized identity and permissions. These pages typically contain functional modules or data resources related to the current service scenario, such as property details pages and contract signing interfaces in a real estate agency scenario, or policy configuration tools used by insurance advisors. Furthermore, accessible pages are interactive, capable of responding to the first user's clicks, swipes, and inputs, switching content in real time, submitting requests, or calling backend services, thereby supporting a complete and seamless customer service process.

[0048] The target system is the core platform that carries specific business functions and data services; while the first device is a shared terminal that runs the front-end interface of the target system, serving as the display window and interactive terminal of the target system. The first device itself does not store business logic, but rather acts as the entry point for users to access the target system. It can receive and verify login credentials pushed by the third device, and after confirming the legitimacy of the user's identity, it sends a request to the target system and renders the accessible pages within its authorized scope, thereby presenting the service capabilities of the target system to business personnel and customers in real time and securely.

[0049] Figure 2 This is a multi-terminal interaction flowchart according to an embodiment of the present disclosure. The display of accessible pages in the target system depends on the collaborative information interaction and functional division between the first device, the second device, and the third device, which will be discussed in conjunction with the following. Figure 2 This document details the collaborative process of the three terminals in terms of timing, and fully presents the implementation process of the page display method described in this disclosure.

[0050] In step 201, the third device obtains login credentials.

[0051] The third device deploys two core components: a client application for the target system and a unified login management platform. Before using the first device, the first entity must first authenticate its identity with the target system on its third device via the client application—for example, by entering an account and password, or performing facial recognition or fingerprint verification. Upon receiving the authentication request, the login management platform verifies whether the provided credentials match the bound target account. If the verification is successful, the first entity is deemed to have legitimate access rights, and a temporary, encrypted login credential is generated accordingly. This login credential not only includes the user's identity and scope of permissions but also has a clearly defined validity period to ensure security. This credential will be used in subsequent seamless cross-device login processes, providing a trusted identity basis for the first device to access the target system.

[0052] In step 202, an address label is displayed on the first device.

[0053] Address tags are used to record the entry address of the target system. The entry address is a network address used to uniquely identify and locate a specific login or service entry point in the target system. Its core function is to provide routing guidance for the secure transmission and accurate delivery of login credentials.

[0054] It should be noted that the form of the address label is not limited. It can be a graphic encoding such as a QR code or barcode, or the entry address can be displayed directly in plain text (such as a complete address string). Any form that is easy for a second device to automatically parse through visual recognition falls within the protection scope of this disclosure.

[0055] Furthermore, when the first subject (i.e., the wearer of the second device) wants to log in to the target system, they can issue commands to the second device via voice. These voice commands not only contain explicit tasks to be performed, such as "log in to the target system," but also implicitly include the first subject's voiceprint characteristics, which can serve as biometric information to aid in identity verification.

[0056] After receiving the voice input, the second device uses its built-in voice recognition module to parse the semantic content of the instruction. If it determines that the task to be executed is a login task for the target system, it confirms that the current scenario meets the conditions for triggering contactless login. Then, the second device executes step 203 and sends the voice instruction to the third device.

[0057] It should be noted that the first entity is not necessarily the same as the account holder of the target account bound to the login credentials. In other words, the person wearing the second device and initiating the voice command may not be the actual authorized user corresponding to the login credentials. Therefore, the third device needs to perform step 204 to analyze the voiceprint features carried in the voice command to determine the identity verification result of the first entity.

[0058] Specifically, the voiceprint characteristics corresponding to the voice command are matched with the voiceprint characteristics of the account holder pre-recorded during the registration of the target account. When the two match, the identity verification result for the first entity is determined to be successful; otherwise, it proves that the first entity does not have the authority to call the second device to parse the address tag, nor does it have the authority to trigger other subsequent steps to display the accessible page. This mechanism effectively prevents credentials from being misused by others and improves the security and reliability of seamless login across devices.

[0059] Further, in step 205, in response to the authentication result being successful, the second device parses the address label.

[0060] The process by which the second device resolves the address tag into an entry address is essentially an intelligent recognition and semantic understanding of visual input information. As a wearable terminal with artificial intelligence capabilities, the second device has built-in computer vision and multimodal perception modules, enabling it to capture image content within its field of view in real time and process it through local or cloud-based AI models.

[0061] Specifically, the system utilizes image recognition technology built into the second device to locate and extract address tag regions, then obtains the original string through decoding algorithms or optical character recognition. To further enhance robustness and contextual understanding, large language models or multimodal models can be introduced to perform semantic verification and format normalization on the extracted content. For example, this involves determining whether the identified content is a valid entry address, completing missing protocol headers (such as automatically adding "https: / / "), or filtering out interference information. Ultimately, the second device outputs a structured entry address that can be directly used for network communication, providing accurate routing for subsequent login credential delivery. This AI-based parsing mechanism not only supports diverse tag formats but also maintains high recognition accuracy in real-world scenarios with complex lighting, tilted angles, or partial occlusion, making it a key technological element for achieving seamless login through "eye contact interaction."

[0062] Further, the second device executes step 206, sending the parsed entry address of the target system to the third device.

[0063] In step 207, the third device sends login credentials to the first device via the entry address.

[0064] Next, step 208 is executed, where the first device verifies the validity of the login credential. This verification process mainly includes: parsing the metadata in the login credential and checking whether the current time is within a preset valid time period. If the current time is within a valid time period, the first device determines that the login credential is valid; otherwise, it determines that the login credential is invalid.

[0065] Further, step 209 is executed, whereby the third device determines whether the first device's verification result of the login credentials is valid.

[0066] When the validity verification is successful, the client running on the target system on the third device can be triggered to log in to the target system, and the successful login status of the target account will be written to the login management platform. Conversely, if the verification fails, the client on the third device will not be able to log in to the target system, and therefore the login management platform will not record the successful login status.

[0067] It should be noted that although the client on the third device has logged into the target system via normal login in step 201, the first entity may not have continuously accessed the system through the third device. During this period, the target system may set the user's status to offline due to session timeout, security policies, or prolonged inactivity, at which point the login status recorded in the login management platform will be set to offline. Therefore, before logging into the target system across devices, the client will log back in and update the current login status on the login management platform.

[0068] Furthermore, in response to the query finding that the login status of the target account is successful, step 210 is executed, and the first device is redirected from the page displaying the address label to the page displaying the accessible page of the target system.

[0069] In some implementations, if the first device verifies the validity of the login credentials as invalid, the first device will send a login failure alarm message to the third device. This login failure alarm message is used to trigger the third device to execute step 211, generating new login credentials for the target system.

[0070] It should be noted that the new login credentials are reissued login credentials with a new validity period. The new login credentials indicate that the account holder of the target account can access the target system during the valid period.

[0071] Obtaining new login credentials does not require the primary user to log in to the target system again via normal login. In fact, the client on the target system in the third device can proactively initiate a credential refresh request to the login management platform; after verifying that the current user session is still in a trusted state, the login management platform will directly return a new, valid login credential. This credential acquisition process is automatically completed by the client in the background, transparent to the user, thus avoiding service interruption. Specific implementation details will be described below and will not be elaborated here.

[0072] Furthermore, the first device listens for new login credentials sent by the third device through the entry address; after obtaining the new login credentials, it verifies their validity. That is, after obtaining the new login credentials, steps 208 to 209 need to be executed again until the first device verifies the validity of the new login credentials and displays the accessible page of the target system on the first device.

[0073] Clearly, this solution not only establishes an automatic handling mechanism for invalid or expired login credentials, but also achieves a seamless login experience for the primary user on the shared terminal through silent background refresh and cross-device collaborative verification.

[0074] In another embodiment of this solution, the page display method operates primarily on a third device and relies on the visual perception capabilities of the second device to trigger the process, achieving seamless and efficient shared device login and page display. The third device is a terminal capable of running a client of the target system, which can be a non-shared device such as the first device's mobile phone, computer, or tablet, and the third device has components such as a client and a login management platform.

[0075] Figure 3 This is a flowchart of another page display method according to an embodiment of the present disclosure. For example... Figure 3 As shown, the page display method M300 applied to a third device is illustrated.

[0076] Step S310: Receive the entry address provided by the second device.

[0077] The second device is a device whose field of view contains the address tags provided by the first device. The second device can resolve the address tags in the field of view into entry addresses. The address tags record the entry address of the target system.

[0078] In step S320, the login credentials applicable to the target system are sent to the first device via the entry address.

[0079] The login credentials are used to trigger the first device to verify the validity of the login credentials, and if the verification result is valid, the first device displays the accessible page of the target system.

[0080] After receiving the login failure alarm from the first device, the third device will generate a new login credential for the target system. The login failure alarm is generated by the first device when the validity verification result is invalid.

[0081] Figure 4 This is a flowchart of the login failure handling process according to an embodiment of this disclosure. Figure 4 The image shows the specific process for handling login failures.

[0082] In step 401, the client sends a credential request to the login management platform.

[0083] The credential request is initiated by the client on the third device and includes target account information to support the login management platform in accurately determining the legitimacy of the request. Specifically, the target account information includes not only the target account to be logged into on the first device, but also the identity characteristics of the account holder bound to that account. These identity characteristics are crucial for verifying whether the current operator is a legitimate and authorized user, and may include the account holder's location information (such as their organization or region), account password, and pre-stored biometric templates (such as facial feature vectors and fingerprint data). By submitting these multi-dimensional identity elements together, the login management platform can efficiently and securely complete identity verification without relying on explicit user interaction, and issue new login credentials accordingly, providing reliable support for seamless login.

[0084] The login management platform can be a system-level or application-level component deployed locally on the third-party device; alternatively, it can be deployed on a remote server, receiving credential requests from the third-party device, authenticating them, and returning login credentials to the client of the third-party device upon successful authentication. There are no restrictions on the specific form of the login management platform, but it can be used to uniformly manage and coordinate the identity authentication and session state of all installed applications on the device. It not only serves the client of the target system but may also integrate or associate login information from other business-related applications on the third-party device. When any application needs to authenticate or refresh credentials, the login management platform can quickly complete authentication based on locally stored account information and biometric templates, and generate or update unique login credentials for the corresponding application.

[0085] In this solution, if the login management platform does not belong to a third device, the client of the target system can securely obtain valid login credentials without requiring the user to repeatedly enter the password by calling the capabilities of the local login management platform. This supports the subsequent push of credentials to the first device and the realization of a seamless login process.

[0086] In step 402, the login management platform verifies the identity of the target account information in the credential request.

[0087] During the identity verification process, the login management platform verifies whether the target account has been registered and bound to a third-party device, whether the third-party device's environment is within the geographical scope specified by the local information, and the time of the target account's last login to the target system. For example, if the target account is bound to the Beijing area and the third-party device is also located in Beijing, and the last active operation was less than 30 minutes ago, the current environment can be determined to be highly trustworthy. A new login credential can be issued directly without requiring the user to re-enter their password or perform biometric authentication, thus achieving a truly smooth and seamless cross-device login experience while ensuring compliance with security policies. Conversely, if the third-party device has not logged into the target system through normal login methods for a period of time, such as not logging in with an account and password within a year, the credential will not be issued. This localized verification mechanism ensures security while avoiding frequent calls to remote servers, laying the foundation for efficient and seamless credential acquisition.

[0088] Further, in step 403, the login management platform determines whether the verification is successful. In response to successful verification, in step 404, the login management platform provides a new login credential to the client.

[0089] It should be noted that when generating login credentials, the login management platform configures a validity period for those credentials. Therefore, the login management platform also configures a validity period for new login credentials, and the new login credential indicates that the target account described by the target account information has the permission to log in to the target system during the validity period.

[0090] Furthermore, the client provides the new login credentials to the first device for permission verification.

[0091] This implementation method is completely consistent with the first implementation method in terms of overall processing logic, interaction flow and technical effect. The only difference is in the deployment location of the execution subject. Therefore, the same parts can be referred to the detailed description of the first implementation method above.

[0092] In another embodiment of this solution, the page display method operates primarily on a second device. This second device possesses visual perception capabilities to trigger the process, enabling the first entity to seamlessly and efficiently log in to the shared device and display the page. The second device is a device that can be worn by the first entity and shares its field of vision with it, such as AI glasses or a head-mounted camera, etc., which will not be listed here.

[0093] Figure 5 This is a flowchart of another page display method according to an embodiment of the present disclosure. For example... Figure 5 As shown, the page display method M500 applied to the second device is illustrated.

[0094] Step S510: The address tags contained within the field of view are parsed into entry addresses. The address tags are provided by the first device and contain the entry address of the target system.

[0095] Step S520: Send the entry address to the third device. The entry address triggers the third device to send login credentials to the first device. The login credentials trigger the first device to verify their validity. If the verification is successful, the first device displays the accessible page of the target system.

[0096] In some implementations, before resolving the address tags contained in the field of view into an entry address, the process includes: a second device responding to receiving a voice command from the first subject regarding the address tags, sending the voice command to a third device, the voice command being used to trigger the third device to compare the voiceprint features in the voice command with the voiceprint features of the account subject of the target account bound to the login credentials, and obtaining the authentication result of the first subject.

[0097] For example, when a first entity issues a voice command, a second device first identifies the task semantics within the command. If the task is to log in to the target system, the second device forwards the voice command (or at least voice data containing voiceprint features) to a paired (e.g., Bluetooth pairing) third device. Upon receiving the command, the third device retrieves locally stored account information and compares the voiceprint features in the voice with the pre-registered voiceprint features of the target account linked to the login credentials, thus verifying the first entity's identity. Only when the voiceprint matches and identity verification is successful is the subsequent process allowed to continue. This design places identity verification at the initial interaction stage, enhancing security and ensuring that subsequent automated processes are only activated when initiated by a legitimate user, preventing invalid or malicious triggering.

[0098] It's important to note that in real-world scenarios, multiple address tags may exist around the first device or within the field of view of the second device (e.g., multiple shared terminals simultaneously displaying their respective QR codes). In such cases, visual recognition alone is insufficient to automatically determine which device the user intends to log in to. However, by introducing a voice command mechanism, the user can naturally point to their current target when issuing a login request—for example, saying "Log in to the computer with ID 001" or "Log in to the computer closest to me." Upon receiving this voice command, the second device not only extracts the voiceprint for authentication but also combines the user's gaze focus, spatial location, and contextual semantics at the moment the voice command is issued to associate and match the command with multiple address tags in its field of view, thereby uniquely identifying the specific address tag the user is referring to. This mechanism effectively solves the ambiguity problem in scenarios with multiple coexisting tags, ensuring that the parsing of the entry address accurately corresponds to the user's true intent, further improving the accuracy and robustness of seamless login.

[0099] Furthermore, after sending the voice command to the third device, the method also includes: in response to the successful authentication result, determining the address label within the field of view and resolving the address label into an entry address, wherein in response to the successful authentication result, the first subject is the account subject.

[0100] In some embodiments, the second device is in the form of glasses that can be worn by the first subject, and the second device has the same field of vision as the first subject after being worn by the first subject.

[0101] In some implementations, the second device and the third device are the same device.

[0102] When the second device (such as AI glasses) lacks network connectivity, authentication capabilities, or standard login functionality, it typically needs to pair with a third device (such as a smartphone) via short-range communication methods like Bluetooth. The third device then handles tasks such as credential acquisition and authentication. However, if the second device itself integrates complete network connectivity, authentication, and login management capabilities (i.e., possessing the core functions of a traditional third device), then logically, the second and third devices can be combined into one, with the same physical device simultaneously handling both visual perception and authentication processing. In this case, the device still needs to meet specific form requirements: it must be a wearable smart terminal (such as AI glasses or a head-mounted camera), and its field of view must match that of the first device to ensure automatic address tag capture and seamless triggering of the interaction process.

[0103] Figure 6 This is a schematic block diagram of the structure of a page display device according to an embodiment of the present disclosure. For example... Figure 6 As shown, this disclosure proposes a page display device 600, including a page providing module 610 and a credential processing module 620.

[0104] In one implementation, the page providing module 610 provides an address tag that records the entry address of the target system; the credential processing module 620, in response to receiving a login credential sent by a third device through the entry address, verifies the validity of the login credential, wherein the entry address is provided to the third device by a second device, the second device being a device whose field of view contains the address tag, and the second device being able to parse the address tag in its field of view into an entry address; and in response to the validity verification result being valid, the page providing module 610 displays the accessible pages of the target system.

[0105] In another embodiment, the credential processing module 620 is used to receive an entry address provided by a second device, the second device being a device whose field of view includes an address tag provided by the first device, the second device being able to parse the address tag in its field of view into an entry address, the address tag recording the entry address of the target system; and the credential processing module 620 is also used to send login credentials applicable to the target system to the first device through the entry address, wherein the login credentials are used to trigger the first device to perform validity verification on the login credentials, and if the validity verification result is valid, to display the accessible page of the target system on the first device.

[0106] In another embodiment, the credential processing module 620 is used to parse the address tags contained in the field of view into entry addresses. The address tags are provided by the first device and record the entry address of the target system. The credential processing module 620 is also used to send the entry address to a third device. The entry address is used to trigger the third device to send login credentials to the first device through the entry address. The login credentials are used to trigger the first device to verify the validity of the login credentials. If the validity verification result is valid, the first device displays the accessible page of the target system on the first device.

[0107] The page display device 600 disclosed herein can be in the form of computer software, and the various modules of the page display device 600 can be in the form of computer software modules.

[0108] The various modules of the page display device 600 disclosed herein are set up to implement the various steps of the page display device. Their execution principles and steps can be referred to the above text and will not be repeated here.

[0109] Figure 7 This is a schematic block diagram of an electronic device according to one embodiment of the present disclosure. Figure 7As shown, this disclosure also provides an electronic device 1000, including: a processor 1200 and a memory 1300, the memory 1300 storing execution instructions; the processor 1200 executes the execution instructions stored in the memory 1300, causing the processor 1200 to execute a page display device.

[0110] The hardware architecture of the electronic device 1000 can be implemented using a bus architecture. The bus architecture can include any number of interconnect buses and bridges, depending on the specific application of the hardware and overall design constraints. Bus 1100 connects various circuits, including one or more processors 1200, memory 1300, and / or hardware modules. Bus 1100 can also connect various other circuits 1400, such as peripheral devices, voltage regulators, power management circuits, external antennas, etc.

[0111] Bus 1100 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, this diagram uses only one connection line, but this does not imply that there is only one bus or one type of bus.

[0112] This disclosure also provides a readable storage medium storing a computer program that, when executed by a processor, is used to implement the methods described above. A "readable storage medium" can be any means capable of containing, storing, communicating, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, apparatus, or device. More specific examples of a readable storage medium include: an electrical connection with one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and portable read-only memory (CDROM), etc.

[0113] This disclosure also provides a computer program product, the methods of which can be implemented wholly or partially through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented wholly or partially as a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed, all or part of the processes or functions of this disclosure are performed.

[0114] Computer programs or instructions can be stored in a readable storage medium or transferred from one readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The readable storage medium can be any available medium capable of access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video optical disc; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or it can include both volatile and non-volatile types of storage media.

[0115] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, electronic devices, readable storage media, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0116] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0117] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0118] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0119] In the description of this specification, the references to terms such as "one embodiment / mode," "some embodiments / modes," "example," "specific example," or "some examples," etc., refer to specific features, structures, or characteristics described in connection with that embodiment / mode or example, which are included in at least one embodiment / mode or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment / mode or example. Moreover, the specific features, structures, or characteristics described may be combined in any suitable manner in one or more embodiments / modes or examples. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments / modes or examples described in this specification, as well as the features of different embodiments / modes or examples.

[0120] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

Claims

1. A page display method, characterized in that, Applied to a second device, the method includes: The address tags contained in the field of view of the second device are parsed into entry addresses, and the address tags are provided by the first device and contain the entry address of the target system; The entry address is sent to a third device, wherein the entry address is used to trigger the third device to send login credentials to the first device through the entry address.

2. The page display method according to claim 1, characterized in that, Before resolving the address labels contained within the field of view into entry addresses, the following is included: In response to receiving a voice command from the first subject regarding the address tag, the voice command is sent to the third device. The voice command is used to trigger the third device to compare the voiceprint features in the voice command with the voiceprint features of the account subject of the target account bound to the login credential, and obtain the authentication result of the first subject.

3. The page display method according to claim 2, characterized in that, After sending the voice command to the third device, the process includes: In response to the authentication result being successful, the address label is determined within the field of view, and the address label is parsed into the entry address.

4. The page display method according to any one of claims 1 to 3, characterized in that, The second device is in the form of glasses that can be worn by the first subject. After being worn by the first subject, the second device has the same field of vision as the first subject.

5. A page display method, characterized in that, Applied to a first device, the method includes: Provide an address label, which records the entry address of the target system; In response to receiving login credentials sent by the third device via the entry address, the validity of the login credentials is verified, wherein the entry address is provided to the third device by a second device, the second device being a device whose field of view includes the address tag, and the second device being capable of resolving the address tag within its field of view into the entry address; and If the validity verification result is valid, the accessible page of the target system is displayed.

6. The page display method according to claim 5, characterized in that, After verifying the validity of the login credentials, the process also includes: In response to the invalidity of the validity verification result, a login failure alarm message is sent to the third device, wherein the login failure alarm message is used to trigger the third device to generate a new login credential for the target system.

7. The page display method according to claim 6, characterized in that, In response to the validity verification result being valid, the accessible pages of the target system are displayed, including: The login status of the target account bound to the login credential is determined from the login management platform of the third device, wherein, in response to the validity verification result being valid, a client running on the target system of the third device can be triggered to log in to the target system, and the successful login status of the target account is written to the login management platform; and In response to the query finding that the login status of the target account is successful, the first device is redirected from the page displaying the address label to the accessible page displaying the target system.

8. A page display method, characterized in that, Applied to a third device, the method includes: The system receives an entry address provided by a second device, which is a device whose field of view includes an address tag provided by a first device. The second device is capable of resolving the address tag within its field of view into an entry address, and the address tag records the entry address of the target system. The login credentials applicable to the target system are sent to the first device through the entry address, wherein the login credentials are used to trigger the first device to verify the validity of the login credentials, and if the validity verification result is valid, the accessible page of the target system is displayed on the first device.

9. An electronic device, characterized in that, include: The memory stores execution instructions; as well as A processor that executes execution instructions stored in the memory, causing the processor to perform the page display method according to any one of claims 1 to 8.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it performs the page display method according to any one of claims 1 to 8.

Images