WO2023066036A1 - 一种跨设备文件显示方法、设备及系统 - Google Patents

一种跨设备文件显示方法、设备及系统 Download PDF

Info

Publication number
WO2023066036A1
WO2023066036A1 PCT/CN2022/123906 CN2022123906W WO2023066036A1 WO 2023066036 A1 WO2023066036 A1 WO 2023066036A1 CN 2022123906 W CN2022123906 W CN 2022123906W WO 2023066036 A1 WO2023066036 A1 WO 2023066036A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
thumbnail
request
path
file thumbnail
Prior art date
Application number
PCT/CN2022/123906
Other languages
English (en)
French (fr)
Inventor
朱博帆
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023066036A1 publication Critical patent/WO2023066036A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/13—File access structures, e.g. distributed indices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/172—Caching, prefetching or hoarding of files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/176—Support for shared access to files; File sharing support
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a cross-device file display method, device, and system.
  • the device 1 may display thumbnails of multiple pictures or videos and other files in the device 2 for the user to select from and view the detailed information of the files.
  • Conventional cross-device file display needs to be realized with the help of a third-party customized application that can provide cross-device file access and viewing related functions, such as a third-party housekeeper application.
  • the first device such as a computer
  • the second device such as a mobile phone
  • the first device displays the butler shown in (b) in Figure 1 application interface.
  • the first device may obtain the thumbnail image of the album of the second device from the second device (ie, the mobile phone) in response to the user selecting the option of the backup album function on the housekeeper application interface shown in (b) in FIG. 1 . Further, the first device may display thumbnails of the aforementioned photo albums (as shown in (c) in FIG. 1 ) on the butler application interface of the second device for the user to select and view photos from.
  • cross-device file display method shown in FIG. 1 is highly dependent on third-party applications, and is limited to realize cross-device file display in the housekeeper application interface, which is inconvenient to use.
  • the present application provides a cross-device file display method, device and system, which can realize cross-device file display efficiently and quickly.
  • a cross-device file display method includes: a first device receives a file thumbnail display request.
  • the file thumbnail display request is initiated by the user, and the file thumbnail display request is used to request to display a first file thumbnail, and the first file thumbnail corresponds to one or more files on the second device.
  • the first device acquires the thumbnail image of the first file stored on the second device from the storage unit of the first device or from the second device.
  • the first device displays the first file thumbnail on an interface corresponding to the path of the file thumbnail display request.
  • the first device may provide the user with the ability to access files in the second device. For example, when the user needs to access the thumbnail image of a file under a certain path of the second device, the first device may acquire the second file corresponding to the file thumbnail display request from the storage unit of the first device according to the user's file thumbnail display request.
  • File thumbnails under the device path (such as the first file thumbnail)
  • obtain the file thumbnails stored under the corresponding path of the second device such as the first file thumbnail
  • the second device such as the first file thumbnail
  • the path corresponding to the file thumbnail display request belongs to the resource manager application of the first device, and the first device displays the first file thumbnail on the resource manager interface corresponding to the file thumbnail display request.
  • Sketch map exemplary, in this application, the first device can implement cross-device file display based on native operating system applications (such as resource manager applications), without resorting to third-party customized applications. Moreover, based on native application interfaces such as resource manager applications, users can be provided with a clearer and more intuitive cross-device file access and viewing experience.
  • the above method further includes: after the first device establishes a communication connection with the second device, on the resource manager application main interface Display the virtual drive letter of the second device.
  • the above-mentioned file thumbnail display request includes the following operations: the user clicks on the virtual icon of the folder in any path of the second device on the first device, double-clicks, selects the open option after a long press The operation of the operation, the right mouse button and select the operation of the open option.
  • This application does not limit the specific way for the user to access files in the second device, nor does it limit the specific device path for the user to access, which greatly improves the user experience.
  • the above method further includes: after the first device establishes a communication connection with the second device, receiving the second The thumbnail image of the file, and the corresponding relationship between the thumbnail image of the second file and the path; the first device stores the thumbnail image of the second file, and the corresponding relationship between the thumbnail image of the second file and the path in the storage unit; wherein, the thumbnail image of the second file Corresponding to all files on the second device, files of a preset type on the second device, or files under a preset path on the second device.
  • the first device caches the file thumbnails corresponding to all files in the second device after the second device establishes a communication connection, so that when there is a demand for cross-device file thumbnail display, it can respond quickly and in time.
  • the second file thumbnail includes the first file thumbnail
  • the first device acquires the first file thumbnail from a storage unit of the first device.
  • the first device caches the file thumbnails corresponding to all the files in the second device in the storage unit, so that when there is a demand for cross-device file thumbnail display, it can respond quickly and in time. For example, when the second file thumbnail includes the first file thumbnail, the first file thumbnail is directly acquired from the storage unit.
  • the above-mentioned first device obtains the first file thumbnail from the storage unit of the first device, including: the first device displays the corresponding path according to the file thumbnail display request, and the second file thumbnail and the path The corresponding relationship of the first file is obtained from the thumbnail of the second file. Based on the correspondence between the second file thumbnail and the path stored in the storage unit, when the first device receives the user's cross-device file thumbnail display request, it may determine the path based on the path corresponding to the file thumbnail display request The corresponding file thumbnail, such as the first file thumbnail.
  • the second file thumbnail does not include the first file thumbnail
  • the first device acquires the first file thumbnail from the second device.
  • the first device may directly acquire the latest and accurate first file thumbnail from the second device when the first file thumbnail is not cached.
  • the above-mentioned first device obtaining the first file thumbnail from the second device includes: the first device calls a custom thumbnail providing plug-in, and obtains the first file thumbnail from the second device; wherein, The custom thumbnail providing plug-in defines a plug-in for obtaining file thumbnails from corresponding devices and displaying file thumbnails on the interface corresponding to the path of the file thumbnail display request.
  • the first device can provide a plug-in for custom thumbnails to support obtaining file thumbnails from the corresponding device, and display the file thumbnails on the interface corresponding to the path of the file thumbnail display request plugin.
  • a custom thumbnail provider plug-in is ThumbnailProvider.dll.
  • the obtaining of the first file thumbnail by the first device from the second device includes: the first device sends a first request message to the second device, and the first request message carries a file thumbnail display The corresponding path is requested, and the first request message is used to request the thumbnail image of the file under the corresponding path; the first device receives the first thumbnail image of the file from the second device.
  • the first device may request the second device for thumbnail display of file thumbnails under a path corresponding to the request.
  • the above method further includes: in response to receiving the file opening request of the user for the first file, the first device sends a second request message to the second device, and the second request message carries the first The identifier of the thumbnail icon corresponding to the file, and the second request message is used to request the detailed information of the first file, and the first file is the file corresponding to any icon in the thumbnail of the first file.
  • the first device receives detailed information of the first file from the second device.
  • the first device displays the detailed information of the first file on an interface corresponding to the path of the file opening request.
  • the first device may provide the user with a service of accessing detailed information of a specific file in the file thumbnail. For example, the first device may obtain the detailed information of the file from the first device when the user needs to view the file. Through this mode of watching and transmitting, the transmission of too much redundant information and the occupation of transmission resources can be avoided.
  • the above-mentioned first file is a picture, video or audio.
  • a method for displaying cross-device files includes: after the second device establishes a communication connection with the first device, sending a second file thumbnail to the first device, and the second file thumbnail and the path Correspondence; wherein, the second file thumbnail corresponds to all files on the second device, files of a preset type on the second device, or files under a preset path on the second device.
  • the second device after the second device establishes a communication connection with the first device, the second device sends to the first device the file thumbnails corresponding to all the files in the second device, so that the first device receives the user's cross-device When the file thumbnail display is requested, it can respond quickly and in a timely manner.
  • the above method further includes: the second device receives a first request message carrying a path corresponding to the file thumbnail display request from the first device, where the first request message is used to request file thumbnails.
  • the second device sends a file thumbnail under a path corresponding to the file thumbnail presentation request to the first device, such as the first file thumbnail.
  • the second device may, according to the request of the first device, send the thumbnail image of the file under the path corresponding to the thumbnail display request to the first device.
  • the file thumbnail presentation request corresponds to a path belonging to an explorer application of the first device.
  • the first device can implement cross-device file display based on native operating system applications (such as resource manager applications), without resorting to third-party customized applications.
  • native operating system applications such as resource manager applications
  • users can be provided with a clearer and more intuitive cross-device file access and viewing experience.
  • the above method further includes: the second device receives a second request message from the first device, where the second request message carries the identifier of the thumbnail icon corresponding to the first file, and the second request The message is used to request detailed information of the first file, and the first file is a file corresponding to any icon in the thumbnail of the first file.
  • the second device sends detailed information of the first file to the first device.
  • the second device can send the detailed information of the file to the first device according to the request of the first device. Through this mode of watching and transmitting, the transmission of too much redundant information and the occupation of transmission resources can be avoided.
  • the above-mentioned first file is a picture, video or audio.
  • a method for displaying cross-device files includes: establishing a communication connection between a first device and a second device.
  • the second device sends the second file thumbnail and the corresponding relationship between the second file thumbnail and the path to the first device.
  • the second file thumbnail corresponds to all files on the second device, files of a preset type on the second device, or files under a preset path on the second device.
  • the first device stores the second file thumbnail and the corresponding relationship between the second file thumbnail and the path in the storage unit.
  • the second device after the second device establishes a communication connection with the first device, the second device sends the thumbnails of files corresponding to all files in the second device to the first device, so that the first device receives the user's cross-device When the file thumbnail display is requested, it can respond quickly and in a timely manner.
  • the second file thumbnail includes the first file thumbnail
  • the method further includes: the first device receives a file thumbnail display request for requesting to display the first file thumbnail; the first device The first file thumbnail is acquired from the storage unit of the first device; the first device displays the first file thumbnail on an interface corresponding to the path of the file thumbnail display request.
  • the first device caches the file thumbnails corresponding to all the files in the second device in the storage unit, so that when there is a demand for cross-device file thumbnail display, it can respond quickly and in time. For example, when the second file thumbnail includes the first file thumbnail, the first file thumbnail is directly acquired from the storage unit.
  • the above-mentioned first device obtains the first file thumbnail from the storage unit of the first device, including: the first device displays the corresponding path according to the file thumbnail display request, and the second file thumbnail and the path The corresponding relationship of the first file is obtained from the thumbnail of the second file. Based on the correspondence between the second file thumbnail and the path stored in the storage unit, when the first device receives the user's cross-device file thumbnail display request, it may determine the path based on the path corresponding to the file thumbnail display request The corresponding file thumbnail, such as the first file thumbnail.
  • This method can solve the problem of display interface freeze caused by the occupation of communication resources caused by the terminal device obtaining the original file from other devices and the time-consuming, which greatly optimizes the user experience and realizes more efficient and fast cross-device file Show experience.
  • the second file thumbnail does not include the first file thumbnail; the above method further includes: the first device receives a file thumbnail display request for requesting to display the first file thumbnail; the first The device sends a first request message to the second device, the first request message carries the path corresponding to the file thumbnail display request, and the first request message is used to request the file thumbnail under the corresponding path; the second device obtains the stored file thumbnail The thumbnail display requests the file thumbnails under the path corresponding to the request; the second device sends the first file thumbnail to the first device; the first device displays the first file thumbnail on the interface corresponding to the path corresponding to the file thumbnail display request.
  • the first device When the first device needs to access the thumbnail image of a file in a certain path of the second device, it can acquire the thumbnail image of the file stored in the corresponding path of the second device (such as first file thumbnail), and further displayed on the interface corresponding to the path of the file thumbnail display request.
  • the first device can solve the problem of display interface freeze caused by the occupation of communication resources caused by the terminal device obtaining the original file from other devices and the time-consuming, which greatly optimizes the user experience and realizes more efficient and fast cross-device file Show experience.
  • the above-mentioned first device obtaining the first file thumbnail from the second device includes: the first device calls a custom thumbnail providing plug-in, and obtains the first file thumbnail from the second device; wherein, The custom thumbnail providing plug-in defines a plug-in for obtaining file thumbnails from corresponding devices and displaying file thumbnails on the interface corresponding to the path of the file thumbnail display request.
  • the first device can provide a plug-in for custom thumbnails to support obtaining file thumbnails from the corresponding device, and display the file thumbnails on the interface corresponding to the path of the file thumbnail display request plugin.
  • a custom thumbnail provider plug-in is ThumbnailProvider.dll.
  • the path corresponding to the file thumbnail display request belongs to the resource manager application of the first device, and the first device displays the first file thumbnail on the resource manager interface corresponding to the file thumbnail display request.
  • Sketch map exemplary, in this application, the first device can implement cross-device file display based on native operating system applications (such as resource manager applications), without resorting to third-party customized applications. Moreover, based on native application interfaces such as resource manager applications, users can be provided with a clearer and more intuitive cross-device file access and viewing experience.
  • the above method further includes: after the first device establishes a communication connection with the second device, on the resource manager application main interface Display the virtual drive letter of the second device.
  • the above-mentioned file thumbnail display request includes the following operations: the user clicks on the virtual icon of the folder in any path of the second device on the first device, double-clicks, selects the open option after a long press The operation of the operation, the right mouse button and select the operation of the open option.
  • This application does not limit the specific way for the user to access files in the second device, nor does it limit the specific device path for the user to access, which greatly improves the user experience.
  • the above method further includes: in response to receiving the file opening request of the user for the first file, the first device sends a second request message to the second device, and the second request message carries the first The identifier of the thumbnail icon corresponding to the file, and the second request message is used to request the detailed information of the first file, and the first file is the file corresponding to any icon in the thumbnail of the first file.
  • the second device sends detailed information of the first file to the first device.
  • the first device displays the detailed information of the first file on an interface corresponding to the path of the file opening request.
  • the first device may provide the user with a service of accessing detailed information of a specific file in the file thumbnail. For example, the first device may obtain the detailed information of the file from the first device when the user needs to view the file. Through this mode of watching and transmitting, the transmission of too much redundant information and the occupation of transmission resources can be avoided.
  • the above-mentioned first file is a picture, video or audio.
  • a first device in a fourth aspect, includes: an input operation detection unit, configured to detect a user's file thumbnail display request; wherein, the file thumbnail display request is initiated by the user, and the file thumbnail display request It is used to request to display the first file thumbnail, and the first file thumbnail corresponds to one or more files on the second device.
  • the storage unit is used for storing the thumbnail image of the first file.
  • the processing unit is configured to obtain the thumbnail image of the first file stored on the second device from the storage unit; or obtain the thumbnail image of the first file stored on the second device from the second device through the transceiver unit.
  • a display unit configured to display the first file thumbnail on the interface corresponding to the path of the file thumbnail display request.
  • the first device may provide the user with the ability to access files in the second device. For example, when the user needs to access the thumbnail image of a file under a certain path of the second device, the first device may acquire the second file corresponding to the file thumbnail display request from the storage unit of the first device according to the user's file thumbnail display request. File thumbnails under the device path (such as the first file thumbnail), or obtain the file thumbnails stored under the corresponding path of the second device (such as the first file thumbnail) from the second device, and further display them in the file thumbnail On the interface that displays the path corresponding to the request.
  • this method it can solve the problem of display interface freeze caused by the occupation of communication resources caused by the terminal device obtaining the original file from other devices and the time-consuming, which greatly optimizes the user experience and realizes more efficient and fast cross-device file Show experience.
  • the path corresponding to the file thumbnail display request belongs to the resource manager application of the first device, and the display unit displays the first file thumbnail on the resource manager interface of the file thumbnail display request corresponding to the path .
  • the first device can implement cross-device file display based on native operating system applications (such as resource manager applications), without resorting to third-party customized applications.
  • native application interfaces such as resource manager applications, users can be provided with a clearer and more intuitive cross-device file access and viewing experience.
  • the display unit is further configured to, after the communication connection is established between the first device and the second device, display the virtual disk letter of the second device on the resource manager application main interface.
  • the above-mentioned input operation detection unit is specifically configured to: detect the user's single-click operation, double-click operation, and long-press selection of the open option on the folder virtual icon in any path of the second device on the first device The operation of the operation, the right mouse button and select the operation of the open option.
  • This application does not limit the specific way for the user to access files in the second device, nor does it limit the specific device path for the user to access, which greatly improves the user experience.
  • the above-mentioned transceiver unit is further configured to: receive the second file thumbnail from the second device after the communication connection is established between the first device and the second device, and the second file thumbnail and The corresponding relationship between the paths; the above-mentioned storage unit is specifically used to: store the second file thumbnail, and the corresponding relationship between the second file thumbnail and the path; wherein, the second file thumbnail corresponds to all files on the second device, and the second device A file of a preset type on the device, or a file under a preset path on the second device.
  • the first device caches the file thumbnails corresponding to all files in the second device after the second device establishes a communication connection, so that when there is a demand for cross-device file thumbnail display, it can respond quickly and in time.
  • the second file thumbnail includes the first file thumbnail.
  • the first device caches the file thumbnails corresponding to all the files in the second device in the storage unit, so that when there is a demand for cross-device file thumbnail display, it can respond quickly and in time. For example, when the second file thumbnail includes the first file thumbnail, the first file thumbnail is directly acquired from the storage unit.
  • the above processing unit is specifically configured to: obtain the first file thumbnail from the second file thumbnail according to the path corresponding to the file thumbnail display request and the corresponding relationship between the second file thumbnail and the path.
  • Sketch map Based on the correspondence between the second file thumbnail and the path stored in the storage unit, when the first device receives the user's cross-device file thumbnail display request, it may determine the path based on the path corresponding to the file thumbnail display request The corresponding file thumbnail, such as the first file thumbnail.
  • the second file thumbnail does not include the first file thumbnail.
  • the first device may directly acquire the latest and accurate first file thumbnail from the second device when the first file thumbnail is not cached.
  • the above-mentioned processing unit acquires the first file thumbnail from the second device through the transceiver unit, including: the processing unit invokes a custom thumbnail providing plug-in, and acquires the first file thumbnail from the second device through the transceiver unit. Thumbnail; wherein, the custom thumbnail providing plug-in defines a plug-in for obtaining a file thumbnail from a corresponding device and displaying the file thumbnail on the interface corresponding to the path of the file thumbnail display request.
  • the first device can provide a plug-in for custom thumbnails to support obtaining file thumbnails from the corresponding device, and display the file thumbnails on the interface corresponding to the path of the file thumbnail display request plugin.
  • a custom thumbnail provider plug-in is ThumbnailProvider.dll.
  • the above-mentioned transceiving unit acquiring the first file thumbnail from the second device includes: the transceiving unit sends a first request message to the second device, and the first request message carries a file thumbnail display request corresponding path, the first request message is used to request the thumbnail image of the file under the corresponding path; the transceiver unit receives the first thumbnail image of the file from the second device.
  • the first device may request the second device for thumbnail display of file thumbnails under a path corresponding to the request.
  • the above-mentioned transceiver unit is further configured to: send a second request message to the second device in response to the input operation detection unit receiving the user's file opening request for the first file, and the second request message carries There is an identification of the thumbnail icon corresponding to the first file, and the second request message is used to request detailed information of the first file, and the first file is a file corresponding to any icon in the thumbnail of the first file. And, receiving detailed information of the first file from the second device.
  • the first device displays the detailed information of the first file on an interface corresponding to the path of the file opening request.
  • the first device may provide the user with a service of accessing detailed information of a specific file in the file thumbnail. For example, the first device may obtain the detailed information of the file from the first device when the user needs to view the file. Through this mode of watching and transmitting, the transmission of too much redundant information and the occupation of transmission resources can be avoided.
  • the above-mentioned first file is a picture, video or audio.
  • a second device includes: a transceiver unit, configured to send a second file thumbnail to the first device after the second device establishes a communication connection with the first device, and the second file Correspondence between thumbnails and paths; wherein, the second file thumbnail corresponds to all files on the second device, files of a preset type on the second device, or files under a preset path on the second device.
  • the second device after the second device establishes a communication connection with the first device, the second device sends to the first device the file thumbnails corresponding to all files in the second device, so that the first device receives the user's cross-device When the file thumbnail display is requested, it can respond quickly and in a timely manner.
  • the transceiver unit is further configured to: receive a first request message carrying a path corresponding to the file thumbnail display request from the first device, where the first request message is used to request file thumbnails. And, send the file thumbnails under the path corresponding to the file thumbnail presentation request to the first device, such as the first file thumbnail.
  • the second device may, according to the request of the first device, send the thumbnail image of the file under the path corresponding to the thumbnail display request to the first device.
  • the file thumbnail presentation request corresponds to a path belonging to an explorer application of the first device.
  • the first device can implement cross-device file display based on native operating system applications (such as resource manager applications), without resorting to third-party customized applications.
  • native operating system applications such as resource manager applications
  • users can be provided with a clearer and more intuitive cross-device file access and viewing experience.
  • the above-mentioned transceiving unit is further configured to: receive a second request message from the first device, wherein the second request message carries the identifier of the thumbnail icon corresponding to the first file, and the second request message It is used to request the detailed information of the first file.
  • the first file is the file corresponding to any icon in the thumbnail of the first file.
  • the second device can send the detailed information of the file to the first device according to the request of the first device. Through this mode of watching and transmitting, the transmission of too much redundant information and the occupation of transmission resources can be avoided.
  • the above-mentioned first file is a picture, video or audio.
  • a first device includes: a memory for storing a computer program; a transceiver for receiving or sending a radio signal; a processor for executing the computer program, so that the first The device executes the method in any possible implementation manner of the first aspect.
  • a second device in a seventh aspect, includes: a memory for storing a computer program; a transceiver for receiving or sending a radio signal; a processor for executing the computer program, so that the second The device executes the method in any possible implementation manner of the second aspect.
  • a communication system in an eighth aspect, includes the first device in any possible implementation manner of the fourth aspect or the sixth aspect, and any possible implementation manner of the fifth aspect or the seventh aspect in the second device.
  • the communication system is used to implement the method in any possible implementation manner of the third aspect.
  • a computer-readable storage medium is provided.
  • Computer program code is stored on the computer-readable storage medium.
  • the processor implements any one of the first aspect or the second aspect. method in one possible implementation.
  • a chip system the chip system includes a processor, a memory, and computer program code is stored in the memory; when the computer program code is executed by the processor, the processor implements the first aspect or the first aspect.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • a computer program product comprising computer instructions.
  • the computer instructions When the computer instructions are run on the computer, the computer is made to implement the method in any possible implementation manner of the first aspect or the second aspect.
  • FIG. 1 is a schematic diagram of a conventional cross-device file display method
  • FIG. 2 is a schematic diagram of a hardware structure of a terminal device provided in an embodiment of the present application
  • FIG. 3 is a schematic diagram of a software structure of a terminal device provided in an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a resource manager interface provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a mobile phone resource interface in a resource manager provided by an embodiment of the present application
  • FIG. 6 is a schematic diagram of an interface of a mobile phone image thumbnail in an resource manager provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a process of displaying file thumbnails in an explorer provided by an embodiment of the present application.
  • Fig. 8 is two kinds of flowcharts for displaying file thumbnails in the resource manager provided by the embodiment of the present application.
  • FIG. 9 is a schematic diagram of another process for displaying file thumbnails in the resource manager provided by the embodiment of the present application.
  • FIG. 10 is a flow chart of displaying file thumbnails in the resource manager provided by the embodiment of the present application.
  • FIG. 11 is another flow chart for displaying file thumbnails in the resource manager provided by the embodiment of the present application.
  • FIG. 12 is a flowchart of a second device responding to a request for obtaining a thumbnail image of a file according to an embodiment of the present application
  • Fig. 13 is a flow chart of a first device providing users with viewing detailed information of files in the first device provided by an embodiment of the present application;
  • FIG. 14 is a flowchart of a second device responding to a request for obtaining detailed information of a file according to an embodiment of the present application
  • FIG. 15 is a schematic diagram of a custom thumbnail providing plug-in definition process provided by the embodiment of the present application.
  • FIG. 16 is an interactive diagram of a cross-device file display method provided by the embodiment of the present application.
  • FIG. 17 is a structural block diagram of a terminal device provided by an embodiment of the present application.
  • first and second are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of indicated technical features. Thus, a feature defined as “first” and “second” may explicitly or implicitly include one or more of these features. In the description of this embodiment, unless otherwise specified, “plurality” means two or more.
  • An embodiment of the present application provides a method for displaying cross-device files, which is used in a process in which a device (such as a first device) displays files in another device (such as a second device) to a user across devices.
  • a device such as a first device
  • the first device may display thumbnails of multiple files in the second device to the user across devices, so that the user may select a file to view.
  • the terminal device includes a display screen for cross-device file display.
  • the terminal device may include but not limited to a personal computer (personal computer, PC), a smart phone, a netbook, a tablet computer, a smart watch, a smart bracelet, a phone watch, Smart cameras, PDAs, personal digital assistants (PDAs), portable multimedia players (PMPs), augmented reality (AR)/virtual reality (VR) devices, televisions , projection equipment or somatosensory game consoles in human-computer interaction scenes, etc.
  • PDAs personal digital assistants
  • PMPs portable multimedia players
  • AR augmented reality
  • VR virtual reality
  • This application does not limit the specific functions and structures of the terminal device (including the first device and the second device).
  • FIG. 2 takes a smart phone as an example and shows a schematic diagram of a hardware structure of a terminal device (including a first device and a second device) provided in an embodiment of the present application.
  • the terminal device may include a processor 210, a memory (comprising an external memory interface 220 and an internal memory 221), a universal serial bus (universal serial bus, USB) interface 230, a charging management module 240, and a power management module 241 , battery 242, antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, audio module 270, speaker 270A, receiver 270B, microphone 270C, earphone jack 270D, sensor module 280, button 290, motor 291, indicator 292 , a camera 293, a display screen 294, and a subscriber identification module (subscriber identification module, SIM) card interface 295, etc.
  • SIM subscriber identification module
  • the sensor module 280 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.
  • the structure shown in the embodiment of the present invention does not constitute a specific limitation on the terminal device.
  • the terminal device may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components.
  • the illustrated components can be realized in hardware, software or a combination of software and hardware.
  • Processor 210 may include one or more processing units.
  • the processor 210 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a flight controller, Video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc.
  • application processor application processor
  • AP application processor
  • modem processor graphics processing unit
  • image signal processor image signal processor
  • ISP image signal processor
  • flight controller Video codec
  • digital signal processor digital signal processor
  • DSP digital signal processor
  • baseband processor baseband processor
  • neural network processor neural-network processing unit
  • a memory may also be provided in the processor 210 for storing instructions and data.
  • the memory in processor 210 is a cache memory.
  • the memory may hold instructions or data that the processor 210 has just used or recycled. If the processor 210 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 210 is reduced, thereby improving the efficiency of the system.
  • processor 210 may include one or more interfaces.
  • the interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transmitter (universal asynchronous receiver/transmitter, UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input and output (general-purpose input/output, GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and /or universal serial bus (universal serial bus, USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input and output
  • subscriber identity module subscriber identity module
  • SIM subscriber identity module
  • USB universal serial bus
  • the charging management module 240 is configured to receive charging input from the charger.
  • the power management module 241 is used for connecting the battery 242 , the charging management module 240 and the processor 210 .
  • the power management module 241 receives the input from the battery 242 and/or the charging management module 240 to provide power for the processor 210 , the internal memory 221 , the display screen 294 , the camera 293 , and the wireless communication module 260 .
  • the wireless communication function of the terminal device can be realized by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modem processor and the baseband processor.
  • Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in an end device can be used to cover single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas.
  • Antenna 1 can be multiplexed as a diversity antenna of a wireless local area network.
  • the antenna may be used in conjunction with a tuning switch.
  • the mobile communication module 250 can provide wireless communication solutions including 2G/3G/4G/5G/6G applied on terminal equipment.
  • the mobile communication module 250 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA) and the like.
  • the mobile communication module 250 can receive electromagnetic waves through the antenna 1, filter and amplify the received electromagnetic waves, and send them to the modem processor for demodulation.
  • the mobile communication module 250 can also amplify the signal modulated by the modem processor, convert it into electromagnetic wave and radiate it through the antenna 1 .
  • at least part of the functional modules of the mobile communication module 250 may be set in the processor 210.
  • at least part of the functional modules of the mobile communication module 250 and at least part of the modules of the processor 210 may be set in the same device.
  • the terminal device can transmit or receive the first request message, the second request message, and/or radio signals related to the embodiment of the present application through the antenna 1, the antenna 2 and the mobile communication module 250.
  • a modem processor may include a modulator and a demodulator.
  • the modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal.
  • the demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator sends the demodulated low-frequency baseband signal to the baseband processor for processing.
  • the low-frequency baseband signal is passed to the application processor after being processed by the baseband processor.
  • the application processor outputs a sound signal through an audio device (not limited to a speaker 270A, a receiver 270B, etc.), or displays an image or video through a display screen 294 .
  • the modem processor may be a stand-alone device. In some other embodiments, the modem processor may be independent of the processor 210, and be set in the same device as the mobile communication module 250 or other functional modules.
  • the wireless communication module 260 can provide wireless local area networks (wireless local area networks, WLAN) (such as WiFi network), Bluetooth (Bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions.
  • the wireless communication module 260 may be one or more devices integrating at least one communication processing module.
  • the wireless communication module 260 receives electromagnetic waves via the antenna 2 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 210 .
  • the wireless communication module 260 can also receive the signal to be sent from the processor 210 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 to radiate out.
  • the antenna 1 of the terminal device is coupled to the mobile communication module 250, and the antenna 2 is coupled to the wireless communication module 260, so that the terminal device can communicate with the network and other devices through wireless communication technology.
  • the wireless communication technology may include global system for mobile communications (GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), new wireless (new radio, NR ), BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc.
  • GSM global system for mobile communications
  • general packet radio service general packet radio service
  • CDMA code division multiple access
  • CDMA broadband Code division multiple access
  • WCDMA wideband code division multiple access
  • time division code division multiple access time-division code division multiple access
  • LTE long term evolution
  • new wireless new radio
  • the GNSS may include a global positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a Beidou navigation satellite system (beidou navigation satellite system, BDS), a quasi-zenith satellite system (quasi -zenith satellite system, QZSS) and/or satellite based augmentation systems (satellite based augmentation systems, SBAS), etc.
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • Beidou navigation satellite system beidou navigation satellite system
  • BDS Beidou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite based augmentation systems
  • the terminal device realizes the display function through the GPU, the display screen 294, and the application processor.
  • the GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering.
  • Processor 210 may include one or more GPUs that execute program instructions to generate or change display information.
  • the display screen 294 is used to display images, videos and the like.
  • Display 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 or an active matrix organic light emitting diode (active-matrix organic light emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diodes (quantum dot light emitting diodes, QLED), etc.
  • the terminal device may include 1 or N display screens 294, where N is a positive integer greater than 1.
  • the terminal device can render the resource manager interface through the GPU, and display the resource manager interface through the display screen 294 .
  • the terminal device can realize the shooting function through ISP, camera 293 , video codec, GPU, display screen 294 and application processor.
  • the external memory interface 220 may be used to connect an external memory card, such as a micro (storage card, SD) card, so as to expand the storage capacity of the terminal device.
  • the external memory card communicates with the processor 210 through the external memory interface 220 to implement a data storage function. Such as saving music, video and other files in the external memory card.
  • files (such as pictures, videos, audios, etc.) displayed across devices may be stored in an external memory card of the terminal device.
  • the internal memory 221 may be used to store computer-executable program codes including instructions.
  • the internal memory 221 may include an area for storing programs and an area for storing data.
  • the stored program area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.) and the like.
  • the storage data area can store data (such as audio data, phone book, etc.) created during the use of the terminal device.
  • the internal memory 221 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.
  • the processor 210 executes various functional applications and data processing of the terminal device by executing instructions stored in the internal memory 221 and/or instructions stored in the memory provided in the processor.
  • the internal memory 221 may be used to cache file thumbnails corresponding to files in other devices.
  • the terminal device can implement audio functions through the audio module 270, the speaker 270A, the receiver 270B, the microphone 270C, and the application processor. Such as music playback, recording, etc.
  • audio module 270 the speaker 270A, the receiver 270B and the microphone 270C, reference may be made to the introduction in conventional technologies.
  • the keys 290 include a power key, a volume key and the like.
  • the key 290 may be a mechanical key. It can also be a touch button.
  • the terminal device can receive key input and generate key signal input related to user settings and function control of the terminal device.
  • the hardware modules included in the terminal device shown in FIG. 2 are only described as examples, and do not limit the specific structure of the terminal device.
  • the terminal device may also include components such as a keyboard and a mouse.
  • the operating system (operating system, OS) of the terminal device may include but not limited to OS and other operating systems.
  • the software of the terminal equipment can be divided into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces.
  • the software structure of the terminal device can be divided into three layers from top to bottom: the application program layer (abbreviated as the application layer), the application program framework layer (referred to as the framework layer), the system library, the Android runtime and the kernel layer ( Also known as the driver layer).
  • the application layer can include a series of application packages, such as camera, gallery, calendar, call, map, navigation, bluetooth, music, video, short message, butler application (such as Computer Manager) and other applications.
  • application for convenience of description, the application program is referred to as application for short below.
  • the housekeeper application can support the terminal device to implement pairing, authentication, and establishment of communication connections between devices.
  • the application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer.
  • the application framework layer may include a window manager service (window manager service, WMS), an activity management server (activity manager service, AMS) and an input event management server (input manager service, IMS).
  • the application framework layer may also include a content provider, a view system, a phone manager, a resource manager, a notification manager, etc. (not shown in FIG. 3 ).
  • the system library and the Android runtime contain the functions that the framework layer needs to call, the core library, and virtual machine.
  • a system library can include multiple function modules. For example: browser kernel, three-dimensional (3 dimensional, 3D) graphics, font library, etc.
  • a system library can include multiple function modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer can include display drivers, input/output device drivers (for example, keyboards, touch screens, earphones, speakers, microphones, etc.), device nodes, camera drivers, audio drivers, and sensor drivers.
  • the user performs an input operation through the input device, and the kernel layer can generate corresponding original input events according to the input operation, and store them in the device node.
  • Input/output device drivers can detect user input events.
  • the microphone can detect the voice uttered by the user
  • the touch screen can detect the user's touch operation
  • the keyboard can detect the information or operation (such as selection operation) input by the user.
  • Figure 3 only uses the layered architecture Taking the system as an example, a software structure of a terminal device is introduced.
  • the present application does not limit the specific architecture of the software system of the terminal device, and for the specific introduction of software systems of other architectures, reference may be made to conventional technologies.
  • the embodiment of the present application provides a method for realizing cross-device file display based on native software and hardware of a terminal device.
  • the types of files displayed across devices may include but not limited to pictures, videos, audios, office documents (such as word documents, excel documents, txt documents, etc.), address books, compressed files, etc.
  • the first device can use the virtual disk technology based on the native resource manager to mount the second device as an independent drive letter to the resource manager of the first device, so that the user can The first device accesses files in the second device. It can be understood that this method can also greatly reduce barriers to cross-device file access, realize further integration between multiple devices, and allow users to conveniently and simply perform cross-device file access and viewing.
  • the resource manager is a resource management tool provided by the operating system of the terminal device.
  • the resource manager can display all resources in the terminal device in a tree-shaped file system structure, so it can provide users with a clearer and more intuitive file access and viewing experience.
  • the files in the terminal device can be displayed in the form of thumbnails in the subpath of the corresponding folder according to the file type. Therefore, realizing cross-device file display based on the resource manager interface can provide users with a very convenient cross-device file access experience.
  • the resource manager can be as The resource manager (Explorer) and the like are not limited in this application.
  • Figure 4 uses Windows As an example, a schematic diagram of an interface is shown in which a second device (such as a mobile phone) is mounted to a resource manager of a first device (such as a computer) with a virtual drive letter.
  • a communication connection is established between the computer (ie, the first device) and the mobile phone (ie, the second device), such as Bluetooth connection, WiFi direct connection, access to the same wireless local area network, etc., which is not limited in this application.
  • the user can access and view files in the mobile phone (that is, the second device) by opening the "My Mobile Phone” virtual disk.
  • the computer i.e. the first device
  • the computer responds to receiving the user's operation (such as double-clicking, right-clicking ⁇ opening, etc.) on the resource manager interface shown in Figure 4 to open the "My Mobile" virtual disk
  • the computer displays the mobile phone resource interface shown in FIG. 5 .
  • folders corresponding to multiple types of files in the mobile phone are displayed on the mobile phone resource interface, such as pictures, videos, audios, office documents, contacts and compressed files as shown in FIG. 5 .
  • the computer i.e. the first device
  • the computer responds to receiving the user's operation of opening the picture folder on the mobile phone resource interface shown in Figure 5 (such as double-clicking, right-clicking ⁇ opening, etc.), and the computer (i.e. the first device) displays the image folder.
  • 6 shows the mobile phone picture thumbnail interface. Based on the mobile phone picture thumbnail interface shown in FIG. 6 , the user can quickly view the pictures on the side of the mobile phone.
  • the file thumbnail displayed by the first device in the resource manager is generated by the first device according to the original file obtained from the second device.
  • the first device determines a device corresponding to a path corresponding to the request. If the device corresponding to the path corresponding to the above request is the second device, the first device obtains the original file from the second device. Then, the first device generates a file thumbnail according to the original file acquired from the second device, and further displays the file thumbnail on the resource manager interface corresponding to the path requested above.
  • the first device Take Windows on the first device Show the picture thumbnail of the second device as an example, as an example, after receiving the user's Windows
  • the picture thumbnail display request initiated on the interface such as the operation of the user opening the picture folder on the mobile phone resource interface shown in Figure 5
  • the first device starts from the second device.
  • the second device obtains the original picture, then generates a thumbnail image based on the original picture obtained from the first device, and further displays the Windows in the path corresponding to the above request On the interface; if the device corresponding to the path corresponding to the above request is the first device, the first device generates a thumbnail image based on the original image under the path corresponding to the above request, and further displays it on the Windows interface.
  • the computer when receiving the user's operation to open the picture folder on the mobile phone resource interface shown in Figure 5, the computer (i.e. the first device) obtains the information in the mobile phone (i.e. the second device) from the mobile phone (i.e. the second device). The complete picture is loaded into the computer (that is, the first device), and then a thumbnail is generated and displayed to the user on the interface shown in FIG. 6 .
  • the first device can store the file thumbnail in the thumbnail cache (that is, the storage unit, such as thumbcache_*.db) , for the convenience of next display. Therefore, as another example, as shown in (b) in FIG. .db) to find file thumbnails. If found, then in the resource manager (such as Windows ) interface; if not found, the first device determines the device corresponding to the path corresponding to the request.
  • the resource manager such as Windows
  • the first device obtains the original file from the second device, and then generates a file thumbnail based on the original file obtained from the second device, and further requests the resource corresponding to the path above File thumbnails are displayed on the manager interface.
  • the first device can first search for the image thumbnail in the thumbnail cache (such as thumbcache_*.db). Sketch map.
  • the first device obtains the original picture from the second device, and then generates a thumbnail image based on the original picture obtained from the first device, and further Windows showing the path corresponding to the above request On the interface; if the device corresponding to the path corresponding to the above request is the first device, the first device generates a thumbnail image based on the original image under the path corresponding to the above request, and further displays it on the Windows interface.
  • the data volume of the file is relatively large.
  • the types of files that can be viewed through this method are relatively limited, for example, only common types of files, such as pictures, videos, audios, etc., can usually be viewed.
  • the embodiment of the present application provides a more efficient and fast cross-device file display method, as shown in Figure 9, in this method, the first device can directly obtain the file stored in the second device from the second device
  • the file thumbnail (such as the first file thumbnail) is displayed on the explorer interface. Based on this, the problem of occupying communication resources and taking a lot of time due to the first device obtaining the original file from the second device can be solved, and the user experience is greatly optimized.
  • the first device executes the following S1002-S1005.
  • the file thumbnail display request includes but is not limited to the following operations: the user clicks on the virtual icon of the folder in any path of the second device on the first device, double-clicks, selects the open option after long pressing, and right-clicks Then select the operation of opening the option, etc., this application does not limit the specific operation type.
  • the first device determines the device corresponding to the path corresponding to the file thumbnail display request.
  • the computer that is, the first device
  • the device corresponding to the path corresponding to the above request ie path: my mobile phone: ⁇ picture
  • my mobile phone ie the second device
  • the device corresponding to the corresponding path is a computer (ie the first device).
  • the first device may determine the device corresponding to the path corresponding to the above request by calling a custom thumbnail providing plug-in (such as ThumbnailProvider.dll).
  • a custom thumbnail providing plug-in such as ThumbnailProvider.dll.
  • the first device may call ThumbnailProvider.dll, and determine the path corresponding to the above file thumbnail display request by customizing the Initialize() function.
  • the first device performs the following S1003-S1005; if the device corresponding to the path corresponding to the above request is the first device, the first device performs the following S1004-S1005.
  • the first device acquires a file thumbnail (such as the first file thumbnail) from the second device.
  • the first file thumbnail is stored in the second device.
  • the first device may obtain a file thumbnail from the second device by calling a custom thumbnail providing plug-in (such as ThumbnailProvider.dll).
  • a custom thumbnail providing plug-in such as ThumbnailProvider.dll.
  • the first device may call ThumbnailProvider.dll to obtain a file thumbnail from the second device through a custom GetThumbnail() function.
  • the first device may send a request message to the second device through an established communication connection (such as Bluetooth connection, WiFi direct connection, access to the same wireless local area network, etc.) with the second device, such as A first request message, where the first request message carries the path corresponding to the file thumbnail display request, so as to request the second device for the file thumbnail under the corresponding path.
  • an established communication connection such as Bluetooth connection, WiFi direct connection, access to the same wireless local area network, etc.
  • the second device such as A first request message, where the first request message carries the path corresponding to the file thumbnail display request, so as to request the second device for the file thumbnail under the corresponding path.
  • the communication connection between the first device and the second device may be established based on technologies such as touch connection, proximity connection, device discovery connection, etc., which are not limited in this application.
  • the second device after the second device receives the first request message (as shown in S1201 in FIG. 12) for obtaining a file thumbnail from the first device, it can traverse The thumbnail information of the file under the corresponding path of the second device (as shown in S1202 in FIG. 12 ). For example, the second device traverses the thumbnail information of the files under the corresponding path according to the path corresponding to the request carried in the first request message from the first device. Further, as shown in S1203 in FIG. 12, the second device sends the above-mentioned file thumbnail to the first device, so that the first device associates the above-mentioned file thumbnail from the second device with the above-mentioned file thumbnail display request correspondence under the path.
  • the second device can also record the mapping relationship between the above-mentioned file thumbnails and specific files (as shown in S1202 in FIG. 12), so that when the user views the file through the first device When the detailed information of any file in the file thumbnail is displayed, the detailed information of the corresponding file is sent to the first device in time. Further, the second device may also send the above-mentioned mapping relationship between the file thumbnail and the specific file to the second device.
  • the second device may also re-execute the above S1202 when the files on the second device are updated (such as deleting files, adding files, modifying files, etc.) to update the files in time.
  • the first device generates a file thumbnail (such as the first file thumbnail) according to the original file under the path corresponding to the file thumbnail display request.
  • the first device may generate a file thumbnail according to the original file in the path corresponding to the above request by calling the original file processing plug-in.
  • the original file processing plug-in can be PhotoMetadataHandler.dll.
  • PhotoMetadataHandler.dll For the specific introduction of PhotoMetadataHandler.dll, you can refer to the explanations and illustrations in the conventional technology, and the embodiments of this application will not repeat them.
  • the first device displays the file thumbnail (that is, the first file thumbnail) on the resource manager interface of the path corresponding to the file thumbnail display request.
  • the first device calls the custom thumbnail providing plug-in (such as ThumbnailProvider.dll) to perform the following steps: Determine the device corresponding to the path corresponding to the above image thumbnail display request.
  • the custom thumbnail providing plug-in such as ThumbnailProvider.dll
  • the device corresponding to the path corresponding to the above image thumbnail display request is the second device, obtain the image thumbnail from the second device and display it on Windows display on the interface; if the device corresponding to the path corresponding to the above picture thumbnail display request is the first device, call the original file processing plug-in (such as PhotoMetadataHandler.dll) to generate a picture thumbnail according to the original picture in the corresponding path in the first device and The thumbnails of the above pictures show the windows corresponding to the requested path displayed on the interface (as shown in Figure 6).
  • the original file processing plug-in such as PhotoMetadataHandler.dll
  • ThumbnailProvider.dll can display file thumbnails on the resource manager interface corresponding to the path of the above file thumbnail display request by customizing the GetThumbnail() function.
  • the first device obtains a file thumbnail from the second device after receiving a file thumbnail display request from the user as an example.
  • the first device obtains a file thumbnail from the second device.
  • the specific timing of the thumbnail is not limited.
  • the first device may also pre-cache file thumbnails (such as second file thumbnails) in the second device, for example, pre-cache all files in the second device
  • the thumbnails of the files, or pre-cache the thumbnails of the files of the preset type in the second device, or pre-cache the thumbnails of the files under the preset path in the second device which is not limited in this application.
  • the first device may acquire thumbnails of all files, preset types, or files in the preset path in the second device from the second device, and cache them in the thumbnail cache (that is, store unit, such as thumbcache_*.db), it is convenient to find the corresponding file thumbnail for displaying according to the path corresponding to the file thumbnail display request when receiving a file thumbnail display request from the user.
  • the thumbnail cache that is, store unit, such as thumbcache_*.db
  • the first device may also obtain the corresponding relationship between the thumbnail of the file and the path from the second device, so that when The path corresponding to the thumbnail display request and the corresponding relationship between the thumbnail and the path of the file are searched for the thumbnail of the corresponding file in the thumbnail cache (such as thumbcache_*.db) for display.
  • the thumbnail cache such as thumbcache_*.db
  • the first device pre-caches file thumbnails of multiple files in the second device in a thumbnail cache (such as thumbcache_*.db).
  • a thumbnail cache such as thumbcache_*.db
  • the first device After receiving the file thumbnail display request initiated by the user on the resource manager interface (ie S1001), the first device first searches the thumbnail cache (such as thumbcache_*.db) for the file under the path corresponding to the file thumbnail display request Thumbnail (ie S1101). If found, execute S1005, and display the resource manager (such as Windows ) interface; if not found, execute S1002-S1005. For the specific process of S1002-S1005, you can refer to the specific introduction of FIG. 10 above, and will not repeat them here.
  • the user can quickly browse the files on the second device side through the first device, or the user can further view the detailed information of any file.
  • the first file is a file corresponding to any icon in the file thumbnail.
  • S1301 The first device acquires detailed information of the first file from the second device.
  • the first device may send a request message, such as a second request message, to the second device through the established communication connection with the second device, and the second request message carries a thumbnail icon. ID, so as to request detailed information of the file corresponding to the ID from the second device.
  • a request message such as a second request message
  • the second device receives the second request message (as shown in S1401 in FIG. 14) for obtaining the detailed information of the first file from the first device
  • the first file corresponding to the above-mentioned identifier can be determined according to the identifier of the thumbnail icon carried in the second request message and the above-mentioned mapping relationship recorded by the second device (that is, the mapping relationship between the file thumbnail and the specific file) (as shown in FIG. 14 shown in S1402). Further, as shown in S1403 in FIG. 14 , the second device sends detailed information of the first file to the first device.
  • the detailed information of the first file is the original picture of the picture. If the first file is a video, the detailed information of the first file is the original video of the video.
  • the first device displays the detailed information of the first file on the resource manager interface of the path corresponding to the file opening request.
  • the first device displays the original picture of the picture on the explorer interface of the path corresponding to the file opening request. If the first file is a video, the first device plays the original video on the resource manager interface of the path corresponding to the file opening request.
  • a conventional operating system installation program cannot implement the method provided in the embodiment of the present application, in order to solve this problem.
  • it can be based on the component object model (such as A custom thumbnail providing plug-in (such as ThumbnailProvider.dll) based on the component object model (COM)).
  • a custom thumbnail providing plug-in such as ThumbnailProvider.dll
  • COM component object model
  • COM is used to specify the interface standard of software components.
  • an interface can be regarded as a class that contains a set of methods to be implemented.
  • multiple application programs are not a complete executable file, but are divided into some relatively independent plug-ins. Therefore, COM usually exists in the terminal device in the form of a plug-in.
  • the plug-in is a dynamic link library (dynamic-link library, dll) file.
  • dll dynamic-link library
  • a COM interface can inherit from a base interface.
  • the base interface (base interface) is such as the IUnknown interface.
  • the IUnknown interface has three method functions: QueryInterface() function, AddRef() function and Release() function.
  • the QueryInterface() function is used to query other interface pointers of a COM after obtaining an interface pointer of a certain COM.
  • the AddRef() function is used to increase the reference count.
  • the Release() function is used to decrement the reference count.
  • IUnknown interface can be defined as follows:
  • the custom thumbnail providing plug-in (such as ThumbnailProvider.dll) for displaying file thumbnails inherits the conventional base interface (such as the IUnknown interface), the conventional initialization interface 1 (such as IInitializeWithFile interface 1) and conventional thumbnail interface 1 (such as IThumbnailProvider interface 1), and improved the conventional initialization interface 1 and conventional thumbnail interface 1.
  • the conventional base interface such as the IUnknown interface
  • the conventional initialization interface 1 Such as IInitializeWithFile interface 1
  • conventional thumbnail interface 1 such as IThumbnailProvider interface 1
  • the method functions QueryInterface(), AddRef() and Release() are defined in the custom thumbnail providing plug-in, but also the method functions Initialize2() and GetThumbnail2() are defined.
  • the Initialize2 () function can be used to determine the path corresponding to the file thumbnail display request.
  • the GetThumbnail2() function can be used to judge the device corresponding to the path determined by the Initialize2() function, and obtain a file thumbnail from the corresponding device and display it on the resource manager interface.
  • the first device may load a custom thumbnail providing plug-in (such as ThumbnailProvider.dll) by calling a DllMain file (such as dllmain.cpp).
  • a DllMain file such as dllmain.cpp.
  • the DllMain file may include but not limited to one or more of the following entry point functions: DllMain() function, DllGetClassObject() function, DllCanUnloadNow() function, DllRegisterServer() function, DllUnregisterServer() function.
  • DllGetClassObject () function and DllCanUnloadNow () function are automatic registration and cancellation functions.
  • the DllMain() function is the entry function of the custom thumbnail provider plug-in (such as ThumbnailProvider.dll).
  • the DllGetClassObject() function is used to create COM objects. When creating a COM object, first load the library containing the COM object, and then obtain the COM interface pointer through the DllGetClassObject() function.
  • the DllCanUnloadNow() function is used to determine whether to release the DLL. For example, you can load the client module of the COM object through the DllGetClassObject() function, and then call the DllCanUnloadNow() function to ensure that the DLL is safely unloaded and released.
  • the DllRegisterServer() function is used to register the DLL in the registry generated by the operating system thumbnail.
  • the DllUnregisterServer() function is used to unregister the DLL in the registry generated by the operating system thumbnail.
  • the first device may save the custom thumbnail providing plug-in (such as ThumbnailProvider.dll) in a folder corresponding to the operating system, for example, under the path C: ⁇ Windows ⁇ System32.
  • plug-in such as ThumbnailProvider.dll
  • GUID globally unique identifier
  • GUID also called a universally unique identifier (UUID)
  • UUID universally unique identifier
  • the format of the GUID is "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx", where each x is a hexadecimal number in the range of 0-9 or a-f. For example: 550e8400-e29b-41d
  • a Cross-device file display methods include S1601-S1608:
  • S1601 The PC and/or the smart phone receives a request for establishing a communication connection between the PC and the smart phone.
  • the PC or the smart phone detects the other device due to being close to the other device, or discovers the other party through a device discovery technology, it is determined that a request for establishing a communication connection between the PC and the smart phone is received.
  • the PC establishes a transmission channel with the smart phone through the PC housekeeper application (that is, establishes a communication connection, such as a distributed file channel).
  • the PC in response to the operation of the user double-clicking the resource manager application icon, or right-clicking the resource manager application icon ⁇ open, the PC displays the resource manager interface (as shown in FIG. 4 ).
  • the resource manager interface includes a virtual drive letter of the smart phone (as shown in FIG. 4 "my mobile phone" virtual drive letter).
  • S1604 The smart phone sends the file thumbnails corresponding to the multiple files to the PC through the above transmission channel, and the corresponding relationship between the file thumbnails and paths.
  • the smart phone may traverse the thumbnail image information of the smart phone to find the file thumbnail, and record the corresponding relationship between the file thumbnail and the path.
  • S1605 The PC stores, in the cache, the file thumbnails corresponding to the plurality of files, and the corresponding relationship between the file thumbnails and paths.
  • the PC may store the file thumbnails corresponding to the above multiple files in a thumbnail cache (such as thumbcache_*.db), and the corresponding relationship between the file thumbnails and paths.
  • a thumbnail cache such as thumbcache_*.db
  • the file thumbnail display request includes but is not limited to the following operations: the user clicks on the virtual drive letter of the smartphone on the resource manager interface, double-clicks, long-presses and selects the open option, and selects the open option after the right mouse button Operation, etc., this application does not limit the specific operation type.
  • the file thumbnail display request is an operation such as opening a picture folder on the resource interface of the mobile phone shown in FIG. 5 .
  • the PC finds the file thumbnail in the cache corresponding to the path of the file thumbnail display request, the PC executes S1608; if the PC does not find the file thumbnail in the cache in the file thumbnail display path corresponding to the request, the PC executes S1607 and S1608.
  • S1607 The PC invokes a custom thumbnail providing plug-in (such as ThumbnailProvider.dll), and obtains the file thumbnail from the smart phone to display the file thumbnail in the path corresponding to the request.
  • a custom thumbnail providing plug-in such as ThumbnailProvider.dll
  • the PC calls the custom GetThumbnail() function in the custom thumbnail providing plug-in ThumbnailProvider.dll to obtain the file thumbnail from the smart phone and display the file thumbnail in the path corresponding to the request.
  • the PC may send a first request message to the smart phone through an established transmission channel with the smart phone, and the first request message carries the path corresponding to the above-mentioned file thumbnail display request, so as to request the smart phone A thumbnail of the file under the corresponding path.
  • S1608 The PC displays the thumbnail image of the file on the resource manager interface of the path corresponding to the request for displaying the thumbnail image of the file.
  • the PC may send a second request message to the smart phone through the established transmission channel with the smart phone, and the second request message carries an identifier of a thumbnail icon, so as to request the smart phone for a file corresponding to the corresponding identifier. Details.
  • S1610 The PC displays the detailed information of the first file on the resource manager interface of the path corresponding to the file opening request.
  • the first device displays the original picture of the picture on the explorer interface of the path corresponding to the file opening request. If the first file is a video, the first device plays the original video on the resource manager interface of the path corresponding to the file opening request.
  • the mobile phone can also update the information to the PC in real time when the file is updated. That is, as shown in Figure 16, the mobile phone can also perform the following S1611-S1612:
  • S1611 The mobile phone detects that the file is updated.
  • a file is updated, such as deleting a file, adding a file, modifying a file, etc., which is not limited in this embodiment of the present application.
  • S1612 The mobile phone updates the file thumbnail and the corresponding relationship between the file thumbnail and the path to the PC.
  • the file thumbnail display process can be performed based on the updated file thumbnail and the corresponding relationship between the file thumbnail and the path.
  • the PC receives a file opening request from the user next time, it can display the detailed information of the file based on the updated mapping relationship between the thumbnail image of the file and the file.
  • S1611-S1612 is executed after S1606-S1610 as an example, and this application does not limit the timing when the mobile phone updates information to the PC.
  • S1611-S1612 may also be executed before S1606-S1610, or during the execution of S1606-S1610, depending on the actual situation.
  • the terminal device can perform cross-device file compression by modifying the operating system installation program-related plug-ins and interfaces based on native software and hardware without resorting to third-party customized applications.
  • the logic of thumbnail display enables direct acquisition and cross-device display of file thumbnails on the terminal device side. Through this method, it is possible to solve the problem that the display interface freezes due to the occupation of communication resources caused by the terminal device obtaining the original file from other devices, and the time-consuming consumption, which greatly optimizes the user experience.
  • the cross-device file display method provided by the embodiment of the present application can be based on the native resource manager and use virtual disk technology to mount a device (such as the second device) as an independent drive letter to another device (such as the first device) in Explorer. Based on this, users can conveniently and simply access and view files across devices. Moreover, the file types that can be viewed by this method are more comprehensive than the conventional method.
  • serial numbers of the above-mentioned processes do not mean the order of execution, and the order of execution of the processes should be determined by their functions and internal logic, and should not be implemented in this application.
  • the implementation of the examples constitutes no limitation.
  • the terminal device includes corresponding hardware structures and/or software modules for performing various functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • the functional modules of the terminal device can be divided.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • the terminal device may include an input operation detection unit 1710 , a processing unit 1720 , a transceiver unit 1730 , a storage unit 1740 and a display unit 1750 .
  • the input operation detection unit 1710 is used to support the terminal device to detect the user's file thumbnail display request, file opening request and other request operations related to the embodiment of the present application.
  • the file thumbnail display request may include, but is not limited to, the user's single-click operation, double-click operation, operation of selecting the open option after a long press on the virtual icon of the folder under any path of the second device on the first device, and the right mouse button Then select the operation of the open option, etc.
  • the file opening request may include, but is not limited to, the user's single-click operation, double-click operation, long-press operation and operation of selecting an open option on a virtual icon of a certain file on the first device, or operation of selecting an open option after a right mouse button.
  • the storage unit 1740 is configured to store thumbnail images of files from the second device, and/or other information related to this embodiment of the present application.
  • the processing unit 1720 is used to support the terminal device to determine the device corresponding to the path corresponding to the file thumbnail display request, obtain the file thumbnail (such as the first file thumbnail) under the file thumbnail display request corresponding path from the storage unit 1740, and determine that the file is opened Files corresponding to the request, and/or other processes related to the embodiment of this application.
  • the transceiver unit 1730 is used to support the terminal device to obtain from the second device the file thumbnails corresponding to all the files on the second device, the file thumbnail display request corresponding to the file thumbnails corresponding to the path, the detailed information of the files, and/or the information related to the implementation of this application. Other processes related to the example.
  • the display unit 1750 is configured to support the terminal device to display file thumbnails, file detailed information, and/or other interfaces related to the embodiment of the present application.
  • the transceiver unit 1730 may include a radio frequency circuit.
  • the terminal device can receive and send wireless signals through a radio frequency circuit.
  • radio frequency circuitry includes, but is not limited to, an antenna, at least one amplifier, transceiver, coupler, low noise amplifier, duplexer, and the like.
  • radio frequency circuits can also communicate with other devices through wireless communication.
  • the wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile Communications, General Packet Radio Service, Code Division Multiple Access, Wideband Code Division Multiple Access, Long Term Evolution, Email, Short Message Service, etc.
  • each module in the terminal device may be implemented in the form of software and/or hardware, which is not specifically limited.
  • electronic equipment is presented in the form of functional modules.
  • the "module” here may refer to an application-specific integrated circuit ASIC, a circuit, a processor and memory executing one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated.
  • the available medium can be a magnetic medium, (such as a floppy disk, a hard disk, etc. , tape), optical media (such as digital video disk (digital video disk, DVD)), or semiconductor media (such as solid state disk (SSD)), etc.
  • the steps of the methods or algorithms described in conjunction with the embodiments of the present application may be implemented in hardware, or may be implemented in a manner in which a processor executes software instructions.
  • the software instructions can be composed of corresponding software modules, and the software modules can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage known in the art medium.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC may be located in the electronic device.
  • the processor and the storage medium may also exist in the terminal device as discrete components.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Software Systems (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

一种跨设备文件显示方法、设备及系统，涉及通信技术领域，可以基于终端设备原生软件和硬件，实现在终端设备侧直接获取文件缩略图并跨设备显示文件缩略图。本申请提供的方案无需借助第三方定制化应用，通过修改原生操作系统安装程序相关插件和接口，改变操作系统进行跨设备文件缩略图显示时的逻辑，实现直接获取并跨设备显示文件缩略图。通过该方法，可以解决由于终端设备从其他设备获取原文件导致的占用通信资源，耗时多导致的显示界面卡顿问题，极大优化了用户的使用体验。

Description

一种跨设备文件显示方法、设备及系统
本申请要求于2021年10月22日提交国家知识产权局、申请号为202111234902.8、申请名称为“一种跨设备文件显示方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种跨设备文件显示方法、设备及系统。
背景技术
随着终端技术的多样化发展，用户使用终端设备的范围从一个终端设备扩展到了多个终端设备。多个终端设备之间实现跨设备文件访问和查看可以为用户提供方便快捷的使用体验。
示例性的，设备1可以通过显示设备2中多个图片或视频等文件的缩略图，以供用户从中选择并查看文件详细信息。常规的跨设备文件显示需要借助能够提供跨设备文件访问和查看相关功能的第三方定制化应用实现的，如第三方管家应用等。如图1中的(a)所示，在第一设备(如电脑)与第二设备(如手机)建立通信连接之后，第一设备(即电脑)显示图1中的(b)所示管家应用界面。第一设备可以响应于用户在图1中的(b)所示管家应用界面上选择备份相册功能的选项，从第二设备(即手机)获取第二设备的相册缩略图。进一步的，第一设备可以在第二设备的管家应用界面上展示上述相册缩略图(如图1中的(c)所示)，以供用户从中选择并查看照片。
但是，图1所示跨设备文件显示方法对第三方应用依赖强，且仅限于在管家应用界面内实现跨设备文件显示，使用不便捷。
发明内容
本申请提供一种跨设备文件显示方法、设备及系统，可以高效、快捷地实现跨设备文件显示。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，提供一种跨设备文件显示方法，该方法包括：第一设备接收文件缩略图展示请求。其中，文件缩略图展示请求由用于发起，文件缩略图展示请求用于请求展示第一文件缩略图，第一文件缩略图对应第二设备上的一个或多个文件。第一设备从第一设备的存储单元或者从第二设备获取存储在第二设备上的第一文件缩略图。第一设备在文件缩略图展示请求对应路径的界面上展示第一文件缩略图。
上述第一方面提供的方案，第一设备可以为用户提供访问第二设备中文件的能力。例如，第一设备可以在用于有访问第二设备某一路径下文件缩略图的需求时，根据用户的文件缩略图展示请求从第一设备的存储单元获取文件缩略图展示请求对应的第二设备路径下的文件缩略图(如第一文件缩略图)，或者从第二设备获取存储在第二设备对应路径下的文件缩略图(如第一文件缩略图)，并进一步展示在文件缩略图展示请求对应路径的界面上。通过该方法，可以解决由于终端设备从其他设备获取原文件导致的占用通信资源，耗时多导致的显示界面卡顿问题，极大优化了用户的使用体验， 实现更加高效、快捷地跨设备文件显示体验。
在一种可能的实现方式中，上述文件缩略图展示请求对应路径属于第一设备的资源管理器应用，第一设备在上述文件缩略图展示请求对应路径的资源管理器界面上展示第一文件缩略图。示例性的，本申请中，第一设备可以基于原生操作系统应用程序(如资源管理器应用)实现跨设备文件显示，无需借助第三方定制化应用。并且，基于资源管理器应用等原生应用界面，可以为用户提供更加清楚、直观地跨设备文件访问和查看体验。
在一种可能的实现方式中，在上述第一设备接收文件缩略图展示请求之前，上述方法还包括：第一设备在与第二设备之间建立通信连接之后，在资源管理器应用主界面上显示第二设备的虚拟盘符。通过跨设备显示设备的虚拟盘符，可以为用户提供更加清楚、直观地跨设备文件访问和查看体验。
在一种可能的实现方式中，上述文件缩略图展示请求包括以下操作：用户在第一设备上对第二设备任意路径下文件夹虚拟图标的单击操作、双击操作、长按后选择打开选项的操作、鼠标右键后选择打开选项的操作。本申请不限定用户访问第二设备中文件的具体方式，也不限定用户访问的具体设备路径，极大提高了用户的使用体验。
在一种可能的实现方式中，在上述第一设备接收文件缩略图展示请求之前，上述方法还包括：第一设备在与第二设备之间建立通信连接之后，接收来自第二设备的第二文件缩略图，以及第二文件缩略图与路径的对应关系；第一设备将第二文件缩略图，以及第二文件缩略图与路径的对应关系保存在存储单元中；其中，第二文件缩略图对应第二设备上的所有文件，第二设备上预设类型的文件，或者第二设备上预设路径下的文件。第一设备通过在于第二设备建立通信连接之后缓存第二设备中所有文件对应的文件缩略图，以便在有跨设备文件缩略图展示需求时，可以快速、及时响应。
在一种可能的实现方式中，上述第二文件缩略图包括第一文件缩略图，则第一设备从第一设备的存储单元获取第一文件缩略图。第一设备通过在存储单元中缓存第二设备中所有文件对应的文件缩略图，以便在有跨设备文件缩略图展示需求时，可以快速、及时响应。例如，在第二文件缩略图包括第一文件缩略图时，直接从存储单元中获取第一文件缩略图。
在一种可能的实现方式中，上述第一设备从第一设备的存储单元获取第一文件缩略图，包括：第一设备根据文件缩略图展示请求对应的路径，以及第二文件缩略图与路径的对应关系，从第二文件缩略图中获取第一文件缩略图。基于存储单元中存储的第二文件缩略图与路径的对应关系，第一设备在接收到用户的跨设备文件缩略图展示请求时，可以以文件缩略图展示请求对应的路径为基准，确定该路径对应的文件缩略图，如第一文件缩略图。
在一种可能的实现方式中，上述第二文件缩略图不包括第一文件缩略图，则第一设备从第二设备获取第一文件缩略图。为了保证跨设备文件显示的准确性，第一设备可以在未缓存第一文件缩略图时，直接从第二设备获取最新的、准确的第一文件缩略图。
在一种可能的实现方式中，上述第一设备从第二设备获取第一文件缩略图，包括：第一设备调用自定义缩略图提供插件，从第二设备获取第一文件缩略图；其中，自定 义缩略图提供插件中定义了用于从相应设备获取文件缩略图，并在文件缩略图展示请求对应路径的界面上展示文件缩略图的插件。为了保证从第二设备直接获取文件缩略图，第一设备可以通过自定义的缩略图提供插件来支持从相应设备获取文件缩略图，并在文件缩略图展示请求对应路径的界面上展示文件缩略图的插件。
作为一种示例，自定义缩略图提供插件是ThumbnailProvider.dll。
在一种可能的实现方式中，上述第一设备从第二设备获取第一文件缩略图，包括：第一设备向第二设备发送第一请求消息，第一请求消息中携带有文件缩略图展示请求对应的路径，第一请求消息用于请求相应路径下的文件缩略图；第一设备接收来自第二设备的第一文件缩略图。为了保证跨设备文件缩略图展示的准确性，第一设备可以向第二设备请求缩略图展示请求对应的路径下的文件缩略图。
在一种可能的实现方式中，上述方法还包括：响应于接收到用户对第一文件的文件打开请求，第一设备向第二设备发送第二请求消息，第二请求消息中携带有第一文件对应的缩略图标的标识，所第二请求消息用于请求第一文件的详细信息，第一文件是第一文件缩略图中任意图标对应的文件。第一设备接收来自第二设备的第一文件的详细信息。第一设备在文件打开请求对应路径的界面上展示第一文件的详细信息。进一步的，第一设备可以向用户提供访问文件缩略图中某一具体文件详细信息的服务。例如，第一设备可以在用户有查看某一文件需求时，从第一设备获取该文件的详细信息。通过这种随看随传的方式，可以避免过多冗余信息的传输，对传输资源的占用。
在一种可能的实现方式中，上述第一文件是图片、视频或者音频。
第二方面，提供一种跨设备文件显示方法，该方法包括：第二设备在与第一设备建立通信连接之后，向第一设备发送第二文件缩略图，以及第二文件缩略图与路径的对应关系；其中，第二文件缩略图对应第二设备上的所有文件，第二设备上预设类型的文件，或者第二设备上预设路径下的文件。
上述第二方面提供的方案，第二设备在与第一设备建立通信连接之后，通过向第一设备发送第二设备中所有文件对应的文件缩略图，以便在第一设备接收到用户的跨设备文件缩略图展示请求时，可以快速、及时响应。
在一种可能的实现方式中，上述方法还包括：第二设备接收来自第一设备的携带有文件缩略图展示请求对应的路径的第一请求消息，其中第一请求消息用于请求相应路径下的文件缩略图。第二设备向第一设备发送文件缩略图展示请求对应的路径下的文件缩略图，如第一文件缩略图。为了保证跨设备文件缩略图展示的准确性，第二设备可以根据第一设备的请求，向第一设备发送缩略图展示请求对应的路径下的文件缩略图。
在一种可能的实现方式中，上述文件缩略图展示请求对应路径属于第一设备的资源管理器应用。示例性的，本申请中，第一设备可以基于原生操作系统应用程序(如资源管理器应用)实现跨设备文件显示，无需借助第三方定制化应用。并且，基于资源管理器应用等原生应用界面，可以为用户提供更加清楚、直观地跨设备文件访问和查看体验。
在一种可能的实现方式中，上述方法还包括：第二设备接收来自第一设备的第二请求消息，其中第二请求消息中携带有第一文件对应的缩略图标的标识，第二请求消 息用于请求第一文件的详细信息，第一文件是第一文件缩略图中任意图标对应的文件。第二设备向第一设备发送第一文件的详细信息。第二设备可以在用户有查看某一文件需求时，根据第一设备的请求向第一设备发送该文件的详细信息。通过这种随看随传的方式，可以避免过多冗余信息的传输，对传输资源的占用。
在一种可能的实现方式中，上述第一文件是图片、视频或者音频。
第三方面，提供一种跨设备文件显示方法，该方法包括：第一设备与第二设备建立通信连接。第二设备向第一设备发送第二文件缩略图，以及第二文件缩略图与路径的对应关系。其中，第二文件缩略图对应第二设备上的所有文件，第二设备上预设类型的文件，或者第二设备上预设路径下的文件。第一设备将第二文件缩略图，以及第二文件缩略图与路径的对应关系保存在存储单元中。
上述第三方面提供的方案，第二设备在与第一设备建立通信连接之后，通过向第一设备发送第二设备中所有文件对应的文件缩略图，以便在第一设备接收到用户的跨设备文件缩略图展示请求时，可以快速、及时响应。
在一种可能的实现方式中，上述第二文件缩略图包括第一文件缩略图，上述方法还包括：第一设备接收用于请求展示第一文件缩略图的文件缩略图展示请求；第一设备从第一设备的存储单元获取第一文件缩略图；第一设备在文件缩略图展示请求对应路径的界面上展示第一文件缩略图。第一设备通过在存储单元中缓存第二设备中所有文件对应的文件缩略图，以便在有跨设备文件缩略图展示需求时，可以快速、及时响应。例如，在第二文件缩略图包括第一文件缩略图时，直接从存储单元中获取第一文件缩略图。
在一种可能的实现方式中，上述第一设备从第一设备的存储单元获取第一文件缩略图，包括：第一设备根据文件缩略图展示请求对应的路径，以及第二文件缩略图与路径的对应关系，从第二文件缩略图中获取第一文件缩略图。基于存储单元中存储的第二文件缩略图与路径的对应关系，第一设备在接收到用户的跨设备文件缩略图展示请求时，可以以文件缩略图展示请求对应的路径为基准，确定该路径对应的文件缩略图，如第一文件缩略图。通过该方法，可以解决由于终端设备从其他设备获取原文件导致的占用通信资源，耗时多导致的显示界面卡顿问题，极大优化了用户的使用体验，实现更加高效、快捷地跨设备文件显示体验。
在一种可能的实现方式中，上述第二文件缩略图不包括第一文件缩略图；上述方法还包括：第一设备接收用于请求展示第一文件缩略图的文件缩略图展示请求；第一设备向第二设备发送第一请求消息，第一请求消息中携带有文件缩略图展示请求对应的路径，第一请求消息用于请求相应路径下的文件缩略图；第二设备获取存储的文件缩略图展示请求对应的路径下的文件缩略图；第二设备向第一设备发送第一文件缩略图；第一设备在文件缩略图展示请求对应路径的界面上展示第一文件缩略图。第一设备可以在用于有访问第二设备某一路径下文件缩略图的需求时，根据用户的文件缩略图展示请求从第二设备获取存储在第二设备对应路径下的文件缩略图(如第一文件缩略图)，并进一步展示在文件缩略图展示请求对应路径的界面上。通过该方法，可以解决由于终端设备从其他设备获取原文件导致的占用通信资源，耗时多导致的显示界面卡顿问题，极大优化了用户的使用体验，实现更加高效、快捷地跨设备文件显示体 验。
在一种可能的实现方式中，上述第一设备从第二设备获取第一文件缩略图，包括：第一设备调用自定义缩略图提供插件，从第二设备获取第一文件缩略图；其中，自定义缩略图提供插件中定义了用于从相应设备获取文件缩略图，并在文件缩略图展示请求对应路径的界面上展示文件缩略图的插件。为了保证从第二设备直接获取文件缩略图，第一设备可以通过自定义的缩略图提供插件来支持从相应设备获取文件缩略图，并在文件缩略图展示请求对应路径的界面上展示文件缩略图的插件。
作为一种示例，自定义缩略图提供插件是ThumbnailProvider.dll。
在一种可能的实现方式中，上述文件缩略图展示请求对应路径属于第一设备的资源管理器应用，第一设备在上述文件缩略图展示请求对应路径的资源管理器界面上展示第一文件缩略图。示例性的，本申请中，第一设备可以基于原生操作系统应用程序(如资源管理器应用)实现跨设备文件显示，无需借助第三方定制化应用。并且，基于资源管理器应用等原生应用界面，可以为用户提供更加清楚、直观地跨设备文件访问和查看体验。
在一种可能的实现方式中，在上述第一设备接收文件缩略图展示请求之前，上述方法还包括：第一设备在与第二设备之间建立通信连接之后，在资源管理器应用主界面上显示第二设备的虚拟盘符。通过跨设备显示设备的虚拟盘符，可以为用户提供更加清楚、直观地跨设备文件访问和查看体验。
在一种可能的实现方式中，上述文件缩略图展示请求包括以下操作：用户在第一设备上对第二设备任意路径下文件夹虚拟图标的单击操作、双击操作、长按后选择打开选项的操作、鼠标右键后选择打开选项的操作。本申请不限定用户访问第二设备中文件的具体方式，也不限定用户访问的具体设备路径，极大提高了用户的使用体验。
在一种可能的实现方式中，上述方法还包括：响应于接收到用户对第一文件的文件打开请求，第一设备向第二设备发送第二请求消息，第二请求消息中携带有第一文件对应的缩略图标的标识，所第二请求消息用于请求第一文件的详细信息，第一文件是第一文件缩略图中任意图标对应的文件。第二设备向第一设备发送第一文件的详细信息。第一设备在文件打开请求对应路径的界面上展示第一文件的详细信息。进一步的，第一设备可以向用户提供访问文件缩略图中某一具体文件详细信息的服务。例如，第一设备可以在用户有查看某一文件需求时，从第一设备获取该文件的详细信息。通过这种随看随传的方式，可以避免过多冗余信息的传输，对传输资源的占用。
在一种可能的实现方式中，上述第一文件是图片、视频或者音频。
第四方面，提供一种第一设备，该第一设备包括：输入操作检测单元，用于检测用户的文件缩略图展示请求；其中，文件缩略图展示请求由用于发起，文件缩略图展示请求用于请求展示第一文件缩略图，第一文件缩略图对应第二设备上的一个或多个文件。存储单元，用于存储第一文件缩略图。处理单元，用于从存储单元获取存储在第二设备上的第一文件缩略图；或者通过收发单元从第二设备获取存储在第二设备上的第一文件缩略图。显示单元，用于在文件缩略图展示请求对应路径的界面上展示第一文件缩略图。
上述第四方面提供的方案，第一设备可以为用户提供访问第二设备中文件的能力。 例如，第一设备可以在用于有访问第二设备某一路径下文件缩略图的需求时，根据用户的文件缩略图展示请求从第一设备的存储单元获取文件缩略图展示请求对应的第二设备路径下的文件缩略图(如第一文件缩略图)，或者从第二设备获取存储在第二设备对应路径下的文件缩略图(如第一文件缩略图)，并进一步展示在文件缩略图展示请求对应路径的界面上。通过该方法，可以解决由于终端设备从其他设备获取原文件导致的占用通信资源，耗时多导致的显示界面卡顿问题，极大优化了用户的使用体验，实现更加高效、快捷地跨设备文件显示体验。
在一种可能的实现方式中，上述文件缩略图展示请求对应路径属于第一设备的资源管理器应用，显示单元在上述文件缩略图展示请求对应路径的资源管理器界面上展示第一文件缩略图。示例性的，本申请中，第一设备可以基于原生操作系统应用程序(如资源管理器应用)实现跨设备文件显示，无需借助第三方定制化应用。并且，基于资源管理器应用等原生应用界面，可以为用户提供更加清楚、直观地跨设备文件访问和查看体验。
在一种可能的实现方式中，上述显示单元还用于，在第一设备与第二设备之间建立通信连接之后，在资源管理器应用主界面上显示第二设备的虚拟盘符。通过跨设备显示设备的虚拟盘符，可以为用户提供更加清楚、直观地跨设备文件访问和查看体验。
在一种可能的实现方式中，上述输入操作检测单元具体用于：检测用户在第一设备上对第二设备任意路径下文件夹虚拟图标的单击操作、双击操作、长按后选择打开选项的操作、鼠标右键后选择打开选项的操作。本申请不限定用户访问第二设备中文件的具体方式，也不限定用户访问的具体设备路径，极大提高了用户的使用体验。
在一种可能的实现方式中，上述收发单元还用于：在第一设备与第二设备之间建立通信连接之后，接收来自第二设备的第二文件缩略图，以及第二文件缩略图与路径的对应关系；上述存储单元具体用于：存储第二文件缩略图，以及第二文件缩略图与路径的对应关系；其中，第二文件缩略图对应第二设备上的所有文件，第二设备上预设类型的文件，或者第二设备上预设路径下的文件。第一设备通过在于第二设备建立通信连接之后缓存第二设备中所有文件对应的文件缩略图，以便在有跨设备文件缩略图展示需求时，可以快速、及时响应。
在一种可能的实现方式中，上述第二文件缩略图包括第一文件缩略图。第一设备通过在存储单元中缓存第二设备中所有文件对应的文件缩略图，以便在有跨设备文件缩略图展示需求时，可以快速、及时响应。例如，在第二文件缩略图包括第一文件缩略图时，直接从存储单元中获取第一文件缩略图。
在一种可能的实现方式中，上述处理单元具体用于：根据文件缩略图展示请求对应的路径，以及第二文件缩略图与路径的对应关系，从第二文件缩略图中获取第一文件缩略图。基于存储单元中存储的第二文件缩略图与路径的对应关系，第一设备在接收到用户的跨设备文件缩略图展示请求时，可以以文件缩略图展示请求对应的路径为基准，确定该路径对应的文件缩略图，如第一文件缩略图。
在一种可能的实现方式中，上述第二文件缩略图不包括第一文件缩略图。为了保证跨设备文件显示的准确性，第一设备可以在未缓存第一文件缩略图时，直接从第二设备获取最新的、准确的第一文件缩略图。
在一种可能的实现方式中，上述处理单元通过收发单元从第二设备获取第一文件缩略图，包括：处理单元调用自定义缩略图提供插件，通过收发单元从第二设备获取第一文件缩略图；其中，自定义缩略图提供插件中定义了用于从相应设备获取文件缩略图，并在文件缩略图展示请求对应路径的界面上展示文件缩略图的插件。为了保证从第二设备直接获取文件缩略图，第一设备可以通过自定义的缩略图提供插件来支持从相应设备获取文件缩略图，并在文件缩略图展示请求对应路径的界面上展示文件缩略图的插件。
作为一种示例，自定义缩略图提供插件是ThumbnailProvider.dll。
在一种可能的实现方式中，上述收发单元从第二设备获取第一文件缩略图，包括：收发单元向第二设备发送第一请求消息，第一请求消息中携带有文件缩略图展示请求对应的路径，第一请求消息用于请求相应路径下的文件缩略图；收发单元接收来自第二设备的第一文件缩略图。为了保证跨设备文件缩略图展示的准确性，第一设备可以向第二设备请求缩略图展示请求对应的路径下的文件缩略图。
在一种可能的实现方式中，上述收发单元还用于：响应于输入操作检测单元接收到用户对第一文件的文件打开请求，向第二设备发送第二请求消息，第二请求消息中携带有第一文件对应的缩略图标的标识，所第二请求消息用于请求第一文件的详细信息，第一文件是第一文件缩略图中任意图标对应的文件。以及，接收来自第二设备的第一文件的详细信息。第一设备在文件打开请求对应路径的界面上展示第一文件的详细信息。进一步的，第一设备可以向用户提供访问文件缩略图中某一具体文件详细信息的服务。例如，第一设备可以在用户有查看某一文件需求时，从第一设备获取该文件的详细信息。通过这种随看随传的方式，可以避免过多冗余信息的传输，对传输资源的占用。
在一种可能的实现方式中，上述第一文件是图片、视频或者音频。
第五方面，提供一种第二设备，该第二设备包括：收发单元，用于在第二设备与第一设备建立通信连接之后，向第一设备发送第二文件缩略图，以及第二文件缩略图与路径的对应关系；其中，第二文件缩略图对应第二设备上的所有文件，第二设备上预设类型的文件，或者第二设备上预设路径下的文件。
上述第五方面提供的方案，第二设备在与第一设备建立通信连接之后，通过向第一设备发送第二设备中所有文件对应的文件缩略图，以便在第一设备接收到用户的跨设备文件缩略图展示请求时，可以快速、及时响应。
在一种可能的实现方式中，上述收发单元还用于：备接收来自第一设备的携带有文件缩略图展示请求对应的路径的第一请求消息，其中第一请求消息用于请求相应路径下的文件缩略图。以及，向第一设备发送文件缩略图展示请求对应的路径下的文件缩略图，如第一文件缩略图。为了保证跨设备文件缩略图展示的准确性，第二设备可以根据第一设备的请求，向第一设备发送缩略图展示请求对应的路径下的文件缩略图。
在一种可能的实现方式中，上述文件缩略图展示请求对应路径属于第一设备的资源管理器应用。示例性的，本申请中，第一设备可以基于原生操作系统应用程序(如资源管理器应用)实现跨设备文件显示，无需借助第三方定制化应用。并且，基于资源管理器应用等原生应用界面，可以为用户提供更加清楚、直观地跨设备文件访问和 查看体验。
在一种可能的实现方式中，上述收发单元还用于：接收来自第一设备的第二请求消息，其中第二请求消息中携带有第一文件对应的缩略图标的标识，第二请求消息用于请求第一文件的详细信息，第一文件是第一文件缩略图中任意图标对应的文件。以及，向第一设备发送第一文件的详细信息。第二设备可以在用户有查看某一文件需求时，根据第一设备的请求向第一设备发送该文件的详细信息。通过这种随看随传的方式，可以避免过多冗余信息的传输，对传输资源的占用。
在一种可能的实现方式中，上述第一文件是图片、视频或者音频。
第六方面，提供一种第一设备，该第一设备包括：存储器，用于存储计算机程序；收发器，用于接收或发送无线电信号；处理器，用于执行所述计算机程序，使得第一设备执行如第一方面任一种可能的实现方式中的方法。
第七方面，提供一种第二设备，该第二设备包括：存储器，用于存储计算机程序；收发器，用于接收或发送无线电信号；处理器，用于执行所述计算机程序，使得第二设备执行如第二方面任一种可能的实现方式中的方法。
第八方面，提供一种通信系统，该通信系统包括如第四方面或第六方面任一种可能的实现方式中第一设备，以及如第五方面或第七方面任一种可能的实现方式中第二设备。该通信系统用于实现如第三方面任一种可能的实现方式中的方法。
第九方面，提供一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序代码，该计算机程序代码被处理器执行时，使得处理器实现如第一方面或第二方面任一种可能的实现方式中的方法。
第十方面，提供一种芯片系统，该芯片系统包括处理器、存储器，存储器中存储有计算机程序代码；所述计算机程序代码被所述处理器执行时，使得处理器实现如第一方面或第二方面任一种可能的实现方式中的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第十一方面，提供一种计算机程序产品，该计算机程序产品包括计算机指令。当该计算机指令在计算机上运行时，使得计算机实现如第一方面或第二方面任一种可能的实现方式中的方法。
附图说明
图1为一种常规的跨设备文件显示方法示意图；
图2为本申请实施例提供的一种终端设备的硬件结构示意图；
图3为本申请实施例提供的一种终端设备的软件结构示意图；
图4为本申请实施例提供的一种资源管理器界面示意图；
图5为本申请实施例提供的一种资源管理器中手机资源界面示意图；
图6为本申请实施例提供的一种资源管理器中手机图片缩略图界面示意图；
图7为本申请实施例提供的一种在资源管理器中展示文件缩略图的过程示意图；
图8为本申请实施例提供的两种在资源管理器中展示文件缩略图的流程图；
图9为本申请实施例提供的另一种在资源管理器中展示文件缩略图的过程示意图；
图10为本申请实施例提供的一种在资源管理器中展示文件缩略图的流程图；
图11为本申请实施例提供的另一种在资源管理器中展示文件缩略图的流程图；
图12为本申请实施例提供的一种第二设备对获取文件缩略图的请求的响应流程图；
图13为本申请实施例提供的一种第一设备为用户提供查看第一设备中文件详细信息的流程图；
图14为本申请实施例提供的一种第二设备对获取文件详细信息的请求的响应流程图；
图15为本申请实施例提供的一种自定义缩略图提供插件定义过程示意图；
图16为本申请实施例提供的一种跨设备文件显示方法交互图；
图17为本申请实施例提供的一种终端设备的结构框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请实施例的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本申请实施例的描述中，“多个”是指两个或多于两个。
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征。在本实施例的描述中，除非另有说明，“多个”的含义是两个或两个以上。
本申请实施例提供一种跨设备文件显示方法，该方法用于一个设备(如第一设备)跨设备向用户展示另一个设备(如第二设备)中文件的过程中。示例性的，在本申请实施例中，第一设备可以跨设备向用户展示第二设备中多个文件的缩略图，以供用户从中选择文件进行查看。
其中，在本申请实施例中，终端设备(包括第一设备和第二设备)包括显示屏，以进行跨设备文件显示。作为一种示例，终端设备(包括第一设备和第二设备)可以包括但不限定于个人计算机(personal computer，PC)、智能手机、上网本、平板电脑、智能手表、智能手环、电话手表、智能相机、掌上电脑、个人数字助理(personal digital assistant，PDA)、便携式多媒体播放器(portable multimedia player，PMP)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、电视机、投影设备或人机交互场景中的体感游戏机等。本申请对终端设备(包括第一设备和第二设备)的具体功能和结构不做限定。
请参考图2，图2以智能手机为例，示出了本申请实施例提供的一种终端设备(包括第一设备和第二设备)的硬件结构示意图。如图2所示，终端设备可以包括处理器210，存储器(包括外部存储器接口220和内部存储器221)，通用串行总线(universal serial bus，USB)接口230，充电管理模块240，电源管理模块241，电池242，天线1，天线2，移动通信模块250，无线通信模块260，音频模块270，扬声器270A，受话器270B，麦克风270C，耳机接口270D，传感器模块280，按键290，马达291，指示器292，摄像头293，显示屏294，以及用户标识模块(subscriber identification module，SIM)卡接口295等。其中传感器模块280可以包括压力传感器，陀螺仪传感器，气 压传感器，磁传感器，加速度传感器，距离传感器，接近光传感器，指纹传感器，温度传感器，触摸传感器，环境光传感器，骨传导传感器等。
可以理解的是，本发明实施例示意的结构并不构成对终端设备的具体限定。在本申请另一些实施例中，终端设备可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器210可以包括一个或多个处理单元。例如：处理器210可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，飞行控制器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
处理器210中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器210中的存储器为高速缓冲存储器。该存储器可以保存处理器210刚用过或循环使用的指令或数据。如果处理器210需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器210的等待时间，因而提高了系统的效率。
在一些实施例中，处理器210可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
充电管理模块240用于从充电器接收充电输入。电源管理模块241用于连接电池242，充电管理模块240与处理器210。电源管理模块241接收电池242和/或充电管理模块240的输入，为处理器210，内部存储器221，显示屏294，摄像头293，和无线通信模块260等供电。
终端设备的无线通信功能可以通过天线1，天线2，移动通信模块250，无线通信模块260，调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。终端设备中的每个天线可用于覆盖单个或多个通信频段。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块250可以提供应用在终端设备上的包括2G/3G/4G/5G/6G等无线通信的解决方案。移动通信模块250可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块250可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块250还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块250的至少部分功能模块可以被设置于 处理器210中。在一些实施例中，移动通信模块250的至少部分功能模块可以与处理器210的至少部分模块被设置在同一个器件中。
在本申请实施例中，终端设备可以通过天线1、天线2和移动通信模块250实现发射或接收第一请求消息、第二请求消息，和/或与本申请实施例相关的无线电信号。
调制解调处理器可以包括调制器和解调器。其中，调制器用于将待发送的低频基带信号调制成中高频信号。解调器用于将接收的电磁波信号解调为低频基带信号。随后解调器将解调得到的低频基带信号传送至基带处理器处理。低频基带信号经基带处理器处理后，被传递给应用处理器。应用处理器通过音频装置(不限于扬声器270A、受话器270B等)输出声音信号，或通过显示屏294显示图像或视频。在一些实施例中，调制解调处理器可以是独立的器件。在另一些实施例中，调制解调处理器可以独立于处理器210，与移动通信模块250或其他功能模块设置在同一个器件中。
无线通信模块260可以提供应用在终端设备上的包括无线局域网(wireless local area networks，WLAN)(如WiFi网络)，蓝牙(Bluetooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，调频(frequency modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块260可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块260经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器210。无线通信模块260还可以从处理器210接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
在一些实施例中，终端设备的天线1和移动通信模块250耦合，天线2和无线通信模块260耦合，使得终端设备可以通过无线通信技术与网络以及其他设备通信。所述无线通信技术可以包括全球移动通讯系统(global system for mobile communications，GSM)，通用分组无线服务(general packet radio service，GPRS)，码分多址接入(code division multiple access，CDMA)，宽带码分多址(wideband code division multiple access，WCDMA)，时分码分多址(time-division code division multiple access，TD-SCDMA)，长期演进(long term evolution，LTE)，新无线(new radio，NR)，BT，GNSS，WLAN，NFC，FM，和/或IR技术等。所述GNSS可以包括全球卫星定位系统(global positioning system，GPS)，全球导航卫星系统(global navigation satellite system，GLONASS)，北斗卫星导航系统(beidou navigation satellite system，BDS)，准天顶卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)等。
终端设备通过GPU，显示屏294，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏294和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器210可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏294用于显示图像，视频等。显示屏294包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)，有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)，柔性发光二极管(flex light-emitting diode， FLED)，Miniled，MicroLed，Micro-oLed，量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，终端设备可以包括1个或N个显示屏294，N为大于1的正整数。
在本申请实施例中，终端设备可以通过GPU进行资源管理器界面渲染，通过显示屏294进行资源管理器界面显示等。
终端设备可以通过ISP，摄像头293，视频编解码器，GPU，显示屏294以及应用处理器等实现拍摄功能。
外部存储器接口220可以用于连接外部存储卡，例如微型(micro)存储(storage card，SD)卡，实现扩展终端设备的存储能力。外部存储卡通过外部存储器接口220与处理器210通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
在本申请实施例中，跨设备显示的文件(如图片、视频、音频等)可以存储在终端设备的外部存储卡中。
内部存储器221可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。内部存储器221可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储终端设备使用过程中所创建的数据(比如音频数据，电话本等)等。此外，内部存储器221可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。处理器210通过运行存储在内部存储器221的指令，和/或存储在设置于处理器中的存储器的指令，执行终端设备的各种功能应用以及数据处理。
在本申请实施例中，内部存储器221可以用于缓存其他设备中文件对应的文件缩略图。
终端设备可以通过音频模块270，扬声器270A，受话器270B，麦克风270C以及应用处理器等实现音频功能。例如音乐播放，录音等。关于音频模块270，扬声器270A，受话器270B和麦克风270C的具体工作原理和作用，可以参考常规技术中的介绍。
按键290包括开机键，音量键等。按键290可以是机械按键。也可以是触摸式按键。终端设备可以接收按键输入，产生与终端设备的用户设置以及功能控制有关的键信号输入。
需要说明的是，图2所示终端设备包括的硬件模块只是示例性地描述，并不对终端设备的具体结构做出限定。例如，若终端设备是PC，那么终端设备还可以包括键盘、鼠标等部件。
在本申请中，终端设备的操作系统(operating system，OS)可以包括但不限于
Figure PCTCN2022123906-appb-000001
Figure PCTCN2022123906-appb-000002
Figure PCTCN2022123906-appb-000003
OS等操作系统。
以包括分层架构的
Figure PCTCN2022123906-appb-000004
系统的终端设备为例，如图3所示，终端设备的软件可以分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口通信。如图3所示，终端设备的软件结构从上至下可以分为三层：应用程序层(简称应用层)，应用程序框架层(简称框架层)，系统库，安卓运行时和内核层(也称为驱动层)。
其中，应用程序层可以包括一系列应用程序包，例如相机，图库，日历，通话，地图，导航，蓝牙，音乐，视频，短信息，管家应用(如
Figure PCTCN2022123906-appb-000005
电脑管家)等应用程序。为方便描述，以下将应用程序简称为应用。在本申请实施例中，管家应用可以支持终端设备实现设备之间的配对、认证以及建立设备之间的通信连接等。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。如图3所示，应用程序框架层可以包括窗口管理服务器(window manager service，WMS)，活动管理服务器(activity manager service，AMS)和输入事件管理服务器(input manager service，IMS)。在一些实施例中，应用程序框架层还可以包括内容提供器，视图系统，电话管理器，资源管理器，通知管理器等(图3中未示出)。
系统库和安卓运行时包含框架层所需要调用的功能函数，
Figure PCTCN2022123906-appb-000006
的核心库，以及
Figure PCTCN2022123906-appb-000007
虚拟机。系统库可以包括多个功能模块。例如：浏览器内核，三维(3 dimensional，3D)图形，字体库等。
系统库可以包括多个功能模块。例如：表面管理器(surface manager)，媒体库(Media Libraries)，三维图形处理库(例如：OpenGL ES)，2D图形引擎(例如：SGL)等。
内核层是硬件和软件之间的层。内核层可以包含显示驱动，输入/输出设备驱动(例如，键盘、触摸屏、耳机、扬声器、麦克风等)，设备节点，摄像头驱动，音频驱动以及传感器驱动等。用户通过输入设备进行输入操作，内核层可以根据输入操作产生相应的原始输入事件，并存储在设备节点中。输入/输出设备驱动可以检测到用户的输入事件。例如，麦克风可以检测到用户发出的语音，触摸屏可以检测到用户的触控操作，键盘可以检测到用户输入的信息或者操作(如选择操作)等。
需要说明的是，图3仅以分层架构的
Figure PCTCN2022123906-appb-000008
系统为例，介绍一种终端设备的软件结构。本申请不限定终端设备软件系统的具体架构，关于其他架构的软件系统的具体介绍，可以参考常规技术。
为了在跨设备文件显示时，不依赖于第三方应用，本申请实施例提供了一种基于终端设备原生软件和硬件，实现跨设备文件显示的方法。
其中，在本申请实施例中，跨设备展示的文件类型可以包括但不限定于图片、视频、音频、办公文档(如word文档、excel文档、txt文档等)、通信录、压缩包等。
示例性，在本申请实施例中，第一设备可以基于原生资源管理器，使用虚拟磁盘技术，将第二设备作为一个独立盘符挂载到第一设备的资源管理器中，以方便用户通过第一设备访问第二设备中的文件。可以理解，该方法还可以极大降低跨设备文件访问的壁垒，实现多设备之间的进一步融合，让用户能够便捷、简单地进行跨设备文件访问和查看。
其中，资源管理器是终端设备操作系统提供的资源管理工具。资源管理器可以以树形文件系统结构展示终端设备中的所有资源，因此可以为用户提供更加清楚、直观地文件访问和查看体验。例如，终端设备中的文件可以根据文件类型，在对应文件夹的子路径中，以缩略图的形式展示。因此，基于资源管理器界面实现跨设备文件显示，可以为用户提供非常便捷的跨设备文件访问体验。
例如，资源管理器可以如
Figure PCTCN2022123906-appb-000009
资源管理器(Explorer)等，本申请不限定。请参考图4，图4以Windows
Figure PCTCN2022123906-appb-000010
为例，示出了一种第二设备(如手机)以虚拟盘符挂载到第一设备(如电脑)的资源管理器中的界面示意图。其中，电脑(即第一设备)与手机(即第二设备)之间建立有通信连接，该通信连接如蓝牙连接、WiFi直连，接入同一无线局域网等，本申请不限定。
基于图4所示资源管理器界面，用户可以通过打开“我的手机”虚拟盘，对手机(即第二设备)中的文件进行访问和查看等操作。
作为一种示例，电脑(即第一设备)响应于接收到用户在图4所示资源管理器界面上打开“我的手机”虚拟盘的操作(如双击，右键→打开等操作)，电脑(即第一设备)显示图5所示手机资源界面。如图5所示，手机资源界面上显示有手机(即第二设备)中多个类型文件对应的文件夹，如图5所示图片、视频、音频、办公文档、通信录和压缩包。
进一步的，电脑(即第一设备)响应于接收到用户在图5所示手机资源界面上打开图片文件夹的操作(如双击，右键→打开等操作)，电脑(即第一设备)显示图6所示手机图片缩略图界面。基于图6所示手机图片缩略图界面，用户可以快速查看手机侧图片。
作为一种可能的实现方式，如图7所示，第一设备在资源管理器中展示的文件缩略图是第一设备根据从第二设备获取的原文件生成的。
作为一种示例，如图8中的(a)所示，在接收到用户在资源管理器界面上发起的文件缩略图展示请求后，第一设备确定上述请求对应的路径所对应的设备。若上述请求对应的路径所对应的设备是第二设备，第一设备从第二设备获取原文件。然后，第一设备根据从第二设备获取的原文件生成文件缩略图，并进一步在上述请求对应路径的资源管理器界面上展示文件缩略图。
以在第一设备的Windows
Figure PCTCN2022123906-appb-000011
中展示第二设备的图片缩略图为例，作为一种示例，在接收到用户在Windows
Figure PCTCN2022123906-appb-000012
界面上发起的图片缩略图展示请求(如用户在图5所示手机资源界面上打开图片文件夹的操作)后，若上述请求对应的路径所对应的设备是第二设备，第一设备从第二设备获取原图片，然后根据从第一设备获取的原图片生成图片缩略图，并进一步展示在上述请求对应路径的Windows
Figure PCTCN2022123906-appb-000013
界面上；若上述请求对应的路径所对应的设备是第一设备，第一设备根据上述请求对应路径下的原图片生成缩略图，并进一步展示在上述请求对应路径的Windows
Figure PCTCN2022123906-appb-000014
界面上。以图5所示手机资源界面为例，在接收到用户在图5所示手机资源界面上打开图片文件夹的操作时，电脑(即第一设备)从手机(即第二设备)获取手机中的完整图片，加载到电脑(即第一设备)中，然后生成缩略图，并以图6所示界面向用户展示。
可以理解，在一些实施例中，若第一设备之前展示过第二设备的文件缩略图，则第一设备可以将该文件缩略图存储在缩略图缓存(即存储单元，如thumbcache_*.db)中，方便下次展示。因此，作为另一种示例，如图8中的(b)所示，在接收到用户在资源管理器界面上发起的文件缩略图展示请求后，第一设备先在缩略图缓存(如thumbcache_*.db)中查找文件缩略图。若找到，则在上述请求对应路径的资源管理器 (如Windows
Figure PCTCN2022123906-appb-000015
)界面上展示；若未找到，第一设备确定请求对应的路径所对应的设备。若上述请求对应的路径所对应的设备是第二设备，第一设备从第二设备获取原文件，然后根据从第二设备获取的原文件生成文件缩略图，并进一步在上述请求对应路径的资源管理器界面上展示文件缩略图。
以在第一设备的Windows
Figure PCTCN2022123906-appb-000016
中展示第二设备的图片缩略图为例，在接收到用户在Windows
Figure PCTCN2022123906-appb-000017
界面上发起的图片缩略图展示请求(如用户在图5所示手机资源界面上打开图片文件夹的操作)后，第一设备可以先在缩略图缓存(如thumbcache_*.db)中查找图片缩略图。若找到，则在上述请求对应路径的Windows
Figure PCTCN2022123906-appb-000018
界面上展示；若未找到，上述请求对应的路径所对应的设备是第二设备，第一设备从第二设备获取原图片，然后根据从第一设备获取的原图片生成图片缩略图，并进一步展示在上述请求对应路径的Windows
Figure PCTCN2022123906-appb-000019
界面上；若上述请求对应的路径所对应的设备是第一设备，第一设备根据上述请求对应路径下的原图片生成缩略图，并进一步展示在上述请求对应路径的Windows
Figure PCTCN2022123906-appb-000020
界面上。
但是，基于上述方法，第一设备从第二设备获取的是原文件，因此文件数据量较大。大量的文件数据在从第二设备传输至第一设备时，会占用较多的通信资源，也会耗费大量的时间，造成显示界面卡顿。另外，通过该方法能够查看的文件类型比较受限，例如通常仅能查看常见类型的文件，如图片、视频、音频等。
为解决上述问题，本申请实施例提供了一种更加高效、快捷的跨设备文件显示方法，如图9所示，该方法中，第一设备可以直接从第二设备获取第二设备中存储的文件缩略图(如第一文件缩略图)并在资源管理器界面上展示。基于此可以解决由于第一设备从第二设备获取原文件导致的占用通信资源，耗时多的问题，极大优化了用户的使用体验。
作为一种可能的实现方式，如图10所示，在接收到用户在资源管理器界面上发起的文件缩略图展示请求(即S1001)后，第一设备执行以下S1002-S1005。其中，文件缩略图展示请求包括但不限于以下操作：用户在第一设备上对第二设备任意路径下文件夹虚拟图标的单击操作、双击操作、长按后选择打开选项的操作、鼠标右键后选择打开选项的操作等，本申请不限定具体操作类型。
S1002：第一设备确定上述文件缩略图展示请求对应的路径所对应的设备。
示例性的，假设电脑(即第一设备)接收到用户在图5所示手机资源界面上打开图片文件夹的操作，即接收到用户在资源管理器界面上发起的文件缩略图展示请求的操作，则上述请求对应的路径(即路径：我的手机:\图片)所对应的设备是我的手机(即第二设备)。
假设电脑(即第一设备)接收到用户在图4所示资源管理器界面上打开D盘的操作，即接收到用户在资源管理器界面上发起的文件缩略图展示请求的操作，则上述请求对应的路径(即路径：D:\)所对应的设备是电脑(即第一设备)。
以资源管理器是Windows
Figure PCTCN2022123906-appb-000021
为例，第一设备可以通过调用自定义缩略图提供插件(如ThumbnailProvider.dll)，确定上述请求对应的路径所对应的设备。示例性的，第一设备可以调用ThumbnailProvider.dll，通过自定义Initialize()函数确定上述文件缩略图展示请求对应的路径。
若上述请求对应的路径所对应的设备是第二设备，第一设备执行以下S1003-S1005；若上述请求对应的路径所对应的设备是第一设备，第一设备执行以下S1004-S1005。
S1003：第一设备从第二设备获取文件缩略图(如第一文件缩略图)。
其中，第二设备中存储有第一文件缩略图。
以资源管理器是Windows
Figure PCTCN2022123906-appb-000022
为例，第一设备可以通过调用自定义缩略图提供插件(如ThumbnailProvider.dll)，从第二设备获取文件缩略图。示例性的，第一设备可以调用ThumbnailProvider.dll，通过自定义GetThumbnail()函数从第二设备获取文件缩略图。
作为一种可能的实现方式，第一设备可以通过已建立的与第二设备之间的通信连接(如蓝牙连接，WiFi直连，接入同一无线局域网等)向第二设备发送请求消息，如第一请求消息，该第一请求消息携带有上述文件缩略图展示请求对应的路径，以向第二设备请求相应路径下的文件缩略图。示例性的，第一设备与第二设备之间的通信连接可以基于碰一碰连接、靠近连接、设备发现连接等技术建立，本申请不限定。
作为一种可能的实现方式，如图12所示，第二设备在接收到来自第一设备的用于获取文件缩略图的第一请求消息(如图12中的S1201所示)之后，可以遍历第二设备对应路径下文件的缩略图信息(如图12中的S1202所示)。例如，第二设备根据来自第一设备的第一请求消息中携带的上述请求对应的路径，遍历对应路径下文件的缩略图信息。进一步的，如图12中的S1203所示，第二设备将上述文件缩略图发送至第一设备，用于第一设备将来自第二设备的上述文件缩略图关联到上述文件缩略图展示请求对应的路径下。
进一步的，在一些实施例中，如图12所示，第二设备还可以记录上述文件缩略图与具体文件的映射关系(如图12中的S1202所示)，以便在用户通过第一设备查看文件缩略图中任意文件的详细信息时，及时向第一设备发送对应文件的详细信息。进一步的，第二设备还可以将上述文件缩略图与具体文件的映射关系发送给第二设备。
进一步的，在一些实施例中，如图12所示，第二设备还可以在第二设备上的文件发生更新(例如删除文件、增加文件、修改文件等)时，重新执行上述S1202，及时更新文件缩略图，以及文件缩略图与具体文件的映射关系。
S1004：第一设备根据上述文件缩略图展示请求对应路径下的原文件生成文件缩略图(如第一文件缩略图)。
以资源管理器是Windows
Figure PCTCN2022123906-appb-000023
为例，第一设备可以通过调用原文件处理插件，根据上述请求对应路径下的原文件生成文件缩略图。以文件类型是图片为例，原文件处理插件可以是PhotoMetadataHandler.dll。关于PhotoMetadataHandler.dll的具体介绍，可以参考常规技术中的解释和说明，本申请实施例不做赘述。
S1005：第一设备在上述文件缩略图展示请求对应路径的资源管理器界面上展示文件缩略图(即第一文件缩略图)。
以在第一设备的Windows
Figure PCTCN2022123906-appb-000024
中展示第二设备的图片缩略图为例，在接收到用户在Windows
Figure PCTCN2022123906-appb-000025
界面上发起的图片缩略图展示请求(如用户在图5所示手机资源界面上打开图片文件夹的操作)后，第一设备调用自定义缩略图提供插件(如ThumbnailProvider.dll)执行以下步骤：确定上述图片缩略图展示请求对应的路径所对 应的设备。若上述图片缩略图展示请求对应的路径所对应的设备是第二设备，从第二设备获取图片缩略图并在Windows
Figure PCTCN2022123906-appb-000026
界面上展示；若上述图片缩略图展示请求对应的路径所对应的设备是第一设备，调用原文件处理插件(如PhotoMetadataHandler.dll)根据第一设备中对应路径下的原图片生成图片缩略图并在上述图片缩略图展示请求对应路径的Windows
Figure PCTCN2022123906-appb-000027
界面上展示(如图6所示)。
以自定义缩略图提供插件是ThumbnailProvider.dll为例，作为一种示例，ThumbnailProvider.dll可以通过自定义GetThumbnail()函数在上述文件缩略图展示请求对应路径的资源管理器界面上展示文件缩略图。
需要说明的是，图10是以第一设备在接收到来自用户的文件缩略图展示请求之后，从第二设备获取文件缩略图作为示例，本申请实施例对于第一设备从第二设备获取文件缩略图的具体时机不做限定。
作为一种示例，为了提供更加快速、便捷的文件缩略图展示，第一设备还可以预先缓存第二设备中的文件缩略图(如第二文件缩略图)，例如预先缓存第二设备中全部文件的文件缩略图，或者预先缓存第二设备中预设类型文件的文件缩略图，或者预先缓存第二设备中预设路径下的文件缩略图，本申请不限定。
例如，第一设备可以在与第二设备建立通信连接时，从第二设备获取第二设备中所有文件、预设类型或预设路径下文件的缩略图，并缓存在缩略图缓存(即存储单元，如thumbcache_*.db)中，方便在接收到来自用户的文件缩略图展示请求时，根据文件缩略图展示请求对应的路径查找相应文件缩略图以进行展示。
示例性的，第一设备还可以在与第二设备建立通信连接时，从第二设备获取文件的缩略图与路径的对应关系，以便在接收到来自用户的文件缩略图展示请求时，根据文件缩略图展示请求对应的路径和文件的缩略图与路径的对应关系，在缩略图缓存(如thumbcache_*.db)中查找相应文件缩略图以进行展示。
基于上述思路，作为另一种可能的实现方式，如图11所示，第一设备在缩略图缓存(如thumbcache_*.db)中预先缓存第二设备中多个文件的文件缩略图。在接收到用户在资源管理器界面上发起的文件缩略图展示请求(即S1001)后，第一设备先在缩略图缓存(如thumbcache_*.db)中查找文件缩略图展示请求对应路径下的文件缩略图(即S1101)。若找到，执行S1005，在上述文件缩略图展示请求对应路径的资源管理器(如Windows
Figure PCTCN2022123906-appb-000028
)界面上展示；若未找到，执行S1002-S1005。关于S1002-S1005的具体过程，可以参考上文中对图10的具体介绍，这里不做赘述。
进一步的，基于第一设备图10或图11所示S1005展示的文件缩略图，用户可以通过第一设备实现对第二设备侧文件的快速浏览，或者用户可以进一步查看任意文件的详细信息。
以图11所示在资源管理器中展示文件缩略图的流程图为例，作为一种示例，如图13所示，第一设备在接收到用户在文件缩略图中对第一文件的文件打开请求(例如用户在在文件缩略图中双击第一文件对应的图标的操作)后，执行以下步骤S1301-S1302。其中，第一文件是文件缩略图中任意图标对应的文件。
S1301：第一设备从第二设备获取第一文件的详细信息。
作为一种可能的实现方式，第一设备可以通过已建立的与第二设备之间的通信连 接向第二设备发送请求消息，如第二请求消息，该第二请求消息携带有缩略图标的标识，以向第二设备请求相应标识对应的文件的详细信息。
作为一种可能的实现方式，如图14所示，第二设备在接收到来自第一设备的用于获取第一文件的详细信息的第二请求消息(如图14中的S1401所示)之后，可以根据第二请求消息中携带的缩略图标的标识和第二设备记录的上述映射关系(即文件缩略图与具体文件的映射关系)确定上述标识对应的第一文件(如图14中的S1402所示)。进一步的，如图14中的S1403所示，第二设备向第一设备发送第一文件的详细信息。
示例性的，若第一文件是图片，则第一文件的详细信息即该图片的原图片。若第一文件是视频，则第一文件的详细信息即该视频的原视频。
S1302：第一设备在上述文件打开请求对应路径的资源管理器界面上展示第一文件的详细信息。
示例性的，若第一文件是图片，则第一设备在上述文件打开请求对应路径的资源管理器界面上展示该图片的原图。若第一文件是视频，则第一设备在上述文件打开请求对应路径的资源管理器界面上播放该原视频。
可以理解，常规的操作系统安装程序无法实现本申请实施例提供的方法，为了解决该问题。在本申请实施例中，可以基于组件对象模型(如
Figure PCTCN2022123906-appb-000029
的基于组件对象模型(component object model，COM))自定义缩略图提供插件(如ThumbnailProvider.dll)。以下对本申请实施例提供的自定义缩略图提供插件作具体介绍。
其中，COM用于规定软件组件(software component)的接口(interface)的标准。其中，接口可以看成是包含一组待实现方法的类。在终端设备中，多个应用程序并不是一个完整的可执行文件，而是被分割成一些相对独立的插件。因此，COM通常以插件的形式存在于终端设备中。其中，插件如动态链接库(dynamic-link library，dll)文件。在终端设备执行应用程序时，可以通过调用应用程序相应的插件(如dll文件)来实现。
示例性的，COM接口可以从基接口(base interface)继承。其中，基接口(base interface)如IUnknow接口。IUnknow接口有三个方法函数：QueryInterface()函数、AddRef()函数和Release()函数。其中，QueryInterface()函数用于在获取某个COM的一个接口指针后，查询该COM的其它接口指针。AddRef()函数用于增加引用计数。Release()函数用于减少引用计数。
示例性的，IUnknow接口可以如下定义：
Figure PCTCN2022123906-appb-000030
本申请实施例中，如图15所示，用于实现文件缩略图展示的自定义缩略图提供插件(如ThumbnailProvider.dll)继承了常规的基接口(如IUnknow接口)、常规的初 始化接口1(如IInitializeWithFile接口1)和常规的缩略图接口1(如IThumbnailProvider接口1)，并对常规的初始化接口1和常规的缩略图接口1做了改进。
其中，本申请实施例中，自定义缩略图提供插件中不仅定义了方法函数QueryInterface()函数、AddRef()函数和Release()函数，还定义了方法函数Initialize2()函数和GetThumbnail2()函数。其中，相比于Initialize1()函数，Initialize2()函数可以用于确定文件缩略图展示请求对应的路径。相比于GetThumbnail1()函数，GetThumbnail2()函数可以用于对Initialize2()函数确定的路径对应的设备进行判断，以及从相应设备获取文件缩略图并在资源管理器界面上展示。
作为一种示例，在本申请实施例中，第一设备可以通过调用DllMain文件(如dllmain.cpp)以加载自定义缩略图提供插件(如ThumbnailProvider.dll)。示例性的，DllMain文件可以包括但不限于以下中的一种或多种入口点函数：DllMain()函数，DllGetClassObject()函数，DllCanUnloadNow()函数，DllRegisterServer()函数，DllUnregisterServer()函数。
其中，DllGetClassObject()函数和DllCanUnloadNow()函数是自动注册和注销函数。DllMain()函数是自定义缩略图提供插件(如Thumbna ilProvider.dll)的入口函数。DllGetClassObject()函数用于创建COM对象。在进行COM对象创建时，首先要加载包含这个COM对象的库，后通过DllGetClassObject()函数取得COM接口指针。DllCanUnloadNow()函数用于判断是否释放DLL。例如，可以通过DllGetClassObject()函数加载COM对象的客户模块，然后调用DllCanUnloadNow()函数来保证DLL被安全地卸载和释放。DllRegisterServer()函数用于在操作系统缩略图生成的注册表中注册DLL。DllUnregisterServer()函数用于在操作系统缩略图生成的注册表中反注册DLL。关于插件、COM接口、COM接口中定义的方法函数的具体介绍，可以参考常规技术，本申请不做赘述。
作为一种示例，在本申请实施例中，第一设备可以将自定义缩略图提供插件(如ThumbnailProvider.dll)保存在操作系统对应的文件夹下，例如C:\Windows\System32路径下。
作为一种实现方式，为了在接收到文件缩略图展示请求后，成功调用自定义缩略图提供插件(如ThumbnailProvider.dll)实现跨设备文件缩略图展示，在本申请实施例中，第一设备可以将自定义缩略图提供插件(如ThumbnailProvider.dll)的全局唯一标识符(globally unique identifier，GUID)添加在插件GUID对应的项(如HKCR\CLSID路径下的对应项)，并修改操作系统缩略图生成的注册表对应项，如HKCR\SystemFileAssiciations\image\shellex路径下缩略图提供插件的GUID。
其中，GUID(也称通用唯一标识码(universally unique identifier，UUID))是用于标识信息的长度为128比特(bit)的数字标识符。GUID的格式为“xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”"，其中每个x是0-9或a-f范围内的一个16进制数。例如：550e8400-e29b-41d
4-a716-446655440000。
为方便理解，以下以图11所示在资源管理器中展示文件缩略图的流程为例，结合 具体场景，对本申请实施例提供的一种跨设备文件显示的具体交互过程作具体介绍。其中，假设第一设备是PC，第二设备是智能手机，第一设备与第二设备通过碰一碰、靠近连接等发起通信连接建立，如图16所示，本申请实施例提供的一种跨设备文件显示方法包括S1601-S1608：
S1601：PC和/或智能手机接收到建立PC和智能手机之间的通信连接的请求。
示例性，若PC或智能手机由于与对方设备靠近检测到对方设备，或者通过设备发现技术发现对方，则确定接收到建立PC和智能手机之间的通信连接的请求。
S1602：PC通过PC管家应用建立与智能手机之间的传输通道(即建立通信连接，如分布式文件通道)。
其中，通信连接如蓝牙连接、WiFi直连、接入同一无线局域网等；传输通道如蓝牙传输通道、WiFi直连通道等，本申请不限定。
S1603：响应于打开资源管理器的操作，PC在资源管理器界面上显示智能手机的虚拟盘符。
示例性的，响应于用户双击资源管理器应用图标，或右键源管理器应用图标→打开的操作，PC显示资源管理器界面(如图4所示界面)。其中，资源管理器界面上包括智能手机的虚拟盘符(如图4所示“我的手机”虚拟盘符)。
S1604：智能手机通过上述传输通道向PC发送多个文件对应的文件缩略图，以及文件缩略图与路径的对应关系。
示例性的，智能手机可以遍历智能手机的缩略图信息以查找文件缩略图，并记录文件缩略图与路径的对应关系。
S1605：PC在缓存中存储上述多个文件对应的文件缩略图，以及文件缩略图与路径的对应关系。
示例性的，PC可以在缩略图缓存(如thumbcache_*.db)中存储上述多个文件对应的文件缩略图，以及文件缩略图与路径的对应关系。
S1606：响应于接收到文件缩略图展示请求，PC在缓存中查找文件缩略图展示请求对应路径下的文件缩略图。
其中，文件缩略图展示请求包括但不限于以下操作：用户对资源管理器界面上智能手机虚拟盘符的单击操作、双击操作、长按后选择打开选项的操作、鼠标右键后选择打开选项的操作等，本申请不限定具体操作类型。
示例性的，文件缩略图展示请求如在图5所示手机资源界面上打开图片文件夹的操作。
若PC在缓存中找到文件缩略图展示请求对应路径下的文件缩略图，PC执行S1608；若PC在缓存中未找到文件缩略图展示请求对应路径下的文件缩略图，PC执行S1607和S1608。
S1607：PC调用自定义缩略图提供插件(如ThumbnailProvider.dll)，从智能手机获取文件缩略图展示请求对应路径下的文件缩略图。
例如，PC调用自定义缩略图提供插件ThumbnailProvider.dll中的自定义GetThumbnail()函数从智能手机获取文件缩略图展示请求对应路径下的文件缩略图。
示例性的，PC可以通过已建立的与智能手机之间的传输通道向智能手机发送第一 请求消息，该第一请求消息携带有上述文件缩略图展示请求对应的路径，以向智能手机备请求相应路径下的文件缩略图。
S1608：PC在上述文件缩略图展示请求对应路径的资源管理器界面上展示文件缩略图。
进一步的，如图16所示，若PC接收到对第一文件的文件打开请求9)，PC执行以下S1609-S1610：
S1609：响应于接收到对第一文件的文件打开请求，PC从智能手机获取第一文件的详细信息。
示例性的，PC可以通过已建立的与智能手机之间的传输通道向智能手机发送第二请求消息，该第二请求消息携带有缩略图标的标识，以向智能手机请求相应标识对应的文件的详细信息。
S1610：PC在上述文件打开请求对应路径的资源管理器界面上展示第一文件的详细信息。
示例性的，若第一文件是图片，则第一设备在上述文件打开请求对应路径的资源管理器界面上展示该图片的原图。若第一文件是视频，则第一设备在上述文件打开请求对应路径的资源管理器界面上播放该原视频。
进一步的，手机还可以在文件发生更新时，实时向PC进行信息更新。即，如图16所示，手机还可以执行以下S1611-S1612：
S1611：手机检测到文件发生更新。
例如，文件发生更新如删除文件、增加文件、修改文件等，本申请实施例不限定。
S1612：手机向PC更新文件缩略图，以及文件缩略图与路径的对应关系。
基于此，在PC下一次接收到用户的文件缩略图展示请求时，可以基于更新后的文件缩略图，文件缩略图与路径的对应关系进行文件缩略图展示流程。或者，在PC下一次接收到用户的文件打开请求时，可以基于更新后的文件缩略图与文件的映射关系进行文件详细信息展示。
需要说明的是，图16仅以S1611-S1612在S1606-S1610之后执行作为示例，本申请不限定手机向PC进行信息更新的时机。例如，S1611-S1612还可以在S1606-S1610之前执行，或者在执行S1606-S1610的过程中执行，具体视实际情况而定。
基于本申请实施例提供的跨设备文件显示方法，终端设备无需借助第三方定制化应用，便可以基于原生软件和硬件，通过修改操作系统安装程序相关插件和接口，改变操作系统进行跨设备文件缩略图显示时的逻辑，实现在终端设备侧直接获取并跨设备显示文件缩略图。通过该方法，可以解决由于终端设备从其他设备获取原文件导致的占用通信资源，耗时多导致的显示界面卡顿问题，极大优化了用户的使用体验。
另外，本申请实施例提供的跨设备文件显示方法，可以基于原生资源管理器，使用虚拟磁盘技术，将一个设备(如第二设备)作为一个独立盘符挂载到另一个设备(如第一设备)的资源管理器中。基于此，用户可以便捷、简单地进行跨设备文件访问和查看。并且，通过该方法能够查看的文件类型相比于常规方法更加全面。
应理解，本申请实施例的各个方案可以进行合理的组合使用，并且实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
还应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
可以理解的是，终端设备(包括第一设备和第二设备)为了实现上述任一个实施例的功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以对终端设备(包括第一设备和第二设备)进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，如图17所示，为本申请实施例提供的一种终端设备的结构框图。如图17所示，该终端设备可以包括输入操作检测单元1710、处理单元1720、收发单元1730、存储单元1740和显示单元1750。
其中，输入操作检测单元1710用于支持终端设备检测用户的文件缩略图展示请求，文件打开请求等与本申请实施例相关的请求操作。示例性的，文件缩略图展示请求可以包括但不限于用户在第一设备上对第二设备任意路径下文件夹虚拟图标的单击操作、双击操作、长按后选择打开选项的操作、鼠标右键后选择打开选项的操作等。文件打开请求可以包括但不限于用户在第一设备上对某一文件虚拟图标的单击操作、双击操作、长按后选择打开选项的操作、鼠标右键后选择打开选项的操作等。存储单元1740用于存储来自第二设备的文件缩略图，和/或与本申请实施例相关的其他信息。处理单元1720用于支持终端设备确定文件缩略图展示请求对应路径所对应的设备，从存储单元1740获取文件缩略图展示请求对应路径下的文件缩略图(如第一文件缩略图)，确定文件打开请求所对应的文件，和/或与本申请实施例相关的其他过程。收发单元1730用于支持终端设备从第二设备获取第二设备上所有文件对应的文件缩略图，文件缩略图展示请求对应路径对应的文件缩略图，文件的详细信息，和/或与本申请实施例相关的其他过程。显示单元1750用于支持终端设备进行文件缩略图展示，文件详细信息展示，和/或与本申请实施例相关的其他界面。
作为一种示例，上述收发单元1730可以包括射频电路。具体的，终端设备可以通过射频电路进行无线信号的接收和发送。通常，射频电路包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频电路还可以通过无线通信和其他设备通信。所述无线通信可以使用任一通信标准或协议，包括但不限于全球移动通讯系统、通用分组无线服务、码分多址、宽带码分多址、长期演进、电子邮件、短消息服务等。
应理解，终端设备中的各个模块可以通过软件和/或硬件形式实现，对此不作具体 限定。换言之，电子设备是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路ASIC、电路、执行一个或多个软件或固件程序的处理器和存储器、集成逻辑电路，和/或其他可以提供上述功能的器件。
在一种可选的方式中，当使用软件实现数据传输时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地实现本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线((digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如软盘、硬盘、磁带)、光介质(例如数字化视频光盘(digital video disk，DVD))、或者半导体介质(例如固态硬盘solid state disk(SSD))等。
结合本申请实施例所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于电子设备中。当然，处理器和存储介质也可以作为分立组件存在于终端设备中。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。

Claims (29)

  1. 一种跨设备文件显示方法，其特征在于，所述方法包括：
    第一设备接收文件缩略图展示请求，所述文件缩略图展示请求用于请求展示第一文件缩略图，所述第一文件缩略图对应所述第二设备上的一个或多个文件；
    所述第一设备从所述第一设备的存储单元或者从所述第二设备获取所述第一文件缩略图，所述第一文件缩略图存储在所述第二设备上；
    所述第一设备在所述文件缩略图展示请求对应路径的界面上展示所述第一文件缩略图。
  2. 根据权利要求1所述的方法，其特征在于，所述文件缩略图展示请求对应路径属于所述第一设备的资源管理器应用，所述第一设备在所述文件缩略图展示请求对应路径的资源管理器界面上展示所述第一文件缩略图。
  3. 根据权利要求2所述的方法，其特征在于，在所述第一设备接收所述文件缩略图展示请求之前，所述方法还包括：
    所述第一设备在与所述第二设备之间建立通信连接之后，在资源管理器应用主界面上显示所述第二设备的虚拟盘符。
  4. 根据权利要求3所述的方法，其特征在于，所述文件缩略图展示请求包括以下操作：用户在所述第一设备上对所述第二设备任意路径下文件夹虚拟图标的单击操作、双击操作、长按后选择打开选项的操作、鼠标右键后选择打开选项的操作。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，在所述第一设备接收所述文件缩略图展示请求之前，所述方法还包括：
    所述第一设备在与所述第二设备之间建立通信连接之后，接收来自所述第二设备的第二文件缩略图，以及所述第二文件缩略图与路径的对应关系；
    所述第一设备将所述第二文件缩略图，以及所述第二文件缩略图与路径的对应关系保存在所述存储单元中；
    其中，所述第二文件缩略图对应所述第二设备上的所有文件，所述第二设备上预设类型的文件，或者所述第二设备上预设路径下的文件。
  6. 根据权利要求5所述的方法，其特征在于，所述第二文件缩略图包括所述第一文件缩略图，则所述第一设备从所述第一设备的存储单元获取所述第一文件缩略图。
  7. 根据权利要求6所述的方法，其特征在于，所述第一设备从所述第一设备的存储单元获取所述第一文件缩略图，包括：
    所述第一设备根据所述文件缩略图展示请求对应的路径，以及所述第二文件缩略图与路径的对应关系，从所述第二文件缩略图中获取所述第一文件缩略图。
  8. 根据权利要求5所述的方法，其特征在于，所述第二文件缩略图不包括所述第一文件缩略图，则所述第一设备从所述第二设备获取所述第一文件缩略图。
  9. 根据权利要求8所述的方法，其特征在于，所述第一设备从所述第二设备获取所述第一文件缩略图，包括：
    所述第一设备调用自定义缩略图提供插件，从所述第二设备获取所述第一文件缩略图；
    其中，所述自定义缩略图提供插件中定义了用于从相应设备获取文件缩略图，并 在文件缩略图展示请求对应路径的界面上展示文件缩略图的插件。
  10. 根据权利要求9所述的方法，其特征在于，所述自定义缩略图提供插件是ThumbnailProvider.dll。
  11. 根据权利要求1-5、8-10中任一项所述的方法，其特征在于，所述第一设备从所述第二设备获取所述第一文件缩略图，包括：
    所述第一设备向所述第二设备发送第一请求消息，所述第一请求消息中携带有所述文件缩略图展示请求对应的路径，所述第一请求消息用于请求相应路径下的文件缩略图；
    所述第一设备接收来自所述第二设备的第一文件缩略图。
  12. 根据权利要求1-11中任一项所述的方法，其特征在于，所述方法还包括：
    响应于接收到用户对第一文件的文件打开请求，所述第一设备向所述第二设备发送第二请求消息，所述第二请求消息中携带有所述第一文件对应的缩略图标的标识，所述第二请求消息用于请求所述第一文件的详细信息，所述第一文件是所述第一文件缩略图中任意图标对应的文件；
    所述第一设备接收来自所述第二设备的所述第一文件的详细信息；
    所述第一设备在所述文件打开请求对应路径的界面上展示所述第一文件的详细信息。
  13. 根据权利要求12所述的方法，其特征在于，所述第一文件是图片、视频或者音频。
  14. 一种跨设备文件显示方法，其特征在于，所述方法包括：
    第一设备与第二设备建立通信连接；
    所述第二设备向所述第一设备发送第二文件缩略图，以及所述第二文件缩略图与路径的对应关系；其中，所述第二文件缩略图对应所述第二设备上的所有文件，所述第二设备上预设类型的文件，或者所述第二设备上预设路径下的文件；
    所述第一设备将所述第二文件缩略图，以及所述第二文件缩略图与路径的对应关系保存在所述存储单元中。
  15. 根据权利要求14所述的方法，其特征在于，所述第二文件缩略图包括第一文件缩略图；所述方法还包括：
    所述第一设备接收文件缩略图展示请求，所述文件缩略图展示请求用于请求展示所述第一文件缩略图；
    所述第一设备从所述第一设备的存储单元获取所述第一文件缩略图；
    所述第一设备在所述文件缩略图展示请求对应路径的界面上展示所述第一文件缩略图。
  16. 根据权利要求15所述的方法，其特征在于，所述第一设备从所述第一设备的存储单元获取所述第一文件缩略图，包括：
    所述第一设备根据所述文件缩略图展示请求对应的路径，以及所述第二文件缩略图与路径的对应关系，从所述第二文件缩略图中获取所述第一文件缩略图。
  17. 根据权利要求14所述的方法，其特征在于，所述第二文件缩略图不包括第一文件缩略图；所述方法还包括：
    所述第一设备接收文件缩略图展示请求，所述文件缩略图展示请求用于请求展示所述第一文件缩略图；
    所述第一设备向所述第二设备发送第一请求消息，所述第一请求消息中携带有所述文件缩略图展示请求对应的路径，所述第一请求消息用于请求相应路径下的文件缩略图；
    所述第二设备获取存储的所述文件缩略图展示请求对应的路径下的文件缩略图；
    所述第二设备向所述第一设备发送所述第一文件缩略图；
    所述第一设备在所述文件缩略图展示请求对应路径的界面上展示所述第一文件缩略图。
  18. 根据权利要求17所述的方法，其特征在于，所述第一设备从所述第二设备获取所述第一文件缩略图，包括：
    所述第一设备调用自定义缩略图提供插件，从所述第二设备获取所述第一文件缩略图；
    其中，所述自定义缩略图提供插件中定义了用于从相应设备获取文件缩略图，并在文件缩略图展示请求对应路径的界面上展示文件缩略图的插件。
  19. 根据权利要求18所述的方法，其特征在于，所述自定义缩略图提供插件是ThumbnailProvider.dll。
  20. 根据权利要求14-19中任一项所述的方法，其特征在于，所述文件缩略图展示请求对应路径属于所述第一设备的资源管理器应用，所述第一设备在所述文件缩略图展示请求对应路径的资源管理器界面上展示所述第一文件缩略图。
  21. 根据权利要求20所述的方法，其特征在于，在所述第一设备接收所述文件缩略图展示请求之前，所述方法还包括：
    所述第一设备在与所述第二设备之间建立通信连接之后，在资源管理器应用主界面上显示所述第二设备的虚拟盘符。
  22. 根据权利要求21所述的方法，其特征在于，所述文件缩略图展示请求包括以下操作：用户在所述第一设备上对所述第二设备任意路径下文件夹虚拟图标的单击操作、双击操作、长按后选择打开选项的操作、鼠标右键后选择打开选项的操作。
  23. 根据权利要求14-22中任一项所述的方法，其特征在于，所述方法还包括：
    响应于接收到用户对第一文件的文件打开请求，所述第一设备向所述第二设备发送第二请求消息，所述第二请求消息中携带有所述第一文件对应的缩略图标的标识，所述第二请求消息用于请求所述第一文件的详细信息，所述第一文件是所述第一文件缩略图中任意图标对应的文件；
    所述第二设备向所述第一设备发送所述第一文件的详细信息；
    所述第一设备在所述文件打开请求对应路径的界面上展示所述第一文件的详细信息。
  24. 根据权利要求23所述的方法，其特征在于，所述第一文件是图片、视频或者音频。
  25. 一种第一设备，其特征在于，所述第一设备包括：
    存储器，用于存储计算机程序；
    收发器，用于接收或发送无线电信号；
    处理器，用于执行所述计算机程序，使得所述第一设备实现如权利要求1-13中任一项所述的方法。
  26. 一种跨设备文件显示系统，其特征在于，所述通信系统用于实现如权利要求14-24中任一种可能的实现方式中的方法，所述通信系统包括：
    如权利要求25所述的第一设备，以及与所述第一设备建立了通信连接的第二设备。
  27. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序代码，所述计算机程序代码被处理电路执行时实现如权利要求1-13任一项所述的方法。
  28. 一种芯片系统，其特征在于，所述芯片系统包括处理电路、存储介质，所述存储介质中存储有计算机程序代码；所述计算机程序代码被所述处理电路执行时实现如权利要求1-13中任一项所述的方法。
  29. 一种计算机程序产品，其特征在于，所述计算机程序产品用于在计算机上运行，以实现如权利要求1-13中任一项所述的方法。
PCT/CN2022/123906 2021-10-22 2022-10-08 一种跨设备文件显示方法、设备及系统 WO2023066036A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111234902.8 2021-10-22
CN202111234902.8A CN116009742A (zh) 2021-10-22 2021-10-22 一种跨设备文件显示方法、设备及系统

Publications (1)

Publication Number Publication Date
WO2023066036A1 true WO2023066036A1 (zh) 2023-04-27

Family

ID=86021718

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/123906 WO2023066036A1 (zh) 2021-10-22 2022-10-08 一种跨设备文件显示方法、设备及系统

Country Status (2)

Country Link
CN (1) CN116009742A (zh)
WO (1) WO2023066036A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140330872A1 (en) * 2013-05-02 2014-11-06 Samsung Electronics Co., Ltd. Method and apparatus for managing file using thumbnail
CN104199728A (zh) * 2014-08-14 2014-12-10 腾讯科技（深圳）有限公司 图片传送信息展示方法和装置
CN104243923A (zh) * 2014-09-09 2014-12-24 苏州科达科技股份有限公司 一种图片处理及图片预览的方法及系统
CN109388620A (zh) * 2018-09-30 2019-02-26 联想(北京)有限公司 一种跨设备访问数据的方法及第一电子设备
CN112486363A (zh) * 2020-10-30 2021-03-12 华为技术有限公司 一种跨设备的内容分享方法、电子设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140330872A1 (en) * 2013-05-02 2014-11-06 Samsung Electronics Co., Ltd. Method and apparatus for managing file using thumbnail
CN104199728A (zh) * 2014-08-14 2014-12-10 腾讯科技（深圳）有限公司 图片传送信息展示方法和装置
CN104243923A (zh) * 2014-09-09 2014-12-24 苏州科达科技股份有限公司 一种图片处理及图片预览的方法及系统
CN109388620A (zh) * 2018-09-30 2019-02-26 联想(北京)有限公司 一种跨设备访问数据的方法及第一电子设备
CN112486363A (zh) * 2020-10-30 2021-03-12 华为技术有限公司 一种跨设备的内容分享方法、电子设备及系统

Also Published As

Publication number Publication date
CN116009742A (zh) 2023-04-25

Similar Documents

Publication Publication Date Title
CN113741840B (zh) 多窗口投屏场景下的应用界面显示方法及电子设备
WO2021052147A1 (zh) 一种数据传输的方法及相关设备
WO2022262530A1 (zh) 内存管理的方法及电子设备
WO2021043029A1 (zh) 一种切换应用的方法及电子设备
US20230094172A1 (en) Cross-Device Application Invoking Method and Electronic Device
WO2022252805A1 (zh) 显示方法及电子设备
WO2023207761A1 (zh) 外设控制方法、电子设备及系统
WO2022247495A1 (zh) 音频焦点的控制方法及相关装置
CN114741039A (zh) 设备控制方法和终端设备
WO2022052928A1 (zh) 一种应用接入方法及相关装置
WO2023109607A1 (zh) 应用界面跨设备显示方法、设备系统
WO2023066036A1 (zh) 一种跨设备文件显示方法、设备及系统
WO2022161058A1 (zh) 一种全景图像的拍摄方法及电子设备
EP4191409A1 (en) Shared library multiplexing method and electronic device
WO2024022119A1 (zh) 数据同步方法、电子设备及系统
WO2023071590A1 (zh) 输入控制方法及电子设备
WO2023142696A1 (zh) 缩略图存储方法及电子设备
WO2024104131A1 (zh) 一种多窗口场景下的窗口获焦方法、设备及系统
WO2024078337A1 (zh) 一种显示屏选择方法及电子设备
WO2023061298A1 (zh) 一种图片备份系统、方法与设备
CN116679998B (zh) 多设备协同冲突处理的方法及电子设备
WO2023125832A1 (zh) 图片分享方法和电子设备
CN115250261B (zh) 一种信息的显示方法及电子设备
WO2023061014A1 (zh) 任务管理方法及装置
WO2024125287A1 (zh) 数据同步方法及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22882646

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22882646

Country of ref document: EP

Kind code of ref document: A1