CN117675881A

CN117675881A - Application data storage method and electronic equipment

Info

Publication number: CN117675881A
Application number: CN202211008280.1A
Authority: CN
Inventors: 龚阿世; 韩露
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-08-22
Filing date: 2022-08-22
Publication date: 2024-03-08
Also published as: WO2024041456A1

Abstract

The application provides an application data storage method and electronic equipment. The first electronic device may provide a set of generic interfaces including a save interface. The first electronic device may invoke the save interface to cache data on the data object in the application one in a local non-application process memory or to save data in a non-application process memory on the second electronic device that established the communication connection. In this way, on one hand, the data is stored in the non-application process memory, and the application data stored in the non-application process memory cannot be deleted along with the closing of the application. On the other hand, the running state of the application on the equipment is not required to be concerned, and the running data of the application of the local equipment before closing can be saved and recovered on the application of the local equipment or the application of the opposite-end equipment.

Description

Application data storage method and electronic equipment

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to an application data storage method and an electronic device.

Background

Application data may be understood as memory data (also referred to as business data) generated by an application program when running. The application program is opened and correspondingly generates application data. If the application program is closed, the application data generated in the application program is also deleted.

However, in some scenarios, the user may wish to resume the application data the next time the application is opened on the local device, or the user may wish to resume the application data on the local device when the application is opened on other devices within the network. How to recover on the local device or other device the application data generated prior to the application shutdown on the local device is to be further investigated.

Disclosure of Invention

The application data storage method and the electronic device are characterized in that on one hand, data are stored in a non-application process memory, and application data stored in the non-application process memory cannot be deleted along with closing of an application. On the other hand, the running state of the application on the equipment is not required to be concerned, and the running data of the application of the local equipment before closing can be saved and recovered on the application of the local equipment or the application of the opposite-end equipment.

In a first aspect, the application data storage system includes a first electronic device and a second electronic device that are in communication connection, where the first electronic device is configured to open a first application on the first electronic device, and obtain data on a first data object in the first application and a first session ID bound to the first data object; the first electronic device is further configured to send the data on the first data object and the first session ID to the second electronic device; and the second electronic equipment is used for receiving the data and the first session ID on the first data object and storing the data and the first session ID on the first data object in a non-application process memory. Thus, the data on the first data object sent by the first electronic device can be received and saved regardless of whether the second application on the second electronic device is open or closed.

By the method provided by the first aspect, the data is stored in the non-application process memory, and the application data stored in the non-application process memory cannot be deleted along with closing of the application. On the other hand, the running state of the application on the equipment is not required to be concerned, and the running data of the application of the local equipment before closing can be saved and recovered on the application of the local equipment or the application of the opposite-end equipment.

With reference to the first aspect, in one possible implementation manner, the second electronic device is specifically configured to: receiving data and a first session ID on a first data object when a second application on a second electronic device is in a closed state; wherein the second application and the first application are the same or corresponding applications. In this way, the second application on the second electronic device may also receive and store the data on the first data object sent by the first electronic device in the closed state.

The same application refers to that the first electronic device and the second electronic device are devices with the same type, for example, are mobile phones, and then the installation package of the first application on the first electronic device is the same as the installation package of the second application on the second electronic device.

The corresponding application means that the first electronic device and the second electronic device are devices with different types, for example, the first electronic device is a mobile phone, and the second electronic device is a tablet. The installation package of the first application on the first electronic device and the installation package of the second application on the second electronic device are also different.

Alternatively, when the first electronic device and the second electronic device are devices of different types, the installation package of the first application installed on the first electronic device and the installation package of the second application on the second electronic device may also be the same.

With reference to the first aspect, in one possible implementation manner, the second electronic device is further configured to open a second application, and obtain a second session ID bound to a second data object in the second application; the second electronic device is further configured to generate data on the second data object based on the data on the first data object if the second session ID is the same as the first session ID.

Thus, the data objects in the same application on different devices can be bound with the same session ID, and the automatic synchronization of the data in the same application on different devices can be realized.

With reference to the first aspect, in one possible implementation manner, the second electronic device is specifically configured to: creating a process of the second application; acquiring data on the first data object from a non-application process memory through a process of the second application; storing the data on the first data object in an application process memory on the second electronic device through a process of the second application; and generating data on the second data object based on the data on the first data object in the application process memory.

Optionally, the application process memory is a block of storage area shared by all processes on the second electronic device. The non-application process memory is a block of memory area shared by all non-processes on the second electronic device.

Alternatively, the application process memory occupied by different applications may be different. The non-application process memory occupied by different applications may also be different.

Thus, after the second application is started on the second electronic device, the data on the second data object may be based on the data generated on the first data object saved prior to the start.

With reference to the first aspect, in one possible implementation manner, the first electronic device is further configured to store the data on the first data object and the first session ID in a non-application process memory on the first electronic device.

Therefore, the first electronic device can store the data on the first data object in the local non-application process memory, so that when the first application is opened after being closed, the application data generated by the first application before being closed can be recovered again.

With reference to the first aspect, in one possible implementation manner, the first electronic device is further configured to close the first application; the first electronic device is further configured to, after closing the first application, restart the first application, and obtain a third session ID bound to the third data object; the first electronic device is further configured to generate data on the third data object based on the data on the first data object if the third session ID and the first session ID are the same. Therefore, when the first application is opened after being closed, the application data generated by the first application before being closed can be recovered again.

With reference to the first aspect, in one possible implementation manner, the non-application process memory includes any one of the following: a first memory partition in the ROM read only memory and the RAM random access memory; the application process memory comprises a second storage partition in the RAM; wherein the second memory partition in RAM is different from the first memory partition in RAM.

With reference to the first aspect, in one possible implementation manner, the first electronic device is further configured to send a first instruction to the second electronic device; the second electronic device is further configured to delete the data on the first data object and the first session ID from the non-application process memory on the second electronic device in response to the first instruction. Thus, application data stored on other electronic devices can be deleted.

With reference to the first aspect, in one possible implementation manner, the first electronic device is further configured to delete the data on the first data object and the first session ID from the non-application process memory on the first electronic device. Thus, the application data stored on the local device can be deleted.

In a second aspect, the application data storage method includes that a first electronic device and a second electronic device establish communication connection; the method comprises the steps that a first electronic device starts a first application on the first electronic device, and obtains data on a first data object in the first application and a first session ID bound with the first data object; the first electronic device sends the data on the first data object and the first session ID to the second electronic device through communication connection; the data and the first session ID on the first data object are used for the second electronic device to store the data and the first session ID on the first data object in the non-application process memory.

With reference to the second aspect, in one possible implementation manner, the sending, by the first electronic device, the data on the first data object and the first session ID to the second electronic device through a communication connection specifically includes: when a second application on a second electronic device is in a closed state, the first electronic device sends data on a first data object and a first session ID to the second electronic device through communication connection; wherein the second application and the first application are the same or corresponding applications.

With reference to the second aspect, in one possible implementation manner, the method further includes the first electronic device storing the data on the first data object and the first session ID in a non-application process memory on the first electronic device.

With reference to the second aspect, in one possible implementation manner, after the first electronic device stores the data on the first data object and the first session ID in the non-application process memory on the first electronic device, the method further includes the first electronic device closing the first application; after the first electronic equipment closes the first application, the first electronic equipment opens the first application again, and acquires a third session ID bound with a third data object; in the case that the third session ID and the first session ID are the same, the first electronic device generates data on the third data object based on the data on the first data object.

With reference to the second aspect, in one possible implementation manner, the first electronic device generates data on a third data object based on the data on the first data object, and specifically includes: the method comprises the steps that a first electronic device creates a process of a first application; the first electronic device acquires data on a first data object from a non-application process memory through a process of a first application; the first electronic device stores the data on the first data object in an application process memory on the first electronic device through a process of the first application; the first electronic device generates data on a third data object based on the data on the first data object in the application process memory through the process of the first application.

With reference to the second aspect, in one possible implementation manner, the non-application process memory includes any one of the following: a first memory partition in the ROM read only memory and the RAM random access memory; the application process memory comprises a second storage partition in the RAM; wherein the second memory partition in RAM is different from the first memory partition in RAM.

With reference to the second aspect, in one possible implementation manner, after the first electronic device sends the data on the first data object and the first session ID to the second electronic device through the communication connection, the method further includes: the first electronic device sends a first instruction to the second electronic device; the first instruction is used for instructing the second electronic device to delete the data on the first data object and the first session ID from the non-application process memory on the second electronic device.

With reference to the second aspect, in one possible implementation manner, after the first electronic device stores the data on the first data object and the first session ID in a non-application process memory on the first electronic device, the method further includes: the first electronic device deletes the data on the first data object and the first session ID from the non-application process memory on the first electronic device.

In a third aspect, the present application provides a method for storing application data, where the method includes: the second electronic device establishes communication connection with the first electronic device; the second electronic device receives data on a first data object sent by the first electronic device and a first session ID bound with the first data object, wherein the first data object is a data object in a first application on the first electronic device; and the second electronic equipment stores the data on the first data object and the first session ID in a non-application process memory.

With reference to the third aspect, in one possible implementation manner, the second electronic device receives data on the first data object sent by the first electronic device and a first session ID bound by the first data object, and specifically includes: when a second application on the second electronic equipment is in a closed state, the second electronic equipment receives data and a first session ID on a first data object sent by the first electronic equipment; wherein the second application and the first application are the same or corresponding applications.

With reference to the third aspect, in one possible implementation manner, after the second electronic device saves the data on the first data object and the first session ID in the non-application process memory, the method further includes: the second electronic device creates a process of a second application; the second electronic equipment acquires data on the first data object from a non-application process memory through a process of a second application; the second electronic device stores the data on the first data object in an application process memory on the second electronic device through a process of the second application; the second electronic device generates data on the second data object based on the data on the first data object in the application process memory through the process of the second application.

With reference to the third aspect, in one possible implementation manner, the non-application process memory includes any one of the following: a first memory partition in the ROM read only memory and the RAM random access memory; the application process memory comprises a second storage partition in the RAM; wherein the second memory partition in RAM is different from the first memory partition in RAM.

With reference to the third aspect, in one possible implementation manner, after the second electronic device saves the data on the first data object and the first session ID in the non-application process memory, the method further includes: the second electronic equipment receives a first instruction sent by the first electronic equipment; in response to the first instruction, the second electronic device deletes the data on the first data object and the first session ID from the non-application process memory on the second electronic device.

In a fourth aspect, the present application provides an application data saving method, where the method includes: the method comprises the steps that a first electronic device starts a first application on the first electronic device, and obtains data on a first data object in the first application and a first session ID bound with the first data object; the first electronic device stores the data on the first data object and the first session ID in a non-application process memory.

With reference to the fourth aspect, in one possible implementation manner, after the first electronic device saves the data on the first data object and the first session ID in the non-application process memory, the method further includes: the first electronic device closes the first application; after the first application is closed, the first electronic equipment opens the first application again, and acquires a third session ID bound with a third data object; in the case that the third session ID and the first session ID are the same, the first electronic device generates data on the third data object based on the data on the first data object.

With reference to the fourth aspect, in one possible implementation manner, the first electronic device generates data on the third data object based on the data on the first data object, specifically includes: the first electronic equipment builds a process of a first application; the first electronic device acquires data on a first data object from a non-application process memory through a process of a first application; the first electronic device stores the data on the first data object in an application process memory through a process of a first application; the first electronic device generates data on a third data object based on the data on the first data object in the applied process memory.

With reference to the fourth aspect, in one possible implementation manner, the non-application process memory includes any one of the following: a first memory partition in the ROM read only memory and the RAM random access memory; the application process memory comprises a second storage partition in the RAM; wherein the second memory partition in RAM is different from the first memory partition in RAM.

With reference to the fourth aspect, in one possible implementation manner, after the first electronic device saves the data on the first data object and the first session ID in the non-application process memory, the method further includes: the first electronic device deletes the data on the first data object and the first session ID from the non-application process memory.

In a fifth aspect, the present application provides an electronic device, which is a first electronic device, and is characterized in that the first electronic device includes: one or more processors, one or more memories; the one or more memories are coupled to the one or more processors, the one or more memories for storing computer program code comprising computer instructions that the one or more processors invoke to cause the first electronic device to perform an application data preservation method provided in any of the possible implementations of the above.

In a sixth aspect, the present application provides an electronic device, which is a second electronic device, the second electronic device including: one or more processors, one or more memories; the one or more memories are coupled to the one or more processors, the one or more memories for storing computer program code comprising computer instructions that the one or more processors invoke to cause the second electronic device to perform an application data preservation method provided in any of the possible implementations of the above.

In a seventh aspect, the present application provides a computer readable storage medium storing computer instructions that, when executed on a first electronic device, cause the first electronic device to perform an application data saving method provided in any one of the possible implementations of the above aspect.

In an eighth aspect, the present application provides a computer readable storage medium storing computer instructions that, when executed on a second electronic device, cause the second electronic device to perform an application data saving method provided in any one of the possible implementations of the above aspect.

In a ninth aspect, the present application provides a computer program product for, when run on a first electronic device, causing the first electronic device to perform a method of application data preservation as provided in any one of the possible implementations of the above aspect.

In a tenth aspect, the present application provides a computer program product, characterized in that the computer program product, when run on a second electronic device, causes the second electronic device to perform an application data saving method provided in any one of the possible implementations of the above aspect.

For the beneficial effects of the second aspect to the tenth aspect, reference may be made to the description of the beneficial effects in the first aspect, which is not repeated herein.

Drawings

FIG. 1 is a schematic diagram of a system 10 according to an embodiment of the present disclosure;

fig. 2 is a schematic structural diagram of an electronic device 100 according to an embodiment of the present application;

fig. 3 is a software block diagram of an electronic device 100 according to an embodiment of the present application;

fig. 4 is a functional schematic diagram of a data buffering module on an electronic device 100 according to an embodiment of the present application;

fig. 5A is a functional schematic diagram of a data buffering module on an electronic device 200 according to an embodiment of the present application;

FIG. 5B is a schematic diagram of binding the same session ID to a data object in the same application according to an embodiment of the present application;

FIG. 6 is a schematic diagram of how to recover, on an electronic device 100, operation data generated by an application on the electronic device 100 according to an embodiment of the present application;

FIG. 7 is a schematic diagram of how to recover, on an electronic device 200, operation data generated by an application on the electronic device 100 according to an embodiment of the present application;

fig. 8 is a schematic diagram of an electronic device 200 according to an embodiment of the present application recovering data in an application one of the electronic device 100 locally;

fig. 9 is a flowchart of an application data recovery method according to an embodiment of the present application;

fig. 10 is a flowchart of another method for storing application data according to an embodiment of the present application;

fig. 11 is a flowchart of another method for storing application data according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and thoroughly described below with reference to the accompanying drawings. Wherein, in the description of the embodiments of the present application, "/" means or is meant unless otherwise indicated, for example, a/B may represent a or B; the text "and/or" is merely an association relation describing the associated object, and indicates that three relations may exist, for example, a and/or B may indicate: the three cases where a exists alone, a and B exist together, and B exists alone, and in addition, in the description of the embodiments of the present application, "plural" means two or more than two.

The terms "first," "second," and the like, are used below for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature, and in the description of embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" is two or more.

The term "User Interface (UI)" in the following embodiments of the present application is a media interface for interaction and information exchange between an application program or an operating system and a user, which enables conversion between an internal form of information and an acceptable form of the user. A commonly used presentation form of the user interface is a graphical user interface (graphic user interface, GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It may be a visual interface element of text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc., displayed in a display of the electronic device.

The embodiment of the application provides an application data storage method. The method comprises the following steps: the electronic device 100 may provide a set of generic interfaces including a save interface. The electronic device 100 may invoke a save interface to cache data on a data object in an application in a local non-application process memory or in a non-application process memory on other electronic devices (e.g., the electronic device 200) that establish a communication connection.

The non-application process memory comprises any one of the following: a ROM read-only memory, a first memory partition in the RAM random access memory.

The application process memory comprises a second storage partition in the RAM; the second memory partition in RAM is different from the first memory partition in RAM.

The electronic device 100 may cache data on the data object in the application in the first memory partition in ROM or RAM according to the scene requirements. For example, when the running memory capacity is lower than the threshold value, the electronic device 100 may store the data on the data object in the application one in the ROM, so that the data on the data object in the application one is prevented from being stored in the RAM to occupy the running memory capacity, which is beneficial to improving the running speed of the electronic device 100. When the running memory capacity is above the threshold, the electronic device 100 may store data on the data object in the application in a first memory partition in ROM or RAM. Optionally, when the running memory capacity is below the threshold, the electronic device 100 may also save the data on the data object in the application one in the first memory partition in the RAM. The data stored in the first memory partition in ROM and RAM will not be deleted as the application process disappears. In this way, the electronic device 100 stores the data on the data object in the application in the first storage partition in the ROM or the RAM, so that the situation that the running memory is too low to cause the data stored in the application process memory to be deleted after the process disappears can be prevented.

Thus, in one aspect, the present application provides a set of general programming paradigms that enable data to be cached locally or on other electronic devices that establish a connection in a very simple manner, reducing the workload of the developer. On the other hand, the data in the application is stored in the non-application process memory, so that the situation that the local device or other electronic devices which establish connection cannot recover to obtain the application data generated by the application on the electronic device 100 after the application on the electronic device 100 is closed can be avoided.

Optionally, the universal interface provided in the present application further includes a delete interface, and the electronic device 100 may also call the delete interface to delete data on the data object in the application in a very simple manner from the local or delete data cached on other electronic devices that establish the connection.

The description of the programming paradigm provided in the embodiments of the present application will be described in detail in the following embodiments, which are not described herein in detail.

The method can be applied to other equipment for establishing networking connection to recover the application data on the local equipment. Specifically, after the application on the electronic device 100 is started, the application data is generated during the running process of the application, and the electronic device 100 may cache the application data generated by the application in a local non-application process memory based on the programming paradigm provided in the embodiment of the present application. If the application is closed, and the application is opened next time, the electronic device 100 may recover the application data generated by the application before closing based on the data stored in the non-application process memory. Because the data stored in the non-application process memory will not be deleted after the application is closed, the data stored in the application process memory will be deleted.

For example, when a user records an event using a memo application on the electronic device 100, the electronic device 100 periodically buffers the application data generated by the memo in the local non-application process memory. When the user opens the memo on the electronic device 100 again due to the suddenly closed memo application caused by the too low running memory capacity, the electronic device 100 may recover the event recorded by the memo before closing based on the data in the non-application process memory.

The method can also be applied to the recovery of application data on the local equipment on the opposite equipment. Specifically, the electronic device 100 establishes a networking connection with the electronic device 200. After the application on the electronic device 100 is started, the application generates application data in the running process, and sends the application data to the electronic device 200 in real time. The electronic device 200 may cache application data sent by the electronic device 100 in a local non-application process memory. After the application one on the electronic device 200 is started, the application data of the application one on the electronic device 100 can be obtained based on the data recovery in the non-application process memory, so that the application data is migrated from the electronic device 100 to the electronic device 200 without paying attention to the running states of the electronic device 100 and the application one on the electronic device 200.

The application may be applied to an application migration scenario, and specifically, the electronic device 100 establishes a networking connection with the electronic device 200. The electronic device 100 receives the user operation to migrate the operation data of the first application to the second application, and after the first application on the electronic device 100 is closed, the operation data generated by the first application on the electronic device 100 can still be recovered on the electronic device 200. For example, application one may be a memo application, electronic device 100 may be a cell phone, and electronic device 200 may be a tablet. The user opens the memo application on the mobile phone, edits task items on the memo, and the edited records on the memo on the mobile phone can also flow to the tablet in real time. At this time, the user wants to switch the memo to the larger-screen tablet to continue editing task items, and the user can open the memo application on the tablet, and no matter the memo application on the mobile phone is in an open state or a closed state, the memo application on the tablet also has an editing record in the memo application on the mobile phone, so that the user can continue editing task items on the tablet.

Next, a system architecture provided in an embodiment of the present application is described.

Referring to fig. 1, fig. 1 is a schematic diagram illustrating an architecture of a system 10 according to an embodiment of the present application.

A plurality of electronic devices may be included in the system 10. The device types of the plurality of electronic devices may be various types, and the specific types of the plurality of electronic devices are not particularly limited in the embodiments of the present application. For example, the plurality of electronic devices include cell phones, which may also include tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, smart screens, wearable devices, augmented reality (augmented reality, AR) devices, virtual Reality (VR) devices, artificial intelligence (artificial intelligence, AI) devices, car computers, smart headphones, gaming machines, and may also include internet of things (internet of things, IOT) devices or smart home devices such as smart water heaters, smart lights, smart air conditioners, and the like. Without limitation, the plurality of devices in system 10 may also include non-portable terminal devices such as laptop computers (labtop) having a touch sensitive surface or touch panel, desktop computers having a touch sensitive surface or touch panel, and the like.

The plurality of electronic devices may be configured with different software Operating Systems (OSs), including but not limited toEtc. Wherein (1)>Is a hong Mongolian system.

The plurality of electronic devices may be all configuredThe same software operating system, e.g. may all be configured

The plurality of electronic devices may establish a networking connection in any of the following ways.

Mode one: the plurality of electronic devices may be connected to the same network, for example, the plurality of electronic devices may be connected to the same local area network to establish a networking connection.

Mode two: the plurality of electronic devices can also log in the same system account number to establish networking connection. For example, the system account number for the plurality of electronic devices may all be "HW1234".

Mode three: the system account numbers logged on the plurality of electronic devices may all belong to the same account group. For example, the system account registered on the plurality of electronic devices includes "HW001", "HW002", "HW003". The system accounts "HW001", "HW002", "HW003" belong to the account group "Huazhi".

Mode four: the plurality of electronic devices may establish networking connections through near field communication (Near Field Communication, NFC), bluetooth (BT), wireless local area network (wireless local area networks, WLAN), such as wireless fidelity point-to-point (wireless fidelity point to point, wi-Fi P2P), infrared (IR), and the like.

Mode five: a plurality of electronic devices can establish a temporary account group by scanning the same two-dimensional code, and networking connection is established to realize communication.

The method is not limited to the above five methods, and the electronic device 100 may also establish a networking connection through other methods, which is not limited in the embodiment of the present application.

In addition, multiple electronic devices may be connected and communicate in any of several ways described above, which is not limited by the embodiments of the present application.

In other embodiments, the system 10 may also include only two electronic devices, such as the electronic device 100 and the electronic device 200, with the electronic device 100 and the electronic device 200 establishing a networking connection. The following embodiments of the present application illustrate an example in which the system 10 includes two electronic devices, the electronic device 100 is a mobile phone, and the electronic device 200 is a tablet.

One or more applications are installed on the electronic device 100, and one or more applications are also installed on the electronic device 200. After the electronic device 100 and the electronic device 200 establish a networking connection, the electronic device 100 generates application data after a while when running the application. The electronic device 100 may transmit application data generated by the application to the electronic device 200 in real time. The electronic device 200 caches application data generated by the application of the electronic device 100 in the local non-application process memory. Then, the electronic device 200 may start the application one, and recover the application data generated by the application one on the electronic device 100 based on the application data in the non-application process memory, so as to implement application migration.

The following embodiments of the present application take the electronic device 100 as an example of a mobile phone, and the electronic device 200 may also have the same or similar components.

Fig. 2 shows a schematic structural diagram of the electronic device 100.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge 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, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It should be understood that the illustrated structure of the embodiment of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present invention is only illustrative, and is not meant to limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also use different interfacing manners, or a combination of multiple interfacing manners in the foregoing embodiments.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. 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 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied to the electronic device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

In some embodiments, antenna 1 and mobile communication module 150 of electronic device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that electronic device 100 may communicate with a network and other devices through wireless communication techniques. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organiclight emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The electronic device 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent awareness of the electronic device 100 may be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The internal memory 121 may include one or more random access memories (random access memory, RAM) and one or more non-volatile memories (NVM).

The random access memory may include a static random-access memory (SRAM), a dynamic random-access memory (dynamic random access memory, DRAM), a synchronous dynamic random-access memory (synchronous dynamic random access memory, SDRAM), a double data rate synchronous dynamic random-access memory (double data rate synchronous dynamic random access memory, DDR SDRAM, such as fifth generation DDR SDRAM is commonly referred to as DDR5 SDRAM), etc.;

the nonvolatile memory may include a disk storage device, a flash memory (flash memory).

The FLASH memory may include NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. divided according to an operation principle, may include single-level memory cells (SLC), multi-level memory cells (MLC), triple-level memory cells (TLC), quad-level memory cells (QLC), etc. divided according to a storage specification, may include universal FLASH memory (english: universal FLASH storage, UFS), embedded multimedia memory cards (embedded multimedia Card, eMMC), etc. divided according to a storage specification.

The random access memory may be read directly from and written to by the processor 110, may be used to store executable programs (e.g., machine instructions) for an operating system or other on-the-fly programs, may also be used to store data for users and applications, and the like.

The nonvolatile memory may store executable programs, store data of users and applications, and the like, and may be loaded into the random access memory in advance for the processor 110 to directly read and write.

The external memory interface 120 may be used to connect external non-volatile memory to enable expansion of the memory capabilities of the electronic device 100. The external nonvolatile memory communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and video are stored in an external nonvolatile memory.

The electronic device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 100 may listen to music, or to hands-free conversations, through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When electronic device 100 is answering a telephone call or voice message, voice may be received by placing receiver 170B in close proximity to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may also be provided with three, four, or more microphones 170C to enable collection of sound signals, noise reduction, identification of sound sources, directional recording functions, etc.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The gyro sensor 180B may be used to determine a motion gesture of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., x, y, and z axes) may be determined by gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the electronic device 100, calculates the distance to be compensated by the lens module according to the angle, and makes the lens counteract the shake of the electronic device 100 through the reverse motion, so as to realize anti-shake. The gyro sensor 180B may also be used for navigating, somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude from barometric pressure values measured by barometric pressure sensor 180C, aiding in positioning and navigation.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip machine, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 100 is stationary. The electronic equipment gesture recognition method can also be used for recognizing the gesture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, the electronic device 100 may range using the distance sensor 180F to achieve quick focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it may be determined that there is an object in the vicinity of the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there is no object in the vicinity of the electronic device 100. The electronic device 100 can detect that the user holds the electronic device 100 close to the ear by using the proximity light sensor 180G, so as to automatically extinguish the screen for the purpose of saving power. The proximity light sensor 180G may also be used in holster mode, pocket mode to automatically unlock and lock the screen.

The ambient light sensor 180L is used to sense ambient light level. The electronic device 100 may adaptively adjust the brightness of the display 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. Ambient light sensor 180L may also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent false touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 may utilize the collected fingerprint feature to unlock the fingerprint, access the application lock, photograph the fingerprint, answer the incoming call, etc.

The temperature sensor 180J is for detecting temperature. In some embodiments, the electronic device 100 performs a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs a reduction in the performance of a processor located in the vicinity of temperature sensor 180J in order to reduce power consumption to implement thermal protection. In other embodiments, when the temperature is below another threshold, the electronic device 100 heats the battery 142 to avoid the low temperature causing the electronic device 100 to be abnormally shut down. In other embodiments, when the temperature is below a further threshold, the electronic device 100 performs boosting of the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperatures.

The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a different location than the display 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, bone conduction sensor 180M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 180M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 170 may analyze the voice signal based on the vibration signal of the sound portion vibration bone block obtained by the bone conduction sensor 180M, so as to implement a voice function. The application processor may analyze the heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 180M, so as to implement a heart rate detection function.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card.

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. In the embodiment of the invention, taking an Android system with a layered architecture as an example, a software structure of the electronic device 100 is illustrated.

Fig. 3 is a software configuration block diagram of the electronic device 100 according to the embodiment of the present invention.

The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages.

As shown in fig. 3, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.

The application framework layer provides application programming interfaces (application programming interface, APIs) for application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in fig. 3, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, a data caching module, and the like.

The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.

The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

The telephony manager is used to provide the communication functions of the electronic device 100. Such as the management of call status (including on, hung-up, etc.).

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

Upon opening of an application on the electronic device 100, the electronic device 100 creates a data object of the application one, which may be referred to as a first data object. The electronic device 100 obtains the data on the first data object and obtains a session ID (session identification) to which the first data object is bound, which may be referred to as a first session ID. The same session identifier may be associated between the same data object on the electronic device 100 and the same data object on the electronic device 200, and after the data on the data object with the first session ID associated in the electronic device 100 changes, the data on the data object with the first session ID associated on the electronic device 200 may change based on the data change on the data object with the first session ID associated in the electronic device 100, so that the data between the same data objects between the electronic device 100 and the electronic device 200 are the same, and automatic synchronization of the data on the same data object between the electronic devices is achieved. The data caching module is further used for calling a caching interface based on a very simple programming paradigm, and caching the data on the first data object in a local non-application process memory in real time and/or caching the data on the opposite terminal equipment for establishing networking connection in the non-application process memory.

Non-application process memory may include, but is not limited to: a ROM read only memory, a first memory partition in RAM random access memory, etc. Therefore, the condition that the data on the first data object is deleted due to the fact that the data is stored in the application process memory after the application is closed can be avoided.

In some embodiments, after the data caching module caches the application data on the local area in real time based on the extremely simple programming paradigm, in a case that the application on the electronic device 100 is turned on again after being turned off, when determining that the session ID bound to the data object in the application one is the first session ID, the electronic device 100 may restore the data on the data object in the application one based on the data on the cached first data object, that is, restore the application data generated before the application is turned off. Thus, the situation that the application data is lost due to the fact that the application is suddenly closed under the condition that the application data is not stored can be avoided.

In other embodiments, after the data caching module caches the application data on the electronic device 200 in real time based on the extremely simple programming paradigm, after the application on the electronic device 200 is started, the electronic device 200 obtains the session ID of the application one data object binding on the electronic device 200, and in the case that the session ID of the application one data object binding on the electronic device 200 is the first session ID, the electronic device 100 can recover the data on the data object of the application one on the electronic device 200 based on the data on the cached first data object, that is, recover the application data on the electronic device 100 generated before the application is closed, so as to realize migration of the application data between devices.

Android run time includes a core library and virtual machines. Android run time is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

Fig. 4 schematically illustrates a functional diagram of a data caching module on the electronic device 100.

As shown in fig. 4, the data caching module on the electronic device 100 includes a distributed data object creation module 401 and an application data caching module 402.

Wherein, the distributed data object creating module 401 is configured to create a data object of an application one, and obtain data on the data object; the data object may be referred to as a first data object.

The distributed data object creation module 401 is further configured to acquire a session ID bound to the first data object to establish a binding relationship; the session ID may be referred to as a first session ID.

The distributed data object creation module 401 is further configured to send the data on the first data object and the first session ID to the application data cache module 402.

In some embodiments, the application data caching module 402 is configured to cache the data on the first data object and the first session ID in a local non-application process memory after receiving the data on the first data object and the first session ID. In this way, the application data caching module 402 may cache the data on the first data object and the first session ID outside the locally corresponding application process memory. After an application is closed, the data of the first data object may not be deleted with the closing of the application process.

Non-application process memory may include, but is not limited to: a ROM read only memory, a first memory partition in RAM random access memory, etc.

In other embodiments, the application data caching module 402 may also send the data on the first data object and the first session ID to the peer device that establishes the networking connection.

Optionally, after the application data buffer module 402 sends the data on the first data object and the first session ID to the peer device, the peer device stores the data on the first data object and the first session ID in a non-application process memory of the peer device.

Fig. 5A schematically illustrates a functional diagram of a data caching module on an electronic device 200.

As shown in fig. 5A, the data caching modules on the electronic device 200 include an application data caching module 501 and a distributed data object creation module 502.

The application data caching module 501 is configured to receive data on a first data object and a first session ID sent by the electronic device 100. The first session ID is a session ID bound to the first data object on the electronic device 100.

The application data caching module 501 is further configured to cache the data on the first data object and the first session ID in a local non-application process memory.

Thus, even if the application on the electronic device 200 is not on, the electronic device 200 may receive the data on the first data object and the first session ID, and store the data on the first data object and the first session ID in the local non-application process memory. Because the electronic device 200 stores the data in the non-application process memory, the participation of the application one process is not needed, and even if the application one process is not created in the closed state, the data can still be stored in the non-application process memory. The method solves the problems that when data is stored in a non-application process memory on the electronic equipment 200, the application on the electronic equipment 200 is required to be started, the application process receives the data and stores the data in the application process memory on the electronic equipment 200, and the situation that the application process memory is deleted when the application is suddenly closed is solved.

The application data caching module 501 is further configured to send the data on the first data object and the first session ID to the distributed data object creation module 502.

The distributed data object creation module 502 is configured to create a second data object of an application one on the electronic device 200 after the application one on the electronic device 200 is started. And obtains the session ID of the second data object binding.

It should be noted that, the application one on the electronic device 200 and the application one on the electronic device 100 are the same application or corresponding applications.

The same application refers to that the electronic device 100 and the electronic device 200 are the same type of devices, for example, the electronic device 100 and the electronic device 200 are both mobile phones, so that the installation package of the application one on the electronic device 200 is the same as the installation package of the application one on the electronic device 100, for example, the installation package of the application one may be a memo installation package of a mobile phone version. In addition, when the types of the first electronic device and the second electronic device are different, the applications installed on the two electronic devices may also be the same application.

The corresponding application means that the electronic device 100 and the electronic device 200 are different types of devices, for example, the electronic device 100 is a mobile phone, the electronic device 200 is a tablet, and then the installation package of the application one on the electronic device 200 is different from the installation package of the application one on the electronic device 100, the installation package of the application one on the electronic device 100 is an installation package of a mobile phone version, and the installation package of the application one on the electronic device 200 is an installation package of a tablet version. For example, the installation package of application one on the electronic device 100 is a memo installation package of a mobile phone version, and the installation package of application one on the electronic device 200 is a memo installation package of a tablet version.

In the case where the session ID of the second data object binding is the first session ID, the distributed data object creation module 502 may recover the data on the second data object based on the data on the first data object. In this way, recovery of data generated by the electronic device 100 using an operation on the electronic device 200 is achieved.

In the embodiment of the application, the data objects on the same or corresponding applications on different devices in the network can be bound with the same session ID, so that the data on the same or corresponding applications on the two devices can be automatically synchronized. For example, after the data on the application one changes, the electronic device 100 sends the data on the application one to the electronic device 200, and the electronic device 200 may modify the data on the application one on the electronic device 200 based on the data on the application one change on the electronic device 100 in the case that the same session ID of the binding is applied on the electronic device 100 and the application one on the electronic device 200.

As shown in fig. 5B, in the case of one data object on application one, the electronic device 100 creates a first data object of application one, and the electronic device 200 creates a second data object of application one, where the first data object and the second data object are associated with the same session ID, which may be the session ID-1. In this way, when the data on the first data object of the first application on the electronic device 100 changes, the data on the second data object of the first application on the electronic device 200 is also automatically updated, so as to realize the data synchronization between the electronic device 100 and the first application on the electronic device 200.

Specifically, after the application one on the electronic device 200 is started, a process of the application one on the electronic device 200 is created. Then, the application one process on the electronic device 200 obtains the data and the first session ID on the first data object stored previously from the non-application process memory. The application one process on the electronic device 200 saves the data on the first data object and the first session ID in the application process memory. Finally, in the case that the session ID bound to the second data object is determined to be the first session ID by the application-one process on the electronic device 200, the application-one process on the electronic device 200 recovers the data on the second data object based on the data on the first data object in the application process memory.

Fig. 6 illustrates a schematic diagram of how the resulting operational data of an application on the electronic device 100 is retrieved on the electronic device 100.

The electronic device 100 includes an application one, a data buffer module 601 and a non-application process memory module 602.

Recovering, on the electronic device 100, the operation data generated by the application on the electronic device 100 may include the following steps. It should be understood that the following steps may be combined, not performed, deleted, etc., without limitation.

Step one: upon the application on the electronic device 100 opening, the application sends an open instruction to the data cache module 601.

Step two: the data buffer module 601 creates a first data object of the application one after receiving the start instruction.

Step three: the data cache module 601 obtains data on the first data object and obtains a session ID bound to the first data object, where the session ID may be referred to as a first session ID. The first data object binds the first session ID, so that after the application one closes, the data on the application one can be recovered based on the session ID bound by the data object on the application one.

It should be noted that, there may be one data object or multiple different data objects in the same application, which is not limited in this embodiment of the present application.

Step four: after the data caching module 601 obtains the data on the first data object and obtains the first session ID bound to the first data object, the data caching module 601 sends the data on the first data object and the first session ID bound to the first data object to the non-application process memory module 602, so that the data on the first data object and the first session ID bound to the first data object are cached in the non-application process memory.

In some examples, after the application one on the electronic device 100 is started, the data on the first data object is cached in the application process memory in real time during the running process of the application one, so that the process of the application one can obtain the data on the first data object from the application process memory. Meanwhile, the electronic device 100 may buffer the data on the first data object in the non-application process memory in real time, so that after the application one is closed, the data on the first data object stored in the application process memory is deleted along with the disappearance of the application one, and the data on the first data object stored in the non-application process memory is not deleted along with the disappearance of the application one.

In this way, the data on the first data object and the first session ID bound to the first data object are cached in the non-application process memory, and the data on the first data object is not cleared after the application is closed.

Alternatively, the data on the first data object may be stored in the non-application process memory in the form of key-value pairs.

For example, the data on the first data object may be stored in a non-application process memory (e.g., database) in the form of a key-value pair.

The data on the data object may be represented by fields and attribute values. In some embodiments, a field may also be referred to as an attribute name.

TABLE 1

Table 1 exemplarily shows a storage form of data on a data object in a database. Illustratively, the data on the first data object includes field 1 and field 2, field 1 being stored in a database named kv store1, field 1 having a stored attribute value of key1 within kv store1, field 2 being stored in a distributed content database named kv store1, field 2 having a stored attribute value of key2 within kv store 1. The data on the nth data object includes field 3 and field 4, field 3 being stored in a database named kv store2, field 3 having a stored attribute value of key3 within kv store2, field 4 being stored in a database named kv store2, field 4 having a stored attribute value of key4 within kv store 2. The data on the n+1th data object includes a field 5 and a field 6, the field 5 being stored in a database named kv store N, the stored attribute value of the field 5 in the kv store N being key5, the field 6 being stored in a database named kv store N, the stored attribute value of the field 6 in the kv store N being key6.

It should be noted that the same application may create a plurality of different data objects, with the data on the different data objects being different. The data on different data objects may be stored in the same non-application process memory, or may be stored in different non-application process memories, which is not limited in this embodiment of the present application. For example, data on different data objects may be stored in the same database or in different databases. The embodiments of the present application are not limited in this regard.

Step five: the application once turns on again after turning off, and the application sends a turn-off and turn-on again instruction to the data cache module 601.

As soon as an application on the electronic device 100 is closed due to low running memory or other reasons, currently, running data generated during the running process of the application is stored in the application process memory. After the application one is closed, the process of the application one exits, and then the running data stored in the memory of the application process is cleared. According to the scheme, the operation data generated in the operation process are cached in the non-application process memory, and the operation data cannot be cleared after the application is suddenly closed.

Alternatively, if the electronic device 100 monitors that the user actively triggers to cause the application to be closed, the data buffering module 601 may not store the application operation data (e.g. the data on the first data object) generated during the operation in the non-application process memory, that is, only if the electronic device 100 monitors that the application is automatically closed, the data buffering module 601 stores the application operation data (e.g. the data on the first data object) generated during the operation in the non-application process memory. In this way, the excessive data amount stored in the non-application process memory can be avoided.

Alternatively, the electronic device 100 may monitor that the application is closed, whether the application is automatically closed or the user is actively triggered to cause the application to be closed, and the electronic device 100 stores the application operation data (e.g., the data on the first data object) generated during the operation in the non-application process memory.

Step six: after application one is turned off and turned on, the data cache module 601 creates a third data object for application one.

Step seven: the data cache module 601 obtains the session ID bound to the third data object, and when the session ID bound to the third data object is the first session ID, the data cache module 601 sends a first request to the non-application process memory module 602.

The first request is for retrieving data on a first data object stored in the non-application process memory module 602.

Step eight: the non-application process memory module 602 sends the data on the first data object to the data cache module 601.

Step nine: the data caching module 601 generates data on a third data object based on the data on the first data object after receiving the data on the first data object.

Specifically, after the application on the electronic device 100 is turned on again and again, the electronic device 100 creates a process of the application one on the electronic device 100. Thereafter, the application one process on the electronic device 100 obtains the data and the first session ID on the first data object stored previously from the non-application process memory. The application one process on the electronic device 100 saves the data on the first data object and the first session ID in the application process memory. Finally, in the case that the application-one process on the electronic device 100 determines that the session ID bound to the third data object is the first session ID, the application-one process on the electronic device 200 recovers the data on the third data object based on the data on the first data object in the application process memory.

In this way, it is achieved that after the application one closes, the electronic device 100 can resume on the application one to obtain the operation data of the application one generated before closing after the application one opens again.

Fig. 7 illustrates a schematic diagram of how the resulting operational data of an application on the electronic device 100 is retrieved on the electronic device 200.

The electronic device 200 includes an application one, a data buffer module 701, a non-application process memory module 702, and a communication module 703.

The electronic device 100 includes an application one, a data buffer module 601 and a communication module 704.

The recovery of the generated operation data of the electronic device 100 may include the following steps. It should be understood that the following steps may be combined, not performed, deleted, etc., without limitation.

Step one: the electronic device 100 establishes a networking connection through the communication module 704 and the electronic device 200 through the communication module 703.

Specifically, the manner in which the device shown in the embodiment of fig. 1 establishes the networking connection may be referred to, which is not described herein.

Step two: upon the application on the electronic device 100 opening, the application sends an open instruction to the data cache module 601.

Step three: the data buffer module 601 creates a first data object of the application one after receiving the start instruction.

Step four: the data buffer module 601 obtains data on the first data object, and obtains a session ID (first session ID) to which the first data object is bound. The first data object binds the first session ID, so that after the application one closes, the data on the application one can be recovered based on the session ID bound by the data object on the application one.

For the detailed descriptions of the second to fourth steps, reference may be made to the descriptions of the first to third steps in the embodiment of fig. 6, and the description of this embodiment will not be repeated here.

Optionally, the non-application process memory module 602 shown in fig. 6 may also be included in fig. 7, that is, the electronic device 100 may also select to store the data on the first data object and the first session ID in the non-application process memory module 602 on the electronic device 100.

Step five: the data buffering module 601 sends the data on the first data object and the first session ID to the communication module 704.

Alternatively, the data buffer module 601 may periodically send the data on the first data object to the communication module 704.

Optionally, the data buffer module 601 may also send the data on the first data object to the communication module 704 before applying a shutdown.

Step six: after acquiring the data and the first session ID on the first data object, the communication module 704 sends the data and the first session ID on the first data object to the communication module 703 on the electronic device 200 through the networking connection.

Step seven: after acquiring the data and the first session ID on the first data object, the communication module 703 sends the data and the first session ID on the first data object to the non-application process memory module 702.

The non-application process memory module 702 stores the data and the first session ID on the first data object in the non-application process memory after receiving the data and the first session ID on the first data object.

Thus, even if the application on the electronic device 100 is closed, the electronic device 200 still stores the operation data generated before the application on the electronic device 100 is closed.

For how the non-application process memory module 702 stores the data on the first data object and the first session ID in the non-application process memory, reference may be made to the description of step four in the embodiment of fig. 6, which is not repeated herein.

Step eight: upon the application on the electronic device 200 opening, the application on the electronic device 200 sends an opening instruction to the data cache module 701.

Step nine: after receiving the start instruction, the data buffer module 701 creates a second data object of the application one, and obtains a session ID bound to the second data object.

Step ten: the data cache module 701 determines the session ID of the second data object binding as the first session ID.

It should be noted that, the session ID of an internal data object binding is applied to the electronic device 200, which is preset. For example, data objects within the same application on electronic device 100 and electronic device 200 may bind the same session ID. In this way, synchronization of data between applications on both devices can be achieved.

Step eleven: the data cache module 701 sends the first session ID to the non-application process memory module 702.

Because the non-application process memory module 702 may store data within a plurality of different applications on the electronic device 100, such as data on a plurality of sets of in-application data objects and stored data of session IDs to which the in-application data objects are bound. The data caching module 701 needs to determine which session ID is acquired for the data on the associated data object. Therefore, the data buffer module 701 may send the first session ID of the application-internal data object binding on the electronic device 200 to the non-application process memory module 702, and determine, based on the first session ID of the application-internal data object binding on the electronic device 200, that the session ID on the electronic device 100 is also data on the data object associated with the first session ID.

Step twelve: in response to the first session ID, the non-application process memory module 702 obtains the data on the first data object associated with the first session ID, and sends the data on the first data object to the data cache module 701.

Step thirteen: the data buffer module 701, after receiving the data on the first data object, recovers the data on the second data object based on the data on the first data object.

In some examples, application one on electronic device 200 is open, and electronic device 200 corresponds to a process that creates application one. Thereafter, the application one process on the electronic device 200 obtains the session ID of the second data object, which may be the first session ID. The process of application one on the electronic device 200 obtains the data on the first data object associated with the first session ID from the non-application process memory based on the first session ID. The application one process on the electronic device 200 stores the data on the first data object in the application process memory. Finally, the process of application one on the electronic device 200 retrieves the data on the second data object based on the data on the first data object in the application process memory.

In this way, recovery of data within application one on electronic device 100 is achieved on application one of electronic device 200. And, the data in the application is recovered on the opposite terminal device, and the data in the application can be recovered on the opposite terminal device even if the application is closed regardless of the running state of the application on the opposite terminal device. The method solves the problem that the same application on the two-end equipment must be in an open state when the data in the same application on the two-end equipment are synchronized at present.

Fig. 8 illustrates a schematic diagram of the electronic device 200 locally retrieving data within an application on the electronic device 100.

Similar to fig. 8, the embodiment of the present application describes how the electronic device 200 recovers the data in the application one of the electronic device 100. It should be understood that the following steps may be combined, not performed, deleted, etc., without limitation. For example, step 806 in the corresponding embodiment of fig. 8 may not be performed or deleted.

S801, the electronic device 200 opens the application one, and creates a second data object of the application one.

Not limited to the second data object, the electronic device 200 may create a plurality of different data objects of application one, and the embodiment of the present application is described by taking the application one second data object as an example, but not by way of limitation.

S802, the electronic device 200 acquires the session ID bound to the second data object.

The session ID of the data object binding within the application may be preset. Data objects on different devices within the same or corresponding applications may bind the same session ID.

Alternatively, there may be multiple data objects within an application, and the multiple data objects may be of different types, so that the same session ID may be bound without the same type of data object on the same application on the device.

Alternatively, there may be multiple data objects within the application, and the multiple data objects may also bind the same session ID. The embodiments of the present application are not limited in this regard.

S803, is the electronic device 200 obtained the cached data and the corresponding session ID?

That is, whether the electronic device 200 has data and a corresponding session ID cached locally. If so, the electronic apparatus 100 performs S804, otherwise, the electronic apparatus 200 performs S807.

S804, the session ID corresponding to the cached data is the same as the session ID of the second data object?

Based on the description of the embodiment of fig. 7, electronic device 100 may save the application-generated operational data on electronic device 200 that established the networking connection. The cached data may refer to the application of a generated operating data on the electronic device 100. For example, the running data generated by an application on the electronic device 100 may be data on a first data object.

The electronic device 200 may obtain the cached data and the session ID corresponding to the cached data from the local cache area. If the electronic device 200 may cache multiple sets of cached data and session IDs corresponding to the cached data, the electronic device 100 may determine, based on the session ID bound by the second data object, cached data corresponding to the same session ID as the session ID bound by the second data object. In this way, the electronic device 100 may obtain the operation data within the application one on the electronic device 100.

If the electronic apparatus 200 does not acquire the cached data corresponding to the session ID identical to the session ID bound to the second data object, the electronic apparatus 200 performs S807.

If the electronic device 200 acquires the cached data corresponding to the session ID identical to the session ID bound to the second data object, the electronic device 200 performs S805.

S805, the electronic device 200 retrieves the data on the second data object based on the cached data.

For example, the electronic device 200 obtains the data on the first data object based on the session ID bound to the second data object, where the data on the first data object may be the running data of the application one on the electronic device 100, and the electronic device 200 may recover the data on the second data object based on the data on the first data object. In this way, recovery of data within the application on the electronic device 100 is achieved on the electronic device 200. Moreover, since the data on the first data object is stored in the non-application process memory on the electronic device 200, even if the running states of the application one on the electronic device 100 and the application one on the electronic device 200 are different, for example, the application one on the electronic device 100 is turned on, the application one on the electronic device 200 is turned off, and the electronic device 200 can still recover the running data in the application one on the electronic device 100 in the application one on the electronic device 200.

S806, the electronic device 200 deletes the cached data.

For example, after the electronic device 200 retrieves the data on the second data object based on the data on the first data object, the electronic device 200 may delete the data on the first data object cached in the non-application process, i.e., delete the retrieved data. In this way, on the one hand, the buffered data may be reduced from occupying memory space on the electronic device 200. On the other hand, after the cached data is recovered on the electronic device 200, the cached data is deleted, so that the security of the data can be ensured.

Alternatively, the electronic device 200 may not execute S806, and even after the electronic device 200 recovers the data on the second data object based on the data on the first data object, the data on the first data object may be stored locally, so that when the application on the electronic device 200 is started next time, the data on the first data object is recovered again on the application one on the electronic device 200.

Alternatively, the electronic device 200 may delete the cached data after recovering the cached data for a certain number of times. For example, after the electronic device 200 recovers the data on the second data object more than three times based on the data on the first data object, the electronic device 200 deletes the data on the first data object.

S807, ending.

Fig. 9 is a flowchart of an application data recovery method according to an embodiment of the present application.

S903-S906 are method steps for recovering and obtaining the operation data generated by the application on the electronic device 100 or on the electronic device 200.

S907-S910 are method steps for deleting, on the electronic device 100 or on the electronic device 200, the saved application of a generated operation data on the electronic device 100.

It should be understood that the following steps may be combined, not performed, deleted, etc., without limitation. E.g. S907-S910 may also be performed before S903-S906.

S901, an application on the electronic device 100 is started. The electronic device 100 creates a first data object for application one.

Before S901, the electronic device 100 and the electronic device 200 establish a networking connection, and in particular, the method for establishing a networking connection between the electronic device 100 and the electronic device 200 described in the foregoing embodiment may be referred to, which is not described herein.

Not limited to the first data object, the electronic device 100 may create a plurality of different data objects of application one, and the embodiment of the present application is described by taking the first data object of application one as an example, but not by way of limitation.

S902, the electronic device 100 obtains the data on the first data object and the session ID bound to the first data object.

The session ID of the data object binding within the application may be preset. The same session ID may be bound without data objects within the same application on the device.

S903, the electronic device 100 invokes a save interface, and determines whether the saved device identifier is the electronic device 100 or the electronic device 200?

The electronic device 100 may save the running data generated by the application on the electronic device 100 or on the electronic device 200 that established the connection.

The present application provides a set of general programming paradigms that allow electronic device 100 to invoke a save interface to cache data locally or on other electronic devices that establish a connection in a very simple manner, reducing the workload of the developer.

Examples of the contents of the save interface in the programming paradigm are as follows:

let obj= (); data object creation

obj. Setsessionid ("sessionId"); session ID of/get data object

await result = obj.save (); apparatus for selecting and saving

The save interface mainly comprises three parts, the first part is a create data object interface, which is used to create data objects of the application. The second part is a session ID interface for acquiring the data object, and the session ID interface of the data object is used for acquiring the session ID bound to the data object of the application. The third part is to select a saved device interface, which is used to select a saved device identity.

Wherein the device interface selected for saving may specify one or more devices. I.e. simultaneously save the running data generated by the application one on one or more devices.

It should be noted that, in other embodiments, the name of the interface for creating the data object, the name of the session ID interface for obtaining the data object, and the name of the device interface selected for saving may all be changed, but the principles are similar, and the embodiments of the present application are not limited thereto.

S904, in the case that the saved device identifier is the electronic device 200, the data on the first data object and the session ID bound to the first data object are sent to the electronic device 200.

The electronic device 100 may invoke the save interface and select the saved device's identification as the device identification of the electronic device 200. In the case that the saved device identifier is determined to be the device identifier of the electronic device 200, the electronic device 100 sends the data on the first data object and the session ID bound to the first data object to the electronic device 200.

S905, the electronic device 200 caches the data on the first data object and the session ID bound to the first data object in the local non-application process memory.

After receiving the data on the first data object and the session ID bound to the first data object sent by the electronic device 100, the electronic device 200 stores the data on the first data object and the session ID bound to the first data object in a local non-application process memory. In this way, it is possible to receive and store the data in the application sent by the electronic device 100 even if the application on the electronic device 200 is not opened, where the data in the application may be the data on the first data object, and recover the data in the application on the electronic device 100 from the application on the electronic device 200 after the application on the subsequent electronic device 200 is opened.

Optionally, after the electronic device 200 stores the data on the first data object and the session ID of the first data object binding in the local area, the electronic device 200 may inform the electronic device 100 that the data on the first data object and the session ID of the first data object binding have been stored in the local area based on the remote callback.

After the electronic device 200 caches the data on the first data object and the session ID bound to the first data object locally, the electronic device 200 may recover the data on the first data object within the application on the electronic device 200. For a specific implementation, reference may be made to the description in the embodiment of fig. 7, and this embodiment of the application is not repeated here.

The application provides a set of general programming paradigms, and the electronic device 100 invokes a recovery interface, so that local data can be recovered and stored in a very simple manner, and the workload of developers is reduced.

aset (result. Version= obj. Version); data on data object

The electronic device 200 may invoke the restore interface to restore the resulting operational data of the application one on the electronic device 100 to the application one on the electronic device 200.

It should be noted that, in other embodiments, the name of the restoration interface may vary, but the principles are similar, and the embodiments of the present application are not limited thereto.

S906, under the condition that the saved device identifier is the electronic device 100, caching the data on the first data object and the session ID bound by the first data object in a local non-application process memory.

The electronic device 100 may invoke the save interface and select the saved device's identification as the device identification of the electronic device 100.

In the case that the saved device identifier is determined to be the device identifier of the electronic device 100, the electronic device 100 caches the data on the first data object and the session ID bound by the first data object in the local non-application process memory. Specifically, the electronic device 100 may store the data on the first data object and the session ID bound to the first data object in the non-application process memory, and after the application on the electronic device 100 is suddenly closed, the data on the first data object is not cleared.

Alternatively, the electronic device 100 may invoke the save interface and select the saved device identifier as the device identifier of the electronic device 100 and the electronic device 200, that is, save the operation data generated by the application on the electronic device 100 on multiple devices at the same time. In the case that the saved device identifier is determined to be the device identifier of the electronic device 100 and the device identifier of the electronic device 200, on one hand, the electronic device 100 caches the data on the first data object and the session ID bound by the first data object in the local non-application process memory. On the other hand, the electronic device 100 sends the data on the first data object and the session ID of the first data object binding to the electronic device 200, so that the data on the first data object and the session ID of the first data object binding may be stored in a non-application process memory on the electronic device 200.

S907, after saving the data, the electronic device 100 may call the deletion interface, and determine whether the deleted device is identified as the electronic device 100 or the electronic device 200.

The electronic device 100 may delete the operation data generated by the application stored on the electronic device 100 or on the connection-established electronic device 200.

The present application provides a set of general programming paradigms in which the electronic device 100 invokes a delete interface to delete data locally or from other electronic devices that establish a connection in a very simple manner, reducing the workload of the developer.

The content of the delete interface is as follows:

await result = obj. Delet (); apparatus for selecting/deleting

Wherein the device interface selected for deletion may specify one or more devices. I.e., the application-generated operational data is simultaneously deleted from one or more devices.

It should be noted that, in other embodiments, the name of the device interface selected for deletion may vary, but the principle is similar, which is not limited in this embodiment of the present application.

S908, in the case where the deleted device identifier is the electronic device 200, the electronic device 100 sends a deletion instruction to the electronic device 200.

The electronic device 100 may invoke the delete interface to select the identity of the deleted device as the device identity of the electronic device 200. In the case where it is determined that the identification of the deleted device is the device identification of the electronic device 200, the electronic device 100 transmits a deletion instruction to the electronic device 200.

In response to the deletion instruction, the electronic device 200 deletes the data on the first data object and the session ID bound to the first data object from the local.

Optionally, after the electronic device 200 deletes the data on the first data object and the session ID of the first data object binding from the local, the electronic device 200 may inform the electronic device 100 that the data on the first data object and the session ID of the first data object binding have been deleted from the local based on the remote callback.

S910, in the case that the saved device identifier is the electronic device 100, the electronic device 100 deletes the data on the first data object and the session ID bound to the first data object from the local.

The electronic device 100 may invoke the delete interface and select the identity of the deleted device as the device identity of the electronic device 100. In the case that the deleted device identifier is determined to be the device identifier of the electronic device 100, the electronic device 100 deletes the data on the first data object and the session ID bound to the first data object from the local.

Alternatively, the electronic device 100 may invoke the deletion interface and select the identifier of the deleted device as the device identifiers of the electronic device 100 and the electronic device 200, i.e. the running data generated by the application on the electronic device 100 may be deleted from multiple devices at the same time. In the case that the deleted device identifier is determined to be the device identifier of the electronic device 100 and the device identifier of the electronic device 200, on the one hand, the electronic device 100 deletes the data on the first data object and the session ID bound to the first data object from the local. On the other hand, the electronic device 100 sends a deletion instruction to the electronic device 200, so that the electronic device 200 deletes the stored data on the first data object and the session ID bound to the first data object from the local after receiving the deletion instruction.

Fig. 10 is a flowchart of another method for storing application data according to an embodiment of the present application.

S1001, the first electronic device starts a first application on the first electronic device, and obtains data on a first data object in the first application and a first session ID bound by the first data object.

The first electronic device may be the electronic device 100 and the second electronic device may be the electronic device 200.

The first application may be application one on the electronic device 100 described in the foregoing embodiments.

In one possible implementation, the first electronic device is further configured to store the data on the first data object and the first session ID in a non-application process memory on the first electronic device.

In one possible implementation, the first electronic device is further configured to close the first application; the first electronic device is further configured to, after closing the first application, restart the first application, and obtain a third session ID bound to the third data object; the first electronic device is further configured to generate data on the third data object based on the data on the first data object if the third session ID and the first session ID are the same. Therefore, when the first application is opened after being closed, the application data generated by the first application before being closed can be recovered again.

In one possible implementation, the first electronic device is further configured to delete the data on the first data object and the first session ID from the non-application process memory on the first electronic device. Thus, the application data stored on the local device can be deleted.

S1002, the first electronic device sends the data on the first data object and the first session ID to the second electronic device.

S1003, the second electronic device receives the data and the first session ID on the first data object, and stores the data and the first session ID on the first data object in a non-application process memory.

In one possible implementation, the second electronic device is specifically configured to: receiving data and a first session ID on a first data object when a second application on a second electronic device is in a closed state; wherein the second application and the first application are the same or corresponding applications. In this way, the second application on the second electronic device may also receive and store the data on the first data object sent by the first electronic device in the closed state.

Wherein the second application may be application one on the electronic device 200 described in the previous embodiments.

In one possible implementation manner, the second electronic device is further configured to open a second application, and obtain a second session ID bound to a second data object in the second application; the second electronic device is further configured to generate data on the second data object based on the data on the first data object if the second session ID is the same as the first session ID.

In one possible implementation, the second electronic device is specifically configured to: creating a process of the second application; acquiring data on the first data object from a non-application process memory through a process of the second application; storing the data on the first data object in an application process memory on the second electronic device through a process of the second application; and generating data on the second data object based on the data on the first data object in the application process memory.

In one possible implementation, the non-application process memory includes any one of the following: a first memory partition in the ROM read only memory and the RAM random access memory; the application process memory comprises a second storage partition in the RAM; wherein the second memory partition in RAM is different from the first memory partition in RAM.

In one possible implementation, the first electronic device is further configured to send a first instruction to the second electronic device; the second electronic device is further configured to delete the data on the first data object and the first session ID from the non-application process memory on the second electronic device in response to the first instruction. Thus, application data stored on other electronic devices can be deleted.

Thus, the data on the first data object sent by the first electronic device can be received and saved regardless of whether the second application on the second electronic device is open or closed.

S1101, the first electronic device starts a first application on the first electronic device, and obtains data on a first data object in the first application and a first session ID bound by the first data object.

And S1102, the first electronic device stores the data on the first data object and the first session ID in a non-application process memory.

In one possible implementation, after the first electronic device saves the data on the first data object and the first session ID in the non-application process memory, the method further includes: the first electronic device closes the first application; after the first application is closed, the first electronic equipment opens the first application again, and acquires a third session ID bound with a third data object; in the case that the third session ID and the first session ID are the same, the first electronic device generates data on the third data object based on the data on the first data object.

In one possible implementation, the first electronic device generates data on a third data object based on the data on the first data object, specifically including: the first electronic equipment builds a process of a first application; the first electronic device acquires data on a first data object from a non-application process memory through a process of a first application; the first electronic device stores the data on the first data object in an application process memory through a process of a first application; the first electronic device generates data on a third data object based on the data on the first data object in the applied process memory.

In one possible implementation, after the first electronic device saves the data on the first data object and the first session ID in the non-application process memory, the method further includes: the first electronic device deletes the data on the first data object and the first session ID from the non-application process memory.

The embodiments of the present application may be arbitrarily combined to achieve different technical effects.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that implementing all or part of the above-described method embodiments may be accomplished by a computer program to instruct related hardware, the program may be stored in a computer readable storage medium, and the program may include the above-described method embodiments when executed. And the aforementioned storage medium includes: ROM or random access memory RAM, magnetic or optical disk, etc.

In summary, the foregoing description is only exemplary embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present invention should be included in the protection scope of the present invention.

Claims

1. An application data saving system, characterized in that the system comprises a first electronic device and a second electronic device which are communicatively connected, wherein,

the first electronic device is configured to open a first application on the first electronic device, and obtain data on a first data object in the first application and a first session id bound to the first data object;

the first electronic device is further configured to send the data on the first data object and the first session ID to the second electronic device;

The second electronic device is configured to receive the data on the first data object and the first session id, and store the data on the first data object and the first session id in a non-application process memory.

2. The system of claim 1, wherein the second electronic device is specifically configured to:

receiving data on the first data object and the first session ID when a second application on the second electronic device is in a closed state; wherein the second application and the first application are the same or corresponding applications.

3. The system of claim 2, wherein the second electronic device is further configured to open the second application and obtain a second sessionID bound to a second data object in the second application;

the second electronic device is further configured to generate data on the second data object based on the data on the first data object if the second session ID and the first session ID are the same.

4. A system according to claim 3, characterized in that the second electronic device is specifically configured to:

creating a process of the second application;

Acquiring data on the first data object from the non-application process memory through the process of the second application;

storing the data on the first data object in an application process memory on the second electronic device through the process of the second application;

and generating data on the second data object based on the data on the first data object in the application process memory.

5. The system of any of claims 1-4, wherein the first electronic device is further configured to store the data on the first data object and the first session ID in a non-application process memory on the first electronic device.

6. The system of any of claims 5, wherein the first electronic device is further configured to close the first application;

the first electronic device is further configured to, after closing the first application, restart the first application, and obtain a third sessionID bound to a third data object;

the first electronic device is further configured to generate data on the third data object based on the data on the first data object if the third session ID and the first session ID are the same.

7. The system of claim 4, wherein the non-application process memory comprises any one of: a first memory partition in the ROM read only memory and the RAM random access memory;

the application process memory comprises a second storage partition in the RAM;

wherein the second memory partition in the RAM is different from the first memory partition in the RAM.

8. The system of any of claims 1-7, wherein the first electronic device is further configured to send a first instruction to the second electronic device;

the second electronic device is further configured to delete, in response to the first instruction, the data on the first data object and the first session id from the non-application process memory on the second electronic device.

9. The system of claim 5 or 6, wherein the first electronic device is further configured to delete the data on the first data object and the first session ID from a non-application process memory on the first electronic device.

10. An application data preservation method, characterized in that the method comprises:

the method comprises the steps that communication connection is established between a first electronic device and a second electronic device;

The first electronic equipment starts a first application on the first electronic equipment, and acquires data on a first data object in the first application and a first session ID bound with the first data object;

the first electronic device sends the data on the first data object and the first session ID to the second electronic device through the communication connection; the data on the first data object and the first session ID are used for the second electronic device to store the data on the first data object and the first session ID in a non-application process memory.

11. The method according to claim 10, wherein the first electronic device sends the data on the first data object and the first session ID to the second electronic device via the communication connection, in particular comprising:

when a second application on the second electronic device is in a closed state, the first electronic device sends the data on the first data object and the first session ID to the second electronic device through the communication connection; wherein the second application and the first application are the same or corresponding applications.

12. The method according to claim 10 or 11, characterized in that the method further comprises:

and the first electronic equipment stores the data on the first data object and the first session ID in a non-application process memory on the first electronic equipment.

13. The method of claim 12, wherein after the first electronic device saves the data on the first data object and the first session ID in non-application process memory on the first electronic device, the method further comprises:

the first electronic device closes the first application;

after the first electronic device closes the first application, the first electronic device opens the first application again, and obtains a third sessionID bound by a third data object;

and generating data on the third data object by the first electronic equipment based on the data on the first data object under the condition that the third session ID and the first session ID are the same.

14. The method according to claim 13, wherein the first electronic device generates data on the third data object based on data on the first data object, specifically comprising:

The first electronic device creates a process of the first application;

the first electronic device obtains data on the first data object from the non-application process memory through the process of the first application;

the first electronic device stores the data on the first data object in an application process memory on the first electronic device through the process of the first application;

and the first electronic equipment generates data on the third data object based on the data on the first data object in the application process memory through the process of the first application.

15. The method of claim 14, wherein the non-application process memory comprises any one of: a first memory partition in the ROM read only memory and the RAM random access memory;

the application process memory comprises a second storage partition in the RAM;

16. The method of any of claims 10-15, wherein after the first electronic device transmits the data on the first data object and the first session id to the second electronic device over the communication connection, the method further comprises:

The first electronic device sends a first instruction to the second electronic device; the first instruction is used for indicating the second electronic equipment to delete the data on the first data object and the first session ID from the non-application process memory on the second electronic equipment.

17. The method of any of claims 12-15, wherein after the first electronic device saves the data on the first data object and the first session ID in non-application process memory on the first electronic device, the method further comprises:

and deleting the data on the first data object and the first sessionID from a non-application process memory on the first electronic device by the first electronic device.

18. An application data preservation method, characterized in that the method comprises:

the second electronic device establishes communication connection with the first electronic device;

the second electronic device receives data on a first data object sent by the first electronic device and a first session ID bound with the first data object, wherein the first data object is a data object in a first application on the first electronic device;

And the second electronic equipment stores the data on the first data object and the first session ID in a non-application process memory.

19. The method of claim 18, wherein the second electronic device receives the data on the first data object sent by the first electronic device and the first session id bound to the first data object, specifically comprising:

when a second application on the second electronic device is in a closed state, the second electronic device receives data on the first data object and the first session ID, which are sent by the first electronic device; wherein the second application and the first application are the same or corresponding applications.

20. The method of claim 18 or 19, wherein after the second electronic device saves the data on the first data object and the first session ID in non-application process memory, the method further comprises:

the second electronic device creates a process of the second application;

the second electronic equipment acquires the data on the first data object from the non-application process memory through the process of the second application;

The second electronic equipment stores the data on the first data object in an application process memory on the second electronic equipment through the process of the second application;

and the second electronic equipment generates data on the second data object based on the data on the first data object in the application process memory through the process of the second application.

21. The method of claim 20, wherein the non-application process memory comprises any one of: a first memory partition in the ROM read only memory and the RAM random access memory;

the application process memory comprises a second storage partition in the RAM;

22. The method of any of claims 18-21, wherein after the second electronic device saves the data on the first data object and the first session ID in non-application process memory, the method further comprises:

the second electronic equipment receives a first instruction sent by the first electronic equipment;

and in response to the first instruction, the second electronic device deletes the data on the first data object and the first session ID from the non-application process memory on the second electronic device.

23. An electronic device, which is a first electronic device, characterized in that the first electronic device comprises: one or more processors, one or more memories; the one or more memories coupled with the one or more processors, the one or more memories to store computer program code comprising computer instructions that the one or more processors invoke to cause the first electronic device to perform the method of any of the above claims 10-17.

24. An electronic device, being a second electronic device, characterized in that the second electronic device comprises: one or more processors, one or more memories; the one or more memories coupled with the one or more processors, the one or more memories to store computer program code comprising computer instructions that the one or more processors invoke to cause the second electronic device to perform the method of any of the above claims 18-22.

25. A computer readable storage medium storing computer instructions which, when run on a first electronic device, cause the first electronic device to perform the method of any of the preceding claims 10-17.

26. A computer readable storage medium storing computer instructions which, when run on a second electronic device, cause the second electronic device to perform the method of any of the preceding claims 18-22.

27. A computer program product, characterized in that the computer program product, when run on a first electronic device, causes the first electronic device to perform the method of any of the preceding claims 10-17.

28. A computer program product, characterized in that the computer program product, when run on a second electronic device, causes the second electronic device to perform the method of any of the preceding claims 18-22.