A file sharing method and related apparatus

Abstract

This application provides a file sharing method and related apparatus, relating to the field of terminal technology. The method includes: creating a first sharing task in response to a first user operation; acquiring the task status and / or sending progress of the first sharing task; and displaying the task status and / or sending progress of the first sharing task in a first quick sharing window and the main window of a sharing application. Based on the above method, the sharing task generated using quick sharing is simultaneously displayed in the main window and the quick sharing window, allowing the user to view the task status and / or sending progress of the sharing task in both windows. This facilitates the user's understanding of the overall status of the electronic device's current sharing task directly from the main window of the sharing application, enabling adjustments to the sharing task within the application and thus providing a better user experience.

Description

[0001] This application is a divisional application. The original application has the application number 202210521952.2 and the original application date is May 13, 2022. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal technology, and more specifically, to a file sharing method and related apparatus. Background Technology

[0003] In today's internet age, many users own more than one electronic device, such as smartphones, tablets, and personal computers. In their daily use, users often encounter scenarios like sharing files from their personal computers with other electronic devices.

[0004] There are two ways to share files: using a sharing application and quick sharing. Using a sharing application involves opening the application's main window on your computer, such as the file sharing window in "PC Manager" (an example of a sharing application), and then dragging the file icon you want to share onto the corresponding network device icon in the main window. This method is more complex and involves more steps. Quick sharing, on the other hand, involves right-clicking the file icon you want to share on your computer and selecting "Quick Share" from the pop-up options. This method is simpler and involves fewer steps.

[0005] However, after sharing files using the quick share method, the status of the sharing task using quick share is not visible in the main window. In other words, the sharing task status is not synchronized when using the sharing application and quick share, leading to a poor user experience. For example, users may not be able to directly understand the overall status of the electronic device's sharing tasks, making adjustments difficult; for instance, quick share tasks cannot be canceled in the sharing application's main window. Therefore, we hope to provide a method to synchronize the quick share task status to the sharing application for a better user experience. Summary of the Invention

[0006] This application provides a file sharing method and related apparatus for use in electronic devices, with the aim of synchronizing the task status of quick sharing to the sharing application to provide a better user experience.

[0007] In a first aspect, this application provides a file sharing method applied to an electronic device. The method includes: creating a first sharing task in response to a first user operation; the first user operation is an operation of selecting a first device to be shared in a first quick sharing window corresponding to a first file set, and the first sharing task is used to share files in the first file set to the first device; wherein, the first quick sharing window is a window generated in response to the user's quick sharing operation on the first file set, the first file set includes one or more files, the quick sharing operation is an operation of sharing a file by clicking on it, and the quick sharing operation is not performed in the main window of a sharing application, the sharing application being an application used for sharing files; obtaining the task status and / or sending progress of the first sharing task, the task status including: waiting to send, sending, or sending completed; and displaying the task status and / or sending progress of the first sharing task in the first quick sharing window and the main window of the sharing application.

[0008] Quick Share is a file sharing method that allows sharing without using a sharing application. Quick Share allows you to share files simply by clicking on one or more files, without having to operate within the main window of the sharing application. Therefore, it is more convenient than traditional methods.

[0009] Based on the above method, the sharing task generated using the quick share method is displayed synchronously in the main window and the quick share window, allowing users to view the task status and / or sending progress of the sharing task in both the main window and the quick share window. This makes it easier for users to understand the overall status of the current sharing task of the electronic device directly from the main window of the sharing application, and to make adjustments to the sharing task in the sharing application, such as canceling a quick share task, etc., thus providing users with a better user experience.

[0010] In conjunction with the first aspect, in some possible implementations of the first aspect, creating the first sharing task in response to a first user operation includes: in response to the first user operation, obtaining task information, which includes the filenames and storage paths of each file in the first file set, and the device identifier of the first device; and creating the first sharing task based on the task information through a sharing application.

[0011] In other words, the creation of a sharing task occurs based on the selection of a device. One or more sharing tasks can be created for a single device. After the user selects the first device to share with, task information is obtained. Based on this task information, the electronic device can read the file from the corresponding storage path and send the file to the first device.

[0012] In conjunction with the first aspect, in some possible implementations of the first aspect, the task information also includes a first task identifier, which is generated in response to a first user operation. The first task identifier is used to identify the first sharing task and corresponds to the first quick sharing window.

[0013] Since users may perform multiple quick share operations, different task identifiers can be used to distinguish different sharing tasks, with each task corresponding to a unique identifier. Furthermore, to differentiate the quick share windows corresponding to different sharing tasks, a mapping can be established between task identifiers and quick share windows. It should be understood that the mapping between task identifiers and quick share windows is the same as the mapping between sharing tasks and quick share windows. In practice, this mapping can be maintained by a quick share window service. By maintaining this mapping, electronic devices can associate different sharing tasks with different quick share windows.

[0014] It should also be understood that a quick share window can correspond to one share task or multiple share tasks.

[0015] In conjunction with the first aspect, in some possible implementations of the first aspect, the method further includes: determining, based on the first task identifier, a corresponding first quick sharing window for displaying the task status and / or sending progress of the first sharing task.

[0016] After obtaining the task status and / or sending progress of the first sharing task, the electronic device can determine to update the task status and / or sending progress of the first sharing task in the corresponding quick sharing window based on the first task identifier. In this way, multiple quick sharing windows can be displayed on the interface simultaneously, and the corresponding quick sharing window can be updated according to the task status and / or sending progress of any sharing task.

[0017] In conjunction with the first aspect, in some possible implementations of the first aspect, the first task identifier corresponds to the first quick sharing window, including: the first task identifier corresponds to the window identifier of the first quick sharing window; before obtaining task information in response to a first user operation, the method further includes: in response to a second user operation, displaying the first quick sharing window, the second user operation being a quick sharing operation of the first file set, the first quick sharing window displaying one or more devices including a first device, the one or more devices being devices having a communication connection with an electronic device; and assigning a window identifier to the first quick sharing window.

[0018] Different window identifiers can be used to identify different quick share windows. An electronic device can maintain a list of windows containing the window identifiers of one or more quick share windows. In a specific implementation, this window list can be maintained by a quick share window service.

[0019] Since window identifiers can be used to identify quick share windows, one possible form of the correspondence between the first sharing task and the first quick share window could be a correspondence between the first task identifier and the window identifier of the first quick share window.

[0020] Furthermore, for an electronic device, the device list displayed in different quick share windows can be consistent. In other words, the electronic device can maintain a device list that includes devices with which it has a communication connection, such as identifiers of the devices with which it has a communication connection. In a specific implementation, this device list can be maintained by a quick share window service.

[0021] In conjunction with the first aspect, in some possible implementations of the first aspect, the method further includes: activating a first quick share window in response to a third user operation, the third user operation being another quick share operation on the first file set following the first user operation; creating a second share task in response to a fourth user operation, the fourth user operation being an operation of selecting a second device to be shared in the first quick share window, the second share task being used to share the first file set to the second device; updating the first quick share window, the updated first quick share window displaying the task status and / or sending progress of the first share task, and the task status and / or sending progress of the second share task.

[0022] Therefore, the first quick share window can be activated in response to user actions and can be repeatedly used. This eliminates the need for users to wait for a quick share to complete before performing another quick share on the same set of files. Thus, users can quickly share files one or more times as needed, resulting in a better user experience.

[0023] In conjunction with the first aspect, in some possible implementations of the first aspect, the method further includes: in response to a fourth user operation, generating a second task identifier, the second task identifier being used to identify a second sharing task, the second task identifier also corresponding to the first quick share window.

[0024] In other words, one quick share window can correspond to multiple share tasks.

[0025] Since the first and second sharing tasks involve sharing the same set of files, they can be displayed in a single quick sharing window. This avoids displaying too many windows on the interface, which can be confusing for users and makes the process more convenient.

[0026] In conjunction with the first aspect, in some possible implementations of the first aspect, the method further includes: in response to a fifth user operation, displaying a second quick share window corresponding to the second file set, the fifth user operation being a quick share operation on the second file set, the second file set being a different file set from the first file set, the first quick share window and the second quick share window being different windows, and both the first quick share window and the second quick share window being able to be activated in response to the user's operation.

[0027] Therefore, users can quickly share one set of files while simultaneously sharing another set of files, and can freely switch between the two quick sharing windows as needed to perform other operations, resulting in a better user experience.

[0028] In conjunction with the first aspect, in some possible implementations of the first aspect, the areas occupied by the first quick share window and the second quick share window in the user interface do not completely overlap.

[0029] By displaying the first and second quick share windows in different areas of the user interface, users can easily see different quick share windows and then activate the window that needs to be operated on according to their needs.

[0030] Secondly, this application provides a file sharing device, which includes modules for performing the first aspect and any possible implementation thereof.

[0031] Thirdly, this application provides a file sharing device, including a memory and a processor, wherein the memory is used to store a computer program and the processor is used to execute the computer program to perform the first aspect and any possible implementation thereof.

[0032] Fourthly, an electronic device is provided, comprising a processor and a memory for storing a computer program, the processor for invoking the computer program in the memory to perform a method as described in the first aspect and any possible implementation thereof.

[0033] Fifthly, a chip is provided, the chip including a processor for invoking a computer program in memory to perform methods as described in the first aspect and any possible implementation thereof.

[0034] In a sixth aspect, this application provides a computer-readable storage medium including a computer program that, when run on a computer, causes an electronic device to perform the methods of the first aspect and any possible implementation thereof.

[0035] In a seventh aspect, this application provides a computer program product, including a computer program that, when run on a computer, causes an electronic device to perform the methods of the first aspect and any possible implementation thereof.

[0036] It should be understood that the second to seventh aspects of this application correspond to the technical solutions of the first aspect of this application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

[0037] Figure 1 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application;

[0038] Figure 2 This is a schematic diagram of the main window sharing interface provided in an embodiment of this application;

[0039] Figure 3 This is a schematic diagram of the quick sharing interface provided in the embodiments of this application;

[0040] Figure 4 This is a schematic flowchart of the file sharing method provided in the embodiments of this application;

[0041] Figure 5 This is a schematic diagram illustrating the interaction process between various modules in the file sharing method provided in the embodiments of this application;

[0042] Figure 6 A schematic diagram of the interface for the file sharing method provided in this application embodiment;

[0043] Figure 7 A schematic flowchart illustrating the first operation of the file sharing method provided in this application embodiment;

[0044] Figure 8 A schematic diagram of the interface for the first operation of the file sharing method provided in the embodiments of this application;

[0045] Figure 9 A schematic diagram of the interface for a second operation of the file sharing method provided in this application embodiment;

[0046] Figure 10 This is a schematic diagram of the hardware structure of a file sharing device provided in an embodiment of this application. Detailed Implementation

[0047] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and purpose. For example, "first chip" and "second chip" are used only to distinguish different chips and do not limit their order. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" do not necessarily imply that they are different.

[0048] It should be noted that, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0049] In this application embodiment, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0050] The file sharing method provided in this application can be applied to electronic devices with display and file transfer functions. These electronic devices can be mobile phones, smart TVs, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and so on. The embodiments of this application do not limit the specific technology or form of the electronic device used.

[0051] To better understand the embodiments of this application, the structure of the electronic device provided in the embodiments of this application is described below:

[0052] Figure 1 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application.

[0053] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0054] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0055] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0056] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0057] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

[0059] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C buses. The processor 110 can couple to the touch sensor 180K, charger, flash, camera 193, etc., through different I2C bus interfaces. For example, the processor 110 can couple to the touch sensor 180K through the I2C interface, enabling the processor 110 and the touch sensor 180K to communicate through the I2C bus interface, thereby realizing the touch function of the electronic device 100.

[0060] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to enable the function of answering phone calls through a Bluetooth headset.

[0061] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via the PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering phone calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0062] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface to enable music playback through Bluetooth headphones.

[0063] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to enable the electronic device 100 to capture images. The processor 110 and the display screen 194 communicate via the DSI interface to enable the electronic device 100 to display images.

[0064] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to a camera 193, a display screen 194, a wireless communication module 160, an audio module 170, a sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0065] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0066] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0067] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0068] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, display screen 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0069] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0070] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0071] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0072] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0073] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0074] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0075] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0076] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0077] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0078] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0079] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0080] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0081] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0082] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs can enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0083] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0084] Internal memory 121 can be used to store computer executable program code, which includes instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 110 executes various functional applications and data processing of electronic device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory located in the processor.

[0085] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0086] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0087] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or make hands-free calls through the speaker 170A.

[0088] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a telephone call or voice message, the receiver 170B can be brought close to the ear to listen to the voice.

[0089] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Electronic device 100 may have at least one microphone 170C. In some embodiments, electronic device 100 may have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic device 100 may also have three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0090] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0091] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the intensity of the touch operation based on pressure sensor 180A. Electronic device 100 can also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0092] The gyroscope sensor 180B can be used to determine the motion attitude of the electronic device 100. In some embodiments, the gyroscope sensor 180B can determine the angular velocity of the electronic device 100 about three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the shake of the electronic device 100, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the electronic device 100 by moving in the opposite direction, thus achieving image stabilization. The gyroscope sensor 180B can also be used in navigation and motion-sensing game scenarios.

[0093] The barometric pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates altitude using the air pressure value measured by the barometric pressure sensor 180C to assist in positioning and navigation.

[0094] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip cover. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover using the magnetic sensor 180D. Then, based on the detected opening and closing state of the cover or the flip cover, features such as automatic flip unlocking can be set.

[0095] The 180E accelerometer can detect the magnitude of acceleration of electronic device 100 in various directions (typically three axes). When electronic device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of electronic devices and applied to applications such as screen orientation switching and pedometers.

[0096] A distance sensor 180F is used to measure distance. Electronic device 100 can measure distance via infrared or laser. In some embodiments, during a shooting scene, electronic device 100 can utilize the distance sensor 180F to measure distance for rapid focusing.

[0097] The proximity sensor 180G may include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The LED may be an infrared LED. The electronic device 100 emits infrared light outward through the LED. The electronic device 100 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 may use the proximity sensor 180G to detect when a user holds the electronic device 100 close to their ear for a call, so as to automatically turn off the screen to save power. The proximity sensor 180G can also be used in holster mode and pocket mode for automatic unlocking and locking of the screen.

[0098] The ambient light sensor 180L is used to sense the brightness of ambient light. The electronic device 100 can adaptively adjust the brightness of the display screen 194 based on the sensed ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also work with the proximity sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

[0099] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can utilize the characteristics of the collected fingerprints to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering calls with fingerprints, etc.

[0100] Temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 uses the temperature detected by temperature sensor 180J to execute a temperature handling strategy. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs thermal protection by reducing the performance of a processor located near temperature sensor 180J to reduce power consumption. In other embodiments, when the temperature is below another threshold, electronic device 100 heats battery 142 to prevent abnormal shutdown of electronic device 100 due to low temperature. In still other embodiments, when the temperature is below yet another threshold, electronic device 100 boosts the output voltage of battery 142 to prevent abnormal shutdown due to low temperature.

[0101] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0102] The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire vibration signals from the vibrating bone segments of the human vocal cords. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure signals. In some embodiments, the bone conduction sensor 180M can also be incorporated into headphones to form bone conduction headphones. The audio module 170 can parse the voice signals from the vibrating bone segments of the vocal cords acquired by the bone conduction sensor 180M to realize voice functionality. The application processor can parse heart rate information from the blood pressure signals acquired by the bone conduction sensor 180M to realize heart rate detection functionality.

[0103] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0104] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0105] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0106] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0107] To facilitate understanding, let's first briefly explain some of the terms used below. Sharing application: An application that can be used to share files, such as a PC manager. To share files using a sharing application, open the application and share files by dragging and dropping them in its main window.

[0108] Quick Share: File sharing can be achieved without using a sharing application. Quick Share is still a form of sharing, but because the operation of sharing differs from that of sharing using a sharing application, it is named differently. It should be understood that Quick Share is just one possible name, and other names such as Quick Drop, AirDrop, and AirShare are also possible. This application does not preclude the possibility of giving Quick Share other names to express the same or similar meaning.

[0109] Quick Share: This allows you to share files by clicking on one or more files. For example, you could select one or more files, right-click, and choose "Quick Share." Quick Share doesn't require interaction within the main window of the sharing application. Therefore, it's a different method from sharing within the application itself.

[0110] Sharing task: A task that shares a target file with a target device is called a sharing task. The target file is the file or set of files to be shared in this sharing task, and the target device is the device that receives the target file in this sharing task.

[0111] In this embodiment of the application, a sharing task can be established in response to the operation of sharing a set of files to a target device. The set of files can be one or more files selected by the user before performing a quick share operation.

[0112] Additionally, it should be noted that the following text, along with several accompanying figures, illustrates the interfaces of the main sharing application window and the quick sharing window. The sharing application window can be found in [reference needed]. Figure 2 and Figure 6 The quick share window can be found in the "PC Manager" window. Figure 3 , Figure 6 , Figure 8 and Figure 9 The accompanying drawings illustrate the "Quick Share" window. However, it should be understood that these drawings are merely examples and should not be construed as limiting this application. On different devices, the main window and / or quick share window of the sharing application may have different designs. In response to user actions, the displayed window may include the content shown in the drawings, or it may contain more or less content than the interface shown in the drawings below. This application does not impose any limitations on this.

[0113] The following is a combination of... Figure 2 and Figure 3 The two methods of file sharing will be introduced separately.

[0114] Figure 2 This is a schematic diagram of the interface for performing a sharing operation in the main window of a sharing application, provided in an embodiment of this application. Figure 2 The sharing application shown is "PC Manager".

[0115] like Figure 2 As shown in (a), use the mouse to drag the icon of the file you want to share, such as the icon of file 1, to the main window for file sharing in "PC Manager". Then drag the icon to the icon of the target device, such as device 1.

[0116] like Figure 2 As shown in (b), a progress circle indicating the sharing progress appears next to the icon of device 1. When the progress circle completes one full rotation around the icon of device 1, it means that the sharing of file 1 to device 1 is complete.

[0117] like Figure 2 As shown in (c), clicking the icon of Device 1 in the main window will bring up a pop-up window above the Device 1 icon, displaying the current task status of the file sharing task of sending file 1 to Device 1. The pop-up window shows the icon of file 1, the name of file 1, the current sharing progress, and a progress bar. To the right of the progress bar is a "Cancel" button; clicking the "Cancel" button will cancel the file sharing task of sending file 1 to Device 1.

[0118] Figure 3 This is a schematic diagram of the interface for quick sharing provided in the embodiments of this application.

[0119] like Figure 3As shown in (a), right-click the icon of the file you want to share on your computer desktop, for example, file 1.

[0120] like Figure 3 As shown in (b), the pop-up options bar includes multiple operations, such as "Open," "Print," and "Quick Share" as shown in the figure, as well as "Copy," "Cut," and other possible operation options not shown in the figure. Users can quickly share file 1 by clicking "Quick Share."

[0121] like Figure 3 As shown in (c), in the pop-up quick share window, you can see the icon, name and some brief information of the file to be shared, and on the right is a list of devices that can be shared.

[0122] like Figure 3 As shown in (d), users can select the target device they wish to share with from the device list, for example, the target device is device 1 as shown in the figure.

[0123] like Figure 3 As shown in (e), the device list in the quick share window for file 1 displays a sharing task in progress, sending file 1 to device 1. Below the name of device 1 is a progress bar for this sharing task, and to the right of the progress bar is a "..." "This is the cancel button. Clicking this cancel button will cancel the task of sharing file 1 to device 1."

[0124] Currently, both of the above methods can be used to share file 1 to device 1. However, after sharing a file using the quick share method, the task status and / or sending progress cannot be viewed in the main window. In other words, the sharing task status is not synchronized when using the sharing application and the quick share method, resulting in a poor user experience. For example, users may not be able to directly understand the overall status of the sharing task on the electronic device, making it inconvenient for them to make adjustments. For instance, the quick share task cannot be canceled in the main window of the sharing application, etc. Therefore, we hope to provide a method that can synchronize the task status of quick share to the sharing application to provide a better user experience.

[0125] In view of this, this application provides a file sharing method that synchronously displays the sharing task generated using the quick share method in the main window and the quick share window, so that users can view the task status and / or sending progress of the task in either the main window or the quick share window, thus providing users with a better user experience.

[0126] Figure 4This is a schematic flowchart of a file sharing method provided in an embodiment of this application. The method may include steps 410 to 430, which can be executed by a file sharing device, such as... Figure 1 The electronic device in the method can be a component of that electronic device, such as a chip, chip system, or other module that can be used to implement some or all of its functions; this application does not limit this. The steps of method 400 are described in detail below.

[0127] In step 410, in response to the first user action, a first sharing task is created.

[0128] The first quick share window is generated in response to the user's quick share operation on the first file set, such as... Figure 3 The quick share window is shown in (c). The first user action is to select the first device to be shared in the first quick share window corresponding to the first file set, such as... Figure 3 As shown in (d), the operation of selecting device 1 in the quick share window. The first sharing task can be a task used to share files in the first file set to the first device, such as... Figure 3 As shown in (e), a sharing task for file 1 is sent to device 1.

[0129] It should be understood that the first file set may include one or more files. If the user selects file 1, file 1 is the first file set; if the user selects both file 1 and file 2, then file 1 and file 2 together constitute the first file set.

[0130] In step 420, the task status and / or sending progress of the first sharing task are obtained.

[0131] The task status includes waiting to send, sending, and sending completed. When the first sharing task is completed, the task status is "sent completed"; when other sharing tasks are in progress, the first sharing task will wait for the other sharing tasks to complete before sending, i.e., the task status is "waiting to send"; when the first sharing task is being sent, the task status is "sent". Furthermore, when the first sharing task is being sent, its sending progress can also be obtained.

[0132] In step 430, the task status and / or sending progress of the first sharing task are displayed in the first quick share window and the main window of the sharing application.

[0133] It should be understood that if the task status is "Waiting to Send" or "Sent Completed," the first sharing task has no sending progress. Conversely, if the first sharing task has sending progress, it means the task status is "Sending in Progress." Therefore, when the task status is "Waiting to Send" or "Sent Completed," the sending progress may not be displayed; and when the task status is "Sending in Progress," only the sending progress may be displayed without showing the task status, or both the sending progress and the task status may be displayed. This application does not impose any limitations on this.

[0134] It should be noted that since step 410 is performed in the first quick share window, that is, the sharing of the first file set uses the quick share method, the user can directly see the task status and / or sending progress of the first sharing task from the already opened first quick share window. Although the main window of the sharing application may not be open, if the user opens the main window of the sharing application at this time, they can see the task status and / or sending progress of the first sharing task from that main window.

[0135] Based on the above method, the sharing task generated using the quick share method is displayed synchronously in the main window and the quick share window, allowing users to view the task status and / or sending progress of the sharing task in both the main window and the quick share window. This makes it easier for users to understand the overall status of the current sharing task of the electronic device directly from the main window of the sharing application, and to make adjustments to the sharing task in the sharing application, such as canceling a quick share task, etc., thus providing users with a better user experience.

[0136] To make it easier to understand, the following will be combined with Figure 5 The interaction process between the various modules involved in the file sharing method provided in the embodiments of this application will be described.

[0137] For example, Figure 5 This is a schematic diagram illustrating the interaction process between various modules in the file sharing method provided in the embodiments of this application.

[0138] like Figure 5 As shown, the software system of this electronic device may include: a quick share window service and a main share application service, etc. It should be understood that... Figure 5 The Quick Share Window service and the Analysis Application Main Service shown are merely examples of two modules in a software system. They can be replaced by other modules with the same or similar functions. Furthermore, the software system may include additional modules with other functions. This application does not impose any limitations on this.

[0139] It should also be understood that Figure 5For ease of distinction and understanding, the quick share window and the main share application window are shown here. In actual implementation, the quick share window and the main share application window can be displayed by calling window functions through their respective services. For example, the quick share window can be displayed by calling window functions through the quick share window service, and its displayed content can be updated through calling window functions through the quick share window service; the main share application window can be displayed by calling window functions through the main share application service, and its displayed content can be updated through calling window functions through the main share application service.

[0140] The following will combine Figure 6 The interface shown Figure 5 The interaction process will be explained in detail.

[0141] Users can perform quick share operations on the first set of files. These quick share operations could be, for example, like... Figure 6 The operations shown in (a) and (b) are: Select file 1 (i.e., the files in the first file set) → Right-click file 1 → Select Quick Share. To distinguish it from the first user operation mentioned earlier, the quick share operation on the first file set can be referred to as the second user operation.

[0142] The quick share window service responds to a second user's action by generating a first quick share window. The quick share window service can also respond to the second user's action by generating a window identifier corresponding to the first quick share window, which can be used to identify the first quick share window. In this way, even when multiple quick share windows are generated, different quick share windows can be distinguished by different window identifiers.

[0143] After generating the first quick share window, the quick share window service can display it by calling window functions. For example... Figure 6 As shown in (c), the device list in the first quick share window displays one or more devices that have a communication connection with the electronic device currently being operated by the user. The user can click on the device list in the first quick share window to select the first device to share, such as... Figure 6 As shown in (c), the user selected device 1 as the first device to be shared in the device list. This operation can be regarded as an example of the first user operation mentioned above.

[0144] The device list here can be obtained from the main sharing application service. For example, the main sharing application service can invoke the communication module to discover other nearby connectable electronic devices, connect to them, and establish a device list. The communication module can send this device list to the main sharing application service, which then sends it to the quick share window service. The quick share window service can display the device list in response to a user's quick share operation, such as the second user operation mentioned above. When updating the device list, the sending module can synchronize it to the main sharing application service, which then synchronizes it to the quick share window service.

[0145] It should be understood that the communication module here can be a module with device discovery, device connection, and transmission functions. For example, it could be... Figure 1 The wireless communication module 160 in this application can also be other modules with the same or similar functions, and this application does not limit it.

[0146] The quick share window service responds to the first user's operation by generating task information and sending this task information to the main sharing application service. The task information includes the filenames and storage paths of each file in the first file set, as well as the device identifier of the first device. The storage path can be the absolute storage path of each file in the first file set within the electronic device.

[0147] After receiving the task information, the main sharing application service can create the first sharing task based on the task information.

[0148] Optionally, in response to the first user's operation, the quick share window service may generate a first task identifier in the task information, which can be used to identify the first share task.

[0149] For example, if the first sharing task is to share file 1 to device 1 through the first quick sharing window, then the first task identifier includes the device identifier of the target device of the first sharing task, the file name of the target file of the first sharing task, and the storage path.

[0150] There is a correspondence between the first sharing task and the first quick sharing window. In other words, the first task identifier corresponds to the window identifier of the first quick sharing window. By establishing the correspondence between the first sharing task and the first quick sharing window, it is possible to determine the quick sharing window corresponding to each different sharing task when there are multiple sharing tasks and multiple quick sharing windows.

[0151] After the main sharing application service creates the first sharing task, it can call the communication module to send the first set of files to the first device via the sending module. Simultaneously, a notification is sent to the main sharing application window to display the first sharing task.

[0152] While the first sharing task is in progress, the main sharing application service can obtain the task status and / or sending progress of the first sharing task in real time through a callback function injected into the communication module, and update the task status and / or sending progress of the first sharing task in the main sharing application window in real time. Simultaneously, the main sharing application service can send the first task identifier, along with the task status and / or sending progress of the first sharing task, to the quick share window service.

[0153] The quick share window service can determine whether the sharing task corresponding to the first task identifier is a quick share task based on the received first task identifier. If it is, the quick share window corresponding to the first task identifier can be updated according to the task status and / or sending progress of the received first share task. If not, the task status and / or sending progress of the received first share task can be not displayed, for example, it can be discarded or not processed.

[0154] In this embodiment, the first task identifier corresponds to the first sharing task, which is a quick sharing task. Since the first sharing task corresponds to the first quick sharing window, the quick sharing window service can update the task status and / or sending progress of the first sharing task in the first quick sharing window in real time by calling the window function.

[0155] It should be noted that sharing tasks may include tasks created in response to user actions in the main sharing application window and tasks created in response to user actions in the quick share window. Since sharing tasks created in response to user actions in the main sharing application window are not quick share tasks, they may not be displayed in the quick share window.

[0156] It should be understood that, in cases such as Figure 6 Following the first user action shown in (c), the subsequent process of creating the first sharing task and obtaining its task status and / or sending progress is very brief. Therefore, the first quick share window can begin displaying the task status and / or sending progress of the first sharing task immediately after the first user action, as shown in (c). Figure 6 As shown in (d) in the figure.

[0157] At this time, as Figure 6 As shown in (e), if you open the main window of the PC Manager, i.e., the main window of the sharing application, you can see a progress circle indicating the sending progress appearing next to the icon of the first device. Figure 6As shown in (f), clicking the icon of the first device will reveal, as shown in [the image]. Figure 6 As shown in (g), the task status and / or sending progress of the first sharing task can also be seen in the main window of the sharing application.

[0158] Based on the above technical content, the sharing of the first set of files was realized through quick sharing, and the first sharing task was synchronized in the main window of the sharing application and the quick sharing window.

[0159] After a user selects a first device in the first shortcut window, they may continue to perform other sharing operations. These other sharing operations may include the following two types: the first type is to continue sharing the first file set with other electronic devices in the first shortcut sharing window; the second type is to share a second file set, which is different from the first file set.

[0160] The second file set differs from the first file set in that the files included in the second file set are completely different or partially different from those included in the first file set. For example, the first file set includes file 1, and the second file set includes file 2; or the first file set includes files 1 and 2, and the second file set includes files 2 and 3; or the first file set includes file 1, and the second file set includes files 1 and 3.

[0161] The following sections will provide a detailed explanation of the processes for these two sharing operations.

[0162] See Figure 7 and Figure 8 , Figure 7 and Figure 8 This pertains to the process of the first type of sharing operation mentioned above. It should be understood that... Figure 7 The operation process shown can be performed at any time. Figure 5 The process shown is executed after the user clicks to select the first device in the first quick share window. Since the quick share operation of the user selecting the first set of files and the related content of generating and displaying the first quick share window can be found in the previous explanation, it will not be repeated here. Figure 8 It shows in Figure 7 The diagram shows the interface of the process.

[0163] Before the user selects the second device, the user can perform another quick share operation on the first file set. For clarity, this second quick share operation on the first file set is referred to as the third user operation. This third user operation can be the same as the second user operation mentioned earlier. For example, the third user operation could be the user reopening or selecting the first quick share window, or the user re-selecting files in the first file set, right-clicking on a file in the first file set, and then selecting quick share.

[0164] The quick share window service responds to a third user's action by activating the first quick share window.

[0165] Here, "activation" can mean placing the first quick-share window program on the front of the interface, making it interactive. For example, users can move or close the first quick-share window, or select more devices to share the first file collection within it.

[0166] Users can click to select the second device to share from the list in the first quick sharing window, such as... Figure 8 As shown in (a), the user selected device 3 from the list in the quick share window. For clarity, the user's action of selecting a new target device for the first file set is referred to as the fourth user action. It can be understood that the fourth user action can be the same as the first user action mentioned above.

[0167] In response to a fourth user action, the Quick Share window service can generate a second task identifier. Although this second task identifier can be used for another sharing task, since both the current and previous sharing tasks involve quick sharing of the same file set (i.e., the first file set), they can be displayed in the same quick share window. As shown in the figure, in response to the fourth user action, the Quick Share window service updates the first quick window, so that the user's newly selected device 3 (an example of the second device) is also displayed in the first quick window. That is, the second task identifier also corresponds to the window identifier of the first quick window. In other words, the sharing task corresponding to the second task identifier corresponds to the first quick window.

[0168] On the other hand, the quick share window can send the generated second task identifier and its corresponding task information to the main sharing application service, so that the main sharing application service can create a second sharing task.

[0169] The second sharing task could be a task used to share files from the first file set to a second device, that is, Figure 8 The interface shown is for sharing file 1 to device 3.

[0170] It should be understood that the main sharing application service creates a second sharing task based on the second task identifier and task information, and the process after the creation of the second sharing task can be referred to the preceding text. Figure 5 and Figure 6 The descriptions regarding the creation of the first sharing task and its subsequent processes in the embodiments are not repeated here. The main sharing application service can obtain the task status and / or sending progress of the first sharing task and the task status and / or sending progress of the second sharing task in real time by calling the sending module, and can update the main sharing application window based on the latest task status and / or sending progress obtained each time, and synchronize it to the quick sharing window service so that the quick sharing window service can update the first quick sharing window.

[0171] like Figure 8 As shown in (b), the first quick share window displays two sharing tasks: a task to share file 1 to device 1, i.e., the first task, and a task to share file 1 to device 3, i.e., the second task. The first quick share window also displays the sending progress of the first task and the task status of the second task.

[0172] Based on the above technical features, the quick share window can be activated in response to user actions and can be repeatedly used. This eliminates the need for users to wait for a quick share to complete before performing another quick share on the same set of files. Therefore, users can quickly share files one or more times as needed, resulting in a better user experience.

[0173] See Figure 9 , Figure 9 This pertains to the process of the second type of sharing operation mentioned above.

[0174] Users can perform quick sharing operations on the second set of files. For example, a quick sharing operation could be like this: Figure 9 The operations shown in (a) and (b) are: select files in the second file set → right-click on files in the second file set → select quick share. For clarity, the user's quick share operation on another file set is referred to as the fifth user operation. It can be understood that the fifth user operation can be the same as the second user operation mentioned earlier.

[0175] The quick share window service responds to the fifth user action by displaying a second quick share window corresponding to the second file set. This second quick share window is different from the first quick share window; the two windows do not completely overlap in the user interface area, and both windows can be activated in response to user actions. For example... Figure 9 As shown in (c), the new quick share window that overlays the original quick share window is the second quick share window.

[0176] Here, both windows can be activated in response to user actions. Specifically, the user can choose to perform a new operation in either the first or second quick share window, depending on their needs. For example, the user can directly perform a new operation in the second quick share window, which is currently on top of the interface, or they can click on the first quick share window to bring it to the forefront and perform a new operation on it.

[0177] Similar to the first quick share window, the second quick share window contains a device list. The device list here is the same as that in the first quick share window, so it will not be described again here.

[0178] Next, as Figure 9 As shown in (c), the user clicks on the device list in the second quick share window to select the device to be shared, such as device 3. For ease of distinction, the user's operation of selecting the target device for the second file set is denoted as the sixth user operation. It can be understood that the sixth user operation can be the same as the first user operation mentioned above.

[0179] The quick share window service responds to the process following the sixth user action as described above. Figure 5 and Figure 6 In the illustrated embodiment, the quick sharing window service responds to the first user's operation in a similar manner. The process executed by the main service of the sharing application is also similar to that described above. For example, based on the sixth user's operation, a third sharing task can be created, and the sending module can be called to share the files in the second file set with the target device, as well as to obtain the task status and / or sending progress of the third sharing task in real time. For details, please refer to the relevant descriptions above, which will not be repeated here.

[0180] The quick share window service can receive real-time updates of the second quick share window from the main service of the sharing application for the second share task, and display the task status and / or sending progress of the third task in the second quick share window.

[0181] like Figure 9 As shown in (d), in the second quick share window, a task to share file 2 to device 3 is displayed, which is an example of the third share task, and the second quick share window displays the task status and / or sending progress of the third share task.

[0182] Based on the above technology, users can quickly share one set of files while simultaneously sharing another set of files. Furthermore, they can freely switch between the two quick sharing windows as needed to perform other operations, resulting in a better user experience.

[0183] Figure 10 This is a schematic diagram of the hardware structure of a file sharing device provided in an embodiment of this application.

[0184] like Figure 10 As shown, the device includes a memory 1001, a processor 1002, and an interface circuit 1003. The device may also include a display screen 1004, wherein the memory 1001, processor 1002, interface circuit 1003, and display screen 1004 are communicable. For example, the memory 1001, processor 1002, interface circuit 1003, and display screen 1004 can communicate via a communication bus. The memory 1001 stores computer execution instructions, which are controlled by the processor 1002, and the interface circuit 1003 performs the communication, thereby realizing the file sharing method provided in this application embodiment.

[0185] Optionally, the interface circuit 1003 may further include a transmitter and / or a receiver. Optionally, the processor 1002 may include one or more CPUs, or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0186] In possible implementations, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0187] The file sharing device provided in this application embodiment is used to execute the file sharing method of the above embodiment. The technical principle and technical effect are similar, and will not be described again here.

[0188] This application provides an electronic device, the structure of which is described below. Figure 1 The electronic device's memory can be used to store at least one program instruction, and the processor is used to execute at least one program instruction to implement the technical solution of the above-described method embodiments. Its implementation principle and technical effects are similar to those of the related embodiments of the above-described method, and will not be repeated here.

[0189] This application provides a chip. The chip includes a processor, which is used to call a computer program in memory to execute the technical solutions in the above embodiments. Its implementation principle and technical effects are similar to those in the related embodiments described above, and will not be repeated here.

[0190] This application provides a computer program product that, when run on an electronic device, causes the electronic device to execute the technical solutions described in the above embodiments. Its implementation principle and technical effects are similar to the related embodiments described above, and will not be repeated here.

[0191] This application provides a computer-readable storage medium storing program instructions. When these program instructions are executed by an electronic device, the electronic device performs the technical solution described in the above embodiments. Its implementation principle and technical effects are similar to the related embodiments described above, and will not be repeated here.

[0192] The above specific embodiments further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of the present invention should be included within the scope of protection of the present invention.

Claims

1. A file sharing method characterized by, Applied to electronic devices, including: In response to a first user operation, a first sharing task is created; the first user operation is the operation of selecting a first device to be shared in a first quick sharing window corresponding to a first file set, and the first sharing task is used to share files in the first file set to the first device; wherein, the first quick sharing window is a window generated in response to the user's quick sharing operation on the first file set, the first file set includes one or more files, and the quick sharing operation is the operation of sharing a file by clicking on it; Obtain the task status and / or sending progress of the first sharing task, wherein the task status includes: waiting to send, sending in progress, or sending completed; The task status and / or sending progress of the first sharing task are displayed in the first quick sharing window; In response to a fourth user action, a second sharing task is created, wherein the fourth user action is the operation of selecting a second device to be shared in the first quick sharing window, and the second sharing task is used to share the first file set to the second device. Update the first quick share window. The updated first quick share window displays the task status and / or sending progress of the first sharing task, as well as the task status and / or sending progress of the second sharing task.

2. The method of claim 1, wherein, The step of creating the first sharing task in response to a first user operation includes: In response to the first user operation, task information is obtained, including the filenames and storage paths of each file in the first file set, and the device identifier of the first device; Based on the task information, the first sharing task is created.

3. The method of claim 2, wherein, The task information also includes a first task identifier, which is generated in response to the first user operation. The first task identifier is used to identify the first sharing task and corresponds to the first quick share window.

4. The method of claim 3, wherein, The method further includes: Based on the first task identifier, determine the corresponding first quick share window, which is used to display the task status and / or sending progress of the first share task.

5. The method of claim 3 or 4, wherein, The first task identifier corresponds to the first quick share window, including: the first task identifier corresponds to the window identifier of the first quick share window; Before obtaining task information in response to the first user operation, the method further includes: In response to a second user operation, the first quick sharing window is displayed. The second user operation is a quick sharing operation of the first file set. The first quick sharing window displays one or more devices, including the first device. The one or more devices are devices that have a communication connection with the electronic device. Assign the window identifier to the first quick share window.

6. The method of claim 5, wherein, The method further includes: In response to a third user action, the first quick share window is activated, wherein the third user action is another quick share action on the first file set following the first user action.

7. The method of claim 6, wherein, The method further includes: In response to the fourth user operation, a second task identifier is generated. The second task identifier is used to identify the second sharing task and also corresponds to the first quick share window.

8. The method of any one of claims 1 to 7, wherein, The method further includes: In response to a fifth user action, a second quick share window corresponding to the second file set is displayed. The fifth user action is a quick share operation on the second file set, which is a different file set from the first file set. The first quick share window and the second quick share window are different windows, and both the first quick share window and the second quick share window can be activated in response to the user's action.

9. The method of claim 8, wherein, The areas occupied by the first quick share window and the second quick share window in the user interface do not completely overlap.

10. A file sharing apparatus characterized by comprising: Includes a module for performing the method as described in any one of claims 1 to 9.

11. A file sharing apparatus, characterized by comprising: Including memory and processor, among which, The memory is used to store computer programs; The processor is used to invoke and execute the computer program to cause the device to perform the method as described in any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, Used to store a computer program that, when run on a computer, causes an electronic device to perform the method as described in any one of claims 1 to 9.

13. A computer program product, characterised in that, The computer program product includes computer program code that, when run on a computer, causes an electronic device to perform the method as described in any one of claims 1 to 9.

Images