Data sharing methods, electronic devices and systems

The data sharing method enhances user experience by enabling quick viewing and management of digital assets across devices through metadata sharing and wireless connections, addressing the challenge of centralized asset management across multiple devices.

JP7844803B2Active Publication Date: 2026-04-14HUAWEI TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
HUAWEI TECH CO LTD
Filing Date
2021-03-16
Publication Date
2026-04-14

AI Technical Summary

Technical Problem

Users face challenges in centrally managing their digital assets across multiple devices such as mobile phones, tablets, and PCs, leading to degraded user experience due to the need for regular file transfer and backup operations.

Method used

A data sharing method and system that allows electronic devices to share metadata, enabling quick viewing and management of digital assets across devices by associating login accounts and using short-range or long-range wireless connections to transmit metadata and thumbnails, reducing the need for transferring full file data.

Benefits of technology

Improves user experience by allowing quick browsing and centralized management of digital assets across devices, saving storage space by sharing metadata instead of full file data and facilitating efficient file access and search functionality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007844803000005
    Figure 0007844803000005
  • Figure 0007844803000006
    Figure 0007844803000006
  • Figure 0007844803000007
    Figure 0007844803000007
Patent Text Reader

Abstract

The present application provides a data sharing method, electronic device, and system. The method includes: an electronic device establishing a network connection to another electronic device, the network connection being used to communicate data; when detecting a user's operation to search for a target file, the electronic device requesting a shared file associated with the target file from the other electronic device; receiving the shared file sent by the other electronic device; and displaying a first interface on the electronic device, the first interface including an identifier of the shared file on the electronic device and an identifier of the shared file on the other electronic device. The present application facilitates quick viewing of distributed digital assets on multiple devices, thereby improving the user experience.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application claims priority to Chinese Patent Application No. 202010225513.8, titled "Data Sharing Method, Electronic Device, and System", filed with the China National Intellectual Property Administration on March 26, 2020. The entire patent application is incorporated herein by reference in its entirety.

[0002] This application relates to the field of terminals, and more specifically, to a data sharing method, an electronic device, and a system.

Background Art

[0003] As users increasingly own more intelligent devices, the user's digital assets (such as pictures, videos, audio, and documents) are distributed across these separate devices, including mobile phones, tablet computers, personal computers (PCs), personal computers, smart TVs, and head units. However, if the user wishes to centrally manage their digital assets on these devices, there is currently no simple and effective method.

[0004] Currently, when transferring or sharing files such as pictures, audio, videos, and documents between devices, the user can back up pictures and videos on a device such as a mobile phone or pad to a PC. The PC can be used as the final storage medium. However, in this case, the user needs to perform the operation regularly. As a result, the user experience is degraded.

Summary of the Invention

[0005] This application provides a data sharing method, an electronic device, and a system to improve the user experience by facilitating the quick viewing of digital assets distributed across multiple devices.

[0006] According to the first embodiment, a system is provided. The system includes a first electronic device and a second electronic device, the first electronic device storing a shared file of a first application. The second electronic device is configured to determine the first electronic device within a predetermined distance. A login account on the first electronic device is associated with a login account on the second electronic device. The second electronic device is further configured to request metadata corresponding to each file in the shared file from the first electronic device when it detects an operation by a user to open the first application. The first electronic device is further configured to send the metadata for each file to the second electronic device. The second electronic device is further configured to determine the number of files in the shared file based on the number of metadata received. The second electronic device is further configured to display a first interface, the first interface including a folder corresponding to the shared file, the device name of the first electronic device, and the number of files.

[0007] In this embodiment of the present application, a second electronic device may determine a first electronic device within a predetermined distance associated with a login account on the second electronic device, and the second electronic device may request metadata of application files from the first electronic device. This helps users to quickly view the status of digital assets stored on the first electronic device by using the second electronic device, and satisfies user requirements for performing centralized management of digital assets distributed across various devices. This improves the user experience.

[0008] In addition, the first electronic device shares metadata corresponding to each file with the second electronic device, rather than the original data of each file. In this case, during the data sharing process, the user can also quickly browse the status of digital assets on the other device, and more storage space is saved on the electronic device.

[0009] In some possible implementations, the metadata for each file includes information such as the file name, file size, and creation time.

[0010] In relation to the first embodiment, in some implementations of the first embodiment, the first application is an album application. The second electronic device is further configured to request thumbnails of one or more pictures stored in the first electronic device from the first electronic device. The second electronic device is further configured to display at least a portion of the thumbnails of one or more pictures after detecting a user tap on a folder on the first interface.

[0011] In this embodiment of the present application, with respect to the album application, the second electronic device may further request thumbnails of one or more pictures in the album application on the first electronic device from the first electronic device. In this way, after the user taps a folder, the second electronic device displays at least a portion of the thumbnails of one or more pictures to the user in a timely manner.

[0012] In some possible implementations, the second electronic device may, alternatively, request thumbnails of one or more pictures from the first electronic device after detecting a user tap on a folder.

[0013] In some possible implementations, the second electronic device may, after detecting a user tap on a folder, alternatively display multiple subfolders of the folder. Either a thumbnail is displayed for each of the multiple subfolders, or the thumbnails within each subfolder are displayed on the subfolder's cover page.

[0014] In relation to the first embodiment, in some implementations of the first embodiment, the second electronic device is further configured to request a first picture corresponding to the first thumbnail from the first electronic device when it detects an operation by the user to tap the first thumbnail. The thumbnails of one or more pictures include the first thumbnail, and the first picture is a picture having a preset screen resolution. The first electronic device is further configured to transmit the first picture to the second electronic device. The second electronic device is further configured to display a second interface, which includes the first picture.

[0015] In this embodiment of the present application, when a user is viewing a thumbnail of a picture stored on a first electronic device on a second electronic device, the second electronic device may request a picture with a preset screen resolution from the first electronic device instead of the original data of the picture corresponding to the thumbnail. This can ensure that the second electronic device displays the picture to the user quickly. This helps to improve the user's browsing speed and saves more storage space on the electronic device.

[0016] In relation to the first embodiment, in some implementations of the first embodiment, the second interface further includes a first control for local storage. The second electronic device is further configured to request a second picture corresponding to a first thumbnail from the first electronic device when it detects a user tap on the first control. The second picture is the original data of the picture corresponding to the thumbnail. The first electronic device is further configured to send the second picture to the second electronic device. The second electronic device is further configured to store the second picture in the second electronic device.

[0017] In this embodiment of the present application, the second electronic device requests the original data of the picture from the first electronic device only if the user wishes to locally store the picture on the first electronic device to the second electronic device. Thus, in the process of the second electronic device displaying the picture in the first electronic device to the user, the second electronic device does not need to store the original data of each picture stored in the first electronic device. As a result, the user can quickly browse the status of digital assets on another device, and more storage space is saved on the electronic device.

[0018] In relation to the first embodiment, in some implementations of the first embodiment, the second electronic device is further configured to establish a metadata index for each file based on the metadata of each file after receiving the metadata of each file transmitted by the first electronic device. The second electronic device is further configured to display search results based on the keyword and the metadata index after detecting a keyword entered by the user into the search box of the first application.

[0019] In this embodiment of the present application, the second electronic device may, after retrieving the metadata of each file stored in the first electronic device, establish an index of each file based on the metadata. This helps the user quickly find the file they wish to view.

[0020] In one embodiment, the second electronic device also stores each file of the first application (for example, the album application of the second electronic device also includes one or more pictures). In this case, the second electronic device may generate metadata corresponding to each file and establish an index of the metadata for each file. Thus, when the second electronic device detects that a user is searching for a file, it may display search results based on keywords, the index of the metadata for each file stored in the second electronic device, and the index of the metadata for each file transmitted by the first electronic device.

[0021] In relation to the first embodiment, in some implementations of the first embodiment, the first electronic device is further configured to send the metadata of each file in the updated shared file to the second electronic device when it detects that the shared file has been updated. The second electronic device is configured to receive the metadata of each file in the updated shared file and update the metadata of the shared file.

[0022] In this embodiment of the present application, if metadata in a shared file stored on the first electronic device changes, for example, if the first electronic device detects that a user has added some files to the shared file or deleted some files from the shared file, the first electronic device may send the updated metadata to the second electronic device. In this way, the second electronic device can update the metadata of the shared file on the first electronic device in a timely manner and display the change status of the files stored on the first electronic device to the user.

[0023] In some possible implementations, if the first electronic device determines that the number of files in the shared file is increasing, it may send the metadata of the added files to the second electronic device, or it may send the metadata of each file in the shared file to the second electronic device.

[0024] In relation to the first embodiment, in some implementations of the first embodiment, the association of a login account on a first electronic device with a login account on a second electronic device includes the following: the login account on the first electronic device is the same as the login account on the second electronic device; the login account on the first electronic device and the login account on the second electronic device are in the same family group; or the login account on the first electronic device is an account authenticated by the login account on the second electronic device.

[0025] In this embodiment of the present application, data sharing between the first electronic device and the second electronic device may be performed under the same account or under different accounts. This may extend the range of electronic devices that can be found by the second electronic device and help the user perform centralized management of digital assets in more electronic devices.

[0026] A data sharing method is provided according to a second embodiment. The method is applied to an electronic device having a display. The method includes the steps of: determining that an electronic device determines another electronic device within a predetermined distance, wherein a login account on the other electronic device is associated with a login account on the electronic device; transmitting request information to another electronic device when the electronic device detects an operation by a user to open a first application, wherein the request information is used to request metadata for each file in a shared file stored on the other electronic device of the first application; receiving metadata for each file in a shared file transmitted by the other electronic device; and displaying a first interface using a display, wherein the first interface includes a folder corresponding to the shared file, the device name of the other electronic device, and the number of files, the number of files being determined by the electronic device based on the number of received metadata.

[0027] In relation to the second aspect, in some implementations of the second aspect, the first application is an album application. The method further includes the steps of: before displaying the first interface, the electronic device requests from the other electronic device thumbnails of one or more pictures stored on the other electronic device; and after detecting a user tap on a folder on the first interface, the electronic device displays at least some of the thumbnails of one or more pictures.

[0028] In connection with the second aspect, in some implementations of the second aspect, when the method detects an operation of a user tapping on a first thumbnail, the method includes a step of the electronic device requesting a first picture corresponding to the first thumbnail from another electronic device, where the thumbnail of one or more pictures includes the first thumbnail, and the first picture is a picture having a preset screen resolution; a step of the electronic device receiving the first picture transmitted by the other electronic device; and a step of the electronic device displaying a second interface on the display by using the display, where the second interface includes the first picture.

[0029] In connection with the second aspect, in some implementations of the second aspect, the second interface further includes a first control for local storage. When the method detects an operation of a user tapping on the first control, the method includes a step of the electronic device requesting a second picture corresponding to the first thumbnail from another electronic device, where the second picture is the original data of the picture corresponding to the thumbnail; and a step of the electronic device receiving and storing the second picture transmitted by the other electronic device.

[0030] In connection with the second aspect, in some implementations of the second aspect, after the electronic device receives the metadata of each file transmitted by another electronic device, the method includes a step of the electronic device establishing an index of the metadata of each file based on the metadata of each file; and after the method detects a keyword entered by the user in the search box of the first application, a step of the electronic device displaying search results based on the keyword and the index of the metadata.

[0031] In connection with the second aspect, in some implementations of the second aspect, the method further includes a step of the electronic device receiving and storing the metadata of each file in an updated shared file on another electronic device.

[0032] In relation to the second aspect, in some implementations of the second aspect, the association of a login account on another electronic device with a login account on another electronic device includes the login account on the other electronic device being the same as the login account on another electronic device, the login account on the other electronic device and the login account on another electronic device being in the same family group, or the login account on the other electronic device being an account authenticated by the login account on another electronic device.

[0033] According to a third aspect, a system is provided. The system includes a first electronic device and a second electronic device. The first electronic device is configured to establish a network connection to the second electronic device, which is used to transmit data. The first electronic device is further configured to request a shared file associated with a target file from the second electronic device when it detects an operation by a user to search for a target file. The second electronic device is further configured to send the shared file to the first electronic device. The first electronic device is further configured to display a first interface. The first interface includes an identifier for the shared file of the first electronic device and an identifier for the shared file of the second electronic device.

[0034] In this embodiment of the present application, after the first electronic device has established a network connection to the second electronic device, if a user wishes to view files distributed on the second electronic device using the first electronic device, the first electronic device may request the shared files from the second electronic device. As a result, the first electronic device displays the identifier of the shared files to the user. This actually helps the user view information about digital assets distributed on other devices on a single device and can satisfy the user's requirement for centralized management of information about digital assets distributed on various devices.

[0035] In some possible implementations, the identifier for a shared file on the first electronic device may be a folder or a thumbnail. The identifier for a shared file on the second electronic device may also be a folder or a thumbnail.

[0036] In relation to the third aspect, in some implementations of the third aspect, the shared file contains the original data or metadata, and the metadata is attribute description information for each file within the shared file.

[0037] In this embodiment of the present application, the second electronic device may transmit metadata information of a shared file to the first electronic device. In this case, during the data sharing process, the user may quickly browse the status of digital assets on another device, and more storage space on the electronic device is saved.

[0038] In relation to the third aspect, in some implementations of the third aspect, the first interface further includes the device name of the second electronic device.

[0039] In this embodiment of the present application, the device name of the second electronic device is displayed on the display interface. This can help the user quickly find the status of digital assets on the electronic device that the user wishes to see.

[0040] In relation to the third aspect, in some implementations of the third aspect, the establishment of a network connection between a first electronic device and a second electronic device includes the first electronic device communicating with the second electronic device via a short-range wireless connection or the first electronic device communicating with the second electronic device via a long-range wireless connection.

[0041] In this embodiment of the present application, the first electronic device and the second electronic device may establish a connection using short-range wireless communication technology or long-range wireless communication technology. In this way, the user can quickly view the status of digital assets on nearby or distant devices using the first electronic device, and the user can easily perform centralized management of digital assets distributed across nearby or distant devices.

[0042] In relation to the third aspect, in some implementations of the third aspect, the shared file is a multimedia file. The first electronic device is further configured to request thumbnails of one or more multimedia files stored in the second electronic device from the second electronic device.

[0043] In relation to the third aspect, in some implementations of the third aspect, the first electronic device is further configured to request a first multimedia file corresponding to the first thumbnail from the second electronic device when it detects an operation by the user to tap a first thumbnail, wherein the thumbnails of one or more multimedia files include the first thumbnail, and the first multimedia file is a multimedia file having a preset screen resolution. The second electronic device is further configured to send the first multimedia file to the first electronic device. The first electronic device is further configured to display a second interface, which includes the first multimedia file.

[0044] In relation to the third aspect, in some implementations of the third aspect, the second interface further includes a first control for local storage. The first electronic device is further configured to request a second multimedia file corresponding to a first thumbnail from the second electronic device when it detects a user tapping operation on the first control, the second multimedia file being the original data of the multimedia file corresponding to the thumbnail. The second electronic device is further configured to send the second multimedia file to the first electronic device. The first electronic device is further configured to store the second multimedia file in the first electronic device.

[0045] In relation to the third aspect, in some implementations of the third aspect, the shared file includes metadata. The first electronic device is further configured to establish an index of metadata for each file based on the metadata of each file after receiving the metadata for each file transmitted by the second electronic device. The first electronic device is further configured to display search results based on keywords entered by the user and the metadata index.

[0046] In relation to the third aspect, in some implementations of the third aspect, the second electronic device is further configured to send the updated shared file to the first electronic device when it detects that the shared file has been updated. The first electronic device is configured to receive the updated shared file sent by the second electronic device.

[0047] In relation to the third aspect, in some implementations of the third aspect, the first electronic device is further configured to determine that a login account on the first electronic device is associated with a login account on the second electronic device before establishing a network connection to the second electronic device.

[0048] A data sharing method is provided according to a fourth aspect. This method is applied to an electronic device. The method includes the steps of: establishing a network connection between an electronic device and another electronic device, the network connection being used to transmit data; detecting an operation by a user to search for a target file, the electronic device requesting a shared file associated with the target file from another electronic device; the electronic device receiving the shared file transmitted by the other electronic device; and displaying a first interface, the first interface including an identifier for the shared file of the electronic device and an identifier for the shared file of the other electronic device.

[0049] In relation to the fourth aspect, in some implementations of the fourth aspect, the shared file contains the original data or metadata, and the metadata is attribute description information for each file within the shared file.

[0050] In relation to the fourth aspect, in some implementations of the fourth aspect, the first interface further includes the device name of another electronic device.

[0051] In relation to the fourth aspect, in some implementations of the fourth aspect, establishing a network connection between an electronic device and another electronic device includes either the electronic device communicating with the other electronic device via a short-range wireless connection or the electronic device communicating with the other electronic device via a long-range wireless connection.

[0052] In relation to the fourth aspect, in some implementations of the fourth aspect, the shared file is a multimedia file. The method further includes the step of an electronic device requesting thumbnails of one or more multimedia files stored in another electronic device from the other electronic device.

[0053] In relation to the fourth aspect, in some implementations of the fourth aspect, the method further includes: when an operation by a user to tap a first thumbnail is detected, the electronic device requests a first multimedia file corresponding to the first thumbnail from another electronic device, wherein the thumbnails of one or more multimedia files include the first thumbnail, and the first multimedia file is a multimedia file having a preset screen resolution; the electronic device receives the first multimedia file transmitted by the other electronic device; and the electronic device displays a second interface on a display, wherein the second interface includes the first multimedia file.

[0054] In relation to the fourth aspect, in some implementations of the fourth aspect, the second interface further includes a first control for local storage. The method further includes, when it detects an operation by a user to tap the first control, a request by an electronic device for a second multimedia file corresponding to a first thumbnail from another electronic device, wherein the second multimedia file is the original data of the multimedia file corresponding to the thumbnail; a step by which the electronic device receives the second multimedia file transmitted by the other electronic device; and a step by which the electronic device stores the second multimedia file in the electronic device.

[0055] In relation to the fourth aspect, in some implementations of the fourth aspect, the shared file includes metadata. The method further includes the steps of: the electronic device receiving metadata for each file transmitted by another electronic device, establishing an index of metadata for each file based on the metadata for each file; and the electronic device displaying search results based on keywords entered by the user and the metadata index.

[0056] In relation to the fourth aspect, in some implementations of the fourth aspect, the method further includes the step of an electronic device receiving an updated shared file transmitted by another electronic device.

[0057] In relation to the fourth aspect, in some implementations of the fourth aspect, the method further includes the step of determining that a login account on an electronic device is associated with a login account on another electronic device before establishing a network connection to another electronic device.

[0058] According to a fifth aspect, an apparatus is provided. The apparatus is included in an electronic device and has a function to implement the behavior of the electronic device in the second aspect and in possible implementations of the second and fourth aspects. This function may be implemented in hardware, or it may be implemented in hardware by running corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned function.

[0059] According to the sixth aspect, an electronic device is provided that includes one or more processors, memory, and one or more computer programs. The one or more computer programs are stored in memory, and the one or more computer programs include instructions. When the instructions are executed by the electronic device, the electronic device becomes capable of performing a data sharing method according to any possible implementation of the second and fourth aspects.

[0060] According to the seventh aspect, an electronic device comprising one or more processors and one or more memories is provided in this technical solution. The one or more memories are coupled to one or more processors and are configured to store computer program code, the computer program code includes computer instructions. When one or more processors execute computer instructions, the electronic device becomes capable of performing a data sharing method according to any possible implementation of the second and fourth aspects.

[0061] According to the eighth aspect, a computer storage medium containing computer instructions is provided in this technical solution. When the computer instructions are executed on an electronic device, the electronic device becomes capable of performing a data sharing method according to any possible implementation of the second and fourth aspects.

[0062] According to the ninth aspect, a computer program product is provided in this technical solution. When the computer program product is executed on an electronic device, the electronic device becomes capable of performing a data sharing method according to any possible design of the second and fourth aspects. [Brief explanation of the drawing]

[0063] [Figure 1] This is a schematic diagram of the structure of an electronic device according to one embodiment of the present invention.

[0064] [Figure 2] This is a block diagram of the software structure of an electronic device according to one embodiment of the present invention.

[0065] [Figure 3(a)] This is a group of GUIs according to one embodiment of the present invention. [Figure 3(b)] This is a group of GUIs according to one embodiment of the present invention. [Figure 3(c)] This is a group of GUIs according to one embodiment of the present invention. [Figure 3(d)] This is a group of GUIs according to one embodiment of the present invention. [Figure 3(e)] This is a group of GUIs according to one embodiment of the present invention. [Figure 3(f)] This is a group of GUIs according to one embodiment of the present invention. [Figure 3(g)] This is a group of GUIs according to one embodiment of the present invention.

[0066] [Figure 4(a)] This is another group of GUIs according to one embodiment of the present invention. [Figure 4(b)] This is another group of GUIs according to one embodiment of the present invention.

[0067] [Figure 5(a)] This is another group of GUIs according to one embodiment of the present invention. [Figure 5(b)] This is another group of GUIs according to one embodiment of the present invention. [Figure 5(c)] This is another group of GUIs according to one embodiment of the present invention. [Figure 5(d)] This is another group of GUIs according to one embodiment of the present invention.

[0068] [Figure 6(a)] This is another group of GUIs according to one embodiment of the present invention. [Figure 6(b)] This is another group of GUIs according to one embodiment of the present invention. [Figure 6(c)] This is another group of GUIs according to one embodiment of the present invention.

[0069] [Figure 7] This is a diagram showing another software structure for an electronic device according to one embodiment of the present invention.

[0070] [Figure 8(a)] This is a data sharing process between device A and device B according to one embodiment of the present invention. [Figure 8(b)]This is a data sharing process between device A and device B according to one embodiment of the present invention.

[0071] [Figure 9] This is a schematic diagram of a distributed browsing, searching, and management of pictures and videos according to one embodiment of the present invention.

[0072] [Figure 10(a)] This is another group of GUIs according to one embodiment of the present invention. [Figure 10(b)] This is another group of GUIs according to one embodiment of the present invention. [Figure 10(c)] This is another group of GUIs according to one embodiment of the present invention. [Figure 10(d)] This is another group of GUIs according to one embodiment of the present invention. [Figure 10(e)-1] This is another group of GUIs according to one embodiment of the present invention. [Figure 10(e)-2] This is another group of GUIs according to one embodiment of the present invention. [Figure 10(e)-3] This is another group of GUIs according to one embodiment of the present invention.

[0073] [Figure 11] This is a schematic flowchart of a data sharing method according to one embodiment of the present invention. [Modes for carrying out the invention]

[0074] The terms used in the following embodiments are intended to describe specific embodiments only and are not intended to limit the Application. Furthermore, the singular terms “one,” “a,” “the,” “the aforementioned,” “this,” and “the one” used in this Specification and the appended claims are intended to include plural forms such as “one or more,” unless explicitly stated otherwise in context. It should also be understood that “at least one” and “one or more” in the following embodiments of this Application mean one, two, or more than two. The terms “and / or” describe a correspondence to describe related subjects, indicating that three relationships may exist. For example, A and / or B may mean that only A exists, both A and B exist, or only B exists. A and B may be singular or plural. The letter “ / ” generally indicates an “or” relationship between related subjects.

[0075] The following describes electronic devices, user interfaces used with such electronic devices, and embodiments for using such electronic devices. In some embodiments, the electronic device may be a portable electronic device, such as a mobile phone, a tablet computer, or a wearable electronic device with wireless communication capabilities (e.g., a smartwatch), further including other functions such as personal digital assistant functionality and / or music playback functionality. Exemplary embodiments of the portable electronic device include, but are not limited to, portable electronic devices using iOS®, Android®, Microsoft®, or another operating system. The portable electronic device may alternatively be another portable electronic device, such as a laptop computer. It should also be understood that in some other embodiments, the electronic device may alternatively be a desktop computer instead of a portable electronic device.

[0076] For example, Figure 1 is a schematic diagram of the structure of electronic device 100. Electronic device 100 may include a processor 110, an external memory interface 120, internal memory 121, a universal serial bus (USB) port 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, a headset jack 170D, a sensor module 180, a compass 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195, etc.

[0077] It should be understood that the structures shown in these embodiments of the Application do not constitute any particular limitation on the electronic device 100. In some other embodiments of the Application, the electronic device 100 may include more or fewer components than those shown in the figures, some components may be combined, some components may be separated, and different component arrangements may be used. The components shown in the figures may be implemented in hardware, software, or a combination of software and hardware.

[0078] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent components or may be integrated into one or more processors. In some embodiments, the electronic device 100 may also include one or more processors 110. The controller may generate operation control signals based on instruction operation codes and time-series signals to complete the control of instruction fetching and instruction execution. In some other embodiments, memory may be further located within the processor 110 and configured to store instructions and data. For example, the memory within the processor 110 may be a cache. The memory may store instructions or data that have just been used or that are periodically used by the processor 110. If the processor 110 needs to use an instruction or data again, it can retrieve the instruction or data directly from memory. This avoids repeated access, reduces the latency of the processor 110, and thereby improves the data processing efficiency or instruction execution efficiency of the electronic device 100.

[0079] In some embodiments, the processor 110 may include one or more interfaces. These interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM card interface, a USB port, and the like. The USB port 130 is a port compliant with the USB standard and may specifically be a mini USB port, a micro USB port, or a USB Type-C port. The USB port 130 may be configured to connect to a charger to charge the electronic device 100, or it may be used for data transmission between the electronic device 100 and peripheral devices. Alternatively, the USB port 130 may be configured to connect to a headset to play audio using the headset.

[0080] It should be understood that the interface connection relationships between modules shown in this embodiment of the present application are merely illustrative examples and do not constitute limitations on the structure of the electronic device 100. In some other embodiments of the present application, the electronic device 100 may alternatively use a different interface connection scheme or a combination of multiple interface connection schemes than those in the embodiments described above. The charge management module 140 is configured to receive a charge input from a charger. The charge management module 140 may receive a charge input from a wired charger through the USB port 130. In some embodiments of wireless charging, the charge management module 140 may receive a wireless charge input by using the wireless charging coil of the electronic device 100. The charge management module 140 supplies power to the electronic device by using the power management module 141 while charging the battery 142. The power management module 141 is configured to connect the battery 142 and the charge management module 140 to the processor 110.

[0081] The wireless communication function of the electronic device 100 can be implemented by using antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor, etc.

[0082] The wireless communication module 160 may provide wireless communication solutions applicable to the electronic device 100, such as wireless local area network (WLAN) (Wireless Fidelity (Wi-Fi) network, etc.), Bluetooth (Bluetooth, BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technology.

[0083] The display 194 is configured to display images or videos, etc. The display 194 includes a display panel. The display panel may be a liquid crystal display (LCD), organic light-emitting diode (OLED), active-matrix organic light-emitting diode (AMOLED), flexible light-emitting diode (FLED), mini light-emitting diode (miniLED), microLED, microOLED, or quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or more displays 194.

[0084] In some embodiments of the present application, when the display panel is made of a material such as OLED, AMOLED, or FLED, the display 194 in Figure 1 can be bent. In this specification, the ability of the display 194 to be bent means that the display may be bent at any angle in at least a partial area and may be maintained at this angle. For example, the display 194 may be folded in half from left to right, or folded in half vertically.

[0085] The ISP is configured to process data fed back by the camera 193. For example, during shooting, the shutter is pressed, light is transmitted through the lens to the camera's photosensitive element, the light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, converting the electrical signal into a visible image.

[0086] The camera 193 is configured to capture still images or videos. The external memory interface 120 may be configured to connect to an external storage card, such as a microSD card, to expand the storage capacity of the electronic device 100.

[0087] The external storage card communicates with the processor 110 via the external memory interface 120 to implement data storage functionality. For example, files such as music and videos are stored on the external storage card.

[0088] The internal memory 121 may be configured to store one or more computer programs, each containing instructions. The processor 110 can execute the instructions stored in the internal memory 121. As a result, the electronic device 100 can perform data sharing methods, various applications, and data processing, etc., as provided in some embodiments of the present application.

[0089] The electronic device 100 may implement audio functions by using an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headset jack 170D, and an application processor, for example, it may implement music playback and recording functions.

[0090] The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, an optical proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, and a bone conduction sensor 180M, etc.

[0091] The gyro sensor 180B may be configured to determine the operating orientation of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (i.e., axes X, Y, and Z) can be determined using the gyro sensor 180B. The accelerometer 180E may detect the acceleration of the electronic device 100 in various directions (usually on the three axes) and may detect the magnitude and direction of gravity when the electronic device 100 is at rest. The accelerometer 180E may be further configured to recognize the orientation of the electronic device and may be used in screen switching between landscape and portrait modes, as a pedometer, or in other applications.

[0092] The magnetic sensor 180D includes a Hall effect sensor. The electronic device 100 can detect the opening and closing of the flip cover by using the magnetic sensor 180D.

[0093] The accelerometer 180E may detect acceleration of the electronic device 100 in various directions (usually on three axes), and may detect the magnitude and direction of gravity when the electronic device 100 is at rest. The accelerometer 180E may be further configured to recognize the orientation of the electronic device and may be used in screen switching between landscape and portrait modes, as a pedometer, or in other applications.

[0094] The distance sensor 180F is configured to measure distance.

[0095] The optical proximity sensor 180G may include, for example, a light-emitting diode (LED) and a photodetector, such as a photodiode. The light-emitting diode may be an infrared light-emitting diode.

[0096] The ambient light sensor 180L is configured to detect ambient light intensity. The fingerprint sensor 180H is configured to collect fingerprints. The electronic device 100 can implement fingerprint-based unlocking, application lock access, fingerprint-based capture, and fingerprint-based call answering, etc., using the characteristics of the collected fingerprints.

[0097] In this embodiment of the present application, the fingerprint sensor may include an in-display fingerprint sensor located below the side screen. The in-display fingerprint sensor may be located in a certain area of ​​the side screen. When the user performs unlocking using the side screen, they may press or touch this area. Alternatively, when the user performs unlocking using their fingerprint, they may press or touch any area on the side screen. As a result, the in-display fingerprint sensor can detect and verify the user's fingerprint information.

[0098] The temperature sensor 180J is configured to detect temperature.

[0099] The touch sensor 180K is also referred to as a “touch panel.” The touch sensor 180K is located within the display 194, and the touch sensor 180K and the display 194 may form a touchscreen, also referred to as a “touch control screen.” The touch sensor 180K is configured to detect touch operations performed on or near the touch sensor 180K. The touch sensor may forward the detected touch operations to an application processor to determine the type of touch event. Visual outputs related to the touch operations may be provided on the display 194. In some other embodiments, the touch sensor 180K may, alternatively, be located on the surface of the electronic device 100 at a location different from that of the display 194.

[0100] Figure 2 is a block diagram of the software structure of an electronic device 100 according to one embodiment of the present application. In a hierarchical architecture, the software is divided into several layers, each with a clear role and responsibility. These layers communicate with each other through a software interface. In some embodiments, the software architectures of devices A, B, and C are divided into four layers. Devices A, B, and C all include a distributed application layer and a service layer. Device A further includes a Harmony operating system core layer and a Linux® kernel layer. Device B further includes a Windows® core layer and a Windows kernel layer. Device C further includes an Android core layer and a Linux kernel layer.

[0101] The application layer may include distributed applications such as camera, gallery, file management, music, video, and contacts.

[0102] In this embodiment of the present application, the service layer may include a device knowledge library, device authentication management, and device data storage. The device knowledge library may store device names, device types, device status information, capability information, and address information for the current device and other devices. Device status information is used to indicate whether a device is online or offline. Device capability information is used to indicate whether a device supports data sharing.

[0103] In this embodiment of the present application, another device stored in the device knowledge library may be a device associated with the account of the current device, or it may be a device not associated with the account of the current device, for example, the other device and the current device may be devices in the same social software group (for example, the other device may be a device of the user's friend in the address book, or the other device may be a device in the same WeChat® group as the current device), or the other device may be a device that is not logged into an account.

[0104] Device authentication management can be applied to the process by which the current device authenticates to another device. For example, after receiving a device name transmitted by another device, the current device may determine whether the current device and the other device are devices in the same account based on the device name of the other device. For example, user account A includes devices A, B, and C. In this case, after receiving device name information transmitted by device B, device A may determine that device B is a device in the same account based on the device names stored in device A of multiple devices in account A.

[0105] For example, the current device may determine whether the current device and another device are devices within the same family group based on the device name of another device. For example, the same family group includes accounts A and B, account A includes devices A, B, and C, and account B includes devices D, E, and F. In this case, after receiving the device name of device D transmitted by device D, device A may determine that device B is a device within the same family group based on the device names of multiple devices in account B that are stored in device A.

[0106] For example, the current device may alternatively perform authentication against several devices that are not logged into any account. For instance, device A may call the lightweight computing platform interface to generate a QR code (registered trademark). Device G (a device that is not logged into any account) may scan the QR code on device A to obtain device A's media access control (MAC) address, Internet protocol (IP) address, public key information, and challenge value. Device G may encrypt its own public key using device A's public key information and send the encrypted public key to device A. Device A may decrypt device G's encrypted public key using device A's public key and obtain device G's public key. In this way, authentication between device A and device G is completed. After successful authentication with device G, device A may store device G's device name, device type, device status information, capability information, and address information in the device knowledge library.

[0107] In this embodiment of the present application, devices under the same account or within the same family group may be directly trusted by using a trust ring.

[0108] The device data storage area may be used by the current device to store data from another device (e.g., picture information, video information, document information, and audio information). The SDK interface in the distributed application layer may retrieve data from the device data storage area and display that data from another device to the user through the user interface.

[0109] Figures 3(a) to 3(g) show a group of graphical user interfaces (GUIs) for mobile phones.

[0110] Please refer to Figure 3(a). The GUI is the home screen 301 of the mobile phone. After detecting that the user has tapped the icon 302 of the album application (app) on the home screen 301, the mobile phone may open the album application and display the GUI shown in Figure 3(b).

[0111] Please refer to Figure 3(b). The GUI is the display interface for the album application. The display interface may show that the mobile phone currently has 4,278 photos and 134 videos stored. 3,177 photos have been taken by the camera, 12 photos have been taken through screenshots and screen recordings, 25 photos are in favorites, and 3 photos are in shared albums. In addition, the mobile phone also automatically searches for nearby devices under the same account when it detects that the user has opened the album application. For example, User A's account is currently logged into the mobile phone. User A's account may also have other devices (such as another mobile phone, a large-screen device, a tablet, or a smartwatch). In this case, the mobile phone will use User A's account to search for other nearby devices.

[0112] In this embodiment of the present application, multiple devices under the same account can be directly authenticated using a trust ring. When the mobile phone detects that a user has opened the album application, it can determine which devices under user A's account are within a predetermined distance from the mobile phone. For other devices under user A's account that are within a predetermined distance, the mobile phone can initiate a service request to these devices. The service request may be used to request digital assets (e.g., photos, videos, or files) stored on these devices. Thus, the digital assets on these devices are displayed on the mobile phone.

[0113] In one embodiment, the mobile phone may search for nearby or distant devices before detecting the user's tap on icon 302. After detecting the user's tap on icon 302, the mobile phone may directly display other devices that have been found.

[0114] Please refer to Figure 3(c). The GUI is an alternative display interface for the album application. If the mobile phone detects another device within a pre-set distance in User A's account, the caption "Other Devices" may be automatically displayed. The user can choose between "Local" and "Other Devices" for browsing. After detecting that the user has tapped the "Other Devices" control, the mobile phone may display the GUI shown in Figure 3(d).

[0115] In one embodiment, a mobile phone may periodically send broadcast messages to nearby devices before detecting that the user has opened the album application. The broadcast messages are used to search for other electronic devices within a predetermined distance for accounts associated with a login account on the mobile phone. If the mobile phone detects that the user has opened the album application, "Local" and "Other Devices" may be displayed directly. "Other Devices" are electronic devices found by the mobile phone that meet certain criteria.

[0116] Please refer to Figure 3(d). The GUI is another display interface for the album application. The display interface may show information about other devices within a pre-set distance in User A's account, found by the mobile phone, including the Huawei M7, Honor Vision, and Huawei P30. The mobile phone may retrieve information about the number of digital assets (e.g., photos) on the other devices. As shown in Figure 3(d), the number of photos stored on the Huawei M7 is 80, the number of photos stored on the Honor Vision is 120, and the number of photos stored on the Huawei P30 is 120. If the mobile phone detects that the user has tapped to view the album folder on the Huawei M7, it may display the GUI shown in Figure 3(e).

[0117] In one embodiment, Figure 3(d) may display folders, device names, and file counts for another device, or it may display only some of the folders, device names, and file counts for another device, or it may display information only about folders or other identifiers. After the user taps on the identifier information for another device, information such as the device name and file count may be displayed.

[0118] Please refer to Figure 3(e). The GUI is the display interface for the album on another device. The mobile phone can display information about folders stored on another device (Huawei M7). The Huawei M7's albums include folders 305, 306, 307, 308, 309, and 310. The photos in folder 305 were taken using the Huawei M7's camera, and there are 3,177 photos in folder 305. The photos in folder 306 were taken through screenshots and screen recordings, and there are 25 photos in folder 306. The photos in folder 307 were taken through data sharing (Huawei Share), and there are 9 photos in folder 307. The photos in folder 308 were taken using a social application (e.g., QQ), and there are 12 photos in folder 308. The photos in folder 309 were taken using a social application (e.g., Weibo), and there are 12 photos in folder 309. The photos in folder 310 are obtained using a social application (e.g., WeChat), and there are 6 photos in folder 310. After detecting that the user has tapped folder 305, the mobile phone may display the GUI shown in Figure 3(f).

[0119] Please refer to Figure 3(f). The GUI is the display interface for folder 305. The user can view the photos and videos stored in folder 305 by sliding the screen upwards. The mobile phone may display the GUI shown in Figure 3(g) after detecting that the user has tapped a thumbnail 311.

[0120] In one embodiment, the mobile phone may directly display the GUI shown in Figure 3(f) when it detects that the user has tapped to view the album on the Huawei M7.

[0121] Please refer to Figure 3(g). The GUI is a large image preview screen corresponding to thumbnail 311. The large image preview screen may also display more detailed information about the photograph. For example, this photograph was taken at 10:00 AM on February 14, 2019, the electronic device used to take this photograph was a Huawei M7, and this photograph was taken in Yuhuatai District, Nanjing. The large image preview screen may also display function controls such as sharing, setting as, screen projection, printing, and local saving.

[0122] After detecting a user tap on thumbnail 311, the mobile phone may request information from the Huawei M7 about a picture having a pre-set screen resolution. As shown in Figure 3(g), the picture displayed on the interface may not be the original data of the picture, but rather a picture having a pre-set screen resolution (for example, a picture with a resolution of 1080 x 1920 pixels).

[0123] For example, a user can share photo 311 with their friends using the sharing function. Alternatively, a user can set photo 311 as their home screen wallpaper or contact avatar using the "Set as" function. Alternatively, a user can project photo 311 onto a larger screen device for browsing using the screen projection function. Alternatively, a user can print photo 311 using the print function. Alternatively, a user can save photo 311 to their mobile phone using the local save function.

[0124] In one embodiment, if the mobile phone detects that the user has tapped a sharing function, a "set as" function, a screen protector function, a print function, or a local save function, it may prompt the user to save the original data or save a picture with a preset screen resolution by using a prompt box. For example, if the mobile phone detects that the user has tapped to save the original data, it may request the data of the original picture from the Huawei M7. In another example, if the mobile phone detects that the user has tapped to save a picture with a preset screen resolution, it may save the picture with the preset screen resolution directly to the local device.

[0125] In this embodiment of the present application, a user can view digital assets (e.g., pictures, videos, audio, and documents) on multiple other electronic devices in their account by using an electronic device in that account. This satisfies the user's requirement for centralized management of digital assets distributed across these devices, reduces redundant operations when the user views digital assets on these devices, and improves the user experience.

[0126] The GUIs in Figures 3(a) to 3(g) illustrate the process by which a user views photographs on another device via a mobile phone. Figures 4(a) and 4(b) show another group of GUIs according to one embodiment of the present invention, illustrating the process by which a user views videos on another device using a mobile phone.

[0127] Please refer to Figure 4(a). The GUI is the display interface for folder 305. The user can view the photos and videos stored in folder 305 by sliding the screen upwards. After detecting that the user has tapped video 401, the mobile phone may display the GUI shown in Figure 4(b).

[0128] Please refer to Figure 4(b). The GUI is a large image preview screen for video 401. The large image preview screen may also display more detailed information about video 401. For example, video 401 was filmed at 11:30 AM on March 20, 2019, the electronic device used to film video 401 was a Huawei M7, and video 401 was filmed in Yuhuatai District, Nanjing. The large image preview screen may also display function controls such as sharing, screen projection, and local saving.

[0129] For example, a user can share video 401 with their friends using the sharing function. Alternatively, a user can project video 401 onto a larger screen device for browsing using the screen projection function. Alternatively, a user can save video 401 to their mobile phone using the local save function.

[0130] Figures 5(a) to 5(d) show another group of GUIs according to one embodiment of the present invention.

[0131] Please refer to Figure 5(a). The GUI is the display interface for the album application. After detecting that the user has tapped the search box 501, the mobile phone may display the GUI shown in Figure 5(b).

[0132] Please refer to Figure 5(b). The GUI is the search interface for the album application. If the mobile phone does not detect the search keywords entered by the user, it may automatically display photo classification information to the user. For example, the mobile phone may classify photos on this phone and other devices by time, portrait, location, and label. The user can view the classification information without entering search keywords.

[0133] See Figure 5(c). The GUI is another search interface for the album application. If the mobile phone detects that the user has entered the keyword "hua" into the search box, it may categorize photos related to "hua" on this mobile phone and other devices.

[0134] For example, the mobile phone has found a total of 1,385 photos related to "hua" on this mobile phone and other devices. The mobile phone may also find 8 photos taken in Huadu District, Nanjing, 8 photos taken in Yuhuatai District, Nanjing, 8 photos of a contact named "Sister Xiaohua", and 8 photos of a contact named "Huahua", among others.

[0135] See Figure 5(d). The GUI is another search interface for the album application. If the mobile phone detects that the user has entered the keyword "huaduo" into the search box, it may search for photos related to "huaduo" on this mobile phone and other devices. The mobile phone has found a total of 890 photos related to "huaduo" on this mobile phone and other devices. The mobile phone has found 755 photos related to "huaduo" on this mobile phone. The mobile phone has found 105 photos related to "huaduo" on a Huawei M7 among other devices, and 130 photos related to "huaduo" on an Honor Vision among other devices.

[0136] Other devices in Figures 3(a) to 3(g) to 5(a) to 5(d) are on the same account as this mobile phone for illustrative purposes. In this embodiment of the present application, this mobile phone may further share data with other devices on different accounts. Figures 6(a) to 6(c) show another group of GUIs according to one embodiment of the present application.

[0137] As shown in Figure 6(a), the GUI is an alternative display interface for the album application. If the phone detects another device on the same or a different account within a pre-set distance, the caption "Other Devices" may be automatically displayed. The user can choose between "Local" and "Other Devices" for browsing. After detecting that the user has tapped the "Other Devices" control, the phone may display the GUI shown in Figure 6(b).

[0138] As shown in Figure 6(b), the GUI is another display interface for the album application. The display interface can display information about other devices (shown as "My Devices" in Figure 6(b)) within a pre-set distance and under the same account as this mobile phone, which are acquired by the mobile phone. Other devices include the Huawei M7, Honor Vision, and Huawei P30. In addition, the display interface can also display information about other devices (shown as "Other People's Devices" in Figure 6(b)) under other accounts in the same family group as the login account on the mobile phone. Other devices include the Xiaomi 9, a notebook computer (Macbook), and a tablet computer (MatePad Pro). The mobile phone can acquire information about the number of digital assets (e.g., photos) on other devices. As shown in Figure 6(b), under "My Devices," the number of photos stored on the Huawei M7 is 80, the number of photos stored on the Honor Vision is 120, and the number of photos stored on the Huawei P30 is 120. In "Other People's Devices," the number of photos stored on the Xiaomi 9 is 250, the number of photos stored on the Macbook is 220, and the number of photos stored on the MatePad Pro is 310. If the mobile phone detects that the user has tapped to view the album on the MatePad Pro, it may display the GUI shown in Figure 6(c).

[0139] In this embodiment of the present invention, it should be understood that the mobile phone may also share data with devices that are not logged into any account. For example, the mobile phone may automatically generate a QR code after opening an album. If the user wishes to view data on a device that is not logged into any account on the mobile phone, they may activate the QR code and scan it using the device that is not logged into any account. After successful authentication between the mobile phone and the device that is not logged into any account, the data may be shared between the mobile phone and the device that is not logged into any account.

[0140] Figure 7 is a diagram of another software structure of an electronic device according to one embodiment of the present application. Referring to Figure 7, the authentication procedure, service request procedure, service data synchronization procedure, and device discovery procedure between this electronic device and another device in this embodiment of the present application will be described below.

[0141] [Authentication Procedure]

[0142] An electronic device may automatically trigger an authentication procedure for a nearby device if it detects that the user is tapping a distributed application, such as an album application, music player application, file management application, or contacts application.

[0143] For example, an electronic device may, after detecting that a user has tapped an icon for a distributed application on the device's home screen, open the application and display its interface. Specifically, when the electronic device detects that a user has tapped an icon for an application on the device's home screen (e.g., an album application, a music player application, a file management application, or a contacts application), and this application is a distributed application, the application in the distributed application layer sends the identifier corresponding to this application (e.g., a process identifier (PID)) and the process name corresponding to this application to the device monitor in the service layer. The device monitor may determine that the APP has started by using the identifier and process name. For example, the electronic device may determine that the album application has started by determining the process identifier and process name of the album. The device monitor may generate a Bluetooth low energy (BLE) broadcast data packet by using the electronic device's online broadcast module. The broadcast data packet may carry the electronic device's device name and address (e.g., MAC address or IP address). The device monitor may broadcast the BLE broadcast data packet by using the Bluetooth broadcast / scan module in the communication protocol layer. Electronic devices can also receive BLE broadcast responses transmitted by other nearby devices in real time by using a Bluetooth broadcast / scan module. BLE broadcast responses may carry device name information of the other device.After receiving a broadcast response, the device monitor may use the name information of another device to determine whether the other device is a device in the same account or a device in a different account within the same family group. If the other device is a device in the same account, authentication between the electronic device and the other device may succeed directly. Alternatively, if the other device is a device in a different account within the same family group, authentication between the electronic device and the other device may succeed directly. A distributed application may listen to the device knowledge library. After discovering that information about another device has been added to the device knowledge library, the distributed application may display the corresponding information in its display interface.

[0144] For example, as shown in Figure 3(c), a mobile phone may automatically display "other devices" in its display interface after determining that another nearby device on the same account exists.

[0145] Furthermore, the device monitor may store information such as the device name, device type, device status, capability information, and address information of other devices in the device knowledge library.

[0146] In this embodiment of the present application, if the device monitor determines that the device name carried in the broadcast response does not represent another device in the same account or a device in another account within the same family group, it may further transmit information about the device name to the distributed response at the application layer. In addition, the distributed application may prompt the user to confirm that the device is not another device in the same account or a device in another account within the same family group. The distributed application may prompt the user to authenticate the device by scanning a QR code. For a specific authentication process using a QR code, please refer to the description in the above embodiments. For brevity, the details will not be described again here. In one embodiment, the user may send a QR code screenshot to a remote device, which scans the QR code to establish a network connection to the current device. In this way, the remote device can synchronize information about the digital asset with the current device.

[0147] In one embodiment, in addition to discovering nearby devices through short-range wireless communication, an electronic device may also discover other devices through far-range communication technology. For example, an electronic device may establish a network connection to a distant device by using far-range communication technology such as a server or a cellular network.

[0148] [Service Request Procedure]

[0149] After successful authentication between an electronic device and another device, a distributed application can invoke a distributed service request at the application layer to generate a corresponding service request.

[0150] For example, if an electronic device detects that a user has opened an album application, the album application may invoke a distributed service request to generate a thumbnail request. The distributed service request may then send the thumbnail request to a service processing engine (SPE) in the service layer.

[0151] In this embodiment of the present application, the SPE is a logical processing unit that may be configured to perform service proxy functions, analyze and process service requests, and select appropriate devices / hardware / services for an application. After receiving a corresponding service request, the SPE may select an appropriate device for the service request by using a device knowledge library. For example, the device knowledge library stores information about devices A, B, and C. The SPE may first obtain status information for devices A, B, and C. If the SPE finds that device A is offline and devices B and C are online, it may determine that devices B and C are the appropriate devices.

[0152] The SPE can forward service requests and address information from other devices (devices B and C) to the DataBus. The DataBus delivers the service requests and address information to the communication layer downlink module in the communication protocol layer. The communication layer downlink module can forward service requests to other devices based on the address information of the other devices.

[0153] Accordingly, after receiving the service request, the other device parses the request and sends it to the SPE within the other device. The SPE in the other device acts as the agent for the local service and returns the service response and corresponding data to the electronic device. In this case, the service request process is completed.

[0154] An electronic device may, after receiving responses and data transmitted by another device, store the data in a data storage area at the service layer and further transmit the corresponding data to a distributed application at the application layer. As a result, the user can view the data on the other device using a display interface.

[0155] For example, as shown in Figure 3(d), if the mobile phone detects that the user has tapped “Other Devices,” it may trigger the aforementioned service request procedure and request picture metadata from other devices (Huawei M7, Honor Vision, and Huawei P30). After receiving the metadata transmitted by the other device, the electronic device may use its display interface to display the number of photos in the album on the other device.

[0156] For example, as shown in Figure 3(g), the aforementioned service request procedure may be triggered after the mobile phone detects that the user has tapped the thumbnail of the photo 311, and the mobile phone may request data of the photo 311 with a pre-set screen resolution from the Huawei M7.

[0157] For example, as shown in Figure 3(g), the aforementioned service request procedure may be triggered after the mobile phone detects that the user has tapped "Save locally," and the mobile phone may request the original data of photo 311 from the Huawei M7.

[0158] [Service Data Synchronization Procedure]

[0159] Before an electronic device and another device can share data with each other, the electronic device must first establish a data transmission channel (DataBus PIPE) with the other device. The other device can establish the data transmission channel by calling the DataBus PIPE establishment interface based on the service request after receiving a service request from the electronic device. Once the data transmission channel is established, the other device can share data stored by the other device with the electronic device.

[0160] In this embodiment of the present application, the data synchronization procedure between the first electronic device and the second electronic device may include initial synchronization and incremental synchronization. Initial synchronization is a synchronization triggered when the first electronic device and the second electronic device first establish a data transmission channel and the first electronic device synchronizes its data to the second electronic device, or the second electronic device synchronizes its data to the second electronic device. Incremental synchronization is a synchronization triggered when the data on the first electronic device and the data on the second electronic device change. For example, if the data on the first electronic device changes (e.g., some photos or videos are added to the first electronic device), the first electronic device may synchronize its data to the second electronic device.

[0161] It should be understood that, if the network connection between the first and second electronic devices is not interrupted, or if the inter-device connection is not interrupted, a data transmission channel between the first and second electronic devices can exist throughout the entire period. If data needs to be synchronized, the data can be synchronized directly through the data transmission channel.

[0162] [Device detection]

[0163] In the authentication process, electronic devices need to scan information transmitted by other nearby devices to determine the appropriate nearby device. However, some devices may go offline after a certain period of time, and therefore, the electronic device needs to detect another device.

[0164] For example, an electronic device may periodically transmit BLE broadcast data packets. If the electronic device receives a broadcast response from another device within a predetermined time period, it may determine that the other device is online after transmitting the BLE broadcast data packet. Conversely, if the electronic device does not receive a broadcast response within a predetermined time period, it may determine that the other device is offline.

[0165] In one embodiment, an electronic device does not find device B (device B and other electronic devices in the same account) during the initial scan, but finds device B in a subsequent scan process. In this case, the electronic device may store information about device B in the device knowledge library. In addition, the device monitor may further send updated device information to a distributed application to display information about device B on the electronic device's display interface.

[0166] Distributed applications can listen to information in the device knowledge library. If device information in the device knowledge library changes, the distributed application can update the device information in real time using a display interface. In addition, when an SPE sends a service request to the DataBus, it can also send an updated device address to the DataBus based on the updated device information.

[0167] The following describes a data sharing process between device A and device B according to one embodiment of the present invention, with reference to Figures 8(a) and 8(b). This process includes the following steps.

[0168] 101: When an electronic device detects user interaction on the display interface of a distributed application, the distributed application initiates a service request by calling the software development kit (SDK) for the distributed service. The SDK sends the service request to the SPE at the service layer. The specific content of the service request may be determined based on the user interaction.

[0169] For example, as shown in Figure 3(c), after an electronic device detects a user tapping another device, the SDK sends a service request to the SPE for picture metadata and thumbnails.

[0170] In another example, as shown in Figure 3(f), the mobile phone may display more photo thumbnails downwards after detecting an upward swipe gesture by the user on the display. If the mobile phone has previously requested picture metadata and thumbnails from the Huawei M7, it may only retrieve 200 photo thumbnails. When the mobile phone scrolls down the photo thumbnails, and it determines that it is about to scroll to the 200th photo thumbnail, the SDK may automatically initiate another service request to the Huawei M7 for the photo thumbnails. This can ensure continuity when the user views the photo thumbnails.

[0171] In another example, as shown in Figure 3(f), the mobile phone may, after detecting a user tap on the display to obtain a photo 311, request data from the Huawei M7 for a photo 311 with a pre-set screen resolution (for example, a photo with a pixel value of 1080 × 1920).

[0172] In another example, as shown in Figure 3(g), after the mobile phone detects that the user has tapped "Save locally," the mobile phone may request the original data of photo 311 from the Huawei M7.

[0173] 102: The SPE uses the data bus to forward the service request and the address of device B to the communication protocol layer.

[0174] 103: The communication protocol layer sends a service request to device B based on the address of device B.

[0175] 104: After receiving the service request, the communication protocol layer of device B forwards the service request to the SPE of device B.

[0176] 105: Device B's SPE continues to forward service requests to the search service.

[0177] 106: After the search service obtains a service request, it may analyze the service request and then search the data index storage area of ​​device B to find the corresponding data index.

[0178] For example, a search service on device B may, after determining that a service request is being used to request picture metadata and thumbnails, search the data index storage area to find the corresponding index of the photographs stored on device B. The photograph index as used herein may be an index established after device B has classified the photographs stored on device B. For example, device B may classify the photographs stored on device B based on information such as time, task, location, and label. The photograph index stored on device B may also indicate the classification information for each photograph.

[0179] 107: The search service searches for data in the data storage area of ​​device B based on the service request.

[0180] For example, a search service on device B may, after determining that a service request is being used to request picture metadata and thumbnails, search its data storage for information about the picture metadata and thumbnails stored on device B. Device B's data storage may contain local data and data from remote device A. During the search, device B may search the local data to retrieve the corresponding data.

[0181] For example, Table 1 shows picture metadata. [Table 1] [Table 1]

[0182] Please understand that the picture metadata listed in Table 1 is merely an example and is not limited to this embodiment of the present application.

[0183] It should be further understood that picture metadata can be retrieved using the original picture data stored in the electronic device's memory. Internal memory is different from the data storage area in Figures 8(a) and 8(b). Internal memory stores the original picture data. The amount of data in the original data is large. Picture metadata and thumbnails stored in the data storage area are retrieved using the original picture data. The amount of data in the metadata and thumbnails is small.

[0184] As shown in Figure 3(c), when the SDK sends a service request to the SPE for picture metadata and thumbnails, the data that the Huawei M7 synchronizes to the mobile phone is actually picture metadata and thumbnails.

[0185] As shown in Figure 3(f), after detecting an upward swipe operation by the user on the display, the mobile phone may request more thumbnails from the Huawei M7 if it has set it to display all previously stored thumbnails.

[0186] As shown in Figure 3(g), the mobile phone may request the original data of photo 311 from the Huawei M7 after detecting the user's tap of “Save Locally”.

[0187] In this embodiment of the present application, when the current device accesses and manages digital assets on another device, it does not directly copy the original data on the other device to the current device. This can help improve the user's browsing speed and save storage space on the electronic device.

[0188] 108: The search service of device B forwards the response to the service request and the found data to the communication protocol layer of device B.

[0189] 109: Device B's communication protocol layer sends the response and data to Device A's communication protocol layer.

[0190] For example, a picture can be used as an example. Device B may send picture metadata and thumbnails stored in Device B to Device A. For example, if Device B has 1,000 pictures stored, it may send metadata information for 1,000 pictures and thumbnail information for 200 pictures to Device A.

[0191] 110: The communication protocol layer of device A sends the received response and data to the search service of device A.

[0192] 111: The search service of device A stores the received data in the data storage area of ​​device A.

[0193] As shown in Figures 8(a) and 8(b), the data storage area of ​​device A includes local data of device A and data of remote device B. After receiving data transmitted by device B, device A may store the data in the data of remote device B.

[0194] In one embodiment, after receiving metadata transmitted by device B, device A may establish a data index based on the information in the metadata and store the metadata index of device B in the data index storage area of ​​device A.

[0195] For example, pictures can be used as an example. Device B stores 1,000 pictures. In this case, device B can send metadata for the 1,000 pictures to device A. The metadata includes the time the picture was created, the location where the picture was created, and the picture's category label, etc. The structure of the metadata may be shown in Table 2. [Table 2] [Table 2]

[0196] After receiving 1,000 pieces of metadata, device B may establish an index of 1,000 pieces of metadata based on the content of the 1,000 pieces of metadata, and store the established index in remote device B in the data index storage area of ​​device A.

[0197] For example, as shown in Table 3, device A may establish an index table of 1,000 pictures within the data index storage area of ​​remote device B within the data index storage area of ​​device A. [Table 3] [Table 3]

[0198] It should be understood that the classification schemes shown in Tables 2 and 3 are merely examples. In this embodiment of the present application, the index of received metadata may alternatively be established based on a different classification scheme. For example, the location category may further include Category 3. Category 3 may include territorial information for each city, for example, Nanjing may be further divided into Huadu District and Yuhuatai District of Nanjing, and Xi'an may be further divided into Beilin District and Yanta District of Xi'an.

[0199] In this embodiment of the present application, the current device can receive metadata transmitted by another device and establish a corresponding index based on the information in the metadata. Thus, when a user searches the current device for data that is stored locally and data stored on another device, the search results are displayed to the user in a simple and quick manner.

[0200] For example, as shown in Figure 5(c), a mobile phone may display categorized results obtained based on the keyword "hua" after the user enters the keyword "hua" into the search box. Search results for "hua" include "Huadu District" and "Yuhuatai District," categorized based on location, as well as "Sister Xiaohua" and "Huahua," categorized based on the names of the people photographed.

[0201] For example, as shown in Figure 5(d), a mobile phone may display categorized results obtained based on the keyword "huaduo" after the user enters the keyword "huaduo" into the search box. The mobile phone may display eight photos taken in 2018 related to "huaduo" (and may also display photos taken in 2019 and 2020 related to "huaduo," which are not shown in this figure), and may also display the number of photos found on this mobile phone related to "huaduo" and the number of photo data found on other devices related to "huaduo."

[0202] 112: Device A's search service sends data to the SDK in the application layer, and Device A's user interface displays the data to the user.

[0203] For example, as shown in Figure 3(d), a search service may send information about the number of pictures on the Huawei M7, Honor Vision, and Huawei P30 to the SDK. The mobile phones can also display the number of pictures on each device through their display interface.

[0204] In this application, the current device may store metadata information transmitted by another device in its data storage area. For example, a Huawei M7 may transmit 80 pieces of metadata information corresponding to 80 pictures stored in the Huawei M7 to a mobile phone. In this case, a search service may collect statistics on the number of metadata pieces received. The statistical result of the number of metadata pieces is the number of pictures stored in the Huawei M7.

[0205] For example, as shown in Figure 3(e), after the mobile phone detects that the user has tapped folder 305, the search service sends information about the thumbnails in folder 305 on the Huawei M7 to the SDK, and the display may show the GUI shown in Figure 3(f).

[0206] 201: If the data stored on device B changes, the application on device B calls the SDK to indicate to the search service that the shared data has changed.

[0207] For example, after a user takes several more photos using device B, the SDK may be triggered to indicate to a searchable service that the photo data in the album application has changed.

[0208] 202: The search service establishes a new shared data index in the data index storage area of ​​device B.

[0209] For example, device B updates the index information stored in its data index storage area based on the label information of a newly added photograph.

[0210] 203: The search service updates the information in the data storage area of ​​device B.

[0211] For example, device B adds corresponding metadata and thumbnail information to its data storage area based on the newly added photo.

[0212] Next, device B may transmit the updated data information to the communication protocol layer of device A by using the communication protocol layer. The search service of device A updates the data of remote device B in the data storage area of ​​device A. After the update is complete, the search service may further present the updated data to the SDK in the application layer, and the user interface of device A displays the updated data of device B to the user.

[0213] Figure 9 is a schematic diagram of a distributed browsing, searching, and management of pictures and videos according to one embodiment of the present invention.

[0214] As shown in Figure 9, the internal memories of devices A, B, and C store the original data for their respective pictures and videos. Based on the original data stored in their internal memories, devices A, B, and C can independently determine metadata, data indexes, and thumbnail information in the data storage area at the service layer.

[0215] For example, after a user takes a photo in Huadu District, Nanjing using their mobile phone, the original data size of the photo is 8MB, and the mobile phone can store the original photo data in its internal memory. In addition, the mobile phone can also store in its data memory the device name of the device that took the photo (e.g., Huawei M7), the file name (e.g., the picture suffix .JPG), the absolute path of the file (e.g., the physical path of the photo in internal memory), the file size (e.g., the size of the photo is 8MB), the time the file was added to the device (e.g., 10:00 AM on February 14, 2019), the file width (e.g., 500 pixels), the file height (e.g., 500 pixels), and the file type (e.g., picture). The mobile phone can also store the photo index in its data index memory. For example, the mobile phone can automatically identify the information in the photo and classify the photo (or add a corresponding label to the photo) based on the information in the photo. If the metadata of a photo is synchronized from the Huawei M7 to the current device, the current device can establish an index of various types of data within the photo (e.g., time, location, and label information) based on that index (for example, by using Luence) to facilitate subsequent searches. The mobile phone can store thumbnails corresponding to the photos in a thumbnail database.

[0216] Please understand that the data storage area and thumbnail database in Figure 9 may be located in the data storage area shown in Figures 8(a) and 8(b). The data index storage area in Figure 9 is the data index storage area in Figure 9.

[0217] In one embodiment, the data storage area, data index storage area, and thumbnail database shown in Figure 9 may be further separated according to a two-dimensional {Group ID, App ID}, and the mobile phone may control the corresponding access permissions.

[0218] For example, Table 4 shows the data storage structure. [Table 4] [Table 4]

[0219] For example, music metadata may include the file name and file size of the music, as well as information used for other service categories and searches, such as the music author, the name and style of the album to which the music belongs.

[0220] Figures 10(a) to 10(e)-3 show another group of mobile phone GUIs.

[0221] Please refer to Figure 10(a). The GUI is the home screen 1001 of the mobile phone. After detecting that the user has tapped the album application (APP) icon 1002 on the home screen 1001, the mobile phone may open the album application and display the GUI shown in Figure 10(b).

[0222] Please refer to Figure 10(b). The GUI is the display interface for the album application. The display interface may show that the mobile phone currently has 4,278 photos and 134 videos stored. 3,177 photos were taken by the camera, 12 photos were taken through screenshots and screen recordings, 25 photos are in favorites, and 3 photos are in shared albums. In addition, the mobile phone also automatically searches for nearby devices on the same account or another account associated with this account when it detects that the user has opened the album application.

[0223] Please refer to Figure 10(c). The GUI is an alternative display interface for the album application. If the mobile phone finds another device in User A's account or an account associated with User A's account within a pre-set distance, the subtitles "Other Devices" and "Add Device" may be automatically displayed. The user can select "Local" and "Other Devices" for browsing. If the mobile phone detects that the user has tapped "Other Devices," it may display device information for the other device in User A's account and information about the other device in the account associated with User A's account. After detecting that the user has tapped the "Add Device" control 1003, the mobile phone may display the GUI shown in Figure 10(d).

[0224] In this embodiment of the present application, the account associated with user A's account may be an account within the same family group as user A's account, or an account authenticated by user A's account.

[0225] Refer to Figure 10(d). The GUI is a display interface for adding a data synchronization device. If the mobile phone detects that the user has tapped “Add Device”, a prompt box 1004 may pop up on the screen. The prompt box 1004 contains the text prompt “Please scan the QR code for data synchronization using your device.” The user can implement data synchronization between the mobile phone and the device that is not logged into any account by scanning the QR code using a device that is not logged into any account (or a device that is logged into an account not associated with user A's account).

[0226] In one embodiment, in addition to displaying a QR code, the display interface for adding a data synchronization device may further display some group information about social software such as a WeChat group or address book. The user may also determine the device to be added by selecting the corresponding social software group. In this embodiment of the present application, the other device and the added device may be a device close to the current device or a device for long-distance communication. For example, the user may send a screenshot of the QR code information to another device far away from the user. After receiving the screenshot, the other device scans this QR code to establish a network connection to the current device, thereby sharing the data of the other device with the current device.

[0227] Refer to Figures 10(e)-1 to 10(e)-3. After the mobile phone detects that a QR code has been scanned by a device (e.g., a Huawei Mate 30) that is not logged into any account, it may display in "Add Device" that a total of 100 pictures exist on the Huawei Mate 30.

[0228] Please refer to the previous explanation for the process by which the current device detects that another electronic device (e.g., a Huawei Mate 30) has scanned a QR code and is performing data synchronization between the current device and the other electronic device. For brevity, we will not go into detail again here.

[0229] Figure 11 is a schematic flowchart of a data sharing method 1100 according to one embodiment of the present invention. As shown in Figure 11, this method is performed by a first electronic device and a second electronic device. This method includes the following steps.

[0230] S1101: The first electronic device stores one or more files.

[0231] For example, if the first application is an album application, the first file is a video or a picture. If the first electronic device detects that the user is taking a video or a picture by using the camera, it may store the video or picture locally. For example, the first electronic device may store the video or picture on its external storage card.

[0232] For example, if the first application is a music application, the first file may be music. If the first electronic device detects that a user is downloading a single piece of music, it may retrieve this piece of music from the server and store it locally. For example, the first electronic device may store the music on its external storage card.

[0233] S1102: The first electronic device generates metadata for each of one or more files.

[0234] For example, suppose an album application in a first electronic device contains 80 pictures. In this case, the first electronic device may generate 80 pieces of metadata for the 80 pictures, each piece of metadata may include information such as the picture name, picture size, creation event, and creation location of the picture.

[0235] For example, suppose a music application on a first electronic device contains 10 music tracks. In this case, the first electronic device may generate metadata corresponding to the 10 music tracks, each metadata track may include information such as the title of the music track, the size of the music track, the author of the music track, and the album to which the music track belongs.

[0236] Optionally, the first electronic device may further establish an index for each file based on information about the generated metadata. An album application is used as an example. For the process of establishing an index for each picture, please refer to the processes in Tables 2 and 3. For brevity, the details will not be explained again here.

[0237] Optionally, if the file is a picture, the first electronic device may further generate thumbnails based on each of one or more pictures in the album application.

[0238] In this embodiment of the present application, it should be understood that metadata generated by the first electronic device may be stored in a storage area for metadata (for example, in local data within the data storage area of ​​device B in Figures 8(a) and 8(b)). A data index established for metadata may be stored in a data index storage area (for example, in local data index within the data index storage area of ​​device B in Figures 8(a) and 8(b)).

[0239] S1103: The second electronic device transmits a broadcast message. The broadcast message is used to search for electronic devices within a predetermined distance, and the broadcast message may include the device name and address information of the second electronic device.

[0240] For example, a broadcast message is a Bluetooth low energy BLE broadcast message.

[0241] In this embodiment of the present application, the second electronic device may periodically send broadcast messages, send broadcast messages when the second electronic device is idle, or send broadcast messages when it detects that a user has started a particular application.

[0242] S1104: The first electronic device sends a response message to the second electronic device based on the address information. The response message includes the device name of the first electronic device.

[0243] S1105: The second electronic device determines, based on the response message, that the first electronic device is an electronic device within a predetermined distance, and that the login account on the first electronic device is associated with the login account on the second electronic device.

[0244] In one embodiment, the second electronic device may determine whether the distance between the first electronic device and the second electronic device is within a preset distance based on the signal strength or signal quality of the response message transmitted by the first electronic device.

[0245] In this embodiment of the present application, the signal strength and signal quality (hereinafter, a long-term evolution (LTE) system is used as an example for illustrative purposes) are as follows: (1) Reference signal received power (RSRP), (2) Received signal strength indicator (RSSI) (3) Reference signal received quality (RSRQ), and (4) Signal-to-interference-to-noise ratio (SINR) This may include one or more of the following parameters.

[0246] It should be understood that the above uses only one example in which the distance between the second electronic device and the first electronic device is determined by the second electronic device based on signal strength or signal quality. The distance between the second electronic device and the first electronic device may be determined by alternative means, and this is not limited to the present embodiment of the application.

[0247] Optionally, the association of a login account on a first electronic device with a login account on a second electronic device includes the following: the login account on the first electronic device is the same as the login account on the second electronic device; the login account on the first electronic device and the login account on the second electronic device are in the same family group; or the login account on the first electronic device is an account authenticated by the login account on the second electronic device.

[0248] For example, a second electronic device may store information about the device name of another electronic device in the second electronic device's login account. In this case, the second electronic device may determine that the first electronic device is a device in the same account based on the device name in the response message.

[0249] For example, the second electronic device may further store the device name of a device in another account within the same family group as the login account for the second electronic device. In this case, the second electronic device may determine, based on the device name in the response message, that the first electronic device is a device in the same account or a device in another account within this family group.

[0250] In this embodiment of the present application, if the first electronic device and the second electronic device are devices in the same account or devices in different accounts within this family group, the first electronic device and the second electronic device can directly trust each other by using a trust ring.

[0251] S1106: The second electronic device sends a request message to the first electronic device. The request message is used to request metadata for one or more files of the first application.

[0252] In one embodiment, the second electronic device may send a request message to the first electronic device after determining that the first electronic device is within a predetermined distance and that the login account on the first electronic device is associated with the login account on the second electronic device.

[0253] In one embodiment, the second electronic device may, alternatively, send a request message to the first electronic device if it detects that the user has opened the first application.

[0254] In one embodiment, the second electronic device may alternatively send multiple request messages to the first electronic device. Each request message is used to request metadata within a different application.

[0255] S1107: The first electronic device transmits metadata of one or more files of the first application to the second electronic device.

[0256] For example, a second electronic device may store metadata for one or more files transmitted by the first electronic device in its data storage area (for example, in local data within the data storage area of ​​device A in Figures 8(a) and 8(b)).

[0257] In this embodiment of the present application, a second electronic device may determine a first electronic device within a predetermined distance associated with a login account on the second electronic device, and the second electronic device may request metadata of application files from the first electronic device. This helps users to quickly view the status of digital assets stored on the first electronic device by using the second electronic device, and satisfies user requirements for performing centralized management of digital assets distributed across various devices. This improves the user experience.

[0258] In addition, the first electronic device shares metadata corresponding to each file with the second electronic device, rather than the original data of each file. In this case, during the data sharing process, the user can also quickly browse the status of digital assets on the other device, and more storage space is saved on the electronic device.

[0259] In one embodiment, the second electronic device may generate a corresponding metadata index based on the metadata received from one or more files transmitted by the first electronic device, and store the corresponding metadata index in the data index storage area of ​​the second electronic device (for example, in the data index of remote device B within the data index storage area of ​​device A in Figures 8(a) and 8(b)).

[0260] In this embodiment of the present application, the second electronic device may, after retrieving the metadata of each file stored in the first electronic device, establish an index of each file based on the metadata. In addition, the second electronic device may also establish an index of the locally stored metadata of each file. This is convenient for the user to quickly find a file they wish to view if they search for it later. This helps to improve the user experience.

[0261] Optionally, if the first application is an album application, in addition to sending metadata for one or more pictures to the second electronic device, the first electronic device may further send thumbnails of at least some of the one or more pictures to the second electronic device. For example, if the first electronic device stores 1,000 pictures, the first electronic device may further carry 200 picture thumbnails using a response message.

[0262] In this embodiment of the present application, with respect to the album application, the second electronic device may further request thumbnails of one or more pictures in the album application on the first electronic device from the first electronic device. In this way, after the user taps a folder, the second electronic device displays at least a portion of the thumbnails of one or more pictures to the user in a timely manner.

[0263] As shown in Figure 3(f), the mobile phone may display thumbnails in a scrolling manner after detecting the user's upward swipe gesture. If the user is trying to view the 200th thumbnail (for example, if the user has already viewed the 150th thumbnail), the mobile phone may be triggered to request more thumbnails from the Huawei M7 again. This ensures that the phone does not freeze when the user is viewing thumbnails.

[0264] S1108: The second electronic device uses a display to show the folder, the device name of the second electronic device, and the number of files.

[0265] For example, as shown in Figure 3(d), the mobile phone may display folder 304, the device name "Huawei M7", and the number of files "80" on its interface.

[0266] It should be understood that the mobile phone can receive 80 metadata from Huawei M7 in S1107. In this case, the "80" displayed on the interface by the mobile phone indicates that the mobile phone has determined that Huawei M7 stores 80 pictures.

[0267] When the mobile phone detects an operation by the user to tap folder 304, it can display the interface in FIG. 3(e) or FIG. 3(f). When the interface in FIG. 3(f) is directly displayed, the mobile phone can display a plurality of thumbnails on the interface. In S1107, Huawei M7 may also send a plurality of thumbnails to the mobile phone. Therefore, the interface of the mobile phone may actually be directly switched from the interface in FIG. 3(d) to the interface in FIG. 3(f) without freezing for the user.

[0268] Optionally, after detecting an operation by the user to tap a thumbnail, the second electronic device may request a picture with a preset screen resolution from the first electronic device.

[0269] As shown in FIG. 3(f), after the mobile phone detects an operation by the user to tap thumbnail 311, it can display the picture shown in FIG. 3(g). This picture is not actually the original picture. A picture with a preset screen resolution occupies less storage space compared to the original picture. As a result, the user's browsing speed can be relatively high. The GUI shown in FIG. 3(g) may further include information such as the shooting time and shooting position of the picture. As a result, the user can further know the details about the picture.

[0270] For example, the space occupied by a thumbnail is about 20KB, the space occupied by a picture with a preset screen resolution is about 200KB, and the space occupied by the original data of the picture is about 5MB to 20MB.

[0271] As shown in Figure 3(f), after detecting the user's tap of "Save Locally," the mobile phone may request the original picture data from the Huawei M7 and store the original data sent by the Huawei M7 locally.

[0272] In this embodiment of the present application, the second electronic device requests the original data of the picture from the first electronic device only if the user wishes to locally store the picture on the first electronic device to the second electronic device. Thus, in the process of the second electronic device displaying the picture from the first electronic device to the user, the second electronic device does not need to store the original data of each picture stored on the first electronic device. As a result, the user can quickly browse the status of digital assets on another device, and more storage space is saved on the electronic device.

[0273] In this embodiment of the present application, metadata is file information including the file name and file size. A thumbnail is a picture obtained after the picture has been reduced in size according to a specified percentage. A thumbnail occupies a very small amount of memory space. A picture with a preset screen resolution and the original data of the picture are both pictures, but they occupy different memory spaces. Furthermore, the space occupied by a picture with a preset screen resolution is less than the space occupied by the original data of the picture.

[0274] Optionally, the second electronic device may, after detecting that the user has entered keywords into the search box of the first application, display search results based on the keywords, the local metadata index, and the metadata index received from the first electronic device.

[0275] For example, in Figure 5(c), after detecting that the user has entered the keyword "hua" into the search box, the mobile phone may display search results for the keyword "hua" based on an index of locally stored metadata and an index of metadata transmitted by another device. The search results include pictures taken in "Huadu District" and "Yuhuatai District," and pictures with usernames "Sister Xiaohua" and "Huahua."

[0276] For example, in Figure 5(d), after detecting the keyword "huaduo" entered by the user into the search box, the mobile phone may display search results for the keyword "huaduo" based on an index of locally stored metadata and an index of metadata transmitted by another device. The search results include pictures taken in 2018 related to "huaduo" and the number of pictures related to "huaduo" on the mobile phone and other devices.

[0277] S1109: The first electronic device detects that a file in the first application has changed.

[0278] S1110: The first electronic device sends metadata of one or more updated files to the second electronic device.

[0279] For example, pictures can be used as an example. If the Huawei M7 detects that the user has taken two pictures using the camera, the number of pictures stored in the Huawei M7 will increase from 80 to 82. In this case, the Huawei M7 may send the updated metadata to the current phone. For example, the Huawei M7 may send the metadata of the two newly added pictures to the current phone, or it may send the metadata of the two newly added pictures and their corresponding thumbnails.

[0280] If the number of files on the first electronic device decreases, the first electronic device may send the metadata of all files to the second electronic device after reduction and instruct the second electronic device to overwrite the previous data with the newly sent data from the first electronic device. Alternatively, the first electronic device may indicate which files have been reduced. As a result, the second electronic device deletes the corresponding metadata for the files.

[0281] In this embodiment of the present application, if metadata in a shared file stored on the first electronic device changes, for example, if the first electronic device detects that a user has added some files to the shared file or deleted some files from the shared file, the first electronic device may send the updated metadata to the second electronic device. In this way, the second electronic device can update the metadata of the shared file on the first electronic device in a timely manner and display the change status of the files stored on the first electronic device to the user.

[0282] Those skilled in the art will recognize, in combination with the examples described in the embodiments disclosed herein, that the unit and algorithmic stages can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software will depend on the specific application and the design constraints of the technical solution. Those skilled in the art may implement the described functions for specific applications using different methods, but such implementations should not be considered beyond the scope of the Application.

[0283] For the purpose of a simple and straightforward explanation, it will be readily apparent to those skilled in the art that the detailed operating processes of the aforementioned systems, devices, and units can be described by referring to the corresponding processes in the embodiments of the methods described above. Further details will not be described here.

[0284] In some embodiments provided herein, it should be understood that the disclosed systems, apparatus, and methods may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into multiple units is merely a logical functional division, and other divisions may occur in actual implementation. For example, multiple units or components may be combined or integrated into another system, and some functions may be ignored or not performed. In addition, the mutual coupling, direct coupling, or communication connection shown or described may be implemented through several interfaces. Indirect coupling or communication connection between apparatus or units may be implemented in electronic, mechanical, or other forms.

[0285] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, and may be located in one place or distributed across multiple network units. Some or all of these units may be selected based on the actual requirements for achieving the objectives of the solution of the embodiment.

[0286] In addition, the functional units in the embodiments of the present invention may be integrated into a single processing unit, each of these units may exist physically independently, or two or more units may be integrated into a single unit.

[0287] When the function is implemented in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of the present application are essentially, or the parts that contribute to the prior art, or some of these technical solutions, may be implemented in the form of software products. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or some of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes various media capable of storing program codes, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0288] The foregoing description is merely a specific implementation example of the present application and is not intended to limit the protection scope of the present application. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims. [Other conceivable items] (Item 1) A system comprising a first electronic device and a second electronic device, The first electronic device is configured to establish a network connection to the second electronic device for transmitting data, The first electronic device is further configured to request a shared file associated with the target file from the second electronic device when detecting an operation of a user searching for the target file, The second electronic device is further configured to transmit the shared file to the first electronic device, The first electronic device is further configured to display a first interface that includes an identifier for the shared file of the first electronic device and an identifier for the shared file of the second electronic device. system. (Item 2) The shared file includes the original data or metadata, and the metadata is attribute description information for each file within the shared file, as described in item 1. (Item 3) The system described in item 1 or 2, wherein the first interface further includes the device name of the second electronic device. (Item 4) The system according to any one of items 1 to 3, wherein the establishment of a network connection between the first electronic device and the second electronic device comprises the first electronic device communicating with the second electronic device via a short-range wireless connection, or the first electronic device communicating with the second electronic device via a long-range wireless connection. (Item 5) The aforementioned target file is a multimedia file, The first electronic device is further configured to request thumbnails of one or more multimedia files stored in the second electronic device from the second electronic device. The second electronic device is further configured to transmit the thumbnails of the one or more multimedia files to the first electronic device. A system described in any one of items 1 through 4. (Item 6) The first electronic device is further configured to request a first multimedia file corresponding to the first thumbnail from the second electronic device when it detects an operation by the user to tap a first thumbnail, wherein the thumbnails of one or more multimedia files include the first thumbnail, and the first multimedia file is a multimedia file having a preset screen resolution. The second electronic device is further configured to transmit the first multimedia file to the first electronic device. The first electronic device is further configured to display a second interface, the second interface containing the first multimedia file, The system described in item 5. (Item 7) The aforementioned second interface further includes a first control for local storage, The first electronic device is further configured to request a second multimedia file corresponding to the first thumbnail from the second electronic device when it detects an operation by the user to tap the first control, the second multimedia file being the original data of the multimedia file corresponding to the thumbnail. The second electronic device is further configured to transmit the second multimedia file to the first electronic device. The first electronic device is further configured to store the second multimedia file in the first electronic device. The system described in item 6. (Item 8) The shared file includes the metadata, The first electronic device is further configured to establish an index of the metadata for each file based on the metadata of each file after receiving the metadata transmitted by the second electronic device for each file. The first electronic device is further configured to display search results based on keywords entered by the user and the index of the metadata. A system described in any one of items 1 through 7. (Item 9) The second electronic device is further configured to send the updated shared file to the first electronic device when it detects that the shared file has been updated. The first electronic device is configured to receive the updated shared file transmitted by the second electronic device. A system described in any one of items 1 through 8. (Item 10) The first electronic device is further configured to determine, before establishing the network connection to the second electronic device, that a login account on the first electronic device is associated with a login account on the second electronic device. A system described in any one of items 1 through 9. (Item 11) A data sharing method applicable to electronic devices, The step of establishing a network connection between the aforementioned electronic device and another electronic device, wherein the network connection is used to transmit data. When the electronic device detects an operation by the user to search for a target file, the electronic device requests the shared file associated with the target file from the other electronic device. The electronic device receives the shared file transmitted by the other electronic device, A step in which the electronic device displays a first interface, wherein the first interface includes an identifier for the shared file of the electronic device and an identifier for the shared file of another electronic device. A method that includes [a certain feature]. (Item 12) The method according to item 11, wherein the shared file includes original data or metadata, and the metadata is attribute description information for each file in the shared file. (Item 13) The method according to item 11 or 12, wherein the first interface further includes the device name of the other electronic device. (Item 14) The method according to any one of items 11 to 13, wherein the step of the electronic device establishing a network connection to another electronic device comprises the step of the electronic device communicating with the other electronic device via a short-range wireless connection, or the step of the electronic device communicating with the other electronic device via a long-range wireless connection. (Item 15) The aforementioned target file is a multimedia file, and the aforementioned method is The electronic device requests thumbnails of one or more multimedia files stored in the other electronic device from the other electronic device, The electronic device receives the thumbnail of one or more multimedia files transmitted by the other electronic device. A method according to any one of items 11 to 14, further comprising: (Item 16) When the electronic device detects that the user has tapped a first thumbnail, the electronic device requests a first multimedia file corresponding to the first thumbnail from another electronic device, wherein the thumbnails of one or more multimedia files include the first thumbnail, and the first multimedia file is a multimedia file having a preset screen resolution. The electronic device receives the first multimedia file transmitted by the other electronic device, The electronic device displays a second interface, the second interface includes the first multimedia file, and the display step is as follows: The method described in item 15, further comprising: (Item 17) The second interface further includes a first control for local storage, and the method is When the electronic device detects that the user has tapped the first control, the electronic device requests a second multimedia file corresponding to the first thumbnail from the other electronic device, wherein the second multimedia file is the original data of the multimedia file corresponding to the thumbnail, and the electronic device requests a second multimedia file corresponding to the first thumbnail from the other electronic device, and the electronic device requests a second multimedia file corresponding to the first thumbnail. The electronic device receives the second multimedia file transmitted by the other electronic device, The electronic device stores the second multimedia file in the electronic device. The method described in item 16, further comprising: (Item 18) The shared file includes the metadata, and the method is After the electronic device receives the metadata for each file transmitted by the other electronic device, the electronic device establishes an index of the metadata for each file based on the metadata for each file. The electronic device performs the steps of displaying search results based on keywords entered by the user and the index of the metadata. A method according to any one of items 11 to 17, further comprising: (Item 19) The method according to any one of items 11 to 18, further comprising the step of the electronic device receiving an updated shared file transmitted by the other electronic device. (Item 20) Before establishing the network connection to the other electronic device, the step of determining that the login account on the electronic device is associated with the login account on the other electronic device. A method of any one of items 11 to 19, further comprising: (Item 21) The display and One or more processors, One or more memory units and An electronic device having, The one or more memory stores one or more computer programs, and the one or more computer programs include instructions, and when the instructions are executed by the one or more processors, the electronic device The stage of establishing a network connection to another electronic device, wherein the network connection is used to transmit data, and the stage of establishing the connection, When an operation by the user to search for a target file is detected, the steps include requesting the shared file associated with the target file from the other electronic device, The step of receiving the shared file transmitted by the aforementioned other electronic device, A step of displaying a first interface, wherein the first interface includes an identifier for a shared file of the electronic device and an identifier for a shared file of another electronic device. An electronic device that makes it possible to perform certain actions. (Item 22) The shared file includes the original data or metadata, and the metadata is attribute description information for each file within the shared file, as described in item 21. (Item 23) The first interface further includes the device name of the other electronic device, as described in item 21 or 22. (Item 24) The electronic device according to any one of items 21 to 23, wherein the electronic device establishing the network connection to the other electronic device comprises the electronic device communicating with the other electronic device via a short-range wireless connection, or the electronic device communicating with the other electronic device via a long-range wireless connection. (Item 25) The target file is a multimedia file, and when the instruction is executed by the one or more processors, the electronic device The steps include: requesting thumbnails of one or more multimedia files stored in the other electronic device from the other electronic device; The step of receiving the thumbnail of one or more multimedia files transmitted by the other electronic device. It becomes possible to perform this action. An electronic device as described in any one of items 21 through 24. (Item 26) When the instruction is executed by the one or more processors, the electronic device When the operation of the user tapping the first thumbnail is detected, the request is made for a first multimedia file corresponding to the first thumbnail from the other electronic device, wherein the thumbnails of the one or more multimedia files include the first thumbnail, and the first multimedia file is a multimedia file having a preset screen resolution. The steps include receiving the first multimedia file transmitted by the aforementioned other electronic device, A step of displaying a second interface, wherein the second interface includes the first multimedia file. It becomes possible to perform this action. Electronic devices as described in item 25. (Item 27) The second interface further includes a first control for local storage, and when the instruction is executed by the one or more processors, the electronic device When the user's tapping operation on the first control is detected, the request is made for a second multimedia file corresponding to the first thumbnail from the other electronic device, wherein the second multimedia file is the original data of the multimedia file corresponding to the thumbnail. The steps include receiving the second multimedia file transmitted by the aforementioned other electronic device, The steps include storing the second multimedia file in the electronic device and It becomes possible to perform this action. The electronic devices listed in item 26. (Item 28) The shared file includes the metadata, and when the instruction is executed by one or more processors, the electronic device After receiving metadata for each file transmitted by the other electronic device, the step of establishing an index of the metadata for each file based on the metadata for each file, A step of displaying search results based on the keywords entered by the user and the index of the metadata. It becomes possible to perform this action. An electronic device as described in any one of items 21 through 27. (Item 29) When the instruction is executed by the one or more processors, the electronic device The step of receiving an updated shared file transmitted by the aforementioned other electronic device. It becomes possible to perform this action. An electronic device as described in any one of items 21 through 28. (Item 30) When the instruction is executed by the one or more processors, the electronic device Before establishing the network connection to the other electronic device, The step of determining that the login account on the aforementioned electronic device is associated with the login account on the aforementioned other electronic device. It becomes possible to perform this action. An electronic device listed in any one of items 21 through 29.

Claims

1. A data sharing method applicable to electronic devices, The step of establishing a network connection between the aforementioned electronic device and another electronic device, wherein the network connection is used to transmit data. When the electronic device detects a keyword entered by the user, the electronic device requests from the other electronic device a thumbnail of one or more multimedia files, which are shared files stored in the other electronic device, related to the keyword. The electronic device receives the thumbnail of one or more multimedia files transmitted by the other electronic device, The electronic device displays a first interface, the first interface includes the received thumbnail, When the electronic device detects that the user has tapped a first thumbnail, the electronic device requests a first multimedia file corresponding to the first thumbnail from another electronic device, wherein the thumbnail of one or more multimedia files includes the first thumbnail, the first multimedia file is a multimedia file having a preset screen resolution, corresponds to the same content as a second multimedia file stored on the other electronic device, and always occupies less memory space than the second multimedia file, and the electronic device requests a first multimedia file corresponding to the first thumbnail from another electronic device, and the first multimedia file is a multimedia file having a preset screen resolution, and always occupies less memory space than the second multimedia file, The electronic device receives the first multimedia file transmitted by the other electronic device, The electronic device displays a second interface, the second interface includes the first multimedia file, and the display step is as follows: Methods that include...

2. The method according to claim 1, wherein the shared file includes metadata, and the metadata is attribute description information for each file in the shared file.

3. The method according to claim 1 or 2, wherein the first interface further includes the device name of the other electronic device.

4. The method according to any one of claims 1 to 3, wherein the step of the electronic device establishing a network connection to another electronic device comprises the step of the electronic device communicating with the other electronic device via a short-range wireless connection, or the step of the electronic device communicating with the other electronic device via a long-range wireless connection.

5. The second interface further includes a first control for local storage, and the method is When the electronic device detects that the user has tapped the first control, the electronic device requests the second multimedia file corresponding to the first thumbnail from the other electronic device. The electronic device receives the second multimedia file transmitted by the other electronic device, The electronic device stores the second multimedia file in the electronic device. The method according to any one of claims 1 to 4, further comprising:

6. The shared file includes metadata, and the method is After the electronic device receives the metadata for each file transmitted by the other electronic device, the electronic device establishes an index of the metadata for each file based on the metadata for each file. The electronic device performs the steps of displaying search results based on keywords entered by the user and the index of the metadata. The method according to any one of claims 1 to 5, further comprising:

7. The electronic device receives metadata for each file in the updated shared file transmitted by the other electronic device, The electronic device updates the metadata in the shared file stored in the electronic device. The method according to any one of claims 1 to 6, further comprising:

8. Before establishing the network connection to the other electronic device, the step of determining that the login account on the electronic device is associated with the login account on the other electronic device. The method according to any one of claims 1 to 7, further comprising:

9. When the operation to open the first application by the user is detected, the process includes the step of requesting metadata corresponding to each file in the shared file from the other electronic device, The steps include receiving the metadata for each file from the aforementioned other electronic device, The steps include determining the number of files in the shared file based on the number of metadata received, A step of displaying the first interface, wherein the first interface includes a folder corresponding to the shared file, the device name of the other electronic device, and the number of files. The method according to any one of claims 1 to 8, further comprising:

10. The display and One or more processors, One or more memory and An electronic device having, The one or more memory stores one or more computer programs, and the one or more computer programs include instructions, and when the instructions are executed by the one or more processors, the electronic device The stage of establishing a network connection to another electronic device, wherein the network connection is used to transmit data, and the stage of establishing the connection, When a keyword entered by the user is detected, the electronic device requests thumbnails of one or more multimedia files, which are shared files stored on the other electronic device, related to the keyword. The steps include receiving the thumbnails of one or more multimedia files transmitted by the other electronic device, The electronic device displays a first interface, the first interface includes the received thumbnail, When the operation of the user tapping the first thumbnail is detected, the system requests a first multimedia file corresponding to the first thumbnail from the other electronic device, wherein the thumbnails of the one or more multimedia files include the first thumbnail, the first multimedia file is a multimedia file having a preset screen resolution, corresponds to the same content as a second multimedia file stored on the other electronic device, and always occupies less storage space than the second multimedia file, and the system requests the first multimedia file. The steps include receiving the first multimedia file transmitted by the aforementioned other electronic device, A step of displaying a second interface, wherein the second interface includes the first multimedia file. An electronic device that makes it possible to perform certain actions.

11. The electronic device according to claim 10, wherein the shared file includes metadata, and the metadata is attribute description information for each file in the shared file.

12. The electronic device according to claim 10 or 11, wherein the first interface further includes the device name of the other electronic device.

13. The electronic device according to any one of claims 10 to 12, wherein the electronic device establishing the network connection to the other electronic device comprises the electronic device communicating with the other electronic device via a short-range wireless connection, or the electronic device communicating with the other electronic device via a long-range wireless connection.

14. The second interface further includes a first control for local storage, and when the instruction is executed by the one or more processors, the electronic device When the user is detected to tap the first control, the process includes requesting the second multimedia file corresponding to the first thumbnail from the other electronic device, The steps include receiving the second multimedia file transmitted by the aforementioned other electronic device, The steps include storing the second multimedia file in the electronic device and It becomes possible to perform this action. The electronic device according to any one of claims 10 to 13.

15. The shared file includes metadata, and when the instruction is executed by one or more processors, the electronic device After receiving metadata for each file transmitted by the other electronic device, the step of establishing an index of the metadata for each file based on the metadata for each file, A step of displaying search results based on the keywords entered by the user and the index of the metadata. It becomes possible to perform this action. The electronic device according to any one of claims 10 to 14.

16. When the instruction is executed by the one or more processors, the electronic device The steps include receiving metadata for each file in the updated shared file transmitted by the aforementioned other electronic device, The steps include updating the metadata in the shared file stored in the electronic device. It becomes possible to perform this action. The electronic device according to any one of claims 10 to 15.

17. When the instruction is executed by the one or more processors, the electronic device Before establishing the network connection to the other electronic device, The step of determining that the login account on the aforementioned electronic device is associated with the login account on the aforementioned other electronic device. It becomes possible to perform this action. The electronic device according to any one of claims 10 to 16.

18. The aforementioned electronic device When the operation to open the first application by the user is detected, the process includes the step of requesting metadata corresponding to each file in the shared file from the other electronic device, The steps include receiving the metadata for each file from the aforementioned other electronic device, The steps include determining the number of files in the shared file based on the number of metadata received, A step of displaying the first interface, wherein the first interface includes a folder corresponding to the shared file, the device name of the other electronic device, and the number of files. The electronic device according to any one of claims 10 to 17, which makes it possible to further perform the above.

Citation Information

Patent Citations

  • Communication program, recording medium, communication method and communication terminal device

    JP2007199863A