Cross-device file management method and apparatus, and electronic device and program product

Abstract

Disclosed in the embodiments of the present application are a cross-device file management method and apparatus, and an electronic device and a program product. The method is applied to a first electronic device, and the first electronic device establishes a communication connection with a second electronic device. The method comprises: acquiring file information corresponding to one or more files stored in a second electronic device; displaying a file management interface on the basis of the file information corresponding to the one or more files, wherein icons corresponding to the one or more files are displayed in the file management interface, and the icons corresponding to the files are determined on the basis of file types corresponding to the files; and in response to a trigger operation on a target icon in the file management interface, performing a management operation on a target file corresponding to the target icon.

Description

Cross-device file management methods, devices, electronic equipment and software products

[0001] This application claims priority to Chinese Patent Application No. 202411448833.4, filed on October 16, 2024, entitled “Cross-Device File Management Method, Apparatus, Electronic Device and Program Product”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a cross-device file management method, apparatus, electronic device, and program product. Background Technology

[0003] With the rapid development of information technology, cross-device file management has become an indispensable function in daily work and life. Users can manage files stored on one electronic device while using another, meeting their convenient file management needs. Currently, most cross-device file management solutions on the market display limited information on their front-end file management interfaces, making them less intuitive and affecting the convenience and accuracy of file management operations for users. Summary of the Invention

[0004] This application discloses a cross-device file management method, apparatus, electronic device, and program product.

[0005] This application discloses a cross-device file management method applied to a first electronic device, wherein the first electronic device establishes a communication connection with a second electronic device, the method comprising:

[0006] Obtain file information corresponding to one or more files stored in the second electronic device;

[0007] Based on the file information corresponding to the one or more files, a file management interface is displayed; the file management interface displays one or more icons corresponding to the files, and the icons corresponding to the files are determined according to the file types corresponding to the files;

[0008] In response to a trigger operation on a target icon in the file management interface, management operations are performed on the target file corresponding to the target icon.

[0009] This application discloses a cross-device file management method applied to a second electronic device, wherein the second electronic device establishes a communication connection with a first electronic device, and the method includes:

[0010] The first electronic device sends file information corresponding to one or more files stored in the second electronic device, so that the first electronic device displays a file management interface based on the file information corresponding to the one or more files; the file management interface displays one or more icons corresponding to the files, and the icons corresponding to the files are determined according to the file types corresponding to the files; the file management interface is used to provide management functions for the files stored in the second electronic device.

[0011] This application discloses a cross-device file management device applied to a first electronic device, wherein the first electronic device establishes a communication connection with a second electronic device, the device comprising:

[0012] The information acquisition module is used to acquire file information corresponding to one or more files stored in the second electronic device;

[0013] The display module is used to display a file management interface based on the file information corresponding to the one or more files; the file management interface displays one or more icons corresponding to the files, and the icons corresponding to the files are determined according to the file types corresponding to the files;

[0014] The management module is used to perform management operations on the target file corresponding to the target icon in response to the trigger operation of the target icon in the file management interface.

[0015] This application discloses a cross-device file management device applied to a second electronic device, wherein the second electronic device establishes a communication connection with a first electronic device, and the device includes:

[0016] The information sending module is used to send file information corresponding to one or more files stored in the second electronic device to the first electronic device, so that the first electronic device can display a file management interface based on the file information corresponding to the one or more files; the file management interface displays one or more icons corresponding to the files, and the icons corresponding to the files are determined according to the file types corresponding to the files; the file management interface is used to provide management functions for the files stored in the second electronic device.

[0017] This application discloses an electronic device, including a memory, a processor, and a transceiver unit. The memory stores a computer program, and when the computer program is executed by the processor, the electronic device performs the method described in any of the above embodiments.

[0018] This application discloses a computer-readable storage medium storing a computer program thereon, which, when executed by a processor in an electronic device, causes the electronic device to perform the method described in any of the above embodiments.

[0019] This application discloses a computer program product, including a computer program, which, when executed by a processor in an electronic device, causes the electronic device to perform the method described in any of the above embodiments.

[0020] Details of one or more embodiments of this application are set forth in the following drawings and description. Other features and advantages of this application will be apparent from the specification, drawings, and claims. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 illustrates an application scenario of a cross-device file management method in one embodiment.

[0023] Figure 2 is a timing diagram of a cross-device file management method in one embodiment;

[0024] Figure 3 is a flowchart of a cross-device file management method in one embodiment;

[0025] Figure 4 is a schematic diagram of icons in one embodiment;

[0026] Figure 5A is a schematic diagram of the interface for triggering file management operations in a second electronic device in one embodiment;

[0027] Figure 5B is a schematic diagram of the interface for triggering file management operations in a second electronic device in another embodiment;

[0028] Figure 6 is a flowchart of an embodiment of implementing cross-device file search functionality;

[0029] Figure 7A is a schematic diagram of the file management interface in one embodiment;

[0030] Figure 7B is a schematic diagram of the file management interface in another embodiment;

[0031] Figure 7C is a schematic diagram of the file management interface in another embodiment;

[0032] Figure 8 is a flowchart of a first electronic device managing target files in a second electronic device in one embodiment;

[0033] Figure 9 is a timing diagram of a second electronic device transmitting files to a first electronic device in one embodiment;

[0034] Figure 10 is a timing diagram of data transmission between a first electronic device and a second electronic device in one embodiment;

[0035] Figure 11 is a timing diagram of data transmission between the first electronic device and the second electronic device in another embodiment;

[0036] Figure 12 is a timing diagram of data transmission between the first electronic device and the second electronic device in another embodiment;

[0037] Figure 13 is a flowchart of a first electronic device downloading a file from a second electronic device in one embodiment;

[0038] Figure 14 is a timing diagram of sending files from a second electronic device to a third-party application local to a first electronic device in one embodiment;

[0039] Figure 15 is a schematic diagram of the file management interface in another embodiment;

[0040] Figure 16 is a flowchart of a cross-device file management method in another embodiment;

[0041] Figure 17 is a block diagram of a cross-device file management device in one embodiment;

[0042] Figure 18 is a block diagram of a cross-device file management device in another embodiment;

[0043] Figure 19 is a structural block diagram of an electronic device in one embodiment. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] It should be noted that the terms "comprising" and "having," and any variations thereof, in the embodiments and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0046] It is understood that the terms "first," "second," etc., used herein may be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of this application, a first electronic device may be referred to as a second electronic device, and similarly, a second electronic device may be referred to as a first electronic device. Both the first electronic device and the second electronic device are electronic devices, but they are not the same electronic device.

[0047] Figure 1 illustrates an application scenario of a cross-device file management method in one embodiment. As shown in Figure 1, a communication connection can be established between the first electronic device 110 and the second electronic device 120. The first electronic device 110 and the second electronic device 120 may include, but are not limited to, mobile phones, wearable devices (such as smartwatches, smart glasses, etc.), vehicle terminals, tablet computers, laptops, PCs (Personal Computers), smart home devices, and other devices.

[0048] For example, the first electronic device 110 may be a laptop or PC, and the second electronic device may be a mobile phone or wearable device, etc., but is not limited thereto.

[0049] In this embodiment of the application, cross-device file management can be implemented on the first electronic device 110. The cross-device file management can refer to the first electronic device 110 managing files stored on other electronic devices (such as the second electronic device 120).

[0050] The communication connection established between the first electronic device 110 and the second electronic device 120 may include, but is not limited to, Bluetooth communication connection, Wi-Fi communication connection, USB (Universal Serial Bus) connection, etc.

[0051] Optionally, the first electronic device 110 and the second electronic device 120 may establish a communication connection based on the WebSocket protocol, which is a protocol for full-duplex communication over a single TCP (Transmission Control Protocol) connection.

[0052] In some embodiments, the first electronic device 110 and the second electronic device 120 may be electronic devices from different manufacturers, and the operating systems of the first electronic device 110 and the second electronic device 120 may be different. For example, the operating system of the first electronic device 110 may be a Mac operating system or a Windows operating system, and the second electronic device may be an Android operating system, but it is not limited to these. In related technologies, due to the different technical standards and data formats supported by electronic devices from different manufacturers, cross-device file management between electronic devices from different manufacturers is usually quite difficult, and the file management interface displayed on the front end shows limited information and provides relatively simple management operations, which cannot meet the user's needs.

[0053] In this embodiment, the first electronic device 110 may install a file management application for implementing cross-device file management functions. This file management application provides the function of managing files stored in the second electronic device 120 by the first electronic device 110. The file management application may display a file management interface, and users can perform management operations on the files stored in the second electronic device 120 by interacting with the file management interface.

[0054] When the first electronic device 110 and the second electronic device 120 establish a communication connection, the second electronic device 120 can send file information corresponding to one or more files stored within itself to the first electronic device 110. The first electronic device 110 can obtain the file information corresponding to one or more files sent by the second electronic device 120 and display a file management interface based on this information. Furthermore, the first electronic device 110 can display this file management interface within a file management application. This file management interface displays icons corresponding to one or more files in the second electronic device 120, where the icons are determined based on the file type.

[0055] Users can manage files in the second electronic device 120 through the file management interface. Users can select one or more icons in the file management interface to manage files. The first electronic device 110 can respond to a trigger operation on a target icon in the file management interface and perform management operations on the target file corresponding to that target icon.

[0056] Figure 2 is a timing diagram of a cross-device file management method in one embodiment. As shown in Figure 2, the cross-device file management method may include the following steps:

[0057] Step 1: The second electronic device sends file information corresponding to one or more files stored in itself to the first electronic device, and the first electronic device obtains the file information corresponding to one or more files stored in the second electronic device.

[0058] Step 2: The first electronic device displays a file management interface based on the file information corresponding to the one or more files. This file management interface displays icons corresponding to one or more files in the second electronic device, where the file icon is determined based on the file type.

[0059] Step 3: The first electronic device responds to the trigger operation of the target icon in the file management interface and performs management operations on the target file corresponding to the target icon. Furthermore, the first electronic device can perform management operations on the target file in the second electronic device through information interaction with the second electronic device.

[0060] As shown in Figure 3, in one embodiment, a cross-device file management method is provided, which can be applied to the first electronic device described above. This cross-device file management method may include the following steps:

[0061] Step 310: Obtain file information corresponding to one or more files stored in the second electronic device.

[0062] When a communication connection is established between the first electronic device and the second electronic device, the second electronic device can send file information corresponding to one or more files stored within itself to the first electronic device. The files stored by the second electronic device may include, but are not limited to, images, videos, audio files, documents, application package files, etc. The file information may refer to information describing the file, such as, but is not limited to, the filename, the application to which the file belongs, and / or the file type.

[0063] The second electronic device can send file information corresponding to all the files it stores to the first electronic device, or it can send file information corresponding to some of the files it stores to the first electronic device.

[0064] In one implementation, when the first electronic device has a file management application enabled, the first electronic device can send a file information retrieval request to the second electronic device. After receiving the file information retrieval request from the first electronic device, the second electronic device can respond to the file information retrieval request by sending file information corresponding to one or more files stored therein to the first electronic device.

[0065] In some embodiments, when a user accesses files in a directory on a second electronic device through a file management application, the first electronic device, in response to the user's access operation to the first directory (e.g., clicking the first directory), can send a file information retrieval request corresponding to the first directory to the second electronic device. This file information retrieval request can carry directory information of the first directory (such as directory path, directory name, etc.). After receiving the file information retrieval request, the second electronic device can send the file information of each file belonging to the first directory to the first electronic device based on the directory information of the first directory carried in the file information retrieval request. This method ensures the accuracy of the files displayed in the file management application, avoids file omissions, and improves the accuracy of cross-device file management.

[0066] Step 320: Display the file management interface based on the file information corresponding to the one or more files; the file management interface displays icons corresponding to one or more files, and the icons corresponding to the files are determined according to the file types corresponding to the files.

[0067] The file management interface refers to the interface used in a file management application to display files stored on a second electronic device and provide management functions. The first electronic device can display the file management interface based on the file information corresponding to one or more files stored on the second electronic device.

[0068] In related technologies, the front-end interface of applications used to implement cross-device file management typically relies on the interface of the local file management tool of the first electronic device. This local file management tool refers to the tool used to manage local files on the first electronic device, which cannot be customized, resulting in a poor user experience. Moreover, the icon styles displayed on the front-end interface generally follow the icon styles of the local file management tool on the first electronic device. The icon styles are limited and not easy to distinguish, leading to a high error rate for users when multiple file types are mixed.

[0069] In this embodiment, the front-end interface of the file management application does not rely on the local file management tool of the first electronic device, but is a self-designed and developed front-end interface. In some embodiments, the file management interface can be implemented using tools such as Electron. Electron is a cross-platform desktop application framework built using JavaScript, HTML (Hypertext Markup Language), and CSS (Cascading Style Sheets). It is compatible with various operating systems, allowing developers to use web development methods for front-end interface development, enabling highly flexible interactive development, thereby developing more aesthetically pleasing and interactive front-end interfaces and increasing the customization space of the application.

[0070] The file management interface may include a file display area, which can be used to display icons corresponding to one or more files in the second electronic device. These icons may refer to graphic symbols with descriptive meaning.

[0071] The icon corresponding to a file can be determined based on the file type, which in turn can be determined based on the file format. For example, the file type can include, but is not limited to, one or more of the following: presentation documents, videos, images, audio, spreadsheets, text documents, plain text documents, and application package files; no further limitation is imposed here.

[0072] Optionally, after the first electronic device obtains file information corresponding to one or more files stored in the second electronic device, this file information may include the file name. The first electronic device can analyze the extensions in the file names of each file to determine the file type. The file name extension refers to the suffix in the file name, which can be used to characterize the file format.

[0073] For example, file types with extensions such as .dwt (Dreamweaver Template) and .dxf (Drawing Exchange Format) can be drawing files; file types with extensions such as .key and .ppt (PowerPoint) can be presentation documents; file types with extensions such as .txt and .md (Markdown) can be plain text documents; file types with extensions such as .pages and .doc (DOCument) can be text documents; file types with extensions such as .jpg (Joint Photographic Experts Group) and .gif (Graphics Interchange Format) can be images; file types with extensions such as .numbers and .excel can be spreadsheet documents; and file types with extensions such as .apk (Android application package) can be application package files, etc., but are not limited to these.

[0074] Different icons can be set for different file types. For example, Figure 4 is a schematic diagram of icons in one embodiment. As shown in Figure 4, the icon corresponding to a drawing file can be icon 402; the icon corresponding to a presentation document can be icon 404; the icon corresponding to a text document can be icon 406; the icon corresponding to a table document can be icon 408; the icon corresponding to a plain text document can be icon 410; and the icon corresponding to an application package file can be icon 412. It should be noted that Figure 4 is only used to illustrate the relationship between file types and icons in this embodiment and is not intended to limit specific icon styles. The icon styles can be set according to actual needs; or they can be based on more or fewer file types than those shown in Figure 4. Optionally, the icons corresponding to each file type can be simple and clear rounded corner file icons.

[0075] In some embodiments, the first electronic device may pre-store a mapping relationship between file types and icons. For example, an icon mapping table may be pre-stored, which may include icons (or icon information, such as icon number, icon name, etc.) corresponding to multiple file types and / or extensions. After the first electronic device obtains file information of one or more files stored in the second electronic device, it can determine the extension and / or file type corresponding to each file, and determine the icon corresponding to each file's extension and / or file type according to the mapping relationship, displaying the corresponding icon for each file in the file management interface. Through the pre-stored mapping relationship, the icon corresponding to each file can be determined quickly and accurately, improving the efficiency of displaying icons in the file management interface.

[0076] In this embodiment, the file management application can customize simpler and clearer file icons for different file types. Compared with the way files are displayed in related technologies, there are more file types and more detailed divisions. The graphic features of each icon are more obvious and clear, which can help users quickly find the file they want to operate on when multiple file types are mixed together, reduce the error rate and improve the convenience of operation.

[0077] Step 330: In response to the triggering operation of the target icon, perform management operations on the target file corresponding to the target icon.

[0078] Users can select one or more files in the file management interface to perform management operations according to their actual needs. Optionally, the management operations may include, but are not limited to, one or more of the following: downloading, deleting, editing, opening files, copying, and sending files to local applications.

[0079] The download operation can refer to the operation of downloading files from the second electronic device to the local device of the first electronic device.

[0080] The deletion operation can refer to the operation of deleting files from a second electronic device.

[0081] Editing operations can refer to the operation of editing files on a second electronic device using a first electronic device.

[0082] The file opening operation can refer to the operation of opening a second electronic device from a first electronic device.

[0083] A copy operation refers to the operation of copying files from a second electronic device to the local device of a first electronic device, such as an application that copies files from a second electronic device to the local device of a first electronic device.

[0084] The operation of sending a file to a local application refers to sending a file from a second electronic device to a local application on a first electronic device.

[0085] It should be noted that the local application on the first electronic device can be a third-party application installed on the first electronic device. For example, the application may include, but is not limited to, social applications, audio and video playback applications, and game applications. The local application on the first electronic device may also be a non-third-party application on the first electronic device, such as the desktop of the first electronic device or the native applications of the first electronic device.

[0086] Different management operations can correspond to the same or different trigger operations. These trigger operations refer to user actions on file icons that initiate file management. When the first electronic device detects a user's trigger operation on a target icon in the file management interface, it can respond to this trigger operation by performing management operations on the target file corresponding to that icon. It should be noted that the target icon refers to the icon triggered by the user; there can be one or more target icons. That is, the user can select only one file for management or select multiple files for batch management.

[0087] For example, different management operations can all be triggered by right-clicking the file icon, displaying a drop-down menu, and selecting the management operation from the menu. For instance, Figure 5A is a schematic diagram of the interface for triggering a file management operation on a second electronic device in one embodiment. As shown in Figure 5A, the user can select one or more files displayed on the file management interface 500, right-click the icon of the file, and the first electronic device can display a drop-down menu 510 on the file management interface 500. This drop-down menu 510 can include multiple selectable management operations, and the user can select any management operation and click it, thereby triggering the first electronic device to perform that management operation on the selected file.

[0088] For example, the trigger for copying could be right-clicking the file icon, displaying a drop-down menu, and selecting the copy operation from the menu. Sending a file to a local application or downloading it could be triggered by dragging and dropping the file icon. Dragging the file icon to a local application on the first electronic device sends the file to that application; dragging the file icon to a local file directory on the first electronic device downloads the file to that directory. For example, Figure 5B is a schematic diagram of an interface for triggering file management operations on a second electronic device in another embodiment. As shown in Figure 5B, the user can select one or more files displayed on the file management interface 500, and can trigger the first electronic device to send the one or more files to the third-party application by dragging the icons of these files to the local third-party application interface 520, thus allowing the third-party application to access the one or more files.

[0089] It should be noted that the triggering operation can also be other operations, such as double-clicking an icon, operating an icon via a shortcut key, long-pressing and dragging an icon, selecting multiple icons simultaneously, etc., which are not limited here.

[0090] In the above implementation, the file management application can provide richer and more flexible management operations and triggering operations, improve the user's interactive experience, and better meet the user's needs for cross-device file management.

[0091] In this embodiment of the application, the first electronic device can display icons corresponding to the file types of the files stored in the second electronic device in the file management interface corresponding to the second electronic device. The icons can more intuitively reflect the file types, which can help users find the files that need to be managed more quickly, reduce the probability of misoperation, and improve the convenience and accuracy of users managing files across devices.

[0092] In some embodiments, the file management application may also provide a search function for searching files on the second electronic device. As shown in Figure 6, the above method may further include the following steps:

[0093] Step 602: In response to the search operation, retrieve the search content entered in the search component.

[0094] The file management interface of a file management application may include a file display area and a function area. The file display area can be used to display icons corresponding to one or more files, and the function area can be used to provide one or more functional components, each of which can be used to implement different functions. In this embodiment, the function area may include a search component, which can be used to receive search content input by the user and trigger a search function to search for files in the second electronic device. For example, the search component may be a search box, etc.

[0095] The first electronic device can, in response to a search operation on the search component, obtain the search content entered by the user in the search component. The search content refers to the content entered by the user in the search component, such as search keywords entered by the user.

[0096] Step 604: Based on the search content and the file information corresponding to one or more files, determine one or more files that match the search content.

[0097] The first electronic device can search based on the search content and file information corresponding to one or more files stored in the second electronic device to find files whose file information matches the search content. The search can be performed using either fuzzy search or exact search. Fuzzy search is an approximate matching search method, allowing search results that are similar to but not exactly the search content. Exact search, on the other hand, is a completely identical search method, yielding search results that are exactly the same as the search content.

[0098] Optionally, a file whose name matches the search content can be searched. The first electronic device can compare the search content with the file names corresponding to one or more files stored in the second electronic device. If the file name contains the search content, then the file can be determined to be a file that matches the search content.

[0099] Optionally, files whose content matches the search content can be searched. For example, the second electronic device can identify the content of each stored file and generate file tags corresponding to each file based on the identification results. These file tags can be used to characterize the file content. For instance, the second electronic device can identify stored images and generate file tags (such as tags for people, scenery, animals, food, etc.) that can characterize the image content based on the identified image content. The file information corresponding to a file may include the file tags. After the first electronic device obtains the search content, it can compare the search content with the file tags corresponding to one or more files stored in the second electronic device. If the file tags of a file are the same as or similar to the search content, then the file can be determined to be a file matching the search content.

[0100] Step 606: Display icons corresponding to one or more matching files in the file display area.

[0101] After the first electronic device identifies one or more files in the second electronic device that match the search content, it can display icons corresponding to each matching file in the file display area for the user to view.

[0102] For example, Figure 7A is a schematic diagram of a file management interface in one embodiment. As shown in Figure 7A, the file management interface 500 may include a file display area 710 and a function area 720, wherein the function area 720 may include a search component 722. For example, the function area 720 may be located above the file display area 710. The user can enter the search content to be searched in the search component 722. The first electronic device searches for files stored in the second electronic device according to the search content, and can display the icons corresponding to each searched file in the file display area 710.

[0103] In this embodiment of the application, the file management application can also provide a search function to search for files on the second electronic device, realize cross-device file search, meet the user's search needs, and improve the user experience.

[0104] In some embodiments, the file management interface may further include a file categorization area, which may include multiple categories, and these categories may be divided according to one or more of the following methods:

[0105] (1) Divide according to the file type corresponding to the file.

[0106] The file management application can categorize files on the second electronic device into multiple categories based on their file types. The first electronic device can determine the file type of each file based on its extension and assign the file to the corresponding category. For example, files can be categorized into images, videos, music, documents, and compressed files based on their file types. Optionally, the categories corresponding to the file types can be determined based on user habits. For instance, multiple file types can be selected according to their frequency of use, from highest to lowest, and multiple categories can be created based on these selected file types.

[0107] (2) Divide according to the application to which the file belongs.

[0108] The file management application can categorize files on the second electronic device into multiple categories based on the application to which the files belong. The first electronic device can determine the application to which each file on the second electronic device belongs and assign the file to the category corresponding to that application. Optionally, the categories corresponding to the applications can be determined based on user habits. For example, multiple applications can be selected according to their usage frequency from high to low, and multiple categories can be created based on the selected file types.

[0109] (3) The time allocation for management operations according to documents.

[0110] The file management application can categorize files on the second electronic device according to the operation time of file management operations. The first electronic device can determine the operation time of the most recent management operation for each file on the second electronic device, determine the time interval to which the most recent management operation time of each file belongs, and then classify the files into the category corresponding to that time interval. For example, files can be classified into categories such as the most recent day, the most recent week, and the most recent month according to the operation time of file management operations.

[0111] For example, Figure 7B is a schematic diagram of a file management interface in another embodiment. As shown in Figure 7B, the file management interface 500 may include a file display area 710, a function area 720, and a file categorization area 730. The function area 720 may be located on the first side of the file display area (such as the top side), and the file categorization area 730 may be located on the second side of the file display area (such as the left side). This layout makes the file management interface more concise and aesthetically pleasing, and improves the interactivity of the interface. The file categorization area 730 may display multiple categories, such as categorizing files according to their file type (images, videos, audio, documents, and compressed files), categorizing them according to the application to which they belong (application 1, application 2, etc.), and categorizing them according to the time of file management operations (recent files, such as files managed within the last day) and device storage (referring to non-recent files). Users can click on any category, and the file display area 710 can display icons corresponding to each file under the clicked category.

[0112] In this embodiment, file categorization across devices can be implemented using various dimensions, helping users to find files more quickly across devices and improving file management efficiency. Furthermore, file categorization across devices can be based on user habits, making the categories more aligned with actual user needs and enhancing the user experience.

[0113] In some embodiments, the file management application may also provide the ability to view records of file management operations across devices. The file management interface may also include a recording component that provides the ability to view file management records. When a user needs to view file management records, the user may trigger the recording component (e.g., by clicking the recording component), and the first electronic device may, in response to the triggering operation of the recording component, display one or more file management records in the file management interface. These file management records include operation information related to file management operations.

[0114] Optionally, the operation information may include, but is not limited to, file name, operation type of management operation, operation time, etc., wherein the operation type of management operation may refer to the specific operation of management operation, such as one or more of the following: download operation, delete operation, edit operation, copy operation, operation of sending target file to local application (or sharing operation).

[0115] It should be noted that the file management records displayed in the file management interface can be file management records corresponding to all management operations performed on the first electronic device, file management records corresponding to management operations performed by the file management application running on the first electronic device this time, or file management records corresponding to specific management operations. For example, only file management records corresponding to download operations can be displayed, but this is not limited to these. This application embodiment does not limit the specific file management records displayed.

[0116] For example, Figure 7C is a schematic diagram of a file management interface in another embodiment. As shown in Figure 7C, the file management interface 500 may also include a recording component 740. Further, the functional area 720 may include the recording component 740, which may be located to the right of the search component 722. Users can view file management records by clicking on the recording component 740.

[0117] In this embodiment, the file management application can also provide the function of viewing the record of file management operations across devices. Users can view the file management record by triggering the record component on the file management interface, which realizes richer cross-device file management functions, meets the user's needs, and improves the user experience.

[0118] In some embodiments, as shown in FIG8, the step of managing the target file corresponding to the target icon may include the following steps:

[0119] Step 802: Obtain the first path information of the target file in the second electronic device.

[0120] When the first electronic device detects a user's trigger operation on a target icon in the file management interface, it determines that a management operation needs to be performed on the target file corresponding to the target icon. It can determine the first path information of the target file in the second electronic device, which can be used to characterize the storage path of the target file in the second electronic device.

[0121] In some embodiments, the file information corresponding to one or more files sent by the second electronic device to the first electronic device may include the first path information of the files in the second electronic device. When the first electronic device detects a trigger operation performed by the user on the target icon in the file management interface, it can obtain the first path information of the target file in the second electronic device based on the file information corresponding to the target file.

[0122] Step 804: Generate an operation request based on the first path information and send the operation request to the second electronic device so that the second electronic device can perform the corresponding management operation on the target file corresponding to the first path information according to the operation request.

[0123] The first electronic device can generate an operation request corresponding to the target file based on the first path information of the target file in the second electronic device. The operation request can carry the first path information of the target file in the second electronic device. The first electronic device can send the operation request to the second electronic device, and the second electronic device can determine the target file corresponding to the first path information based on the first path information carried in the operation request, and perform management operations on the target file.

[0124] As an optional implementation, the operation request may further include an operation type identifier corresponding to the management operation to be performed. This operation type identifier can be used to identify the operation type corresponding to the management operation. For example, the operation type identifier may be represented by one or more of numbers, letters, and symbols. The second electronic device can perform the management operation corresponding to the operation type identifier on the target file according to the operation type identifier carried in the operation request.

[0125] Taking the deletion of a target file as an example, the first electronic device can send a deletion request to the second electronic device. The deletion request may include the first path information of the target file in the second electronic device and the operation type identifier corresponding to the deletion operation. After receiving the deletion request sent by the first electronic device, the second electronic device can delete the target file corresponding to the first path information according to the deletion request.

[0126] As an alternative implementation, the management operation to be performed can be an operation requiring data transfer, such as downloading, copying, opening files, or sending a target file to a local application. The first electronic device can generate an operation request based on the first path information and send the operation request to the second electronic device. This operation request can be used to instruct the second electronic device to create a data transfer channel corresponding to the target file and return response information.

[0127] The operation request may carry the first path information of the target file in the second electronic device. After receiving the operation request sent by the first electronic device, the second electronic device can determine the target file according to the first path information carried in the operation request, create a data transmission channel corresponding to the target file, and send response information to the first electronic device.

[0128] The data transmission channel can refer to the channel for data transmission between the first electronic device and the second electronic device. Optionally, the data transmission channel can be a virtual transmission channel or a physical communication link. The virtual transmission channel can refer to a virtual connection abstracted on the physical communication link, which can be used to transmit data, so that there is no need to pay attention to the underlying physical implementation details when transmitting data.

[0129] The first electronic device can receive response information sent by the second electronic device, and based on the response information, send a data acquisition request to the second electronic device. The data acquisition request is used to instruct the second electronic device to transfer the file data of the target file to the first electronic device through the data transmission channel.

[0130] After receiving the response information from the second electronic device, the first electronic device can determine from the response information that the second electronic device has created a data transmission channel corresponding to the target file, and can then send a data acquisition request to the second electronic device. Upon receiving the data acquisition request from the first electronic device, the second electronic device can send the file data of the target file to the first electronic device through the data transmission channel corresponding to the target file.

[0131] For example, Figure 9 is a timing diagram illustrating the transmission of a file from a second electronic device to a first electronic device in one embodiment. As shown in Figure 9, when the first electronic device detects a user's trigger operation on a target icon in the file management interface, it can obtain the first path information of the target file corresponding to the target icon in the second electronic device. The first electronic device can generate an operation request based on the first path information and send the operation request to the second electronic device. The second electronic device receives the operation request sent by the first electronic device, can create a data transmission channel corresponding to the target file based on the operation request, and sends a response message to the first electronic device. After receiving the response message sent by the second electronic device, the first electronic device can send a data acquisition request to the second electronic device. The second electronic device receives the data acquisition request sent by the first electronic device and, based on the data acquisition request, sends the target file to the first electronic device through the data transmission channel corresponding to the target file to complete the transmission of the file data of the target file.

[0132] In this embodiment, when data transmission of a target file is required, the first electronic device can first send an operation request to the second electronic device, carrying the first path information of the target file in the second electronic device, so that the second electronic device can prepare for transmission, identify the target file and create a corresponding data transmission channel. The first electronic device can then send a data acquisition request to the second electronic device so that the second electronic device can transmit the file data of the target file through the data transmission channel. The data transmission of the file data and the information triggering the data transmission can be sent separately, which improves the flexibility and efficiency of data transmission.

[0133] In some embodiments, the operation request may carry not only the first path information of the target file in the second electronic device, but also a task identifier for the download task corresponding to the target file. The second electronic device creates a data transmission channel corresponding to the target file and binds the data transmission channel to the task identifier.

[0134] If the first electronic device determines that the management operation to be performed may involve data transmission, it can create a download task corresponding to the target file and assign a task identifier, such as a task ID (identity document). An operation request can be generated based on the first path information of the target file in the second electronic device and the task identifier. Upon receiving the operation request, the second electronic device can determine the target file based on the first path information and create a data transmission channel corresponding to the target file, binding this data transmission channel to the task identifier.

[0135] After receiving the response information sent by the second electronic device, the first electronic device can generate a data acquisition request based on the task identifier of the download task and send the data acquisition request to the second electronic device. The data acquisition request is used to instruct the second electronic device to transfer the file data of the target file to the first electronic device through the data transmission channel corresponding to the task identifier.

[0136] After receiving a data acquisition request from the first electronic device, the second electronic device can determine the data transmission channel corresponding to the task identifier carried in the data acquisition request, determine the file to be transmitted as the target file, and transmit the file data of the target file to the first electronic device through the data transmission channel.

[0137] Optionally, if multiple target files exist, the first electronic device can generate a single download task, corresponding to each of the target files; alternatively, the first electronic device can generate multiple download tasks, each corresponding to a specific target file. The download request sent by the first electronic device can carry task identifiers corresponding to each of the multiple download tasks. The second electronic device can create a data transmission channel based on the task identifiers of each download task, and sequentially send the file data of each target file to the first electronic device through this channel; alternatively, the second electronic device can create multiple data transmission channels based on the task identifiers of each download task, and send the file data of multiple target files to the first electronic device in parallel through these multiple data transmission channels, without affecting or interfering with each other's transmission.

[0138] In this embodiment, the first electronic device can create a download task and send an operation request carrying a task identifier of the download task, so that the second electronic device binds the created data transmission channel with the task identifier, thereby enabling more accurate and convenient data transmission and improving the accuracy and efficiency of cross-device file transmission.

[0139] In some embodiments, data transmission between the first electronic device and the second electronic device can be achieved using a combination of the WebSocket protocol and the HTTP protocol over a local area network.

[0140] The WebSocket protocol enables full-duplex communication over a single TCP connection, allowing persistent connections between clients and servers. It allows the server to proactively push data to the client. A first electronic device can act as a WebSocket client, and a second electronic device as a WebSocket server. The first device can send messages to the second device and receive event-driven responses. Because WebSocket allows bidirectional communication between the server and client, supporting more frequent two-way data exchange, it is well-suited for short message delivery.

[0141] The HTTP protocol is a simple request-response protocol. It requires the client to make a data request to the server, and then the server responds based on the data request. It can only achieve one-way data transmission at any given time. However, the communication method is easier to manage and supports caching and resuming interrupted downloads, making it more reliable. Therefore, it is suitable for transmitting file data.

[0142] In this embodiment of the application, the operation request and response information are transmitted based on the WebSocket protocol, while the data acquisition request and the file data of the target file are transmitted based on the HTTP protocol.

[0143] For example, Figure 10 is a timing diagram of data transmission between a first electronic device and a second electronic device in one embodiment. As shown in Figure 10, the first electronic device can act as a client, and the second electronic device can create a WebSocket server. A WebSocket connection can be established between the client and the WebSocket server. The client can initiate a download request using the WebSocket protocol to the WebSocket server. This download request can carry the first path information of the target file in the second electronic device. Further, the first electronic device can also create a download task corresponding to the target file. This download request can carry the task identifier of the download task. After receiving the download request through the WebSocket server, the second electronic device can prepare the target file according to the first path information and create an HTTP server. The HTTP server can be bound to the task identifier, and the WebSocket server can send an ACK (Acknowledge character) to the client.

[0144] After receiving the ACK, the client can initiate an HTTP request to the HTTP server of the second electronic device. For example, it can request the target file via HTTP GET. Furthermore, the first electronic device can use the task identifier of the download task as the request path of the HTTP GET request, such as as the URL (uniform resource location) of the HTTP GET request. After receiving the request, the HTTP server of the second electronic device can send the file data of the target file to the client.

[0145] By combining the WebSocket protocol with the HTTP protocol to achieve cross-device file data transfer, compared with other near-field communication methods (such as Bluetooth, Wi-Fi, etc.), the transmission speed is faster and the communication is more flexible, improving the efficiency and flexibility of cross-device data transfer.

[0146] In some embodiments, when the file management application of the first electronic device detects a user's trigger operation on a target icon, it can first determine whether a communication connection has been established with the second electronic device. If a communication connection has been established, an operation request can be sent to the second electronic device. If a communication connection has not yet been established, the first electronic device can first send a connection request to the second electronic device. After receiving the connection request from the first electronic device, the second electronic device can respond to the connection request and send connection information to the first electronic device, such as IP (Internet Protocol) address and port number. After receiving the connection information, the first electronic device can establish a communication connection with the second electronic device based on the connection information.

[0147] Furthermore, after receiving a request from the first electronic device, the second electronic device can determine the request type. If the request type is an operation request, it can confirm that an operation request has been received from the first electronic device, and perform processing on the target file corresponding to the management operation based on the operation request. If the request type is a connection request, it can confirm that a connection request has been received from the first electronic device, and respond to the connection request by sending connection information to the first electronic device.

[0148] Optionally, the request sent by the first electronic device may carry a type identifier, which can be used to identify the request type corresponding to the request. The second electronic device can determine the request type corresponding to the request based on the type identifier carried in the request. Optionally, the data format may be different for different request types. The second electronic device can determine the request type corresponding to the request by analyzing the data format corresponding to the request.

[0149] The second electronic device can automatically identify the request type corresponding to the request sent by the first electronic device and respond accordingly, ensuring the accuracy and flexibility of cross-device file management.

[0150] In one specific implementation, a WebSocket connection can be established between the first electronic device and the second electronic device, and communication can be conducted based on this WebSocket connection. When the file management application of the first electronic device detects a user's trigger operation on a target icon, it can first determine whether a WebSocket connection has been established with the second electronic device. If no WebSocket connection has been established, the client of the first electronic device can send a WebSocket connection request to the second electronic device. After receiving the WebSocket connection request, the second electronic device can start or create a WebSocket server and send the IP address and port number that the WebSocket server is listening on back to the first electronic device. The client of the first electronic device can then establish a WebSocket connection with the WebSocket server of the second electronic device based on this IP address and port number.

[0151] In some embodiments, the file management application running on the first electronic device may run an extension process (or extension module). This extension process (or extension module) may run within the local file management tool environment of the first electronic device, and may be used to provide cross-device file access permissions. For example, the extension process (or extension module) may be implemented based on the FileProvider Extension class. The extension process (or extension module) may communicate with the operating system or file management process of the first electronic device to enable file management functions such as opening files on the second electronic device from the first electronic device, downloading files from the second electronic device to the local storage of the first electronic device, and sending files from the second electronic device to applications on the local storage of the first electronic device.

[0152] For example, Figure 11 is a timing diagram of data transmission between a first electronic device and a second electronic device in another embodiment. When the file management application of the first electronic device detects user actions such as downloading, copying, or sending files to the local device triggered by a target icon through the file management interface, the extended process can call the download interface of the download module. The download module can then start downloading the target file. This download module refers to the module in the file management application used to implement the download function. The download module can first determine whether a WebSocket connection has been established with the second electronic device. The download module can also create a download task. If a WebSocket connection has been established, it can initiate a WebSocket protocol download request to the second electronic device. This download request carries the first path information corresponding to the target file and the task identifier of the download task. After receiving the download request, the second electronic device can determine the target file corresponding to the first path information, create a corresponding data transmission channel, and then send an ACK to the first electronic device. After the download module of the first electronic device obtains the ACK, it can use the task identifier as the task_url of an HTTP:GET request and send an HTTP:GET request to the second electronic device. The second electronic device sends back the file data of the target file via an HTTP GET request. After receiving the file data, the download module can send the download path of the target file to the extension process. This download path can refer to the path where the target file is saved after being downloaded to the first electronic device. The extension process can then send back the target file based on this download path.

[0153] For example, Figure 12 is a timing diagram of data transmission between the first electronic device and the second electronic device in another embodiment. If the download module determines that a WebSocket connection has not yet been established with the second electronic device, it can initiate a connection to the second electronic device. The second electronic device starts a WebSocket server and sends the IP address and port number that the WebSocket server is listening on back to the first electronic device. The client of the first electronic device establishes a WebSocket connection with the WebSocket server of the second electronic device based on the IP address and port number, and then proceeds with subsequent processes such as sending download requests and file transfer.

[0154] In this embodiment of the application, a WebSocket connection can be established between the first electronic device and the second electronic device for communication. The connection process is simple and convenient, requiring minimal user intervention, which further improves the convenience of cross-device file management and enhances the user experience.

[0155] In this embodiment, the first electronic device can generate an operation request based on the first path information of the target file in the second electronic device and send the operation request to the second electronic device, so that the second electronic device can perform the processing corresponding to the management operation on the target file corresponding to the first path information according to the operation request, thereby improving the accuracy and convenience of cross-device file management.

[0156] In some embodiments, the file management application can provide functions such as downloading and saving files from a second electronic device to the local storage of a first electronic device, and sending files from the second electronic device to an application on the local storage of the first electronic device. For example, the target file can be sent to a third-party application by dragging and dropping the target icon onto the local storage of the first electronic device, or the target file can be copied to a third-party application by right-clicking the target icon. When implementing the function of sending files from the second electronic device to an application on the local storage of the first electronic device, the target file from the second electronic device must first be downloaded to the local storage of the first electronic device, and then the application on the local storage of the first electronic device must read the target file.

[0157] As shown in Figure 13, the steps for managing the target file corresponding to the target icon may include the following steps:

[0158] Step 1302: Obtain the second path information of the target file in the local file system.

[0159] The second path information may refer to the storage path of the target file in the local file system of the first electronic device. In some embodiments, the file management application may create a target directory locally on the first electronic device. This target directory can be used to store non-native files of the first electronic device, that is, the target directory can be used to store files of the second electronic device. For example, the target directory may be a directory under / Users / [username] / Library / CloudStorage / , but is not limited to this. When reading files in the target directory, the operating system or local file management tool of the first electronic device will send a callback to the file management application to trigger the file management application to download the corresponding files from the second electronic device.

[0160] After obtaining the file information corresponding to one or more files stored in the second electronic device, the first electronic device can generate the second path information corresponding to one or more files in the target directory of the local file system, and establish a mapping relationship between the second path information corresponding to each file and the corresponding first path information.

[0161] In one implementation, the first electronic device can obtain first path information of one or more files stored in the second electronic device, encode the first path information corresponding to each file to obtain second path information, and generate the second path information in the target directory.

[0162] As another implementation method, the first electronic device can also directly generate the second path information corresponding to each file stored by the second electronic device in the target directory, and then establish a mapping relationship between the second path information corresponding to the file and the corresponding first path information.

[0163] The first electronic device generates second path information in the target directory of the local file system, which maps the first path information to the corresponding first path information of each file. This facilitates subsequent path mapping and initiates cross-device file downloads, thereby improving the accuracy of cross-device file management.

[0164] In some embodiments, when the first electronic device displays icons corresponding to one or more files in the file management interface, it generates second path information corresponding to each file displayed in the file management interface in the target directory of the local file system.

[0165] When the first electronic device establishes a communication connection with the second electronic device, the file information obtained by the first electronic device may not be complete, for example, only information about some files stored on the second electronic device may be obtained. Therefore, when a user accesses files in a directory of the second electronic device through a file management application, the first electronic device can generate secondary path information for each file in the accessed directory of the second electronic device in the target directory of the first electronic device's local file system. When the file management application displays icons for one or more files in the file management interface, it can generate secondary path information for each file displayed in the file management interface in the target directory of the local file system. This ensures that each currently displayed file has corresponding secondary path information in the local file system, guaranteeing accurate acquisition of the secondary path information for the target file requiring management operations.

[0166] Step 1304: Map the second path information to the first path information of the target file in the second electronic device.

[0167] After obtaining the second path information corresponding to the target file, the first electronic device can map the second path information to the first path information of the target file in the second electronic device, and send an operation request to the second electronic device based on the first path information to download the target file from the second electronic device.

[0168] Step 1306: Generate an operation request based on the first path information and send the operation request to the second electronic device. The operation request is used to instruct the second electronic device to create a data transmission channel corresponding to the target file and return response information.

[0169] Step 1308: Receive response information sent by the second electronic device.

[0170] Step 1310: Send a data acquisition request to the second electronic device. The data acquisition request is used to instruct the second electronic device to transfer the file data of the target file to the first electronic device through the data transmission channel.

[0171] Step 1312: Receive the file data of the target file sent by the second electronic device.

[0172] The descriptions of steps 1306 to 1312 can be found in the relevant descriptions in the above embodiments, and will not be repeated here.

[0173] Step 1314: Save the file data to the second path information.

[0174] After receiving the file data of the target file sent by the second electronic device, the first electronic device can save the file data to the second path information. Then, the user can access the target file through the local file system of the first electronic device. The local application in the first electronic device can also read the file data of the target file from the second path information under the target directory, realizing a more flexible cross-device file management method.

[0175] In some embodiments, when the first electronic device creates second path information in the target directory of the local file system, it can create second path information corresponding to one or more files in the second electronic device in the target directory of the local file system, and generate placeholder files for each second path information. These placeholder files can be used to represent the future content of the second path information in the target directory of the local file system, but currently have no actual data to fill them.

[0176] After the first electronic device detects a trigger operation on the target icon of the file management application and obtains the second path information of the target file corresponding to the target icon in the local file system, it can determine whether the second path information is a placeholder file. If it is determined that the second path information is a placeholder file, it means that the target file corresponding to the second path information needs to be downloaded. The first electronic device can then map the second path information corresponding to the target file to the first path information of the target file in the second electronic device, and send an operation request to the second electronic device based on the first path information to download the target file from the second electronic device.

[0177] The first electronic device can receive the file data of the target file sent by the second electronic device and write the file data into a placeholder file under the second path information corresponding to the target file. Then, the placeholder file is updated to the target file so that it can be accessed by local applications or local file management tools of the first electronic device.

[0178] In one specific implementation, when a user selects to download a target file from a second electronic device to a location on the first electronic device using a file management application running on the first electronic device, the operating system of the first electronic device can obtain the second path information of the target file in the local file system and read the files under that second path information. If, during the process of reading the files under that second path information, the operating system of the first electronic device detects that the second path information is located in the target directory and determines that the files under that second path information are placeholder files, it can request the target file corresponding to the second path information from the directory provider of the target directory (i.e., the extension module in the file management application). The extension module in the file management application can map the second path information corresponding to the target file to the first path information corresponding to the target file and call the download interface of the download module to trigger the download module to download the target file from the second electronic device.

[0179] Optionally, the file data of the target file downloaded by the download module can be saved to the local sandbox path of the first electronic device. This local sandbox path can be a path under a directory accessible to the file management application during runtime, such as / Users / [username] / Library / Caches / , or the path of the application sandbox directory corresponding to the file management application. By setting sandbox directories for each application, the security and stability of the system can be improved. The download module can send the local sandbox path of the target file under the application sandbox directory corresponding to the file management application to the extension module (or extension process) in the file management application. The extension module can read the file data of the target file from this local sandbox path and then write the file data of the target file to a placeholder file under the second path information corresponding to the target file. After the file data is written, the operating system of the first electronic device can read the target file from the second path information.

[0180] In this embodiment, the file management application of the first electronic device can create a target directory in the local file system, and can create second path information corresponding to one or more files in the second electronic device in the target directory, and generate placeholder files under the second path information. When the operating system of the first electronic device reads the second path information in the target directory, it can trigger the file management application to download the corresponding files from the second electronic device and write them to the placeholder files under the corresponding second path information, so that the operating system of the first electronic device can accurately read the files in the second electronic device through the local file system, realizing the compatibility of cross-device file management and improving the convenience of cross-device file management.

[0181] In some embodiments, the cross-device file download method described above can be used to send a target file from a second electronic device to a local application on a first electronic device. If the file management application on the first electronic device detects a user's trigger operation on the target icon through the file management interface, such as copying the target file to a third-party application on the first electronic device by right-clicking the target icon, or dragging and dropping the target icon to a third-party application on the first electronic device, it can respond to the trigger operation on the target icon in the file management interface, generate an operation object based on the second path information of the target file in the local file system, and send the operation object to the local application, so that the local application sends a read request corresponding to the second path information. The first electronic device can respond to the read request and obtain the second path information of the target file in the local file system.

[0182] The file management application can respond to triggering events on target icons in the file management interface, obtain the second path information of the target file corresponding to the target icon under the local file system, and encapsulate the second path information into an operation object. This operation object may include, but is not limited to, drag-and-drop items (e.g., DragItem) and copy items. This operation object can be sent to a local application, thereby passing the second path information corresponding to the target file to the local application. The local application, upon detecting the triggering event (e.g., drag-and-drop, copy events), can attempt to read the second path information corresponding to the target file and can send a read request to the operating system of the first electronic device, thereby triggering the operating system of the first electronic device to read the file under the second path information.

[0183] Furthermore, the description of the operating system of the first electronic device reading the files under the second path information and thereby calling the file management application to download the target file from the second electronic device can be found in the relevant description in the above embodiments, and will not be repeated here.

[0184] For example, Figure 14 is a timing diagram of sending a file from a second electronic device to a third-party application on the local machine of a first electronic device in one embodiment. As shown in Figure 14, the file management application on the first electronic device can detect triggering operations on a target icon (such as dragging the target icon, right-clicking the target icon to copy, etc.) through the file management interface. It can encapsulate the second path information of the target file corresponding to the target icon under the local file system into an operation object (such as a drag item, a copy item, etc.). The first electronic device sends the operation object to the third-party application according to the user's operation. After receiving the operation object, the third-party application can attempt to read the second path information, triggering the operating system of the first electronic device or the local file management tool to read the file under the second path information. If it is determined that the file under the second path information is a placeholder file, it requests the file data of the target file from the extension process (or extension module) of the file management application.

[0185] The file management application's extension process can call the download module's download interface to download the target file's data. The file management application's download module can request the target file's data from a second electronic device, and the second electronic device can return the target file's data to the download module. Specifically, the method by which the download module downloads the target file's data from the second electronic device can be referred to the relevant descriptions in the above embodiments, and will not be repeated here. The download module can return the target file's data to the file management application's extension process, which then returns the file data to the third-party application.

[0186] Optionally, the download module can return the local sandbox path corresponding to the target file to the extension process. The extension process reads the file data of the target file from this local sandbox path and writes it to a placeholder file under the second path information. After writing is complete, the third-party application can successfully read the target file from the second path information.

[0187] In this embodiment of the application, the first electronic device implements the management operation of sending files from the second electronic device to the local application, providing more compatible file management functions. This allows the local application of the first electronic device to read cross-device files as if they were local files, improving the flexibility and convenience of cross-device file management.

[0188] In some embodiments, the file management application may also provide cross-device file upload functionality, enabling the uploading of files from a first electronic device to a second electronic device. The file management interface also includes an upload control that can be triggered (e.g., clicked) when a user needs to upload a file to the second electronic device. In response to the triggering of the upload control, the first electronic device can identify the file to be transferred and send the file to the second electronic device.

[0189] When the first electronic device detects a user's trigger operation on the upload control, it can display a file selection interface. This interface displays one or more files that can be uploaded to the second electronic device, such as files locally on the first electronic device and / or files in the cloud. The user can select the file to be transferred on the file selection interface, and the first electronic device can obtain the file to be transferred and send it to the second electronic device.

[0190] Optionally, if the file to be transferred is a file in the cloud, the first electronic device can first download the file from the cloud and then send the file to the second electronic device. Optionally, if the file to be transferred is a local file, the first electronic device can directly send the file to the second electronic device.

[0191] As an optional implementation, the first electronic device can first create an upload task and assign a task identifier to it. It can then send an upload request to the second electronic device based on the WebSocket protocol, carrying the task identifier. The second electronic device can create a data transmission channel based on the upload request and bind this channel to the task identifier. It can then return a response to the first electronic device. Upon receiving this response, the first electronic device can send a data push request based on the HTTP protocol. This data push request can carry the file to be transmitted and the task identifier; for example, the file to be transmitted and the task identifier can be encapsulated in the URL of an HTTP POST request, but is not limited to this. The second electronic device receives the target file uploaded by the first electronic device through the data transmission channel bound to the task identifier and saves the target file.

[0192] For example, Figure 15 is a schematic diagram of a file management interface in another embodiment. As shown in Figure 15, the file management interface 500 may also include an upload control 1502. Further, the functional area 720 may include the upload control 1502, and the recording component 740 may be located to the right of the recording component 740. The user can select a file to upload to the second electronic device by clicking the upload control 1502.

[0193] In this embodiment, the file management application can also realize cross-device file upload function, which enriches the cross-device file management function, meets the different needs of users, and improves the user experience.

[0194] In this embodiment, a cross-device file management solution combining Electron front-end, FileProvider back-end, and WebSocket and HTTP protocols is adopted. This solution provides users with a more aesthetically pleasing, comfortable, and convenient front-end interface, while also ensuring data transmission speed and meeting the requirements for the scope and freedom of cross-device file management operations, thereby improving the user experience.

[0195] As shown in Figure 16, in another embodiment, a cross-device file management method is provided, which can be applied to the aforementioned second electronic device. The method may include the following steps:

[0196] Step 1610: Send file information corresponding to one or more files stored in the second electronic device to the first electronic device, so that the first electronic device can display a file management interface based on the file information corresponding to the one or more files; the file management interface displays icons corresponding to one or more files, and the icons corresponding to the files are determined according to the file types corresponding to the files; the file management interface is used to provide management functions for the files stored in the second electronic device.

[0197] In some embodiments, the method further includes: receiving an operation request sent by a first electronic device; the operation request carrying first path information of a target file in a second electronic device; the target file being a file that needs to be managed; and, according to the operation request, performing processing corresponding to the management operation on the target file corresponding to the first path information.

[0198] In some embodiments, the step of processing the target file corresponding to the first path information according to the operation request includes: determining the target file corresponding to the first path information according to the operation request and creating a data transmission channel corresponding to the target file; sending response information to the first electronic device; receiving a data acquisition request sent by the first electronic device; and responding to the data acquisition request by transmitting the file data of the target file to the first electronic device through the data transmission channel.

[0199] In some embodiments, the operation request also carries a task identifier for the download task corresponding to the target file;

[0200] The steps include: determining the target file corresponding to the first path information based on the operation request, and creating a data transmission channel corresponding to the target file, including: determining the target file corresponding to the first path information based on the operation request, creating a data transmission channel corresponding to the target file, and binding the data transmission channel to the task identifier;

[0201] The step of responding to a data acquisition request and transmitting the target file data to the first electronic device through a data transmission channel includes: transmitting the target file data to the first electronic device through the data transmission channel corresponding to the task identifier carried in the data acquisition request.

[0202] In some embodiments, operation request and response information are transmitted based on the WebSocket protocol, while data acquisition requests and target file data are transmitted based on the HTTP protocol.

[0203] In some embodiments, the step of receiving an operation request sent by a first electronic device includes: receiving a request sent by the first electronic device; determining the request type corresponding to the request; and if the request type is an operation request, determining that an operation request sent by the first electronic device has been received.

[0204] In some embodiments, after determining the request type corresponding to the request in the step, the method further includes: if the request type is a connection request, then determining that a connection request sent by the first electronic device has been received; in response to the connection request, sending connection information to the first electronic device so that the first electronic device establishes a communication connection with the second electronic device according to the connection information.

[0205] It should be noted that the description of the cross-device file management method for the second electronic device provided in the embodiments of this application can be referred to the relevant description of the cross-device file management method for the first electronic device provided in the above embodiments, and will not be repeated here.

[0206] In this embodiment of the application, the second electronic device can send file information corresponding to one or more files stored in itself to the first electronic device. The first electronic device can display icons corresponding to the file types of the files stored in the second electronic device in the file management interface of the second electronic device. The icons can more intuitively reflect the file types, which can help users find the files that need to be managed more quickly, reduce the probability of misoperation, and improve the convenience and accuracy of users managing files across devices.

[0207] As shown in FIG17, in one embodiment, a cross-device file management device 1700 is provided, which can be applied to the first electronic device described above. The cross-device file management device 1700 may include an information acquisition module 1710, a display module 1720, and a management module 1730.

[0208] The information acquisition module 1710 is used to acquire file information corresponding to one or more files stored in the second electronic device.

[0209] The display module 1720 is used to display a file management interface based on the file information corresponding to one or more files. The file management interface displays icons corresponding to one or more files, and the icons corresponding to the files are determined according to the file types.

[0210] The management module 1730 is used to manage the target file corresponding to the target icon in response to the trigger operation of the target icon in the file management interface.

[0211] In one embodiment, the file management interface includes a file display area and a function area. The file display area is used to display icons corresponding to one or more files; the function area includes a search component. The cross-device file management device 1700 also includes a search module.

[0212] The search module is used to respond to search operations, retrieve the search content entered in the search component, and determine one or more files that match the search content based on the search content and the file information corresponding to one or more files.

[0213] The display module 1720 is also used to display icons corresponding to one or more matching files in the file display area.

[0214] In one embodiment, the file management interface further includes a file categorization area, which includes multiple categories, and these categories are divided in one or more of the following ways: according to the file type corresponding to the file; according to the application to which the file belongs; or according to the operation time of the file management operation.

[0215] In one embodiment, the functional area is located on the first side of the document display area, and the document categorization area is located on the second side of the document display area.

[0216] In one embodiment, the file management interface includes a recording component; the cross-device file management device 1700 also includes a recording viewing module.

[0217] The record viewing module is used to respond to the trigger operation of the record component and display one or more file management records in the file management interface. The file management records include operation information for managing files.

[0218] In one embodiment, the management operation includes one or more of the following: download operation, delete operation, edit operation, file open operation, copy operation, and sending the target file to the local application.

[0219] In one embodiment, the management module 1730 includes a path determination unit and a request unit.

[0220] The path determination unit is used to obtain the first path information of the target file in the second electronic device.

[0221] The request unit is used to generate an operation request based on the first path information and send the operation request to the second electronic device, so that the second electronic device performs processing corresponding to the management operation on the target file corresponding to the first path information according to the operation request.

[0222] In one embodiment, the requesting unit is further configured to generate an operation request based on the first path information and send the operation request to the second electronic device, the operation request being used to instruct the second electronic device to create a data transmission channel corresponding to the target file and return response information; receive the response information sent by the second electronic device; and send a data acquisition request to the second electronic device, the data acquisition request being used to instruct the second electronic device to transmit the file data of the target file to the first electronic device through the data transmission channel.

[0223] In one embodiment, the operation request also carries a task identifier for the download task corresponding to the target file. The operation request is used to instruct the second electronic device to create a data transmission channel corresponding to the target file and bind the data transmission channel to the task identifier.

[0224] The request unit is further configured to generate a data acquisition request based on the task identifier of the download task, and send the data acquisition request to the second electronic device. The data acquisition request is used to instruct the second electronic device to transfer the file data of the target file to the first electronic device through the data transmission channel corresponding to the task identifier.

[0225] In one embodiment, operation request and response information are transmitted based on the WebSocket protocol, while data acquisition requests and target file data are transmitted based on the HTTP protocol.

[0226] In one embodiment, the path determination unit is further configured to obtain second path information of the target file in the local file system and map the second path information to first path information of the target file in the second electronic device.

[0227] In one embodiment, the file information of the file includes the first path information of the file in the second electronic device; the cross-device file management device 1700 also includes a path creation module.

[0228] The path creation module is used to generate second path information for one or more files in the target directory of the local file system, and to establish a mapping relationship between the second path information and the corresponding first path information for each file.

[0229] In one embodiment, the path creation module is further configured to create second path information corresponding to one or more files in the target directory of the local file system, and generate placeholder files under each second path information; and to map the second path information corresponding to the target file to the first path information of the target file in the second electronic device if it is determined that the second path information corresponding to the target file is a placeholder file.

[0230] In one embodiment, the management module 1730 is further configured to receive file data of a target file sent by a second electronic device; and write the file data into a placeholder file under the second path information corresponding to the target file.

[0231] In one embodiment, the path creation module is further configured to generate second path information corresponding to each file displayed in the file management interface in the target directory of the local file system, when one or more icons corresponding to files are displayed in the file management interface.

[0232] In one embodiment, the management module 1730 further includes an object generation unit.

[0233] The object generation unit is used to respond to the trigger operation of the target icon in the file management interface, generate an operation object according to the second path information of the target file in the local file system, and send the operation object to the local application so that the local application can send a read request corresponding to the second path information.

[0234] The path determination unit is also used to obtain the second path information of the target file in the local file system in response to a read request.

[0235] In one embodiment, the file management interface further includes an upload control; the cross-device file management device 1700 also includes an upload module.

[0236] The upload module is used to respond to the trigger operation of the upload control, determine the file to be transferred, and send the file to be transferred to the second electronic device.

[0237] In this embodiment of the application, the first electronic device can display icons corresponding to the file types of the files stored in the second electronic device in the file management interface corresponding to the second electronic device. The icons can more intuitively reflect the file types, which can help users find the files that need to be managed more quickly, reduce the probability of misoperation, and improve the convenience and accuracy of users managing files across devices.

[0238] As shown in FIG18, in one embodiment, a cross-device file management device 1800 is provided, which can be applied to the second electronic device described above. The cross-device file management device 1800 includes an information sending module 1810.

[0239] The information sending module 1810 is used to send file information corresponding to one or more files stored in the second electronic device to the first electronic device, so that the first electronic device can display a file management interface based on the file information corresponding to the one or more files; the file management interface displays icons corresponding to one or more files, and the icons corresponding to the files are determined according to the file types corresponding to the files; the file management interface is used to provide management functions for the files stored in the second electronic device.

[0240] In one embodiment, the cross-device file management device 1800 further includes a request processing module.

[0241] The request processing module is used to receive an operation request sent by a first electronic device; the operation request carries first path information of a target file in a second electronic device; the target file is a file that needs to be managed; and is used to perform processing corresponding to the management operation on the target file corresponding to the first path information according to the operation request.

[0242] In one embodiment, the request processing module includes a channel creation unit, a response sending unit, a request receiving unit, and a transmission unit.

[0243] The channel creation unit is used to determine the target file corresponding to the first path information according to the operation request, and to create a data transmission channel corresponding to the target file.

[0244] The response sending unit is used to send response information to the first electronic device.

[0245] The request receiving unit is used to receive data acquisition requests sent by the first electronic device.

[0246] The transmission unit is used to respond to data acquisition requests and transmit the file data of the target file to the first electronic device through the data transmission channel.

[0247] In one embodiment, the operation request also carries a task identifier for the download task corresponding to the target file; the channel creation unit is further configured to determine the target file corresponding to the first path information according to the operation request, create a data transmission channel corresponding to the target file, and bind the data transmission channel to the task identifier.

[0248] The transmission unit is also used to transmit the file data of the target file to the first electronic device through the data transmission channel corresponding to the task identifier carried in the data acquisition request.

[0249] In one embodiment, operation request and response information are transmitted based on the WebSocket protocol, while data acquisition requests and target file data are transmitted based on the HTTP protocol.

[0250] In one embodiment, the request processing module is further configured to receive a request sent by the first electronic device; determine the request type corresponding to the request; and if the request type is an operation request, determine that an operation request sent by the first electronic device has been received.

[0251] In one embodiment, the request processing module is further configured to determine, if the request type is a connection request, that a connection request sent by the first electronic device has been received; and in response to the connection request, send connection information to the first electronic device so that the first electronic device establishes a communication connection with the second electronic device based on the connection information.

[0252] In this embodiment of the application, the second electronic device can send file information corresponding to one or more files stored in itself to the first electronic device. The first electronic device can display icons corresponding to the file types of the files stored in the second electronic device in the file management interface of the second electronic device. The icons can more intuitively reflect the file types, which can help users find the files that need to be managed more quickly, reduce the probability of misoperation, and improve the convenience and accuracy of users managing files across devices.

[0253] Figure 19 is a structural block diagram of an electronic device in one embodiment. As shown in Figure 19, the electronic device 1900 may include one or more of the following components: a processor 1910, a memory 1920 coupled to the processor 1910, and a transceiver unit, wherein the memory 1920 may store one or more computer programs, and the one or more computer programs may be configured to, when executed by one or more processors 1910, enable the electronic device 1900 to implement the cross-device file management method applied to the first electronic device as described in the above embodiments.

[0254] Processor 1910 may include one or more processing cores. Processor 1910 connects to various parts within the electronic device 1900 using various interfaces and lines, and performs various functions and processes data of the electronic device 1900 by running or executing instructions, programs, code sets, or instruction sets stored in memory 1920, and by calling data stored in memory 1920. Optionally, processor 1910 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). Processor 1910 may integrate one or a combination of several of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the modem may also not be integrated into processor 1910 and may be implemented separately through a communication chip.

[0255] The memory 1920 may include random access memory (RAM) or read-only memory (ROM). The memory 1920 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 1920 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as touch functionality, sound playback functionality, image playback functionality, etc.), and instructions for implementing the various method embodiments described above. The data storage area may also store data created by the electronic device 1900 during use.

[0256] The transceiver unit may include, but is not limited to, Bluetooth modules, Wi-Fi modules, etc., and can be used to provide communication functions.

[0257] This application discloses an electronic device including a memory, a processor, and a transceiver unit. The memory stores a computer program, which, when executed by the processor, enables the electronic device to implement the cross-device file management method for a second electronic device as described in the above embodiments.

[0258] This application discloses a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor in an electronic device, the electronic device implements the cross-device file management method applied to a first electronic device as described in the above embodiments.

[0259] This application discloses a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor in an electronic device, the electronic device implements the cross-device file management method for a second electronic device as described in the above embodiments.

[0260] This application discloses a computer program product, which includes a computer program. When the computer program is executed by a processor in an electronic device, it enables the electronic device to implement the cross-device file management method applied to a first electronic device as described in the above embodiments.

[0261] This application discloses a computer program product, which includes a computer program. When the computer program is executed by a processor in an electronic device, it enables the electronic device to implement the cross-device file management method for a second electronic device as described in the above embodiments.

[0262] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, ROM, etc.

[0263] Any references to memory, storage, databases, or other media used herein may include non-volatile and / or volatile memory. Suitable non-volatile memory may include ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which is used as an external cache memory. By way of illustration and not limitation, RAM may take many forms, such as Static RAM (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus DRAM (RDRAM), and Direct Rambus DRAM (DRDRAM).

[0264] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application. In the various embodiments of this application, it should be understood that the sequence number of the above processes does not imply a necessary order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0265] The foregoing has provided a detailed description of a cross-device file management method, apparatus, electronic device, and program product disclosed in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and its core ideas. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A file management method across devices, characterized by, Applied to a first electronic device, wherein the first electronic device establishes a communication connection with a second electronic device, the method includes: Obtain file information corresponding to one or more files stored in the second electronic device; Based on the file information corresponding to the one or more files, a file management interface is displayed; the file management interface displays one or more icons corresponding to the files, and the icons corresponding to the files are determined according to the file types corresponding to the files; In response to a trigger operation on a target icon in the file management interface, management operations are performed on the target file corresponding to the target icon.

2. The method of claim 1, wherein, The file management interface includes a file display area and a function area. The file display area is used to display icons corresponding to one or more of the files. The functional area includes a search component; the method further includes: In response to a search operation, retrieve the search content entered in the search component; Based on the search content and the file information corresponding to the one or more files, determine one or more files that match the search content; The file display area displays icons corresponding to one or more of the matched files.

3. The method of claim 2, wherein, The file management interface also includes a file categorization area, which includes multiple categories, and the multiple categories are divided according to one or more of the following methods: Divided according to the file type corresponding to the file; Files are categorized according to the application they belong to; Divided according to the time of operation for managing files.

4. The method of claim 3, wherein, The functional area is located on the first side of the file display area, and the file categorization area is located on the second side of the file display area.

5. The method of claim 1, wherein, The file management interface includes a recording component; the method further includes: In response to a trigger operation on the recording component, one or more file management records are displayed in the file management interface, the file management records including operation information for managing files.

6. The method according to any one of claims 1 to 5, characterized in that, The management operations include one or more of the following: download, delete, edit, open file, copy, and sending the target file to the local application.

7. The method of claim 1, wherein, The management operation for the target file corresponding to the target icon includes: Obtain the first path information of the target file in the second electronic device; An operation request is generated based on the first path information, and the operation request is sent to the second electronic device so that the second electronic device performs the processing corresponding to the management operation on the target file corresponding to the first path information according to the operation request.

8. The method of claim 7, wherein, The step of generating an operation request based on the first path information and sending the operation request to the second electronic device, so that the second electronic device performs processing on the target file corresponding to the management operation according to the operation request, includes: An operation request is generated based on the first path information and sent to the second electronic device. The operation request is used to instruct the second electronic device to create a data transmission channel corresponding to the target file and return response information. Receive the response information sent by the second electronic device; A data acquisition request is sent to the second electronic device, the data acquisition request being used to instruct the second electronic device to transfer the file data of the target file to the first electronic device through the data transmission channel.

9. The method of claim 8, wherein, The operation request also carries a task identifier for the download task corresponding to the target file. The operation request is used to instruct the second electronic device to create a data transmission channel corresponding to the target file and bind the data transmission channel to the task identifier. Sending a data acquisition request to the second electronic device includes: A data acquisition request is generated based on the task identifier of the download task, and the data acquisition request is sent to the second electronic device. The data acquisition request is used to instruct the second electronic device to transfer the file data of the target file to the first electronic device through the data transmission channel corresponding to the task identifier.

10. The method according to claim 8 or 9, characterized in that, The operation request and the response information are transmitted based on the WebSocket protocol, while the data acquisition request and the file data of the target file are transmitted based on the Hypertext Transfer Protocol (HTTP).

11. The method according to claim 8 or 9, characterized in that, The step of obtaining the first path information of the target file in the second electronic device includes: Obtain the second path information of the target file in the local file system; The second path information is mapped to the first path information of the target file in the second electronic device.

12. The method of claim 11, wherein, The file information of the file includes the first path information of the file in the second electronic device; before obtaining the second path information of the target file in the local file system, the method further includes: In the target directory of the local file system, generate second path information corresponding to one or more of the files, and establish a mapping relationship between the second path information corresponding to each file and the corresponding first path information.

13. The method of claim 12, wherein, The step of generating second path information corresponding to one or more of the files in the target directory of the local file system includes: In the target directory of the local file system, create one or more second path information corresponding to the file, and generate placeholder files under each of the second path information; The step of mapping the second path information to the first path information of the target file in the second electronic device includes: If the second path information corresponding to the target file is determined to be a placeholder file, then the second path information corresponding to the target file is mapped to the first path information of the target file in the second electronic device.

14. The method of claim 13, wherein, The method further includes: Receive file data of the target file sent by the second electronic device; Write the file data into a placeholder file under the second path information corresponding to the target file.

15. The method according to any one of claims 12 to 14, characterized in that, In the target directory of the local file system, generate second path information corresponding to one or more of the aforementioned files, including: When one or more icons corresponding to the files are displayed in the file management interface, second path information corresponding to each file displayed in the file management interface is generated in the target directory of the local file system.

16. The method of claim 11, wherein, The management operation includes sending the target file to a local application; the management operation on the target file corresponding to the target icon in response to a trigger operation on the target icon in the file management interface further includes: In response to a trigger operation on a target icon in the file management interface, an operation object is generated based on the second path information of the target file in the local file system, and the operation object is sent to the local application so that the local application sends a read request corresponding to the second path information. The step of obtaining the second path information of the target file in the local file system includes: In response to the read request, the second path information of the target file in the local file system is obtained.

17. The method according to any one of claims 1 to 5, characterized in that, The file management interface also includes an upload control; the method further includes: In response to the triggering operation of the upload control, the file to be transmitted is determined and the file to be transmitted is sent to the second electronic device.

18. A file management method across devices, characterized by, Applied to a second electronic device, the second electronic device establishing a communication connection with a first electronic device, the method includes: The first electronic device sends file information corresponding to one or more files stored in the second electronic device, so that the first electronic device displays a file management interface based on the file information corresponding to the one or more files; the file management interface displays one or more icons corresponding to the files, and the icons corresponding to the files are determined according to the file types corresponding to the files; the file management interface is used to provide management functions for the files stored in the second electronic device.

19. The method of claim 18, wherein, The method further includes: The system receives an operation request sent by the first electronic device; the operation request carries the first path information of the target file in the second electronic device; the target file is a file that needs to be managed. Based on the operation request, the target file corresponding to the first path information is processed in accordance with the management operation.

20. The method of claim 19, wherein, The step of performing the management operation on the target file corresponding to the first path information according to the operation request includes: Based on the operation request, determine the target file corresponding to the first path information, and create a data transmission channel corresponding to the target file; Send response information to the first electronic device; Receive the data acquisition request sent by the first electronic device; In response to the data acquisition request, the file data of the target file is transmitted to the first electronic device through the data transmission channel.

21. The method of claim 20, wherein, The operation request also carries the task identifier of the download task corresponding to the target file; The step of determining the target file corresponding to the first path information according to the operation request and creating a data transmission channel corresponding to the target file includes: Based on the operation request, determine the target file corresponding to the first path information, create a data transmission channel corresponding to the target file, and bind the data transmission channel to the task identifier; The step of responding to the data acquisition request by transmitting the file data of the target file to the first electronic device through the data transmission channel includes: Based on the task identifier carried in the data acquisition request, the file data of the target file is transmitted to the first electronic device through the data transmission channel corresponding to the task identifier.

22. The method of claim 20 or 21, wherein, The operation request and the response information are transmitted based on the WebSocket protocol, while the data acquisition request and the file data of the target file are transmitted based on the Hypertext Transfer Protocol (HTTP).

23. The method according to any one of claims 19 to 21, characterized in that, The step of receiving the operation request sent by the first electronic device includes: Receive the request sent by the first electronic device; Determine the request type corresponding to the request. If the request type is an operation request, then determine that an operation request sent by the first electronic device has been received.

24. The method of claim 23, wherein, After determining the request type corresponding to the request, the method further includes: If the request type is a connection request, then it is determined that a connection request sent by the first electronic device has been received; In response to the connection request, connection information is sent to the first electronic device so that the first electronic device can establish a communication connection with the second electronic device based on the connection information.

25. An apparatus for managing files across devices, the apparatus comprising: The device is applied to a first electronic device, which establishes a communication connection with a second electronic device, and includes: The information acquisition module is used to acquire file information corresponding to one or more files stored in the second electronic device; The display module is used to display a file management interface based on the file information corresponding to the one or more files; the file management interface displays one or more icons corresponding to the files, and the icons corresponding to the files are determined according to the file types corresponding to the files; The management module is used to perform management operations on the target file corresponding to the target icon in response to the trigger operation of the target icon in the file management interface.

26. An apparatus for managing files across devices, the apparatus comprising: The device is applied to a second electronic device, which establishes a communication connection with the first electronic device, and includes: The information sending module is used to send file information corresponding to one or more files stored in the second electronic device to the first electronic device, so that the first electronic device can display a file management interface based on the file information corresponding to the one or more files; the file management interface displays one or more icons corresponding to the files, and the icons corresponding to the files are determined according to the file types corresponding to the files; the file management interface is used to provide management functions for the files stored in the second electronic device.

27. An electronic device, comprising: The device includes a memory and a processor, and a transceiver unit. The memory stores a computer program, which, when executed by the processor, causes the electronic device to perform the method as described in any one of claims 1 to 17 or 18 to 24.

28. A computer program product, characterised in that, The method includes a computer program, and when the computer program is executed by a processor in an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1 to 17 or 18 to 24.

Images