Multi-platform pattern-based user interfaces
US-2018107343-A1 · Apr 19, 2018 · US
US12047445B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12047445-B2 |
| Application number | US-202118043157-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 3, 2021 |
| Priority date | Aug 31, 2020 |
| Publication date | Jul 23, 2024 |
| Grant date | Jul 23, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An application interface migration method includes: receiving the recovery instruction by using a second distributed service; generating a recovery routing stack based on the page routing data, and load a first page based on the recovery routing stack and a current page routing stack; checking the UI binding data based on a declaration field corresponding to scenario information; storing the UI binding data in a shared data segment of a target application if the check succeeds; and refreshing a component view of the first page.
Opening claim text (preview).
What is claimed is: 1. An application interface migration method, applied to an electronic device, wherein the application interface migration method comprises: receiving a recovery instruction by using a second distributed service, wherein the recovery instruction is used to indicate to recover a user interface (UI) state of a target application on the electronic device, the recovery instruction comprises page routing data and UI binding data, and the UI binding data is bound to a component of the target application; in response to the recovery instruction, generating a recovery routing stack based on the page routing data, and loading a first page based on the recovery routing stack and a current page routing stack of the electronic device; checking compatibility of the UI binding data based on a declaration field corresponding to scenario information of the electronic device; and storing the UI binding data in a shared data segment of the target application if the compatibility of the UI binding data is successfully checked; and refreshing a component view that is on the first page and that is related to the UI binding data. 2. The application interface migration method according to claim 1 , wherein the recovery instruction further comprises component state data, and after the storing the UI binding data in the shared data segment of the target application, the application interface migration method further comprises: determining a target component corresponding to the component state data in the target application; recovering the component state data to the target component; and the refreshing a component view that is on the first page and that is related to the UI binding data comprises: refreshing, on the first page, a component view related to the UI binding data and the target component. 3. The application interface migration method according to claim 1 , wherein the checking the compatibility of the UI binding data based on the declaration field corresponding to scenario information of the electronic device comprises: obtaining the declaration field corresponding to the scenario information of the electronic device; and when the UI binding data is valid data declared in the declaration field, determining that the compatibility of the UI binding data is successfully checked. 4. The application interface migration method according to claim 1 , wherein after the loading the first page, the application interface migration method further comprises: checking integrity of the UI binding data; if the integrity of the UI binding data is successfully checked, performing the checking compatibility of the UI binding data based on a declaration field corresponding to scenario information of the electronic device; and the storing the UI binding data in a shared data segment of the target application if the compatibility of the UI binding data is successfully checked comprises: if the compatibility of the UI binding data is successfully checked, determining a UI component bound to the shared data segment of the target application; obtaining a first data type required by the UI component; determining whether the first data type is consistent with a second data type of the UI binding data; and storing the UI binding data in the shared data segment of the target application if the first data type is consistent with the second data type of the UI binding data. 5. The application interface migration method according to claim 1 , wherein the loading the first page based on the recovery routing stack and the current page routing stack of the electronic device comprises: obtaining first routing data at a top of the recovery routing stack, and moving the first routing data to the top of the current page routing stack of the electronic device; and loading the first page based on the first routing data of the current page routing stack. 6. The application interface migration method according to claim 1 , wherein the application interface migration method further comprises: receiving a back instruction for the first page; in response to the back instruction, determining whether the recovery routing stack is empty; if the recovery routing stack is not empty, obtaining second routing data at the top of the recovery routing stack, and moving the second routing data to the top of the current page routing stack of the electronic device; and loading a second page based on the second routing data of the current page routing stack. 7. The application interface migration method according to claim 6 , wherein the application interface migration method further comprises: if the recovery routing stack is empty, obtaining third routing data at the top of the current page routing stack; and loading a third page based on the third routing data of the current page routing stack. 8. An electronic device, comprising a processor and a memory, wherein the memory is configured to store instructions, and the processor is configured to invoke the instructions in the memory, so that the electronic device performs: receiving a recovery instruction by using a second distributed service, wherein the recovery instruction is used to indicate to recover a user interface (UI) state of a target application on the electronic device, the recovery instruction comprises page routing data and UI binding data, and the UI binding data is bound to a component of the target application; in response to the recovery instruction, generating a recovery routing stack based on the page routing data, and loading a first page based on the recovery routing stack and a current page routing stack of the electronic device; checking compatibility of the UI binding data based on a declaration field corresponding to scenario information of the electronic device; storing the UI binding data in a shared data segment of the target application if the compatibility of the UI binding data is successfully checked; and refreshing a component view that is on the first page and that is related to the UI binding data. 9. The electronic device according to claim 8 , wherein the recovery instruction further comprises component state data, and after the storing the UI binding data in a shared data segment of the target application, the processor is further configured to invoke the instructions stored in the memory, to enable the electronic device to perform: determining a target component corresponding to the component state data in the target application; recovering the component state data to the target component; and the refreshing a component view that is on the first page and that is related to the UI binding data comprises: refreshing, on the first page, a component view related to the UI binding data and the target component. 10. The electronic device according to claim 8 , wherein the checking the compatibility of the UI binding data based on the declaration field corresponding to scenario information of the electronic device comprises: obtaining the declaration field corresponding to the scenario information of the electronic device; and when the UI binding data is valid data declared in the declaration field, determining that the compatibility of the UI binding data is successfully checked. 11. The electronic device according to claim 8 , wherein after the loading the first page, the processor is further configured to invoke the instructions stored in the memory, to enable the electronic device to perform: checking integrity of the UI binding data; if the integrity of the UI binding data is successfully checked, performing the checking compatibility of the UI binding data based on a declaration field corresponding to
Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title
Energy efficient computing, e.g. low power processors, power management or thermal management · CPC title
Peer-to-peer [P2P] networks · CPC title
resumption being on a different machine, e.g. task migration, virtual machine migration (G06F9/5088 takes precedence) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.