WO2022143081A1

WO2022143081A1 - Data synchronization method and apparatus

Info

Publication number: WO2022143081A1
Application number: PCT/CN2021/136803
Authority: WO
Inventors: 陈刚
Original assignee: 华为技术有限公司
Priority date: 2020-12-31
Filing date: 2021-12-09
Publication date: 2022-07-07
Also published as: CN114691631A

Abstract

A data synchronization method and apparatus, capable of simply and conveniently implementing cross-device data sharing, without requiring frequent manual operations of a user, thereby improving user experience. The method comprises: a first device acquires a media file update event (1501), wherein the media file update event is used for adding, modifying or deleting a first media file; the first device updates metadata, in a metadata library, corresponding to the first media file, and updates a thumbnail of the first media file in a media library (1502); and the first device sends a synchronization message to a second device (1503), wherein the synchronization message comprises the metadata corresponding to the first media file and the thumbnail of the first media file.

Description

A data synchronization method and device

This application claims the priority of the Chinese patent application with the application number 202011635721.1 and the application title "A method and device for data synchronization", which was submitted to the State Intellectual Property Office on December 31, 2020, the entire contents of which are incorporated herein by reference. middle.

technical field

The present application relates to the field of communications, and in particular, to a data synchronization method and apparatus.

Background technique

With the popularization and development of digital devices such as smart phones, tablets, and personal computers (PCs), the number of personal terminals has surged, and the data of different devices is stored in a decentralized manner. How to achieve safe and convenient data sharing across devices has become an urgent problem to be solved. .

Currently, schemes such as "AirDrop" and "MFiles" can share some data (for example, picture data) between two devices. For example, after the connection between device A and device B is established, the user of device A can send 10 pictures of device A to device B, and the user of device B can choose to receive and store the 10 pictures. The 10 pictures are shared between them.

However, the above solution is time-consuming in the data transmission process, and requires frequent operations by the user (for example, it is necessary to select the pictures to be shared and the devices to be shared), which cannot well realize cross-device data sharing.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a data synchronization method and apparatus, which can realize cross-device data sharing simply and conveniently, without requiring frequent manual operations by users, and can improve user experience.

In a first aspect, an embodiment of the present application provides a data synchronization method. The method includes: a first device acquires a media file update event; wherein the media file update event is used to add, modify or delete a first media file; the first device updates a metadata metadata corresponding to the first media file in the database, and update the thumbnail of the first media file in the media library; the first device sends a synchronization message to the second device, and the synchronization message includes the metadata corresponding to the first media file and the first media Thumbnail of the file. In this way, the metadata database and the media library can be automatically synchronized between the first device and the second device, data sharing across devices can be easily and conveniently achieved, and frequent manual operations by the user are not required, which can improve user experience.

In a possible implementation manner, the synchronization message further includes at least one of a user account, device information of the first device, and an update type of the first media file, where the update type of the first media file includes addition, modification, or deletion. Based on at least one of the user account, the device information of the first device, and the update type of the first media file, the metadata database and the media library can be automatically synchronized between the first device and the second device, which can easily and conveniently implement cross-device data Sharing, without the need for frequent manual operations by the user, can improve the user experience.

In a possible implementation manner, the thumbnail image of the first media file includes a thumbnail image of a first type, and the size of the thumbnail image of the first type ranges from 10 kilobytes (kb/K) to 20K. For example, the size of the first type of thumbnails may be 10K, 15K or 20K.

In a possible implementation manner, the method further includes: the first device receives a first request message, where the first request message is used to request a thumbnail image of a second type, and the size of the thumbnail image of the second type ranges from 100K to 300K; The first device sends a second type of thumbnail image to the second device. Exemplarily, the size of the second type of thumbnails may be 150K, 180K, 200K, 230K, and so on.

In a possible implementation manner, the first media file includes at least one of pictures, videos, audios, and documents.

In a possible implementation manner, the method further includes: the first device displays a first interface including the identifier of the second device; in response to the user's operation of clicking the identifier of the second device on the first interface, the first device displays the second interface The second interface includes one or more thumbnail images of at least one type of media file of the second device. Exemplarily, as shown in FIG. 5A , the first device (eg, mobile phone A) may display a first interface (eg, interface 420 ) containing the identification of the second device (eg, Mate 30 pro), in response to the user clicking on the first interface (eg, interface 420 ). An operation of clicking the logo of the second device on an interface, as shown in FIG. 6A , the first device displays a second interface, and the second interface includes at least one type of media files (for example, pictures, videos, audios, documents, etc.) of the second device ) of one or more thumbnails. The picture may be, for example, A-002.jpg, and the document may include, for example, cover design.pptx, and the like.

In a possible implementation manner, the first interface or the second interface includes a search control, and in response to an operation of inputting a keyword after the user clicks the search control, the first device displays a third interface, and the third interface includes data from the first device and the The identifier of the media file related to the keyword searched by the second device. Exemplarily, as shown in (a) of FIG. 7B , in response to an operation of inputting a keyword (for example, TOEFL) after the user clicks the search control 440, as shown in (b) of FIG. 7B , the first device displays the No. Three interfaces (eg, interface 441 ), the third interface includes the identifiers of the media files related to the keyword searched from the first device and the second device. For example, it can include TOEFL Ladder Skills.doc, TOEFL Listening Analysis.mp3, etc.

In a possible implementation manner, the method further includes: in response to the user's operation of clicking the first thumbnail on the second interface, the first device displays a first pop-up frame, and the first pop-up frame includes the first operation option; Clicking the operation of the first operation option, the first device displays a second pop-up box, and the second pop-up box includes one or more application programs or device identifiers; in response to the operation of the user clicking an application program or a device identifier, the first device will The first thumbnail is shared to the application program clicked by the user or the device corresponding to the device identifier. Exemplarily, as shown in (a) of FIG. 8A , in response to the user's operation of clicking the first thumbnail (eg, picture 450 ) on the second interface (eg, interface 430 ), the first device displays a first pop-up frame (for example, pop-up box 451), the first pop-up box includes a first operation option (for example, share option 452); in response to the operation of the user clicking the first operation option, as shown in (b) in FIG. 8A, the first device A second pop-up frame (eg, pop-up frame 453) may be displayed, and the second pop-up frame includes one or more application or device identifiers (eg,

Nearby devices, etc.); in response to the operation of the user clicking on an application or a device identifier, the first device shares the first thumbnail to the device corresponding to the application or device identifier clicked by the user.

In a possible implementation manner, when the first device is connected to the second device for the first time, the method further includes: the first device synchronizes the metadata corresponding to all media files of the first device and the thumbnail images corresponding to all media files to the first device. Second equipment. That is, when the first device and the second device are connected for the first time, the metadata corresponding to all the media files of the first device and the thumbnail images corresponding to all the media files of the first device can be automatically synchronized between the first device and the second device. Device data sharing does not require users to perform frequent manual operations, which can improve user experience.

In a possible implementation manner, when the first device is connected to the second device for the Nth time, N is an integer greater than or equal to 2, and the method further includes: the first device synchronizes the media updated on the first device after the last synchronization The metadata corresponding to the file and the thumbnail corresponding to the updated media file are synchronized to the second device. When the first device and the second device are connected for the Nth time, the metadata and thumbnails corresponding to the media files updated by the first device can be automatically synchronized between the first device and the second device, and there is no need to resynchronize all the media files, which can save resources and improve efficiency.

In a possible implementation manner, the method further includes: the first device analyzes the user's preferences and behavioral habits based on an artificial intelligence (artificial intelligence, AI) algorithm; and predicts the media files that the user needs to operate according to the user's preferences and behavioral habits; The second type of thumbnails of the media files that the user needs to operate are sent to the second device. In this way, the second device can cache the media files that the user may open locally in advance, and the user can quickly view the second type of thumbnail images later, which can improve user experience.

In a possible implementation manner, the first device deletes cold data based on a preset period; wherein the cold data includes thumbnails of media files whose access times are lower than a preset threshold. In this way, the memory space of the first device can be saved.

In a possible implementation manner, the method further includes: when the first device plays the media file of the second device for the first time, starting a streaming server proxy, and the streaming server proxy is used to encapsulate the media file of the second device into a streaming media format; A device obtains the media files of the second device from the second device in m times through the streaming server proxy and caches them; where m is an integer greater than or equal to 2; the first device plays the cached data. In this way, when the first device plays the media file of the second device for the first time, the player does not need to wait for the media file (for example, the original video file) to be completely downloaded before starting the playback, and can play it in real time, thereby realizing a high-performance user experience similar to local playback. .

In a possible implementation manner, when the first device plays the media file of the second device for the Nth time, it obtains a uniform resource identifier (URI) of the media file of the second device, obtains the cached data according to the URI, and Play; wherein, N is an integer greater than or equal to 2. In this way, when the first device plays the media file of the second device for the Nth time, it can obtain the cached data according to the URI and directly play the media file without re-cache the data, which can reduce the power consumption of the first device.

In a second aspect, an embodiment of the present application provides a full synchronization method, including: when a first device is connected to a second device for the first time, the method further includes: the first device synchronizes metadata and all media files corresponding to all media files of the first device The thumbnails corresponding to the files are synchronized to the second device. That is, when the first device and the second device are connected for the first time, the metadata corresponding to all the media files of the first device and the thumbnail images corresponding to all the media files of the first device can be automatically synchronized between the first device and the second device. Device data sharing does not require users to perform frequent manual operations, which can improve user experience.

In a third aspect, an embodiment of the present application provides an incremental synchronization method, including: when the first device and the second device are connected for the Nth time, N is an integer greater than or equal to 2, and the method further includes: the first device synchronizes the last After synchronization, the metadata corresponding to the updated media file on the first device and the thumbnail corresponding to the updated media file are synchronized to the second device. That is, when the first device and the second device are connected for the Nth time, the metadata and thumbnail images corresponding to the media files updated by the first device can be automatically synchronized between the first device and the second device. Save resources and improve efficiency.

In a fourth aspect, the embodiments of the present application provide an automatic caching method, including: the first device analyzes the user's preferences and behavioral habits based on an artificial intelligence AI algorithm; predicts the media files that the user needs to operate according to the user's preferences and behavioral habits; A second type of thumbnail image of the media file that the user needs to operate is sent to the second device. In this way, the second device can cache the media files that the user may open locally in advance, and the user can quickly view the second type of thumbnail images later, which can improve user experience.

In a fifth aspect, an embodiment of the present application provides an automatic aging method, including: a first device deletes cold data based on a preset period; wherein the cold data includes thumbnails of media files whose access times are lower than a preset threshold. In this way, the memory space of the first device can be saved.

In a sixth aspect, an embodiment of the present application provides a streaming media playback method, including: when a first device plays a media file of a second device for the first time, starting a streaming server proxy, and the streaming server proxy is used to encapsulate the media file of the second device into a Streaming media format; the first device obtains the media files of the second device from the second device in m times through the streaming server proxy and caches them; where m is an integer greater than or equal to 2; the first device plays the cached data. In this way, when the first device plays the media file of the second device for the first time, the player does not need to wait for the media file (for example, the original video file) to be completely downloaded before starting the playback, and can play it in real time, thereby realizing a high-performance user experience similar to local playback. .

In a possible implementation manner, when the first device plays the media file of the second device for the Nth time, the URI of the media file of the second device is obtained, and the cached data is obtained and played according to the URI; wherein, N is greater than or equal to 2 Integer. In this way, when the first device plays the media file of the second device for the Nth time, it can obtain the cached data according to the URI and directly play the media file without re-cache the data, which can reduce the power consumption of the first device.

In a seventh aspect, an embodiment of the present application provides an electronic device (eg, a first device or a second device), the electronic device having the function of implementing the method described in any of the foregoing aspects and any possible implementation manners thereof. The functions can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In an eighth aspect, the present application provides a computer-readable storage medium, the computer-readable storage medium comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device is caused to perform the method described in any of the above aspects and any possible implementations thereof.

In a ninth aspect, the present application provides a computer program product that, when the computer program product runs on a computer, causes the computer to execute the method described in the first aspect and any possible implementation manners thereof.

In a tenth aspect, an embodiment of the present application provides a chip system, where the chip system includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected by wires. The chip system can be applied to electronic equipment including a communication module and a memory. The interface circuit is configured to receive signals from the memory of the electronic device and send the received signals to the processor, the signals including computer instructions stored in the memory. When the processor executes the computer instructions, the electronic device can execute the method described in any of the above aspects and any of its possible implementations.

In an eleventh aspect, an embodiment of the present application provides a data synchronization system, including two electronic devices (for example, a first device and a second device), and each electronic device can perform any of the above aspects and any possible implementation thereof way method.

Exemplarily, the first device may acquire a media file update event; wherein, the media file update event is used to add, modify or delete the first media file; the first device updates the metadata corresponding to the first media file in the metadata database, and updates The thumbnail of the first media file in the media library; the first device sends a synchronization message to the second device, where the synchronization message includes metadata corresponding to the first media file and the thumbnail of the first media file. The second device may receive the synchronization message from the first device.

Description of drawings

FIG. 1A is a schematic diagram of a network architecture provided by an embodiment of the present application;

FIG. 1B is a schematic diagram of a network architecture provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a hardware structure of an electronic device 200 according to an embodiment of the present application;

FIG. 3 is a schematic display diagram provided by an embodiment of the present application;

FIG. 4A is another schematic display diagram provided by an embodiment of the present application;

FIG. 4B is another schematic display diagram provided by an embodiment of the present application;

FIG. 4C is another schematic display diagram provided by an embodiment of the present application;

FIG. 5A is another schematic display diagram provided by an embodiment of the present application;

FIG. 5B is another schematic display diagram provided by an embodiment of the present application;

FIG. 6A is another schematic display diagram provided by an embodiment of the present application;

FIG. 6B is another schematic display diagram provided by an embodiment of the present application;

FIG. 6C is another schematic display diagram provided by an embodiment of the present application;

FIG. 6D is another schematic display diagram provided by an embodiment of the present application;

FIG. 7A is another schematic display diagram provided by an embodiment of the present application;

FIG. 7B is another schematic display diagram provided by an embodiment of the present application;

FIG. 8A is another schematic display diagram provided by an embodiment of the present application;

FIG. 8B is another schematic display diagram provided by an embodiment of the present application;

FIG. 9A is another schematic display diagram provided by an embodiment of the present application;

FIG. 9B is another schematic display diagram provided by an embodiment of the present application;

10A is a schematic diagram of a software architecture of a mobile phone according to an embodiment of the present application;

10B is a schematic diagram of a system architecture between a mobile phone A, a mobile phone B, and a cloud server according to an embodiment of the application;

11A is a schematic diagram of signal interaction between a mobile phone A and a mobile phone B according to an embodiment of the application;

11B is another schematic diagram of signal interaction between mobile phone A and mobile phone B according to an embodiment of the application;

11C is another schematic diagram of signal interaction between mobile phone A and mobile phone B according to an embodiment of the present application;

11D is another schematic diagram of signal interaction between mobile phone A and mobile phone B according to an embodiment of the present application;

FIG. 11E is another schematic display diagram provided by an embodiment of the present application;

12 is another schematic diagram of signal interaction between mobile phone A and mobile phone B according to an embodiment of the present application;

13 is another schematic diagram of signal interaction between mobile phone A and mobile phone B according to an embodiment of the present application;

FIG. 14 is another schematic diagram of a display provided by an embodiment of the present application;

FIG. 15 is another schematic diagram of signal interaction provided by an embodiment of the present application;

FIG. 16 is a schematic structural diagram of a chip provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Wherein, in the description of the present application, unless otherwise specified, "at least one" refers to one or more, and "a plurality" refers to two or more than two. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with basically the same function and effect. Those skilled in the art can understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like are not necessarily different.

With the popularization and development of digital devices such as smart phones, tablets, personal computers (PCs), and smart home appliances, the number of personal terminals and the amount of media data surge. In addition, the development of the camera technology of mobile phones has resulted in the mass appearance of personal image content, resulting in a shortage of the storage space of a single device. Under the above circumstances, users' demand for intelligent search and sharing is increasing day by day, which promotes the development of distributed media data management.

The embodiments of the present application provide a distributed media data management method and framework, which can realize the localization of user access, retrieval, and sharing across devices, and is convenient to operate.

The system architecture involved in the embodiments of the present application may include multiple electronic devices, the multiple electronic devices may be networked, and information exchange may be performed between the multiple electronic devices after the networking. The networking methods include but are not limited to the following methods:

(1) Wireless fidelity (wireless fidelity, WIFI) networking mode: multiple electronic devices can be connected to the same routing device (for example, a router). As shown in FIG. 1A , a mobile phone 101 , a mobile phone 102 , a tablet computer 103 , a notebook computer 104 , and a smart TV 105 can be connected to a router 106 to form a home network. Alternatively, multiple electronic devices can join the same hotspot device (for example, access the hotspot of the same mobile phone), and at this time, the information interaction between the electronic device and the electronic device can be forwarded through the hotspot device. For example, mobile phone 102, tablet computer 103, notebook computer 104, and smart TV 105 can be connected to mobile phone 101 to form a hotspot network, and mobile phone 101 can be used as a hotspot device to forward information for each electronic device.

(2) Cloud server networking mode: Multiple electronic devices can be connected to the same cloud server. At this time, the information interaction between the electronic device and the electronic device can be forwarded through the cloud server. As shown in FIG. 1B , the mobile phone 102 , the tablet computer 103 , the notebook computer 104 and the smart TV 105 can be connected to the router 106 to form a home network. The router 106 can be connected to the server 201 , and the mobile phone 101 can also be connected to the server 201 , and the server 201 It can be used as a relay device to forward information for the router 106 and the mobile phone 101 , that is, the router 106 can exchange information with the mobile phone 101 through the server 201 . The mobile phone 101 can exchange information with electronic devices such as the mobile phone 102 , the tablet computer 103 , the notebook computer 104 , and the smart TV 105 through the server 201 and the router 106 .

In a possible design, the mobile phone 101, the mobile phone 102, the tablet computer 103, the laptop computer 104, the smart TV 105 and the router 106 can all be connected to the server, and the server can be used as a relay device for the mobile phone 101, the mobile phone 102, the tablet computer 103, Information is forwarded between the notebook computer 104 , the smart TV 105 and the router 106 . That is, the mobile phone 101 , the mobile phone 102 , the tablet computer 103 , the notebook computer 104 , the smart TV 105 and the router 106 can exchange information through the server.

Alternatively, Bluetooth networking may also be performed between multiple electronic devices. For example, multiple electronic devices (eg, mobile phone 102, tablet computer 103, laptop computer 104, smart TV 105, and router 106) may be connected to the same Bluetooth device (eg, mobile phone 101), and the electronic device and the electronic device The information exchange can be forwarded through the Bluetooth device.

Multiple electronic devices may use multiple networking methods, for example, at least two of the wireless fidelity networking method, the Bluetooth networking method, or the cloud server networking method, which are not limited in this application.

In the embodiments of the present application, each electronic device shown in FIG. 1A or FIG. 1B (eg, the mobile phone 101 or the mobile phone 102 ) is the electronic device 200 as an example to illustrate the structure of the electronic device provided by the embodiments of the present application. As shown in FIG. 2, the electronic device 200 may include: a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, Antenna 1, Antenna 2, Mobile Communication Module 250, Wireless Communication Module 260, Audio Module 270, Speaker 270A, Receiver 270B, Microphone 270C, Headphone Interface 270D, Sensor Module 280, Key 290, Motor 291, Indicator 292, Camera 293, a display screen 294, and a subscriber identification module (subscriber identification module, SIM) card interface 295 and the like.

The above sensor module 280 may include sensors such as pressure sensor, gyro sensor, air pressure sensor, magnetic sensor, acceleration sensor, distance sensor, proximity light sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor and bone conduction sensor.

It can be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 200 . In other embodiments, the electronic device 200 may include more or fewer components than shown, or combine some components, or separate some components, or different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 210 may include one or more processing units, for example, the processor 210 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU) Wait. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

The controller may be the nerve center and command center of the electronic device 200 . The controller can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.

A memory may also be provided in the processor 210 for storing instructions and data. In some embodiments, the memory in processor 210 is cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 210 . If the processor 210 needs to use the instruction or data again, it can be called directly from the memory. Repeated accesses are avoided, and the waiting time of the processor 210 is reduced, thereby improving the efficiency of the system.

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

It can be understood that the interface connection relationship between the modules illustrated in this embodiment is only a schematic illustration, and does not constitute a structural limitation of the electronic device 200 . In other embodiments, the electronic device 200 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.

The charging management module 240 is used to receive charging input from the charger. The charger may be a wireless charger or a wired charger. While the charging management module 240 charges the battery 242 , the power management module 241 can also supply power to the electronic device.

The power management module 241 is used to connect the battery 242 , the charging management module 240 and the processor 210 . The power management module 241 receives input from the battery 242 and/or the charging management module 240, and supplies power to the processor 210, the internal memory 221, the external memory, the display screen 294, the camera 293, and the wireless communication module 260. In some embodiments, the power management module 241 and the charging management module 240 may also be provided in the same device.

The wireless communication function of the electronic device 200 may be implemented by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modulation and demodulation processor, the baseband processor, and the like. In some embodiments, the antenna 1 of the electronic device 200 is coupled with the mobile communication module 250, and the antenna 2 is coupled with the wireless communication module 260, so that the electronic device 200 can communicate with the network and other devices through wireless communication technology.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 200 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, the antenna 1 can be multiplexed as a diversity antenna of the wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 250 may provide a wireless communication solution including 2G/3G/4G/5G, etc. applied on the electronic device 200 . The mobile communication module 250 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), and the like. The mobile communication module 250 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation.

The mobile communication module 250 can also amplify the signal modulated by the modulation and demodulation processor, and then convert it into electromagnetic waves for radiation through the antenna 1 . In some embodiments, at least part of the functional modules of the mobile communication module 250 may be provided in the processor 210 . In some embodiments, at least part of the functional modules of the mobile communication module 250 may be provided in the same device as at least part of the modules of the processor 210 .

The wireless communication module 260 can provide applications on the electronic device 200 including WLAN (such as (wireless fidelity, Wi-Fi) network), Bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation ( frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions.

The wireless communication module 260 may be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2 , modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 210 . The wireless communication module 260 can also receive the signal to be sent from the processor 210 , perform frequency modulation on the signal, amplify the signal, and then convert it into an electromagnetic wave for radiation through the antenna 2 .

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

Display screen 294 is used to display images, videos, and the like. The display screen 294 includes a display panel.

The electronic device 200 can realize the shooting function through the ISP, the camera 293, the video codec, the GPU, the display screen 294 and the application processor. The ISP is used to process the data fed back by the camera 293 . Camera 293 is used to capture still images or video. In some embodiments, the electronic device 200 may include 1 or N cameras 293 , where N is a positive integer greater than 1.

The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200. The external memory card communicates with the processor 210 through the external memory interface 220 to realize the data storage function. For example to save files like music, video etc in external memory card.

Internal memory 221 may be used to store computer executable program code, which includes instructions. The processor 210 executes various functional applications and data processing of the electronic device 200 by executing the instructions stored in the internal memory 221 . For example, in this embodiment of the present application, the processor 210 may execute instructions stored in the internal memory 221, and the internal memory 221 may include a program storage area and a data storage area.

The storage program area can store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), and the like. The storage data area can store data (such as audio data, phone book, etc.) created during the use of the electronic device 200 and the like. In addition, the internal memory 221 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), and the like.

The electronic device 200 may implement audio functions through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, and an application processor. Such as music playback, recording, etc.

The keys 290 include a power-on key, a volume key, and the like. Keys 290 may be mechanical keys. It can also be a touch key. Motor 291 can generate vibrating cues. The motor 291 can be used for vibrating alerts for incoming calls, and can also be used for touch vibration feedback. The indicator 292 can be an indicator light, which can be used to indicate the charging status, the change of power, and can also be used to indicate messages, missed calls, notifications, and the like. The SIM card interface 295 is used to connect a SIM card. The SIM card can be contacted and separated from the electronic device 200 by inserting into the SIM card interface 295 or pulling out from the SIM card interface 295 . The electronic device 200 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 can support Nano SIM card, Micro SIM card, SIM card and so on.

For ease of understanding, taking the electronic device as a mobile phone as an example, the method provided by the embodiments of the present application is described in detail with reference to the accompanying drawings.

As shown in (a) of FIG. 3 , after opening the setting application 302 on the main interface 301 of the mobile phone A, the setting interface 303 shown in (b) of FIG. 3 can be entered. In the setting interface 303, a plurality of setting options may be included, for example, a personal account setting item (eg, Glen Gao), a WLAN setting item, a Bluetooth setting item, a mobile network setting item, a more connection setting item, a desktop and a wallpaper setting may be included items etc. In response to the user clicking the control 304 corresponding to the more connection setting items, as shown in (c) of FIG. 3 , the mobile phone may display the more connection interface 305 . In the more connection interface 305, a plurality of connection options may be included, for example, a multi-device collaboration option, an NFC option, a Huawei Share option, a Huawei HiCar option, a mobile phone screen projection option, a printing option, a VPN option, and the like may be included. In response to the user clicking the control 306 corresponding to "multi-device collaboration", as shown in (d) in FIG. 3 , the mobile phone may display a multi-device collaboration interface 307 . In the multi-device collaboration interface 307, a prompt animation/prompt picture 308 and a prompt text 309 may be included. The prompt text 309 is used to prompt the user to "swipe up from the lower left corner of the screen when the screen is not locked to enter the device control center, and the local task can be connected to other nearby devices and quickly control the smart home", and the prompt animation 308 is used to show the user. Demonstrate the operation of swiping up from the lower left corner of the screen. Of course, when the screen is not locked, it can also be swiped up from the lower right corner of the screen to enter the device control center, which is not limited in this application. Among them, the device control center is a system APP. The device control center can also be replaced with a file management (also called a file manager, a system APP). The multi-device collaboration interface 307 may further include switches (buttons) 310 and prompt information 311 . Prompt message 311 explains that "this service (multi-device collaboration service/function) and its underlying services (word processing, resource update AI intelligence, general card management service) need to be connected to the Internet, using storage, information, Bluetooth, telephone (reading device calls Status, make calls), location information, address book, memo, calendar permissions, access device and account information. Turning on the switch (ie switch 310) means that you agree to the above content and the statement on multi-device collaboration and privacy". After reading the prompt information 311 , the user can learn about the permissions required for the multi-device collaborative service, and decide whether to turn on the switch 311 . If the user turns on the switch 311, it means that the user agrees to authorize various permissions required for the multi-device collaborative service, and the mobile phone A can enable the multi-device collaborative service/function.

After multiple devices (for example, mobile phone A and mobile phone B) enable the multi-device collaborative service/function at the same time, a connection is established between the multiple devices. After the connection, any one of the multiple devices can realize cross-device data access, Search and share. Multiple devices may correspond to the same account (for example, a Huawei account), or multiple devices may correspond to different accounts, which are not limited in this application.

For another example, as shown in (a) of FIG. 4A , in the “Browse” interface 401 of the device control center of mobile phone A, a search bar, icons of various media content (for example, including pictures, videos, documents, icons of media content such as apps), location (for example, including my mobile phone, HUAWEI CLOUD, recently deleted, etc.), source (for example, including downloading and receiving,

etc. sources). In interface 401, controls 402 for adding other devices may also be included. In response to the user's operation of clicking the control 402, as shown in (b) of FIG. 4A, the mobile phone may display an add device interface 403. In the adding device interface 403, the devices currently searched by mobile phone A (for example, devices connected to the same local area network) can be displayed, such as Mate 30 pro (mobile phone B), Mate pad pro (tablet computer), Huawei TV, Mate 30 pro (mobile phone B), Mate pad pro (tablet computer) book (laptop), etc. The interface 403 may also include options for adding network neighbors, adding FTP, and WebDAB, and help information 405, which can help the user answer the doubts about "how to connect to other devices?" and perform "device recommendation". In response to the user's operation of clicking the control 404 corresponding to the Mate 30 pro (mobile phone B), as shown in (c) of FIG. 4A , the mobile phone A may pop up a prompt box 406, which includes a text prompt 407a, a cancel button 408 and a connection button 409. The text prompt 407a can prompt the user "After connecting, you can view the data of this device and share data between devices, whether to connect?", in response to the user's operation of clicking the connect button 409, mobile phone A can send a connection request to mobile phone B , At the same time, as shown in (d) of FIG. 4A , the prompt text 407a in the prompt box 406 can be changed to 407b, and the prompt text 407b can prompt the user "waiting for Mate30 pro confirmation...". As shown in FIG. 4B , assuming that when mobile phone A sends a connection request to mobile phone B, mobile phone B is in a bright screen state and the current display content is the desktop, a pop-up box 410 may pop up on the desktop of mobile phone B, and the pop-up box 410 may include text prompts 411 , Deny button 412 and Allow button 413. The text prompt 411 can be used to prompt the user "HUAWEI P20 (ie mobile phone A) wants to connect to this device, after the connection, data can be shared between the devices, whether to connect?", in response to the user's operation of clicking the allow button 413, the mobile phone B can establish a connection with phone A so that data can be shared. Optionally, the pop-up box 410 may also include prompt text 414, which is used to prompt the user whether to select "trust this device and always allow the connection". If the user clicks the check box, the mobile phone B can automatically connect with the mobile phone A next time. There is no need to notify the user, and the user does not need to take a corresponding action (such as clicking the allow button), which can improve the user experience.

In a possible design, as shown in FIG. 4C , in the “recent” interface 415 of mobile phone A, an instant entry 416 for viewing other devices may be displayed, and in response to the operation of the user clicking the instant entry 416, mobile phone A may An interface as shown in (b) in FIG. 4A is displayed. For the subsequent process, reference may be made to the related description about FIG. 4A , which will not be repeated here.

Similar to the process of establishing a connection between mobile phone A and Mate 30 pro (mobile phone B), mobile phone A can establish connections with devices such as Mate pad pro (tablet computer), Huawei TV, and Mate book (laptop computer). In this way, users can access and share data across devices. For example, users can view data from devices such as Mate 30 pro (mobile phone B), Mate pad pro (tablet computer), Huawei TV, and Mate book (laptop computer) on mobile phone A. In this way, the problem of inconvenience for users to find data caused by numerous personal terminal devices and scattered storage of personal data can be solved.

After mobile phone A is connected to devices such as Mate 30 pro (mobile phone B), Mate pad pro (tablet computer), Huawei TV, and Mate book (laptop), as shown in FIG. 5A , under the other device option 421 of the browsing interface 420 , can display all devices currently connected to mobile phone A, such as Mate 30 pro (mobile phone B), Mate pad pro (tablet computer), Huawei TV and Mate book (laptop).

Further, users can also cancel the connection between mobile phone A and Mate 30 pro (mobile phone B), Mate pad pro (tablet computer), Huawei TV and Mate book (laptop computer) and other devices. For example, as shown in (a) of FIG. 5B, in response to the user's long-pressing (for example, pressing and holding the screen for 2s) any position in the area 422 corresponding to the Mate 30 pro (mobile phone B), the mobile phone A can pop up a pop-up Box 423, the pop-up box 423 includes the cancel authorization option and the delete device option. If the user clicks the cancel authorization option, in response to the user's operation, as shown in (c) in FIG. 5B, the mobile phone A can pop up the pop-up box 426, the pop-up box 426 includes the prompt information "After the authorization is cancelled, the devices will no longer share data, whether to cancel", and the temporarily cancel button and the cancel authorization button, and the user can click the corresponding button according to their own needs. If the user clicks the delete device option, as shown in (d) in FIG. 5B , in response to the user's operation, mobile phone A may pop up a pop-up box 427, and the pop-up box 427 includes a prompt message "After deletion, data will no longer be shared between devices. , whether to delete" and the cancel button and delete button, users can click the corresponding buttons according to their own needs. For another example, as shown in (b) in FIG. 5B, the user can swipe left in the area 422 corresponding to the Mate 30 pro (mobile phone B), and the mobile phone A can display the cancel authorization icon 424 and the delete device icon 425. If the user clicks After canceling the authorization icon 424, in response to the user's operation, as shown in (c) of FIG. 5B, the mobile phone A may pop up a pop-up box 426, and the pop-up box 426 may refer to the above description. If the user clicks the delete device icon 425, as shown in (d) of FIG. 5B, in response to the user's operation, the mobile phone A may pop up a pop-up box 427, which can refer to the above description.

In some embodiments, the user may view media files of other devices on cell phone A. In this embodiment of the present application, viewing media files may refer to viewing thumbnails of media files (for example, thumbnails of pictures, and cover thumbnails of audio and video) or the media files themselves (the media files themselves may be referred to as original media files, such as , the original media file can be the original image of the picture, the original file of the video, the original file of the audio, etc.). As shown in FIG. 5A , in response to the user clicking any position in the area 422 corresponding to the Mate 30 pro (mobile phone B), as shown in FIG. 6A , the mobile phone A can display the media file interface 430 corresponding to the Mate 30 pro (mobile phone B) , the interface 430 may include a plurality of tabs, for example, tabs such as recent, picture, video, audio, document, and others may be included. Mobile phone A can display the contents of the recent tab 431 by default, and the interface 430 can display media files (eg, pictures, videos, audios, documents, etc.) recently processed (downloaded, cached, uploaded) by different applications. E.g,

2 media files (pictures) have just been processed (for example, within 5 minutes), namely A-001.jpg and A-001.jpg (the picture format is jpg), and the processing time is 2019/3/16. The size is 9.34KB respectively. Similarly, WPS processed 5 media files (eg, documents) yesterday.

8 media files (eg pictures) were processed yesterday. Figure 6A

The processed 8 media files are not displayed completely, the user can perform an operation of swiping up, and the mobile phone A can display more media files in response to the user's operation. As shown in FIG. 6B, in response to the user's operation of selecting the picture tab 432, the mobile phone A can display the content of the picture tab 432, that is, when the picture tab 432 is selected, the interface 430 can display different pictures of the Mate 30 pro (mobile phone B) The content of the folder, for example, can include all pictures (223 items in total), screenshots (34 items in total), images (123 items in total), pictures (327 items in total) and mail (327 items in total) and other picture folders. As shown in FIG. 6C, in response to the user's operation of selecting the video tab 433, the mobile phone A can display the content of the video tab 433, that is, when the video tab 433 is selected, the interface 430 can display the video file of the Mate 30 pro (mobile phone B). The content of the folder, for example, can include all videos (568 items in total), from

's videos (34 in total), from

videos (123 in total), videos from Huawei Video (327 in total) and videos from

videos (6 items in total) and other video folders. As shown in FIG. 6D, in response to the user's operation of selecting the audio tab 434, the mobile phone A can display the content of the audio tab 434, that is, when the audio tab 434 is selected, the interface 430 can display various The icon and name of the audio, for example can include xx1.mp3, xx2.mp3, xx3mp3, xx4.mp3, xx5.mp3, xx6.mp3, xx7.mp3, xx8.mp3, xx9.mp3, xx10.mp3, xx11.mp3 , xx12.mp3, etc.

In this way, after the connection between mobile phone A and Mate 30 pro (mobile phone B) is established, the user can view the data of Mate 30 pro (mobile phone B) on mobile phone A, which can realize the localization of data access across devices.

Similarly, as shown in FIG. 5A, in response to the user clicking on any position in the area corresponding to the Mate pad pro, Huawei TV or Mate book, mobile phone A can display the interface corresponding to the Mate pad pro, Huawei TV or Mate book, and the user can View media files of different devices through interfaces corresponding to different devices. For the specific description, please refer to the description of the interface corresponding to the Mate 30 pro above, which will not be repeated here.

In some embodiments, the user can retrieve the media files of the device and other devices (other devices currently connected to the phone A) on the mobile phone A. As shown in (a) of FIG. 7A, in response to the user's operation of inputting "TOEFL" in the search box 417 of the recent interface 415 of the mobile phone A, as shown in (b) of FIG. 7A, the mobile phone A may display this book by default. The search results of the computer tab 418, the search results of the local computer can include files from "Huawei Cloud Disk" (for example, TOEFL Basic Lectures. mp4, etc.) and audio (eg, TOEFL Listening Fundamentals Course.mp3, etc.). As shown in (c) of FIG. 7A, in response to the user's operation of selecting the other devices tab 421, mobile phone A may display search results of other devices, and the search results of other devices may include 10 files found by Mate 30Pro and 6 files found by Matebook item file. Exemplarily, the 10-item files found by the Mate 30Pro may include TOEFL problem solving skills.doc and the like. Matebook finds 6 files that can include TOEFL Breakthrough.mp4 and so on. Users can view more files found by the Mate 30Pro or Matebook by clicking the View More button. In this way, the user can search for a certain content on all the devices connected to the mobile phone A, and there is no need to perform search operations on different devices, which can simplify the user's operation and improve the user experience. That is, the embodiment of the present application can realize cross-device fusion retrieval, and can solve the problem that user data is scattered everywhere and is difficult to find.

Alternatively, users can choose to search for an item on a certain device. For example, as shown in (a) in FIG. 7B , in the interface 430 of the mobile phone A, in response to the operation of the user clicking the search control 440, the mobile phone A can display the search interface 441 shown in (b) in FIG. 7B , In the search box 442 of the interface 441, the mobile phone A can receive the "TOEFL" input by the user, and in response to the operation of the user inputting "TOEFL", the mobile phone A can display the search results of the Mate 30 pro (mobile phone B) for "TOEFL", and search for "TOEFL". The result can be to find 10 items of files, for example, can include TOEFL problem solving skills.doc, TOEFL listening analysis.mp3 and TOEFL listening improvement.mp4 and other files. In this way, the user can search for a certain content (for example, "TOEFL") in any device connected to mobile phone A, without the need to perform a corresponding search operation on the corresponding device (for example, Mate 30 pro (mobile phone B)), which can simplify User operation, improve user experience.

The user can share one or more media files of mobile phone B on mobile phone A to third-party applications or system applications. In a possible design, as shown in (a) of FIG. 8A , in the interface 430 of the mobile phone A, in response to the user's operation of long pressing the picture 450 , the mobile phone A may pop up a pop-up frame 451 , and in the pop-up frame 451 It includes multiple operation options, such as sharing, multiple selection, copying, details, and opening method. In response to the user's operation of clicking the share operation option 452, as shown in (b) in FIG. 8A, the mobile phone A may pop up a pop-up box 453, and the pop-up box 453 may include prompt information 454 and information about the application or service that can be shared. The icon 455 and the prompt information 454 can be used to prompt the user: "A nearby device is being discovered. The other party needs to open Huawei Share in the notification bar. If you want to print, please make sure that the printer can be discovered." Icons of applications or services that can be shared 455 for example can include

Email, Huawei Cloud Disk, etc. If the user does not want to continue sharing, the user can click the cancel button 456 to cancel the sharing. The embodiments of the present application can realize the localization of user data sharing, and solve the problem of inconvenience in user data sharing.

In another possible design, as shown in (a) of FIG. 8B, in the interface 430 of the mobile phone A, in response to the user's operation of long pressing the picture 450, the mobile phone A can pop up the pop-up frame 460 and the pop-up frame 461, The pop-up box 460 may include several operation options commonly used by the user, for example, may include operation options such as share, favorite, and delete. The pop-up box 461 may include multiple operation options, for example, may include operation options such as multi-select, move, copy, rename, details, open method, set as, and set as private. In response to the user's operation of clicking the move operation option 462 in the pop-up box 461, as shown in (b) of FIG. 8B, the mobile phone A can pop up a pop-up box 463, and the pop-up box 463 can include a plurality of position information that can be moved , for example, it can include the SD card and Huawei cloud disk in my mobile phone, and can also include different folders of other devices (for example, Mate 30 pro (mobile phone B)), for example, it can include the Alarms, folders such as apmmodel, edge, picture, and my files. In response to the user's operation of clicking any position in the area 464 corresponding to the Alarms folder, a prompt text 465 may be displayed above the pop-up box 463, prompting the user to "move 1 item to "Alarms", a total of 17.34MB". Among them, one media file to be moved is the picture 450, and the picture 450 has a total of 17.34MB. The embodiments of the present application can realize the localization of user data sharing, and solve the problem of inconvenience in user data sharing.

The embodiments of the present application support third-party applications to search, access, and share media files across devices. For example, when a user inserts an attachment in a mail application, he can search from the machine or from multiple devices connected to the machine.

In a possible implementation, as shown in (a) of FIG. 9A , when the user enters the new email interface 470 on the mobile phone A, he can click the control 471 for adding an attachment, and in response to the user's operation of clicking the control 471, As shown in (b) of FIG. 9A , the mobile phone A can display a tab page (Tab) as the most recent interface 472, in the interface 472, a selection box is displayed on the icon of each media file for the user to select. For example, a selection box 473b may be displayed on the icon of the media file 473a. In response to the user's operation of clicking on the media file 473a (ie, cover design.pptx), as shown in (c) of FIG. 9A , the display style of the selection box on the media file 473a changes, indicating that the file is selected. The upper part of the interface 472 may also include prompt information 474, prompting the user that "1/20 has been selected", that is, the user can select a total of 20 files, and one is currently selected. In response to the operation of the user clicking the finish button 475, as shown in (d) in FIG. 9A, the mobile phone A can return to display the new email interface 470. At this time, an attachment display area 476 is added to the newly created email interface 470, and the attachment display area 476 is added. In area 476, user-selected attachments (eg, coverdesign.pptx) may be displayed. Optionally, the user may click on control 477 to delete the currently selected attachment.

In another possible implementation, as shown in (a) of FIG. 9A , when the user enters the new email interface 470 on the mobile phone A, he can click the control 471 for adding an attachment to the email, and in response to the user clicking the control 471 operation, as shown in (a) of FIG. 9B , the mobile phone A can display the tab page (Tab) as the most recent interface 472. In the interface 472, a selection box is displayed floating on the icon of each media file, which is available for the user choose. In response to the user's operation of clicking on the icon 480 of the browse tab, as shown in (b) in FIG. 9B , the mobile phone A may display an interface 480a for browsing the tab, in the interface 480a, in response to the user selecting the Mate 30 pro (mobile phone B). ) operation, as shown in (c) of FIG. 9B , the mobile phone A can display the interface 480b, and the interface 480b displays the contents of the recent tab of the Mate 30pro (mobile phone B) by default. The interface 480b may include prompt information 483 for prompting the user that the media file of the Mate 30 pro (mobile phone B) is currently being browsed. When the user selects the media file 481 (ie A-002.jpg) and the media file 482 (ie the cover design.pptx), the prompt message 484 can prompt the user that "2/20 has been selected", that is, the user can select a total of 20 files , two are currently selected. Then, in response to the user's operation of clicking the finish button 485, as shown in (d) of FIG. 9B, the mobile phone A can return to display the new email interface 470. At this time, an attachment display area 486 is added in the In the attachment display area 486, attachments selected by the user (eg, A-002.jpg and cover design.pptx) may be displayed.

The embodiments of the present application support searching, accessing, and sharing media files from third-party applications across devices, without first downloading media files of other devices to the local area, and without requiring users to perform cumbersome operations, which can improve user experience.

The software system of the above mobile phone (eg, mobile phone A or mobile phone B) may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiments of the present application take an Android system with a layered architecture as an example to illustrate the software structure of a mobile phone (mobile phone A or mobile phone B). Of course, the mobile phone may also be a Hongmeng system, an IOS system, or other operating systems, which are not limited in this embodiment of the present application.

As shown in FIG. 10A , the software architecture of the mobile phone may include an application layer and a framework layer.

The application layer may include a series of application packages, and the application package may include, for example, applications such as mail, camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

The framework layer provides an application programming interface (API) and a programming framework for applications in the application layer. The framework layer includes some predefined functions.

Exemplarily, the framework layer may include a unified operation framework 001, a distributed rights management module 002, a distributed database (also referred to as a distributed data management module) 003, a device management module (also referred to as a Peers management module) 004, Distributed storage module 005 and cross-device transfer module 006. The function of each module is briefly described below.

Unified operation framework 001: It can encapsulate and shield the communication differences between near-field communication and far-field communication, as well as the storage differences between this device and other devices, and provide a unified northbound API to the application, so as to realize the management of the device by the application (adding, operations such as authentication, addition, deletion, modification, query (search), browsing, sharing, backup, and migration of media objects (ie, media files).

Distributed rights management module 002: used to provide rights management for distributed media access, including application rights management and user account rights management.

Distributed database 003: used to realize "plug and play access" of media metadata across devices based on full synchronization, incremental synchronization and real-time synchronization capabilities. "Plug-and-play access" refers to storing media metadata of other devices (eg, phone B) on a certain device (eg, phone A) in advance, so that there is no need to spend time acquiring the media metadata of other devices during access , for quick access to media metadata from other devices. The media metadata is data describing attribute information of media data (media content/media file). For example, the identification, type (audio, video, picture, etc.), size, storage location, etc. of the media file may be included.

Device management module 004: used for device discovery (for example, discovering other devices in the same local area network) and state management (for example, the connection with other devices), and can respond to the system's device chain establishment (connection establishment) and link disconnection (disconnection). Connect) event, trigger media metadata synchronization and state update, and notify the distributed database 003 of application data and state changes.

Distributed storage module 005: used for media data synchronization, thumbnail data synchronization and media data access across devices, caching (including transparent caching and stateful caching), and consistency maintenance (eg, intelligent aging).

Cross-device transmission module 006: used to control the cross-device transmission of media metadata and media data (for example, thumbnail data), and can receive media metadata and media data from other devices, or send media metadata and media data to other devices .

It should be noted that different modules have different interaction interfaces, and the functions and roles of different interaction interfaces are different.

For example, the interaction interface 10 between the application layer and the unified operation framework 001 is a northbound API interface, which is an interface provided for applications to operate media objects.

The interactive interface 20 between the unified operation framework 001 and the distributed rights management module 002 is an authentication and authorization interface, which is an interface provided to the unified operation framework 001 for application authentication, account authentication, and media object rights management.

The interactive interface 21 between the unified operation framework 001 and the distributed database 003 is a database operation interface, which is an interface for adding, deleting, modifying and querying media metadata provided to the unified operation framework 001 . The media metadata includes media metadata of local, cloud, and distributed terminals (ie, other devices).

The interaction interface 22 between the unified operation framework 001 and the cross-device transmission module 006 is a remote control interface, which is an interface for collaborative editing, cross-device copy/paste business control data, and content data transmission provided to the unified operation framework 001 .

The interactive interface 30 between the device management module 004 and the distributed database 003 is a device change notification and query interface, an interface provided to the distributed database 004 for remote device state change notification and real-time state query. The remote device may include a PC, a PAD, a mobile phone, a NAS, a cloud server, and other devices.

The interactive interface 31 between the distributed database 003 and the cross-device transmission module 006 is a metadata synchronization interface, which is an interface for cross-device query and broadcast data transmission of metadata provided to the distributed database 003 .

The interactive interface 32 between the distributed database 003 and the distributed storage module 005 is a file operation interface, which is an operation interface for local, cloud, and distributed media files provided to the distributed database 003, and supports the addition of media files across devices. , delete, modify and query, etc.

The interaction interface 40 between the device management module 004 and the cross-device transmission module 006 is a device discovery and monitoring interface, and is a transmission interface for device state change information provided to the device management module 004 .

The interactive interface 50 between the distributed storage module 005 and the cross-device transmission module 006 is a file cache and synchronization interface, which is a cross-device media file transmission interface provided to the distributed storage module 005 .

In addition, the framework layer may also include an activity manager, a window manager, a content provider, a view system, a resource manager, a notification manager, and the like, which are not limited in this embodiment of the present application. Among them, Activity Manager (Activity Manager): used to manage the life cycle of each application. Applications usually run in the operating system in the form of Activity. For each Activity, there will be a corresponding application record (ActivityRecord) in the activity manager, and this ActivityRecord records the state of the application's Activity. The activity manager can use this ActivityRecord as an identifier to schedule the Activity process of the application. Window Manager (WindowManagerService): used to manage the graphical user interface (graphical user interface, GUI) resources used on the screen, which can be used for: obtaining the display screen size, creating and destroying windows, displaying and hiding windows, Layout, focus management, input method and wallpaper management, etc.

The software architecture of the handset may also include system libraries and kernel layers (not shown in Figure 10A). The system library and the kernel layer can be called the underlying system, and the underlying system includes the underlying display system for providing display services. For example, the underlying display system includes the display driver in the kernel layer and the surface manager in the system library.

A system library can include multiple functional modules. For example: surface manager, Media Libraries, OpenGL ES, SGL, etc. The Surface Manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc. OpenGL ES is used to implement 3D graphics drawing, image rendering, compositing, and layer processing. SGL is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers, camera drivers, audio drivers, and sensor drivers.

It should be noted that the device management module 004 can manage both near-field devices (eg, device discovery, device connection) and far-field devices (eg, device discovery, device connection), and the cross-device transmission module 006 Data synchronization/data transmission between near-field devices and data synchronization/data transmission between far-field devices can be performed.

Before device discovery and data synchronization, at least one of the following preconditions must be met: 1) Create a new device management table to store near-field device/far-field device information that has been connected to the local device; 2) Create a new data synchronization state table for Store the synchronization status of the local media data of the near-field device/far-field device; 3) Create a new album set/album table, which is used to store the album set and album information; 4) Create a new media asset/album relationship correspondence table, which is used to store media assets and The relationship of the album; 5) The near-field device/far-field device registers the local media data monitoring of the near-field device/far-field device.

The process of device discovery may include: receiving online/offline events of devices (near-field devices/far-field devices), and updating status information corresponding to the devices in the device management table. When the device is disconnected, the media data changes are recorded in the data synchronization state table.

The process of data synchronization may include: when the local device is connected to the near-field device/far-field device, the local-end device sends a data synchronization request to the near-field device/far-field device, and the near-field device/far-field device retrieves the data from the data synchronization state table. Extract the synchronization status of the media object from the media database, extract the changed data from the media database, and synchronize it to the local device. Exemplarily, the near-field device/far-field device can create a new album set/album table, media asset/album relationship correspondence table, and according to the link status of the device in the device management table, from the album set/album table, media asset/album relationship correspondence table. The media file metadata synchronization (full synchronization, incremental synchronization, real-time synchronization) obtained from the table and MediaProvider database table is sent to the local device, and the synchronization of thumbnails is completed at the same time. When the near-field device/far-field device goes online for the first time, perform full synchronization of media metadata/thumbnail with the local device; when the near-field device/far-field device is not online for the first time, perform media metadata/thumbnail synchronization with the local device. Incremental synchronization; when the near-field device/far-field device and the local device are online, perform real-time synchronization of metadata/thumbnails.

In addition, abnormal recovery can be performed after the near-field device/far-field device and the local device are disconnected. Exemplarily, the near-field device/far-field device obtains the incremental metadata that needs to be synchronized in the album set/album table, and the corresponding table of media assets/album relationship according to the data status in the device management table and the data synchronization status table, and synchronizes the data. To the local device, and update the data synchronization status table. After the local device receives the synchronized metadata, it completes the data update of the local device's album set/album table, media asset/album relationship correspondence table, and synchronously updates the local near-field device/far-field device data (MediaProvider file surface). 3. After the local device receives the synchronization of the thumbnails of the near-field device/far-field device, it updates the thumbnails to the buffer.

The timing relationship between device online and data synchronization may be: when no device is online (local data version number (version) = 0), full synchronization is not started; incremental synchronization is not started; and the data status table is cleared. When the device goes online for the first time, full synchronization can be performed; incremental synchronization is not initiated; when the data version number of the local device is greater than the data version number of the remote device, real-time synchronization will be pulled up, that is, the data version number of the local device is greater than the data version number of the remote device , perform real-time synchronization. When the device is not online for the first time, it will not automatically start full synchronization. When the incrementally synchronized structured query language (SQL) file (the SQL file includes the metadata of the updated media file) is larger than 1 megabyte (mb) /M), full synchronization will be started, that is, when the incrementally synchronized SQL file is larger than 1M, full synchronization can be started. When it is determined to perform full synchronization, the data version number of the local device is +1. When the database (datebase, db) file (eg, SQL file) is successfully sent, the data version number of the peer device is set to the data version number (ie, the data version number) of the local device before full synchronization. When it is determined to perform incremental synchronization, the data version number of the local device is +1; when the SQL file is successfully sent to the peer, the data version number of the peer device is set to the current local device data version number (that is, the data version number + 1) . The data version number is used to record the number of data synchronizations, and the data version number can be incremented by one (+1) for each synchronization.

Exemplarily, in the far-field communication, as shown in FIG. 10B , the device management module 004 of the mobile phone 100 may perform device discovery with the device management module 004 of the mobile phone 200 through the device cloud server. The cross-device transmission module 006 of the mobile phone 100 can establish a device connection with the cross-device transmission module 006 of the mobile phone 200 through a peer-to-peer (P2P) server, so that data can be directly performed between the far-field devices (that is, the mobile phone 100 and the mobile phone 200). transmission. Among them, the far-field device communication protocol can be used for communication between the far-field devices, and the far-field device communication protocol includes Ethernet, 2/3/4/5G, and the like. The device management module 004 can also be used to determine the specific message format, transmission rate, protocol specification, etc. when communicating between far-field devices.

Among them, the P2P server can adopt technologies such as network address translation (NAT) session traversal utilities for NAT (STUN) and traversal using relays around NAT (TURN). The far-field device establishes a connection, which can implement P2P communication (ie, direct communication) between two far-field devices (for example, the mobile phone 100 and the mobile phone 200 ).

Exemplarily, in the near field communication, the mobile phone 100 and the mobile phone 200 can access the same local area network (for example, a Bluetooth local area network or a WIFI local area network), and the device management module 004 can exchange information with the device management module 004 of the mobile phone 200 based on the local area network, thereby Near-field devices can be managed. The cross-device transmission module 006 of the mobile phone 100 can exchange information with the cross-device transmission module 006 of the mobile phone 200 based on the local area network, so as to perform data transmission with the near-field device. Near-field device communication protocols can be used for communication between near-field devices. Near-field device communication protocols include WIFI, bluetooth (BT), low energy bluetooth (BLE), NFC, infrared (wire), universal string At least one of the universal serial bus (USB). The device management module 004 can also be used to determine the specific message format, transmission rate, protocol specification, etc. when communicating between near-field devices.

In the embodiment of the present application, after the mobile phone A and the mobile phone B are connected, data synchronization can be performed. The data synchronization includes full synchronization and incremental synchronization.

As shown in Figure 11A, it is a signal interaction diagram of data synchronization, including:

s1a. Mobile phone A monitors media metadata changes and records the change status.

s1b. Mobile phone A monitors the change of media metadata and records the change status.

s1n, mobile phone A monitors the change of media metadata and records the change status.

The state tree of the distributed database in mobile phone A can always monitor whether the media metadata is changed, and record the change state. For example, after the user takes a photo through mobile phone A, the media metadata will be changed, and the state tree can monitor the change of the media metadata and record the data of the photo.

When mobile phone A and mobile phone B are connected for the first time, step s2 and step s3 can be performed.

s2. Perform full data synchronization between mobile phone A and mobile phone B (that is, full synchronization).

Full synchronization refers to the cross-device synchronization of all media metadata, user accounts, and device attribute information between devices.

s3. The state tree of mobile phone A records the synchronization state.

The state tree of mobile phone A can record all the media metadata, user account and device attribute information of mobile phone B.

When the mobile phone A and the mobile phone B are subsequently connected (the nth connection, n is greater than or equal to 2), steps s4 to s6 may be performed.

s4. The state tree of mobile phone A obtains the incremental synchronization list.

The incremental synchronization list is a list of change information of media objects such as audio, video, pictures, and files after the last (previous) synchronization, including file name, path, creation time, modification implementation, size, playback duration, etc.

s5. Perform incremental data synchronization (ie, incremental synchronization) between mobile phone A and mobile phone B.

Incremental synchronization is the cross-device synchronization of the metadata of the changed media assets on the device after the device is disconnected and connected again. The synchronization content includes the changed data, user account, device information, and change type (for example, add, modify, delete) .

s6. The state tree of mobile phone A updates the synchronization state.

It should be noted that the mobile phone A and the mobile phone B can perform near field communication or far field communication. Near field communication can complete information exchange between devices through routers and other devices. Far-field communication can complete the information exchange between devices through the server.

It should be noted that the communication mode of mobile phone A and mobile phone B is not fixed and can be dynamically switched. For example, when the user controls the mobile phone B at home through the mobile phone A in the company, the mobile phone A and the mobile phone B perform far-field communication, using the far-field device communication protocol. If the user returns home, both mobile phone A and mobile phone B are connected to the home router network. At this time, mobile phone A and mobile phone B perform near field communication using the near field device communication protocol.

Exemplarily, as shown in FIG. 11B , taking the process of performing full synchronization between the local device (mobile phone A) and the near-field device (mobile phone B) as an example, the following steps are included:

S101, the local device (mobile phone A) and the near-field device (mobile phone B) perform device online and offline management.

When the local device (mobile phone A) and the near-field device (mobile phone B) are connected for the first time, the local device can receive the device online/offline events of the near-field device. If there is no near-field device related information in the device management table of the local device, full synchronization can be performed.

S102, the local device sends an online notification to the near-field device.

S103 , after receiving the online notification from the local device, the near-field device can synchronize the database file (the metadata of the media file) in the MediaProvider to the local device, and also synchronize the related thumbnail files to the local device at the same time.

S104 , after receiving the synchronization of the thumbnails of the near-field devices, the local device updates the thumbnails to the buffer.

S105: The local device sends a thumbnail synchronization status notification to the near-end device.

S106, the local device receives the database file of the near-field device.

Exemplarily, the local device stores the database file of the near-field device in the file directory of the MediaProvider of the local device, and the near-field device database of the local device can be named with the self_id in the device management table.

S107: The local device sends a metadata synchronization state notification to the near-end device.

S108, the local device updates the device status table.

The local device can write the current state information of the near-end device into the device management table.

As shown in Figure 11C, incremental synchronization may include the following steps:

S201, the local device (mobile phone A) and the near-field device (mobile phone B) perform device online and offline management.

When the local device (mobile phone A) and the near field device (mobile phone B) are subsequently connected, the local device can receive the device online/offline events of the near field device. If the device management table of the local device already has information related to the current near-field device, perform incremental synchronization.

S202, the local device sends an incremental synchronization request to the near-field device.

S203, the near-field device sends an SQL statement and a thumbnail image of the changed data to the local device.

Wherein, the SQL statement for changing the data includes the metadata of the updated media file. The SQL file is a database script file, which is a standard data query language used in the database. SQL statements are included in the SQL file. After synchronizing the SQL file to the peer device, and executing the SQL file on the peer device, the metadata of the updated media file can be refreshed to the database of the peer device.

After the near-field device receives the online notification from the local device, the near-field device reads the device data version number from the device status table, compares it with the data version number of the changed data in the synchronization status table, and generates the SQL statement for the data change. Enter the text file, and obtain the thumbnail of the changed data, and then complete the synchronization of the metadata and the thumbnail through the data transmission channel.

S204, the distributed database of the local device parses the SQL file, and inserts the updated metadata into the database.

After the local device receives the text of the SQL statement for changing metadata synchronized by the near-field device, it can parse the text and execute the SQL statement to update the album set/album table, media assets/album in the near-field database of the local device Corresponding data in relational tables and other tables. In addition, when the size of the incrementally synchronized SQL file is greater than 1M, full synchronization can be performed.

S205: The local device sends a metadata synchronization state notification to the near-end device.

S206 , after receiving the synchronization of the thumbnails of the near-field devices, the local device updates the thumbnails to the buffer.

S207: The local device sends a thumbnail synchronization status notification to the near-end device.

S208, the local device writes the current state information of the near-end device into the device management table.

In a possible implementation manner, after mobile phone A and mobile phone B are connected, real-time data synchronization can be performed. The real-time synchronization of data is to perform cross-device synchronization in real time when the media data changes due to user operations (such as downloading pictures, taking pictures, etc.) while the device remains connected. The synchronization content includes the changed media data, user account, device information, and change type. Wait.

Real-time synchronization needs to meet at least one of the following preconditions: 1) When the local device data version number is equal to the remote device data version number, real-time synchronization can be performed. If the data version number of the local device is greater than that of the remote device, incremental synchronization can be performed. 2) During real-time synchronization, when the local data version number is equal to 0, the data status table and the peer device status table can be cleared.

As shown in FIG. 11D , it is a signal interaction diagram of real-time synchronization of data, including:

1101. The application program of the mobile phone A applies to the unified operation framework of the mobile phone A for adding/deleting/modifying media files.

When mobile phone A and mobile phone B are in a connected state, real-time synchronization can be triggered by an operation of a file by a user application (eg, a file manager). Alternatively, real-time synchronization can also be triggered automatically at preset time intervals. The media files may include files such as pictures, videos, audios, and documents. Applications can include third-party applications (eg,

) and system applications (eg, camera applications).

For example, if the user takes a photo through the camera of mobile phone A, the camera application can apply to the unified operation framework to add a new photo.

According to the link status of the devices in the device management table, mobile phone A can obtain the metadata of the changed media files from the album set/album table, the media asset/album relationship correspondence table, and the MediaProvider database table, write it into the SQL file, and synchronize it to the mobile phone in real time. B, the synchronization of thumbnails is completed at the same time. Mobile phone A can perform the following steps:

1102. The unified operation framework of the mobile phone A notifies the distributed database of the mobile phone A to update the media metadata.

For example, media metadata of photos taken by the user may be added to the distributed database of mobile phone A, such as the size and storage location of the photos taken by the user.

1103. The distributed database of the mobile phone A notifies the distributed storage module of the mobile phone A to update the media file.

The distributed storage module of the mobile phone A stores the photos taken by the user.

1104. The distributed database of mobile phone A notifies the unified operation framework of mobile phone B of the synchronously changed media metadata.

The changed media metadata can be included in the SQL file. After mobile phone B receives the SQL file synchronized by mobile phone A, it completes the data update of mobile phone B's album set/album table and the corresponding table of media assets/album relationship according to the changes, and Synchronously update the local near-field device data (MediaProvider's file table). Among them, MediaProvider stores information of multimedia files such as pictures, videos, and audios, and provides basic methods such as addition, deletion, modification, and search, which can be used by applications such as video players, music players, and galleries.

Step 1103 and step 1104 may be performed simultaneously.

1105. The unified operation framework of the mobile phone B notifies the distributed database of the mobile phone B to update the changed media metadata.

1106. The distributed database of the mobile phone B requests the first type of thumbnails of the original media file (original media data) from the distributed database of the mobile phone A.

The original media file may be, for example, an original image of a picture, an original file of a video, an original file of an audio, and the like. The thumbnail of the original media file may be, for example, a thumbnail of a picture, a thumbnail of a cover of an audio or video, and the like. The thumbnails of the original media files can be classified into two types according to their sizes. The size of the thumbnails of the first type can be between 10K and 20K, for example, 10K, 15K or 20K. The resolution of the first type of thumbnails may be 256*256. Refer to the description of step 1109 for the second type of thumbnails.

1107. The distributed database of mobile phone A sends the first type of thumbnail images of the original media file to the distributed database of mobile phone B.

1108. The distributed database of the mobile phone B instructs the distributed storage module of the mobile phone B to cache the thumbnails of the first type of the original media file.

The distributed storage module of the mobile phone B can cache the thumbnails of the first type of the original media files (the user does not perceive the caching process) into the buffer. Among them, the cache represents the state after the data reading (pulling) is completed.

1109. The distributed database of the mobile phone B requests the second type of thumbnail images of the original media file from the distributed database of the mobile phone A.

The size of the thumbnail of the second type of the original media file is about 200K, for example, it can be 150K, 180K, 200K, 230K and so on.

1110. The distributed database of mobile phone A sends the second-type thumbnail of the original media file to the distributed database of mobile phone B.

1111. The distributed database of the mobile phone B instructs the distributed storage module of the mobile phone B to cache the second type of thumbnails of the original media file.

The distributed storage module of the mobile phone B instructs to cache the thumbnails of the second type of the original media files.

1112. The unified operation framework of the mobile phone B notifies that the application media file of the mobile phone B is changed.

Assuming that mobile phone A and mobile phone B are connected, as shown in (a) of FIG. 11E, in response to the user's operation of clicking the camera button 501 on mobile phone B, as shown in (b) of FIG. 11E, a photo 502 can be obtained. Based on the real-time synchronization method shown in FIG. 11E , as shown in (c) of FIG. 11E , the first type of thumbnail (ie, picture 503 ) of the photo (original image) newly taken by mobile phone B can be updated in real time to mobile phone A’s on the interface. In addition, the second-type thumbnail of the picture 503 can also be cached in the mobile phone A, so that when the user clicks on the picture 503, a larger and clearer picture can be viewed.

In this way, instead of storing a copy of the original media files of other devices on each device, it is only necessary to cache the thumbnails of the original media files of other devices on each device (the first type of thumbnails, the second type of thumbnails ), which can reduce the risk of bursting the capacity of personal devices, and also avoid the problem of storing data in the cloud and re-downloading (very troublesome) when accessing cloud data.

For another example, as shown in (a) of FIG. 8A , in response to the user clicking the share operation option 452, the mobile phone A can share the media files on the mobile phone B to a third-party application or a system application. The mobile phone A may share the second type of thumbnails of the media files by default, or the user may choose to share the original media files.

When the real-time synchronization is successful, the local device can update the device status table and set the data version number of the peer device as the current local device data version number; when the real-time synchronization fails, the data version number of the local device is incremented by one (+1) .

In order to achieve a consistent experience of media access across devices and local media access, transparent caching technology can be used. The transparent cache technology can actively cache the file when the file is read for the first time. If the user needs the file next time, the system can retrieve it from the local cache. Transparent caching technology can include processes such as automatic caching, automatic write-back, automatic aging and automatic update. The automatic caching means that the media library can automatically cache the media files of the remote device to the local. The media library can shield the location difference of media files, and users access the files of the remote device in the same way as the local files, for example, they can be accessed based on a uniform resource identifier (URI) or storage path. Auto-write-back means that when a user actively saves a media file or an application automatically saves a media file, the media library automatically synchronizes the saved media file to the remote end and replaces the remote historical file. Automatic aging means that the media library automatically clears the cold data outside the aging period (for example, two weeks, one month, etc.) without additional processing by the developer. Automatic update means that after the media file of the remote device is modified, the media library automatically updates the local cache according to the new file (modified file) of the remote end.

As shown in FIG. 12, the automatic caching process may include steps 1201-1203, wherein:

1201. The distributed database of mobile phone A requests the second type of thumbnail images of the original media file from the distributed database of mobile phone B.

Phone A can automatically cache some media files. For example, as shown in FIG. 6A , the mobile phone can automatically cache the media files corresponding to the thumbnails (the first type of thumbnails) that fill the screen under the recent tab 431 (the media files here refer to the second type of thumbnails of the original media files). Sketch map). As shown in FIG. 6B , the mobile phone can automatically cache the media files covering the screen under the picture tag 432 . As shown in FIG. 6C , the mobile phone can automatically cache the media files that cover the screen under the video tag 433 . As shown in FIG. 6D , the mobile phone can automatically cache the media files that cover the screen under the picture tag 434.

In a possible design, mobile phone A can analyze the user's preferences and behavioral habits based on the AI algorithm, predict the user's operation, and cache the cross-device media files that the user may open locally in advance.

1202. The distributed database of the mobile phone B sends the media file to the distributed database of the mobile phone A.

1203. The distributed database of the mobile phone A caches the media files in the distributed storage module of the mobile phone A.

The automatic write-back process may include steps 1204-1208, wherein:

1204. The distributed database of the mobile phone A sends the content editing information of the cached file (ie, the cached media file) to the distributed storage module of the mobile phone A.

1205. The distributed database of mobile phone A sends the write-back status of the content of the cache file to the distributed database of mobile phone B.

1206. The distributed database of the mobile phone B notifies the distributed storage module of the mobile phone B of the content of the updated media file.

The distributed storage module of the mobile phone B updates the content of the media file.

1207. The distributed database of the mobile phone B updates the media metadata.

1208. Perform media metadata synchronization between the distributed database of the mobile phone B and the distributed database of the mobile phone A.

The automatic aging process may include step 1209, wherein:

1209. The distributed database of the mobile phone A notifies the distributed storage module of the mobile phone A to age the cache files based on the aging policy.

The aging strategy may be, for example, purging cold data (unused data) every two weeks or every month. For example, the cold data includes thumbnails of media files whose access times are below a preset threshold.

The automatic update process may include steps 1210-1215, wherein:

1210. The distributed database of the mobile phone B sends the local (mobile phone B local) media file update status to the distributed storage module of the mobile phone B.

The distributed storage module of the mobile phone B updates the media files according to the update situation of the local (mobile phone B local) media files.

1211. The distributed database of the mobile phone B updates the media metadata.

The distributed database of the mobile phone B can update the corresponding media metadata according to the update situation of the local media files.

1212. The distributed database of the mobile phone B synchronizes the media metadata with the distributed database of the mobile phone A.

1213. The distributed database of mobile phone A requests the updated media file from the distributed database of mobile phone B.

The updated media file refers to the second type of thumbnails of the updated original media file.

1214. The distributed database of the mobile phone B sends the updated media file to the distributed database of the mobile phone A.

1215. The distributed database of the mobile phone A notifies the distributed storage module of the mobile phone A to update the cache file.

The distributed storage module of the mobile phone A can update the previous (last cached) cache file according to the updated media file.

In order to achieve a high-performance user experience similar to local playback for cross-device playback, a lightweight streaming technology can be used. Lightweight streaming includes a first-play phase and a buffered-play phase.

As shown in Figure 13, the first play stage may include steps 1301-1307, wherein:

1301. The application program of the mobile phone A requests the unified operation framework of the mobile phone A to play the remote media file.

After the user clicks the play button of the remote media file (eg, a video of the mobile phone B) for the first time on the mobile phone A, the application program of the mobile phone A can request the unified operation framework of the mobile phone A to play the remote media file. As shown in (a) of FIG. 14 , in response to the user's operation of clicking all videos 490 on the interface 430 , as shown in (b) of FIG. 14 , the mobile phone can display all the video interfaces 491 , in response to the user clicking on the interface 491 For the operation of the video 492 (the duration is 10s), as shown in (c) in Figure 14, the mobile phone can display an interface 493, and the interface 493 can include a play button 494. In response to the operation of the user clicking the play button 494 for the first time, the mobile phone A's The application can request the unified operation framework of the mobile phone A to play the remote media file (ie the video 492 ).

1302. The unified operation framework of the mobile phone A obtains the media file resources from the distributed storage module of the mobile phone A.

1303. The distributed storage module of the mobile phone A requests the unified operation framework of the mobile phone A to start the streaming agent. The streaming proxy is the streaming server proxy, which can encapsulate the media file information pulled across the devices into a streaming media format and send it to the application. The application is unaware of the transfer of media information across devices.

1304. The distributed storage module of mobile phone A obtains and caches the media file from the distributed storage module of mobile phone B.

The distributed storage module of mobile phone A may obtain media files (eg, video files) from the distributed storage module of mobile phone B in m times and cache them. Among them, m is an integer greater than or equal to 2.

1305. The unified operation framework of the mobile phone A returns the URL of the cached media file to the application program of the mobile phone A.

1306. The unified operation framework of the mobile phone A reads the buffered data from the distributed storage module of the mobile phone A.

The unified operation framework of the mobile phone A can read the buffered data (buffered media data) from the distributed storage module of the mobile phone A in m times.

1307. The application program of the mobile phone A plays the remote media file in a streaming media manner.

The application program of the mobile phone A obtains the buffered data in m times from the unified operation framework of the mobile phone A, and can play the buffered media file in m times.

The buffer playback stage may include steps 1308-1310, wherein:

1308. The application program of the mobile phone A may request the unified operation framework of the mobile phone A to play the remote media file.

After the user clicks the play button of the remote media file on the mobile phone A again, the application program of the mobile phone A can request the unified operation framework of the mobile phone A to play the remote media file.

1309. The unified operation framework of the mobile phone A obtains the media file resources from the distributed storage module of the mobile phone A.

1310. The distributed storage module of the mobile phone A returns the URI of the buffered file to the application program of the mobile phone A, and the application program of the mobile phone A directly plays the remote media file.

In this way, the playback end does not need to wait for the media file (for example, the original video file) to be completely downloaded before starting playback, and can play in real time, thereby realizing a high-performance user experience similar to local playback.

As shown in FIG. 15 , an embodiment of the present application provides a data synchronization method, including:

1501. The first device acquires a media file update event; wherein the media file update event is used to add, modify or delete a first media file.

The media file update event may be triggered by a user, or automatically triggered by the first device based on a preset policy. It should be noted that the user can trigger an update event of the local media file on the first device, or can trigger an update event of the local media file of the first device on another device (a device connected to the first device, such as a second device).

Wherein, the first media file includes at least one of pictures, videos, audios, and documents.

1502. The first device updates the metadata corresponding to the first media file in the metadata database, and updates the thumbnail image of the first media file in the media library.

The metadata database stores metadata corresponding to all media files of the first device, and the media library stores thumbnail images of all media files of the first device. For the metadata database, reference may be made to the above description about the distributed database, and for the media library, reference may be made to the above description about the distributed storage module, which will not be repeated here.

The thumbnails of the first media files include thumbnails of the first type, and the size of the thumbnails of the first type ranges from 10K to 20K.

1503. The first device sends a synchronization message to the second device, where the synchronization message includes metadata corresponding to the first media file and a thumbnail image of the first media file.

The synchronization message further includes at least one of a user account, device information of the first device, and an update type of the first media file, where the update type of the first media file includes addition, modification, or deletion.

In a possible design, the first device receives a first request message, where the first request message is used to request a second type of thumbnail image, and the size of the second type of thumbnail image ranges from 100K to 300K; The second device sends a second type of thumbnail image.

In a possible design, the first device may analyze the user's preferences and behavioral habits based on an AI algorithm; predict the media files that the user needs to operate according to the user's preferences and behavioral habits; The thumbnail is sent to the second device.

In a possible design, when the first device is connected to the second device for the first time, the first device synchronizes the metadata corresponding to all media files of the first device and the thumbnail images corresponding to all media files to the second device.

In a possible design, when the first device is connected to the second device for the Nth time, the first device stores the metadata corresponding to the media file updated on the first device after the last synchronization and the thumbnail image corresponding to the updated media file Sync to the second device. Wherein, N is an integer greater than or equal to 2.

In a possible design, the first device deletes the cold data in the cached media file based on a preset period. For example, the cold data includes thumbnails of media files whose access times are below a preset threshold.

In a possible design, when the first device plays the media file of the second device for the first time, the streaming server proxy is started, and the streaming server proxy is used to encapsulate the media file of the second device into a streaming media format; The agent obtains the media files of the second device from the second device in m times and caches them; where m is an integer greater than or equal to 2; the first device plays the cached data.

In a possible design, when the first device plays the media file of the second device for the Nth time, the URI of the media file of the second device is obtained, and the cached data is obtained and played according to the URI; wherein, N is an integer greater than or equal to 2 .

In a possible design, the first device displays a first interface containing the logo of the second device; in response to the user's operation of clicking the logo of the second device on the first interface, the first device displays a second interface, and the second interface One or more thumbnail images of at least one type of media file of the second device are included.

In a possible design, the first interface or the second interface includes a search control, and in response to an operation of inputting a keyword after the user clicks on the search control, the first device displays a third interface, and the third interface includes data from the first device and the third interface. The identifier of the media file related to the keyword searched by the device.

In a possible design, in response to the user's operation of clicking the first thumbnail on the second interface, the first device displays a first pop-up box, and the first pop-up box includes the first operation option; in response to the user clicking the first operation option operation, the first device displays a second pop-up frame, and the second pop-up frame includes one or more application programs or device identifiers; in response to the operation of the user clicking on an application program or a device identifier, the first device shares the first thumbnail image to the device corresponding to the application or device ID that the user clicked.

It should be noted that, the first device in the embodiment shown in FIG. 15 may be the mobile phone A in the foregoing embodiment, and the second device may be the mobile phone B in the foregoing embodiment. Alternatively, the first device may be the mobile phone B in the foregoing embodiment, and the second device may be the mobile phone A in the foregoing embodiment, which is not limited in this application. For parts not described in detail in the embodiment shown in FIG. 15 , reference may be made to the foregoing embodiment, and details are not described here.

Based on the method provided by the embodiment of the present application, after acquiring the media file update event, the first device can update the metadata corresponding to the first media file in the metadata database, and update the thumbnail of the first media file in the media library; The device may send a synchronization message to the second device, where the synchronization message includes metadata corresponding to the first media file and a thumbnail image of the first media file. In this way, the metadata database and the media library can be automatically synchronized between the first device and the second device, data sharing across devices can be easily and conveniently achieved, and frequent manual operations by the user are not required, which can improve user experience.

Other embodiments of the present application provide an electronic device (such as the electronic device 200 shown in FIG. 2 ), the electronic device may include: a communication module, a memory, and one or more processors. The communication module and memory are coupled to the processor. The memory is used to store computer program code comprising computer instructions.

Another embodiment of the present application provides a chip system. As shown in FIG. 16 , the chip system includes at least one processor 1601 and at least one interface circuit 1602 . The processor 1601 and the interface circuit 1602 may be interconnected by wires. For example, interface circuit 1602 may be used to receive signals from other devices (eg, memory of an electronic device). As another example, the interface circuit 1602 may be used to send signals to other devices (eg, the processor 1601).

For example, the interface circuit 1602 may read instructions stored in memory in the electronic device and send the instructions to the processor 1601 . When the instructions are executed by the processor 1601, the electronic device (such as the electronic device 200 shown in FIG. 2) can be made to execute each step in the above embodiments.

For another example, the interface circuit 1602 may read the instructions stored in the memory in the server and send the instructions to the processor 1601 . When the instructions are executed by the processor 1601, the server can be caused to perform the steps in the above-mentioned embodiments.

Certainly, the chip system may also include other discrete devices, which are not specifically limited in this embodiment of the present application.

From the description of the above embodiments, those skilled in the art can clearly understand that, for the convenience and brevity of the description, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be allocated by Different functional modules are completed, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be Incorporation may either be integrated into another device, or some features may be omitted, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or may be distributed to multiple different places . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, which are stored in a storage medium , including several instructions to make a device (may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes.

The above contents are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the present application should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

A data synchronization method, characterized in that the method comprises:

The first device acquires a media file update event; wherein, the media file update event is used to add, modify or delete the first media file;

The first device updates the metadata corresponding to the first media file in the metadata database, and updates the thumbnail of the first media file in the media library;

The first device sends a synchronization message to the second device, where the synchronization message includes metadata corresponding to the first media file and a thumbnail image of the first media file.
The method of claim 1, wherein:

The synchronization message further includes at least one of a user account, device information of the first device, and an update type of the first media file, where the update type of the first media file includes addition, modification, or deletion.
The method according to claim 1 or 2, characterized in that,

The thumbnails of the first media file include thumbnails of a first type, and the size of the thumbnails of the first type ranges from 10 kilobytes to 20 kilobytes.
The method according to any one of claims 1-3, wherein the method further comprises:

The first device receives a first request message, where the first request message is used to request a thumbnail image of a second type, and the size of the thumbnail image of the second type ranges from 100 kilobytes to 300 kilobytes;

The first device sends the second type of thumbnails to the second device.
The method according to any one of claims 1-4, wherein,

The first media file includes at least one of pictures, videos, audios, and documents.
The method according to any one of claims 1-5, wherein when the first device is connected to the second device for the first time, the method further comprises:

The first device synchronizes the metadata corresponding to all media files of the first device and the thumbnail images corresponding to all media files to the second device.
The method according to claim 6, wherein when the first device is connected to the second device for the Nth time, N is an integer greater than or equal to 2, and the method further comprises:

The first device synchronizes the metadata corresponding to the media file updated on the first device and the thumbnail image corresponding to the updated media file to the second device after the last synchronization.
The method according to any one of claims 1-7, wherein the method further comprises:

The first device analyzes the user's preferences and behavioral habits based on the artificial intelligence AI algorithm;

Predict the media files that the user needs to operate according to the user's preferences and behavioral habits;

Sending thumbnail images of the second type of media files that the user needs to operate to the second device.
The method according to any one of claims 1-8, wherein,

The first device deletes cold data based on a preset period; wherein the cold data includes thumbnails of media files whose access times are lower than a preset threshold.
The method according to any one of claims 1-9, wherein the method further comprises:

When the first device plays the media file of the second device for the first time, a streaming server proxy is started, and the streaming server proxy is used to encapsulate the media file of the second device into a streaming media format;

The first device obtains and caches the media files of the second device from the second device in m times by the streaming server proxy; wherein, m is an integer greater than or equal to 2;

The first device plays the cached data.
The method of claim 10, wherein:

When the first device plays the media file of the second device for the Nth time, it obtains the uniform resource identifier URI of the media file of the second device, obtains the cached data according to the URI, and plays it; wherein, N is greater than An integer equal to 2.
The method according to any one of claims 1-11, wherein the method further comprises:

The first device displays a first interface that includes an identification of the second device;

In response to the user's operation of clicking on the identifier of the second device on the first interface, the first device displays a second interface, the second interface including at least one type of media file of the second device. One or more thumbnails.
The method of claim 12, wherein:

The first interface or the second interface includes a search control, and in response to an operation of inputting a keyword after the user clicks on the search control, the first device displays a third interface, and the third interface includes a The identifier of the media file related to the keyword searched by the first device and the second device.
The method according to claim 12 or 13, wherein the method further comprises:

In response to the operation of the user clicking the first thumbnail on the second interface, the first device displays a first pop-up frame, and the first pop-up frame includes a first operation option;

In response to the operation of the user clicking the first operation option, the first device displays a second pop-up box, and the second pop-up box includes one or more application programs or device identifiers;

In response to the operation of the user clicking on an application or a device identifier, the first device shares the first thumbnail to the device corresponding to the application or device identifier clicked by the user.
A first device, characterized in that the first device comprises: a wireless communication module, a memory, and one or more processors; the wireless communication module, the memory are coupled to the processor;

Wherein, the memory is used to store computer program codes, and the computer program codes include computer instructions; when the computer instructions are executed by the processor, the first device is made to execute any one of claims 1-14. method described in item.
A computer-readable storage medium, comprising computer instructions;

The computer instructions, when executed on a first device, cause the first device to perform the method of any of claims 1-14.
A data synchronization system, comprising a first device and a second device, wherein the first device executes the method according to any one of claims 1-14.