A content management method, electronic device and system
By introducing a first service into electronic devices to uniformly manage media content on local and remote storage devices, the problem of cumbersome access processes in existing technologies is solved, and simplified multi-terminal storage access and management are achieved, improving access efficiency and user experience.
Patent Information
- Application Number
- CN202210400216.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2022-01-27
- Filing Date
- 2022-04-15
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-04-15
AI Technical Summary
In the existing technology, electronic devices need to use different methods to access the contents of local and external storage devices, resulting in a cumbersome and complex access process and low access efficiency.
By introducing a first service into electronic devices, media content on local and remote storage devices can be managed in a unified manner. This service can be used to obtain and store the identification information of media content, and applications can directly access the content stored on multiple devices, thus achieving unified access and management.
It simplifies the media content access process across multiple storage devices, improves access efficiency and user experience, and supports applications in real-time access and management of media content stored across multiple storage devices.
Smart Images

Figure CN116561459B_ABST
Abstract
Description
[0001] Cross-reference to related applications
[0002] This application claims priority to Chinese Patent Application No. 202210100318.1, filed on January 27, 2022, entitled “A Method for the Integration Management and Presentation of Home Storage Media Content”, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of computers, and more particularly to a content management method, electronic device, and system. Background Technology
[0004] Currently, electronic devices can store or back up their data to external storage devices, thus meeting the need for secure and reliable storage of large amounts of data while saving storage space on the device itself. External storage devices can be, for example, cloud servers or home data centers (HDCs). Content stored locally on the electronic device can be directly accessed and processed by various applications within the device. However, content stored on external storage devices requires access through specific applications associated with those external storage devices. Other applications need to download the content from external storage devices to the device's local storage before accessing it.
[0005] Therefore, current electronic devices need to use different methods to access content in external storage devices and local content on the electronic device, which makes the access process cumbersome and complex, resulting in low access efficiency. Summary of the Invention
[0006] This application provides a content management method for improving the efficiency of electronic devices accessing media content stored on multiple devices.
[0007] In a first aspect, embodiments of this application provide a content management method applied to a first electronic device, the first electronic device including a first service and a first application, the method including: the first service acquiring first information and second information, and storing the first information and the second information; wherein, the first information is used to identify first media content stored in the first electronic device, and the second information is used to identify second media content stored in a second electronic device; the first application acquiring the first information and / or the second information from the first service; and the first application displaying the first information and / or the second information.
[0008] In this method, the first electronic device can obtain identification information of media content stored locally on the first electronic device, as well as identification information of media content stored on the second electronic device, through the same service (i.e., the first service). Based on the identification information of the media content, the first service can uniformly access and manage the media content stored on the first electronic device and other electronic devices. Therefore, applications installed on the first electronic device can directly obtain metadata of the media content stored on the first electronic device and other electronic devices from the first service, and based on the obtained metadata, access the media content stored on the first electronic device itself and other devices, thus easily and quickly achieving access to media content stored on multiple devices. Therefore, this scheme can improve the efficiency of applications in electronic devices accessing media content stored on multiple devices.
[0009] In one possible design, the first electronic device further includes a second application; after the first service acquires the first information and the second information, and stores the first information and the second information, the method further includes: the second application acquiring the first information and / or the second information from the first service; and the second application displaying the first information and / or the second information.
[0010] In this method, different applications installed on the first electronic device can access the media content stored on the first electronic device itself and other devices through the first service, thereby easily and quickly accessing media content stored on multiple devices. Therefore, this solution can improve the efficiency of applications in electronic devices accessing media content stored on multiple devices.
[0011] In one possible design, the first application obtains the first information and / or the second information from the first service, including: the first application obtains the first information and / or the second information from the first service through a first interface provided by the first service.
[0012] In this method, the first service can provide an access interface for applications in the first electronic device, thereby enabling the connection between the first service and the applications in the first electronic device, and facilitating the applications in the first electronic device to access the content stored by the first service through the interface.
[0013] In one possible design, the first metadata corresponding to the first media content contains the first information, and the second metadata corresponding to the second media content contains the second information; the first service obtains the first information and the second information, and stores the first information and the second information, including: the first service obtains the first metadata and stores the first metadata, and the first service obtains the second metadata and stores the second metadata.
[0014] In this method, metadata can be used to indicate media content. By acquiring and storing metadata, the first service can ensure the storage of relatively detailed information related to the media content, facilitating subsequent processing such as access to the media content. Simultaneously, the metadata can be used to determine the identification information of the media content, namely, the first information and the second information. Thus, the identification information of the media content is presented to the user in the application, making it easier for the user to view.
[0015] In one possible design, the first service acquires and stores the second metadata, including: the first service performing a downlink synchronization process; wherein the downlink synchronization process includes: the first service instructing the second electronic device to send downlink synchronization information to the first service; the first service receiving the downlink synchronization information sent by the second electronic device; wherein the downlink synchronization information includes the second metadata and first indication information, the first indication information indicating that: the second metadata is metadata corresponding to media content added to the second electronic device; the first service determining to store the second metadata based on the first indication information; and the first service storing the second metadata.
[0016] In this method, the second media content is the content stored in the second electronic device. The first service in the first electronic device can obtain and store the metadata of the second media content from the second electronic device by performing a downlink synchronization process. The storage space required for metadata is much lower than that required for media content, thus saving storage space on the first electronic device side. At the same time, it ensures that the first electronic device side can determine the information of the second media content stored in the second electronic device, which is convenient for applications to query and access. Based on the downlink synchronization process, the first service can determine the information of newly added media content in the second electronic device and update it accordingly, so as to achieve the effect of the metadata on the first electronic device side changing synchronously with the media content on the second electronic device side. This ensures that the metadata on the first electronic device side can relatively accurately indicate the media content stored on the second electronic device side.
[0017] In one possible design, before the first service acquires and stores the second metadata, the method further includes: the first service acquiring and storing the third metadata; wherein the third metadata is metadata corresponding to third media content stored in the second electronic device; the first service acquiring and storing the second metadata includes: the first service performing a downlink synchronization process; wherein the downlink synchronization process includes: the first service instructing the second electronic device to send downlink synchronization information to the first service; the first service receiving the downlink synchronization information from the second electronic device, wherein the downlink synchronization information includes the second metadata and second indication information; the second indication information is used to indicate that: the second metadata is metadata obtained after modifying the third metadata; the second media content is the third media content or the modified third media content; the first service determines, according to the second indication information, to update the stored third metadata using the second metadata; the first service updates the third metadata to the second metadata.
[0018] In this method, when the media content and metadata are modified in the second electronic device, the first electronic device performs a downlink synchronization process through the first service, which can update the metadata accordingly. This achieves the effect that the metadata on the first electronic device side changes synchronously with the media content on the second electronic device side, so that the metadata stored in the first electronic device corresponds to the media content stored in the second electronic device, thereby ensuring that the metadata on the first electronic device side can relatively accurately indicate the media content stored on the second electronic device side.
[0019] In one possible design, after the first service acquires and stores the second metadata, the method further includes: the first service performing a downlink synchronization process; wherein the downlink synchronization process includes: the first service instructing the second electronic device to send downlink synchronization information to the first service; the first service receiving the downlink synchronization information from the second electronic device, wherein the downlink synchronization information includes third indication information, the third indication information indicating that: the second metadata is metadata corresponding to media content deleted by the second electronic device; the first service determining to delete the second metadata according to the third indication information; and the first service deleting the stored second metadata.
[0020] In this method, when the media content in the second electronic device is deleted, the first service in the first electronic device can obtain the information of the deleted media content in the second electronic device by performing downlink synchronization, thereby deleting the corresponding metadata in the first electronic device. This achieves the effect of the metadata on the first electronic device side changing synchronously with the media content on the second electronic device side, thereby ensuring that the metadata on the first electronic device side can relatively accurately indicate the media content stored on the second electronic device side.
[0021] In one possible design, the first service performs a downlink synchronization process, including: the first service performing the downlink synchronization process when it determines that the start time of the first period has arrived; or, the first service performing the downlink synchronization process when it determines that fourth media content has been stored in the first electronic device; or, the first service performing the downlink synchronization process when it determines that fifth media content stored in the first electronic device has been modified; or, the first service performing the downlink synchronization process when it determines that sixth media content stored in the first electronic device has been deleted.
[0022] In this method, the first service can perform downlink synchronization when the content stored in the first electronic device changes, and can promptly synchronize the changes in the media content in the second electronic device to the first electronic device, thereby improving the consistency between the media content reflected in the metadata of the first electronic device and the media content actually stored in the second electronic device.
[0023] In one possible design, after the first application displays the first information and the second information, or after the first application displays the second information, the method further includes: when the first application determines to delete the second metadata, sending fourth indication information to the first service; wherein the fourth indication information is used to indicate the deletion of the second metadata; and the first service, in response to the received fourth indication information, deletes the second metadata.
[0024] In this method, after the application in the first electronic device displays the identification information of the media content in the second electronic device, it can also delete the metadata corresponding to the media content of the second electronic device stored in the first service. Therefore, this method can support the application to access and manage the metadata of the remote media content stored in the first electronic device without relying on other applications. This makes it easier for the application to access and manage this metadata according to the user's instructions, thereby improving the user experience.
[0025] In one possible design, after the first application obtains the first information and the second information from the first service, or after the first application obtains the second information from the first service, the method further includes: the first application instructing the first service to obtain the second media content identified by the second information; the first service obtaining the second media content from the second electronic device and storing the second media content.
[0026] In this method, the first application can instruct the first service to obtain media content stored in the second electronic device and store the obtained media content. In this way, the first application can control the download and storage of remote media content as needed, without relying on other applications.
[0027] In one possible design, after the first service obtains the second media content from the second electronic device and stores the second media content, the method further includes: the first application obtaining the second media content from the first service; the first application modifying the second media content to a seventh media content, and instructing the first service to update the second media content to the seventh media content and update the second metadata to a fourth metadata; wherein the fourth metadata is the metadata corresponding to the seventh content; the first service updating the second media content to the seventh media content and updating the second metadata to the fourth metadata.
[0028] In this method, the application in the first electronic device can obtain the media content stored in the second electronic device through the first service and can modify the media content. Therefore, this method can support the application to access and manage the metadata of the remote media content stored in the first electronic device without relying on other applications. This makes it easier for the application to access and manage this metadata according to the user's instructions, thereby improving the user experience.
[0029] In one possible design, after the first service updates the second media content to the seventh media content and updates the second metadata to the fourth metadata, the method further includes: the first service performing an uplink synchronization process; wherein the uplink synchronization process includes: the first service sending the seventh media content, the fourth metadata, and fifth indication information to the second electronic device; wherein the fifth indication information is used to indicate: updating the stored second media content to the seventh media content, and updating the stored second metadata to the fourth metadata.
[0030] In this method, after the first application modifies the second media content, the first service, through an uplink synchronization process, enables the second electronic device to modify the second media content accordingly. This achieves the effect of the application on the first electronic device managing the media content on the second electronic device. Since the application can be controlled by the user, the first service and the first application can support the user's control over modifying the media content on the second electronic device from the first electronic device side, without requiring a specific application to achieve this function. Therefore, this method has high versatility and practicality, and can improve the user experience.
[0031] In one possible design, after the first service obtains the second media content from the second electronic device and stores the second media content, the method further includes: when the first application determines to delete the second media content and the second metadata, sending a sixth instruction message to the first service; wherein the sixth instruction message is used to instruct the deletion of the second media content and the second metadata; and the first service, in response to the received sixth instruction message, deletes the stored second media content and the second metadata.
[0032] In this method, the application in the first electronic device can manage the deletion of media content from the second electronic device through the first service without relying on a specific application associated with the second electronic device. Therefore, this method can be applied to more application scenarios, more easily meet user needs, and improve the user experience.
[0033] In one possible design, the method further includes: the first service performing an uplink synchronization process; wherein the uplink synchronization process includes: the first service sending a seventh indication message to the second electronic device; wherein the seventh indication message is used to indicate: deleting the stored second media content and the second metadata.
[0034] In this method, after deleting the second media content, the first service enables the second electronic device to perform the same operation by executing an uplink synchronization process. This achieves the effect of the application on the first electronic device managing the media content on the second electronic device. Since the application can be controlled by the user, the first service and the first application can support users in controlling the deletion of media content on the second electronic device from the first electronic device side, without requiring a specific application to achieve this function. Therefore, this method has high versatility and practicality, and can improve the user experience.
[0035] In one possible design, the first service performs an uplink synchronization process, including: the first service performing the uplink synchronization process when it determines that the start time of the second period has arrived; or, the first service performing the uplink synchronization process when it determines that the second media content stored in the first electronic device has been modified; or, the first service performing the uplink synchronization process when it determines that the second metadata stored in the first electronic device has been deleted.
[0036] In this method, the first service can perform uplink synchronization when the content stored in the first electronic device changes, and can promptly synchronize the changes in the media content in the first electronic device to the second electronic device, thereby improving the consistency between the media content reflected in the metadata of the first electronic device and the media content actually stored in the second electronic device.
[0037] In one possible design, the first electronic device is in a state of being logged into a first user account; before the first service performs the uplink synchronization process, the method further includes: the first service sending a synchronization lock acquisition request to the second electronic device, the synchronization lock acquisition request being used to request the acquisition of a synchronization lock, the synchronization lock being used to indicate: allowing the first electronic device to perform the uplink synchronization process, and prohibiting a target electronic device from performing the uplink synchronization process, the target electronic device being an electronic device other than the first electronic device that is logged into the first user account; the first service receiving synchronization lock indication information from the second electronic device, the synchronization lock indication information being used to indicate the synchronization lock; after the first service performs the uplink synchronization process, the method further includes: the first service sending a synchronization lock release request to the second electronic device, the synchronization lock release request being used to request the release of the synchronization lock.
[0038] In this method, the first service can request a synchronization lock from the second electronic device to ensure that only the first electronic device is performing the uplink synchronization process with the second electronic device at the same time. Therefore, during the uplink synchronization process of the first electronic device, the modification of media content in the second electronic device by other electronic devices can be avoided, thus ensuring the smooth execution of the uplink synchronization of the first electronic device.
[0039] In one possible design, after the first application obtains the first information and the second information from the first service, or after the first application obtains the second information from the first service, the method further includes: the first application determining to obtain the second media content; the first application sending a content acquisition request to the first service, the content acquisition request being used to request the acquisition of the second media content; the first application receiving the second media content from the first service; and the first application displaying the second media content.
[0040] In this method, when an application needs to use the media content source file, it can instruct the first service to obtain the media content source file and obtain the media source file from the first service, thereby enabling the application to access remote media content instantly.
[0041] In one possible design, after the first application sends a content retrieval request to the first service and before the first application receives the second media content from the first service, the method further includes: the first service, in response to the received content retrieval request, requesting the second electronic device to retrieve the second media content; the first service receiving the second media content from the second electronic device and sending the second media content to the first application.
[0042] In this method, the first electronic device stores the metadata of the media content in the second electronic device, rather than the source file of the media content. Therefore, when the application requests to obtain the source file of the media content, the first service can download the source file of the media content from the second electronic device as needed and provide it to the application. This temporary acquisition method enables the application to access the remote media content instantly.
[0043] In one possible design, the first application determines to acquire the second media content by: the first application determining to acquire the second media content in response to an operation for selecting the second information.
[0044] Based on this method, users can choose whether to obtain media content, and the application determines whether to obtain the target content based on the user's instructions.
[0045] In one possible design, after the first application obtains first information and second information from the first service, the method further includes: the first application obtaining third information from the first service, the third information being used to identify eighth media content stored in the second electronic device; the first application displaying the first information, the second information, and the third information, wherein the second information is ordered adjacent to the third information; and the first application, in response to an operation for selecting the second information, instructing the first service to obtain the second media content and the eighth media content.
[0046] In this method, the second information can be the media content selected by the user to be retrieved, and the third information is adjacent to the second information. Therefore, when the user browses the second media content corresponding to the second information, they may also choose to browse the eighth media content corresponding to the third information. Thus, the application can determine whether to retrieve the eighth media content at the same time as determining to retrieve the second media content. When the user selects to browse the eighth media content, the application can directly display the pre-retrieved eighth media content. Therefore, in this method, the application can determine whether to retrieve the media content stored in the second electronic device based on prediction.
[0047] In one possible design, after the first application displays the first information and the second information, the method further includes: the first application, in response to a received first operation, displays the second information but does not display the first information; wherein the first operation is used to instruct only to view information about media content stored in the second electronic device.
[0048] In this method, the first application can integrate the identification information of the local content of the first electronic device and the identification information of the media content in the second electronic device to achieve the effect of fused presentation of multi-terminal media content. Furthermore, the first application can also display the media content from the second electronic device separately, achieving the effect of single-terminal media content presentation. In summary, the first application can flexibly switch the presentation mode of the identification information of multi-terminal media content according to user needs, making it highly practical and improving the user experience.
[0049] In one possible design, the first media content and the second media content are images or videos, and the first information and the second information are thumbnails.
[0050] In one possible design, the first service resides in the application framework layer of the operating system of the first electronic device.
[0051] In this method, the first service resides in the application framework layer of the operating system. It can directly manage the media content locally stored on the first electronic device, manage the media content stored on the second electronic device through interaction, and also interact with applications installed on the first electronic device. Therefore, based on the first service, integrated management of multi-device media content can be achieved, enabling various applications to access multi-device media content in a unified manner, thus improving the efficiency of media content access.
[0052] In one possible design, the second electronic device is a home storage device.
[0053] In this method, if the second electronic device is a home storage device, the first electronic device can provide integrated access to media content in both the first electronic device and the home storage device based on the first service, thereby improving the efficiency of applications accessing media content on both the first electronic device and the home storage device.
[0054] In one possible design, the first application displays first information and second information, including: the first application displays the first information and the second information on a first interface.
[0055] In this method, the first application can display the identification information of media content in the first electronic device and the second electronic device on the same interface. Therefore, it can achieve the effect of integrating and presenting the metadata of media content from multiple devices, making it easier for users to browse media content stored on multiple devices at the same time and improving the user experience.
[0056] In one possible design, the first interface includes a first window containing the first information and the second information; or, the first interface includes a second window and a third window, where the second window contains the first information and the third window contains the second information.
[0057] In this method, the first application can display the identification information of media content from multiple platforms in the same window, which facilitates users' integrated browsing of media content from multiple platforms. Alternatively, the first application can display the identification information of media content from different platforms in separate windows, which facilitates users' categorized browsing of media content from multiple platforms and confirmation of the media data source.
[0058] In one possible design, the first information and the second information are located in different areas of the first window; or, in the first window, the first information and the second information are distributed according to a set sorting, wherein the set sorting is: the sorting of the time / location / category corresponding to the first media content and the second media content.
[0059] In this method, the identification information of media content from different platforms can be displayed in different areas of the same window, making it easier for users to browse multi-platform media content by category and confirm the source of media data. Displaying sorted media content in the same window also facilitates a more integrated browsing experience for users.
[0060] In one possible design, the time / location / category corresponding to the first media content and the second media content meet the set conditions.
[0061] Based on this method, the application can individually display the identification information of specific categories of media content, making it easier for users to view specific categories of media content.
[0062] In a second aspect, embodiments of this application provide an electronic device, the electronic device including a display screen, a memory and one or more processors; wherein, the memory is used to store computer program code, the computer program code including computer instructions; when the computer instructions are executed by the one or more processors, the electronic device causes the electronic device to perform the method described in the first aspect or any possible design of the first aspect.
[0063] Thirdly, embodiments of this application provide a content management system, including: a first electronic device and a second electronic device, wherein the first electronic device includes a first service and a first application; the first electronic device is used to: obtain first information and second information through the first service, and store the first information and the second information; wherein the first information is used to identify first media content stored in the first electronic device, and the second information is used to identify second media content stored in the second electronic device; obtain the first information and / or the second information from the first service through the first application; and display the first information and / or the second information through the first application.
[0064] In one possible design, the second electronic device is a home storage device.
[0065] In one possible design, the first electronic device is further configured to: determine, via the first application, that the second media content needs to be obtained; send a content acquisition request to the first service via the first application, the content acquisition request being used to request the second media content; in response to the received content acquisition request, request the second electronic device to obtain the second media content via the first service; the second electronic device is configured to send the second media content to the first service; the first electronic device is further configured to: receive the second media content from the second electronic device via the first service and send the second media content to the first application; and display the second media content upon receiving it via the first application.
[0066] In one possible design, the first electronic device is used to perform the method executed by the first electronic device in the method described in the first aspect or any possible design of the first aspect, and the second electronic device is used to perform the method implemented by the second electronic device in the method described in the first aspect or any possible design of the first aspect.
[0067] Fourthly, this application provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible design of the first aspect.
[0068] Fifthly, this application provides a computer program product comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the methods described in the first aspect or any possible design of the first aspect.
[0069] For the beneficial effects described in the second to fifth aspects above, please refer to the description of the beneficial effects in the first aspect above, which will not be repeated here. Attached Figure Description
[0070] Figure 1 A schematic diagram of a method for an electronic device to access and manage content in an HDC device;
[0071] Figure 2 A schematic diagram of the hardware architecture of an electronic device provided in an embodiment of this application;
[0072] Figure 3 A schematic diagram of the software architecture of an electronic device provided in an embodiment of this application;
[0073] Figure 4 A schematic diagram of a possible system architecture applicable to the solutions provided in the embodiments of this application;
[0074] Figure 5 A schematic diagram of a possible system architecture applicable to the solutions provided in the embodiments of this application;
[0075] Figure 6 A schematic diagram of the software architecture of a terminal device provided in an embodiment of this application;
[0076] Figure 7 A schematic diagram illustrating a synchronization scheme provided in an embodiment of this application;
[0077] Figure 8 A schematic diagram illustrating a downlink synchronization method provided in an embodiment of this application;
[0078] Figure 9 A schematic diagram illustrating an uplink synchronization method provided in an embodiment of this application;
[0079] Figure 10 A schematic diagram illustrating a content management method provided in an embodiment of this application;
[0080] Figure 11 A schematic diagram illustrating a content synchronization and management method based on a gallery, provided as an embodiment of this application;
[0081] Figure 12 A schematic diagram illustrating a content fusion management method provided in an embodiment of this application;
[0082] Figure 13 A flowchart illustrating a content synchronization and management method based on a gallery, provided for an embodiment of this application;
[0083] Figure 14a A schematic diagram of a photo album interface provided in an embodiment of this application;
[0084] Figure 14b A schematic diagram of a graphical interface provided in an embodiment of this application;
[0085] Figure 14c A schematic diagram of a gallery control interface provided in an embodiment of this application;
[0086] Figure 14d A schematic diagram of a graphical interface provided in an embodiment of this application;
[0087] Figure 14e A schematic diagram of a gallery settings interface provided in an embodiment of this application;
[0088] Figure 14f A schematic diagram of a gallery settings interface provided in an embodiment of this application;
[0089] Figure 15 A flowchart illustrating a content usage method provided in an embodiment of this application;
[0090] Figure 16a A schematic diagram of an application interface provided in an embodiment of this application;
[0091] Figure 16b A schematic diagram of an interface for selecting an image source in an application provided by an embodiment of this application;
[0092] Figure 16c A schematic diagram of an interface for selecting an image in an application provided in this application embodiment;
[0093] Figure 16d A schematic diagram of an application interface provided in an embodiment of this application;
[0094] Figure 17 A schematic diagram illustrating a content management method provided in an embodiment of this application;
[0095] Figure 18 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0096] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. In the description of the embodiments of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first" and "second" may explicitly or implicitly include one or more of that feature.
[0097] For ease of understanding, exemplary descriptions of concepts related to this application are provided for reference.
[0098] 1) The electronic device is a device with wireless connectivity. In some embodiments of this application, the electronic device is a device with display functionality.
[0099] In some embodiments of this application, the electronic device may be a portable terminal device, such as a mobile phone, tablet computer, wearable device with wireless communication function (e.g., watch, bracelet, helmet, earphone, etc.), vehicle terminal device, augmented reality (AR) / virtual reality (VR) device, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), smart home device (e.g., smart TV, smart speaker, etc.), smart robot, workshop equipment, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, or wireless terminal in smart home, flying equipment (e.g., smart robot, hot air balloon, drone, airplane), etc. Wearable devices are portable devices that users can wear directly on their body or integrate into their clothing or accessories.
[0100] In some embodiments of this application, the electronic device may also be a portable terminal device that includes other functions such as a personal digital assistant and / or a music player. Exemplary embodiments of the portable terminal device include, but are not limited to, devices equipped with... Alternatively, it could be a portable terminal device with another operating system. The aforementioned portable terminal device could also be other portable terminal devices, such as a laptop computer with a touch-sensitive surface (e.g., a touch panel). It should also be understood that in some other embodiments of this application, the aforementioned electronic device may not be a portable terminal device, but rather a desktop computer with a touch-sensitive surface (e.g., a touch panel).
[0101] 2) Metadata, or data about data, primarily describes the properties of data or information resources. It is descriptive data specific to data or information resources. Metadata can be used to support functions such as indicating storage location, historical data, and record retrieval, enabling effective discovery, retrieval, integrated organization, and effective management of data or information resources. Media metadata refers to the descriptive data of media files such as images and videos. For example, image metadata may include data indicating information such as the image's file name, capture time, modification time, shooting mode, original image storage path, thumbnail storage path, and file size.
[0102] 3) Synchronization typically refers to bidirectional data synchronization between two devices (including add, delete, and modify operations). In this embodiment, synchronization refers to uplink and downlink synchronization of data between the electronic device and the HDC (device). Uplink synchronization refers to the uploading of metadata (such as media metadata) from the electronic device to the HDC and the uploading of data or resource information (such as media files) from the electronic device to the HDC. Downlink synchronization refers to the transmission of metadata from the HDC to the electronic device and the transmission of data or resource information from the HDC to the electronic device.
[0103] For example, electronic device 1 (such as a mobile phone) can sync photos to HDC via uplink synchronization, and electronic device 2 (such as a tablet) can obtain photos synced from HDC by electronic device 1 via downlink synchronization. Similarly, electronic device 1 can also obtain photos synced from HDC by electronic device 2. Therefore, through bidirectional synchronization, electronic device 1 and electronic device 2 can view the same photo content.
[0104] 4) An application package (APK) is an application package file format used by operating systems for distributing and installing mobile applications and middleware. For an application's code to run on an electronic device, it must first be compiled and then packaged into a file that the operating system can recognize and run. This file format that the operating system can recognize and run is the APK.
[0105] 5) A software development kit (SDK) is a collection of development tools used to create application software for specific software packages, software frameworks, hardware platforms, operating systems, etc. A typical SDK includes utilities for debugging and other purposes, files that can simply provide application programming interfaces (APIs) for a programming language, or complex hardware that can communicate with an embedded system. SDKs often also include sample code, supporting technical annotations, or other supporting documentation to clarify ambiguities for basic reference materials. A collection of related documents, examples, and tools that assist in developing a particular type of application software can all be called an SDK.
[0106] It should be understood that in the embodiments of this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple.
[0107] Currently, electronic devices can utilize external storage devices such as cloud storage and HDC devices to store or back up data content (e.g., media content). However, electronic devices need to download a dedicated app for the external storage device before they can access and manage the content on that external storage, unlike the method of directly accessing data content on local storage. Therefore, current electronic devices cannot easily and efficiently access both local content and content on external storage simultaneously.
[0108] Figure 1 This is a schematic diagram illustrating a method for an electronic device to access and manage content in an HDC device. Figure 1As shown in the diagram, taking a mobile phone as the electronic device and an HDC device as the external storage device, the HDC device is a high-capacity storage device deployed within a home network. It has the capability to back up and synchronize content across multiple devices, enabling long-term reliable data storage and convenient personal access and management anytime, anywhere. A home storage app (compatible with the HDC) can be installed on the mobile phone, allowing interaction with the HDC device to send media content from the phone to the HDC device for storage or backup, as well as to browse and manage the content on the HDC device. However, only the home storage app can access the content on the HDC device; other apps such as camera apps, gallery apps, or third-party applications cannot directly access the content. Therefore, if a user needs to view and share content on the HDC device through other apps on their phone, they must first find the corresponding content on the HDC device through the home storage app and manually download it to the media library in their local media framework, and then retrieve the content from the local media library through other apps. This requires users to use two apps to view the content on the HDC device, making the process complex and cumbersome, resulting in low efficiency and a poor user experience. Furthermore, users can directly access content stored locally on their electronic devices through other applications on their phones. Therefore, the electronic device needs to use two different methods to access and process content on the HDC device and content stored locally on the device. This prevents the integration of access to both local and HDC content, making the process more complex and cumbersome, and reducing the efficiency of accessing and managing different content, as well as the user experience.
[0109] In view of the above problems, embodiments of this application provide a content management method, electronic device, and system to improve the efficiency of electronic devices accessing content stored on multiple devices and improve the user experience.
[0110] First, refer to... Figure 2 The structure of the electronic device to which the method provided in the embodiments of this application is applicable will be described.
[0111] like Figure 2 As shown, the electronic device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a USB interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, a sensor module 280, buttons 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a SIM card interface 295, etc.
[0112] The sensor module 280 may include a gyroscope sensor, an accelerometer, a proximity sensor, a fingerprint sensor, a touch sensor, a temperature sensor, a pressure sensor, a distance sensor, a magnetic sensor, an ambient light sensor, a barometric pressure sensor, a bone conduction sensor, etc.
[0113] Understandable Figure 2 The electronic device 200 shown is merely an example and does not constitute a limitation on the electronic device. The electronic device may have more or fewer components than those shown in the figure, may combine two or more components, or may have different component configurations. Figure 2 The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.
[0114] Processor 210 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, memory, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). Different processing units may be independent devices or integrated into one or more processors. The controller may serve as the central nervous system and command center of the electronic device 200. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.
[0115] The processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.
[0116] The execution of the content management method provided in this application embodiment can be controlled by the processor 210 or by calling other components. For example, it can call the processing program of this application embodiment stored in the internal memory 221, or call the processing program of this application embodiment stored in a third-party device through the external memory interface 220 to control the wireless communication module 260 to perform data communication with other devices, thereby improving the intelligence and convenience of the electronic device 200 and enhancing the user experience. The processor 210 may include different devices. For example, when integrating a CPU and a GPU, the CPU and GPU can cooperate to execute the content management method provided in this application embodiment. For example, some algorithms in the content management method can be executed by the CPU, and other algorithms can be executed by the GPU to achieve faster processing efficiency.
[0117] Display screen 294 is used to display images, videos, etc. Display screen 294 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 200 may include one or N displays screens 294, where N is a positive integer greater than 1. Display screen 294 can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces (GUIs). For example, display screen 294 can display photos, videos, web pages, or documents, etc.
[0118] In this embodiment of the application, the display screen 294 can be an integral flexible display screen, or it can be a splicing display screen composed of two rigid screens and a flexible screen located between the two rigid screens.
[0119] Camera 293 (either a front-facing camera or a rear-facing camera, or a single camera that can function as both) is used to capture still images or videos. Typically, camera 293 may include a photosensitive element such as a lens assembly and an image sensor. The lens assembly includes multiple lenses (convex or concave lenses) for collecting light signals reflected from the object being photographed and transmitting these signals to the image sensor. The image sensor then generates a raw image of the object being photographed based on the light signals.
[0120] Internal memory 221 can be used to store computer executable program code, which includes instructions. Processor 210 executes various functional applications and data processing of electronic device 200 by running the instructions stored in internal memory 221. Internal memory 221 may include a program storage area and a data storage area. The program storage area may store the operating system, application program code (such as content processing functions), etc. The data storage area may store data created during the use of electronic device 200.
[0121] The internal memory 221 may also store one or more computer programs corresponding to the algorithm of the content management method provided in the embodiments of this application. The one or more computer programs are stored in the internal memory 221 and configured to be executed by one or more processors 210. The one or more computer programs include instructions that can be used to perform the various steps in the following embodiments.
[0122] 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 disk storage device, flash memory device, universal flash storage (UFS), etc.
[0123] Of course, the algorithm code of the content management method provided in this application embodiment can also be stored in external memory. In this case, the processor 210 can run the algorithm code of the content management method stored in external memory through the external memory interface 220.
[0124] The sensor module 280 may include a gyroscope sensor, an accelerometer sensor, a proximity sensor, a fingerprint sensor, a touch sensor, etc.
[0125] A touch sensor, also known as a "touch panel," can be located on the display screen 294. The touch sensor and display screen 294 together form a touch display screen, also called a "touchscreen." The touch sensor detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 294. In other embodiments, the touch sensor may also be located on the surface of the electronic device 200, in a different position than the display screen 294.
[0126] For example, the display screen 294 of the electronic device 200 displays a main interface, which includes icons for multiple applications (such as a camera application, a gallery application, etc.). The user taps the camera application icon on the main interface using a touch sensor, triggering the processor 210 to launch the camera application and open the camera 293. The display screen 294 then displays the camera application's interface, such as the viewfinder.
[0127] The wireless communication function of electronic device 200 can be implemented through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor.
[0128] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 200 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.
[0129] The mobile communication module 250 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 200. The mobile communication module 250 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 250 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 250 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 250 may be housed in the processor 210. In some embodiments, at least some functional modules of the mobile communication module 250 and at least some modules of the processor 210 may be housed in the same device. In this embodiment, the mobile communication module 250 can also be used for information interaction with other devices.
[0130] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 270A, receiver 270B, etc.) or displays images or videos through the display screen 294. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 210 and may be housed in the same device as the mobile communication module 250 or other functional modules.
[0131] The wireless communication module 260 can provide solutions for wireless communication applications on the electronic device 200, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to processor 210. The wireless communication module 260 can also receive signals to be transmitted from processor 210, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2. In this embodiment, the wireless communication module 260 is used to establish connections with other electronic devices for data interaction. Alternatively, the wireless communication module 260 can be used to access access point devices, send control commands to other electronic devices, or receive data from other electronic devices.
[0132] For example, the terminal device described in this application embodiment adopts... Figure 2 When the hardware architecture shown is implemented, the terminal device can receive or send information, data files, and other content through the mobile communication module 250 or the wireless communication module 260, thereby enabling functions such as establishing a communication connection with the HDC device and performing uplink and downlink synchronization.
[0133] In addition, the electronic device 200 can implement audio functions through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, and an application processor, such as music playback and recording. The electronic device 200 can receive input from buttons 290, generating key signal inputs related to user settings and function control. The electronic device 200 can use a motor 291 to generate vibration alerts (such as vibration alerts for incoming calls). The indicator 292 in the electronic device 200 can be an indicator light, used to indicate charging status, battery level changes, messages, missed calls, notifications, etc. The SIM card interface 295 in the electronic device 200 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 295 to achieve contact and separation with the electronic device 200.
[0134] It should be understood that, in practical applications, electronic device 200 may include more than Figure 2 The number of more or fewer components shown is not specifically limited in the embodiments of this application. The illustrated electronic device 200 is merely an example, and the electronic device 200 may have more or fewer components than shown in the figure, may combine two or more components, or may have different component configurations. The various components shown in the figure may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.
[0135] The software system of the electronic device 200 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses the layered architecture Android system as an example to exemplify the software structure of the electronic device.
[0136] Layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. For example... Figure 3 As shown, the software architecture can be divided into four layers, from top to bottom: the application layer, the application framework layer (framework, FWK), the Android runtime and system libraries, and the Linux kernel layer.
[0137] The application layer is the top layer of the operating system and includes native operating system applications such as camera, gallery, calendar, Bluetooth, music, video, and messaging. The applications discussed in this application are referred to as apps (APPs), which are software programs capable of performing one or more specific functions. Typically, multiple apps can be installed on an electronic device. Examples include camera apps, email apps, and smart home control apps. The apps mentioned below can be system apps pre-installed at the factory or third-party apps downloaded by the user from the network or obtained from other electronic devices during use.
[0138] Of course, for developers, they can write applications and install them into this layer. In one possible implementation, the application can be developed using the Java language, by calling the Application Programming Interface (API) provided by the application framework layer. Developers can then interact with the underlying operating system (such as the kernel layer) through the application framework to develop their own applications.
[0139] The application framework layer provides APIs and a programming framework for applications within the application layer. The application framework layer can include predefined functions. It may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.
[0140] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.
[0141] Content providers are used to store and retrieve data, and make that data accessible to applications. This data may include files (e.g., documents, videos, images, audio), text, and other information.
[0142] A view system includes visual controls, such as controls that display text, images, documents, and other content. View systems can be used to build applications. An interface in a display window can consist of one or more views. For example, a display interface including a text message notification icon could include a view that displays text and a view that displays images.
[0143] The phone manager provides communication functionality for electronic devices. The notification manager allows applications to display notification information in the status bar; it can be used to convey informative messages and can disappear automatically after a short pause without user interaction.
[0144] The Android runtime consists of core libraries and a virtual machine. The Android runtime is responsible for scheduling and managing the Android system.
[0145] The core libraries of the Android system consist of two parts: one part contains the functionalities that Java calls, and the other part is the core libraries of the Android system. The application layer and application framework layer run in a virtual machine. Taking Java as an example, the virtual machine executes the Java files in the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.
[0146] The system library can include multiple functional modules. For example: a surface manager, a media library, a 3D graphics processing library (e.g., OpenGL ES), a 2D graphics engine (e.g., SGL), and an image processing library. The surface manager manages the display subsystem and provides the fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of various common audio and video formats, as well as still image files. The media library supports various audio and video encoding formats, such as MPEG4, H.564, MP3, AAC, AMR, JPG, and PNG. The 3D graphics processing library implements 3D graphics drawing, image rendering, compositing, and layer processing. The 2D graphics engine is the drawing engine for 2D graphics.
[0147] The kernel layer provides the core system services of the operating system, such as security, memory management, process management, network protocol stack, and driver models, all of which are implemented based on the kernel layer. The kernel layer also serves as an abstraction layer between the hardware and software stacks. This layer contains many drivers related to electronic devices, including: display drivers; keyboard drivers as input devices; Flash drivers for memory-based devices; camera drivers; audio drivers; Bluetooth drivers; and WiFi drivers.
[0148] It is important to understand that the functional services described above are just an example. In practical applications, electronic devices may be divided into more or fewer functional services based on other factors, or the functions of each service may be divided in other ways, or they may not be divided into functional services but work as a whole.
[0149] The solution provided in this application will be described in detail below with reference to specific embodiments.
[0150] The solution provided in this application can be applied to a system consisting of at least one electronic device and an external storage device. The external storage device provides content storage, backup, and synchronization services for the at least one electronic device. The external storage device can be, for example, an HDC device or a cloud server. On one hand, each electronic device can upload and synchronize its own content to the external storage device, thereby storing or backing up its content there. On the other hand, the external storage device can download and synchronize the stored content to each electronic device, allowing each electronic device to view and manage the content in the external storage device (including its own content and content from other electronic devices). The content in the external storage device or electronic devices can be various types of data, resources, or information, such as media content like images, videos, audio, and files.
[0151] It should be noted that, in this embodiment, synchronizing the content of an external storage device to an electronic device specifically refers to transferring the metadata of the content stored in the external storage device to the electronic device for storage. Based on the metadata, the electronic device can retrieve the corresponding content from the external storage device at any time. Furthermore, synchronizing the content of an electronic device to an external storage device in this embodiment refers to transferring the content stored in the electronic device and its metadata to the external storage device for storage. Metadata is data used to describe the content in the electronic device or external storage device, and the content described by the metadata can be obtained based on the metadata.
[0152] In this embodiment, the external storage device and at least one electronic device can communicate via wired or wireless communication. Optionally, the external storage device and the electronic device can be connected to the same local area network (LAN) or different LANs.
[0153] For example, external storage devices and electronic devices can establish a wireless connection with the same wireless access point. They can also connect to the same Wi-Fi hotspot. Furthermore, they can connect to the same Bluetooth beacon via Bluetooth. Additionally, external storage devices and electronic devices can initiate a communication connection via a near field communication (NFC) tag, transmitting encrypted information for authentication via Bluetooth. After successful authentication, data transmission occurs in a point-to-point (P2P) manner.
[0154] The following uses electronic devices as terminal devices and external storage devices as HDC devices as examples to introduce the solutions provided in the embodiments of this application.
[0155] For example, Figure 4 This is a schematic diagram of a possible system architecture applicable to the solutions provided in the embodiments of this application. For example... Figure 4 As shown, the system includes at least: an HDC device and a terminal device (e.g., a mobile phone). System applications (e.g., [missing information]) can be installed on the terminal device. Figure 4 (The image library shown) and third-party applications. The terminal device also includes HDC services, media libraries, and file systems.
[0156] The HDC service enables uplink and downlink content synchronization between terminal devices and the HDC device. The file system stores the terminal device's own content as well as content synchronized from the HDC device. The media library manages content stored on the terminal device itself, such as data and files from system applications and third-party applications; it also manages content synchronized from the HDC device. Furthermore, the media library provides an HDC synchronization interface to the HDC service, as well as access interfaces to system and third-party applications. The HDC service can then interact with the media library by calling the HDC synchronization interface to complete uplink and downlink content synchronization. System and third-party applications can access the content managed by the media library through the access interface, enabling unified access and management of both local content on the terminal device and content synchronized from the HDC device, thereby improving access efficiency and user experience. Optionally, a home storage app can be installed on the terminal device, which can also be used to access and manage the HDC device and its stored content.
[0157] Optional, in Figure 4 In the system shown, both the HDC device and the terminal device can be accessed via the above... Figure 2 The hardware architecture shown and Figure 3 The software architecture implementation is shown.
[0158] Furthermore, such as Figure 5 As shown, Figure 4 The HDC service for terminal devices in the system shown can include two sub-services: application-side synchronization service and terminal-side synchronization service. The application-side synchronization service can be deployed as a software development kit (SDK) in the home storage app or a designated system application (e.g., [example application]). Figure 5 The image gallery application shown is an example. The device-side synchronization service can be deployed as an application package (APK) within the software layer architecture of the terminal device.
[0159] The application-side synchronization service is primarily used to provide the following functions:
[0160] 1) Synchronization status notification
[0161] The application-side synchronization service can obtain information on the progress and status of uplink and downlink synchronization between the terminal device and the HDC device from the end-side synchronization service, and can notify the user of this information so that the user can be informed of the synchronization progress and status information between the terminal device and the HDC device in a timely manner.
[0162] 2) Provide a content download API and download progress notifications.
[0163] The application-side synchronization service can obtain download APIs for content (including content stored in the HDC device and content locally stored on the terminal device) from the device-side synchronization service or media library. This allows the application hosting the application-side synchronization service to drive the device-side synchronization service to download the corresponding content from the HDC device by calling the download API. Furthermore, the application-side synchronization service can receive download progress callback notifications from the device-side synchronization service. These notifications indicate the progress of the synchronization between the device-side synchronization service and the HDC device, and the application-side synchronization service can notify the user of this progress via appropriate notification messages.
[0164] 3) Provide a synchronous control entry point
[0165] The application-side synchronization service can provide a control switch for the synchronization process between the user control terminal device and the HDC device, and provide this control switch to the user so that the user can control the synchronization process between the terminal device and the HDC device by operating the control switch.
[0166] For example, the application-side synchronization service in a gallery application can provide a gallery synchronization switch to the user. This switch controls the synchronization process of images and videos between the terminal device and the HDC device. When the user turns on the gallery synchronization switch, the terminal device can perform uplink and downlink synchronization of images and videos between the terminal device and the HDC device, thus ensuring the consistency of image and video content on both devices. When the user turns off the gallery synchronization switch, the terminal device can stop uplink and downlink synchronization of image and video content with the HDC device.
[0167] The endpoint synchronization service is mainly used to provide the following functions:
[0168] 1) Synchronization function
[0169] The endpoint synchronization service enables uplink and downlink synchronization of content between the terminal device and the HDC device. For example, the endpoint synchronization service may include a media library SDK. This SDK can interact with the media library via the Ethernet (E) interface, thereby sending content obtained from the HDC device by the endpoint synchronization service to the media library for storage, thus achieving downlink synchronization. The SDK can also provide a southbound interface definition language (AIDL) interface for interacting with the media library. This AIDL interface allows content to be obtained from the media library, which can then be sent by the endpoint synchronization service to the HDC device for storage. During uplink and downlink synchronization between the terminal device and the HDC device, metadata can be transmitted in an object-oriented data format. That is, the terminal device or HDC device performs object-oriented processing on the metadata to be transmitted before transmitting it to the peer device.
[0170] 2) Communication function
[0171] The end-to-end synchronization service can complete the interaction processes between the terminal device and the HDC device, including discovery, connection establishment, communication, and data transmission. For example, the end-to-end synchronization service may include a communication SDK, such as an SDK integrating Hilink and P2P functionality. This SDK can establish a data transmission channel with the HDC device based on Hilink and P2P communication methods to realize data transmission during uplink and downlink synchronization. It can also parse the transmitted data and assemble it into VO data for the media library SDK, and call the interfaces provided by the media library SDK to update the media library with the VO data.
[0172] 3) Control functions
[0173] The end-side synchronization service can control the uplink and downlink synchronization process between the terminal device and the HDC device. For example, the end-side synchronization service may include a control SDK, which can receive data change messages from the HDC device (used to notify the HDC device of data changes), and then initiate the uplink and downlink synchronization process based on the received data change messages.
[0174] In some embodiments of this application, such as Figure 5As shown, the file system of the terminal device can include a local file system and an HDC file system. The local file system stores the terminal device's own content, while the HDC file system stores content synchronized from the HDC device. The HDC file system can be implemented using a filesystem in userspace (FUSE) or a distributed file system. The local file system and HDC file system can interact with the media library and HDC synchronization service through a virtual file system (VFS) interface.
[0175] In some embodiments of this application, such as Figure 5 As shown, an HDC device may include a Hypertext Transfer Protocol (HTTP) server, an HDC synchronization service, a media management service, and a file system. The HTTP server can interact with the HDC synchronization service of the terminal device through a signaling gateway, and can also interact with the file system through a data gateway, thereby reading and writing data from the file system. The HDC synchronization service of the HDC device can perform functions related to uplink / downlink synchronization between the HDC device and the terminal device, as well as management functions for the HTTP server and the media management service. The media management service is used to manage the content stored in the file system. The file system is used to store content.
[0176] Furthermore, when the terminal device adopts the above... Figure 3 When using the software system shown, the media library, HDC service, file system, etc. in the terminal device can be deployed on... Figure 3 The application framework layer shown is used for this purpose. Of course, these service structures can also be deployed in other software layers as needed, and this application embodiment does not impose specific restrictions.
[0177] For example, refer to Figure 6 , Figure 3 The application framework layer shown may further include an application interface layer (ML interface), a framework service layer (ML framework), a data management layer (ML adapter), and an operation platform layer.
[0178] The application interface layer may include a unified media operation framework module (identified as MediaLibrarySDK), a content resolver interface, and a media provider interface.
[0179] The unified media operation framework module provides a unified interface, encapsulates content objects, and shields database operations, making it streamlined and flexible in use. For Android applications, it supports accessing terminal device content (including local, cloud, and DHC content) with zero adaptation through native Android interfaces. For HarmonyOS applications, it supports accessing terminal device content (including local and distributed file system content) through its provided unified interface.
[0180] Specifically, the unified media operation framework module provides a unified northbound interface to the application layer for apps to call, thereby enabling specific content (such as media data) management functions. When the content processed by the terminal device is media data, the unified media operation framework module can provide media object query interfaces and media object modification interfaces. The media object query interface enables the querying of metadata, thumbnails, and content files for media resources and media files. The media object modification interface enables functions such as media object change notifications, subscription / unsubscription changes, and media object change comparisons. In summary, the unified media operation framework module encapsulates media resources and other objects, unifies local and distributed media object access capabilities, shields various differences and implementation details in media metadata and media data access, and provides rich, unified, and layered media data management interfaces, thereby achieving simple and efficient content management functions.
[0181] The content parser interface and media database interface can be used by system applications or third-party applications to access the content of the media database.
[0182] The framework service layer may include a unified media service module (identified as MediaLibraryService), a media database, and a data fusion access module (identified as MediaLibraryFusion), etc.
[0183] The unified media service module provides event management capabilities related to local devices, cloud devices, distributed file systems, and HDC devices. It can receive various event information and trigger corresponding business logic operations. It also provides transmission and management capabilities for media resources on local devices, distributed file systems, cloud devices, and HDC devices, supporting media resource status management based on the connection status between the terminal device and the cloud / HDC device. This enables integrated management and access to media services and resources on local devices, distributed file systems, cloud devices, and HDC devices. This module can interact with the distributed soft bus, cloud space SDK, and application-side synchronization service to achieve cross-device synchronization of media metadata between distributed file systems, cloud space, and HDC devices, as well as real-time detection and integrated access to media data status. The functions provided by this module can include device discovery, device status monitoring (including distributed devices, cloud devices, HDC devices, etc.), media data status monitoring, media metadata synchronization transmission, media resource operations, and media content transmission caching.
[0184] Media databases can be used to store information related to local content or content synchronized from HDC devices, such as metadata.
[0185] The data fusion access module is primarily used to enable fusion access to media data. Specific functions it provides include single-table metadata access, multi-table metadata view fusion access, and multi-database metadata view fusion access. This module enables access to media metadata on local devices, distributed devices, and in the cloud (including operations such as adding, deleting, modifying, and viewing), and decouples the database and business application layers.
[0186] The data management layer may include a synchronous data management module (identified as MediaLibraryDataBase), a local data management module, and a synchronization module.
[0187] The synchronization data management module serves as a media database for distributed devices / cloud / HDC devices, enabling the management of corresponding media data. This module can be used to achieve full, incremental, and real-time synchronization of the distributed device / cloud / HDC device database, message-triggered synchronization, and insertion of synchronized data into the distributed device / cloud / HDC device database.
[0188] The local data management module can serve as a media database for local content, providing functions such as local media data management.
[0189] The synchronization module can include services such as device-side synchronization service and cloud synchronization service, which can synchronize content with different devices. Among them, the device-side synchronization service is used to synchronize content with HDC devices.
[0190] The operating system (OS) platform layer can include systems used for content storage, such as local file systems, distributed file systems, HDC file systems, and cloud file systems. Among these, the HDC file system is used to store content obtained by terminal devices from HDC devices.
[0191] It should be noted that the above Figures 4-6 The device system architecture described herein is merely an exemplary description of the system architecture applicable to the terminal device provided in the embodiments of this application, and does not limit the system architecture of the terminal device in the embodiments of this application. In actual applications, the system architecture adopted by the terminal device is not limited to this.
[0192] The solution provided in this application mainly consists of two parts: content synchronization and content access. The content synchronization part primarily includes a method for synchronizing content between the terminal device and the HDC device. This method ensures that the terminal device can access the content stored in the HDC device and can also store the content on the terminal device in the HDC device. The content access part primarily includes a method for system applications or third-party applications on the terminal device to access the content stored in the HDC device. Based on this method, system applications or third-party applications on the terminal device can easily and quickly obtain the content stored in the HDC device without relying on a home storage app or manual intervention, thereby improving access efficiency and user experience. These will be described in detail below.
[0193] I. Content Synchronization
[0194] Reference Figure 7 The content synchronization component mainly involves modules or components including the media library of the terminal device, the end-to-end synchronization service in the HDC service, and the HDC device itself. The media library and the end-to-end synchronization service can communicate via the E interface. The end-to-end synchronization service can communicate with the HDC device using a P2P method. The end-to-end synchronization service can use the communication SDK to synchronize content with the HDC device. Using the media library SDK, through the E interface, it can update the media library with content synchronized with the HDC device. The media library can then perform corresponding operations such as add, retrieve, update, and delete (create, retrieve, update, delete, CRUD).
[0195] The content synchronization process between terminal devices and HDC devices can be divided into uplink synchronization and downlink synchronization. Uplink synchronization refers to the synchronization of content from the terminal device to the HDC device, while downlink synchronization refers to the synchronization of content from the HDC device to the terminal device.
[0196] See Figure 8Taking the content synchronized between the terminal device and the HDC device as the album content as an example, the downlink synchronization process can include:
[0197] S801: The end-side synchronization service sends a version retrieval request to the media library of the terminal device. This request is used to retrieve the media library version information, which is used to indicate the historical version of the album content in the HDC device.
[0198] The end-side synchronization service can periodically trigger the execution of the above steps S801 and subsequent steps, thereby periodically determining whether downlink synchronization needs to be performed, and executing the corresponding downlink synchronization process when it is determined that downlink synchronization needs to be performed.
[0199] The media library version information indicates the version of the album content in the HDC device after the previous synchronization process. Specifically, the HDC device can indicate the version information of the downlink synchronized content to the terminal device during previous downlink synchronization processes, and the terminal device's media stores this version information as the media library version information. During downlink synchronization, the media library can determine the historical version information of the HDC device based on this media library version information, so as to determine whether the content in the HDC device has been updated based on the historical version information and the latest version information.
[0200] S802: The media library sends media library version information to the end-side synchronization service.
[0201] S803: The client-side synchronization service determines whether the version of the album content in the media library is empty based on the media library version information. If it is, proceed to step S804; otherwise, proceed to step S815.
[0202] If the version of the album content in the media library is empty, it means that the album content of the HDC device has not been synchronized to the terminal device before, or the album content previously synchronized from the HDC device to the terminal device has been cleared. In this case, the terminal synchronization service can determine that the downlink synchronization method is full synchronization, and can use the full synchronization method to perform downlink synchronization, that is, synchronize all album content in the HDC device to the media library of the terminal device.
[0203] If the version of the album content in the media library is not empty, the end-side synchronization service further determines whether the album content in the HDC device is updated relative to the album content in the media library. If so, it determines to use incremental synchronization for downlink synchronization, that is, to synchronize the updated content of the HDC device relative to the media library to the media library, thereby ensuring that the content in the media library is updated as the content in the HDC device is updated; otherwise, it determines not to perform downlink synchronization and can stop executing the current process.
[0204] Specifically, when determining whether the album content in the HDC device is updated relative to the album content in the media library, the end-side synchronization service can obtain the version information of the album content in the HDC device and compare it with the version information in the media library. If the two version information are inconsistent, it is determined that the album content in the HDC device has been updated; otherwise, it is determined that the album content in the HDC device and the album content in the media library have not been updated. For specific execution, please refer to step S815 and subsequent steps below.
[0205] In some embodiments of this application, the content stored in the HDC device can be divided into different types of content according to characteristics such as data type, data level, data source, and data volume. After division, different types of content can be processed such as transmission separately. Therefore, during downlink synchronization, the terminal device and the HDC device can synchronize different types of content separately, and different types of content can be transmitted through different interfaces during the synchronization process.
[0206] For example, during the downlink synchronization of album content between a terminal device and an HDC device, the terminal device and the HDC device can divide the album content into albums and media files (images, videos) within the albums according to their levels. The metadata corresponding to the album content is then divided into album metadata and file metadata. Album metadata indicates the album's attribute information, such as the album's identifier, the number of images or videos contained in the album, and the album's storage location. File metadata indicates the information of the images or videos within the album, such as the image or video's identifier, storage location, and file size. During downlink synchronization, the terminal device and the HDC device can independently transmit album metadata and file metadata.
[0207] Furthermore, considering the amount of data to be synchronized, the terminal device and HDC device can also use a breakpoint resumption method to complete full synchronization. Specifically, the terminal device's end-side synchronization service can set a synchronization progress flag to record the progress of the synchronization process. This synchronization progress flag can include two factors: a progress flag (unique ID) and a time flag (time ID). The progress flag records the offset of the synchronized content, which determines which content has been synchronized and which content is yet to be synchronized. The time flag records the time information of the synchronization execution. During breakpoint resumption, the terminal device's end-side synchronization service updates and saves the corresponding synchronization progress flag locally after each time it retrieves content from the HDC device for storage in the media library. If the synchronization process is interrupted, when the end-side synchronization service restarts the synchronization process, it can determine the synchronization progress based on the saved synchronization progress flag and continue to retrieve the content to be synchronized from the HDC device for storage in the media library according to the progress. After full synchronization is completed, the end-side synchronization service can set the synchronization progress flag to mark that full synchronization is complete.
[0208] Specifically, when the version of the album content in the media library is empty, the corresponding processing method can refer to steps S804 to S814; when the version of the album content in the media library is not empty, the corresponding processing method can refer to steps S815 to S827. The downlink synchronization process using the full synchronization method can refer to steps S805 to S814, and the downlink synchronization process using the incremental synchronization method can refer to steps S818 to S827.
[0209] S804: The end-side synchronization service determines to use full synchronization for downlink synchronization. Then, execute the following steps S805 to S814.
[0210] S805: The end-side synchronization service sends a full album retrieval request to the HDC device. This request is used to retrieve the album metadata corresponding to the album content in the HDC device.
[0211] S806: The HDC device sends the album metadata corresponding to the album content in the HDC device to the end-side synchronization service.
[0212] S807: The client-side synchronization service sends album metadata to the media library.
[0213] S808: The media library stores the received album metadata.
[0214] S809: The media library sends a progress indication message to the end-side synchronization service. This message indicates that the downlink synchronization of album metadata has been successfully completed.
[0215] Upon receiving the progress indication information, the end-side synchronization service determines and records the synchronization progress of the album metadata based on the progress indication information, thereby updating and saving the synchronization progress of the album metadata.
[0216] S810: The end-side synchronization service sends a full album file retrieval request to the HDC device. This request is used to request the file metadata corresponding to the album content in the HDC device.
[0217] S811: The HDC device sends the metadata of the files to be synchronized, corresponding to the album content in the HDC device, to the end-side synchronization service.
[0218] S812: The end-side synchronization service sends the metadata of the files to be synchronized to the media library.
[0219] S813: The media library stores some of the received file metadata.
[0220] S814: The media library sends a progress indication message to the end-side synchronization service, which indicates that the downlink synchronization of the metadata of this part of the file has been successfully completed.
[0221] Upon receiving the progress indication information, the end-side synchronization service determines and records the synchronization progress of the file metadata based on the progress indication information, thereby updating and saving the synchronization progress of the album metadata.
[0222] Among them, the above steps S810 to S814 can be executed in a loop until all file metadata corresponding to the album content in the HDC device is transmitted and successfully stored in the terminal device, thereby achieving the effect of downlink full synchronization using the breakpoint resume method.
[0223] S815: The end-side synchronization service obtains HDC version information from the HDC device, which is used to indicate the version of the album content in the HDC device.
[0224] This is the latest version of the photo album content in HDC devices.
[0225] S816: The end-side synchronization service determines whether the HDC version information and the media library version information are inconsistent. If so, proceed to step S817; otherwise, proceed to step S828.
[0226] S817: The end-side synchronization service determines that incremental synchronization will be used for downlink synchronization. Then, steps S818 to S827 are executed.
[0227] Taking the case where the album content on the HDC device has increased compared to the album content on the terminal device as an example, the terminal-side synchronization service can obtain and store the metadata corresponding to the increased album content from the HDC device, referring to steps S818 to S827. When album content is modified on the HDC device, the HDC device can send the metadata corresponding to the modified album content to the terminal-side synchronization service, which can then make the corresponding modifications. When album content is deleted on the HDC device, the HDC device can indicate the metadata corresponding to the deleted album content to the terminal-side synchronization service, so that the terminal-side synchronization service can determine the metadata corresponding to the deleted content on the HDC device and then delete the stored metadata.
[0228] S818: The end-side synchronization service sends an incremental album retrieval request to the HDC device. This request is used to retrieve the album metadata corresponding to the incremental album content in the HDC device.
[0229] S819: The HDC device sends the album metadata corresponding to the incremental album content in the HDC device to the end-side synchronization service.
[0230] S820: The device-side synchronization service sends the album's metadata to the media library.
[0231] S821: The media library stores the received album metadata.
[0232] S822: The media library sends a progress indication message to the end-side synchronization service. This message indicates that the downlink synchronization of the album metadata corresponding to the incremental album content has been successfully completed.
[0233] S823: The end-side synchronization service sends an incremental album file retrieval request to the HDC device. This request is used to request the file metadata corresponding to the incremental album content in the HDC device.
[0234] S824: The HDC device sends the metadata of the files to be synchronized corresponding to the incremental album content in the HDC device to the end-side synchronization service.
[0235] S825: The device-side synchronization service sends the metadata of the files to be synchronized to the media library.
[0236] S826: The media library stores some of the received file metadata.
[0237] S827: The media library sends a progress indication message to the end-side synchronization service, which indicates that the downlink synchronization of the metadata of this part of the file has been successfully completed.
[0238] The incremental synchronization process described above can also employ the breakpoint resume method. When using the breakpoint resume method, steps S823 to S827 can be executed repeatedly until all file metadata corresponding to the album content in the HDC device is transmitted and successfully stored in the terminal device, thereby achieving the effect of downlink incremental synchronization using the breakpoint resume method.
[0239] S828: The end-side synchronization service determines that it will not perform downlink synchronization and ends the current process.
[0240] Optionally, after the current process ends, the end-side synchronization service can determine whether the uplink synchronization process needs to be executed. If so, it can continue to execute the corresponding uplink synchronization process.
[0241] Based on the above embodiments, the terminal device can obtain and store the metadata of the content in the HDC device through downlink synchronization, without relying on a home storage app. When an application in the terminal device needs to access the content in the HDC device, it can retrieve the corresponding content in the HDC device based on the stored metadata of the content in the HDC device.
[0242] See Figure 9 Taking the content synchronized between the terminal device and the HDC device as the album content as an example, the uplink synchronization process can include:
[0243] S901: The end-side synchronization service sends an uplink synchronization request to the media library. This request is used to request uplink synchronization.
[0244] S902: The media library sends an uplink synchronization confirmation message to the end-side synchronization service. This message is used to confirm that uplink synchronization is being performed.
[0245] S903: End-side synchronization service obtains synchronization lock from HDC device.
[0246] In this embodiment, a synchronization lock is used to control the effect that only one terminal device among multiple terminal devices corresponding to the same user account can perform uplink and downlink synchronization with the HDC device at any given time. The same user account can log in on multiple terminal devices, generate media content on each terminal device, and synchronize the generated media content to and from the HDC device via the corresponding terminal device. Therefore, in this embodiment, each user account has one and only one synchronization lock, which is assigned by the HDC device and can be used to control the operation permissions of the media content corresponding to that user account, such as whether uplink and downlink synchronization of the media content corresponding to that user account is allowed with the HDC device. At any given time, only one terminal device corresponding to that account is allowed to possess the synchronization lock. When a terminal device possesses the synchronization lock corresponding to that user account, it can perform synchronization operations on the media content corresponding to that user account; otherwise, synchronization operations on the content corresponding to that user account are not allowed.
[0247] S904: The device-side synchronization service retrieves the album content added to the terminal device and its corresponding album metadata from the media library.
[0248] The device-side synchronization service can send a request to the media library to retrieve newly added album content and its corresponding metadata from the terminal device. Upon receiving the request, the media library determines whether any album content added since the last uplink synchronization process exists in its stored album content. If so, it sends that album content and its corresponding metadata to the device-side synchronization service. If not, it returns an indication that no album content has been added to the device-side synchronization service. Upon receiving this indication, the device-side synchronization service can then continue retrieving modified or deleted album content and its corresponding metadata from the media library.
[0249] The end-side synchronization service can periodically trigger the execution of the above steps S801 and subsequent steps, thereby periodically determining whether uplink synchronization needs to be performed, and executing the corresponding uplink synchronization process when it is determined that uplink synchronization needs to be performed.
[0250] S905: The end-to-end synchronization service sends the album content added in the terminal device and its corresponding album metadata to the HDC device for storage.
[0251] Based on this, newly added album content on the terminal device after the last uplink synchronization process can be uplinked and synchronized to the HDC device.
[0252] S906: The end-side synchronization service will indicate the uplink synchronization progress to the media library.
[0253] The device-side synchronization service sends the newly added album content and its corresponding album metadata from the terminal device to the HDC device. The HDC device saves this content and, upon successful saving, sends a synchronization success notification to the device-side synchronization service to indicate that the uplink synchronization of this content has been successfully completed. Upon receiving this notification, the device-side synchronization service can also send a notification to the media library to indicate the completion of the uplink synchronization of this content, allowing the media library to track the uplink synchronization progress.
[0254] In the process of sending the album content added to the terminal device and its corresponding album metadata to the HDC device, the end-to-end synchronization service can also use the breakpoint resume method to complete the synchronization. Then, the above process S904 to S906 can be executed in a loop until the end-to-end synchronization service sends all the album content added to the terminal device and its corresponding album metadata to the HDC device and successfully stores it on the HDC device.
[0255] S907: The device-side synchronization service retrieves the modified album content and its corresponding album metadata from the media library on the terminal device.
[0256] The device-side synchronization service can send a request to the media library to retrieve modified album content and its corresponding metadata from the terminal device. Upon receiving the request, the media library determines whether any album content in its stored albums has been modified since the last uplink synchronization process. If so, it sends that album content and its corresponding metadata to the device-side synchronization service. If not, it returns an indication that no album content has been modified. Upon receiving this indication, the device-side synchronization service can then retrieve deleted album content and its corresponding metadata from the media library.
[0257] S908: The terminal-side synchronization service sends the modified album content and its corresponding album metadata from the terminal device to the HDC device for updating and storage.
[0258] After receiving the modified album content and its corresponding metadata from the terminal device, the HDC device updates the stored corresponding content using the modified album content and its corresponding metadata, thus making the same modifications to that part of the content as in the terminal device. Based on this, album content modified in the terminal device after the last uplink synchronization process can be uplinked and synchronized to the HDC device.
[0259] S909: The end-side synchronization service will indicate the uplink synchronization progress to the media library.
[0260] For details, please refer to the execution of step S906 above, which will not be repeated here.
[0261] S910: The device-side synchronization service obtains the identification information of the metadata of the albums deleted from the terminal device from the media library.
[0262] After deleting album content and its corresponding metadata, the media library can record the identifier information of the deleted metadata. During uplink synchronization, the device-side synchronization service can send a request to the media library to retrieve the identifier information of the album metadata corresponding to the deleted album content on the terminal device. Upon receiving the request, if the media library determines that the identifier information of the deleted metadata exists, it sends that identifier information to the device-side synchronization service. If it does not exist, it returns an indication that no album content has been deleted to the device-side synchronization service. Upon receiving this information, the device-side synchronization service can continue to retrieve the deleted album content and its corresponding metadata from the media library.
[0263] S911: The end-to-end synchronization service sends the identification information of the album metadata deleted by the terminal device to the HDC device.
[0264] The endpoint synchronization service can simultaneously instruct the HDC device to delete the album's metadata and corresponding media content. Upon receiving this identification information, the HDC device identifies the corresponding metadata and album content from its stored data and deletes them. Based on this, album content deleted from the terminal device after the last uplink synchronization process can be uplinked and synchronized to the HDC device, meaning that this portion of album content is also deleted from the HDC device.
[0265] S912: The end-side synchronization service will indicate the uplink synchronization progress to the media library.
[0266] For details, please refer to the execution of step S906 above, which will not be repeated here.
[0267] S913: After uplink synchronization is completed, the end-side synchronization service obtains HDC version information from the HDC device. This information is used to indicate the version information of the latest album content in the HDC device.
[0268] S914: The end-side synchronization service notifies the media library that uplink synchronization has been successfully completed.
[0269] When the end-side synchronization service notifies the media library that uplink synchronization has been successfully completed, it can send the version information of the content synchronized from the HDC device to the media library for storage.
[0270] S915: The end-side synchronization service requests the HDC device to release the synchronization lock.
[0271] After the current uplink synchronization process is completed, the end-side synchronization service can request the release of the synchronization lock from the HDC device. After the synchronization lock is released, the end-side synchronization service cannot perform an uplink synchronization process with the HDC device again. If it is necessary to perform an uplink synchronization process with the HDC device again, the end-side synchronization service needs to request the synchronization lock from the HDC device again.
[0272] Based on the above embodiments, the terminal device can synchronize local content to the HDC device for storage without relying on a home storage app.
[0273] II. Content Access
[0274] Based on the content synchronization method provided in the above embodiments, the terminal device can synchronize the metadata of the content in the HDC device to its own media library for storage, and then, based on this metadata, the applications installed on the terminal device can access the content in the HDC device.
[0275] See Figure 10 Taking a scenario where a third-party application installed on a terminal device accesses content in an HDC device as an example, the content access method provided in this application embodiment may include:
[0276] S1001: A third-party application in the terminal device receives an operation performed by the user, which instructs the user to view the contents of the HDC device.
[0277] In some embodiments of this application, third-party applications may provide controls for selecting the source (or range) of accessed content. Users can operate on these controls to select the source of the accessed content as local content, content from an HDC device, or both local content and content from an HDC device. After the user selects the source of the accessed content, the third-party application can request the corresponding content from the media library and display it, so that the user can further select the specific content to view.
[0278] For example, when a user selects the source of the content to be accessed as local content and content in the HDC device, the following steps S1002 and subsequent steps may be performed.
[0279] S1002: A third-party application sends a content retrieval request to the media library. This request is used to request media content from the HDC device.
[0280] Third-party applications can interact with the media library through the access interface provided by the media library.
[0281] S1003: The media library determines whether to expose the content synchronized from the HDC device to third-party applications. If yes, proceed to step S1004; otherwise, proceed to step S1006.
[0282] The media library can pre-obtain a user-defined application whitelist, which contains identification information for at least one third-party application authorized to access content on the HDC device. When a third-party application requests content from the HDC device, if the media library can obtain the application's identification information and determine whether it is included in the application whitelist, it can determine that the third-party application has permission to access content on the HDC device and can then provide the content synchronized from the HDC device to the third-party application. Otherwise, it can determine that the third-party application does not have permission to access content on the HDC device and cannot provide the content synchronized from the HDC device to the third-party application.
[0283] S1004: The media library determines whether a third-party application is within the set application whitelist. If yes, proceed to step S1005; otherwise, proceed to step S1006.
[0284] S1005: The media library sends metadata corresponding to local content and content synchronized from HDC devices to third-party applications.
[0285] S1006: The media library sends metadata corresponding to local content to third-party applications.
[0286] S1007: Third-party application display interface, which includes information on the local content of the terminal device and information on the content of the HDC device.
[0287] This information can be identification information, etc. For example, when a third-party application requests an image from the media library, the content display interface can include identification information (such as thumbnails) of the image stored locally on the terminal device and identification information of the image in the HDC device. The identification information of the image in the HDC device is determined by the media library based on metadata corresponding to the content in the HDC device. This metadata can be obtained by the terminal device performing downlink synchronization with the HDC device according to the method provided in the above embodiments.
[0288] S1008: A third-party application receives an operation performed by the user, which instructs the user to view a target image in the HDC device.
[0289] For example, the user's action could be clicking on the identifier information of the target image displayed in the content display interface on the HDC device, indicating that the user wants to view the target image.
[0290] S1009: A third-party application sends an image acquisition request to the media library. This request is used to request the acquisition of a target image from the HDC device.
[0291] S1010: The media library sends the image acquisition request to the end-side synchronization service.
[0292] S1011: The end-side synchronization service acquires the target image from the HDC device.
[0293] S1012: The end-side synchronization service sends the target image to the media library.
[0294] S1013: The media library sends the target image to a third-party application.
[0295] S1014: Third-party applications display the target image.
[0296] In this approach, third-party applications can register content change notifications with the media library. This allows the media library to notify the third-party application when it determines that the local content on the terminal device or the content synchronized from the HDC has changed, facilitating corresponding updates. Alternatively, after a third-party application successfully registers its content change notification with the media library, the media library can notify the third-party application of the latest metadata of both the local content and the content synchronized from the HDC device after each uplink / downlink synchronization process.
[0297] Optionally, in the above process, before step S1002, the following step S100a may also be included:
[0298] S100a: Third-party applications register content change notifications with the media library.
[0299] After step S1005 or step S1006, the following step S100b may also be included:
[0300] S100b: The media library sends content change notifications to third-party applications.
[0301] Based on the above method, third-party applications on the terminal device can obtain information about the content in the HDC device without going through the home storage app. This information is then combined with the local content on the terminal device for integrated display. Based on user operations, the application can display either the local content on the terminal device or the content obtained from the HDC device to the user. Compared to the cumbersome process of switching from a third-party application to the home storage app, this method allows users to directly access the local content on the terminal device and the content in the HDC device through the third-party application, improving the simplicity and convenience of viewing content.
[0302] The content management method provided in this application will be illustrated below with specific examples.
[0303] In this example, images and videos are used as examples of content accessed and processed by the solution in this application.
[0304] The HDC device provides storage, backup, and synchronization functions for files such as pictures, videos, and documents. The Home Storage App is a companion application for the HDC device and can be installed on the terminal device. Users can use the Home Storage App on the terminal device to complete the initial installation of the HDC device, bind user accounts, and connect to the network. The HDC device supports isolating content uploaded and downloaded by different users according to their user accounts.
[0305] In this example, a gallery application can be installed on the terminal device, serving as a convergence platform for content from both the terminal device and the HDC device. Users can browse and manage media content (images and videos) stored on the HDC device within the gallery application. The gallery application can integrate and display media content from the HDC device with local media content on the terminal device, and even media content from the cloud and distributed storage devices, avoiding duplicate content presentation. This allows users to view media content stored across multiple devices within a single gallery application.
[0306] Specifically, refer to Figure 11 In the content processing solution based on the image library application, the solution mainly includes the following 5 steps.
[0307] Step 1: Uplink and Downlink Synchronization
[0308] In this stage, the media library deployed in the application framework layer of the terminal device can integrate and call the HDC service to work with the HDC service to complete the uplink and downlink synchronization of media content between the terminal device and the HDC device. For details, please refer to the description of the uplink and downlink synchronization process in the embodiments of this application.
[0309] Step 2: Media Library Integration and Management
[0310] In this stage, the media library provides a synchronization interface to the gallery application, enabling the gallery application to connect to the HDC service through the media library. In turn, the HDC service synchronizes the media content in the HDC device to the gallery application's database, and allows the gallery application to complete the integration of local media content with the media content in the HDC device.
[0311] Optionally, the media library may also include a cloud storage synchronization service. Based on this service, the media library can synchronize media content with cloud storage. Then, based on the media library's synchronization interface, the gallery application can also acquire and merge media content stored in the cloud storage. Optionally, the media library may also include a distributed subsystem interface. Based on this interface, the media library can interact with distributed storage devices to synchronize media content with the distributed storage devices (corresponding to the same user account). Then, based on the media library's synchronization interface, the gallery application can also acquire and merge media content stored in the distributed storage devices.
[0312] For example, such as Figure 12 As shown, the media library may include a local database and an HDC database. The local database includes a local media data table and an incremental operation table. The local media data table records the metadata of the media content stored locally on the terminal device. The incremental operation record table records the operations performed on the locally stored media content during the time interval between two synchronization processes. Based on the incremental operation record table, the changes in the local media content during the time interval between two synchronization processes can be determined, thereby determining the content to be synchronized during the uplink incremental synchronization process. A synchronization process includes one uplink synchronization process and / or one downlink synchronization process. The HDC database manages the media content synchronized by the terminal device from the HDC device. The HDC database includes an HDC data table and an HDC operation table. The HDC data table records the metadata of the media content synchronized by the terminal device from the HDC device. The HDC operation table records the operations performed on the media content in the HDC device during the time interval between two synchronization processes. This can be used for downlink incremental synchronization by the HDC service, and also for applications such as gallery applications to determine the changes in the media content in the HDC device, thereby updating the displayed content. The content recorded in the HDC data table and HDC operation table is obtained by the HDC service from the HDC device. Optionally, the home storage app can also obtain media content from the HDC device through the HDC database in the media library.
[0313] like Figure 12 As shown, for media content, the gallery application can synchronize local data from the media library's local database to the gallery, and can synchronize data from the media library's HDC database to the gallery application, thereby completing the fusion of local media content and HDC media content within the gallery application. Specifically, for acquiring HDC media content, the gallery application does not interact directly with the HDC service, but only with the media library's HDC database.
[0314] Specifically, refer to Figure 13 The relevant processes may include:
[0315] S1301: The gallery application registers a list of synchronization status listener events with the HDC service.
[0316] Specifically, the gallery application can register a list of synchronization status listening events with the application-side synchronization service, which in turn registers the same list with the client-side synchronization service. After successful registration, the client-side synchronization service can notify the application-side synchronization service of the synchronization status when the status of the uplink / downlink synchronization process changes. The application-side service then notifies the gallery application of the synchronization status, allowing the gallery application to track the progress of the uplink / downlink synchronization process.
[0317] S1302: After the HDC service completes the synchronization process using the full synchronization method, it will notify the gallery application of this status information.
[0318] S1303: The gallery application retrieves HDC media content from the HDC data table of the media library.
[0319] S1304: The gallery application merges HDC media content with local content and writes it to the gallery media table.
[0320] Specifically, steps S1301 to S1304 can be executed during the initial synchronization between the terminal device and the HDC device. In this initial synchronization, a full synchronization method is used. After the full synchronization process, the gallery application acquires the synchronized full HDC media content and merges it with the local media content. In subsequent synchronization processes, an incremental synchronization method can be used between the terminal device and the HDC device. After the incremental synchronization process, the gallery application acquires the synchronized incremental HDC media content and updates the existing content.
[0321] Optionally, after steps S1031 to S1303 above, the following steps may also be included:
[0322] S1305: After the HDC service completes the synchronization process using the incremental synchronization method, it will notify the gallery application of this status information.
[0323] S1306: The gallery application queries the HDC media content increment information from the HDC operation table of the media library.
[0324] S1307: The gallery application updates the stored HDC media content accordingly based on the incremental information retrieved.
[0325] Specifically, if the incremental information is to add some HDC content, the gallery application will merge the added HDC media content with the local content and write it into the gallery media table; if the incremental information is to modify some HDC content, the gallery application will modify and update the information recorded in the gallery media table accordingly based on the incremental information; if the incremental information is to delete some HDC content, the gallery application will delete the record of the corresponding HDC content in the gallery media table.
[0326] In some embodiments of this application, during the execution of the above process by the terminal device, if a breakpoint-resume synchronization method is used during the synchronization process, the synchronization process may be interrupted for various reasons. When the synchronization process is interrupted, the HDC service can notify the gallery application of the terminal status. The gallery application can then display an interruption message to alert the user that the synchronization process has been interrupted. Simultaneously, the gallery application can provide a control to trigger the resumption of the synchronization process. After confirming the interruption based on the interruption message, the user can manually control the continuation of synchronization by operating this control. Upon receiving the user's operation, the gallery application instructs the HDC service to resume the execution of the synchronization process.
[0327] Optionally, during the execution of the above process, the terminal device can also simultaneously perform a media content synchronization process in the cloud. For example, the terminal device can include a cloud synchronization service to complete the synchronization with the media content in the cloud. However, the operation of the cloud synchronization service will increase the power consumption of the terminal device and may even affect the normal operation of the HDC service, causing the synchronization process between the terminal device and the HDC device to be interrupted. In this scenario, the following steps may also be included between steps S1301 and S1302:
[0328] S130a: The HDC service negotiates the remaining power consumption control limit with the cloud synchronization service.
[0329] S130b: When the HDC service determines that power consumption is limited, it interrupts the synchronization process.
[0330] S130c: HDC service notification that the gallery application synchronization process was interrupted.
[0331] S130d: The Gallery app displays a message indicating that the synchronization process has been interrupted.
[0332] S130e: The gallery application receives an operation performed by the user, which instructs the resumption of the synchronization process.
[0333] S130f: The gallery application sends an instruction message to the HDC service, which instructs the resumption of the synchronization process.
[0334] S130g: The HDC service continues the synchronization process.
[0335] Based on the above process, users can control the execution progress of the synchronization process, thereby improving the user experience.
[0336] Step 3: Synchronization Status Notification Step
[0337] In this process, the HDC service can provide a synchronization status interface for the gallery application. Based on this interface, the HDC service can notify the gallery application of the progress of uplink and downlink synchronization with the HDC device. The gallery application can then display the synchronization status information so that users can perceive the synchronization progress.
[0338] Step 4: Image Library Integration Management
[0339] In this stage, the data management service in the gallery application can integrate and manage local media content, content synchronized from HDC devices, and content synchronized from the cloud and distributed devices.
[0340] For example, the gallery application can use the synchronization interface provided by the media library to write the user's operations on HDC media content (including offline operations) in the gallery application to the media library. The media library records the corresponding operations in the HDC operation table and can synchronize them to the HDC device in the next synchronization process.
[0341] Section 5: Integrated Display Section
[0342] Based on step 5, the gallery application can perform integrated display and subsequent processing of local media content, content synchronized from HDC devices, and content synchronized from the cloud and distributed devices. For example, the gallery application can integrate local media content and HDC media content for display, including integrated display of album and image display interfaces, album filtering, uplink status icons, and downlink synchronization progress. The gallery application can also set the scope of synchronized albums, including whether to display the HDC synchronization settings entry and album settings lists independent of cloud-synchronized albums. The gallery application can also adapt deletion logic, including deletion logic adaptation under different page and album filtering conditions. Furthermore, the gallery application can adapt to smart gallery data sources, ensuring that the data sources that the smart gallery can analyze and display include HDC media content.
[0343] In one possible example, when a user opens the gallery app, the terminal device can display... Figure 14a The interface shown may include at least one album icon. Each album contains at least one local image and / or at least one HDC image. When a user clicks the icon of one of the albums, the terminal device can display thumbnails of the images contained in that album. When the user clicks a thumbnail, the terminal device can enlarge and display the original image corresponding to that thumbnail. The local images are images stored locally on the terminal device, and the HDC images are images stored in the HDC device. The terminal device can obtain thumbnails of the HDC albums and HDC images based on metadata obtained from the HDC device during synchronization.
[0344] For example, when a user clicks Figure 14a When the "All Photos" album shown is displayed, the terminal device can display... Figure 14b The image display interface shown can include thumbnails of local images and HDC images from all other albums. The terminal device can sort the thumbnails of local and HDC images according to a user-selected sorting method (e.g., by creation time, file name, file size, etc.) before merging and displaying them. For example, in... Figure 14b In the interface shown, thumbnails a-c, e, g-i can be thumbnails of local images, and thumbnails d and f can be thumbnails of HDC images. Optionally, the interface can also integrate and display thumbnails of images synchronized from other storage devices by the terminal device, such as thumbnails of cloud images.
[0345] Furthermore, the terminal device can add controls to the image display interface to display filtered images, allowing users to choose to view filtered or selected images from local images and HDC images. For example, ... Figure 14b The image display interface shown may include a filter control. Users can interact with this filter control to trigger a process where the terminal device filters the displayed thumbnails before showing them. When the user clicks... Figure 14b When the filter control shown is displayed, the terminal device can show... Figure 14c The interface shown contains controls for selecting different types of images, such as controls for selecting local images. Figure 14c The "Local" control shown), and the control for selecting the HDC image ( Figure 14c The "Home Storage Center" control shown in the image, etc. When the user clicks the "Home Storage Center" control, the terminal device can display... Figure 14d The interface shown here contains only thumbnails of HDC images.
[0346] Of course, as another alternative implementation, the terminal device can also directly... Figure 14b The interface shown displays thumbnails of local images and HDC images in different areas to allow users to clearly distinguish the image source.
[0347] In one possible example, the terminal device could add a switch to display controls for HDC synchronization to the gallery settings interface, for example... Figure 14e The "Home Storage Sync" control is shown in the image. When the user turns on the HDC sync switch, the terminal device can periodically synchronize media content such as pictures and videos with the HDC device, and then merge the image and video information synchronized from the HDC device with the local image and video information in the gallery application for display.
[0348] Furthermore, the terminal device can provide selection controls for choosing the range of photos to be synced, for example, when the user clicks... Figure 14e After the "Family Storage Sync" control shown, the terminal device can display... Figure 14f The interface shown includes selection controls for different albums, allowing users to choose which albums to synchronize with the HDC device. For example, if only the "Camera" album is selected, during uplink synchronization with the HDC device, only images from the "Camera" album will be synchronized to the HDC device, and the HDC device will then store the "Camera" album and its images. During downlink synchronization, the terminal device will also only synchronize images from the "Camera" album from the HDC device to its local storage.
[0349] Optionally, with the HDC synchronization switch on, the terminal device can also display information indicating the synchronization progress. When the synchronization progress is "synchronizing," the terminal device can temporarily prohibit the user from accessing and operating the content in the HDC album. When the user attempts to access or operate the content in the HDC album, the terminal device will prompt the user that synchronization is in progress and prohibit the corresponding operation. When the synchronization progress is "synchronized," the terminal device can allow and respond to the user's access to and operation of the content in the HDC album.
[0350] Reference Figure 15 Based on the above examples, the flow of a content usage method provided in this application embodiment may include:
[0351] S1501: The terminal device displays the first interface, which is the interface used in the terminal device.
[0352] The applications in the terminal device can be system applications or third-party applications.
[0353] S1502: The terminal device receives the user's operation on the first interface, which is used to trigger the selection of an image.
[0354] This operation refers to a user's action within a system application or a third-party application on their terminal device. Based on this operation, the user can trigger a process of retrieving and viewing images from the gallery application within the system application or third-party application.
[0355] For example, Figure 16a The diagram shown is a schematic of a first interface. For example... Figure 16aAs shown, the first interface can be the display interface of a memo application. This interface includes an image selection control, which is used to trigger the selection of an image so that an image can be added to the memo note. The user's operation on the first interface can be the user clicking the image selection control in the first interface.
[0356] S1503: The terminal device displays a second interface, which includes a gallery selection control for selecting an image from a gallery application.
[0357] For example, Figure 16b The image shown is a schematic diagram of a second interface. When the user clicks... Figure 16a After the image selection control shown is displayed, the terminal device can show... Figure 16b The second interface shown includes at least a gallery selection control, and may also include other selection controls for selecting other methods of acquiring images.
[0358] S1504: The terminal device receives an operation performed by the user on the second interface, which is used to select to obtain an image from the gallery application.
[0359] For example, this operation can be a user click Figure 16b The operation of the gallery selection control shown in the image.
[0360] The terminal device can perform the above steps S1501 to 1503 through the installed system application or third-party application.
[0361] S1505: The terminal device displays a third interface, which includes thumbnails of at least one local image and at least one HDC image.
[0362] In this context, local images are images stored locally on the terminal device, while HDC images are images stored in the HDC device. Thumbnails serve as image identification information, facilitating image selection for the user. At least one HDC image thumbnail can be obtained from the HDC device after synchronization by the terminal device using the synchronization method described in the above embodiments.
[0363] Optionally, the third interface also includes a source identifier for each image, which indicates whether the image originates from the local terminal device or the HDC device.
[0364] For example, when the user clicks Figure 16b After the gallery selection control shown, the terminal device can display... Figure 16c The third interface shown includes thumbnails of local images and HDC images, where thumbnails a-c, e, g-i are thumbnails of local images, and thumbnails d and f are thumbnails of HDC images.
[0365] In some embodiments of this application, system applications or third-party applications in the terminal device can call the image picker component of the gallery application through PickAction. When the image picker component is called, the gallery application blends and presents local content and HDC content in the image picker, so that users can choose either images saved locally or images saved on the HDC device, making it easier and more convenient for users to select images.
[0366] S1506: The terminal device receives an operation performed by the user on the third interface, which is used to select an HDC image.
[0367] This operation involves the user selecting a thumbnail of an HDC image on the interface.
[0368] For example, this operation can be performed by the user in Figure 16c In the interface shown, select a thumbnail of an HDC image and click "Done".
[0369] S1507: The terminal device downloads the HDC image selected by the user from the HDC device.
[0370] Specifically, the gallery application in the terminal device can determine the corresponding metadata based on the thumbnail information of the HDC image selected by the user, obtain the HDC image download API based on the corresponding metadata, and drive the HDC service to download the HDC image from the HDC device by calling the download API.
[0371] After downloading an HDC image from an HDC device, the terminal device can store the downloaded HDC image locally and provide its local Uniform Resource Identifier (URI) to system applications or third-party applications. Subsequently, the system applications or third-party applications can use this URI to access the HDC image or perform other operations on it.
[0372] Optionally, before downloading the HDC image selected by the user from the HDC device, the terminal device may prompt the user to confirm whether to download the HDC image. If the user confirms the download based on the feedback, the terminal device will then perform the operation of downloading the image from the HDC device.
[0373] S1508: The terminal device displays a fourth interface, which includes an HDC image selected by the user.
[0374] For example, when the user is Figure 16cAfter selecting a thumbnail of an HDC image (thumbnail d) in the interface shown and clicking "Done", the terminal device can display as follows: Figure 16d The fourth interface shown is compared to Figure 16a The first interface shown adds the user-selected image (image d corresponding to thumbnail d), enabling the addition of an image from the HDC device to the Notes app. For users, this can be achieved within the Notes app itself, making the process extremely simple and significantly improving the user experience.
[0375] It should be noted that the specific implementation processes provided in the above examples are merely illustrative examples of the applicable method processes in the embodiments of this application. The execution order of each step can be adjusted according to actual needs, and other steps can be added or some steps can be removed. The method processes provided in the above examples can also be combined with the method processes provided in other examples to achieve the solution provided in the embodiments of this application.
[0376] Based on the above embodiments and the same concept, this application also provides a content management method applied to a first electronic device, the first electronic device including a first service and a first application, such as... Figure 17 As shown, the method includes:
[0377] S1701: The first service obtains first information and second information, and stores the first information and the second information; wherein, the first information is used to identify first media content stored in the first electronic device, and the second information is used to identify second media content stored in the second electronic device.
[0378] For example, the first electronic device may be the terminal device described in the above embodiments, and the second electronic device may be the HDC device described in the above embodiments.
[0379] In some embodiments of this application, the first application is any application installed on the first electronic device. The first service resides in the application framework layer of the operating system of the first electronic device. For example, the first service may include the media library and HDC service described in the above embodiments, and the first application may be a system application or a third-party application as described in the above embodiments.
[0380] In some embodiments of this application, the first application may obtain the first information and / or the second information from the first service through a first interface provided by the first service. For example, the first interface may be as described in the above embodiments. Figure 5 The media library shown provides the access interface.
[0381] In some embodiments of this application, the first media content and the second media content may be images or videos, and the first information and the second information may be thumbnails as described in the above embodiments.
[0382] In some embodiments of this application, the first metadata corresponding to the first media content contains first information, and the second metadata corresponding to the second media content contains second information. The first service can achieve the effect of obtaining and storing the first and second information by obtaining and storing the first metadata, and obtaining and storing the second metadata.
[0383] The first metadata and the first media content are stored locally on the first electronic device, and the first service can directly retrieve this content from the local storage. The first service can obtain the second metadata and the second media content through downlink synchronization with the second electronic device.
[0384] In the solution provided in this application embodiment, the first service can periodically perform a synchronization process with the second electronic device, or the first service can perform a synchronization process with the second electronic device when the stored media content and / or metadata changes. The synchronization process includes a downlink synchronization process and / or an uplink synchronization process. When the synchronization process includes both downlink and uplink synchronization processes, the downlink synchronization process can be executed first, followed by the uplink synchronization process, or vice versa. Changes in the media content stored in the first electronic device can occur when the first electronic device adds stored media content, or when the stored media content in the first electronic device is modified or deleted, or when the metadata synchronized from the second electronic device and stored in the first electronic device is deleted.
[0385] The first service can trigger downlink synchronization and / or uplink synchronization when determining the start time of the arrival period, or it can trigger downlink synchronization and / or uplink synchronization when it determines that the stored media content and / or the stored metadata from the second electronic device has changed. After triggering downlink synchronization, the first service can send synchronization indication information to the second electronic device. This indication information instructs the second electronic device to send downlink synchronization information to the first service. The downlink synchronization information can instruct at least one of the following: sending metadata corresponding to newly added media content in the second electronic device to the first service; sending modified metadata or metadata corresponding to modified media content in the second electronic device to the first service; or indicating metadata corresponding to deleted media content in the second electronic device to the first service. After the second electronic device sends the corresponding information to the first service according to the indication, the first service can determine the changes in the media content and metadata in the second electronic device based on this information, and then update its own stored metadata accordingly.
[0386] In one possible scenario, the aforementioned second media content could be newly added media content to the second electronic device after the previous downlink synchronization process. In this case, when the first service determines to execute the downlink synchronization process, it can first instruct the second electronic device to send downlink synchronization information to the first service. Upon receiving the instruction, the second electronic device determines that the second media content was added after the previous downlink synchronization process. The second electronic device can then send downlink synchronization information to the first service containing second metadata and first indication information. The first indication information indicates that the second metadata corresponds to the metadata of the media content added to the second electronic device. Based on the received first indication information, the first service can then determine that only the second metadata needs to be stored, and thus the first service stores the second metadata.
[0387] In another possible scenario, the second media content could be media content obtained by modifying the third media content after the previous synchronization process by the second electronic device. Since the third media content was stored by the second electronic device before the previous synchronization process, during the previous downlink synchronization process, the first service could obtain and store the third metadata corresponding to the third media content from the second electronic device. After the second electronic device modifies the third media content to obtain the second media content, the third metadata is updated accordingly to the second metadata. Therefore, when determining to execute the current downlink synchronization process, the first service needs to obtain the second metadata from the second electronic device to update the previously stored third metadata. The first service can then instruct the second electronic device to send downlink synchronization information to the first service. Upon receiving the instruction, the second electronic device determines that the second media content is the modified third media content and can then send the downlink synchronization information containing the second metadata and the second indication information to the first service; wherein the second indication information indicates that the second metadata is metadata obtained after modifying the third metadata. The first service can then determine, based on the second indication information, to update the stored third metadata using the second metadata, and thus update the third metadata to the second metadata. When the first service updates the third metadata to the second metadata, it can replace the corresponding content in the third metadata with the content in the second metadata that differs from the third metadata; that is, it only replaces the changed content in the third metadata. Alternatively, the first service can first delete the third metadata and then save the second metadata, which can also achieve the effect of updating the third metadata to the second metadata.
[0388] In the above method, the second electronic device may only modify the third metadata corresponding to the third media content to the second metadata, while the third media content itself remains unchanged. In this case, the second media content is the third media content. After the first service triggers this downlink synchronization process, the second electronic device also needs to indicate the second metadata and the information that the second metadata is the modified third metadata to the first service according to the above method, so that the first service updates the stored third metadata to the second metadata.
[0389] In another possible scenario, after the first service acquires and stores the second metadata, if the second electronic device deletes the second media content and its corresponding second metadata, then when the first service performs the downlink synchronization process again, the first service can instruct the second electronic device to send downlink synchronization information to the first service. Upon receiving this instruction, the second electronic device determines that the second media content and the second metadata have been deleted, and then sends downlink synchronization information containing third instruction information to the first service. This third instruction information indicates that the second metadata corresponds to the media content deleted by the second electronic device. The first service can then determine to delete the second metadata based on the third instruction information, and thus delete the stored second metadata. Optionally, the third instruction information is included in the aforementioned synchronization instruction information, and the first service can send the third instruction information to the second electronic device by sending the aforementioned synchronization instruction information.
[0390] S1702: The first application obtains the first information and / or the second information from the first service.
[0391] After the first service acquires and stores the first metadata and the second metadata, the first application can access the first metadata and the second metadata through the first interface provided by the first service, thereby determining the corresponding first information and second information, and can display them to the user so that the user can know the content stored in the first electronic device and the second electronic device.
[0392] S1703: The first application displays the first information and / or the second information.
[0393] In some embodiments of this application, after the first application displays the first information and the second information, or after the first application displays the second information, the user can instruct the first application to store the second media content identified by the second information locally on the first electronic device by performing a corresponding operation. Then, the first application can instruct a first service to obtain and store the second media content. The first service can obtain and store the second media content from the second electronic device, and can also provide the second media content to the first application. After the first service provides the second media content to the first application, the first application can display the media content to the user. And based on the user's operation, the first application can determine whether to modify or delete the second media content and the second metadata.
[0394] Specifically, when the first application modifies the second media content to the seventh media content based on the user's operation, the first application instructs the first service to update the second media content to the seventh media content and update the second metadata to the fourth metadata corresponding to the seventh media content. The first service, according to the instruction of the first application, updates the stored second media content to the seventh media content and updates the stored second metadata to the fourth metadata. After updating the second media content to the seventh media content, the first service can trigger an uplink synchronization process. During the uplink synchronization process, the first service can send the seventh media content, the fourth metadata, and fifth instruction information to the second electronic device; wherein the fifth instruction information is used to instruct: update the stored second media content to the seventh media content, and update the stored second metadata to the fourth metadata. Then, the second electronic device can update the stored second media content to the seventh media content and update the stored second metadata to the fourth metadata according to the instruction of the first service.
[0395] When the first application receives an instruction from the user to delete the second media content and second metadata stored in both the first and second electronic devices, the first application may first determine whether the second media content is already stored in the first electronic device. If so, the first application instructs the first service to delete the second media content and second metadata, and the first service deletes the stored second media content and second metadata accordingly. Otherwise, the first application may only instruct the first service to delete the second metadata, and the first service deletes the stored second metadata accordingly. After deleting the stored second media content and second metadata, or after deleting the second metadata, the first service may trigger an uplink synchronization process. During the uplink synchronization process, the first service instructs the second electronic device to delete the stored second media content and second metadata.
[0396] In some embodiments of this application, the first electronic device further includes a second application, and after step S1701 above, the following steps S1704 to S1705 may also be included:
[0397] S1704: The second application obtains the first information and / or the second information from the first service.
[0398] S1705: The second application displays the first information and / or the second information.
[0399] The method by which the second application acquires and displays the first information and / or the second information can be referred to the method by which the first application acquires and displays the first information and / or the second information, and will not be repeated here.
[0400] The specific execution process of each of the above steps can be referred to the relevant description in the previous embodiments, and will not be repeated here.
[0401] Based on the above embodiments and the same concept, this application also provides an electronic device for implementing the content management method provided in this application. For example... Figure 18 As shown, the electronic device 1800 may include: a display screen 1801, a memory 1802, one or more processors 1803, and one or more computer programs (not shown). These devices may be coupled via one or more communication buses 1804.
[0402] The display screen 1801 is used to display images, videos, application interfaces, and other related user interfaces. The memory 1802 stores one or more computer programs (code), which include computer instructions; one or more processors 1803 call the computer instructions stored in the memory 1802, causing the electronic device 1800 to execute the content management method provided in this application embodiment.
[0403] In a specific implementation, the memory 1802 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 1802 may store an operating system (hereinafter referred to as the system), such as Android, iOS, Windows, or embedded operating systems like Linux. The memory 1802 can be used to store implementation programs of the embodiments of this application. The memory 1802 may also store network communication programs, which can be used to communicate with one or more additional devices, one or more user devices, or one or more network devices. The one or more processors 1803 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of programs in the scheme of this application.
[0404] It needs to be explained that, Figure 18 This is merely one implementation of the electronic device 1800 provided in this application embodiment. In actual applications, the electronic device 1800 may include more or fewer components, which is not limited here.
[0405] Based on the above embodiments and the same concept, this application also provides a content management system, including: a first electronic device and a second electronic device, wherein the first electronic device includes a first service and a first application; the first electronic device is used to: obtain first information and second information through the first service, and store the first information and the second information; wherein the first information is used to identify first media content stored in the first electronic device, and the second information is used to identify second media content stored in the second electronic device; obtain the first information and / or the second information from the first service through the first application; and display the first information and / or the second information through the first application.
[0406] In one possible design, the second electronic device is a home storage device.
[0407] In one possible design, the first electronic device is further configured to: determine, via the first application, that the second media content needs to be obtained; send a content acquisition request to the first service via the first application, the content acquisition request being used to request the second media content; in response to the received content acquisition request, request the second electronic device to obtain the second media content via the first service; the second electronic device is configured to send the second media content to the first service; the first electronic device is further configured to: receive the second media content from the second electronic device via the first service and send the second media content to the first application; and display the second media content upon receiving it via the first application.
[0408] It should be noted that the method executed by the first electronic device in this system can refer to the method executed by the terminal device or the first electronic device described in the above embodiments, and the method executed by the second electronic device in this system can refer to the method executed by the HDC device or the second electronic device described in the above embodiments, which will not be repeated here.
[0409] Based on the above embodiments and the same concept, this application also provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the method provided in the above embodiments of this application.
[0410] Based on the above embodiments and the same concept, this application also provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run on a computer, the computer performs the method provided in the above embodiments of this application.
[0411] The methods provided in this application can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented in software, they can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media (e.g., floppy disk, hard disk, magnetic tape), optical media (e.g., digital video disc (DVD), or semiconductor media (e.g., SSD), etc.
[0412] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.
Claims
1. A content management method applied to a first electronic device, the first electronic device including a first service and a first application, characterized in that, The method includes: The first service acquires first information and second information, and stores the first information and the second information; wherein, the first information is used to identify first media content stored in the first electronic device, and the second information is used to identify second media content stored in the second electronic device; the first service is used to provide multiple applications in the first electronic device with access to the first information and the second information, as well as the first media content and the second media content; The first application obtains the first information and / or the second information from the first service; The first application displays the first information and / or the second information; The method further includes: The first application instructs the first service to obtain the second media content identified by the second information; The first service obtains the second media content from the second electronic device and stores the second media content; The first application obtains the second media content from the first service; The first application modifies the second media content and instructs the first service to update the second media content and the corresponding second information; The first service will synchronize the updated second media content and the second information to the second electronic device via uplink.
2. The method as described in claim 1, characterized in that, The first electronic device also includes a second application; After the first service obtains the first information and the second information, and stores the first information and the second information, the method further includes: The second application obtains the first information and / or the second information from the first service; The second application displays the first information and / or the second information.
3. The method as described in claim 1 or 2, characterized in that, The first application obtains the first information and / or the second information from the first service, including: The first application obtains the first information and / or the second information from the first service through the first interface provided by the first service.
4. The method according to any one of claims 1 to 3, characterized in that, The first metadata corresponding to the first media content contains the first information, and the second metadata corresponding to the second media content contains the second information; The first service acquires first information and second information, and stores the first information and the second information, including: The first service acquires and stores the first metadata, and the first service acquires and stores the second metadata.
5. The method as described in claim 4, characterized in that, The first service obtains the second metadata and stores the second metadata, including: The first service performs a downlink synchronization process; wherein the downlink synchronization process includes: The first service instructs the second electronic device to send downlink synchronization information to the first service; The first service receives the downlink synchronization information sent by the second electronic device; wherein the downlink synchronization information includes the second metadata and the first indication information, the first indication information being used to indicate that: the second metadata is metadata corresponding to media content added to the second electronic device; The first service determines to store the second metadata based on the first indication information; The first service stores the second metadata.
6. The method as described in claim 4, characterized in that, Before the first service obtains and stores the second metadata, the method further includes: The first service acquires and stores the third metadata; wherein the third metadata is metadata corresponding to the third media content stored in the second electronic device; The first service obtains the second metadata and stores the second metadata, including: The first service performs a downlink synchronization process; wherein the downlink synchronization process includes: The first service instructs the second electronic device to send downlink synchronization information to the first service; The first service receives the downlink synchronization information from the second electronic device, wherein the downlink synchronization information includes the second metadata and the second indication information; the second indication information is used to indicate that: the second metadata is metadata obtained by modifying the third metadata; and the second media content is the third media content or the modified third media content. The first service determines, based on the second instruction information, to update the stored third metadata using the second metadata; The first service updates the third metadata to the second metadata.
7. The method as described in claim 4, characterized in that, After the first service obtains and stores the second metadata, the method further includes: The first service performs a downlink synchronization process; wherein the downlink synchronization process includes: The first service instructs the second electronic device to send downlink synchronization information to the first service; The first service receives the downlink synchronization information from the second electronic device, wherein the downlink synchronization information includes third indication information, the third indication information being used to indicate that: the second metadata is metadata corresponding to media content deleted from the second electronic device; The first service determines to delete the second metadata based on the third instruction information; The first service deletes the stored second metadata.
8. The method according to any one of claims 4 to 7, characterized in that, After the first application displays the first information and the second information, or after the first application displays the second information, the method further includes: When the first application determines to delete the second metadata, it sends a fourth indication message to the first service; wherein the fourth indication message is used to indicate the deletion of the second metadata; In response to the received fourth instruction information, the first service deletes the second metadata.
9. The method according to any one of claims 4 to 7, characterized in that, The first application modifies the second media content and instructs the first service to update the second media content and the corresponding second information, including: The first application modifies the second media content to the seventh media content, and instructs the first service to update the second media content to the seventh media content and update the second metadata to the fourth metadata; wherein, the fourth metadata is the metadata corresponding to the seventh media content; The first service updates the second media content to the seventh media content and updates the second metadata to the fourth metadata.
10. The method as described in claim 9, characterized in that, The first service will uplink and synchronize the updated second media content and the second information to the second electronic device, including: The first service performs an uplink synchronization process; wherein, the uplink synchronization process includes: The first service sends the seventh media content, the fourth metadata, and the fifth instruction information to the second electronic device; wherein the fifth instruction information is used to instruct: to update the stored second media content to the seventh media content, and to update the stored second metadata to the fourth metadata.
11. The method according to any one of claims 4 to 7, characterized in that, After the first service obtains the second media content from the second electronic device and stores the second media content, the method further includes: When the first application determines to delete the second media content and the second metadata, it sends a sixth instruction message to the first service; wherein the sixth instruction message is used to instruct the deletion of the second media content and the second metadata; In response to the received sixth instruction information, the first service deletes the stored second media content and the second metadata.
12. The method as described in claim 8 or 11, characterized in that, The method further includes: The first service performs an uplink synchronization process; wherein, the uplink synchronization process includes: The first service sends a seventh instruction message to the second electronic device; wherein the seventh instruction message is used to instruct: delete the stored second media content and the second metadata.
13. The method as described in claim 10 or 12, characterized in that, The first service performs an uplink synchronization process, including: The first service executes the uplink synchronization process when it determines the start time of the second cycle; or The first service executes the uplink synchronization process when it determines that the second media content stored in the first electronic device has been modified; or The first service performs the uplink synchronization process when it determines that the second metadata stored in the first electronic device has been deleted.
14. The method as described in claim 10, 12, or 13, characterized in that, The first electronic device is logged into the first user account; Before the first service performs the uplink synchronization process, the method further includes: The first service sends a synchronization lock acquisition request to the second electronic device. The synchronization lock acquisition request is used to request the acquisition of a synchronization lock. The synchronization lock is used to indicate: allowing the first electronic device to perform the uplink synchronization process and prohibiting the target electronic device from performing the uplink synchronization process. The target electronic device is an electronic device other than the first electronic device that is logged into the first user account. The first service receives synchronization lock indication information from the second electronic device, the synchronization lock indication information being used to indicate the synchronization lock; After the first service performs the uplink synchronization process, the method further includes: The first service sends a synchronization lock release request to the second electronic device, the synchronization lock release request being used to request the release of the synchronization lock.
15. The method according to any one of claims 1 to 8, characterized in that, After the first application obtains the first information and the second information from the first service, or after the first application obtains the second information from the first service, the method further includes: The first application determines to acquire the second media content; The first application sends a content retrieval request to the first service, the content retrieval request being used to request the retrieval of the second media content; In response to the received content acquisition request, the first service requests the second electronic device to acquire the second media content; The first service receives the second media content from the second electronic device and sends the second media content to the first application; After receiving the second media content, the first application displays the second media content.
16. The method according to any one of claims 1 to 8, characterized in that, After the first application displays the first information and the second information, the method further includes: In response to a received first operation, the first application displays the second information but does not display the first information; wherein the first operation is used to instruct only to view information about media content stored in the second electronic device.
17. The method according to any one of claims 1 to 16, characterized in that, The first media content and the second media content are images or videos, and the first information and the second information are thumbnails.
18. The method according to any one of claims 1 to 17, characterized in that, The first service resides in the application framework layer of the operating system of the first electronic device.
19. The method according to any one of claims 1 to 18, characterized in that, The second electronic device is a home storage device.
20. An electronic device, characterized in that, The electronic device includes a display screen, a memory, and one or more processors; The memory is used to store computer program code, which includes computer instructions; when the computer instructions are executed by the one or more processors, the electronic device performs the method as described in any one of claims 1 to 19.
21. A content management system, characterized in that, include: A first electronic device and a second electronic device, wherein the first electronic device includes a first service and a first application; The first electronic device is configured to: acquire first information and second information through the first service, and store the first information and the second information; wherein the first information is used to identify first media content stored in the first electronic device, the second information is used to identify second media content stored in the second electronic device, the first service is configured to provide multiple applications in the first electronic device with access to the first information and the second information, as well as the first media content and the second media content; acquire the first information and / or the second information from the first service through the first application; and display the first information and / or the second information through the first application. The first electronic device is further configured to: instruct the first service to obtain the second media content identified by the second information through the first application; obtain the second media content from the second electronic device through the first service and store the second media content; obtain the second media content from the first service through the first application; modify the second media content through the first application and instruct the first service to update the second media content and the corresponding second information; and uplink and synchronize the updated second media content and the second information to the second electronic device through the first service.
22. The system as claimed in claim 21, characterized in that, The second electronic device is a home storage device.
23. The system as described in claim 21 or 22, characterized in that, The first electronic device is further configured to: determine the acquisition of the second media content through the first application; and send a content acquisition request to the first service through the first application, wherein the content acquisition request is used to request the acquisition of the second media content; In response to the received content acquisition request, the first service requests the second electronic device to acquire the second media content. The second electronic device is used to send the second media content to the first service; The first electronic device is further configured to: receive the second media content from the second electronic device through the first service, and send the second media content to the first application.
24. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on an electronic device, causes the electronic device to perform the method as described in any one of claims 1 to 19.
Citation Information
Patent Citations
Method and apparatus for transferring digital content from a computer to a mobile handset
CN108040298A
Method and system for quickly synchronizing data under low-bandwidth network
CN108093007A
