Page jumping method and electronic equipment

Abstract

The invention provides a page jumping method and electronic equipment. The method comprises the steps that in response to receiving of a first message, a first notification control is displayed on a first page, at least one first button is displayed on the first notification control, the first message comprises a first link used for entering a target application program, and the first notification control is used for notifying a user that the first message is currently received; and in response to a first operation on the first button, jumping from the first page to a target page associated with the first link, the target page being an application page of the target application. According to the scheme provided by the embodiment of the invention, the electronic equipment can quickly jump to the target page of the target application program from the first page without depending on the access of a third-party application program, so that the page jump process is optimized, and the use experience of a user is improved.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a page navigation method and an electronic device. Background Technology

[0002] Based on the messaging capabilities of electronic devices, users can share content to meet their interaction needs.

[0003] When User A's sending electronic device sends a message containing a link to User B's receiving electronic device, the receiving electronic device typically displays a message notification control on its notification center page. User B needs to click this notification control to have the message displayed in a third-party application on the receiving electronic device. Furthermore, User B needs to click the link within the message to allow the receiving electronic device to access the target application linked from the third-party application. This process involves multiple clicks by User B and multiple page jumps on the receiving electronic device, making the process cumbersome and negatively impacting the user experience. Summary of the Invention

[0004] This application provides a page navigation method and an electronic device that enables the electronic device to quickly navigate from a first page to the target page of a target application without relying on the access of a third-party application, thus optimizing the page navigation process and improving the user experience.

[0005] In a first aspect, embodiments of this application provide a page navigation method applied to a first electronic device, comprising: in response to receiving a first message, displaying a first notification control on a first page and displaying a first button on the first notification control, wherein the first message includes a first link for entering a target application, and the first notification control is used to notify the user that the first message has been received; in response to a first operation on the first button, navigating from the first page to a target page associated with the first link, the target page being the application page of the target application.

[0006] The page jump method provided in this application embodiment allows a first electronic device to display a first button in a first notification control corresponding to the first message after receiving a first message containing a first link. In this way, after the user clicks the first button, the first electronic device can quickly jump from the first page to the target page of the target application without relying on the access of a third-party application, thus optimizing the page jump process and improving the user experience.

[0007] In one implementation, in response to receiving a first message, a first notification control is displayed on a first page, and at least one first button is displayed on the first notification control. This includes: in response to receiving a first message sent by a first application in a second electronic device, displaying a first notification control corresponding to the first application in the first electronic device on the first page, and displaying a first button on the first notification control, wherein the second electronic device is the peer device of the first electronic device. Using this implementation, this application can be applied to scenarios where different senders send a first message with a first link. The sender may be, for example, the first application in the second electronic device. Thus, this application can optimize page navigation processes in various scenarios, improving the user experience.

[0008] In one implementation, in response to receiving a first message, a first notification control is displayed on a first page, and at least one first button is displayed on the first notification control. This includes: in response to receiving a first message sent by a file-sharing function in a second electronic device, displaying a first notification control corresponding to the file-sharing function in the first electronic device on the first page, and displaying a first button on the first notification control. The second electronic device is the peer device of the first electronic device, and the file-sharing function is a built-in function of the electronic device. Using this implementation, this application can be applied to scenarios where different senders send a first message with a first link. For example, the sender could be the file-sharing function in a second electronic device. Thus, this application can optimize page navigation processes in various scenarios, improving the user experience.

[0009] In one implementation, in response to receiving a first message, a first notification control is displayed on a first page, and a first button is displayed on the first notification control. This includes: displaying the first notification control on the first page in response to receiving the first message; parsing the first message to determine whether the first electronic device has a target application set; and updating the first notification control to display the first button if the first electronic device has a target application set. This implementation demonstrates a specific display method for the first button. Thus, after the user clicks the first button, the first electronic device can quickly jump from the first page to the target page of the target application without relying on the access of a third-party application, optimizing the page jump process and improving the user experience.

[0010] In one implementation, parsing the first message to determine whether the first electronic device has a target application configured includes: parsing the first message to obtain the first packet name corresponding to the first message and the text information of the first link, wherein the first packet name is the packet name of the sender of the first message, and the sender includes the target application in the second electronic device, or the file sharing function in the second electronic device; and determining whether the first electronic device has a target application configured based on the first packet name and / or the text information. By using this implementation, detecting the target application in the first electronic device ensures that the first electronic device can quickly jump from the first page to the target page of the target application. This ensures the feasibility of this application.

[0011] In one implementation, determining whether a first electronic device has a target application set up based on a first package name and / or text information includes: determining the link type of a first link based on the text information, wherein the link type includes at least one of a card link, a password link, a Uniform Resource Locator (URL) link, and a share link corresponding to a file sharing function; determining the target application based on the link type and the first package name, and detecting whether the first electronic device has the target application set up. This implementation can identify different link forms of the first link, providing different page redirection methods for different links. Thus, this application can optimize the page redirection process in various scenarios, improving the user experience.

[0012] In one implementation, in response to receiving a first message, displaying a first notification control on a first page includes: in response to the Notification Management Service (NMS) receiving the first message, the NMS determining the properties of the first notification control corresponding to the first message; and the NMS displaying the first notification control on the first page based on the properties of the first notification control. This implementation illustrates a specific display method for the first notification control.

[0013] In one implementation, the first message is parsed to obtain the first packet name corresponding to the first message and the text information of the first link. This includes: NMS parsing the first message to obtain the first packet name and text information; and notifying the application to obtain the first packet name and text information based on its listening relationship with NMS. This implementation illustrates the specific display method of the first packet name and text information.

[0014] In one implementation, determining the link type of the first link based on text information includes: notifying the application to determine the link type based on the text information. This implementation can identify different link formats of the first link, allowing for different page redirection methods for different links. Thus, this application can optimize the page redirection process in various scenarios, improving the user experience.

[0015] In one implementation, determining the target application based on the link type and the first package name includes: if the link type is a card link, URL link, or share link, obtaining the target simulated click path corresponding to the first package name, wherein the target simulated click path is pre-stored in the first electronic device; after obtaining the target simulated click path, creating a virtual screen; performing a simulated click operation on the virtual screen based on the target simulated click path to display the target page on the virtual screen; and obtaining the page information of the target page to determine the target application based on the page information. This implementation demonstrates a method for determining the target application, enabling subsequent detection of the target application in the first electronic device. This ensures that the first electronic device supports quick navigation from the first page to the target page of the target application, guaranteeing the feasibility of this application.

[0016] In one implementation, after creating the virtual screen, the method further includes obtaining a first screen identifier for the virtual screen, wherein each screen has a corresponding screen identifier. Using this implementation, screen switching can be performed based on the first screen identifier, allowing the target page displayed on the virtual screen to quickly switch to the page displayed on the physical screen. This ensures that the first electronic device can quickly jump from the first page to the target page of the target application, guaranteeing the feasibility of this application.

[0017] In one implementation, responding to a first operation on a first button, navigating from a first page to a target page associated with a first link includes: responding to the first operation on the first button by switching a first screen identifier to a second screen identifier, thereby causing the display screen to switch from displaying the first page to displaying the target page, wherein the display screen corresponds to the second screen identifier. This implementation illustrates a specific method of screen switching.

[0018] In one implementation, determining the target application based on the link type and the first package name, and detecting whether the first electronic device has the target application set, includes: when the link type is a card link, URL link, or share link, notifying the application to obtain the target simulated click path corresponding to the first package name; notifying the application to send the target simulated click path to the simulated click application; after receiving the target simulated click path, the simulated click application sends a first instruction to the Display Management Service (DMS); the DMS responds to the first instruction by creating a virtual screen; the simulated click application performs a simulated click operation on the virtual screen based on the target simulated click path, so that the DMS displays the target page on the virtual screen; the Accessibility Service (AS) obtains the target page based on the listening relationship with the DMS, performs content analysis processing on the target page to obtain page information, and sends the page information to the DMS; notifying the application to obtain the page information from the DMS; notifying the application to determine the target application based on the page information, and detecting whether the first electronic device has the target application set. This implementation illustrates a specific method for detecting whether the first electronic device has the target application set. By detecting the target application in the first electronic device, it can be ensured that the first electronic device can quickly jump from the first page to the target page of the target application, thus ensuring the feasibility of this application.

[0019] In one implementation, notifying the application to obtain the target simulated click path corresponding to the first package name includes: notifying the application to match the first package name with at least one preset package name to determine the target package name matching the first package name from the preset package names, wherein each preset package name has an associated preset simulated click path; and notifying the application to obtain the target simulated click path associated with the target package name from the preset simulated click paths. This implementation illustrates a specific method for obtaining the target simulated click path.

[0020] In one implementation, the DMS creates a virtual screen in response to a first instruction, including: the DMS creating the virtual screen in response to the first instruction, displaying a first virtual page on the virtual screen, and displaying a first message on the first virtual page, wherein the first virtual page includes an application page of a first application in the first electronic device, or an application page of an application associated with a file-sharing function in the first electronic device. This implementation illustrates the content displayed on the virtual screen.

[0021] In one implementation, the simulated click application performs a simulated click operation on a virtual screen based on a target simulated click path, causing the DMS to display a target page on the virtual screen. This includes: the simulated click application performing a simulated click operation on a first message on a first virtual page based on the target simulated click path, causing the DMS to jump from the first virtual page to the target page on the virtual screen. This implementation illustrates a specific method by which a first electronic device can quickly jump from a first page to the target page of a target application.

[0022] In one implementation, obtaining the first screen identifier of the virtual screen includes: after creating the virtual screen, the DMS obtains the first screen identifier of the virtual screen; and notifies the application to obtain the first screen identifier from the DMS. This implementation illustrates a method for obtaining the first screen identifier. This allows for screen switching based on the first screen identifier, enabling the target page displayed on the virtual screen to quickly switch to the page displayed on the main screen. This ensures that the first electronic device can quickly jump from the first page to the target page of the target application, guaranteeing the feasibility of this application.

[0023] In one implementation, when a target application is set on the first electronic device, updating a first notification control to display a first button on the first notification control includes: when the notification application determines that the first electronic device has set the target application, the notification application sends a first update notification to the NMS, the first update notification including page information, the first update notification being used to notify the NMS to update the first notification control; the NMS responds to the first update notification by updating the first notification control to display the first button on the first notification control. This implementation demonstrates a specific display method for the first button. Thus, after the user clicks the first button, the first electronic device can quickly jump from the first page to the target page of the target application without relying on the access of a third-party application, optimizing the page jump process and improving the user experience.

[0024] In one implementation, in response to a first operation on a first button, switching a first screen identifier to a second screen identifier to display a target page includes: in response to the NMS receiving the first operation on the first button, notifying the application that it has obtained the first operation based on its listening relationship with the NMS; in response to notifying the application that it has obtained the first operation, notifying the application to send a second instruction to the DMS, the second instruction being used to switch to the second screen identifier; and in response to the second instruction, the DMS switching the first screen identifier to the second screen identifier, causing the display to jump from displaying the first page to displaying the target page. This implementation illustrates a specific method for screen switching based on a first screen identifier.

[0025] In one implementation, determining the target application based on the link type and the first package name includes: when the link type is a password link, matching the first package name with at least one preset package name to determine the target package name that matches the first package name from the preset package names; and determining the target application based on the target package name. This implementation illustrates a method for determining the target application, enabling subsequent detection of the target application in the first electronic device. This ensures that the first electronic device supports quick navigation from the first page to the target page of the target application, guaranteeing the feasibility of this application.

[0026] In one implementation, after determining the link type of the first link based on the text information, the method further includes: obtaining the target simulated click path corresponding to the first package name, wherein the target simulated click path is pre-stored in the first electronic device. Using this implementation, the target simulated click path can be obtained for subsequent use.

[0027] In one implementation, responding to a first operation on a first button, navigating from a first page to a target page associated with a first link includes: responding to the first operation on the first button by copying text information to the clipboard; launching a target application; and loading the text information from the clipboard into the target application based on a target simulated click path, thereby causing the display screen to navigate from displaying the first page to displaying the target page. This implementation illustrates a specific method for displaying the target page. In this way, the first electronic device can quickly navigate from the first page to the target page of the target application without relying on the access of a third-party application, optimizing the page navigation process and improving the user experience.

[0028] In one implementation, determining the target application based on the link type and the first package name, and detecting whether the first electronic device has the target application set, includes: when the link type is a password link, instructing the application to match the first package name with preset package names to determine the target package name matching the first package name from the preset package names; instructing the application to determine the target application based on the target package name, and detecting whether the first electronic device has the target application set. By using this implementation and detecting the target application in the first electronic device, it can be ensured that the first electronic device can quickly jump from the first page to the target page of the target application. This ensures the feasibility of this application.

[0029] In one implementation, obtaining the target simulated click path corresponding to the first package name includes: notifying the application to obtain the target simulated click path corresponding to the first package name. This implementation illustrates a specific method for obtaining the target simulated click path.

[0030] In one implementation, when a target application is set on a first electronic device, updating a first notification control to display a first button on the first notification control includes: if the notification application determines that the first electronic device has set the target application, the notification application sends a second update notification to the NMS, the second update notification including text information, the second update notification being used to notify the NMS to update the first notification control; the NMS responds to the second update notification by updating the first notification control to display the first button on the first notification control. This implementation demonstrates a specific display method for the first button. Thus, after a user clicks the first button, the first electronic device can quickly jump from the first page to the target page of the target application without relying on the access of a third-party application, optimizing the page jump process and improving the user experience.

[0031] In one implementation, in response to a first operation on a first button, the user jumps from a first page to a target page associated with a first link, including: in response to the NMS receiving the first operation on the first button, notifying the application to obtain the first operation based on the listening relationship with the NMS; in response to notifying the application to obtain the first operation, notifying the application to copy text information to the clipboard; notifying the application to send a third instruction to the Activity Management Service (AMS); the AMS responding to the third instruction and launching the target application; and the simulated click application loading the text information in the clipboard in the target application based on the target simulated click path, so that the display screen jumps from displaying the first page to displaying the target page. This implementation illustrates a specific method for displaying the target page. Thus, the first electronic device can quickly jump from the first page to the target page of the target application without relying on the access of a third-party application, optimizing the page jump process and improving the user experience.

[0032] Secondly, embodiments of this application provide a page navigation device applied to a first electronic device, comprising: a display module, configured to display a first notification control on a first page and a first button on the first notification control in response to receiving a first message, wherein the first message includes a first link for accessing a target application, and the first notification control is configured to notify the user that the first message has been received; and a navigation module, configured to navigate from the first page to a target page associated with the first link in response to a first operation on the first button, wherein the target page is the application page of the target application.

[0033] The page jump device provided in this application embodiment allows a first electronic device to display a first button in a first notification control corresponding to the first message after receiving a first message containing a first link. In this way, after the user clicks the first button, the first electronic device can quickly jump from the first page to the target page of the target application without relying on the access of a third-party application, thus optimizing the page jump process and improving the user experience.

[0034] Thirdly, embodiments of this application provide an electronic device, including: a processor and a memory, wherein the memory stores program instructions, and when the program instructions are executed by the processor, the electronic device performs the page jump method provided in the first aspect and any possible implementation thereof.

[0035] Fourthly, embodiments of this application provide a computer-readable storage medium, including: computer instructions that, when executed on an electronic device, cause the electronic device to perform a page navigation method as provided in the first aspect and any possible implementation thereof.

[0036] Fifthly, embodiments of this application provide a computer program product that, when run on an electronic device, causes the electronic device to execute the page redirection method provided by the first aspect and any possible implementation thereof.

[0037] Understandably, the beneficial effects that the technical solutions provided in the third to fifth aspects above can achieve can be referred to the beneficial effects in the first aspect and any of its possible implementations, and will not be repeated here. Attached Figure Description

[0038] To more clearly illustrate the technical solution of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1 This is a schematic diagram of a scenario where electronic devices transmit messages;

[0040] Figure 2 This is a schematic diagram of the first scenario where electronic devices share content.

[0041] Figure 3 This is a diagram illustrating the second scenario of content sharing using electronic devices;

[0042] Figure 4 This is a schematic diagram of the third scenario for content sharing using electronic devices;

[0043] Figure 5This is a diagram illustrating the fourth scenario of content sharing using electronic devices.

[0044] Figure 6 This is a diagram illustrating the fifth scenario of content sharing using electronic devices.

[0045] Figure 7 This is a diagram illustrating the sixth scenario of content sharing using electronic devices.

[0046] Figure 8 This is a schematic diagram of the hardware structure of the first electronic device provided in an embodiment of this application;

[0047] Figure 9 This is a schematic diagram of the software structure of the first electronic device provided in an embodiment of this application;

[0048] Figure 10 This is a schematic diagram of the first scenario of the page redirection method provided in the embodiments of this application;

[0049] Figure 11 This is the first method flowchart of the page redirection method provided in the embodiments of this application;

[0050] Figure 12 This is the second method flowchart of the page redirection method provided in the embodiments of this application;

[0051] Figure 13 This is the first interactive schematic diagram of the page navigation method provided in the embodiments of this application;

[0052] Figure 14 This is a schematic diagram of the first scenario of performing a simulated click operation on a virtual screen, provided in an embodiment of this application;

[0053] Figure 15 This is a schematic diagram of a second scenario of performing a simulated click operation on a virtual screen, provided in an embodiment of this application;

[0054] Figure 16 This is a schematic diagram of the second scenario of the page redirection method provided in the embodiments of this application;

[0055] Figure 17 This is the second interactive schematic diagram of the page navigation method provided in the embodiments of this application;

[0056] Figure 18 This is a schematic diagram of the third scenario of the page redirection method provided in the embodiments of this application;

[0057] Figure 19 This is the third interactive schematic diagram of the page navigation method provided in the embodiments of this application;

[0058] Figure 20This is a schematic diagram of a third scenario of performing a simulated click operation on a virtual screen, provided in an embodiment of this application;

[0059] Figure 21 This is a schematic diagram of the fourth scenario of the page redirection method provided in the embodiments of this application;

[0060] Figure 22 This is the third method flowchart of the page redirection method provided in the embodiments of this application;

[0061] Figure 23 This is the fourth interactive schematic diagram of the page navigation method provided in the embodiments of this application;

[0062] Figure 24 This is a schematic diagram of the fourth scenario of performing a simulated click operation on a virtual screen, provided in an embodiment of this application;

[0063] Figure 25 This is the fourth method flowchart of the page redirection method provided in the embodiments of this application;

[0064] Figure 26 This is a schematic diagram of the structure of a chip system provided in an embodiment of this application. Detailed Implementation

[0065] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. Other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are all within the protection scope of this application.

[0066] In the description of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences.

[0067] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0068] The application scenarios of the embodiments of this application will be described below with reference to the accompanying drawings.

[0069] Based on the messaging capabilities of electronic devices, users can share content to meet their interaction needs.

[0070] Figure 1 This is a schematic diagram of a scenario where electronic devices transmit messages.

[0071] like Figure 1 As shown, a message transmission scenario can involve multiple electronic devices, such as electronic device 1 and electronic device 2. Based on the transmission direction of the message from one electronic device to another, the electronic devices can be divided into sending devices and receiving devices. The sending device, also called the source, refers to the party that sends the message during transmission, such as electronic device 1. The receiving device, also called the sink, refers to the party that receives the message during transmission, such as electronic device 2.

[0072] Among them, the sending electronic device can send the content to be shared to the receiving electronic device in the form of a message based on methods such as card link sharing, password link sharing, Uniform Resource Locator (URL) link sharing, and multi-device collaborative sharing.

[0073] It should be noted that the sending and receiving devices in a message transmission scenario are logically determined based on the direction of message transmission. Therefore, depending on the direction of message transmission, an electronic device can act as both a sending and receiving device. For example, for electronic devices 1 and 2, when electronic device 1 sends a message to electronic device 2, electronic device 1 is the sending device and electronic device 2 is the receiving device; conversely, when electronic device 2 sends a message to electronic device 1, electronic device 1 is the receiving device and electronic device 2 is the sending device. For the sake of clarity in describing the technical solutions of the embodiments of this application, electronic device 1 will be consistently referred to as the sending device and electronic device 2 as the receiving device from this application onwards.

[0074] The following explains how to share content on electronic devices.

[0075] Figure 2 This is a schematic diagram of the first scenario where electronic devices share content.

[0076] like Figure 2 As shown, in one implementation, application A1 is used as a social application and application B1 is used as a chat application for illustrative purposes.

[0077] User A can click the first application icon 3 corresponding to application A1 on electronic device 1. In response to user A's click on the first application icon 3, electronic device 1 enters the first application page 4 of application A1 and displays at least one first application control 5 on the first application page 4.

[0078] In the case where application A1 is a social application, the social application can display recommended text and image content to user A based on the first application control 5. The recommended text and image content may be, for example, a note summary or the first frame of a video.

[0079] User A can click on the first application control 5. In response to the click operation on the first application control 5, the electronic device 1 displays the second application page 6 of application A1, and displays the first application content 7 and the first share button 8 on the second application page 6.

[0080] Among them, the first application content 7 can be the detailed text and image content corresponding to the recommended text and image content. The detailed text and image content can be, for example, notes, full videos, etc.

[0081] User A can click the first share button 8. In response to the click operation of the first share button 8, electronic device 1 displays the first share panel 9 and displays the second application icon 10 corresponding to application B1 on the first share panel 9.

[0082] User A can click on the second application icon 10. In response to the click operation on the second application icon 10, electronic device 1 displays the third application page 11 of application B1 and displays at least one contact control 12 within the third application page 11.

[0083] User A can click on the contact control 12 corresponding to User B. In response to the click operation on the contact control 12, application A1 in electronic device 1 sends a first application message to application B1 in electronic device 1, so that application B1 in electronic device 1 sends a first application message to application B1 in user B's electronic device 2 to share the first application content 7.

[0084] Based on the different types of application A1, electronic device 1 can configure different types of links in the first application message to link to the first application content 7.

[0085] A link is a connection from one page to a target, which can be a webpage, a different location on a webpage, an image, an email address, a file, or an application. This application does not limit the specific form of the target that a link points to.

[0086] Among them, the first application message can be linked to the first application content 7 in the form of a card link.

[0087] Card links are a type of card-style link used in social applications or other specific applications. They offer rich visual presentation, displaying information such as titles, descriptions, and images, allowing users to preview the link content without leaving the current page.

[0088] It should be noted that application A1 can be of different types. This embodiment only uses application A1 as a social application for illustrative purposes. In fact, application A1 can also be a shopping application, a video application, or a browser application. This application embodiment does not limit the application type of application A1. Application B1 can also be of different types. This embodiment only uses application B1 as a chat application for illustrative purposes. This application embodiment does not limit the application type of application B1.

[0089] The following is an exemplary description of the process by which user B's electronic device 2 receives the first application message.

[0090] Figure 3 This is a diagram illustrating the second scenario of content sharing using electronic devices.

[0091] like Figure 3 As shown, electronic device 2 can receive the first application message. In response to the received first application message, electronic device 2 can display a message notification control 14 on the notification center page 13. The message notification control 14 is used to notify user B that the first application message has been received.

[0092] User B can click on the message notification control 14. In response to the click operation on the message notification control 14, the electronic device 2 displays the fourth application page 15 of application B1, and displays the first application message 16 in the form of a card link on the fourth application page 15.

[0093] User B can click on the first application message 16. In response to the click operation on the first application message 16, electronic device 2 displays the fifth application page 17 of application B1, and displays the first abbreviated content 18 and at least one first jump button 19 on the fifth application page 17. The first abbreviated content 18 is an abbreviated form of the first application content 7.

[0094] User B can click the first jump button 19. In response to the click operation of the first jump button 19, the electronic device 2 displays a first floating window 20 on the fifth application page 17, and displays a first confirmation button 21 on the first floating window 20. The first confirmation button 21 is used to confirm whether to jump to application A1.

[0095] User B can click the first confirmation button 21. In response to the click operation of the first confirmation button 21, the electronic device 2 displays the second application page 6 of application A1 and displays the first application content 7 on the second application page 6.

[0096] In this way, user B can access the content shared by user A.

[0097] In one implementation, application A1 is used as a shopping application and application B1 is used as a chat application for illustrative purposes.

[0098] It should be noted here that the process of user A sending the first application message from electronic device 1 to user B's electronic device 2 can be found in [reference needed]. Figure 2 This embodiment is not shown in the accompanying drawings. The process of sending the first application message is the same as in the previous embodiment, except that the link type configured in the first application message differs from the previous embodiment. This difference in link type is due to the different application type of application A1.

[0099] User A can click the first application icon 3 corresponding to application A1 on electronic device 1. In response to user A's click on the first application icon 3, electronic device 1 enters the first application page 4 of application A1 and displays at least one first application control 5 on the first application page 4.

[0100] In the case where application A1 is a shopping application, the shopping application can display recommended text and image content to user A based on the first application control 5. The recommended text and image content may be, for example, product introductions, live broadcast links, etc.

[0101] User A can click on the first application control 5. In response to the click operation on the first application control 5, the electronic device 1 displays the second application page 6 of application A1, and displays the first application content 7 and the first share button 8 on the second application page 6.

[0102] Among them, the first application content 7 can be the detailed image and text content corresponding to the recommended image and text content. The detailed image and text content can be, for example, a product purchase page, a live broadcast room, etc.

[0103] User A can click the first share button 8. In response to the click operation of the first share button 8, electronic device 1 displays the first share panel 9 and displays the second application icon 10 corresponding to application B1 on the first share panel 9.

[0104] User A can click on the second application icon 10. In response to the click operation on the second application icon 10, electronic device 1 displays the third application page 11 of application B1 and displays at least one contact control 12 within the third application page 11.

[0105] User A can click on the contact control 12 corresponding to User B. In response to the click operation on the contact control 12, application A1 in electronic device 1 sends a first application message to application B1 in electronic device 1, so that application B1 in electronic device 1 sends a first application message to application B1 in user B's electronic device 2 to share the first application content 7.

[0106] Based on the different types of application A1, electronic device 1 can configure different types of links in the first application message to link to the first application content 7.

[0107] Among them, the first application message can be linked to the first application content 7 in the form of a password link.

[0108] A password link is a link consisting of a string of letters and numbers that represents a URL or specific information. Based on the user's copying and use of the password, it can be shared privately or temporarily to directly access the target content in a specific application or service.

[0109] The following is an exemplary description of the process by which user B's electronic device 2 receives the first application message.

[0110] Figure 4 This is a diagram illustrating the third scenario where electronic devices share content.

[0111] like Figure 4 As shown, electronic device 2 can receive the first application message. In response to the received first application message, electronic device 2 can display a message notification control 14 on the notification center page 13. The message notification control 14 is used to notify user B that the first application message has been received.

[0112] User B can click on the message notification control 14. In response to the click operation on the message notification control 14, the electronic device 2 displays the fourth application page 15 of application B1, and displays the first application message 16 in the form of a password link on the fourth application page 15.

[0113] User B can long press the first application message 16. In response to the long press operation of the first application message 16, the electronic device 2 displays the copy button 22 in the adjacent area of ​​the first application message 16.

[0114] User B can click the copy button 22. In response to the user's click on the copy button 22, electronic device 2 copies the first application message 16 to the clipboard.

[0115] User B can swipe up from the bottom of the display screen of electronic device 2. In response to the swipe up, electronic device 2 displays the main screen page 23 and displays the second application icon 10 corresponding to application B1 on the main screen page 23.

[0116] User B can click the second application icon 10. In response to the click operation, electronic device 2 loads the password link corresponding to the first application message 16 based on application B1 to display the second floating window 24, and displays the second abbreviated content 25 and the second confirmation button 26 in the second floating window 24. The second abbreviated content 25 is an abbreviated form of the first application content 7.

[0117] User B can click the second confirmation button 26. In response to the click operation of the second confirmation button 26, the electronic device 2 displays the second application page 6 of application A1 and displays the first application content 7 on the second application page 6.

[0118] In this way, user B can access the content shared by user A.

[0119] It should be noted that, depending on the application A1, the display format and content of the second application page 6 and the first application content 7 are different. The various embodiments can be referred to each other, and the embodiments of this application do not make specific distinctions in this regard.

[0120] In one implementation, application A1 is used as a browser application and application B1 is used as a chat application for example.

[0121] It should be noted here that the process of user A sending the first application message from electronic device 1 to user B's electronic device 2 can be found in [reference needed]. Figure 2 This embodiment is not shown in the accompanying drawings. The process of sending the first application message is the same as in the previous embodiment, except that the link type configured in the first application message differs from the previous embodiment. This difference in link type is due to the different application type of application A1.

[0122] User A can click the first application icon 3 corresponding to application A1 on electronic device 1. In response to user A's click on the first application icon 3, electronic device 1 enters the first application page 4 of application A1 and displays at least one first application control 5 on the first application page 4.

[0123] In the case where application A1 is a browser application, the browser application can display recommended text and image content to user A based on the first application control 5. The recommended text and image content may be, for example, a news summary.

[0124] User A can click on the first application control 5. In response to the click operation on the first application control 5, the electronic device 1 displays the second application page 6 of application A1, and displays the first application content 7 and the first share button 8 on the second application page 6.

[0125] Among them, the first application content 7 can be the detailed text and image content corresponding to the recommended text and image content, such as a complete news report.

[0126] User A can click the first share button 8. In response to the click operation of the first share button 8, electronic device 1 displays the first share panel 9 and displays the second application icon 10 corresponding to application B1 on the first share panel 9.

[0127] User A can click on the second application icon 10. In response to the click operation on the second application icon 10, electronic device 1 displays the third application page 11 of application B1 and displays at least one contact control 12 within the third application page 11.

[0128] User A can click on the contact control 12 corresponding to User B. In response to the click operation on the contact control 12, application B1 in electronic device 1 sends a first application message to application B1 in user B's electronic device 2 to share the first application content 7.

[0129] Based on the different types of application A1, electronic device 1 can configure different types of links in the first application message to link to the first application content 7.

[0130] Among them, the first application message can be linked to the first application content 7 via a URL link.

[0131] A URL is a standardized form of link used to find and access resources, such as web pages, images, videos, and documents.

[0132] The following is an exemplary description of the process by which user B's electronic device 2 receives the first application message.

[0133] Figure 5 This is a diagram illustrating the fourth scenario of content sharing using electronic devices.

[0134] like Figure 5 As shown, electronic device 2 can receive the first application message. In response to the received first application message, electronic device 2 can display a message notification control 14 on the notification center page 13. The message notification control 14 is used to notify user B that the first application message has been received.

[0135] User B can click the message notification control 14. In response to the click operation of the message notification control 14, the electronic device 2 displays the fourth application page 15 of application B1, and displays the first application message 16 in the form of a URL link on the fourth application page 15.

[0136] It should be noted that the first application message 16 can be in the form of a combination of text and URL link, or it can be just a URL link. This application embodiment does not limit the specific form of the first application message 16.

[0137] User B can click on the first application message 16. In response to the click operation on the first application message 16, the electronic device 2 displays the second application page 6 of application A1 and displays the first application content 7 on the second application page 6.

[0138] In this way, user B can access the content shared by user A.

[0139] In the second to fourth scenarios of content sharing by the aforementioned electronic devices, after receiving the first application message, electronic device 2 needs to first enter application B1, open the link in the first application message 16 within the application page of application B1, and then application B1 needs to access application A1 before the first application content 7 can be displayed within the application page of application A1. In other words, electronic device 2 relies on the access of a third-party application to complete the page redirection process. This series of operations makes the page redirection process cumbersome and negatively impacts the user experience.

[0140] Electronic devices can share content not only based on different applications, but also based on multi-device collaboration technology.

[0141] Multi-device collaborative sharing technology can establish a self-organizing network among multiple near-field electronic devices based on a user-centric identity authentication system, enabling trusted interconnection between these devices. This allows for information sharing among the multiple electronic devices.

[0142] Based on multi-device collaborative sharing technology, electronic devices can have built-in file sharing functions. These functions can wirelessly share files such as pictures, videos, and documents between electronic devices. The function can discover nearby electronic devices via Bluetooth and directly transfer files through a wireless local area network (WLAN).

[0143] The following explains the process of content sharing by electronic devices based on multi-device collaboration technology.

[0144] Figure 6 This is a diagram illustrating the fifth scenario of content sharing using electronic devices.

[0145] like Figure 6 As shown, in one implementation, application A1 is used as an example of a video application.

[0146] User A can click the first application icon 3 corresponding to application A1 on electronic device 1. In response to user A's click on the first application icon 3, electronic device 1 enters the first application page 4 of application A1 and displays at least one first application control 5 on the first application page 4.

[0147] In the case where application A1 is a video application, the video application can display recommended text and image content to user A based on the first application control 5. The recommended text and image content may be, for example, the first frame of a video.

[0148] User A can click on the first application control 5. In response to the click operation on the first application control 5, the electronic device 1 displays the second application page 6 of application A1, and displays the first application content 7 and the first share button 8 on the second application page 6.

[0149] Among them, the first application content 7 can be the detailed text and image content corresponding to the recommended text and image content, such as a complete video.

[0150] User A can click the first share button 8. In response to the click operation of the first share button 8, the electronic device 1 displays the first share panel 9 and displays at least one receiver control 27 based on the file sharing function on the first share panel 9.

[0151] User A can click on the receiver control 27. In response to the click operation on the receiver control 27, the file sharing function of electronic device 1 sends a file sharing message to the file sharing function of user B's electronic device 2 to share the first application content 7.

[0152] Among them, based on the file sharing function, file sharing messages can be linked to the first application content 7 via URL links.

[0153] The following is an illustrative description of the process by which user B's electronic device 2 receives file sharing messages.

[0154] Figure 7 This is a diagram illustrating the sixth scenario of content sharing using electronic devices.

[0155] like Figure 7As shown, electronic device 2 can receive file sharing messages. In response to the received file sharing message, electronic device 2 can display system notification control 28 on the notification center page 13. System notification control 28 is used to notify user B that a file sharing message has been received.

[0156] The user can click the system notification control 28. In response to the click operation of the system notification control 28, the electronic device 2 displays the sixth application page 29 of the application C1, and displays the file sharing message 30 in the form of a URL link on the sixth application page 29.

[0157] It should be noted that since the file sharing function does not exist as a standalone application, it can be associated with an application C1 (such as a note-taking application) that can display text links, so that when the electronic device 2 receives a file sharing message based on the file sharing function, it can display the content of the file sharing message.

[0158] The user can click on the file sharing message 30. In response to the click operation on the file sharing message 30, the electronic device 2 displays the second application page 6 of the application A1, and displays the first application content 7 on the second application page 6.

[0159] In this way, user B can access the content shared by user A.

[0160] In the sixth scenario of content sharing by the aforementioned electronic devices, after receiving the file sharing message 30, electronic device 2 needs to first enter application C1, open the link in file sharing message 30 within application C1's application page, and then application C1 needs to connect to application A1 before the first application content 7 can be displayed within application A1's application page. In other words, electronic device 2 relies on the access of a third-party application to complete the page redirection process. This series of operations makes the page redirection process cumbersome and negatively impacts the user experience.

[0161] In summary, in various scenarios where electronic devices share content, they all rely on the access of third-party applications to complete the page navigation process. This makes the page navigation process cumbersome and affects the user experience.

[0162] To address this issue, this application provides a page redirection method.

[0163] The page redirection method provided in this application embodiment can be applied to a first electronic device. The first electronic device can be a receiving electronic device.

[0164] It should be noted that the embodiments of this application are only illustrated by using the first electronic device as the receiving electronic device. In fact, the embodiments of this application do not limit the first electronic device to be either the receiving electronic device or the sending electronic device.

[0165] The first electronic device includes, but is not limited to, mobile phones, tablets, personal computers, workstations, large-screen devices (e.g., smart screens, smart TVs), wearable devices (e.g., smart bracelets, smartwatches), handheld game consoles, home game consoles, virtual reality devices, augmented reality devices, mixed reality devices, and in-vehicle smart terminals. This application does not limit the specific technology or form of the first electronic device.

[0166] Figure 8 This is a schematic diagram of the hardware structure of the first electronic device provided in the embodiments of this application.

[0167] like Figure 8 As shown, the first electronic device 100 may include a processor 110, a memory 120, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antennas 01 and 02, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, a camera 192, a display screen 193, and a Subscriber Identification Module (SIM) card interface 194, etc. The sensor module 180 may include a touch sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a geomagnetic sensor 180D, an accelerometer sensor 180E, a proximity sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, etc. Among them, the gyroscope sensor 180B, the barometric pressure sensor 180C, the geomagnetic sensor 180D, and the accelerometer sensor 180E can all be used to detect the motion state of the first electronic device, and therefore can also be called motion sensors.

[0168] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the first electronic device 100. In other embodiments of this application, the first electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0169] Processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0170] The memory 120 can be used to store computer executable program code, including instructions. The memory 120 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the first electronic device 100 (such as audio data, phonebook, etc.). Furthermore, the memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, Universal Flash Storage (UFS), etc. The processor 110 executes various functional applications and data processing of the first electronic device 100 by running instructions stored in the memory 120 and / or instructions stored in memory disposed in the processor.

[0171] USB interface 130 is a USB standard compliant interface, specifically a Mini USB interface, Micro USB interface, USB Type-C interface, etc. USB interface 130 can be used to connect a charger to charge the first electronic device 100, and can also be used for data transfer between the first electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other first electronic devices, such as AR devices.

[0172] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the first electronic device 100. In other embodiments of this application, the first electronic device 100 may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0173] The charging management module 140 is used to receive charging input from the charger.

[0174] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, memory 120, display screen 193, camera 192, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance).

[0175] The wireless communication function of the first electronic device 100 can be implemented through antenna 01, antenna 02, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0176] Antenna 01 and antenna 02 are used to transmit and receive electromagnetic wave signals.

[0177] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the first electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 01, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 01. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0178] A modem processor may include a modulator and a demodulator.

[0179] The wireless communication module 160 can provide solutions for wireless communication applications on the first electronic device 100, including Wireless Local Area Networks (WLANs) (such as Wireless Fidelity (Wi-Fi) networks), Bluetooth (BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), and Infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 02, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 02.

[0180] In this embodiment, the file sharing function of the first electronic device 100 relies on wireless communication technologies such as WLAN and Bluetooth provided by the wireless communication module 160.

[0181] In some embodiments, the antenna 01 of the first electronic device 100 is coupled to the mobile communication module 150, and the antenna 02 is coupled to the wireless communication module 160, so that the first electronic device 100 can communicate with the network and other devices through wireless communication technology.

[0182] The first electronic device 100 implements display functions through a GPU, a display screen 193, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 193 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0183] The display screen 193 is used to display images, videos, etc. The display screen 193 includes a display panel. In some embodiments, the first electronic device 100 may include one or N display screens 193, where N is a positive integer greater than 1.

[0184] In this embodiment of the application, the display screen 193 is used to display a first notification control and a first button on the first notification control.

[0185] The first electronic device 100 can perform shooting functions through an ISP, camera 192, video codec, GPU, display screen 193, and application processor.

[0186] The ISP (Image Signal Processor) is used to process data fed back from the camera 192. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set within the camera 192.

[0187] Camera 192 is used to capture still images or videos. An object passes through the lens to generate an optical image that is projected onto a photosensitive element. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP (Internet Service Provider) for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP (Digital Signal Processor) for processing. The DSP converts the digital image signal into image signals in standard formats such as RGB, RYYB, and YUV. In some embodiments, the first electronic device 100 may include one or N cameras 192, where N is a positive integer greater than 1.

[0188] The first electronic device 100 can implement audio functions, such as music playback and recording, through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, and an application processor.

[0189] Touch sensor 180A, also known as a "touch device," can be disposed on display screen 193. The touch sensor 180A and display screen 193 together form a touchscreen, also known as a "touchscreen." Touch sensor 180A is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 193. In other embodiments, touch sensor 180A may also be disposed on the surface of the first electronic device 100, in a different location than display screen 193.

[0190] The gyroscope sensor 180B can be used to determine the motion attitude of the first electronic device 100.

[0191] The 180C barometric pressure sensor is used to measure barometric pressure.

[0192] The geomagnetic sensor 180D includes a Hall sensor. The first electronic device 100 can use the geomagnetic sensor 180D to detect the opening and closing of the flip cover.

[0193] The accelerometer 180E can detect the magnitude of the acceleration of the first electronic device 100 in various directions (generally three axes).

[0194] Distance sensor 180F is used to measure distance.

[0195] The proximity light sensor 180G may include, for example, a light-emitting diode and a light detector, such as a photodiode.

[0196] The fingerprint sensor 180H is used to collect fingerprints.

[0197] The 180J temperature sensor is used to detect temperature.

[0198] Button 190 includes the power button, volume buttons, etc.

[0199] Motor 191 can generate vibration alerts.

[0200] The SIM card interface 194 is used to connect the SIM card.

[0201] The software system of the first electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses the layered architecture Android system as an example to exemplify the software structure of the first electronic device 100.

[0202] Figure 9 This is a schematic diagram of the software structure of the first electronic device provided in the embodiments of this application.

[0203] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0204] The application layer can include a series of application packages.

[0205] like Figure 9 As shown, the application package may include applications such as battery management, camera, gallery, calendar, call, map, navigation, music, video, and SMS.

[0206] The application package in this application embodiment may include social applications, chat applications, shopping applications, notification applications, and simulated click applications, etc. This application embodiment does not limit the types of applications in the application package.

[0207] In this embodiment, the notification application is an application used to handle notification logic. The notification application may include a notification listening module, a user interface (UI) module, and a click event module.

[0208] The notification listening module can listen for various notification events, such as the arrival of new notifications, cancellation of notifications, and clearing of notifications.

[0209] The UI module can provide ways to display notifications.

[0210] The click event module is used to execute business logic associated with click events in order to manage the triggering, processing and subsequent behavior of click events.

[0211] In this embodiment, the simulated click application is an application used to automatically perform click operations on elements on a graphical user interface. The simulated click application may include a path configuration module and a click execution module.

[0212] The path configuration module can identify and specify specific elements or coordinates on the display screen so that simulated click operations can be executed accurately.

[0213] The click execution module is the part that simulates click actions in an application. This module can perform click actions, control click positions, simulate clicks on different buttons, control click speed, and handle multi-touch, etc.

[0214] The application framework layer provides an Application Programming Interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0215] like Figure 9 As shown, the application framework layer may include a window manager, an input manager, a sensor manager, a phone manager, a resource manager, a notification manager, etc.

[0216] The input manager can be used to listen for user input events, such as clicks and swipes performed by the user's finger on the display screen 193 of the first electronic device 100. By listening to input events, the first electronic device 100 can determine whether it is in use.

[0217] The sensor manager is used to monitor data returned by various sensors in the first electronic device, such as motion sensor data, proximity sensor data, and temperature sensor data. Using the data returned by these sensors, the first electronic device can determine whether it is experiencing vibration or whether the display screen 193 is obstructed.

[0218] In this embodiment of the application, the application framework layer includes Notification Manager Service (NMS), Display Manager Service (DMS), Activity Manager Service (AMS), Package Manager Service (PMS), Accessibility Service (AS), and Instrumentation Service, etc.

[0219] The NMS (Notification Management System) is a service used to manage and control notifications. It can perform functions such as processing notification requests, managing notification display, providing notification query and update capabilities, listening for notification events, and storing notification information. In this embodiment, the NMS can provide notification modification functionality.

[0220] Display Management System (DMS) is a service used to manage and control display devices. It handles the connection and configuration of display devices and notifies the system and applications when the display state of the device changes. In this embodiment, DMS can be used to create virtual screens.

[0221] AMS can perform functions such as component management, process management, task management, memory management, startup process, lifecycle management, cross-process communication, and interaction with other system services. In this embodiment, AMS can be used to launch applications on a virtual screen.

[0222] Application Management System (PMS) is a service used to manage application packages. It can parse application packages to obtain application component information and permissions. In this embodiment, the PMS can be used to obtain application information.

[0223] AS can perform functions such as event listening and feedback, operation automation, assisted operation, cross-application support, and enhanced accessibility. In the embodiments of this application, AS can be used to perform content analysis on page content on a virtual screen.

[0224] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0225] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0226] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0227] System libraries can include multiple functional modules. For example: Surface Manager, Media Libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0228] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0229] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0230] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0231] A 2D graphics engine is a graphics engine for 2D drawing.

[0232] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0233] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the first electronic device 100. In other embodiments of this application, the first electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0234] When the first electronic device 100 is a receiving electronic device, the second electronic device can act as a sending electronic device to send a first message to the first electronic device 100. That is to say, the second electronic device is the peer device of the first electronic device.

[0235] In one implementation, a target application of the second electronic device can send a first message to a first application of the second electronic device. Further, the first application of the second electronic device sends a first message to a first application of the first electronic device 100. The first message includes a first link for accessing the target application.

[0236] The first application can be a third-party application, which refers to an application created by an independent software vendor or individual developer, rather than an application built into the electronic device. Third-party applications can extend the functionality of the electronic device, provide specific services, and enhance the user experience. The first application can also be a system application. This application embodiment does not limit the specific type of the first application. Furthermore, in this application embodiment, the target application can be either a third-party application or a system application. This application embodiment does not limit the specific type of the target application.

[0237] The first embodiment of this application is described below by way of example.

[0238] Figure 10 This is a schematic diagram of the first scenario of the page redirection method provided in the embodiments of this application.

[0239] Figure 11 This is the first method flowchart of the page redirection method provided in the embodiments of this application.

[0240] like Figure 10 and Figure 11 As shown, in some embodiments, the method includes the following steps S1-S2.

[0241] In step S1, in response to receiving a first message sent by a first application in the second electronic device, the first electronic device 100 displays a first notification control 32 corresponding to the first application in the first electronic device 100 on the first page 31, and displays a first button 33 on the first notification control 32. The first message includes a first link for accessing the target application, and the first notification control 32 is used to notify the user that the first message has been received.

[0242] The first application includes an application different from the target application. In some cases, the first application may also be the same as the target application, and this application embodiment does not limit this.

[0243] This embodiment uses a chat application as the first application and a social application as the target application for illustrative purposes.

[0244] For example, a social application of a second electronic device sends a first message to a chat application of the second electronic device, causing the chat application of the second electronic device to send a first message to the chat application of the first electronic device 100, the first message including a card link for accessing the social application.

[0245] The method by which the second electronic device sends the first message to the first electronic device 100 can be referred to in the foregoing embodiments. Figure 2 In this embodiment, application A1 in electronic device 1 sends a first application message to application B1 in electronic device 1, which in turn causes application B1 in electronic device 1 to send a first application message to application B1 in electronic device 2. That is, the second electronic device can be electronic device 1, the first electronic device 100 can be electronic device 2, and the first message can be a first application message. The specific method by which the second electronic device sends the first message to the first electronic device 100 is not described in detail in this application embodiment.

[0246] In this way, the chat application of the first electronic device 100 can receive the first message.

[0247] After receiving the first message, the first electronic device 100 can employ various message notification mechanisms. For example, a banner-based notification mechanism, a pop-up notification mechanism, or a notification center-based notification mechanism. This application embodiment does not limit the specific type of message notification mechanism.

[0248] This embodiment illustrates the use of a notification mechanism based on a notification center in the first electronic device 100.

[0249] When the first electronic device 100 adopts a notification center-based message notification mechanism, the first page 31 can be a notification center page, and correspondingly, the first notification control 32 can be as follows: Figure 11 The control is shown in the form of a small window.

[0250] It should be noted that when the first electronic device 100 adopts other message notification mechanisms, the first page 31 can also be the home screen page, the lock screen page, or other pages. For example, when the first electronic device 100 adopts a message notification mechanism based on pop-up notifications, the first page 31 can be the home screen page, and correspondingly, the first notification control 32 can be a floating window control (not shown in the accompanying drawings). This application embodiment does not limit the page type of the first page 31 or the control type of the first notification control 32.

[0251] In step S2, in response to the first operation of the first button 33, the first electronic device 100 jumps from the first page 31 to the target page 34 associated with the first link, and the target page 34 is the application page of the target application.

[0252] Furthermore, based on the foregoing embodiments, since the target application is a social application, the first link can be associated with the target page 34 in the social application.

[0253] Target page 34 can be referred to in the foregoing embodiments. Figure 3The second application page 6 in this application embodiment does not limit the specific page format of the target page 34.

[0254] In other words, in this embodiment, the first electronic device 100 can quickly jump from the first page 31 to the target page 34 of the target application (e.g., a social application) without relying on the access of a third-party application (e.g., a chat application), thus optimizing the page jump process and improving the user experience.

[0255] The specific implementation of the embodiments of this application will be further described below.

[0256] Figure 12 This is the second method flowchart of the page redirection method provided in the embodiments of this application.

[0257] Figure 13 This is the first interactive schematic diagram of the page navigation method provided in the embodiments of this application.

[0258] like Figure 12 and Figure 13 As shown, in one implementation, step S1 includes the following steps S11-S13.

[0259] In step S11, in response to receiving a first message sent by a first application in the second electronic device, the first electronic device 100 displays a first notification control 32 on the first page 31.

[0260] Step S11 includes the following steps S111-S112.

[0261] In step S111, in response to the NMS receiving the first message, the NMS determines the properties of the first notification control 32 corresponding to the first message.

[0262] The attributes of the first notification control 32 are preset attributes, which can be set based on the system theme of the first electronic device 100 and the application theme of the first application. The attributes of the first notification control 32 may include title, text, icon, image, progress bar, animation, etc. This application embodiment does not limit the form of the attributes of the first notification control 32.

[0263] In step S112, the NMS causes the first page 31 to display the first notification control 32 according to the properties of the first notification control 32.

[0264] In one implementation, the NMS can perform a series of processes on the first message, including verifying the validity of the first message, determining the display method of visual elements such as icons, text, and colors in the first notification control 32 corresponding to the first message, and determining the feedback method of the first message, such as sound and vibration. In other words, the NMS determines the attributes of the first notification control 32. After completing a series of processes, the NMS displays the first notification control 32 based on its attributes, so that the first page 31 displays the first notification control 32.

[0265] In step S12, the first electronic device 100 parses the first message to determine whether the first electronic device 100 has a target application set up.

[0266] Step S12 includes the following steps S121-S123.

[0267] In step S121, the first electronic device 100 parses the first message to obtain the first packet name corresponding to the first message and the text information of the first link.

[0268] The first packet name is the packet name of the sender of the first message, and the sender includes the target application in the second electronic device.

[0269] It should be noted that the sender is the initial generator of the first packet name. For example, in this embodiment, during the process of the social application of the second electronic device sending a first message to the chat application of the second electronic device, and the chat application of the second electronic device sending a first message to the chat application of the first electronic device 100, the social application is the initial generator of the first packet name, and therefore the first packet name is the packet name of the social application. The chat application is only the transmitter of the first message.

[0270] Step S121 may include steps S1211-S1212.

[0271] In step S1211, NMS parses the first message to obtain the first packet name and text information.

[0272] The package name is a string used to uniquely identify an application, and its naming follows certain rules, such as including the reverse domain name, application name, and separators.

[0273] In this embodiment, the first package name is the package name of the social application.

[0274] For example, the first package name could be com.xxx.social. In this package name, the reverse domain is usually the reverse of a domain owned by the developer; for example, com.xxx is a reverse domain. The application name could be social. That is, this package name represents an application named social developed by company xxx.

[0275] It should be noted that the first package name shown in this application embodiment is only for illustrative purposes. The first package name may also include other data structures. This application embodiment does not limit the package name structure of the first package name.

[0276] In this embodiment, since the first link is a card link, the text information obtained by the NMS may include, for example, the title of the card link, the description of the card link, the URL corresponding to the image in the card link, preview text, source information, etc. This embodiment does not limit the specific content of the text information.

[0277] In one implementation, when the target application in the second electronic device creates the first link, it can create a Notification object and store text information in this object. In this way, when the target application in the second electronic device sends a first message to the first application in the second electronic device, the first message includes the Notification object. Correspondingly, when NMS receives and parses the first message, it can directly obtain the text information from the Notification object.

[0278] It should be noted that the process by which NMS obtains text information based on the Notification object is a system-level acquisition process. NMS can also obtain text information through other methods, such as inter-process communication. This application does not limit the specific method by which NMS obtains text information.

[0279] Step S1212: Notify the application to obtain the first packet name and text information based on the listening relationship with NMS.

[0280] In one implementation, the notification listening module obtains the first packet name and text information based on its listening relationship with NMS.

[0281] It should be noted that the corresponding steps executed by the notification listening module in the embodiments of this application can also be executed by the notification application based on other modules. The following embodiments of this application are only illustrated by the notification listening module. In fact, the embodiments of this application do not limit the specific execution module of the notification application.

[0282] The notification listening module can register a listener with the NMS to monitor changes within the NMS. For example, the notification listening module can register a Notification Listener Service with the NMS, setting this service as a listener in the NMS. This way, when the NMS receives the first message, the notification listening module can listen for this event and further retrieve the first packet name and text information from the NMS.

[0283] The notification listening module can also invoke AS to listen to NMS to monitor changes in NMS. For example, the notification listening module can enable AS so that AS calls Accessibility Service Info to configure the notification type to listen for. In this way, when NMS receives the first message, AS can listen for this event and send it to the notification listening module, so that the notification listening module can obtain the first packet name and text information from NMS.

[0284] It should be noted that the embodiments of this application do not limit the way the notification listening module establishes a listening relationship with NMS.

[0285] The notification monitoring module can establish a monitoring relationship with the NMS immediately after the first electronic device 100 is powered on, or it can establish a monitoring relationship with the NMS at other times. For example, the notification monitoring module can establish a monitoring relationship with the NMS after it obtains the first configuration information. This application embodiment does not limit the specific time at which the notification monitoring module establishes a monitoring relationship with the NMS.

[0286] The process of obtaining the first configuration information is explained below.

[0287] Before step S1, steps S001-S003 may be included.

[0288] Step S001: Instruct the application to send a first request to the cloud server to request the first configuration information.

[0289] In step S002, in response to the first request, the cloud server sends the first configuration information to the notification application.

[0290] Step S003: Notify the application to store the first configuration information.

[0291] In one implementation, the notification listening module stores the first configuration information.

[0292] The first configuration information may include preset package names and preset simulated click paths associated with each preset package name. The first configuration information may also include preset rule templates or machine learning models. Furthermore, the first configuration information may configure preset application information associated with each preset package name, which may include application name, application page layout, and special fields of the application. The first configuration information can be configured based on various information involved in this application, and the specific content of the first configuration information is not limited in the embodiments of this application.

[0293] In step S122, the first electronic device 100 determines the link type of the first link based on the text information.

[0294] Step S122 may include step S1221.

[0295] Step S1221: Instruct the application to determine the link type based on the text information.

[0296] In one implementation, the notification listening module determines the link type based on text information.

[0297] In this embodiment, the notification monitoring module can determine that the link type is a card link based on the text information.

[0298] In one implementation, the notification listening module can query a preset rule template or a machine learning model, and use the preset rule module or machine learning model to identify the text information to identify the specific format or special fields corresponding to the card link, thereby determining that the first link is a card link. In this way, the notification listening module can determine that the first link is a card link. This application embodiment does not limit the specific method by which the notification application determines the link type based on text information.

[0299] In step S123, the first electronic device 100 determines the target application based on the link type and the first package name, and detects whether the first electronic device 100 has set the target application.

[0300] In the case of a card link, the first electronic device 100 obtains the target simulated click path corresponding to the first package name, and the target simulated click path is pre-stored in the first electronic device 100.

[0301] After obtaining the target simulated click path, the first electronic device 100 creates a virtual screen and performs a simulated click operation on the virtual screen based on the target simulated click path to display the target page 34 on the virtual screen.

[0302] Furthermore, the first electronic device 100 acquires page information of the target page 34 to determine the target application based on the page information.

[0303] The implementation method of step S123 will be further explained below.

[0304] Specifically, step S123 may include steps S1231-S1238.

[0305] Step S1231: Notify the application to obtain the target simulated click path corresponding to the first package name.

[0306] Step S1231 includes steps S1231a-S1231b.

[0307] Step S1231a: Instruct the application to match the first package name with at least one preset package name to determine the target package name that matches the first package name from the preset package names, wherein each preset package name has an associated preset simulated click path.

[0308] In one implementation, the notification listening module matches the first package name with at least one preset package name to determine the target package name that matches the first package name from the preset package names.

[0309] For example, the preset package names include com.xxx.social, com.xxx.shopping, com.xxx.browser, and com.xxx.share. The preset simulated click path associated with com.xxx.social is simulated click path M1, the preset simulated click path associated with com.xxx.shopping is simulated click path M2, the preset simulated click path associated with com.xxx.browser is simulated click path M3, and the preset simulated click path associated with com.xxx.share is simulated click path M4.

[0310] If the first package name is com.xxx.social, the first package name can be matched with the preset package name to determine the target package name as com.xxx.social.

[0311] Step S1231b: Instruct the application to obtain the target simulated click path associated with the target package name from the preset simulated click path.

[0312] In one implementation, the notification listening module obtains the target simulated click path associated with the target package name from the preset simulated click path.

[0313] For example, if the target package name is com.xxx.social, the notification listening module obtains the target simulated click path associated with the target package name as simulated click path M1.

[0314] Step S1232: Notify the application to send the target simulated click path to the simulated click application.

[0315] In one implementation, the notification listening module sends the target simulated click path to the simulated click application.

[0316] Specifically, the notification listening module can send the target simulated click path to the path configuration module in the simulated click application.

[0317] Furthermore, in response to the notification listening module sending the target simulated click path, the click event module can send a click event corresponding to the target simulated click path to the execution click module in the simulated click application.

[0318] Based on the aforementioned example, the notification listening module sends the simulated click path M1 to the path configuration module.

[0319] Correspondingly, in response to the notification listening module sending a simulated click path M1 to the path configuration module, the click event module sends a click event corresponding to the simulated click path M1 to the click execution module.

[0320] In step S1233, after receiving the target simulated click path, the simulated click application sends a first instruction to the DMS. The first instruction may be an instruction for creating a virtual screen.

[0321] In one implementation, the path configuration module sends a first instruction to the DMS after receiving the target simulated click path.

[0322] In step S1234, DMS responds to the first instruction by creating a virtual screen.

[0323] Step S1234 includes step S1234a.

[0324] In step S1234a, the DMS responds to the first instruction to create a virtual screen, displays a first virtual page on the virtual screen, and displays a first message on the first virtual page, wherein the first virtual page includes the application page of the first application in the first electronic device 100.

[0325] A virtual screen is a display screen generated based on software simulation. A virtual screen can provide display output without a physical display screen.

[0326] After the DMS creates a virtual screen, the DMS can send an application launch command to the AMS to start a first application. In response to the application launch command, the AMS launches the first application so that the DMS can display a first virtual page on the virtual screen and display a first message on the first virtual page.

[0327] In one implementation, the application launch instruction may contain an Intent object, which causes AMS to launch the first application based on the Intent object.

[0328] In this embodiment, when the first application is a chat application, the page format of the first virtual page can be referred to the aforementioned embodiments. Figure 3 The fourth application page 15. The page format of the first virtual page will not be described in detail in this embodiment.

[0329] Step S1234 also includes steps S1234b-S1234c.

[0330] In step S1234b, after creating the virtual screen, DMS obtains the first screen identifier of the virtual screen.

[0331] In step S1234c, the DMS sends the first screen identifier to the notification application so that the notification application can obtain the first screen identifier.

[0332] In one implementation, DMS sends the first screen identifier to the notification listening module so that the notification listening module can obtain the first screen identifier.

[0333] A screen identification (ID) is a string of characters used to uniquely identify the screen of an electronic device. Different electronic devices can have different screen ID formats. A virtual screen's screen ID can be assigned by the software or driver that created the virtual screen, and is used to uniquely identify the virtual screen within the operating system.

[0334] For example, the first screen identifier in this application embodiment can be "\.\DISPLAY1". It should be noted that this application embodiment only illustrates the first screen identifier by way of example. In fact, the first screen identifier can also have other formats. For example, the first screen identifier can be a 64-bit numeric character. This application embodiment does not limit the specific format of the first screen identifier.

[0335] Furthermore, step S1234 also includes step S1234d.

[0336] In step S1234d, AS obtains the first virtual page based on the listening relationship with DMS, performs content analysis processing on the first message to obtain the target application name in the first message, and sends the target application name to DMS.

[0337] It should be noted that the monitoring relationship between AS and DMS can be established after the first electronic device 100 is powered on. AS can continuously monitor DMS to obtain changes in DMS and identify and analyze the content in DMS.

[0338] In this embodiment, when the first link is a card link, the target application name is usually set at the bottom of the card link. In this way, after the AS performs content analysis processing on the first link, the AS can convert the target application name displayed on the first virtual page into data form and send the target application name in data form to the DMS so that the DMS can read it.

[0339] For example, when the first link is a card link, the target application name "Social" can be set at the bottom of the card link. The "Social" displayed on the card link is a page element, which AS can analyze and process to transform the page element form of "Social" into a readable data form.

[0340] It should be noted that different target applications provide card links in different forms. Some card links may have the target application name set, while others may not. This embodiment only uses card links with the target application name set as an example for illustration.

[0341] In step S1235, the simulated click application performs a simulated click operation on the virtual screen for the first message based on the target simulated click path, so that DMS displays the target page 34 on the virtual screen.

[0342] In one implementation, after receiving a click event corresponding to the target simulated click path, the click execution module performs a simulated click operation on the first message on the first virtual page based on the simulated click path M1.

[0343] Figure 14 This is a schematic diagram of the first scenario of performing a simulated click operation on a virtual screen, provided in an embodiment of this application.

[0344] like Figure 14 As shown in the example, after receiving a click event corresponding to the simulated click path M1, the click execution module performs a simulated click operation on the first virtual page based on the simulated click path M1.

[0345] Specifically, DMS creates a virtual screen, displays a first virtual page 35 on the virtual screen, and displays a first message 36 on the first virtual page 35.

[0346] Based on the simulated click path M1, the click module can perform a click operation on the first message 36. In response to the click operation on the first message 36, DMS jumps from the first virtual page 35 to the second virtual page 37 and displays the first virtual button 38 on the second virtual page 37.

[0347] Based on the simulated click path M1, the click module can perform a click operation on the first virtual button 38. In response to the click operation on the first virtual button 38, DMS invokes the first virtual window 39 on the second virtual page 37 and displays the second virtual button 40 on the first virtual window 39.

[0348] In the case where there are multiple first virtual buttons 38, the simulated click path M1 only needs to locate one of them. Based on the simulated click path M1, the click execution module can perform a click operation on the second virtual button 40. In response to the click operation on the second virtual button 40, DMS jumps from the second virtual page 37 to the target page 34.

[0349] It should be noted that the embodiments of this application are only illustrated by simulating the click path M1. When the target simulated click path is another simulated click path, the DMS may have other page jump methods during the process of jumping from the first virtual page 35 to the target page 34. The embodiments of this application do not limit this.

[0350] The following provides examples of other page redirection methods.

[0351] Figure 15 This is a schematic diagram of a second scenario of performing a simulated click operation on a virtual screen, provided in an embodiment of this application.

[0352] like Figure 15 As shown in the example, when the simulated click path is the simulated click path P1 corresponding to the video application, the click execution module performs a simulated click operation on the first virtual page based on the simulated click path P1 after receiving the click event corresponding to the simulated click path P1.

[0353] Specifically, DMS creates a virtual screen, displays a first virtual page 35 on the virtual screen, displays a first message 36 on the first virtual page 35, and displays the target application name 41 in the first message 36.

[0354] Based on the simulated click path P1, the click module can perform a click operation on the first message 36. In response to the click operation on the first message 36, DMS jumps from the first virtual page 35 to the third virtual page 42 and displays the third virtual button 43 on the third virtual page 37.

[0355] Based on the simulated click path P1, the click module can perform a click operation on the third virtual button 43. In response to the click operation on the third virtual button 43, DMS invokes the first virtual panel 44 on the third virtual page 42 and displays the first virtual icon 45 on the first virtual panel 44. For example, the first virtual icon 45 can be the application icon corresponding to the browser application.

[0356] Based on the simulated click path P1, the click module can perform a click operation on the first virtual icon 45. In response to the click operation on the first virtual icon 45, the DMS invokes the second virtual panel 46 on the third virtual page 42 and displays the second virtual icon 47 on the second virtual panel 46. For example, the second virtual icon 47 can be the application icon corresponding to the target application. In this embodiment, the second virtual icon 47 can be the application icon of a video application.

[0357] The second virtual panel 46 can display multiple virtual icons. When the DMS displays the first virtual page 35, since the target application name 41 corresponding to the video application has already been displayed on the page, the DMS can locate the second virtual icon 47 on the second virtual panel 46 based on the target application name 41.

[0358] Furthermore, after DMS locates the second virtual icon 47, the click module can perform a click operation on the second virtual icon 47. In response to the click operation on the second virtual icon 47, DMS jumps from the third virtual page 42 to the target page 34.

[0359] It should be noted that if the target application name is not displayed in the card link, DMS can jump to the target page 34 based on the default target application or other target simulation path settings.

[0360] In step S1236, AS obtains the target page 34 based on the monitoring relationship with DMS, performs content analysis on the target page 34 to obtain page information, and sends the page information to DMS.

[0361] The page information may include various information such as application name, page elements, page theme, application identifier, page source code, and developer tools. This application embodiment does not limit the specific form of the page information.

[0362] Step S1237: Instruct the application to obtain page information from DMS.

[0363] In one implementation, DMS sends page information to the notification listening module.

[0364] In one implementation, the notification listening module can call PMS to obtain page information from DMS, and then obtain page information from PMS based on a callback function.

[0365] This application does not limit the specific method by which the notification application obtains page information from DMS.

[0366] Step S1238: Instruct the application to determine the target application based on the page information and detect whether the first electronic device 100 has the target application set.

[0367] In one implementation, the notification listening module determines the target application based on page information and detects whether the first electronic device 100 has the target application set up. In this embodiment, the notification listening module can determine that the target application is a social application based on page information and detect whether the first electronic device 100 has the social application set up.

[0368] The notification listening module can match page information with the preset application information in the aforementioned embodiments to determine the target application. Alternatively, the notification listening module can directly determine the target application based on fields obtained from AS analysis of the page information. This application embodiment does not limit the specific method by which the notification listening module determines the target application.

[0369] It should be noted that, in the aforementioned steps, although the user did not perform any operation to open the first link, the first electronic device 100 has simulated opening the first link on the virtual screen. During this process, the first electronic device 100 needs to keep the first notification control 32 continuously displayed on the first page 31, and the user should not be aware that the first electronic device 100 has opened the first link. That is, after the first electronic device 100 simulates opening the first link, it does not need to clear the first notification control 32 on the first page 31.

[0370] In step S13, if the first electronic device 100 sets the target application, the first electronic device 100 updates the first notification control 32 to display the first button 33 on the first notification control 32.

[0371] Step S13 includes the following steps S131-S132.

[0372] In step S131, if the notification application determines that the first electronic device 100 is set to a target application, the notification application sends a first update notification to the NMS. The first update notification includes page information and is used to notify the NMS to update the first notification control 32.

[0373] In one implementation, when the notification listening module determines that the first electronic device 100 is configured with a target application, the notification listening module sends a first update notification to the NMS.

[0374] For example, the page information in the first update notification may include the application name of the social application.

[0375] In step S132, the NMS responds to the first update notification by updating the first notification control 32 to display the first button 33 on the first notification control 32.

[0376] In one implementation, in response to a first update notification, the NMS defines the geometric properties, pixel format, and display mode of the first button 33 on the first notification control 32, as well as the display content of the first button 33. For example, the display content can be the application name of a social application. After the definition is completed, the NMS can work with the UI module to update the first notification control 32, thereby displaying the first button 33 on the first notification control 32. It should be noted that if the first electronic device 100 has not set a target application, the first electronic device 100 does not need to update the first notification control 32.

[0377] Step S2 includes the following steps S21-S23.

[0378] Step S21: In response to the NMS receiving the first operation on the first button 33, the application is notified that the first operation has been obtained based on the listening relationship with the NMS.

[0379] In one implementation, the notification listening module obtains the first operation based on its listening relationship with NMS.

[0380] The first operation can be a click operation on the first button 33. In fact, the first operation can also be other types of operations, such as a sliding operation. The specific operation form of the first operation is not limited in this embodiment.

[0381] Step S22: In response to the notification application receiving the first operation, the notification application sends a second instruction to the DMS.

[0382] In one implementation, in response to the notification listening module receiving the first operation, the notification listening module sends a second instruction to the DMS. The second instruction is used to switch to the second screen identifier.

[0383] For example, the notification listening module can have a built-in second screen identifier, such as "\.\DISPLAY2".

[0384] Based on the aforementioned embodiments, when the notification listening module has obtained the first screen identifier "\.\DISPLAY1", the notification listening module can determine that the first screen identifier "\.\DISPLAY1" is not the screen identifier of the physical display screen. In this way, in response to the notification listening module obtaining the first operation, the notification listening module can store the second screen identifier "\.\DISPLAY2" in the second instruction and send the second instruction to the DMS so that the DMS can switch screens based on the second screen identifier.

[0385] In step S23, in response to the second instruction, the DMS switches the first screen identifier to the second screen identifier, so that the display screen jumps from displaying the first page 31 to displaying the target page 34.

[0386] For example, in response to the second instruction, DMS switches the first screen identifier "\.\DISPLAY1" to the second screen identifier "\.\DISPLAY2" so that the display screen jumps from displaying the first page 31 to displaying the target page 34.

[0387] Since the target page 34 has already been displayed on the virtual screen in the preceding steps, the DMS can quickly call up the target page 34 on the virtual screen and display it on the display screen during the screen switching process. This process shortens the display time of the target page 34 and improves the user experience.

[0388] In this embodiment, after the first electronic device 100 receives the first message containing the card link, the first electronic device 100 does not need to rely on the access of a third-party application (such as a chat application) to operate the card link to enter the target page 34. Instead, it can quickly jump from the first page 31 to the target page 34 of the target application (such as a social application). This optimizes the page jump process and improves the user experience.

[0389] The second embodiment of this application is described below as an example.

[0390] Figure 16 This is a schematic diagram of the second scenario of the page redirection method provided in the embodiments of this application.

[0391] like Figure 16 As shown, in some embodiments, the method includes the following steps S1-S2.

[0392] In step S1, in response to receiving a first message sent by a first application in the second electronic device, the first electronic device 100 displays a first notification control 32 corresponding to the first application in the first electronic device 100 on the first page 31, and displays a first button 33 on the first notification control 32.

[0393] This embodiment uses a chat application as the first application and a shopping application as the target application for illustrative purposes.

[0394] For example, a shopping application of a second electronic device sends a first message to a chat application of the second electronic device, causing the chat application of the second electronic device to send a first message to the chat application of the first electronic device 100, the first message including a password link for accessing the shopping application.

[0395] The method by which the second electronic device sends the first message to the first electronic device 100 can be referred to in the foregoing embodiments. Figure 2 In this embodiment, application A1 in electronic device 1 sends a first application message to application B1 in electronic device 1, which in turn causes application B1 in electronic device 1 to send a first application message to application B1 in electronic device 2. That is, the second electronic device can be electronic device 1, the first electronic device 100 can be electronic device 2, and the first message can be a first application message. The specific method by which the second electronic device sends the first message to the first electronic device 100 is not described in detail in this application embodiment.

[0396] In this way, the chat application of the first electronic device 100 can receive the first message.

[0397] This embodiment illustrates the use of a notification mechanism based on a notification center in the first electronic device 100.

[0398] When the first electronic device 100 adopts a notification center-based message notification mechanism, the first page 31 can be a notification center page, and correspondingly, the first notification control 32 can be as follows: Figure 16 The control is shown in the form of a small window.

[0399] In step S2, in response to the first operation of the first button 33, the first electronic device 100 jumps from the first page 31 to the target page 34 associated with the first link.

[0400] Furthermore, based on the foregoing embodiments, since the target application is a shopping application, the first link can be associated with the target page 34 in the shopping application.

[0401] It should be noted that the display format of the target page 34 in this embodiment can be adapted to user habits, such as... Figure 6 As shown in A, users are accustomed to further determining whether to display target page 34, and target page 34 can be referred to in the aforementioned embodiments. Figure 4 In the middle, the page corresponding to the second floating window 24 is displayed on the main screen page 23, such as Figure 6As shown in B, if the user is accustomed to directly opening the target page 34, the target page 34 can be referred to in the aforementioned embodiments. Figure 4 The second application page 6 in this application embodiment does not limit the specific page format of the target page 34.

[0402] In other words, in this embodiment of the application, the first electronic device 100 can quickly jump from the first page 31 to the target page 34 of the target application (e.g., a shopping application) without relying on the access of a third-party application (e.g., a chat application), thus optimizing the page jump process and improving the user experience.

[0403] The specific implementation of the embodiments of this application will be further described below.

[0404] Figure 17 This is the second interactive schematic diagram of the page navigation method provided in the embodiments of this application.

[0405] like Figure 17 As shown, in one implementation, step S1 includes the following steps S31-S33.

[0406] In step S31, in response to receiving a first message sent by a first application in the second electronic device, the first electronic device 100 displays a first notification control 32 on the first page 31.

[0407] Step S31 includes steps S311-S312.

[0408] The specific implementation of steps S311-S312 can be found in steps S111-S112 of the foregoing embodiments, and will not be repeated in this application embodiment.

[0409] In step S32, the first electronic device 100 parses the first message to determine whether the first electronic device 100 has a target application set up.

[0410] Step S32 includes the following steps S321-S323.

[0411] In step S321, the first electronic device 100 parses the first message to obtain the first packet name corresponding to the first message and the text information of the first link.

[0412] The first packet name is the packet name of the sender of the first message, and the sender includes the target application in the second electronic device.

[0413] It should be noted that the sender is the initial generator of the first packet name. For example, in this embodiment of the application, during the process of the shopping application of the second electronic device sending a first message to the chat application therein, so that the chat application of the second electronic device sends a first message to the chat application of the first electronic device 100, if the shopping application is the initial generator of the first packet name, then the first packet name is the packet name of the shopping application.

[0414] Step S321 may include steps S3211-S3212.

[0415] In step S3211, NMS parses the first message to obtain the first packet name and text information.

[0416] In this embodiment, the first package name can be the package name of the shopping application.

[0417] For example, the first package name could be com.xxx.shopping.

[0418] In this embodiment, since the first link is a password link, the text information obtained by NMS may include, for example, the target application name, URL, random string, special characters, etc. This embodiment does not limit the specific content of the text information.

[0419] The method by which NMS obtains text information can be referred to in the foregoing embodiments, and the specific method by which NMS obtains text information is not limited in the embodiments of this application.

[0420] Step S3212: Notify the application to obtain the first packet name and text information based on the listening relationship with NMS.

[0421] The specific implementation of step S3212 can be found in the aforementioned step S1212, and will not be elaborated upon here.

[0422] In step S322, the first electronic device 100 determines the link type of the first link based on the text information.

[0423] Step S322 may include step S3221.

[0424] Step S3221: Instruct the application to determine the link type based on the text information.

[0425] In this embodiment, the notification monitoring module determines the link type as a password link based on the text information.

[0426] In step S323, the first electronic device 100 determines the target application based on the link type and the first package name, and detects whether the first electronic device 100 has set the target application.

[0427] Step S323 includes steps S3231-S3232.

[0428] In step S3231, when the link type is a password link, the first electronic device 100 matches the first package name with at least one preset package name to determine the target package name that matches the first package name from the preset package names.

[0429] Step S3231 includes step S3231a.

[0430] S3231a, when the link type is a password link, instruct the application to match the first package name with the preset package name in order to determine the target package name that matches the first package name from the preset package names.

[0431] In one implementation, the notification listening module matches the first package name with a preset package name to determine the target package name that matches the first package name from the preset package names.

[0432] The method for obtaining the preset package name can be found in the aforementioned embodiments, and will not be repeated here.

[0433] In step S3232, the first electronic device 100 determines the target application based on the target package name and detects whether the first electronic device 100 has set the target application.

[0434] Step S3232 includes step S3232a.

[0435] Step S3232a: Instruct the application to determine the target application based on the target package name and detect whether the first electronic device 100 has set the target application.

[0436] In one implementation, the notification listening module determines the target application based on the target package name and detects whether the first electronic device 100 has the target application set.

[0437] For example, the preset package names include com.xxx.social, com.xxx.shopping, com.xxx.browser, and com.xxx.share. The preset simulated click path associated with com.xxx.social is simulated click path M1, the preset simulated click path associated with com.xxx.shopping is simulated click path M2, the preset simulated click path associated with com.xxx.browser is simulated click path M3, and the preset simulated click path associated with com.xxx.share is simulated click path M4.

[0438] If the first package name is com.xxx.shopping, the first package name can be matched with the preset package name to determine the target package name as com.xxx.shopping.

[0439] In this way, the notification listening module can determine that the target application is a shopping application based on the target package name com.xxx.shopping.

[0440] In one implementation, the notification listening module can further match the text information in the password link with preset application information to determine the target application based on the text information.

[0441] In other words, the notification listening module can determine the target application based on the first package name, text information, or a combination of the first package name and text information. This application embodiment does not limit the specific method by which the notification listening module determines the target application.

[0442] It's important to note that the notification listening module determines the target application based on the link format and the page redirection method corresponding to the password link. This is because the password link doesn't require multiple clicks on the virtual screen; it can be opened simply by copying it to the clipboard. Therefore, the notification listening module doesn't need to display the target page 34 on the virtual screen and determine the target application based on its information. Instead, it can determine the target application based on the first package name and / or text information corresponding to the password link.

[0443] In one implementation, step S324 is included after step S322.

[0444] Step S324: The first electronic device 100 obtains the target simulated click path corresponding to the first package name.

[0445] Step S324 may include step S3241,

[0446] Step S3241: Notify the application to obtain the target simulated click path corresponding to the first package name.

[0447] In one implementation, the notification listening module obtains the target simulated click path corresponding to the first package name. For example, if the target package name is com.xxx.shopping, the notification listening module obtains the target simulated click path associated with the target package name as simulated click path M2.

[0448] It should be noted that the order in which steps S323 and S324 are executed is not limited in the embodiments of this application.

[0449] In step S33, if the first electronic device 100 sets the target application, the first electronic device 100 updates the first notification control 32 to display the first button 33 on the first notification control 32.

[0450] Step S33 includes the following steps S331-S332.

[0451] In step S331, if the notification application determines that the first electronic device 100 has set a target application, the notification application sends a second update notification to the NMS. The second update notification includes text information of a password link and is used to notify the NMS to update the first notification control 32.

[0452] In one implementation, if the notification listening module determines that the first electronic device 100 has a target application set, the notification listening module sends a second update notification to the NMS.

[0453] For example, the text information of the password link in the second update notification may include the application name of the shopping application. In step S332, in response to the second update notification, the NMS updates the first notification control 32 to display the first button 33 on the first notification control 32.

[0454] In one implementation, in response to a first update notification, NMS defines the geometric properties, pixel format, and display mode of the first button 33 on the first notification control 32, as well as the display content of the first button 33. For example, the display content can be the application name of a shopping application. After the definition is completed, NMS can work with the UI module to update the first notification control 32, and then display the first button 33 on the first notification control 32.

[0455] It should be noted that if the first electronic device 100 has not set a target application, the first electronic device 100 does not need to update the first notification control 32.

[0456] Step S2 includes the following steps S41-S43.

[0457] In step S41, in response to the first operation of the first button 33, the first electronic device 100 copies the text information to the clipboard.

[0458] Step S41 includes steps S411-S412.

[0459] Step S411: In response to the NMS receiving the first operation on the first button 33, the application is notified that the first operation has been obtained based on the listening relationship with the NMS.

[0460] In one implementation, the notification listening module obtains the first operation based on its listening relationship with NMS.

[0461] In step S412, in response to the notification application receiving the first operation, the notification application is notified to copy the text information to the clipboard.

[0462] In one implementation, in response to the notification listening module receiving the first operation, the notification listening module copies the text information to the clipboard.

[0463] Step S42, the first electronic device 100 starts the target application.

[0464] Step S42 includes steps S421-S422.

[0465] Step S421: Instruct the application to send a third instruction to the Activity Management Service (AMS).

[0466] In one implementation, the notification listening module sends a third instruction to the Activity Management Service (AMS).

[0467] In step S422, AMS responds to the third instruction and launches the target application.

[0468] In step S43, the first electronic device 100 loads text information from the clipboard in the target application based on the target simulated click path, so that the display screen jumps from displaying the first page 31 to displaying the target page 34.

[0469] Step S43 includes steps S431-S432.

[0470] Step S431: Instruct the application to send the target simulated click path and text information from the clipboard to the simulated click application.

[0471] In step S432, the simulated click application loads text information from the clipboard in the target application based on the target simulated click path, so that the display screen jumps from displaying the first page 31 to displaying the target page 34.

[0472] In one implementation, the path configuration module loads text information from the clipboard in the target application based on the target simulated click path, so that the display screen jumps from displaying the first page 31 to displaying the target page 34.

[0473] For example, the path configuration module loads text information from the clipboard in the shopping application based on a simulated click path M2, so that the display jumps from displaying the first page 31 to displaying the target page 34.

[0474] It should be noted that the simulated click path M2 has different settings, as shown in the example on the target page 34. Figure 4In the case where the page corresponding to the second floating window 24 is displayed on the main screen page 23, the simulated click path M2 is only used to load text information from the clipboard. Thus, after the second floating window 24 is displayed on the main screen page 23, the user can click the second confirmation button 26 in the second floating window 24 to enter the second application page 6.

[0475] In this way, users can choose to enter the second application page 6 within the shopping application, or choose to exit the second application page 6 to enter the main page of the shopping application, resulting in a better user experience.

[0476] On the target page, number 34 is as follows. Figure 4 In the case of the second application page 6, after loading the text information in the clipboard, the simulated click path M2 also needs to perform a simulated click operation on the second confirmation button 26 corresponding to the second floating window 24 so that the display screen jumps from displaying the first page 31 to displaying the target page 34.

[0477] This allows users to quickly open the password link, improving the user experience.

[0478] In other words, during the process of the first electronic device 100 redirecting pages based on the password link, the display screen can redirect to different target pages 34 depending on the different target simulation path settings, so as to adapt to the user's usage habits.

[0479] In this embodiment, after the first electronic device 100 receives the first message 36 containing the password link, the first electronic device 100 does not need to rely on the access of a third-party application (such as a chat application) to operate the password link to enter the target page 34. Instead, it can quickly jump from the first page 31 to the target page 34 of the target application (such as a shopping application). This optimizes the page jump process and improves the user experience.

[0480] The third embodiment of this application is described below by way of example.

[0481] Figure 18 This is a schematic diagram of the third scenario of the page redirection method provided in the embodiments of this application.

[0482] like Figure 18 As shown, in some embodiments, the method includes the following steps S1-S2.

[0483] In step S1, in response to receiving a first message sent by a first application in the second electronic device, the first electronic device 100 displays a first notification control 32 corresponding to the first application in the first electronic device 100 on the first page 31, and displays at least one first button 33 on the first notification control 32.

[0484] This embodiment is only illustrated by using a chat application as the first application and a browser application as the target application.

[0485] For example, a browser application of a second electronic device sends a first message to a chat application therein, causing the chat application of the second electronic device to send a first message to the chat application of the first electronic device 100, the first message including a URL link for accessing the browser application.

[0486] The method by which the second electronic device sends the first message to the first electronic device 100 can be referred to in the foregoing embodiments. Figure 2 In this embodiment, application A1 in electronic device 1 sends a first application message to application B1 in electronic device 1, which in turn causes application B1 in electronic device 1 to send a first application message to application B1 in electronic device 2. That is, the second electronic device can be electronic device 1, the first electronic device 100 can be electronic device 2, and the first message can be a first application message. The specific method by which the second electronic device sends the first message to the first electronic device 100 is not described in detail in this application embodiment.

[0487] It should be noted that when the link type of the first link is a URL link, the first message may include one or more first links. This application embodiment does not limit the specific number of first links in the first message.

[0488] This embodiment is illustrated by way of example, where the first message includes multiple first links.

[0489] In cases where the first message may include multiple first links, the first electronic device 100 displays a first notification control 32 corresponding to the first application in the first electronic device 100 on the first page 31, and displays multiple first buttons 33 on the first notification control 32. The number of first buttons 33 corresponds to the number of first links.

[0490] In this way, the chat application of the first electronic device 100 can receive the first message.

[0491] This embodiment illustrates the use of a notification mechanism based on a notification center in the first electronic device 100.

[0492] When the first electronic device 100 adopts a notification center-based message notification mechanism, the first page 31 can be a notification center page, and correspondingly, the first notification control 32 can be as follows: Figure 18 The control is shown in the form of a small window.

[0493] In step S2, in response to the first operation of the first button 33, the first electronic device 100 jumps from the first page 31 to the target page 34 associated with the first link.

[0494] Furthermore, based on the foregoing embodiments, since the target application is a browser application, the first link can be associated with the target page 34 in the browser application.

[0495] Target page 34 can be referred to in the foregoing embodiments. Figure 5 The second application page 6 in this application embodiment does not limit the specific page format of the target page 34.

[0496] It should be noted that when the first message 36 includes multiple first links, each first link can link to a target page 34. Thus, in response to a first operation on different first buttons 33, the first electronic device 100 jumps from the first page 31 to a different target page 34 associated with the first link.

[0497] In other words, in this embodiment of the application, the first electronic device 100 can quickly jump from the first page 31 to the target page 34 of the target application (e.g., a browser application) without relying on the access of a third-party application (e.g., a chat application), thus optimizing the page jump process and improving the user experience.

[0498] The specific implementation of the embodiments of this application will be further described below.

[0499] Figure 19 This is the second interactive schematic diagram of the page navigation method provided in the embodiments of this application.

[0500] like Figure 19 As shown, in one implementation, step S1 includes the following steps S51-S53.

[0501] In step S51, in response to receiving a first message 36 sent by a first application in the second electronic device, the first electronic device 100 displays a first notification control 32 on the first page 31.

[0502] Step S51 includes steps S511-S512.

[0503] The implementation of steps S511-S512 can be found in steps S111-S112 of the foregoing embodiments, and will not be repeated in this application embodiment.

[0504] In step S52, the first electronic device 100 parses the first message to determine whether the first electronic device 100 has a target application set up.

[0505] Step S52 includes the following steps S521-S523.

[0506] In step S521, the first electronic device 100 parses the first message to obtain the first packet name corresponding to the first message and the text information of the first link.

[0507] The first packet name is the packet name of the sender of the first message, and the sender includes the target application in the second electronic device.

[0508] It should be noted that the sender is the initial generator of the first packet name. For example, in this embodiment of the application, when the browser application of the second electronic device sends a first message to the chat application therein, so that the chat application of the second electronic device sends a first message to the chat application of the first electronic device 100, the browser application is the initial generator of the first packet name, and the first packet name is the packet name of the browser application.

[0509] Step S521 may include steps S5211-S5212.

[0510] In step S5211, NMS parses the first message to obtain the first packet name and text information.

[0511] For example, the first package name could be com.xxx.browser.

[0512] In this embodiment, since the first link is a URL link, the text information obtained by NMS may include, for example, protocol fields (such as http, https, ftp, etc.), username, server domain name, and the port number the server is listening on. This embodiment does not limit the specific content of the text information.

[0513] The method by which NMS obtains text information can be referred to in the foregoing embodiments, and the specific method by which NMS obtains text information is not limited in the embodiments of this application.

[0514] Step S5212: Notify the application to obtain the first packet name and text information based on the listening relationship with NMS.

[0515] The specific implementation of step S5212 can be found in step S1212 of the foregoing embodiments, and will not be repeated in this application embodiment.

[0516] In step S522, the first electronic device 100 determines the link type of the first link based on the text information.

[0517] Step S522 may include step S5221.

[0518] Step S5221: Instruct the application to determine the link type based on the text information.

[0519] In this embodiment, the notification monitoring module determines the link type as a URL link based on the text information.

[0520] In step S523, the first electronic device 100 determines the target application based on the link type and the first package name, and detects whether the first electronic device 100 has set the target application.

[0521] In the case of a URL link, the first electronic device 100 obtains the target simulated click path corresponding to the first package name.

[0522] After obtaining the target simulated click path, the first electronic device 100 creates a virtual screen and performs a simulated click operation on the virtual screen based on the target simulated click path to display the target page 34 on the virtual screen.

[0523] Furthermore, the first electronic device 100 acquires page information of the target page 34 to determine the target application based on the page information.

[0524] The implementation method of step S523 will be further explained below.

[0525] Specifically, step S523 may include steps S5231-S5238.

[0526] Step S5231: Notify the application to obtain the target simulated click path corresponding to the first package name.

[0527] Step S5231 includes steps S5231a-S5231b.

[0528] Step S5231a: Instruct the application to match the first package name with at least one preset package name to determine the target package name that matches the first package name from the preset package names.

[0529] In one implementation, the notification listening module matches the first package name with at least one preset package name to determine the target package name that matches the first package name from the preset package names.

[0530] For example, the default package names include com.xxx.social, com.xxx.shopping, com.xxx.browser, and com.xxx.share.

[0531] The default simulated click path associated with com.xxx.social is simulated click path M1, the default simulated click path associated with com.xxx.shopping is simulated click path M2, the default simulated click path associated with com.xxx.browser is simulated click path M3, and the default simulated click path associated with com.xxx.share is simulated click path M4.

[0532] If the first package name is com.xxx.browser, the first package name can be matched with the preset package name to determine the target package name as com.xxx.browser.

[0533] Step S5231b: Instruct the application to obtain the target simulated click path associated with the target package name from the preset simulated click path.

[0534] In one implementation, the notification listening module obtains the target simulated click path associated with the target package name from the preset simulated click path.

[0535] For example, if the target package name is com.xxx.browser, the notification listening module obtains the target simulated click path associated with the target package name as simulated click path M3.

[0536] The process of obtaining the preset package name and preset simulated click path can be referred to the foregoing embodiments, and will not be repeated here.

[0537] Step S5232: Notify the application to send the target simulated click path to the simulated click application.

[0538] Based on the aforementioned example, the notification listening module sends the simulated click path M3 to the path configuration module.

[0539] Correspondingly, in response to the notification listening module sending a simulated click path M3 to the path configuration module, the click event module sends a click event corresponding to the simulated click path M3 to the click execution module.

[0540] In one implementation, if the first message 36 includes multiple URL links, the simulated click path M3 may include multiple simulated click sub-paths, such as simulated click sub-path M31, simulated click sub-path M32, and simulated click sub-path M33. Accordingly, the click event module sends multiple click events corresponding to the simulated click sub-paths to the click execution module.

[0541] Step S5233: After receiving the target simulated click path, the simulated click application sends the first instruction to the DMS.

[0542] In one implementation, the path configuration module sends a first instruction to the DMS after receiving the target simulated click path.

[0543] In step S5234, DMS responds to the first instruction by creating a virtual screen.

[0544] Step S5234 includes step S5234a.

[0545] In step S5234a, the DMS responds to the first instruction to create a virtual screen, displays a first virtual page on the virtual screen, and displays a first message 36 on the first virtual page, wherein the first virtual page includes the application page of the first application in the first electronic device 100.

[0546] It should be noted that after DMS creates a virtual screen, DMS can send an application launch command to AMS to start the first application. In response to the application launch command, AMS starts the first application so that DMS can display the first virtual page on the virtual screen and display the first message 36 on the first virtual page.

[0547] In this embodiment, when the first application is a browser application, the page format of the first virtual page can be referred to the aforementioned embodiments. Figure 5 The fourth application page 15. The page format of the first virtual page will not be described in detail in this embodiment.

[0548] Step S5234 also includes steps S5234b-S5234c.

[0549] In step S5234b, after creating the virtual screen, DMS obtains the first screen identifier of the virtual screen.

[0550] In step S5234c, the DMS sends the first screen identifier to the notification application so that the notification application can obtain the first screen identifier.

[0551] In one implementation, DMS sends the first screen identifier to the notification listening module so that the notification listening module can obtain the first screen identifier.

[0552] For example, the first screen identifier in this application embodiment can be "\.\DISPLAY1".

[0553] In step S5235, the simulated click application performs a simulated click operation on the first message 36 on the virtual screen based on the target simulated click path, so that the DMS displays the target page 34 on the virtual screen.

[0554] In one implementation, after receiving a click event corresponding to the target simulated click path, the click execution module performs a simulated click operation on the first message 36 on the first virtual page based on the simulated click path M3.

[0555] Figure 20 This is a schematic diagram of a third scenario of performing a simulated click operation on a virtual screen, provided in an embodiment of this application.

[0556] like Figure 20 As shown in the example, after receiving a click event corresponding to the simulated click path M3, the click execution module performs a simulated click operation on the first virtual page based on the simulated click path M3.

[0557] Specifically, DMS creates a virtual screen, displays a first virtual page 35 on the virtual screen, displays a first message 36 on the first virtual page 35, and displays a first link 48 in the first message 36.

[0558] This embodiment is illustrated by exemplifying the inclusion of multiple first links 48 in the first message 36. For example, the number of first links 48 is three.

[0559] Based on the simulated click sub-path M31, the click module can perform a click operation on the first first link 44 in the first message 36. In response to the click operation on the first first link 44, DMS jumps from the first virtual page 35 to the target page 34 corresponding to the first first link 44.

[0560] Based on the simulated click sub-path M32, the click execution module can perform a click operation on the second first link 44 in the first message 36. In response to the click operation on the second first link 44, DMS can create a new virtual screen so that the first virtual page 35 can jump to the target page 34 corresponding to the second first link 44 (not shown in the figure) on the new virtual screen.

[0561] Based on the simulated click sub-path M33, the click execution module can perform a click operation on the third first link 44 in the first message 36. In response to the click operation on the third first link 44, DMS can create a new virtual screen so that the first virtual page 35 can jump to the target page 34 corresponding to the third first link 44 (not shown in the figure) on the new virtual screen.

[0562] In this way, DMS has multiple virtual screens, and each virtual screen displays a target page 34.

[0563] It should be noted that during the process of creating a new virtual screen, DMS can obtain the first screen identifier of the new virtual screen.

[0564] For example, the first screen identifier in this application embodiment may also include "\.\DISPLAY3" and "\.\DISPLAY4".

[0565] In step S5236, AS obtains the target page 34 based on the monitoring relationship with DMS, performs content analysis processing on the target page 34 to obtain page information, and sends the page information to DMS.

[0566] In one implementation, when displaying multiple target pages 34, the AS needs to acquire multiple target pages 34, perform content analysis processing on each target page 34 to obtain page information for each target page 34, and send the page information of each target page 34 to the DMS.

[0567] In step S5237, DMS sends the page information to the notification application.

[0568] In one implementation, DMS sends page information to the notification listening module.

[0569] Step S5238: The application is notified to determine the target application based on the page information and to detect whether the first electronic device 100 has the target application set.

[0570] In this embodiment, the notification monitoring module can determine that the target application is a browser application based on the page information, and detect whether the first electronic device 100 has a browser application set.

[0571] In step S53, if the first electronic device 100 sets the target application, the first electronic device 100 updates the first notification control 32 to display the first button 33 on the first notification control 32.

[0572] Step S53 includes the following steps S531-S532.

[0573] In step S531, if the notification application determines that the first electronic device 100 is set to a target application, the notification application sends a first update notification to the NMS. The first update notification includes page information and is used to notify the NMS to update the first notification control 32.

[0574] For example, the page information in the first update notification may include the page title of the target page 34. In step S532, in response to the first update notification, the NMS updates the first notification control 32 to display the first button 33 on the first notification control 32.

[0575] Based on the foregoing embodiments, since the first notification control 32 can display multiple first buttons 33, each first button 33 can display different page titles corresponding to different target pages 34.

[0576] It should be noted that if the first electronic device 100 has not set a target application, the first electronic device 100 does not need to update the first notification control 32.

[0577] Step S2 includes the following steps S61-S63.

[0578] Step S61: In response to the NMS receiving the first operation on the first button 33, the application is notified that the first operation has been obtained based on the listening relationship with the NMS.

[0579] In step S62, in response to the notification application receiving the first operation, the notification application sends a second instruction to the DMS.

[0580] In one implementation, in response to the notification listening module receiving the first operation, the notification listening module sends a second instruction to the DMS.

[0581] For example, the notification listening module can have a built-in second screen identifier, such as "\.\DISPLAY2".

[0582] Based on the aforementioned embodiments, when the notification listening module has obtained the first screen identifier "\.\DISPLAY1", the notification listening module can determine that the first screen identifiers "\.\DISPLAY1", "\.\DISPLAY3", and "\.\DISPLAY4" are not screen identifiers of the physical display screen. Thus, in response to the notification listening module obtaining the first operation, the notification listening module can store the second screen identifier "\.\DISPLAY2" in the second instruction and send the second instruction to the DMS so that the DMS can switch screens based on the second screen identifier.

[0583] In step S63, in response to the second instruction, the DMS switches the first screen identifier to the second screen identifier, so that the display screen jumps from displaying the first page 31 to displaying the target page 34.

[0584] For example, in response to the second instruction, DMS switches the first screen identifier "\.\DISPLAY1" to the second screen identifier "\.\DISPLAY2" so that the display shows the target page 34.

[0585] Since the target page 34 has already been displayed on the virtual screen in the preceding steps, the DMS can quickly call up the target page 34 on the virtual screen and display it on the display screen during the screen switching process. This process shortens the page display time and improves the user experience.

[0586] In this embodiment, after the first electronic device 100 receives the first message containing the URL link, the first electronic device 100 does not need to rely on the access of a third-party application (such as a chat application) to operate the URL link to enter the target page 34. Instead, it can quickly jump from the first page 31 to the target page 34 of the target application (such as a browser application). This optimizes the page jump process and improves the user experience.

[0587] The fourth embodiment of this application is described below by way of example.

[0588] In one implementation, a target application in the second electronic device can send a first message 36 to a file-sharing function in the first electronic device 100 based on the file-sharing function in the second electronic device. The first message 36 includes a first link for accessing the target application.

[0589] Figure 21 This is a schematic diagram of the fourth scenario of the page redirection method provided in the embodiments of this application.

[0590] Figure 22 This is the third method flowchart of the page redirection method provided in the embodiments of this application.

[0591] like Figure 21 and Figure 22 As shown, in some embodiments, the method includes the following steps S7-S8.

[0592] In step S7, in response to receiving a first message sent by the file sharing function in the second electronic device, the first electronic device 100 displays a first notification control 32 corresponding to the file sharing function in the first electronic device 100 on the first page 31, and displays a first button 33 on the first notification control 32. The first message includes a first link for entering the target application, and the first notification control is used to notify the user that the first message has been received.

[0593] This embodiment uses a video application as the target application for illustrative purposes.

[0594] For example, the file sharing function of the second electronic device sends a first message to the file sharing function of the first electronic device 100, the first message including a sharing link corresponding to the file sharing function.

[0595] It should be noted that, in order to adapt to the technical solution provided in this application, the sharing link format of the file sharing function in this embodiment has been modified. The original sharing link may have only contained a URL link. The sharing link provided in this embodiment may contain the target application name and the URL link. In this way, the target application name can be used to locate the target application, and the URL link can be used to enter the target page 34.

[0596] The method by which the second electronic device sends the first message to the first electronic device 100 can be referred to in the foregoing embodiments. Figure 6 In this embodiment, the file sharing function of electronic device 1 sends a file sharing message to the file sharing function of user B's electronic device 2. That is, the second electronic device can be electronic device 1, the first electronic device 100 can be electronic device 2, and the first message can be a file sharing message. This application embodiment does not elaborate on the specific method by which the second electronic device sends the first message to the first electronic device 100.

[0597] In this way, the file sharing function of the first electronic device 100 can receive the first message.

[0598] This embodiment illustrates the use of a notification mechanism based on a notification center in the first electronic device 100.

[0599] When the first electronic device 100 adopts a notification center-based message notification mechanism, the first page 31 can be a notification center page, and correspondingly, the first notification control 32 can be as follows: Figure 21 The control is shown in the form of a small window.

[0600] In step S8, in response to the first operation of the first button 33, the first electronic device 100 jumps from the first page 31 to the target page 34 associated with the first link, and the target page 34 is the application page of the target application.

[0601] Target page 34 can be referred to in the foregoing embodiments. Figure 3 The second application page 6 in this application embodiment does not limit the specific page format of the target page 34.

[0602] In other words, in this embodiment of the application, the first electronic device 100 can quickly jump from the first page 31 to the target page 34 of the target application (e.g., video application) without relying on the access of a third-party application (e.g., a note-taking application), thus optimizing the page jump process and improving the user experience.

[0603] The specific implementation of the embodiments of this application will be further described below.

[0604] Figure 23 This is the fourth interactive schematic diagram of the page navigation method provided in the embodiments of this application.

[0605] like Figure 23 As shown, in one implementation, step S1 includes the following steps S71-S73.

[0606] In step S71, in response to receiving a first message sent by the file sharing function in the second electronic device, the first electronic device 100 displays a first notification control 32 on the first page 31.

[0607] Step S71 includes steps S711-S712.

[0608] The implementation of steps S711-S712 can be found in steps S111-S112 of the foregoing embodiments, and will not be repeated in this application embodiment.

[0609] In step S72, the first electronic device 100 parses the first message to determine whether the first electronic device 100 has a target application set up.

[0610] Step S72 includes the following steps S721-S723.

[0611] In step S721, the first electronic device 100 parses the first message to obtain the first packet name corresponding to the first message and the text information of the first link.

[0612] Here, the first packet name is the packet name of the sender of the first message, and the sender includes the file sharing function in the second electronic device. It should be noted that the sender is the initial generator of the first packet name. For example, in this embodiment of the application, during the process of the file sharing function of the second electronic device sending the first message to the file sharing function of the first electronic device 100, if the file sharing function is the initial generator of the first packet name, then the first packet name is the packet name of the file sharing function.

[0613] Step S721 may include steps S7211-S7212.

[0614] In step S7211, NMS parses the first message to obtain the first packet name and text information.

[0615] For example, the first package name could be com.xxx.share.

[0616] In this embodiment, since the first link is a sharing link corresponding to the file sharing function, the text information obtained by NMS may include, for example, the target application name, URL, etc. This embodiment does not limit the specific content of the text information.

[0617] The method by which NMS obtains text information can be referred to in the foregoing embodiments, and the specific method by which NMS obtains text information is not limited in the embodiments of this application.

[0618] Step S7212: Notify the application to obtain the first packet name and text information based on the listening relationship with NMS.

[0619] In one implementation, the notification listening module obtains the first packet name and text information based on its listening relationship with NMS.

[0620] In step S722, the first electronic device 100 determines the link type of the first link based on the text information.

[0621] Step S722 may include step S7221.

[0622] Step S7221: Instruct the application to determine the link type based on the text information.

[0623] In one implementation, the notification listening module determines the link type based on text information.

[0624] In this embodiment, the notification monitoring module can determine the link type as a sharing link corresponding to the file sharing function based on the text information.

[0625] In step S723, the first electronic device 100 determines the target application based on the link type and the first package name, and detects whether the first electronic device 100 has set the target application.

[0626] In the case of a link type that is a shareable link, the first electronic device 100 obtains the target simulated click path corresponding to the first package name.

[0627] After obtaining the target simulated click path, the first electronic device 100 creates a virtual screen and performs a simulated click operation on the virtual screen based on the target simulated click path to display the target page 34 on the virtual screen.

[0628] Furthermore, the first electronic device 100 acquires page information of the target page 34 to determine the target application based on the page information.

[0629] The implementation method of step S723 will be further explained below.

[0630] Specifically, step S723 may include steps S7231-S7238.

[0631] Step S7231: Notify the application to obtain the target simulated click path corresponding to the first package name.

[0632] Step S7231 includes steps S7231a-S7231b.

[0633] Step S7231a: Instruct the application to match the first package name with at least one preset package name to determine the target package name that matches the first package name from the preset package names.

[0634] In one implementation, the notification listening module matches the first package name with a preset package name to determine the target package name that matches the first package name from the preset package names.

[0635] For example, the default package names include com.xxx.social, com.xxx.shopping, com.xxx.browser, and com.xxx.share.

[0636] The default simulated click path associated with com.xxx.social is simulated click path M1, the default simulated click path associated with com.xxx.shopping is simulated click path M2, the default simulated click path associated with com.xxx.browser is simulated click path M3, and the default simulated click path associated with com.xxx.share is simulated click path M4.

[0637] If the first package name is com.xxx.share, the first package name can be matched with the preset package name to determine the target package name as com.xxx.share.

[0638] Step S7231b: Instruct the application to obtain the target simulated click path associated with the target package name from the preset simulated click path.

[0639] In one implementation, the notification listening module obtains the target simulated click path associated with the target package name from the preset simulated click path.

[0640] For example, if the target package name is com.xxx.share, the notification listening module obtains the target simulated click path associated with the target package name as simulated click path M4.

[0641] The process of obtaining the preset package name and preset simulated click path can be referred to the foregoing embodiments, and will not be repeated here.

[0642] Step S7232: Notify the application to send the target simulated click path to the simulated click application.

[0643] Based on the aforementioned example, the notification listening module will send the simulated click path M4 to the path configuration module.

[0644] Correspondingly, in response to the notification listening module sending the simulated click path M4 to the path configuration module, the click event module sends the click event corresponding to the simulated click path M4 to the click execution module.

[0645] Step S7233: After receiving the target simulated click path, the simulated click application sends the first instruction to the DMS.

[0646] In one implementation, the path configuration module sends a first instruction to the DMS after receiving the target simulated click path.

[0647] In step S7234, DMS responds to the first instruction by creating a virtual screen.

[0648] Step S7234 includes step S7234a.

[0649] In step S7234a, the DMS responds to the first instruction to create a virtual screen, displays a first virtual page on the virtual screen, and displays a first message 36 on the first virtual page, wherein the first virtual page includes the application page of the first application in the first electronic device 100.

[0650] It should be noted that after DMS creates a virtual screen, DMS can send an application launch command to AMS to start the first application. In response to the application launch command, AMS starts the first application so that DMS can display the first virtual page on the virtual screen and display the first message 36 on the first virtual page.

[0651] In this embodiment, when the first application is a note-taking application, the page format of the first virtual page can be referred to the aforementioned embodiments. Figure 7 The sixth application page 29. The page format of the first virtual page will not be described in detail in this embodiment.

[0652] Step S7234 also includes steps S7234b-S7234c.

[0653] In step S7234b, after creating the virtual screen, DMS obtains the first screen identifier of the virtual screen.

[0654] In step S7234c, the DMS sends the first screen identifier to the notification application so that the notification application can obtain the first screen identifier.

[0655] In one implementation, DMS sends the first screen identifier to the notification listening module so that the notification listening module can obtain the first screen identifier.

[0656] For example, the first screen identifier in this application embodiment can be "\.\DISPLAY1".

[0657] Furthermore, step S7234 also includes step S7234d.

[0658] In step S7234d, the AS obtains the first virtual page based on the listening relationship with the DMS, performs content analysis processing on the first message to obtain the target application name in the first message, and sends the target application name to the DMS.

[0659] In step S7235, the simulated click application performs a simulated click operation on the virtual screen for the first message based on the target simulated click path, so that the DMS displays the target page 34 on the virtual screen.

[0660] In one implementation, after receiving a click event corresponding to the target simulated click path, the click execution module performs a simulated click operation on the first message based on the simulated click path M4 on the first virtual page.

[0661] Figure 24 This is a schematic diagram of the fourth scenario of performing a simulated click operation on a virtual screen, provided in the embodiments of this application.

[0662] like Figure 24 As shown in the example, after receiving a click event corresponding to the simulated click path M4, the click execution module performs a simulated click operation on the first virtual page based on the simulated click path M4.

[0663] Specifically, DMS creates a virtual screen, displays a first virtual page 35 on the virtual screen, displays a first message 36 on the first virtual page 35, and displays a share link in the first message 36. The share link includes the target application name 49 and the target URL 50.

[0664] Based on the simulated click path M4, DMS can open the target application corresponding to the target application name 49 through the Intent object, and load the target URL 47 in the target application. In this way, DMS jumps from the first virtual page 35 to the target page 34.

[0665] In step S7236, AS obtains the target page 34 based on the monitoring relationship with DMS, performs content analysis on the target page 34 to obtain page information, and sends the page information to DMS.

[0666] In step S7237, DMS sends the page information to the notification application.

[0667] In one implementation, DMS sends page information to the notification listening module.

[0668] Step S7238: Instruct the application to determine the target application based on the page information and detect whether the first electronic device 100 has the target application set.

[0669] In one implementation, the notification monitoring module determines the target application based on page information and detects whether the first electronic device 100 has the target application enabled. In this embodiment, the notification monitoring module can determine that the target application is a video application based on page information and detect whether the first electronic device 100 has a video application enabled.

[0670] In step S73, if the first electronic device 100 sets the target application, the first electronic device 100 updates the first notification control 32 to display the first button 33 on the first notification control 32.

[0671] Step S73 includes the following steps S731-S732.

[0672] In step S731, if the notification application determines that the first electronic device 100 is configured with a target application, the notification application sends a first update notification to the NMS.

[0673] For example, the page information in the first update notification may include the application name of the video application.

[0674] In step S732, the NMS responds to the first update notification by updating the first notification control 32 to display the first button 33 on the first notification control 32.

[0675] It should be noted that if the first electronic device 100 has not set a target application, the first electronic device 100 does not need to update the first notification control 32.

[0676] Step S8 includes the following steps S81-S83.

[0677] Step S81: In response to the NMS receiving the first operation on the first button 33, the application is notified that the first operation has been obtained based on the listening relationship with the NMS.

[0678] In one implementation, the notification listening module obtains the first operation based on its listening relationship with NMS.

[0679] In step S82, in response to the notification application receiving the first operation, the notification application sends a second instruction to the DMS.

[0680] In one implementation, in response to the notification listening module receiving the first operation, the notification listening module sends a second instruction to the DMS.

[0681] For example, the notification listening module can have a built-in second screen identifier, such as "\.\DISPLAY2".

[0682] Based on the aforementioned embodiments, when the notification listening module has obtained the first screen identifier "\.\DISPLAY1", the notification listening module can determine that the first screen identifier "\.\DISPLAY1" is not the screen identifier of the physical display screen. In this way, in response to the notification listening module obtaining the first operation, the notification listening module can store the second screen identifier "\.\DISPLAY2" in the second instruction and send the second instruction to the DMS so that the DMS can switch screens based on the second screen identifier.

[0683] In step S83, in response to the second instruction, the DMS switches the first screen identifier to the second screen identifier, so that the display screen jumps from displaying the first page 31 to displaying the target page 34.

[0684] For example, in response to the second instruction, DMS switches the first screen identifier "\.\DISPLAY1" to the second screen identifier "\.\DISPLAY2" so that the display screen jumps from displaying the first page 31 to displaying the target page 34.

[0685] Since the target page 34 has already been displayed on the virtual screen in the preceding steps, the DMS can quickly call up the target page 34 on the virtual screen and display it on the display screen during the screen switching process. This process shortens the page display time and improves the user experience.

[0686] In this embodiment, after the first electronic device 100 receives the first message 36 containing the sharing link, the first electronic device 100 does not need to rely on the access of a third-party application (such as a note-taking application) to operate the sharing link to enter the target page 34. Instead, it can quickly jump from the first page 31 to the target page 34 of the target application (such as a video application). This optimizes the page jump process and improves the user experience.

[0687] Figure 25 This is the fourth method flowchart of the page redirection method provided in the embodiments of this application.

[0688] like Figure 25 As shown, in some embodiments, the method includes the following steps S100-S200.

[0689] In step S100, in response to receiving the first message, the first electronic device displays a first notification control on the first page and displays a first button on the first notification control, wherein the first message includes a first link for entering the target application, and the first notification control is used to notify the user that the first message has been received.

[0690] In step S200, in response to the first operation of the first button, the first electronic device jumps from the first page to the target page associated with the first link, the target page being the application page of the target application.

[0691] The page jump method provided in this application embodiment allows a first electronic device to display a first button in a first notification control corresponding to the first message after receiving a first message containing a first link. In this way, after the user clicks the first button, the first electronic device can quickly jump from the first page to the target page of the target application without relying on the access of a third-party application, thus optimizing the page jump process and improving the user experience.

[0692] The foregoing primarily describes the solutions provided in the embodiments of this application from the perspective of electronic devices. It is understood that, in order to achieve the aforementioned functions, the electronic device includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the page navigation method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed through hardware or by software-driven hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0693] This application embodiment can divide the above-described electronic device into functional modules or functional units according to the above method examples. For example, each function can be divided into its own functional modules or functional units, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module or functional unit. The module or unit division in this application embodiment is illustrative and represents only one logical functional division; other division methods may be used in actual implementation.

[0694] This application also provides a page navigation device applied to an electronic device. The page navigation device includes:

[0695] The display module is used to display a first notification control on a first page in response to receiving a first message, and to display a first button on the first notification control. The first message includes a first link for entering a target application, and the first notification control is used to notify the user that the first message has been received.

[0696] The jump module is used to respond to the first operation of the first button and jump from the first page to the target page associated with the first link. The target page is the application page of the target application.

[0697] The page jump device provided in this application embodiment allows a first electronic device to display a first button in a first notification control corresponding to the first message after receiving a first message containing a first link. In this way, after the user clicks the first button, the first electronic device can quickly jump from the first page to the target page of the target application without relying on the access of a third-party application, thus optimizing the page jump process and improving the user experience.

[0698] This application also provides an electronic device, including a processor and a memory; the memory stores program instructions, which, when executed by the processor, cause the electronic device to execute the page jump method in any of the above embodiments.

[0699] Figure 26 This is a schematic diagram of the structure of a chip system provided in an embodiment of this application.

[0700] like Figure 26 As shown, the chip system 300 provided in this application embodiment, for example, a SoC, includes at least one processor 301 and at least one interface circuit 302. The processor 301 and the interface circuit 302 are interconnected via lines. For example, the interface circuit 302 can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit 302 can be used to send signals to other devices (e.g., the processor 301 or the touchscreen of an electronic device). Exemplarily, the interface circuit 302 can read instructions stored in the memory and send the instructions to the processor 301. When the instructions are executed by the processor 301, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in this application embodiment.

[0701] This application also provides a computer-readable storage medium including computer instructions that, when executed on the electronic device, cause the electronic device to perform the various functions or steps described in the method embodiments.

[0702] This application also provides a computer program product that, when run on a computer, causes the computer to perform the various functions or steps described in the above method embodiments.

[0703] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0704] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0705] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0706] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0707] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0708] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A page jump method, characterized by, Applied to a first electronic device, including: In response to receiving a first message, a first notification control is displayed on a first page, and a first button is displayed on the first notification control, wherein the first message includes a first link for accessing a target application, and the first notification control is used to notify the user that the first message has been received; In response to a first operation on the first button, the user is redirected from the first page to a target page associated with the first link, the target page being the application page of the target application.

2. The page jump method of claim 1, wherein, The step of responding to receiving a first message by displaying a first notification control on a first page and displaying a first button on the first notification control includes: In response to receiving the first message sent by the first application in the second electronic device, the first notification control corresponding to the first application in the first electronic device is displayed on the first page, and the first button is displayed on the first notification control, wherein the second electronic device is the peer device of the first electronic device.

3. The page jump method of claim 1, wherein, The step of responding to receiving a first message by displaying a first notification control on a first page and displaying a first button on the first notification control includes: In response to receiving the first message sent by the file sharing function in the second electronic device, the first notification control corresponding to the file sharing function in the first electronic device is displayed on the first page, and the first button is displayed on the first notification control, wherein the second electronic device is the peer device of the first electronic device, and the file sharing function is a built-in function of the electronic device.

4. The page jump method according to claim 2 or 3, characterized by, The step of responding to receiving a first message by displaying a first notification control on a first page and displaying a first button on the first notification control includes: In response to receiving the first message, the first notification control is displayed on the first page; The first message is parsed to determine whether the first electronic device has the target application set. When the target application is set on the first electronic device, the first notification control is updated to display the first button on the first notification control.

5. The page jump method of claim 4, wherein, The step of parsing the first message to determine whether the first electronic device has the target application set includes: The first message is parsed to obtain the first packet name corresponding to the first message and the text information of the first link. The first packet name is the packet name of the sender that sent the first message. The sender includes the target application in the second electronic device or the file sharing function in the second electronic device. Based on the first package name, and / or the text information, it is determined whether the first electronic device has the target application set.

6. The page jump method of claim 5, wherein, The step of determining whether the first electronic device has the target application set based on the first package name and / or the text information includes: The link type of the first link is determined based on the text information, wherein the link type includes at least one of card link, password link, Uniform Resource Locator (URL) link, and share link corresponding to the file sharing function; The target application is determined based on the link type and the first package name, and it is detected whether the first electronic device has the target application set.

7. The page jump method of claim 6, wherein, The step of displaying the first notification control on the first page in response to receiving the first message includes: In response to the Notification Management Service (NMS) receiving the first message, the NMS determines the attributes of the first notification control corresponding to the first message; The NMS causes the first page to display the first notification control based on the properties of the first notification control.

8. The page jump method of claim 7, wherein, The step of parsing the first message to obtain the first package name corresponding to the first message and the text information of the first link includes: The NMS parses the first message to obtain the first packet name and the text information; The notification application obtains the first package name and the text information based on its listening relationship with the NMS.

9. The page jump method of claim 8, wherein, Determining the link type of the first link based on the text information includes: The notification application determines the link type based on the text information.

10. The page jump method of claim 9, wherein, Determining the target application based on the link type and the first package name includes: When the link type is the card link, the URL link, or the share link, obtain the target simulated click path corresponding to the first package name, wherein the target simulated click path is pre-stored in the first electronic device; After obtaining the target simulated click path, a virtual screen is created; Based on the target simulated click path, a simulated click operation is performed on the virtual screen to display the target page on the virtual screen; Obtain page information of the target page to determine the target application based on the page information.

11. The page jump method of claim 10, wherein, After creating the virtual screen, the process also includes: Obtain the first screen identifier of the virtual screen, wherein each screen has a corresponding screen identifier.

12. The page jump method of claim 11, wherein, The step of responding to a first operation on the first button and navigating from the first page to a target page associated with the first link includes: In response to the first operation on the first button, the first screen identifier is switched to the second screen identifier, so that the display screen jumps from displaying the first page to displaying the target page, wherein the display screen corresponds to the second screen identifier.

13. The page jump method of claim 12, wherein, The step of determining the target application based on the link type and the first package name, and detecting whether the first electronic device has the target application set, includes: When the link type is the card link, the URL link, or the share link, the notification application obtains the target simulated click path corresponding to the first package name; The notification application sends the target simulated click path to the simulated click application; After receiving the target simulated click path, the simulated click application sends a first instruction to the Display Management Service (DMS). The DMS creates a virtual screen in response to the first instruction; The simulated click application performs a simulated click operation on the virtual screen based on the target simulated click path, so that the DMS displays the target page on the virtual screen; Accessibility Service AS obtains the target page based on the monitoring relationship with DMS, performs content analysis on the target page to obtain the page information, and sends the page information to DMS; The notification application obtains the page information from the DMS; The notification application determines the target application based on the page information and detects whether the first electronic device has the target application set.

14. The page jump method of claim 13, wherein, The notification application obtains the target simulated click path corresponding to the first package name, including: The notification application matches the first package name with at least one preset package name to determine a target package name that matches the first package name from the preset package names, wherein each preset package name has an associated preset simulated click path; The notification application obtains the target simulated click path associated with the target package name from the preset simulated click path.

15. The page jump method of claim 14, wherein, The DMS responds to the first instruction by creating a virtual screen, including: The DMS responds to the first instruction by creating a virtual screen, displaying a first virtual page on the virtual screen, and displaying the first message on the first virtual page, wherein the first virtual page includes the application page of a first application in the first electronic device, or the application page of an application associated with the file sharing function in the first electronic device.

16. The page jump method of claim 15, wherein, The simulated click application performs a simulated click operation on the virtual screen based on the target simulated click path, so that the DMS displays the target page on the virtual screen, including: The simulated click application performs the simulated click operation on the first message on the first virtual page based on the target simulated click path, so that the DMS jumps from the first virtual page to the target page on the virtual screen.

17. The page jump method of claim 16, wherein, The step of obtaining the first screen identifier of the virtual screen includes: After creating the virtual screen, the DMS obtains the first screen identifier of the virtual screen. The notification application obtains the first screen identifier from the DMS.

18. The page redirection method according to claim 17, characterized in that, When the target application is set on the first electronic device, updating the first notification control to display the first button on the first notification control includes: When the notification application determines that the first electronic device has set the target application, the notification application sends a first update notification to the NMS. The first update notification includes the page information and is used to notify the NMS to update the first notification control. In response to the first update notification, the NMS updates the first notification control to display the first button on the first notification control.

19. The page redirection method according to claim 18, characterized in that, The step of switching the first screen identifier to the second screen identifier in response to the first operation on the first button, so that the display screen shows the target page, includes: In response to the NMS receiving the first operation on the first button, the notification application obtains the first operation based on the listening relationship with the NMS; In response to the notification application receiving the first operation, the notification application sends a second instruction to the DMS, the second instruction being used to switch to the second screen identifier; In response to the second instruction, the DMS switches the first screen identifier to the second screen identifier, so that the display screen jumps from displaying the first page to displaying the target page.

20. The page redirection method according to claim 9, characterized in that, Determining the target application based on the link type and the first package name includes: In the case where the link type is the password link, the first package name is matched with at least one preset package name to determine the target package name that matches the first package name from the preset package names; The target application is determined based on the target package name.

21. The page redirection method according to claim 20, characterized in that, After determining the link type of the first link based on the text information, the method further includes: Obtain the target simulated click path corresponding to the first package name, wherein the target simulated click path is pre-stored in the first electronic device.

22. The page redirection method according to claim 21, characterized in that, The step of responding to a first operation on the first button and navigating from the first page to a target page associated with the first link includes: In response to the first operation on the first button, the text information is copied to the clipboard; Launch the target application; Based on the target simulated click path, the text information in the clipboard is loaded in the target application, so that the display screen jumps from displaying the first page to displaying the target page.

23. The page redirection method according to claim 22, characterized in that, The step of determining the target application based on the link type and the first package name, and detecting whether the first electronic device has the target application set, includes: When the link type is the password link, the notification application matches the first package name with the preset package name to determine the target package name that matches the first package name from the preset package names; The notification application determines the target application based on the target package name and detects whether the first electronic device has the target application set.

24. The page redirection method according to claim 23, characterized in that, The step of obtaining the target simulated click path corresponding to the first package name includes: The notification application obtains the target simulated click path corresponding to the first package name.

25. The page redirection method according to claim 24, characterized in that, When the target application is set on the first electronic device, updating the first notification control to display the first button on the first notification control includes: When the notification application determines that the first electronic device has set the target application, the notification application sends a second update notification to the NMS. The second update notification includes the text information and is used to notify the NMS to update the first notification control. In response to the second update notification, the NMS updates the first notification control to display the first button on the first notification control.

26. The page redirection method according to claim 25, characterized in that, The step of responding to a first operation on the first button and navigating from the first page to a target page associated with the first link includes: In response to the NMS receiving the first operation on the first button, the notification application obtains the first operation based on the listening relationship with the NMS; In response to the notification application receiving the first operation, the notification application copies the text information to the clipboard; The notification application sends a third instruction to the Activity Management Service (AMS); The AMS responds to the third instruction and launches the target application. The simulated click application loads the text information from the clipboard in the target application based on the target simulated click path, so that the display screen jumps from displaying the first page to displaying the target page.

27. An electronic device, characterized in that, include: A processor and a memory, the memory storing program instructions that, when executed by the processor, cause the electronic device to perform the page jump method as described in any one of claims 1-26.

28. A computer-readable storage medium, characterized in that, include: Computer instructions that, when executed on an electronic device, cause the electronic device to perform the page navigation method as described in any one of claims 1-26.

Images