Method for opening a history page, related device, and computer program

By synchronizing and managing history page information across devices, the method allows quick access and opening of history pages, enhancing user experience by eliminating the need for manual operations on remote devices.

JP7589430B2Active Publication Date: 2024-11-26HUAWEI TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023518974
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-09-30
Filing Date
2021-09-13
Publication Date
2024-11-26
Estimated Expiration
2041-09-13

AI Technical Summary

Technical Problem

Switching between history pages in different applications on an intelligent terminal is not convenient, and history pages cannot be opened quickly, which does not enhance user experience.

Method used

A method for synchronizing and managing history page information across devices, allowing quick access and opening of history pages by grouping and storing page visit history based on applications, and enabling control between local and remote devices to open history pages without manual operation on the remote device.

Benefits of technology

Enables quick access and opening of history pages across different applications, improving user experience by simplifying the process and reducing the need for manual operations on the remote device.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007589430000003
    Figure 0007589430000003
  • Figure 0007589430000004
    Figure 0007589430000004
  • Figure 0007589430000005
    Figure 0007589430000005
Patent Text Reader

Abstract

The present application provides a method for opening a history page, an associated device, and a computer storage medium, which speeds up the opening of history pages in different applications, thereby enabling the history pages in different applications to be opened quickly. The method includes: analyzing received history page information at a remote device to obtain a page visit history for at least one application; storing at least one group of page visit histories obtained after the page visit histories for the at least one application are grouped based on each application; opening a tab corresponding to the page visit history of the at least one group in response to receiving a first instruction to view the visit history; and opening the page visit history of the first group and / or sending a first open instruction to the remote device in response to receiving a second instruction used to open the page visit history of the first group on the tab and in the page visit history of the at least one group.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to Chinese Patent Application No. 202011065608.4, entitled "Method for Opening History Page, Related Device, and Computer Storage Medium," filed with the State Intellectual Property Office of the People's Republic of China on September 30, 2020, which is incorporated herein by reference in its entirety.

[0002] The present application relates to the field of terminal device technology, and in particular to a method for opening a history page, a related device, and a computer storage medium. [Background technology]

[0003] Currently, most applications on an intelligent terminal provide a history record function, and the browsing history of users who access these applications can be viewed by using the history record function. However, if a user wants to view the browsing history of an application on an intelligent terminal, the user needs to open a history page in the application on the intelligent terminal to search the browsing history of the application. If the user wants to search the browsing history of another application at this time, the user needs to close the history page in the application on the intelligent terminal before opening a page in another application to search the browsing history.

[0004] In conclusion, currently, it is not convenient to switch between history pages in different applications on an intelligent terminal, and history pages in different applications cannot be quickly opened, which does not help improve user experience. Summary of the Invention

[0005] The embodiments of the present application provide a method for opening a history page, an associated device, and a computer storage medium, which increases the speed of opening a history page in different applications, thereby enabling history pages in different applications to be opened quickly, thereby helping to improve user experience.

[0006] According to a first aspect, an embodiment of the present application provides a method for opening a history page. The method is applied to a local device, the method including: receiving historical page information at the remote device sent by a remote device and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; further grouping the page visit history of the at least one application based on each application to obtain a page visit history of at least one group, and storing the page visit history of the at least one group, where each group of page visit history includes an open instruction used to open each page visit history in each group of page visit history; further receiving a first instruction to view a visit history, and in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; and further receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and in response to the second instruction, opening the page visit history of the first group and / or sending a first open instruction to the remote device, such that the remote device opens the page visit history of the first group according to the first open instruction.

[0007] For example, the local device is a mobile phone, and the remote device is a laptop computer. Generally, multiple applications may be installed on the laptop computer. For example, WeChat, iQIYI, and Tencent Video are installed. The mobile phone may obtain the history page information synchronized by the laptop computer, for example, the page visit history of at least one application installed on the laptop computer. The mobile phone may further group and store the page visit history of these applications based on each application. For example, the page visit history corresponding to the application Tencent Video has been used as a group of page visit history based on the application Tencent Video, and the page visit history corresponding to the application iQIYI has been used as a group of page visit history based on the application iQIYI. Each group of page visit history may include an open instruction used to open each page visit history in each group of page visit history. For example, the open instruction may include a page thumbnail, a page component name, and so on. For example, by tapping a page thumbnail or a page component name corresponding to the application iQIYI, the user can open the page visit history corresponding to the page thumbnail and the page component name. The mobile phone may further receive a first instruction for viewing the visit history, which may be, for example, an instruction used to open a tab to display the page visit history. For example, an operation of pulling down or pulling up a display desktop of the mobile phone running on a display desktop of the mobile phone may cause the mobile phone to open the tab in response to the first instruction. The mobile phone may further receive a second instruction used to open a first group of page visit histories on the tab and in the at least one group of page visit histories.For example, by searching the tab for an application name of an application corresponding to the first group of page visit histories, the mobile phone can open the first group of page visit histories and / or send a first open command to the laptop computer in response to the second command. After receiving the first open command, the laptop computer can open the first group of page visit histories.

[0008] According to the solution provided in the present application, the historical page information in different applications on the remote device can be synchronized with the local device, so that the local device can quickly access the historical page information in different applications on the remote device. The local device can further control the remote device to quickly access the historical page information in different applications on the remote device without needing to perform operations on the remote device and without needing to search the historical page information in each of the different applications on the remote device. This can simplify the user's operation of searching for the historical page information in different applications and increase the speed of opening different applications, so that pages in different applications can be opened quickly, thereby helping to improve the user experience. In addition, since the tabs corresponding to the page visit histories of at least one group can record the page visit histories of different applications, multiple applications are compatible and do not need to rely on the local page visit history function of the application.

[0009] Referring to the first aspect, in a possible implementation form of the first aspect, after the step of opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device, the method further includes a step of receiving a third instruction used to open a first page visit history in the page visit history of the first group; and a step of opening the first page visit history in response to the third instruction if the page visit history of the first group is opened on the local device; or a step of sending the second open instruction to the remote device in response to the third instruction if the page visit history of the first group is opened on the remote device, where the second open instruction is used to control the remote device to open the first page visit history; or a step of opening the first page visit history on the local device and sending the second open instruction to the remote device in response to the third instruction if the page visit history of the first group is opened synchronously on the local device and the remote device.

[0010] For example, the local device is a mobile phone and the remote device is a laptop computer. The third instruction may be, for example, a user tapping a page thumbnail or a page component name in the first group of page visit histories displayed on the tab of the mobile phone. That is, the user may control the tab of the mobile phone to open the first page visit histories on the mobile phone and / or the laptop computer.

[0011] According to the solution provided in the present application, the page visit history may be supported to be opened on a single terminal device, or the page visit history may be supported to be opened on multiple terminal devices, so that the user can easily select the corresponding terminal device to open the page visit history on the target terminal device, thereby achieving the purpose of quickly opening the page visit history and helping to improve the user experience.

[0012] Referring to the first aspect, in a possible implementation form of the first aspect, the step of opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device includes: displaying on the tab, in response to the second instruction, a first control used to open the page visit history of the first group on the local device, a second control used to open the page visit history of the first group on the remote device, and a third control used to open the page visit history of the first group synchronously on the local device and the remote device; and opening the page visit history of the first group on the local device if a first operation of tapping the first control is received; or sending the first open instruction to the remote device if a second operation of tapping the second control is received; or opening the page visit history of the first group on the local device and on the remote device and sending the first open instruction to the remote device if a third operation of tapping the third control is received.

[0013] For example, the local device is a mobile phone and the remote device is a laptop computer. When a user searches for an application name or the like of an application corresponding to the first group of page visit histories on a tab, prompt information such as, for example, "Select a device to open on" may be displayed on the tab of the mobile phone. The prompt information may include, for example, a first control such as "This device", a second control "Laptop computer", and a third control "Mobile phone and laptop computer". The user may select a device for opening the first group of page visit histories by tapping the corresponding control.

[0014] According to the solution provided in the present application, different page visit histories can be supported to be opened on a single terminal device, or different page visit histories can be supported to be opened on multiple terminal devices synchronously, so that a user can easily select a corresponding terminal device to open at least one page visit history on a target terminal device, thereby achieving the purpose of quickly opening page visit histories and helping to improve user experience.

[0015] Referring to the first aspect, in a possible implementation form of the first aspect, after the step of storing the page visit history of the at least one group, the method further includes the steps of: determining whether the storage space currently used for storing the page visit history of the at least one group has reached a preset threshold; and deleting at least one earliest page visit history from the page visit history of the at least one group when the storage space has reached the preset threshold.

[0016] For example, the local device is a mobile phone and the remote device is a laptop computer. The user can set a preset threshold of the size of the storage space used for the page visit history of the laptop computer in the mobile phone. For example, the preset threshold can be set to 30M, thereby avoiding the size of the storage space being too large to affect the normal operation of the mobile phone, and when the size of the storage space reaches the preset threshold, at least one of the earliest page visit histories can be automatically deleted without manual operation by the user.

[0017] According to the solution provided in the present application, the storage space of the local device for storing page visit history on the remote device can be reduced, and the freshness of the page visit history on the remote device stored on the local device can be further guaranteed.

[0018] Referring to the first aspect, in a possible implementation form of the first aspect, the step of storing the page visit history of the at least one group includes: storing at least one page visit history in the page visit history of the at least one group, where the at least one page visit history is a page visit history in the page visit history of the at least one group, and a time length interval between a time of the page visit history and a current time is less than or equal to a predetermined time length and / or a time of the page visit history is within a predetermined time.

[0019] For example, the local device is a mobile phone and the remote device is a laptop computer. When the laptop computer executes each application, a group of page visit histories corresponding to each application may include multiple page visit histories, and the size of the storage space corresponding to the multiple page visit histories may exceed a preset threshold, so that it is inconvenient for the mobile phone to store the page visit histories of the applications installed on the laptop computer. A user may set the mobile phone to store the page visit histories within a specific period or on a specific date. The mobile phone may store the corresponding page visit histories based on the period or the date.

[0020] According to the solution provided in the present application, by satisfying different users' requirements for viewing the page visit history of a remote device corresponding to different time periods, it may be easy for users to view the corresponding page visit history. By satisfying the personalized demands of users, it may be helpful to improve the user experience.

[0021] Referring to the first aspect, in a possible implementation form of the first aspect, performing a first preset operation on the tab switches between groups of page visit histories in the page visit histories of the at least one group, the first preset operation including at least a left / right flick operation; when a page visit history of a second group in the page visit history of the at least one group is currently displayed on the tab, performing a second preset operation on the tab switches between page visit histories in the page visit history of the second group, the second preset operation including at least an up / down flick operation.

[0022] For example, the local device is a mobile phone and the remote device is a laptop computer. The user may switch from the tab to view a different group of page visit histories, i.e., switch between page visit histories of different applications, by flicking the tab on the mobile phone left / right or performing another operation (e.g., pressing the volume buttons "+" or "-"). The user may further switch to view the page visit histories in the second group of page visit histories currently displayed in the tab by flicking the tab up / down or performing another operation.

[0023] According to the solution provided in the present application, switching between page visit histories of different applications and viewing each page visit history of different applications is supported, which facilitates users to view page visit histories of different applications, thereby helping to improve user experience.

[0024] Referring to the first aspect, in a possible implementation form of the first aspect, before the step of opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device, the method further includes: a step of determining that a first application corresponding to the page visit history of the first group is not installed on the local device; a step of outputting first prompt information used to indicate to the local device that the first application needs to be installed, where the first prompt information includes an installation instruction; and a step of initiating installation of the first application on the local device in response to the installation instruction.

[0025] For example, the local device is a mobile phone and the remote device is a laptop computer. The applications installed on the mobile phone may be different from the applications installed on the laptop computer. The first application corresponding to the page visit history of the first group may not be included in the applications currently installed on the mobile phone. In this case, the mobile phone may display first prompt information to present to the user that the first application needs to be installed on the mobile phone. The first prompt information may display the content "Do you want to install the first application now?", a control "No", and a control "Yes". When the user triggers the control "Yes", the mobile phone may start installing the first application. The user may alternatively reject the installation of the first application on the mobile phone by triggering the control "No".

[0026] According to the solution provided in the present application, when it is determined that the first application is not installed on the local device, the local device is prompted to install the first application, so that the local device is supported to open the page visit history of the first application, which can help achieve the purpose of quickly opening the page visit history and improve the user experience.

[0027] Referring to the first aspect, in a possible implementation form of the first aspect, the first opening command may include a minimum set of information required to open the page visit history of the first group, and the second opening command may include a minimum set of information required to open the first page visit history. Specifically, the mobile phone may open the page visit history of the first group by using the minimum set of information required to open the page visit history of the first group, and may open the first page visit history by using the minimum set of information required to open the first page visit history.

[0028] According to a second aspect, an embodiment of the present application further provides a method for opening a history page, the method being applied to a remote device, the method including: obtaining a page visit history of at least one group by grouping and storing historical page information of at least one application previously opened on the remote device based on each application, where the historical page information includes a page visit history of the at least one application on the remote device, and each group of the page visit history includes an open instruction used to open each page visit history in each group of the page visit history; and further synchronizing the historical page information to a local device, so that the local device obtains the page visit history of the at least one group after analyzing the historical page information, and opens the page visit history of any one group in the page visit history of the at least one group according to the corresponding instruction.

[0029] For example, the remote device is a laptop computer and the local device is a mobile phone. The laptop computer may further group and store the page visit histories of these installed applications based on each application. For example, the page visit history corresponding to the application Tencent Video is used as a group of page visit histories based on the application Tencent Video, and the page visit history corresponding to the application iQIYI is used as a group of page visit histories based on the application iQIYI. Each group of page visit histories may include an open instruction used to open each page visit history in each group of page visit histories. For example, the open instruction may include a page thumbnail, a page component name, and so on. For example, by tapping a page thumbnail or a page component name corresponding to the application iQIYI, the user can open the page visit history corresponding to the page thumbnail and the page component name. The page visit histories of these applications installed on the laptop computer may be synchronized with the mobile phone, so that the page visit histories of these applications may be opened by using the mobile phone.

[0030] According to the solution provided in the present application, the history page information in different applications on the remote device is recorded and synchronized with the connected local device, so that the local device can quickly access the history page information in different applications on the remote device. The local device can further control the remote device to quickly access the history page information in different applications on the remote device without needing to perform operations on the remote device and without needing to search the history page information in each of the different applications on the remote device. This can simplify the user's operation of searching for the history page information in different applications and increase the speed of opening the history pages in different applications, so that the history pages in different applications can be quickly opened, which can help improve the user experience.

[0031] Referring to the second aspect, in a possible implementation form of the second aspect, before the step of obtaining at least one group of page visit history by grouping and storing historical page information of at least one application previously opened on the remote device based on each application, the method further includes: generating one start activity instruction each time a new page of an application in the at least one application is opened, where page information of the new page is held in the start activity instruction, and the page information of the new page includes an application name, a page component name, additional parameters, and a page thumbnail corresponding to the new page; and obtaining a group of page visit history by storing the page information of the new page based on the application and in accordance with the start activity instruction.

[0032] For example, the remote device is a laptop computer, and the local device is a mobile phone. For example, when the laptop computer opens Tencent Video, it may first enter a home page in the application Tencent Video. The home page information may include a page thumbnail of the home page, an application name "Tencent Video" of the application Tencent Video, and a page component name (including the application name of the application Tencent Video and the name of the home page, etc.), and the additional parameters may include a URL address corresponding to the home page. The user may enter a new page, i.e., a featured page, in the application Tencent Video by tapping a control "Featured" displayed on the home page. The featured page information may include a page thumbnail of the featured page, an application name "Tencent Video" of the application Tencent Video, and a page component name (including the application name of the application Tencent Video and the name of the featured page, etc.), and the additional parameters may include a URL address corresponding to the featured page. The laptop computer may store the page information corresponding to the application Tencent Video as a group of page visit history based on the application Tencent Video.

[0033] The solutions provided in the present application may facilitate a remote device to manage page visit histories of different applications, and may further facilitate a local device to subsequently synchronize the page visit histories of the remote device.

[0034] Referring to the second aspect, in a possible implementation form of the second aspect, after the step of synchronizing the historical page information to the local device, the method further includes: receiving a first open instruction sent by the local device; and parsing the first open instruction and opening a page visit history of a first group in the page visit history of the at least one group according to the parsed first open instruction.

[0035] For example, the remote device is a laptop computer and the local device is a mobile phone, and the user may control the mobile phone to send a first open command to the laptop computer to open the page visit history of the first group, e.g., to open the page visit history of the first group of an application corresponding to the page visit history of the first group.

[0036] According to the solution provided in the present application, a local device may support controlling a remote device to quickly access page visit histories of different applications on the remote device without needing to perform operations on the remote device, which may increase the speed of opening history pages in different applications, so that history pages in different applications may be opened quickly, thereby helping to improve user experience.

[0037] Referring to the second aspect, in a possible implementation form of the second aspect, after the step of receiving a first open instruction sent by the local device, the method further includes: a step of receiving a second open instruction sent by the local device; and a step of parsing the second open instruction and opening a first page visit history in the page visit history of the first group according to the parsed second open instruction.

[0038] For example, the remote device is a laptop computer and the local device is a mobile phone, and the user may control the mobile phone to send a second open command to the laptop computer to open a first page visit history in the first group of page visit histories, e.g., to open a first page visit history of an application corresponding to the first group of page visit histories.

[0039] According to the solution provided in the present application, a local device may support controlling a remote device to quickly access page visit histories of different applications on the remote device without needing to perform operations on the remote device, which may increase the speed of opening history pages in different applications, so that history pages in different applications may be opened quickly, thereby helping to improve user experience.

[0040] Referring to the second aspect, in a possible implementation form of the second aspect, the step of opening the page visit history of a first group in the page visit history of the at least one group in accordance with the analyzed first open instruction includes: opening the page visit history of the first group in a start activity manner in accordance with the analyzed first open instruction, and updating changes in the page visit history of the first group after the page visit history of the first group is opened, where the changes in the page visit history of the first group include at least one deleted and / or added page visit history in the page visit history of the first group.

[0041] For example, the remote device is a laptop computer. After the laptop computer opens the page visit history of the first group, if the user enters a new page, one or more page visit histories are added to the page visit history of the first group. If the user does not need a particular page visit history, the user may delete the page visit history from the page visit history of the first group.

[0042] According to the solution provided in the present application, the page visit history of the first group is updated in a start activity manner based on the remote device accessing a new page after the first open command is received, so that the phenomenon of part of the page visit history of the remote device being leaked can be avoided, thereby helping to improve user experience.

[0043] Referring to the second aspect, in a possible implementation form of the second aspect, the step of opening a first page visit history in the page visit history of the first group in accordance with the analyzed second open instruction includes: opening the first page visit history in a start activity manner in accordance with the analyzed second open instruction, and updating change information in the page visit history of the first group after the first page visit history is opened, where the change information in the page visit history of the first group includes content information corresponding to at least one added page visit history in the page visit history of the first group, or at least one updated page visit history in the page visit history of the first group.

[0044] For example, the remote device is a laptop computer. For example, after the laptop computer opens a page visit history of an application, if the progress corresponding to the page visit history is not completed, the progress of the page visit history may continue to be completed and update the content information in the page visit history. Alternatively, the user may tap a corresponding control in the display interface corresponding to the page visit history to enter a new page, for example, enter a setting page by tapping the control "settings", and add the page visit history corresponding to the new page to a group of page visit histories corresponding to the application.

[0045] According to the solution provided in the present application, the page visit history of the first group is updated in a start activity manner based on the remote device accessing a new page or the continuing execution of uncompleted content information in the first page visit history after the second open command is received, so that the phenomenon of part of the page visit history of the remote device being leaked can be avoided, thereby helping to improve user experience.

[0046] Referring to the second aspect, in a possible implementation of the second aspect, the first opening instruction may include a minimum set of information required to open the page visit history of the first group, and the second opening instruction may include a minimum set of information required to open the first page visit history. Specifically, the laptop computer may open the page visit history of the first group by using the minimum set of information required to open the page visit history of the first group, and may open the first page visit history by using the minimum set of information required to open the first page visit history.

[0047] According to a third aspect, embodiments of the present application further comprise: one or more processors; and One or more memories A local device comprising: The one or more memories store one or more computer programs, the one or more computer programs including instructions that, when executed by the one or more processors, cause the local device to perform the following steps: receiving historical page information at the remote device sent by the remote device, and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; grouping the page visit histories of the at least one application based on each application to obtain at least one group of page visit histories, and storing the at least one group of page visit histories, where each group of page visit histories includes an open instruction used to open each page visit history in each group of page visit histories; receiving a first instruction to view a visit history and, in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; and receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device, such that the remote device opens the page visit history of the first group in accordance with the first open instruction. To provide a local device on which the

[0048] Referring to the third aspect, in a possible implementation of the third aspect, when the instructions are executed by the one or more processors, the local device performs the following steps: receiving a third command used to open a first page visit history in the first group of page visit histories; and opening the first page visit history in response to the third instruction if the first group of page visit history is opened on the local device; or sending the second open command to the remote device in response to the third command if the first group of page visit histories is opened on the remote device, where the second open command is used to control the remote device to open the first group of page visit histories; or and in response to the third command, if the first group of page visit histories are synchronously opened on the local device and the remote device, opening the first page visit histories on the local device and sending the second open command to the remote device. It becomes possible to specifically implement the above.

[0049] Referring to the third aspect, in a possible implementation of the third aspect, when the instructions are executed by the one or more processors, the local device performs the following steps: displaying on the tab, in response to the second instruction, a first control used to open a page visit history of the first group on the local device, a second control used to open a page visit history of the first group on the remote device, and a third control used to open the page visit history of the first group synchronously on the local device and the remote device; and opening a page visit history of the first group on the local device when a first operation of tapping the first control is received; or sending the first open command to the remote device when a second operation of tapping the second control is received; or when a third operation of tapping the third control is received, opening a page visit history of the first group on the local device and on the remote device and sending the first open command to the remote device. It becomes possible to specifically implement the above.

[0050] Referring to the third aspect, in a possible implementation of the third aspect, when the instructions are executed by the one or more processors, the local device performs the following steps: determining whether the storage space currently being used to store the page visitation history of the at least one group has reached a preset threshold; and deleting at least one earliest page visit history from the at least one group of page visit histories when the storage space reaches the preset threshold. It becomes possible to specifically implement the above.

[0051] Referring to the third aspect, in a possible implementation of the third aspect, when the instructions are executed by the one or more processors, the local device performs the following steps: Storing at least one page visit history in the page visit history of the at least one group, where the at least one page visit history is a page visit history in the page visit history of the at least one group, and a time length interval between a time of the page visit history and a current time is less than or equal to a preset time length and / or the time of the page visit history is within a preset time. It becomes possible to specifically implement the above.

[0052] Referring to the third aspect, in a possible implementation of the third aspect, when the instructions are executed by the one or more processors, the local device performs the following steps: performing a first preset operation on the tab to switch between groups of page visit histories in the at least one group of page visit histories; and when a page visit history of a second group in the page visit history of the at least one group is currently displayed on the tab, switching between page visit histories in the page visit history of the second group by performing the second preset operation on the tab; It becomes possible to specifically implement the above.

[0053] Referring to the third aspect, in a possible implementation of the third aspect, when the instructions are executed by the one or more processors, the local device performs the following steps: determining that a first application corresponding to the first group of page visit histories is not installed on the local device; outputting first prompt information used to indicate to the local device that the first application needs to be installed, where the first prompt information includes installation instructions; and initiating installation of the first application on the local device in response to the installation command. It becomes possible to specifically implement the above.

[0054] Referring to the third aspect, in a possible implementation form of the third aspect, the first opening instruction may include a minimum set of information required to open the page visit history of the first group, and the second opening instruction includes a minimum set of information required to open the first page visit history.

[0055] According to a fourth aspect, an embodiment of the present application further comprises: one or more processors; and One or more memories A remote device comprising: The one or more memories store one or more computer programs, the one or more computer programs including instructions, which when executed by the one or more processors, cause the remote device to perform the following steps: obtaining at least one group of page visit histories by grouping and storing historical page information of at least one application previously opened on the remote device based on each application, where the historical page information includes page visit histories of the at least one application on the remote device, and each group of the page visit histories includes an open instruction used to open each page visit history in each group of the page visit histories; and Synchronizing the historical page information to a local device, so that the local device obtains the page visit history of the at least one group after analyzing the historical page information, and opens the page visit history of any one group in the page visit history of the at least one group according to a corresponding instruction. To provide a remote device that enables execution of the

[0056] Referring to the fourth aspect, in a possible implementation of the fourth aspect, when the instructions are executed by the one or more processors, the remote device performs the following steps: generating a start activity instruction each time a new page of an application in the at least one application is opened, where page information of the new page is held in the start activity instruction, and the page information of the new page includes an application name, a page component name, additional parameters, and a page thumbnail corresponding to the new page; and obtaining a group of page visit histories by storing the page information of the new page based on the application and according to the start activity instruction. It becomes possible to specifically implement the above.

[0057] Referring to the fourth aspect, in a possible implementation of the fourth aspect, when the instructions are executed by the one or more processors, the remote device performs the following steps: receiving a first open command sent by the local device; and parsing the first open command and opening a page visit history of a first group in the page visit history of the at least one group according to the parsed first open command; It becomes possible to specifically implement the above.

[0058] Referring to the fourth aspect, in a possible implementation of the fourth aspect, when the instructions are executed by the one or more processors, the remote device performs the following steps: receiving a second open command sent by the local device; and parsing the second open command and opening a first page visit history in the page visit history of the first group according to the parsed second open command; It becomes possible to specifically implement the above.

[0059] Referring to the fourth aspect, in a possible implementation of the fourth aspect, when the instructions are executed by the one or more processors, the remote device performs the following steps: opening the page visit history of the first group in a start activity manner according to the analyzed first open command, and updating changes in the page visit history of the first group after the page visit history of the first group is opened, where the changes in the page visit history of the first group include at least one deleted and / or added page visit history in the page visit history of the first group. It becomes possible to specifically implement the above.

[0060] Referring to the fourth aspect, in a possible implementation of the fourth aspect, when the instructions are executed by the one or more processors, the remote device performs the following steps: opening the first page visit history in a start activity manner according to the parsed second open command, and updating change information in the page visit history of the first group after the first page visit history is opened, where the change information in the page visit history of the first group includes content information corresponding to at least one added page visit history in the page visit history of the first group, or at least one updated page visit history in the page visit history of the first group. It becomes possible to specifically implement the above.

[0061] Referring to the fourth aspect, in a possible implementation form of the fourth aspect, the first opening instruction may include a minimum set of information required to open the page visit history of the first group, and the second opening instruction may include a minimum set of information required to open the first page visit history.

[0062] According to a fifth aspect, the present embodiment further provides a terminal device. The terminal device includes a module / unit for performing the method in the first aspect or any one of the possible designs of the first aspect; or the terminal device includes a module / unit for performing the method in the second aspect or any one of the possible designs of the second aspect. These modules / units may be implemented by hardware, or may be implemented by hardware executing corresponding software.

[0063] According to a sixth aspect, an embodiment of the present application further provides a terminal device. The terminal device includes one or more processors and one or more memories or non-volatile storage media. The one or more processors are connected to one or more memories or non-volatile storage media. The one or more memories or non-volatile storage media store one or more computer instructions or computer programs. When the one or more processors execute the one or more computer instructions or computer programs, the terminal device is capable of performing the method in the second aspect or any one of the possible designs of the second aspect.

[0064] According to a seventh aspect, the embodiment of the present application further provides a chip. The chip is coupled to a memory in a terminal device, and is configured to call a computer program stored in the memory to implement the technical solution in any one of the first aspect and possible designs of the embodiment of the present application, or is configured to call a computer program stored in the memory to implement the technical solution in any one of the second aspect and possible designs of the embodiment of the present application. In the embodiment of the present application, "coupled" means that two components are directly or indirectly combined with each other.

[0065] According to an eighth aspect, an embodiment of the present application further provides a computer-readable storage medium or a non-volatile storage medium. The computer-readable storage medium or the non-volatile storage medium stores computer instructions or a computer program. When the computer instructions or the computer program are invoked by a computer, the computer is enabled to execute a method according to any one of the first aspect or the second aspect. When the computer instructions or the computer program are executed on one or more processors, a local device including one or more processors is enabled to execute a method according to the first aspect, or a remote device including one or more processors is enabled to execute a method according to the second aspect.

[0066] According to a ninth aspect, an embodiment of the present application further provides a computer program product, the computer program product being configured to store a computer program which, when executed on a computer, enables the computer to carry out a method according to any one of the first or second aspects.

[0067] According to a tenth aspect, there is further provided a graphical user interface on a terminal device. The terminal device has a display, one or more memories, and one or more processors. The one or more processors are configured to execute one or more computer programs stored in the one or more memories. The graphical user interface includes a graphical user interface that is displayed when the terminal device executes the method according to the first aspect or the method according to the second aspect.

[0068] According to an eleventh aspect, an embodiment of the present application provides a multi-device cooperation system. The multi-device cooperation system includes a plurality of terminal devices. The plurality of terminal devices includes a terminal device used as a local device and a terminal device used as a remote device. The terminal device used as the local device is configured to execute a step performed by the local device in the solution provided in the first aspect or the embodiment of the present application. The terminal device used as the remote device is configured to execute a step performed by the remote device in the solution provided in the second aspect or the embodiment of the present application.

[0069] For the beneficial effects of the third to eleventh aspects, please refer to the beneficial effects of the first and second aspects. Details will not be described again. [Brief description of the drawings]

[0070] [Figure 1] FIG. 1 is a schematic diagram of an architecture of a multi-device cooperation system according to an embodiment of the present application.

[0071] [Diagram 2] FIG. 2 is a schematic diagram of a process of collaboration between a local device and a remote device according to an embodiment of the present application.

[0072] [Diagram 3]FIG. 1 is a schematic diagram of a structure of a mobile phone according to an embodiment of the present application.

[0073] [Figure 4] FIG. 1 is a schematic diagram of a structure of a mobile phone according to an embodiment of the present application.

[0074] [Diagram 5] 1 is a schematic flowchart of a method for opening a history page according to an embodiment of the present application;

[0075] [Figure 6] FIG. 1 is a schematic diagram of a tab on a local device according to an embodiment of the present application.

[0076] [Figure 7A] FIG. 2 is a schematic diagram of switching between groups of page visit history by using tabs according to an embodiment of the present application. [Figure 7B] FIG. 2 is a schematic diagram of switching between groups of page visit history by using tabs according to an embodiment of the present application.

[0077] [Figure 8] FIG. 1 is a schematic diagram of a tab on a local device according to an embodiment of the present application.

[0078] [Figure 9] FIG. 1 is a schematic diagram of a tab on a local device according to an embodiment of the present application.

[0079] [Figure 10] FIG. 1 is a schematic diagram of switching between recently played songs using tabs according to an embodiment of the present application.

[0080] [Figure 11] 1 is a schematic flowchart of a method for opening a history page according to an embodiment of the present application;

[0081] [Figure 12(a)] FIG. 2 is a schematic diagram of a process in which a remote device records different page visit histories according to an embodiment of the present application; [Figure 12(b)] FIG. 2 is a schematic diagram of a process in which a remote device records different page visit histories according to an embodiment of the present application; [Figure 12(c)] FIG. 2 is a schematic diagram of a process in which a remote device records different page visit histories according to an embodiment of the present application;

[0082] [Figure 13] FIG. 2 is a schematic diagram of a structure of a local device according to an embodiment of the present application;

[0083] [Figure 14] FIG. 2 is a schematic diagram of a structure of a remote device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0084] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the embodiments of the present application are described below with reference to the accompanying drawings of the embodiments of the present application.

[0085] FIG. 1 is a schematic diagram of an architecture of a multi-device cooperation system according to an embodiment of the present application. The system may include multiple terminal devices. Some terminal devices may be used as local devices, and other terminal devices may be used as remote devices. It should be understood that in practical applications, any one of the multiple terminal devices may be used as a local device and / or a remote device based on different requirements. In FIG. 1, for example, the multiple terminal devices include a local device 10 and a remote device 20.

[0086] It should be understood that the local device 10 in this embodiment of the present application may be referred to as user equipment (UE), such as a smartphone, a tablet computer, a laptop computer, a television, various wearable devices, a Bluetooth® speaker, an in-vehicle device, and a computer. Exemplary embodiments of portable devices include, but are not limited to, portable devices using iOS®, Android®, Microsoft®, or another operating system. The portable device may alternatively be another portable device. The specific form of the local device 10 is not limited in this embodiment of the present application.

[0087] It should be understood that the remote device 20 in this embodiment of the present application may be referred to as user equipment (UE), such as a smartphone, a tablet computer, a laptop computer, a television, various wearable devices, a Bluetooth speaker, an in-vehicle device, and a computer. Exemplary embodiments of a portable device include, but are not limited to, a portable device using iOS®, Android®, Microsoft®, or another operating system. The portable device may alternatively be another portable device. The specific form of the remote device 20 is not limited in this embodiment of the present application.

[0088] It should be understood that in this embodiment of the present application, the local device 10 and the remote device 20 can be the same type of terminal device or can be different types of terminal devices, which is not limited in this embodiment of the present application.

[0089] It should be understood that in this embodiment of the present application, the local device 10 and the remote device 20 may communicate with each other directly, or may communicate with each other by being forwarded by another device, which is not specifically limited in this embodiment of the present application.

[0090] The remote device 20 may group and store historical page information of at least one application ever opened on the remote device 20 based on each application to obtain at least one group of page visit histories. The historical page information may include page visit histories of at least one application on the remote device 20, and each group of the page visit histories may include an open instruction used to open each page visit history in each group of the page visit histories. Furthermore, the remote device 20 may further synchronize the historical page information to the local device 10.

[0091] The local device 10 may receive the historical page information on the remote device 20 sent by the remote device 20, and analyze the historical page information to obtain a page visit history of at least one application. Furthermore, the local device 10 may further group the page visit history of the at least one application based on each application, obtain the page visit history of the at least one group, and store the page visit history of the at least one group. Furthermore, the local device 10 may further receive a first instruction for viewing the visit history, and in response to the first instruction, open a tab corresponding to the page visit history of the at least one group. Furthermore, the local device 10 may further receive a second instruction used to open the page visit history of the first group on the tab and in the page visit history of the at least one group, and in response to the second instruction, open the page visit history of the first group and / or send a first open instruction to the remote device 20.

[0092] The remote device 20 may further receive the first open command sent by the local device 10. Furthermore, the remote device 20 may further open the page visit history of the first group according to the first open command.

[0093] In this embodiment of the present application, the history page information in different applications on the remote device is recorded and synchronized with the connected local device, so that the local device can quickly access the history page information in different applications on the remote device. The local device can further control the remote device to quickly access the history page information in different applications on the remote device without needing to perform operations on the remote device and without needing to search the history page information in each of the different applications on the remote device. This can simplify the user's operation of searching for the history page information in different applications and increase the speed of opening the history pages in different applications, so that the history pages in different applications can be quickly opened, which can help improve the user experience.

[0094] The process of cooperation between the local device 10 and the remote device 20 is described in detail below with reference to FIGS.

[0095] 2, the local device 10 may include an application layer 11, a framework layer 12, a device driver layer 13, and a system kernel layer 14. The application layer 11 may include a user interface (UI) 1101, which may include a recent task label module 11011, a data storage module 11012, and a data synchronization module 11013. The framework layer 12 may include a cross-device communication module 1201.

[0096] The recent task label module 11011 may be configured to provide a service to search for historical page information synchronized to the local device 10 by the remote device 20. The data storage module 11012 may be configured to store the historical page information of the remote device 20. The data synchronization module 11013 may be configured to synchronize the historical page information of the remote device 20, and may send an open command to open the historical page information to the remote device 20 using the cross-device communication module 1201. The cross-device communication module 1201 may be configured to support communication between the local device 10 and the remote device 20. The device driver layer 13 may be configured to support the hardware of the local device 10 in operation. The system kernel layer 14 may be configured to manage system processes, internal memory, device drivers, files, and network systems on the local device 10, etc.

[0097] In some embodiments, the local device 10 may receive the historical page information in the remote device 20 sent by the remote device 20 using the cross-device communication module 1201, as shown in step 3 in FIG. 2. The local device 10 may analyze the historical page information and obtain the page visit history of at least one application using the data synchronization module 11013, as shown in step 4 in FIG. 2. The local device 10 may synchronize the page visit history of the at least one application using the data synchronization module 11013, as shown in step 6 in FIG. 2, and may send an open command used to open the page visit history of the at least one application to the remote device 20 using the cross-device communication module 1201. The local device 10 may group the page visit history of the at least one application based on each application using the data synchronization module 11013, as shown in step 5 in FIG. 2, to obtain the page visit history of the at least one group, and store the page visit history of the at least one group by using the data storage module 11012. The local device 10 may further receive a first instruction to view the visit history using the cross-device communication module 1201, and in response to the first instruction, open a tab corresponding to the page visit history of at least one group using the recent task label module 11011, using the cross-device communication module 1201, as shown in step 6 in Fig. 2. The local device 10 may further receive a second instruction used to open the page visit history of the first group on the tab and in the page visit history of the at least one group using the cross-device communication module 1201, and in response to the second instruction, open the page visit history of the first group using the recent task label module 11011 and / or send a first open instruction to the remote device 20 using the cross-device communication module 1201, using the cross-device communication module 1201.

[0098] The remote device 20 may include an application layer 21, a framework layer 22, a device driver layer 23, and a system kernel layer 24. The application layer 21 may include multiple applications, such as application a (application a is identified in FIG. 2 at 2101), application b (application b is identified in FIG. 2 at 2102), and application z (application z is identified in FIG. 2 at 2103), as shown in FIG. 2. The framework layer 22 may include a cross-device communication module 2201, a task management module 2202, and a task storage module 2203.

[0099] The cross-device communication module 2201 may be configured to support communication between the remote device 20 and the local device 10. The task management module 2202 may be configured to record historical page information in the remote device 20 and store page visit histories acquired by different applications in the application layer 21 in the task storage module 2203. The task storage module 2203 is configured to group and store the page visit histories of different applications based on each application. The device driver layer 23 may be configured to support the hardware of the remote device 20 in operation. The system kernel layer 24 may be configured to manage system processes, internal memory, device drivers, files, network systems, etc. on the remote device 20.

[0100] In some embodiments, as shown in step 1 in FIG. 2, the remote device 20 may use the task management module 2202 to group and store historical page information of at least one application previously opened on the remote device 20 based on each application to obtain at least one group of page visit histories. The historical page information may include a page visit history of at least one application on the remote device 20, and each group of the page visit history may include an open instruction for opening each page visit history in each group of the page visit history. The remote device 20 may further use the task storage module 2203 to store the page visit history of the at least one application, as shown in step 2 in FIG. 2. The remote device 20 may further use the cross-device communication module 2201 to synchronize the historical page information to the local device 10, as shown in step 3 in FIG. 2. The remote device 20 may further use the cross-device communication module 2201 to receive a first open instruction sent by the local device 10, as shown in step 6 in FIG. 2. The remote device 20 may further use the task management module 2202 to open the page visit history of the first group according to the first open instruction, as shown in step 7 in FIG.

[0101] The cross-device communication module 1201 may communicate with the cross-device communication module 2201 via Bluetooth, Wi-Fi, or another communication protocol, which is not limited in this embodiment of the present application.

[0102] In this embodiment of the present application, due to the different structures of the local device and the remote device, the history page information in the different applications on the remote device can be synchronized with the local device, so that the local device can quickly access the history page information in the different applications on the remote device. The local device can further control the remote device to quickly access the history page information in the different applications on the remote device, without needing to perform operations on the remote device, and without needing to search the different applications on the remote device for the history page information in each of the different applications. This can simplify the user's operation of searching for the history page information in different applications, and increase the speed of opening the history pages in different applications, so that the history pages in different applications can be quickly opened, which can help improve the user experience.

[0103] To describe the functions of each structure of the mobile phone type that may be implemented in the embodiments of the present application, an example in which the local device is a mobile phone is used below.

[0104] As shown in Fig. 3, the mobile phone 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, a subscriber identification module (SIM) card interface 195, a cross-device communication module 196, a data synchronization module 197, and a data storage module 198, etc. The sensor module 180 may include a fingerprint sensor 180A, a touch sensor 180B, etc. The type and number of sensors are not limited herein.

[0105] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a memory, a video codec, a digital signal processor (DSP), a baseband processor, a neural-network processing unit (NPU), and / or a central processing unit (CPU), etc. The different processing units may be separate components or may be integrated into one or more processors.

[0106] A memory may further be disposed in the processor 110 and configured to store instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that have just been used or that are periodically used by the processor 110. When the processor 110 needs to use the instructions or data again, the processor can retrieve the instructions or data directly from the memory. This avoids repeated accesses and reduces the time the processor 110 spends waiting, improving the efficiency of the system.

[0107] The processor 110 can execute the software code / module for the method of opening a history page provided in the embodiment of the present application to open the page visit history of the remote device by using the mobile phone 100 or the remote device. The specific process will be described in detail below.

[0108] The USB interface 130 is an interface that complies with the USB standard specification, and specifically may be a miniUSB interface, a microUSB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect to a charger to charge the mobile phone 100, or may be used to transmit data between the mobile phone 100 and a peripheral device.

[0109] The charging management module 140 is configured to receive a charging input from a charger. The power management module 141 is configured to connect 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, and provides power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, etc.

[0110] The wireless communication function of the mobile phone 100 may be implemented by using antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, a cross-device communication module 196, a modem processor, a baseband processor, and the like. Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the mobile phone 100 may be used to cover one or more communication frequency bands. Furthermore, different antennas may be multiplexed to improve antenna utilization. For example, Antenna 1 may be multiplexed as a diversity antenna in a wireless local area network. In some other embodiments, the antennas may be used in combination with tuning switches.

[0111] The mobile communication module 150 may provide wireless communication solutions including 2G / 3G / 4G / 5G applied to the mobile phone 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, and low noise amplifier (LNA), etc. The mobile communication module 150 may receive electromagnetic waves by the antenna 1, perform processing such as filtering or amplification on the received electromagnetic waves, and send the electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 may further amplify the modulated signal by the modem processor and convert the signal into electromagnetic waves for emission through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 and at least some of the modules of the processor 110 may be disposed in the same component.

[0112] The wireless communication module 160 may be applied to the mobile phone 100 and provide wireless communication solutions including wireless local area network (WLAN) (e.g., wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC) technology, and infrared (IR) technology. The wireless communication module 160 may be one or more components integrating at least one communication processor module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering on the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may further receive signals to be transmitted from the processor 110, perform frequency modulation and amplification on the signals, and convert the signals into electromagnetic waves for radiation through the antenna 2.

[0113] The cross-device communication module 196 is configured to receive a page visit history sent by a remote device. The page visit history may include a page visit history corresponding to each of at least one application on the remote device. The page visit history may be sent by the remote device in response to the synchronization request information after the mobile phone 100 sends synchronization request information to the remote device using the cross-device communication module 196 every cycle or when a connection to the remote device is determined, or may be automatically sent by the remote device to the mobile phone 100 every cycle or when a connection to the mobile phone 100 is determined, and received by the mobile phone 100 using the cross-device communication module 196. This is not limited in this embodiment of the present application.

[0114] In some embodiments, in the mobile phone 100, the antenna 1 and the mobile communication module 150 are coupled, the antenna 2 and the wireless communication module 160 are coupled, and the antenna 1 and the cross-device communication module 196 are coupled or the antenna 2 and the cross-device communication module 196 are coupled, so that the mobile phone 100 can communicate with a network and another device using a wireless communication technology. The wireless communication technology can include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, IR technology, and / or the like. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a BeiDou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and / or a satellite-based augmentation system (SBAS).

[0115] The display 194 is configured to display a display interface of an application, etc. The display 194 includes a display panel. The display panel may use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini-LED, a Micro-LED, a Micro-OLED, and a quantum dot light-emitting diode (QLED), etc. In some embodiments, the mobile phone 100 may include one or N displays 194, where N is a positive integer greater than one.

[0116] Camera 193 is configured to capture still images or video and may include a front-facing camera and a rear-facing camera.

[0117] The internal memory 121 may be configured to store computer executable program code. The executable program code includes instructions. The processor 110 executes the instructions stored in the internal memory 121 to execute various functional applications and data processing on the mobile phone 100. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store the software code of an operating system and at least one application (e.g., application iQIYI and application WeChat), etc. The data storage area may store data (e.g., images or videos) generated in the process of using the mobile phone 100, etc. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a non-volatile memory, such as at least one magnetic disk storage device, a flash component, or a universal flash storage (UFS). In this embodiment of the present application, the internal memory 121 may store the software code / module for the method of opening a history page provided in this embodiment of the present application. When the software code / module is executed, the processor 110 may execute the steps of the method for opening a history page to achieve the purpose of quickly opening the page visit history of an application.

[0118] The external memory interface 120 can be used to connect an external storage card, for example, a micro SD card, to expand the storage capacity of the mobile phone 100. The external storage card communicates with the processor 110 through the external memory interface 120 to implement data storage functions. For example, files such as images and videos are stored in the external storage card. Obviously, the software code / module for the method for opening a history page provided in this embodiment of the present application can be alternatively stored in an external memory. The processor 110 can execute the above software code / module through the external memory interface 120 to perform the steps of the method for opening a history page, thereby achieving the purpose of quickly opening the page visit history of an application.

[0119] The mobile phone 100 may implement audio functions, such as playing or recording music, using an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, and an application processor, for example.

[0120] The fingerprint sensor 180A is configured to acquire a fingerprint. The mobile phone 100 may use the acquired fingerprint characteristics to implement fingerprint-based unlocking, application lock access, fingerprint-based photography, fingerprint-based call answering, and the like. Touch sensor 180B is also referred to as a "touch panel." Touch sensor 180B may be disposed on display 194. Touch sensor 180B and display 194 form a touch screen, which is also referred to as a "touch screen." Touch sensor 180B is configured to detect touch operations performed on or near the touch sensor. Touch sensor 108B may forward the detected touch operations to an application processor and determine the type of touch event. A visual output regarding the touch operation may be provided through display 194. In some other embodiments, touch sensor 180B may alternatively be disposed on the surface of mobile phone 100 at a location different from display 194.

[0121] Obviously, the sensor module 180 may further include a pressure sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, an optical proximity sensor, an ambient light sensor, and a bone conduction sensor, etc. The categories and types of sensors are not limited here in this embodiment of the present application.

[0122] Buttons 190 include a power button, a volume button, and the like. Buttons 190 may be mechanical buttons or may be touch buttons. Cell phone 100 may receive button inputs and generate key signal inputs associated with user settings and function control for cell phone 100.

[0123] The motor 191 may generate a vibration prompt. The motor 191 may be configured to generate an incoming vibration prompt and to provide touch vibration feedback. For example, touch operations performed in different applications (e.g., taking a photo and playing audio) may correspond to different vibration feedback effects.

[0124] Indicator 192 may be an indicator light and may be configured to indicate charging status and power changes, or may be configured to indicate messages, missed calls, notifications, and the like.

[0125] The SIM card interface 195 is used to connect a SIM card, which can be inserted into or removed from the SIM card interface 195 to implement contact or separation from the mobile phone 100.

[0126] The data synchronization module 197 is configured to synchronize the page visit history of the remote device and to send to the remote device, using the cross-device communication module 196, an open command used to open the page visit history of the remote device.

[0127] The data storage module 198 is configured to store the page visit history of the remote device. It should be understood that one or more of the page visit histories mentioned below may be stored in the data storage module 198. In some embodiments, the data block storage module 197 may be integrated into the internal memory 120 or the external memory, or may be independent from the internal memory 120 or the external memory.

[0128] It may be understood that the components illustrated in Figure 3 are not intended to be any particular limitation on the structure of the mobile phone 100. The mobile phone 100 may further include more or fewer components than those illustrated in the figure, may combine some components, may separate some components, or may have a different component configuration.

[0129] In some embodiments, the remote device may alternatively be a mobile phone. To describe the functions of each structure of the type of mobile phone that can be implemented in the embodiments of the present application, an example in which the remote device is a mobile phone is used below.

[0130] As shown in Fig. 4, the mobile phone 200 may include a processor 210, an external memory interface 220, an internal memory 221, a USB interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 3, an antenna 4, a mobile communication module 250, a wireless communication module 260, and an audio module 270, a sensor module 280, a button 290, a motor 291, an indicator 292, a camera 293, a display 294, a SIM card interface 295, a cross-device communication module 296, a task management 297, and a task storage module 298, etc. The structure of the audio module 270 shown in Fig. 4 may be the same as or similar to that of the audio module 170 shown in Fig. 3, and the structure of the sensor module 280 shown in Fig. 4 may be the same as or similar to that of the audio module 180 shown in Fig. 3. Details will not be described again here. Details will not be described again here.

[0131] In addition to the cross-device communication module 296, the task management module 297, and the task storage module 298, other structural functions of the mobile phone 200 may be the same or similar to the corresponding structural functions shown in Figure 3. Details will not be described again here.

[0132] The wireless communication function of the mobile phone 200 may be implemented by using an antenna 3, an antenna 4, a mobile communication module 250, a wireless communication module 260, a cross-device communication module 296, a modem processor, a baseband processor, and the like.

[0133] The cross-device communication module 296 is configured to synchronize the historical page information of the application of the mobile phone 200 to the local device. The historical page information may include page visit history corresponding to each of at least one application of the mobile phone 200. The mobile phone 200 may use the cross-device communication module 296 to transmit the historical page information to the local device every period or after it is determined that the synchronization request information transmitted by the local device is received, or the mobile phone 200 automatically transmits the historical page information to the local device when it is determined to connect to the local device. This is not limited in this embodiment of the present application.

[0134] In some embodiments, in the mobile phone 200, the antenna 3 and the mobile communication module 250 are coupled, the antenna 4 and the wireless communication module 260 are coupled, and the antenna 3 and the cross-device communication module 396 are coupled or the antenna 4 and the cross-device communication module 296 are coupled, so that the mobile phone 200 can communicate with a network and another device using a wireless communication technology. The wireless communication technology used in the mobile phone 200 can be the same as the wireless communication technology used in the mobile phone 100 shown in FIG. 3. Details will not be described again here.

[0135] In this embodiment of the present application, the internal memory 221 may store a software code / module for the method for opening a history page provided in this embodiment of the present application. When the software code / module is executed, the processor 210 may execute the procedure of the method for opening a history page to achieve the purpose of quickly opening the page visit history of an application.

[0136] Obviously, the software code / module for the method for opening a history page provided in this embodiment of the present application can alternatively be stored in an external memory. The processor 210 can execute the above software code / module through the external memory interface 220 to perform the steps of the method for opening a history page, thereby achieving the purpose of quickly opening the page visit history of an application.

[0137] The task management module 297 is configured to record historical page information of the mobile phone 200, and store the page visit history obtained by different applications in the mobile phone 200 in the task storage module 298. In response to the open command sent by the local device, the corresponding page visit history is opened.

[0138] The task storage module 298 is configured to group and store the page visit histories of different applications based on each application. In some embodiments, the task block storage module 298 may be integrated into the internal memory 220 or the external memory, or may be independent from the internal memory 220 or the external memory.

[0139] It may be understood that the components illustrated in Figure 4 are not intended to be any particular limitation on the structure of mobile phone 200. Mobile phone 200 may further include more or fewer components than those illustrated in the figure, may combine some components, may separate some components, or may have a different component configuration.

[0140] It should be understood that when the mobile phone 100 in Fig. 3 is used as a remote device, the mobile phone 100 may further include a task management module and a task storage module. The data storage module 198 and the task storage module may be the same module or may be different modules. This is not limited in this application. Alternatively, when the mobile phone 200 in Fig. 4 is used as a local device, the mobile phone 200 may further include a data synchronization module and a data storage module. The task storage module 298 and the data storage module may be the same module or may be different modules. This is not limited in this application.

[0141] The technical solutions provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0142] Before describing the embodiments of the present application, we will first describe and explain some terms used in the present application to help those skilled in the art to better understand.

[0143] Various applications (applications, abbreviated as app) may be installed on the local device and the remote device in the embodiment of the present application. An app is a software program that may implement one or more specific functions, such as a camera application, a text message application, a multimedia message application, various e-mail applications, WeChat, Tencent instant messaging software (QQ), WhatsApp Messenger, Line, a photo sharing application (Instagram), KakaoTalk, and DingTalk. The applications mentioned below may be default applications installed on the terminal device, or may be applications downloaded from a network or obtained by a user from another terminal device in the process of using the terminal device (e.g., applications sent by another terminal device). This is not specifically limited in this embodiment of the present application.

[0144] The terms used in the following embodiments are intended to merely describe particular embodiments and are not intended to limit the present application. As used in the specification and the appended claims of this application, the terms "one", "a", "the", and "this" in the singular form are intended to further include expressions such as "one or more", unless otherwise specified in the context. It should be further understood that in the embodiments of this application, "one or more" means one, two, or more, and "and / or" describes a correspondence relationship between associated objects and represents that three relationships may exist. For example, A and / or B may represent the case where only A is present, the case where both A and B are present, or the case where only B is present, where A and B may be singular or plural. The symbol " / " generally indicates an "or" relationship between associated objects. It should be further understood that in the embodiments of this application, terms such as "first" to "sixth" are merely used to distinguish in the description, but should not be understood as indicating or implying a relative importance or as indicating or implying a sequence.

[0145] References to "an embodiment" or "some embodiments" described herein indicate that one or more embodiments of the present application include the specific features, structures, or characteristics described with reference to those embodiments. Thus, phrases such as "in an embodiment," "in some embodiments," "in some other embodiments," and "in other embodiments" appearing in different places in this specification are not necessarily meant to refer to the same embodiment. Instead, unless specifically emphasized otherwise in another manner, the phrase means "one or more, but not all embodiments." The terms "including," "having," and variations thereof all mean "including, but not limited to," unless specifically emphasized otherwise in another manner.

[0146] With reference to FIG. 1 to FIG. 7A and FIG. 7B, the method for opening a history page provided in an embodiment of the present application is described in detail below.

[0147] For example, Figure 5 is a schematic diagram of the structure of a method for opening a history page according to an embodiment of the present application. The method can be applied to a local device. As shown in Figure 5, the method can include the following steps:

[0148] S501: A step of receiving historical page information of a remote device sent by the remote device, and obtaining a page visit history of at least one application by analyzing the historical page information, where the historical page information includes a page visit history of the at least one application of the remote device.

[0149] In some embodiments, when the local device is communicatively connected to the remote device, the local device may send synchronization request information to the remote device. The synchronization request information is used to request the remote device to synchronize the page visit history of different applications stored in the remote device to the local device. Obviously, the local device may alternatively send the synchronization request information to the remote device periodically based on a first preset time length, or the local device sends the synchronization request information to the remote device when it receives a control triggered by a user to send the synchronization request information to the remote device. Then, the local device may receive the history page information of the remote device sent by the remote device in response to the synchronization request information. The first preset time length may be set based on actual requirements. This is not specifically limited in this embodiment of the present application. For example, referring to FIG. 2 and FIG. 3, the local device may obtain the synchronization request information using a data synchronization module, and send the synchronization request information to the remote device using a cross-device communication module.

[0150] In some other embodiments, the local device may alternatively wait for the remote device to actively send the history page information of the remote device. For example, when establishing a communication connection to the local device, the remote device may automatically send the history page information of the remote device to the local device, or may periodically send the history page information of the remote device to the local device based on a second preset time length. The second preset time length may be set based on actual requirements. This is not specifically limited in this embodiment of the present application. For example, referring to FIG. 2 to FIG. 4, the remote device may use a cross-device communication module to send the history page information of the remote device to the local device.

[0151] In this embodiment of the present application, the local device periodically sends synchronization request information to the remote device based on a first preset time length, or the remote device periodically sends historical page information of the remote device to the local device based on a second preset time length, thereby updating the historical page information from the remote device stored in the local device, so that the freshness of the historical page information of the remote device stored in the local device can be ensured, thereby helping to improve the user experience.

[0152] In this embodiment of the present application, the history page information of the remote device can be synchronized to the local device in multiple ways, so that the history page information of the remote device can be easily synchronized to the local device, thereby helping to improve the user experience.

[0153] In some embodiments, when receiving the history page information of the remote device, the local device may analyze the history page information of the remote device to obtain the page visit history of at least one application. In a specific implementation process, referring to Figures 2 and 3, the local device may use a data synchronization module to analyze the acquired history page information of the remote device to obtain the page visit history of at least one application. The page visit history of the at least one application may include an application name, a page component name, additional data, a thumbnail, etc.

[0154] S502: Grouping page visit histories of at least one application based on each application, obtaining the page visit history of at least one group, and storing the page visit history of the at least one group, where each group of page visit histories includes an open instruction used to open each page visit history of each group of page visit histories.

[0155] In some embodiments, the open command used to open each page visit history of each group of page visit histories may include the application name of the application corresponding to each page visit history, the page component name, and the like.

[0156] In some embodiments, after the local device analyzes the historical page information of the remote device to obtain the page visit history of at least one application, the local device may group the page visit history of the at least one application based on each application, obtain the page visit history of the at least one group, and store the page visit history of the at least one group. For example, referring to Figures 2 and 3, the local device may store the page visit history of the at least one group in a data storage module. In this process, the local device may further notify a recent task label module to update the content of a user interface based on the page visit history of the at least one group.

[0157] In the process of specific implementation, the local device may store the page visit history of at least one group in several ways, examples of which are given below:

[0158] In example 1, the local device may determine whether a storage space currently used to store the page visit history of at least one group has reached a preset threshold. Upon determining that the storage space has reached the preset threshold, the local device may delete at least one earliest page visit history from the page visit history of the at least one group.

[0159] For example, the preset threshold may be set equal to 30M. When the storage space used by the local device to store the page visit history of the remote device reaches the preset threshold, the corresponding earliest page visit history of the currently stored page visit history may be deleted.

[0160] In Example 1, to save storage space, the local device may, by default, synchronously store page visit histories corresponding to the current date and the date closest to the current date in the page visit histories of at least one group.

[0161] In Example 1, the size of the storage space used by the local device to store the page visit history of at least one group may be set based on actual requirements. For example, a user may manually set the size of the storage space in a setting interface of the local device based on actual requirements.

[0162] In Example 1, the storage space of the local device for storing the page visit history on the remote device can be reduced, and the freshness of the page visit history on the remote device stored on the local device can be further guaranteed.

[0163] In example 2, the local device may store at least one page visit history in the at least one group of page visit histories, where the at least one page visit history is a page visit history in the at least one group of page visit histories, and a time length interval between a time of the page visit history and a current time is less than or equal to a preset time length and / or a page visit history time within a preset time.

[0164] For example, obviously, the preset time length can also be set based on actual requirements, for example, a user can set the preset time length in a setting interface of a local device based on actual requirements.

[0165] In Example 2, the preset time may be a time or date specified by a user, or may be a time interval between two dates specified by a user. This is not specifically limited in this embodiment of the present application. The user may set a preset time in the setting interface of the local device based on actual requirements, and may set the preset time to a touch control, etc. in the prompt information output by the local device after the local device obtains at least one group's page visit history. This is not specifically limited in this embodiment of the present application.

[0166] In Example 2, meeting different users' requirements for viewing page visit histories of remote devices corresponding to different time periods may facilitate users to view corresponding page visit histories. Meeting users' personalized requirements may help improve user experience.

[0167] S503: A first command to view the visit history is received, and in response to the first command, a tab corresponding to the page visit history of at least one group is opened.

[0168] In some embodiments, the first command may be an operation detected by the local device of flicking up / down on a display interface of the local device, or an operation detected by the local device of triggering a control used to open a tab corresponding to a page visit history, etc. The first command is not specifically limited in this embodiment of the present application, as long as the local device can open a tab in response to the first command.

[0169] In some embodiments, the tab may include a fourth control that may be used to switch between displaying the page visit history of the local device and the page visit history of the remote device on the tab. For example, as shown in FIG. 6, a user may tap the right portion (i.e., the gray portion) of the fourth control to cause the tab to display the page visit history of the remote device. A user may tap the left portion of the fourth control to cause the tab to display the page visit history of the local device (not shown in FIG. 6).

[0170] In an embodiment of the present application, the page visit history of different applications is recorded using tabs, so that multiple applications are compatible and do not need to rely on the application's local page visit history function.

[0171] In the embodiment of the present application, the fourth control is used to control the page visit history of the remote device or the page visit history of the local device to be displayed on the tab of the local device, so that the user can easily view the page visit history of different devices. Furthermore, the purpose of quickly opening the page visit history can be achieved, which helps to improve the user experience.

[0172] In some embodiments, a first preset operation may be performed on the tab, resulting in a switching between groups of page visit histories in at least one group of page visit histories. The first preset operation may include at least a left / right flick operation, or touch and hold a volume button such as "+" or "-". This is not specifically limited in this embodiment of the present application.

[0173] In a specific implementation process, the page visit history of each application may be displayed on the tab using an independent list window. The list window may display the icon of the terminal device and the application icon of the application corresponding to the page visit history currently displayed on the tab. For example, as shown in FIG. 6, FIG. 7A, and FIG. 7B, the terminal device and application corresponding to the page visit history currently displayed on the tab are a television and an application z. In this case, the television icon and the application z icon may be displayed in the upper left part of the current display interface of the tab. By flicking the tab left / right, the currently displayed page visit history corresponding to the application z may be switched to the page visit history of another application for display. For example, as shown in FIG. 7A and FIG. 7B, the page visit history of the application z may be switched to the page visit history of the application C by flicking the tab right.

[0174] In some embodiments, when a second group of page visit histories in the at least one group of page visit histories is currently displayed on the tab, a second preset operation may be performed on the tab to switch between page visit histories in the second group of page visit histories. The second preset operation may include at least an up / down flick operation, a tap on the display of the local device, or a touch on the home button of the local device, etc. This is not specifically limited in this embodiment of the present application.

[0175] For example, as shown in Fig. 6, the application corresponding to the page visit history of the second group is application z. By flicking the tab up / down, it is possible to switch between the page visit histories corresponding to application z.

[0176] In this embodiment of the present application, the tab corresponding to the page visit history may support switching between the page visit histories of different applications, so that the user can easily view the page visit histories of different applications and view each page visit history of different applications. Furthermore, the purpose of quickly opening the visit histories of different applications may be achieved, which helps to improve the user experience.

[0177] S504: Receive a second instruction used to open a page visit history of a first group on the tab and in the page visit history of at least one group, and in response to the second instruction, open the page visit history of the first group and / or send a first open instruction to a remote device, so that the remote device opens the page visit history of the first group according to the first open instruction.

[0178] In some embodiments, the second instruction may be an operation of tapping a thumbnail of the page visit history of the first group detected by the local device, and upon receiving the second instruction, the local device may open the page visit history of the first group and / or send a first open instruction to the remote device to control the remote device to open the page visit history of the first group.

[0179] In some embodiments, the page visit history displayed in the tab may be supported to be opened on a local device or a remote device. For example, referring to FIG. 6 and FIG. 8, the page visit history corresponding to application z is the page visit history of the first group. In this case, the first application is application z. When the current user taps the thumbnail of the poster image of the anime series a in the page visit history A of application z, the local device may display second prompt information for opening the page visit history A in the display interface of the tab. The second prompt information may include a fifth control and a sixth control. When the user taps the fifth control, the page visit history A may be opened on the local device. If it is determined that application z is not currently installed, the local device outputs first prompt information to present to the local device that application z needs to be installed. The first prompt information may include an installation instruction. For example, the first prompt information may display the content "Do you want to install the first application now?", the control "No", and the control "Yes". When detecting that the control "Yes" is triggered, in response to the installation instruction, the local device starts installing application z on the local device. When the user taps the sixth control, the page visit history A can be opened on the remote device. In a specific implementation process, when the communication connection between the remote device and the local device is disconnected, the color of the selection box corresponding to the fifth control is gray or another color, which indicates that there is no communication connection currently established between the local device and the remote device.

[0180] In this embodiment of the present application, when it is determined that the first application is not installed on the local device, the local device is prompted to install the first application, so that the local device is supported to open the page visit history of the first application, which can help achieve the purpose of quickly opening the page visit history and improve the user experience.

[0181] In a specific implementation process, when a remote device is selected to open the page visit history of the first group, the local device may regenerate a first open command based on the page information in the page visit history of the first group. The above first open command may include a minimum set of information required to open the page visit history of the first group. For example, referring to FIG. 6 and FIG. 8, the data format of the first open command may include a minimum set that can be used to open the page visit history of application z, such as application name, page component name, and page open mode, while the thumbnail included in the page visit history may be discarded. Optionally, the additional parameters may include at least a uniform resource locator (URL) address of the history page, and the page open mode may include page open modes such as single instance, multi-instance, floating window display, and full screen display. The application z is the application Bilibili (which can be identified using bili), and the page visit history A is used as an example. For example, the first open command may be expressed in the format (data exchange format) JSON (short for the English term JavaScript Object Notation) as follows:

number

[0182] In some other embodiments, the page visit history displayed in the tab may alternatively be supported to be opened on the local device and the remote device. For example, in response to the second command, the local device may display, on the tab corresponding to the page visit history, a first control used to open the page visit history of the first group on the local device, a second control used to open the page visit history of the first group on the remote device, and a third control used to synchronously open the page visit history of the first group on the local device and the remote device. The page visit history of the first group is opened on the local device when a first operation of tapping the first control is received. Alternatively, a first open command is sent to the remote device when a second operation of tapping the second control is received. Alternatively, a third operation of tapping the third control is received, the page visit history of the first group is opened on the local device and the remote device, and the first open command is sent to the remote device. For example, when the second command is received, the local device may output third prompt information. The third prompt information may include the first control to the third control. The page visit history of the first group may be opened on the local device when the local device receives a first operation of tapping a first control. Alternatively, the page visit history of the first group may be opened on the remote device when the local device receives a second operation of tapping a second control. Alternatively, the page visit history of the first group may be opened on the local device and the remote device when the local device receives a third operation of tapping a third control.

[0183] In this embodiment of the present application, the page visit history may be supported to be opened on a single terminal device, or the page visit history may be supported to be opened on multiple terminal devices, so that the user can easily select the corresponding terminal device to open the page visit history on the target terminal device, thereby achieving the purpose of quickly opening the page visit history and helping to improve the user experience.

[0184] In some embodiments, after opening the page visit history of the first group, the local device may further open the first page visit history in the page visit history of the first group. For example, when the local device receives the third instruction used to open the first page visit history, if the page visit history of the first group is opened on the local device, the first page visit history may be opened on the local device in response to the third instruction. Alternatively, if the page visit history of the first group is opened on the remote device, the second open instruction may be sent to the remote device in response to the third instruction. The second open instruction is used to control the remote device to open the first page visit history. Alternatively, if the page visit history of the first group is opened synchronously on the local device and the remote device, the first page visit history may be opened on the local device and the second open instruction may be sent to the remote device in response to the third instruction. The second open instruction may include a minimum set of information required to open the first page visit history, and the format of the minimum set of information may be the same as or similar to the format of the first open instruction. This is not limited in this embodiment of the present application.

[0185] For example, as shown in FIG. 6, the page visit history corresponding to application z is a first group of page visit histories, and two page visit histories in the first group of page visit histories are currently displayed in a tab. When a user taps any thumbnail in page visit history B or any display area in page visit history B, a second instruction may be generated. When the page visit history of the first group is opened on the local device, the local device may open page visit history B of application z in response to the second instruction. When the page visit history of the first group is opened on the remote device, the local device may send a second open instruction to the remote device in response to the second instruction to control the remote device to open page visit history B of application z. Alternatively, when the page visit history of the first group is synchronously opened on the remote device and the remote device, the local device may open page visit history B of application z and send a second open instruction to the remote device in response to the second instruction.

[0186] In this embodiment of the present application, different page visit histories may be supported to be opened on a single terminal device, or different page visit histories may be supported to be opened on multiple terminal devices synchronously, so that a user can easily select a corresponding terminal device to open at least one page visit history on a target terminal device, thereby achieving the purpose of quickly opening page visit histories and helping to improve user experience.

[0187] It should be noted that when the remote device is a Bluetooth speaker, a list of songs recently played by the Bluetooth speaker and an icon of the Bluetooth speaker may be displayed on the tab used by the local device to open the page visit history, as shown in Fig. 9. For the Bluetooth speaker, since the applications are not differentiated, the tab may be flicked up / down to switch between songs in the track list for display, as shown in Fig. 10. For the process of cooperation between the local device and the Bluetooth speaker, please refer to the above related description of the cooperation process between the local device and the remote device. Details will not be described again here.

[0188] In this embodiment of the present application, the history page information in different applications on the remote device can be synchronized to the local device, so that the local device can quickly access the history page information in different applications on the remote device. The local device can further control the remote device to quickly access the history page information in different applications on the remote device without needing to perform operations on the remote device and without needing to search the history page information in each of the different applications on the remote device. This can simplify the user's operation of searching for the history page information in different applications and increase the speed of opening the history pages in different applications, so that the history pages in different applications can be quickly opened, which can help improve the user experience.

[0189] With reference to Figures 1 and 2, 4, 11, and 12(a) to 12(c), the method of opening a history page provided in an embodiment of the present application will be described in detail below.

[0190] For example, Figure 11 is a schematic diagram of the structure of a method for opening a history page according to an embodiment of the present application. The method can be applied to a remote device. As shown in Figure 11, the method can include the following steps:

[0191] S801: A step of obtaining at least one group of page visit histories by grouping and storing historical page information of at least one application previously opened on the remote device based on each application, where the historical page information includes page visit histories of the at least one application on the remote device, and each group of the page visit histories may include an open instruction for opening each page visit history in each group of the page visit histories.

[0192] In some embodiments, a start activity instruction may be generated each time the remote device opens a new page in one of the at least one application. Page information of the new page is held in the start activity instruction, and the page information of the new page includes an application name, a page component name, additional parameters, and a page thumbnail corresponding to the new page. Optionally, the additional parameters may include at least a URL address of the new page. The remote device may store the page information of the new page based on the application and according to the start activity instruction to obtain a group of page visit histories. For example, referring to FIG. 2 and FIG. 4, the remote device may send the generated start activity instruction to a task management module. The remote device may group and store the history page information of at least one application previously opened on the remote device based on each application by using the task management module according to the start activity instruction to obtain at least one group of page visit histories.

[0193] For example, referring to FIG. 2, FIG. 4, and FIG. 12(a) to FIG. 12(c), the remote device is a television, and application C is used as an example. When the remote device opens application C and enters a home page in application C, the remote device may use the task management module to store the home page in application C as one page visit history, i.e., page visit history a (see FIG. 12(a)), in the task storage module. When the user taps "recommendation" in the home page, the recommendation interface in application C may be entered. In this case, the remote device may use the task management module to store the recommendation page in application C as one page visit history, i.e., page visit history b (see FIG. 12(b)), in the task storage module. When the user taps the thumbnail of the poster image of TV series k in the recommendation page, the detail interface of TV series k may be entered. In this case, the remote device may use the task management module to store the detail page of TV series k as one page visit history, i.e., page visit history c (see FIG. 12(c)), in the task storage module. In the process of storing the page visit history a, page visit history b, and page visit history c in application C in the task storage module, the remote device may further store thumbnails of contents in the home page, recommendation page, and detail page of TV series k in application C, and open instructions corresponding to each of the home page, recommendation page, and detail page of TV series k in application C. Correspondingly, when application C is closed and another application, for example, application A and application B, is opened, the remote device may record the page visit history opened in the other application of the remote device in the same or similar manner as that of recording the page visit history of application A. Details will not be described again here.

[0194] For example, the data format of the page visit history of the remote device may be in JSON format or another format, which is not limited in this embodiment of the present application. For example, application C is Bilibili, and the data format JSON of page history a in application C may be as follows:

number

[0195] It should be noted that the manner in which the remote device stores the page visit history of at least one group can be storage using a database, a cloud, or a local file, which is not limited in this embodiment of the present application.

[0196] In this embodiment of the present application, the remote device groups and stores historical page information of at least one application previously opened on the remote device based on each application, so that the remote device can easily manage the page visit history of different applications. Furthermore, the local device can subsequently easily synchronize the page visit history of the remote device.

[0197] S802: Synchronize the historical page information to the local device, so that the local device obtains the page visit history of at least one group after parsing the historical page information, and opens the page visit history of any one group in the page visit history of the at least one group according to the corresponding instruction.

[0198] In some embodiments, for the manner in which the remote device synchronizes the history page information to the local device, please refer to the relevant description of step S501 shown in Figure 5. Details will not be described again here.

[0199] In some embodiments, when the remote device receives the first open command, the remote device may analyze the first open command and open the page visit history of the first group in the page visit history of the at least one group according to the analyzed first open command. Optionally, the first open command may include a minimum set of information required to open the page visit history of the first group. For example, referring to FIG. 2 and FIG. 4, the remote device may use a cross-device communication module to receive the first open command sent by the local device. The cross-device communication module may analyze the first open command and send the first open command to a task management module. The task management module may further analyze the first open command and obtain a minimum set of information required to open the page visit history of the first group. Then, the remote device may open the page visit history of the first group based on the minimum set of information required to open the page visit history of the first group.

[0200] In a specific implementation process, the remote device may open the page visit history of the first group in a start activity manner according to the parsed first open instruction, and update the changes in the page visit history of the first group after the page visit history of the first group is opened, where the changes in the page visit history of the first group include at least one deleted and / or added page visit history in the page visit history of the first group.

[0201] For example, please refer to Fig. 12(a) to Fig. 12(c). After the remote device opens the page visit history of the first group, if the user enters a new page, one or more page visit histories are added to the page visit history of the first group. If the user does not need the page visit history a, the user can delete the page visit history a from the page visit history of the first group.

[0202] In an embodiment of the present application, the page visit history of the first group is updated in a start activity manner based on the remote device accessing a new page after the first open command is received, so that the phenomenon of part of the page visit history on the remote device being leaked can be avoided, thereby helping to improve the user experience.

[0203] In some embodiments, the remote device may further receive a second open instruction sent by the local device. The remote device may analyze the second open instruction and open the first page visit history in the page visit history of the first group according to the analyzed second open instruction. Optionally, the second open instruction may include a minimum set of information required to open the first page visit history. For example, referring to FIG. 2 and FIG. 4, the remote device may use a cross-device communication module to receive the second open instruction sent by the local device. The cross-device communication module may analyze the second open instruction and send the second open instruction to the task management module. The task management module may further analyze the second open instruction and obtain a minimum set of information required to open the first page visit history in the page visit history of the first group. Then, the remote device may open the first page visit history based on the minimum set of information required to open the first page visit history.

[0204] In a specific implementation process, the remote device can open the first page visit history in a start activity manner according to the parsed second open instruction, and update the change content information in the page visit history of the first group after the first page visit history is opened, where the change content information in the page visit history of the first group includes content information corresponding to at least one added page visit history to the page visit history of the first group or at least one updated page visit history in the page visit history of the first group.

[0205] For example, please further refer to FIG. 12(a) to FIG. 12(c). It is used as an example that the first page visit history is page visit history c. If the user watches a part of the video content of episode 1 of TV series k, when the user taps the control "episode 1" after the remote device opens page visit history c, the user can continue to watch the unplayed content of episode 1 of TV series k on the display of the remote device. In this case, the remote device may update the content information corresponding to the first page visit history to update the change information in the first group of page visit histories. Alternatively, when the user taps the thumbnail of the poster image of TV series h in the page visit history, the remote device may enter the details page of TV series h. In this case, the remote device may add one page visit history to the first group of page visit histories.

[0206] In an embodiment of the present application, the page visit history of the first group is updated in a start activity manner based on the remote device accessing a new page or the continuing execution of uncompleted content information in the first page visit history after the second open command is received, so that the phenomenon of part of the page visit history on the remote device being leaked can be avoided, thereby helping to improve the user experience.

[0207] It should be noted that when the remote device is a Bluetooth speaker, the manner in which the Bluetooth speaker stores each recently played song can be the same as or similar to the manner in which the remote device stores each group of page visit history. For the process of cooperation between the Bluetooth speaker and the local device, please refer to the above related description of the process of cooperation between the remote device and the local device. Details will not be described again here.

[0208] In an embodiment of the present application, the history page information in different applications on the remote device is recorded and synchronized with the connected local device, so that the local device can quickly access the history page information in different applications on the remote device. The local device can further control the remote device to quickly access the history page information in different applications on the remote device without needing to perform operations on the remote device and without needing to search the history page information in each of the different applications on the remote device. This can simplify the user's operation of searching for the history page information in different applications and increase the speed of opening the history pages in different applications, so that the history pages in different applications can be quickly opened, which can help improve the user experience.

[0209] It should be understood that in the embodiments of the present application, the remote device and the local device may perform all or part of the steps in the embodiments of the present application. These steps are merely examples. In the embodiments of the present application, other steps or various modifications of the steps may be further performed. In addition, the steps may be performed in a different sequence than presented in the embodiments of the present application, and all steps in the embodiments of the present application may not need to be performed.

[0210] In the embodiments of the present application, unless otherwise specified or logically inconsistent, the terms and / or descriptions in different embodiments are consistent and may be cross-referenced. The technical features in different embodiments may be combined to form a new embodiment according to the internal logical relationship between the different embodiments.

[0211] The solutions provided in the embodiments of the present application are described above in terms of the interaction between the local device and the remote device. It should be understood that in order to implement the aforementioned functions, the local device and the remote device include corresponding hardware structures and / or software modules for performing the functions. Those skilled in the art should easily recognize that the units, algorithms, and steps in the examples described in connection with the embodiments disclosed herein can be implemented in the form of hardware or a combination of hardware and computer software in the present application. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application of the technical solution and the design constraints. Those skilled in the art may use different methods to implement the functions described for each specific application, but such implementation should not be considered to go beyond the scope of the present application.

[0212] In the embodiment of the present application, the functional modules of the local device or the remote device may be divided according to the above-mentioned method example. For example, each functional module may be obtained by dividing based on each corresponding function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that in the embodiment of the present application, the division into modules is an example, which is merely a logical function division, and there may be other divisions in actual implementation.

[0213] In the case where an integrated unit (module) is used, FIG. 13 is a schematic diagram of the structure of a local device according to an embodiment of the present application. As shown in FIG. 13, the local device 1200 may include at least one processor 1201 and a memory 1202. The memory 1202 is configured to store one or more computer programs, for example, to store one or more computer programs required for the local device 1200. The at least one processor 1201 is configured to support the local device 1200 to implement the above-mentioned method for opening a history page. For example, when the one or more computer programs stored in the memory 1202 are executed by the at least one processor 1201, the local device 1200 may implement any possibility of the embodiment of the method for opening a history page shown in FIG. 5 and / or is configured to implement another embodiment described herein. In addition, the local device 1200 may further include a communication interface 1203. The communication interface may be configured to communicate with another device or a communication network, for example, an Ethernet, a RAN, a WLAN, or a wired access network.

[0214] In the case where an integrated unit (module) is used, FIG. 14 is a schematic diagram of the structure of a remote device according to an embodiment of the present application. As shown in FIG. 14, the remote device 1300 may include at least one processor 1301 and a memory 1302. The memory 1302 is configured to store one or more computer programs, for example, to store one or more computer programs required for the remote device 1300. The at least one processor 1301 is configured to support the remote device 1300 to implement the above-mentioned method for opening a history page. For example, when the one or more computer programs stored in the memory 1302 are executed by the at least one processor 1301, the remote device 1300 may implement any possibility of the embodiment of the method for opening a history page shown in FIG. 8 and / or is configured to implement another embodiment described herein. In addition, the remote device 1300 may further include a communication interface 1303. The communication interface may be configured to communicate with another device or communication network, for example, an Ethernet, a RAN, a WLAN, or a wired access network.

[0215] Based on the same concept as that in the above-mentioned method embodiment, the embodiment of the present application further provides a local device. The local device includes one or more processors and one or more memories or non-volatile storage media. The one or more processors are connected to one or more memories or non-volatile storage media. The one or more memories or non-volatile storage media store computer instructions or computer programs. The one or more processors execute computer instructions or computer programs to implement any one of the possibilities of the embodiment of the method for opening a history page shown in FIG. 5 and FIG. 8 and / or to implement other embodiments described herein.

[0216] Based on the same concept as that in the above-mentioned method embodiment, the embodiment of the present application further provides a remote device. The remote device includes one or more processors and one or more memories or non-volatile storage media. The one or more processors are connected to one or more memories or non-volatile storage media. The one or more memories or non-volatile storage media store computer instructions or computer programs. The one or more processors execute computer instructions or computer programs to implement any one of the possibilities of the embodiment of the method for opening a history page shown in FIG. 5 and FIG. 8 and / or to implement other embodiments described herein.

[0217] Based on the same concept as that in the above-mentioned method embodiment, the embodiment of the present application further provides a terminal device, which includes any one of the possibilities for executing the method embodiment for opening a history page shown in Figure 5 and Figure 8, and / or is configured to implement modules / units in other embodiments described herein. These modules / units may be implemented by hardware, or may be implemented by hardware executing corresponding software.

[0218] Based on the same concept as that in the above-mentioned method embodiment, the embodiment of the present application further provides a chip, which is coupled to a memory in a terminal device and configured to call a computer program stored in the memory and execute any one of the possibilities of the method embodiment for opening a history page shown in Figure 5 and Figure 8, and / or configured to implement other embodiments described herein. In the embodiment of the present application, "coupled" means that two components are directly or indirectly combined with each other.

[0219] Based on the same concept as that in the above-mentioned method embodiment, the embodiment of the present application further provides a graphical user interface of a terminal device. The terminal device has a display, one or more memories, and one or more processors. The one or more processors are configured to execute one or more computer programs stored in the one or more memories. The graphical user interface includes any one of the possibilities of the terminal device to execute the above-mentioned embodiment of the method for opening a history page as shown in Figures 5 and 8, and / or a graphical user interface displayed to implement other embodiments described herein.

[0220] Based on the same concept as that in the above-mentioned method embodiment, the embodiment of the present application further provides a computer-readable storage medium or a non-volatile storage medium. The computer-readable storage medium or the non-volatile storage medium stores computer instructions or computer programs. When the computer instructions or computer programs are executed on a computer, the computer is enabled to execute any one of the above-mentioned embodiments of the method for opening a history page and the possible implementation forms of the embodiments. Alternatively, when the computer instructions or computer programs are executed on one or more processors, a local device including the above-mentioned one or more processors is enabled to execute any one of the above-mentioned embodiments of the method for opening a history page and the possible implementation forms of the embodiments, for example, to execute any step in the embodiment of the method for opening a history page shown in FIG. 5 and FIG. 8 and / or execute another process of the technology described herein, or a remote device including one or more processors is enabled to execute any one of the above-mentioned embodiments of the method for opening a history page or the possible implementation forms of the embodiments, for example, to execute any step in the embodiment of the method for opening a history page shown in FIG. 5 and FIG. 8 and / or execute another process of the technology described herein.

[0221] Based on the same concept as that in the above-mentioned method embodiment, the embodiment of the present application further provides a program product. The computer program product is configured to store a computer program. When the computer program is executed on a computer, the computer is capable of executing any one of the above-mentioned embodiments of the method for opening a history page or the possible implementation forms of the embodiments, for example, performing any step in the embodiment of the method for opening a history page as shown in FIG. 5 and FIG. 8 and / or performing another process of the technology described herein.

[0222] Based on the same concept as that in the above-mentioned method embodiment, the embodiment of the present application further provides a chip. The chip may include at least one processor and an interface. The interface may be a code / data read / write interface, and the interface is configured to provide computer-executable instructions (the computer-executable instructions may be stored in a memory and read directly from the memory or pass through another component) to the at least one processor. The at least one processor is configured to execute the computer-executable instructions to perform any one of the above-mentioned embodiments of the method for opening a history page and possible implementation forms of the embodiments, for example, to perform any step in the embodiment of the method for opening a history page shown in FIG. 5 and FIG. 8 and / or to perform another process of the technology described herein.

[0223] Based on the same concept as that in the above-mentioned method embodiment, the embodiment of the present application further provides a multi-device cooperation system. The system includes a plurality of terminal devices. The plurality of devices includes a terminal device used as a local device and a terminal device used as a remote device. The terminal device used as a local device is configured to execute all or part of the steps shown in Figures 5 and 8 or the steps performed by the local device of the solution provided in the embodiment of the present application. The terminal device used as a remote device is configured to execute all or part of the steps shown in Figures 5 and 8 or the steps performed by the remote device of the solution provided in the embodiment of the present application.

[0224] It should be understood that the processor in the embodiment of the present application (the processor or processing unit shown in FIG. 13 and FIG. 14) may be an integrated circuit chip having signal processing capabilities. In implementation, the steps in the above-mentioned embodiment of the method for opening a history page as shown in FIG. 5 and FIG. 8 are implemented using hardware integrated logic circuits in the processor or processing unit, or instructions in the form of software. The processor or processing unit may be a programmable logic component, such as a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or another programmable logic component, a transistor logic component, a hardware component, or any combination thereof; or a combination for implementing a computing function, such as a combination including one or more microprocessors, or a combination of a DSP and a microprocessor, etc.

[0225] It should be understood that the memory in the embodiments of the present application may be volatile or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM) and is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DR RAM). It should be noted that memory in the systems and methods described herein is intended to include, without being limited to, these and any other suitable types of memory.

[0226] The various exemplary logic units and circuits described in the embodiments of this application may implement or operate the described functions using a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of the foregoing designs. A general-purpose processor may be a microprocessor. Optionally, a general-purpose processor may alternatively be any conventional processor, controller, microcontroller, or state machine. A processor may alternatively be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other similar configuration.

[0227] The steps of the method or algorithm described in the embodiments of the present application may be directly embedded in hardware, in a software unit executed by a processor, or a combination thereof. The software unit may be stored in a RAM, a flash memory, a ROM, an EPROM, an EEPROM, a register, a hard disk, a removable magnetic disk, a CD-ROM, or any other form of storage medium in the art. For example, the storage medium may be connected to the processor, so that the processor can read information from the storage medium and write information to the storage medium. Optionally, the storage medium may alternatively be integrated into the processor. The processor and the storage medium may be located in an ASIC. The ASIC may be located in a communication device (e.g., a local device or a remote device), for example, in different components of the communication device.

[0228] All or some of the above-mentioned embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, the procedures or functions described in the embodiments of the present application are executed completely or partially. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or another programmable device. The computer programs or instructions may be stored in a computer-readable storage medium or transmitted using a computer-readable storage medium. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device, such as a server that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; an optical medium, such as a DVD; or a semiconductor medium, such as a solid-state drive (SSD).

[0229] The embodiments of the present application are described with reference to flowcharts and / or block diagrams of methods, devices, and computer program products used in the embodiments. It should be understood that computer program instructions may be used to implement each step and / or each block in the flowcharts and / or block diagrams, and combinations of steps and / or blocks in the flowcharts and / or block diagrams. These computer program instructions may provide a processor of a general purpose computer, a special purpose computer, an embedded processor, or another programmable data processing device to generate a machine, such that the instructions may be executed by the processor of the computer or another programmable data processing device to generate an apparatus for implementing a particular function in one or more steps in the flowcharts and / or one or more blocks in the block diagrams.

[0230] The computer program instructions may alternatively be stored in a computer-readable memory that may direct a computer or another programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable memory may be used to generate an artifact that includes an instruction apparatus that implements a particular function in one or more steps of the flowcharts and / or one or more blocks of the block diagrams.

[0231] The computer program instructions may alternatively be loaded into a computer or other programmable data processing device such that a sequence of operations and steps are executed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide steps for implementing a particular function in one or more steps in the flowcharts and / or one or more blocks in the block diagrams.

[0232] Although the embodiments of the present application have been described with reference to certain features, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the embodiments of the present application. Correspondingly, this specification and the accompanying drawings are merely examples for illustrating the embodiments of the present application as defined by the claims, and are to be considered to cover any or all modifications, variations, combinations, or equivalents within the scope of the embodiments of the present application.

Claims

1. 1. A method for opening a history page, comprising: receiving historical page information at the remote device sent by the remote device and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; grouping the page visit histories of the at least one application by application to obtain at least one group of page visit histories, and storing the at least one group of page visit histories, wherein each group of page visit histories includes an open instruction used to open each page visit history in each group of page visit histories; receiving a first instruction to view a visit history and, in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device, so that the remote device opens the page visit history of the first group in accordance with the first open instruction. Equipped with After the step of opening the page visit history of the first group in response to the second command and / or sending a first open command to the remote device, the method further comprises: receiving a third command used to open a first page visit history in the first group of page visit histories; and opening the first page visit history in response to the third instruction if the first group of page visit history is opened on the local device; or sending a second open command to the remote device in response to the third command if the first group of page visit histories is opened on the remote device, where the second open command is used to control the remote device to open the first group of page visit histories; or in response to the third command, if the first group of page visit histories are synchronously opened on the local device and the remote device, opening the first page visit histories on the local device and sending the second open command to the remote device. A method comprising:

2. The step of opening the page visit history of the first group in response to the second command and / or sending a first open command to the remote device includes: displaying on the tab, in response to the second instruction, a first control used to open a page visit history of the first group on a local device, a second control used to open a page visit history of the first group on the remote device, and a third control used to open the page visit history of the first group synchronously on the local device and the remote device; and opening a page visit history of the first group on the local device when a first operation of tapping the first control is received; or sending the first open command to the remote device when a second operation of tapping the second control is received; or opening a page visit history of the first group on the local device and on the remote device and sending the first open command to the remote device when a third operation of tapping the third control is received. The method of claim 1 , comprising:

3. A method for opening a history page, comprising: receiving historical page information at the remote device sent by the remote device and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; grouping the page visit histories of the at least one application by application to obtain at least one group of page visit histories, and storing the at least one group of page visit histories, wherein each group of page visit histories includes an open instruction used to open each page visit history in each group of page visit histories; receiving a first instruction to view a visit history and, in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device, so that the remote device opens the page visit history of the first group in accordance with the first open instruction. Equipped with The step of opening the page visit history of the first group in response to the second command and / or sending a first open command to the remote device includes: displaying on the tab, in response to the second instruction, a first control used to open a page visit history of the first group on a local device, a second control used to open a page visit history of the first group on the remote device, and a third control used to open the page visit history of the first group synchronously on the local device and the remote device; and opening a page visit history of the first group on the local device when a first operation of tapping the first control is received; or sending the first open command to the remote device when a second operation of tapping the second control is received; or opening a page visit history of the first group on the local device and on the remote device and sending the first open command to the remote device when a third operation of tapping the third control is received. A method comprising:

4. A method for opening a history page, comprising: receiving historical page information at the remote device sent by the remote device and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; grouping the page visit histories of the at least one application by application to obtain at least one group of page visit histories, and storing the at least one group of page visit histories, wherein each group of page visit histories includes an open instruction used to open each page visit history in each group of page visit histories; receiving a first instruction to view a visit history and, in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and sending a first open instruction to the remote device in response to the second instruction, such that the remote device opens the page visit history of the first group according to the first open instruction. A method comprising:

5. After the step of storing the page visit history of the at least one group, the method further comprises: determining whether the storage space currently being used to store the page visitation history of the at least one group has reached a preset threshold; and deleting at least one earliest page visit history from the at least one group of page visit histories when the storage space reaches the preset threshold. The method according to claim 1 , comprising:

6. The step of storing a page visit history of the at least one group comprises:

5. A method according to claim 1, further comprising: storing at least one page visit history in the page visit history of the at least one group; wherein the at least one page visit history is a page visit history in the page visit history of the at least one group, and a time length interval between a time of the page visit history and a current time is less than or equal to a predetermined time length and / or the time of the page visit history is within a predetermined time.

7. performing a first preset operation on the tab to switch between groups of page visit histories in the at least one group of page visit histories, the first preset operation including at least a left / right flick operation; 7. The method of claim 1, wherein when a page visit history of a second group in the page visit history of the at least one group is currently displayed on the tab, performing a second preset operation on the tab switches between page visit histories in the page visit history of the second group, the second preset operation including at least an up / down flick operation.

8. Prior to the step of opening the page visit history of the first group in response to the second command and / or sending a first open command to the remote device, the method further comprises: determining that a first application corresponding to the first group of page visit histories is not installed on the local device; outputting first prompt information used to indicate to the local device that the first application needs to be installed, where the first prompt information includes installation instructions; and initiating installation of the first application on the local device in response to the installation command. The method of claim 7 comprising:

9. A method for opening a history page, comprising: receiving historical page information at the remote device sent by the remote device and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; grouping the page visit histories of the at least one application by application to obtain at least one group of page visit histories, and storing the at least one group of page visit histories, wherein each group of page visit histories includes an open instruction used to open each page visit history in each group of page visit histories; receiving a first instruction to view a visit history and, in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device, so that the remote device opens the page visit history of the first group in accordance with the first open instruction. Equipped with Prior to the step of opening the page visit history of the first group in response to the second command and / or sending a first open command to the remote device, the method further comprises: determining that a first application corresponding to the first group of page visit histories is not installed on the local device; outputting first prompt information used to indicate to the local device that the first application needs to be installed, where the first prompt information includes installation instructions; and initiating installation of the first application on the local device in response to the installation command. A method comprising:

10. 10. The method of claim 1, wherein the first opening instructions include a minimum set of information required to open the page visit history of the first group, and the second opening instructions include a minimum set of information required to open a first page visit history in the page visit history of the first group.

11. A method for opening a history page, comprising: obtaining at least one group of page visit histories by grouping and storing historical page information of at least one application previously opened on the remote device by application, where the historical page information includes page visit histories of the at least one application on the remote device, and each group of the page visit histories includes an open instruction used to open each page visit histories in each group of the page visit histories; and Synchronizing the historical page information to a local device, so that the local device obtains the page visit history of the at least one group after analyzing the historical page information, and opens the page visit history of any one group in the page visit history of the at least one group according to a corresponding instruction. Equipped with After the step of synchronizing the historical page information to a local device, the method further comprises: receiving a first open command sent by the local device; and parsing the first open command and opening a page visit history of a first group in the page visit history of the at least one group according to the parsed first open command; A method comprising:

12. Prior to the step of obtaining the page visit history of at least one group by grouping and storing historical page information of at least one application previously opened on the remote device by application, the method further comprises: generating a start activity instruction each time a new page of an application in the at least one application is opened, where page information of the new page is held in the start activity instruction, and the page information of the new page includes an application name, a page component name, additional parameters, and a page thumbnail corresponding to the new page; and obtaining a group of page visit histories by storing the page information of the new page based on the application and in accordance with the start activity instruction; The method of claim 11 , comprising:

13. After the step of receiving a first open command sent by the local device, the method further comprises: receiving a second open command sent by the local device; and parsing the second open command and opening a first page visit history in the page visit history of the first group according to the parsed second open command; The method according to claim 11 or 12, comprising:

14. The step of opening a page visit history of a first group in the page visit history of the at least one group according to the parsed first open command includes: Opening the page visit history of the first group in a start activity manner according to the analyzed first open command, and updating the changes in the page visit history of the first group after the page visit history of the first group is opened, where the changes in the page visit history of the first group include at least one deleted and / or added page visit history in the page visit history of the first group.

13. The method of claim 11 or 12, having the following structure:

15. The step of opening a first page visit history in the first group of page visit histories according to the parsed second open command includes: Opening the first page visit history in a start activity manner according to the parsed second open command, and updating change information in the page visit history of the first group after the first page visit history is opened, where the change information in the page visit history of the first group includes content information corresponding to at least one added page visit history in the page visit history of the first group, or at least one updated page visit history in the page visit history of the first group.

14. The method of claim 13, comprising:

16. 16. A method according to any one of claims 11 to 15, wherein the first opening instructions include a minimum set of information required to open a first group's page visit history in the page visit history of the at least one group, and the second opening instructions include a minimum set of information required to open a first page visit history in the page visit history of the first group.

17. one or more processors; and One or more memories A local device comprising: The one or more memories store one or more computer programs, the one or more computer programs including instructions that, when executed by the one or more processors, cause the local device to perform the following steps: receiving historical page information at the remote device sent by the remote device and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; grouping the page visit histories of the at least one application by application to obtain at least one group of page visit histories, and storing the at least one group of page visit histories, wherein each group of page visit histories includes an open instruction used to open each page visit history in each group of page visit histories; receiving a first instruction to view a visit history and, in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; and receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device, so that the remote device opens the page visit history of the first group in accordance with the first open instruction. It becomes possible to carry out When the instructions are executed by the one or more processors, the local device performs the following steps: receiving a third command used to open a first page visit history in the first group of page visit histories; and opening the first page visit history in response to the third instruction if the first group of page visit history is opened on the local device; or sending a second open command to the remote device in response to the third command if the first group of page visit histories is opened on the remote device, where the second open command is used to control the remote device to open the first group of page visit histories; or in response to the third command, if the first group of page visit histories are synchronously opened on the local device and the remote device, opening the first page visit histories on the local device and sending the second open command to the remote device. Specifically, it becomes possible to run the local device.

18. When the instructions are executed by the one or more processors, the local device performs the following steps: displaying on the tab, in response to the second instruction, a first control used to open a page visit history of the first group on the local device, a second control used to open a page visit history of the first group on the remote device, and a third control used to open the page visit history of the first group synchronously on the local device and the remote device; and opening a page visit history of the first group on the local device when a first operation of tapping the first control is received; or sending the first open command to the remote device when a second operation of tapping the second control is received; or opening a page visit history of the first group on the local device and on the remote device and sending the first open command to the remote device when a third operation of tapping the third control is received. The local device of claim 17 , wherein the local device is specifically enabled to execute the steps:

19. One or more processors; and One or more memories A local device comprising: The one or more memories store one or more computer programs, the one or more computer programs including instructions that, when executed by the one or more processors, cause the local device to perform the following steps: receiving historical page information at the remote device sent by the remote device and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; grouping the page visit histories of the at least one application by application to obtain at least one group of page visit histories, and storing the at least one group of page visit histories, wherein each group of page visit histories includes an open instruction used to open each page visit history in each group of page visit histories; receiving a first instruction to view a visit history and, in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; and receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device, so that the remote device opens the page visit history of the first group in accordance with the first open instruction. It becomes possible to carry out When the instructions are executed by the one or more processors, the local device performs the following steps: displaying on the tab, in response to the second instruction, a first control used to open a page visit history of the first group on the local device, a second control used to open a page visit history of the first group on the remote device, and a third control used to open the page visit history of the first group synchronously on the local device and the remote device; and opening a page visit history of the first group on the local device when a first operation of tapping the first control is received; or sending the first open command to the remote device when a second operation of tapping the second control is received; or opening a page visit history of the first group on the local device and on the remote device and sending the first open command to the remote device when a third operation of tapping the third control is received. Specifically, it becomes possible to run the local device.

20. One or more processors; and One or more memories A local device comprising: The one or more memories store one or more computer programs, the one or more computer programs including instructions that, when executed by the one or more processors, cause the local device to perform the following steps: receiving historical page information at the remote device sent by the remote device and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; grouping the page visit histories of the at least one application by application to obtain at least one group of page visit histories, and storing the at least one group of page visit histories, wherein each group of page visit histories includes an open instruction used to open each page visit history in each group of page visit histories; receiving a first instruction to view a visit history and, in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; and receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and in response to the second instruction, sending a first open instruction to the remote device, such that the remote device opens the page visit history of the first group according to the first open instruction. It allows you to run the command on a local device.

21. When the instructions are executed by the one or more processors, the local device performs the following steps: determining whether the storage space currently being used to store the page visitation history of the at least one group has reached a preset threshold; and deleting at least one earliest page visit history from the at least one group of page visit histories when the storage space reaches the preset threshold.

21. The local device of claim 17, further comprising:

22. When the instructions are executed by the one or more processors, the local device performs the following steps: Storing at least one page visit history in the page visit history of the at least one group, where the at least one page visit history is a page visit history in the page visit history of the at least one group, and a time length interval between a time of the page visit history and a current time is less than or equal to a preset time length and / or the time of the page visit history is within a preset time.

21. A local device according to any one of claims 17 to 20, which is specifically enabled to execute:

23. When the instructions are executed by the one or more processors, the local device performs the following steps: performing a first preset operation on the tab to switch between groups of page visit histories in the at least one group of page visit histories, where the first preset operation includes at least a left / right flick operation; When a page visit history of a second group in the page visit history of the at least one group is currently displayed on the tab, performing a second preset operation on the tab to switch between page visit histories in the page visit history of the second group, where the second preset operation includes at least an up / down flick operation.

23. A local device according to any one of claims 17 to 22, which is specifically enabled to execute:

24. When the instructions are executed by the one or more processors, the local device performs the following steps: determining that a first application corresponding to the first group of page visit histories is not installed on the local device; outputting first prompt information used to indicate to the local device that the first application needs to be installed, where the first prompt information includes installation instructions; and initiating installation of the first application on the local device in response to the installation command.

23. The local device of claim 22, wherein the local device is specifically enabled to execute:

25. One or more processors; and One or more memories A local device comprising: The one or more memories store one or more computer programs, the one or more computer programs including instructions that, when executed by the one or more processors, cause the local device to perform the following steps: receiving historical page information at the remote device sent by the remote device and parsing the historical page information to obtain a page visit history of at least one application, where the historical page information includes the page visit history of the at least one application on the remote device; grouping the page visit histories of the at least one application by application to obtain at least one group of page visit histories, and storing the at least one group of page visit histories, wherein each group of page visit histories includes an open instruction used to open each page visit history in each group of page visit histories; receiving a first instruction to view a visit history and, in response to the first instruction, opening a tab corresponding to the page visit history of the at least one group; and receiving a second instruction used to open a page visit history of a first group on the tab and in the page visit history of the at least one group, and opening the page visit history of the first group in response to the second instruction and / or sending a first open instruction to the remote device, so that the remote device opens the page visit history of the first group in accordance with the first open instruction. It becomes possible to carry out When the instructions are executed by the one or more processors, the local device performs the following steps: determining that a first application corresponding to the first group of page visit histories is not installed on the local device; outputting first prompt information used to indicate to the local device that the first application needs to be installed, where the first prompt information includes installation instructions; and initiating installation of the first application on the local device in response to the installation command. Specifically, it becomes possible to run the local device.

26. one or more processors; and One or more memories A remote device comprising: The one or more memories store one or more computer programs, the one or more computer programs including instructions, which when executed by the one or more processors, cause the remote device to perform the following steps: obtaining at least one group of page visit histories by grouping and storing historical page information of at least one application previously opened on the remote device by application, where the historical page information includes page visit histories of the at least one application on the remote device, and each group of the page visit histories includes an open instruction used to open each page visit histories in each group of the page visit histories; and Synchronizing the historical page information to a local device, so that the local device obtains the page visit history of the at least one group after analyzing the historical page information, and opens the page visit history of any one group in the page visit history of the at least one group according to a corresponding instruction. It becomes possible to carry out When the instructions are executed by the one or more processors, the remote device performs the following steps: receiving a first open command sent by the local device; and parsing the first open command and opening a page visit history of a first group in the page visit history of the at least one group according to the parsed first open command; Specifically, it becomes possible to run on a remote device.

27. When the instructions are executed by the one or more processors, the remote device performs the following steps: generating a start activity instruction each time a new page of an application in the at least one application is opened, where page information of the new page is held in the start activity instruction, and the page information of the new page includes an application name, a page component name, additional parameters, and a page thumbnail corresponding to the new page; and obtaining a group of page visit histories by storing the page information of the new page based on the application and in accordance with the start activity instruction; 27. The remote device of claim 26, wherein the remote device is specifically enabled to execute:

28. When the instructions are executed by the one or more processors, the remote device performs the following steps: receiving a second open command sent by the local device; and parsing the second open command and opening a first page visit history in the page visit history of the first group according to the parsed second open command; 28. A remote device according to claim 26 or 27, which is specifically enabled to execute:

29. When the instructions are executed by the one or more processors, the remote device performs the following steps: Opening the page visit history of the first group in a start activity manner according to the analyzed first open command, and updating the changes in the page visit history of the first group after the page visit history of the first group is opened, where the changes in the page visit history of the first group include at least one deleted and / or added page visit history in the page visit history of the first group.

28. A remote device according to claim 26 or 27, which is specifically enabled to execute:

30. When the instructions are executed by the one or more processors, the remote device performs the following steps: Opening the first page visit history in a start activity manner according to the parsed second open command, and updating change information in the page visit history of the first group after the first page visit history is opened, where the change information in the page visit history of the first group includes content information corresponding to at least one added page visit history in the page visit history of the first group, or at least one updated page visit history in the page visit history of the first group.

30. The remote device of claim 28, wherein the remote device is specifically enabled to execute:

31. A computer program product for causing a computer to carry out the method according to any one of claims 1 to 10 or the method according to any one of claims 11 to 16.

32. A graphical user interface on a terminal device, the terminal device having a display, one or more memories, and one or more processors, the one or more processors configured to execute one or more computer programs stored in the one or more memories, the graphical user interface comprising a graphical user interface that is displayed when the terminal device executes a method according to any one of claims 1 to 10 or a method according to any one of claims 11 to 16.

Citation Information

Patent Citations

  • Information processor and information processing method

    JP2012008770A

  • Information processor and information processing method

    JP2012212191A

  • web browser history

    JP2016520936A

  • Information processing device, browsing history sorting method, and browsing history sorting program

    WO2014073037A1