File access method, communication system and electronic device

Abstract

The present application discloses a file access method, which is applied to a communication system including a first electronic device and a second electronic device, wherein the first electronic device and the second electronic device establish a communication connection; the method comprises: the first electronic device receives a trigger operation of a user on a sandbox file in a sharing interface sent by the second electronic device, and sends an access request to the second electronic device; the second electronic device receives the access request and determines mapping information corresponding to the sandbox file based on the access request, wherein the mapping information includes a mapping file corresponding to the sandbox file, a path of the mapping file, and a correspondence between the path of the mapping file and file index information of the sandbox file; the second electronic device sends the mapping information to the first electronic device; the first electronic device receives the mapping information and can directly access the sandbox file based on the mapping information, thereby effectively improving the user experience. The present application also discloses a communication system and an electronic device.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a file access method, a communication system, and an electronic device. Background Art

[0002] A sandbox is a security mechanism that provides an isolated environment for programs running on electronic devices. It ensures the security of the system by strictly controlling the resources accessed by the executed programs. In electronic devices, files protected by the sandbox principle are generally referred to as sandbox files. For example, files protected by the sandbox principle within an application in an electronic device are sandbox files. Generally, an application in an electronic device can access the sandbox file corresponding to the application. Other applications in the electronic device or applications in other electronic devices generally do not have access to the sandbox file, or other applications can only access the sandbox file if authorized by the application.

[0003] With the widespread adoption of electronic devices such as mobile phones and personal computers (PCs), technologies enabling collaboration between these devices have become widely used. For example, collaboration between PCs and mobile phones is now possible. Currently, when collaborating between a PC and a mobile phone, the PC displays a shared interface shared by the mobile phone. Through this shared interface, the PC can open and even edit documents, images, and other files stored in the mobile phone's internal storage. However, the PC cannot open or edit sandbox files corresponding to applications in the mobile phone, impacting the user experience. Summary of the Invention

[0004] The present application provides a file access method, a communication system, and an electronic device, which are used to solve the problem in the prior art that electronic devices cannot operate each other's sandbox files, thereby achieving better interaction between electronic devices and improving the user experience.

[0005] To solve the above technical problems, in the first aspect, an embodiment of the present application provides a file access method, which is applied to a communication system including a first electronic device and a second electronic device, and the first electronic device and the second electronic device establish a communication connection; the method includes: the first electronic device displays a sharing interface sent by the second electronic device, and the sharing interface includes a sandbox file corresponding to the application in the second electronic device; the first electronic device receives a user's trigger operation on the sandbox file and sends an access request to the second electronic device; the second electronic device receives the access request and determines the mapping information corresponding to the sandbox file according to the access request, the mapping information including the mapping file corresponding to the sandbox file, the path of the mapping file, and the correspondence between the path of the mapping file and the file index information of the sandbox file; the second electronic device sends the mapping information to the first electronic device; the first electronic device receives the mapping information and accesses the sandbox file according to the mapping information.

[0006] The file access method provided in this application enables a first electronic device to directly access a sandbox file corresponding to an application in a second electronic device based on mapping information corresponding to the sandbox file, thereby improving the interaction effect between the first electronic device and the second electronic device, and improving the user experience.

[0007] In a possible implementation of the first aspect, the establishing of a communication connection between the first electronic device and the second electronic device may be that the first electronic device and the second electronic device establish a communication connection with a collaborative function between the devices enabled.

[0008] In one possible implementation of the first aspect described above, the sandbox file corresponding to the application in the second electronic device may be an internal sandbox file of the application, such as an email attachment such as an image or document corresponding to the mailbox application in the second electronic device. That is, the file access method provided by this implementation allows the first electronic device to directly access the email attachment in the mailbox of the second electronic device. Of course, the sandbox file may also be other files in the electronic device that are normally accessible only to the application itself.

[0009] In a possible implementation of the first aspect above, the second electronic device determines the mapping information corresponding to the sandbox file based on the access request, including: the second electronic device determines the sandbox file based on the access request; the second electronic device determines the uniform resource identifier corresponding to the sandbox file, and determines the file index information corresponding to the uniform resource identifier based on the uniform resource identifier; the second electronic device determines the mapping information based on the uniform resource identifier and the file index information.

[0010] In a possible implementation of the first aspect above, the first electronic device accesses the sandbox file according to the mapping information, including: the first electronic device determines the mapping file and file index information according to the path of the mapping file; the first electronic device accesses the sandbox file according to the mapping file and the file index information.

[0011] The first electronic device can determine the mapping file corresponding to the mapping file path based on the mapping file path, and can also determine the file index information corresponding to the mapping file path based on the mapping file path and the correspondence between the mapping file path and the file index information of the sandbox file. The first electronic device can then determine the sandbox file based on the mapping file and access the sandbox file based on the file index information corresponding to the sandbox file. In other words, the first electronic device can directly access the aforementioned sandbox file based on the mapping file and the file index information.

[0012] In a possible implementation of the first aspect, the mapping file is a soft link file, and the mapping file includes location information of the sandbox file.

[0013] In a possible implementation of the first aspect above, the file index information is a file descriptor.

[0014] The first electronic device can determine the location of the sandbox file according to the location information of the sandbox file in the soft link file, and can perform operations such as opening or reading and writing the sandbox file according to the file descriptor to access the sandbox file.

[0015] In a possible implementation of the first aspect above, the access request includes operation type information and operation area information corresponding to the triggering operation.

[0016] The operation type information may be, for example, a user clicking on a sandbox file, and the operation area information may be, for example, the coordinates of the location where the user clicked on the sandbox file. The second electronic device may determine the sandbox file accessed by the first electronic device based on the operation type information and the operation area information.

[0017] In a second aspect, an embodiment of the present application provides a file access method, which is applied to a communication system including a first electronic device and a second electronic device, wherein the first electronic device and the second electronic device establish a communication connection, the first electronic device includes a first collaborative application and a first file sharing module, and the second electronic device includes a second collaborative application, a second file sharing module and a target operation application, and the method includes: the first collaborative application displays a sharing interface of the second electronic device sent by the second collaborative application, the sharing interface includes a sandbox file corresponding to the target operation application in the second electronic device; the first collaborative application receives a user's trigger operation on the sandbox file and sends an access request to the second collaborative application; the second collaborative application receives the access request, and according to the access request, enables the second collaborative application to share the file. The module determines the mapping information corresponding to the sandbox file, and the mapping information includes the mapping file corresponding to the sandbox file, the path of the mapping file, and the correspondence between the path of the mapping file and the file index information of the sandbox file; the second file sharing module sends the mapping file and the correspondence between the path of the mapping file and the file index information of the sandbox file to the first file sharing module, and the second file sharing module sends the path of the mapping file to the second collaborative application; the second collaborative application sends the path of the mapping file to the first collaborative application; the first collaborative application receives the path of the mapping file, determines the mapping file and file index information corresponding to the path of the mapping file from the second file sharing module according to the path of the mapping file, and accesses the sandbox file according to the mapping file and the file index information.

[0018] The file access method provided by the present application is that the first collaborative application can determine the mapping file corresponding to the path of the mapping file in the second file sharing module based on the path of the mapping file, and the first collaborative application can determine the file index information corresponding to the path of the mapping file based on the correspondence between the path of the mapping file and the path of the mapping file in the second file sharing module and the file index information of the sandbox file. Then the first collaborative application can determine the sandbox file based on the mapping file, and can access the sandbox file based on the file index information corresponding to the sandbox file. That is, the first collaborative application can directly access the aforementioned sandbox file based on the mapping file and the file index information. That is, the first electronic device can directly access the sandbox file corresponding to the application in the second electronic device based on the mapping information corresponding to the sandbox file, which can improve the interaction effect between the first electronic device and the second electronic device, and can improve the user experience.

[0019] In a possible implementation of the second aspect above, the second electronic device also includes a content provider module, and the second collaborative application enables the second file sharing module to determine the mapping information corresponding to the sandbox file based on the access request, including: the second collaborative application determines the sandbox file based on the access request; the second collaborative application obtains the uniform resource identifier corresponding to the sandbox file from the target operation application corresponding to the sandbox file, and sends the uniform resource identifier to the second file sharing module; the second file sharing module receives the uniform resource identifier, and obtains the file index information corresponding to the uniform resource identifier from the content provider module based on the uniform resource identifier; the second file sharing module generates a mapping file based on the uniform resource identifier and the file index information and stores it in the shared directory of the second file sharing module, and determines the path of the mapping file, and determines that the correspondence between the path of the mapping file and the file index information is stored in the data structure of the second file sharing module.

[0020] In a possible implementation of the second aspect, the method further includes: the second collaborative application calls the soft link interface of the second file sharing module to send the uniform resource identifier to the second file sharing module so that the second file sharing module determines the mapping information.

[0021] In a possible implementation of the second aspect, the second file sharing module obtains file index information corresponding to the uniform resource identifier from the content provider module through the Android interface definition language interface of the content provider module according to the uniform resource identifier.

[0022] In a possible implementation of the second aspect, the mapping file is a soft link file, and the mapping file includes location information of the sandbox file.

[0023] In a possible implementation of the second aspect above, the file index information is a file descriptor.

[0024] In a possible implementation of the second aspect, the access request includes operation type information and operation area information corresponding to the triggering operation.

[0025] In a third aspect, an embodiment of the present application provides a file access method, which is applied to a first electronic device, and the method includes: the first electronic device displays a sharing interface sent by a second electronic device that establishes a communication connection with the first electronic device, and the sharing interface includes a sandbox file corresponding to an application in the second electronic device; the first electronic device receives a user's trigger operation on the sandbox file, and sends an access request to the second electronic device; the first electronic device receives mapping information sent by the first electronic device, and accesses the sandbox file according to the mapping information, the mapping information is information corresponding to the sandbox file determined by the second electronic device according to the access request, and the mapping information includes a mapping file corresponding to the sandbox file, a path of the mapping file, and a correspondence between the path of the mapping file and the file index information of the sandbox file.

[0026] In a fourth aspect, an embodiment of the present application provides a file access method, which is applied to a second electronic device, and the method includes: the second electronic device receives an access request sent by a first electronic device that establishes a communication connection with the second electronic device, and determines, based on the access request, mapping information corresponding to the sandbox file requested to be accessed by the first electronic device, the mapping information including the mapping file corresponding to the sandbox file, the path of the mapping file, and the correspondence between the path of the mapping file and the file index information of the sandbox file, the access request is a request generated by the first electronic device receiving a user's trigger operation on the sandbox file, and the sandbox file is a file corresponding to an application in the second electronic device included in the sharing interface sent by the second electronic device displayed by the first electronic device; the second electronic device sends the mapping information to the first electronic device so that the first electronic device accesses the sandbox file according to the mapping information.

[0027] In a fifth aspect, an embodiment of the present application provides a communication system, comprising a first electronic device and a second electronic device, wherein the first electronic device and the second electronic device establish a communication connection; wherein the first electronic device is used to display a sharing interface sent from the second electronic device, and the sharing interface includes a sandbox file corresponding to an application in the second electronic device; the first electronic device is also used to receive a user trigger operation on the sandbox file and send an access request to the second electronic device; the second electronic device is used to receive the access request and determine the mapping information corresponding to the sandbox file based on the access request, the mapping information including the mapping file corresponding to the sandbox file, the path of the mapping file, and the correspondence between the path of the mapping file and the file index information of the sandbox file; the second electronic device is also used to send the mapping information to the first electronic device; the first electronic device is also used to receive the mapping information and access the sandbox file based on the mapping information.

[0028] The communication system provided in the present application includes an electronic device for executing the file access method provided by the above-mentioned first aspect and / or any possible implementation method of the first aspect, and thus can also achieve the beneficial effects (or advantages) of the file access method provided by the first aspect.

[0029] In a sixth aspect, an embodiment of the present application provides an electronic device, comprising: a memory for storing a computer program, the computer program including program instructions; and a control component for executing the program instructions so that the electronic device executes a file access method provided by any possible implementation method as described above.

[0030] In the seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. The computer program includes program instructions, and the program instructions are executed by a computer to enable the computer to execute a file access method provided by any possible implementation method as described above.

[0031] In an eighth aspect, an embodiment of the present application provides a computer program product, which, when running on an electronic product, enables the electronic product to execute the aforementioned file access method.

[0032] It can be understood that the beneficial effects of the second to seventh aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings used in the description of the implementation methods.

[0034] Figure 1 is a schematic diagram showing a communication system provided by the present application according to some embodiments of the present application;

[0035] Figure 2A and Figure 2B 1 is a schematic diagram showing some interfaces of a mobile phone 100 and a PC 200 in the prior art according to some embodiments of the present application;

[0036] Figure 3A is a schematic structural diagram of a mobile phone 100 according to some embodiments of the present application;

[0037] Figure 3B is a schematic diagram showing the structure of a PC 200 according to some embodiments of the present application;

[0038] Figure 4A 1 is a schematic diagram showing a software structure of a mobile phone 100 according to some embodiments of the present application;

[0039] Figure 4B 1 is a schematic diagram showing a software structure of a PC 200 according to some embodiments of the present application;

[0040] Figures 5A-5E1 is a diagram showing some interface diagrams of the mobile phone 100 and the PC 200 provided by the present application according to some embodiments of the present application;

[0041] Figure 6 is a schematic diagram showing another communication system provided by the present application according to some embodiments of the present application;

[0042] Figure 7A — Figure 7C 1 is a diagram showing some other interface diagrams of the mobile phone 100 and the PC 200 provided by the present application according to some embodiments of the present application;

[0043] Figure 8 1 is a flowchart illustrating the process of establishing a communication connection between the mobile phone 100 and the PC 200 and sharing a shared directory in the file access method provided by the present application according to some embodiments of the present application;

[0044] Figure 9 1 is a schematic diagram showing a process flow of PC 200 accessing a sandbox file in mobile phone 100 in a file access method provided by the present application according to some embodiments of the present application;

[0045] Figure 10 1 is a schematic diagram showing another process of establishing a communication connection between the mobile phone 100 and the PC 200 and sharing a shared directory in the file access method provided by the present application according to some embodiments of the present application;

[0046] Figure 11 is a schematic structural diagram of an electronic device according to some embodiments of the present application;

[0047] Figure 12 The present invention is a schematic structural diagram of a system on chip (SoC) according to some embodiments of the present application. DETAILED DESCRIPTION

[0048] The technical solution of this application will be further clearly and completely described below in conjunction with the accompanying drawings.

[0049] See Figure 1, the present application provides a communication system, including a mobile phone 100 and a PC 200 (a desktop computer is used as an example of PC 200). The mobile phone 100 and the PC 200 can establish a communication connection (or can be called a network communication connection) such as WiFi, Bluetooth, and Near Field Communication (NFC) with each other, and the mobile phone 100 and the PC 200 can enable a collaborative function between the two based on the communication connection to perform collaborative operations. The manner and process of establishing a communication connection between the mobile phone 100 and the PC 200 can be the same as the manner and process of establishing a communication connection such as WiFi, Bluetooth, NFC, etc. between currently common electronic devices, and this application will not provide a detailed description of this.

[0050] See Figure 2A In one implementation of the present application, the mobile phone 100 and the PC 200 establish an NFC communication connection, and the mobile phone 100 and the PC 200 start the collaboration function between each other, and the PC 200 displays Figure 2A The settings interface 202 and the email display interface 2033 shown are shown. The settings interface 202 is used for the user to perform management operations such as collaboration and communication connection on the mobile phone 100 through PC200. The email display interface 2033 is a sharing interface shared by the mobile phone 100 to PC200. The email display interface 2033 includes the sender information "xxxxxx.@163.com", the recipient information "******.@163.com", and the "IMG_0094.JPG" picture file as an email attachment (an email attachment can also be called an email attachment file). In addition, the email display interface 2033 also includes a "download" control corresponding to the email attachment. If PC200 detects that the user clicks on the "download" control, PC200 executes the operation of downloading the email attachment. Of course, the email display interface 2033 also includes controls and information such as reply, reply all, forward, delete, more, and add to group.

[0051] Since the email attachment in the mailbox application in the mobile phone 100 is a sandbox file, during the process of PC200 cooperating with the mobile phone 100, PC200 is usually unable to access the email attachment, for example, PC200 cannot download the email attachment. In one implementation of the present application, PC200 cannot download the email attachment and displays the following message: Figure 2B The prompt message 204 shown is "Download failed".

[0052] During the process of PC200 collaborating with mobile phone 100, PC200 cannot access the email attachment corresponding to the mailbox application in mobile phone 100 as a sandbox file, that is, it cannot perform collaborative operations such as downloading, opening, and editing on the email attachment. There is a problem that affects the collaborative effect between PC200 and mobile phone 100, as well as a problem that affects the user experience.

[0053] The present application provides a file access method for the above-mentioned communication system. If PC200 detects a user's click operation on the "Download" control corresponding to the email attachment (the click operation is an example of a trigger operation), PC200 sends an access request to the mobile phone 100. The access request includes the access action information of the user clicking the mouse corresponding to the user's click operation on the "Download" control and the coordinate information of the location where the user clicked on the email display interface 2033 as the shared interface. PC200 requests the mobile phone 100 to obtain the soft link (Soft link) corresponding to the email attachment, the path of the soft link, and the correspondence (or mapping relationship) between the path of the soft link and the file descriptor (file descriptor, fd) from the access request. A soft link is actually a text file, so a soft link can also be called a soft link file. The soft link contains the location information of the email attachment. The location information can be, for example, the absolute path of the email attachment. The absolute path includes information such as the package name, relative path and name corresponding to the email attachment. fd is the information required to access a file (such as an email attachment). For example, fd is used to determine the file to be opened or read and written. The file descriptor is a non-negative integer. PC 200 can determine the soft link and fd corresponding to the soft link path based on the soft link path. Then, PC 200 can determine the email attachment in the mailbox application of mobile phone 100 based on the fd and the location information of the email attachment in the soft link, and can directly access the email attachment. For example, PC 200 can download the aforementioned email attachment "IMG_0094.JPG" picture file.

[0054] The file access method provided by the present application is that the mobile phone 100 sends the soft link corresponding to the email attachment, the path of the soft link, and the correspondence between the path of the soft link and fd to PC200 respectively, so that when PC200 needs to access the email attachment as a sandbox file, it can determine the soft link corresponding to the path of the soft link through the path of the soft link. And PC200 can "see" (i.e., query or link to) the email attachment in the mailbox application of the mobile phone 100 through the soft link. In addition, PC200 can also determine the fd required to access the email attachment based on the correspondence between the path of the soft link and fd. The file access method provided by the present application is that PC200 can directly access the email attachment inside the mailbox application in the mobile phone 100 based on the soft link and fd, which can effectively improve the effect of PC200's interaction and collaborative operation with the mobile phone 100, and improve the user experience.

[0055] In addition, the file access method provided by the present application allows PC200 to access email attachments as sandbox files through soft links and fd, without the need for PC200 to copy email attachments from mobile phone 100 to PC200. This can effectively reduce file copying time, improve file access efficiency, save PC200 memory, and improve the interaction and collaboration between PC200 and mobile phone 100.

[0056] See Figure 3A , Figure 3A A schematic structural diagram of a mobile phone 100 is shown as an example.

[0057] The mobile phone 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) connector 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light 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.

[0058] It should be understood that the illustrated structure of the embodiment of the present invention does not constitute a specific limitation on the mobile phone 100. In other embodiments of the present application, the mobile phone 100 may include more or fewer components than shown, or some components may be combined or separated, or arranged differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0059] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0060] The processor can generate operation control signals based on instruction opcodes and timing signals to complete the control of instruction fetching and execution.

[0061] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0062] In some embodiments, the processor 110 may include one or more interfaces. The 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, and a subscriber identity module (SIM) interface.

[0063] The wireless communication function of the mobile phone 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0064] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in mobile phone 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0065] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied on the mobile phone 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0066] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the mobile phone 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0067] In some embodiments, the antenna 1 of the mobile phone 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the mobile phone 100 can communicate with the network and other devices through wireless communication technologies. The wireless communication technologies 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 technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0068] Mobile phone 100 implements display functionality through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0069] Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, mobile phone 100 may include one or N display screens 194, where N is a positive integer greater than one.

[0070] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU enables intelligent cognitive applications in the phone 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0071] The internal memory 121 can be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the mobile phone 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the mobile phone 100 by running instructions stored in the internal memory 121 and / or instructions stored in a memory provided in the processor, such as executing the file access method provided in this application.

[0072] The mobile phone 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

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

[0074] The touch sensor 180K is also called a "touch device." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the mobile phone 100, in a location different from that of the display screen 194.

[0075] See Figure 3B , Figure 3B A structural diagram of a PC 200 is shown as an example.

[0076] The PC 200 may include a processor 210 , a communication module 220 , an audio module 230 , a display screen 240 , a power module 250 , and an internal memory 260 .

[0077] The processor 210 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and the like. The different processing units may be independent devices or integrated into one or more processors. The processor may generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0078] Processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 210 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 210. If processor 210 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 210 latency, and thus improves system efficiency.

[0079] The communication module 220 can provide wireless communication solutions including WLAN (Wi-Fi), BT, etc. applied on the PC 200.

[0080] PC 200 implements display functions through a GPU, display screen 240, and an application processor. The GPU is a microprocessor for image processing that connects display screen 240 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs that execute program instructions to generate or modify display information.

[0081] The PC 200 can implement audio functions such as video playback and music playback through the audio module 230 and the application processor.

[0082] The PC 200 can be powered by itself through the power module 250 .

[0083] The internal memory 260 can be used to store computer executable program codes, which include instructions. The internal memory 260 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data (such as video data) created during the use of PC200, etc. In addition, the internal memory 260 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 210 executes various functional applications and data processing of PC200 by running instructions stored in the internal memory 260 and / or instructions stored in a memory provided in the processor, such as executing the file access method provided in this application.

[0084] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on PC 200. In other embodiments of the present application, PC 200 may include more or fewer components than shown, or may combine or separate certain components, or may have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0085] See Figure 4A , Figure 4A A software structure block diagram of a mobile phone 100 is shown as an example.

[0086] The software structure of the mobile phone 100 may be based on Android, including an application layer, an operating system (OS) framework layer, and an OS layer. The application layer includes a mobile client application (the mobile client application is an example of a second collaborative application), an email application (the email application is an example of a target operating application), a file sharing module (the file sharing module is an example of a second file sharing module), and a content provider (ContentProvider) module (or also referred to as a ContentProvider component).

[0087] The function of the mobile client application is to realize the collaborative function between the PC 200 and the mobile phone 100 for establishing a communication connection.

[0088] The mobile client application is also used to interact with other applications in the mobile phone 100 during the process of PC200 collaborating with the mobile phone 100, for example, to interact with the mailbox application in the mobile phone 100 which is the target operation application requested for collaboration by PC200, and to obtain the Universal Resource Identifier (URI) string of the sandbox file inside the mailbox application.

[0089] The structure of a URI string is similar to a common URL. For example, an example URI string is:

[0090] content: / / com.huawei.mail / my_images / IMG_0094.JPG.

[0091] The "content: / / " header represents the dedicated access protocol for the ContentProvider module. The ContentProvider module is a standard application programming interface (API) for data exchange between different applications. ContentProvider provides data to the outside world in the form of a URI string, allowing other applications to access and modify the data.

[0092] "com.huawei.mail" represents the package name and is used to identify which application owns the file represented by this URI string. This indicates that the file represented by this URI string is owned by the Huawei Mail application.

[0093] "my_images" represents a relative path to this file (specifically, it can be a relative path under the package name directory).

[0094] "IMG_0094.JPG" represents a file name, such as the name of an email attachment. "IMG_0094.JPG" can also be a file name such as default_image.jpg.

[0095] The URI string is configured strictly according to the dedicated access protocol of the ContentProvider module, and thus can represent a globally unique file in the mobile phone 100 .

[0096] The mobile client application can also interact with the file sharing module in the mobile phone 100 to map the sandbox file inside the mailbox application to the shared directory of the file sharing module in the mobile phone 100 .

[0097] The file sharing module is the core of this application. The file sharing module is responsible for the basic operations on the files in the shared directory and for interacting with the ContentProvider module. Specifically, the soft link interface of the file sharing module in the mobile phone 100 is extended so that the soft link interface of the file sharing module in the mobile phone 100 supports soft links in the form of URI strings, and the file sharing module in the mobile phone 100 can interact with the ContentProvider module using the aidl (Android interface definition language) interface to map the internal files of the application in the mobile phone 100 to the shared directory in the file sharing module. For example, the sandbox file of the aforementioned mailbox application is mapped to the shared directory in the file sharing module. The sandbox file inside the mailbox application is mapped to the shared directory of the file sharing module. For example, a soft link can be created for the email attachment as a sandbox file inside the aforementioned mailbox application, and the soft link of the email attachment is stored in the shared directory. The soft link includes the location information of the mailbox application, which can be the absolute path determined according to the URI. And the file sharing module stores the correspondence between the path of the soft link and the fd in the data structure in the file sharing module in the mobile phone 100.

[0098] The file sharing module in mobile phone 100 is further configured to share its shared directory with the shared directory in the file sharing module in PC 200, so that PC 200 can view the shared directory in the file sharing module in PC 200, that is, view the soft link of the email attachment. The file sharing module in mobile phone 100 is further configured to share the correspondence between the path and file directory of the soft link in the file sharing module with the file sharing module in PC 200.

[0099] In addition, the mobile client application can also send the soft link path to the PC client application in PC 200. The PC client application in PC 200 can determine the corresponding soft link and fd based on the soft link path and the soft link in the file sharing module in PC 200, as well as the correspondence between the soft link path and fd, and can access the aforementioned email attachment based on the soft link and fd.

[0100] The application layer in the mobile phone 100 may also include other application programs. In addition, the OS framework layer and the OS layer in the mobile phone 100 may include other functional modules, which will not be described in this application.

[0101] See Figure 4B , Figure 4B A software structure block diagram of a PC 200 is shown as an example.

[0102] The software structure of PC 200 may be an Android-based software structure, including an application layer, an OS framework layer, and an OS layer. The application layer includes a PC client application (the PC client application is an example of a first collaborative application) and a file sharing module (the file sharing module is an example of a first file sharing module).

[0103] The function of the PC client application is to realize the collaborative function between the PC 200 and the mobile phone 100 for establishing a communication connection.

[0104] The PC client application can also access files in the shared directory in the file sharing module in the PC 200 , that is, can access the soft link of the aforementioned email attachment.

[0105] In addition, the PC client application receives the path of the soft link sent by the mobile phone 100, and based on the soft link shared by the file sharing module in the mobile phone 100 in the file sharing module in the PC 200 and the correspondence between the path of the soft link and fd, it can determine the corresponding soft link and fd, and the aforementioned email attachment can be accessed based on the soft link and fd.

[0106] The application layer in the PC 200 may also include other application programs. In addition, the OS framework layer and the OS layer in the PC 200 may include other functional modules, which will not be described in this application.

[0107] In this application, the file sharing module is the core of this application, which is responsible for the basic operations on the files in the shared directory and for interacting with the ContentProvider module. File sharing modules are created in the mobile phone 100 and PC200 respectively, and the file sharing modules in the mobile phone 100 and PC200 will maintain a shared directory. That is, the shared directories under different devices of the mobile phone 100 and PC200 have the same name. The file sharing module has communication and distribution capabilities. On the two devices of the mobile phone 100 and PC200 where the file sharing module is deployed, the contents in the file sharing modules of different devices (including the aforementioned soft links and the correspondence between the paths of the soft links and fd) will be synchronized. The files created in the shared directory of the mobile phone 100 device (such as the aforementioned soft links) can be accessed through the network on PC200, and conversely, the files created on PC200 can also be accessed on the mobile phone 100.

[0108] The file sharing module supports file sharing services. File sharing services are typically presented in the form of a file system and support standard file access interfaces, generally in kernel mode and user mode. In this application, the file sharing module supports operations such as file creation, deletion, reading and writing, and creating soft links to files. Because the file sharing module in this application needs to interact with applications on the device, it is more convenient to implement it at the user level (i.e., the application layer).

[0109] In this application, the mobile phone 100 creates a soft link for the email attachment that the PC 200 requests to access and stores it in a shared directory in the file sharing module in the mobile phone 100, that is, mapping the email attachment to the shared directory, and storing the corresponding relationship between the soft link path and the file directory in the file sharing module in the data structure in the file sharing module. The mobile phone 100 also shares the shared directory and its data structure in the file sharing module of the mobile phone 100 with the file sharing module in the PC 200. The PC 200 can obtain the soft link corresponding to the email attachment of the mobile phone 100 that is requested to be accessed from the shared directory in the file sharing module in the PC 200, and can link to the email attachment based on the soft link. In addition, the PC 200 can determine the file directory required to access the email attachment based on the corresponding relationship between the soft link path and the file directory, thereby enabling the PC 200 to access the email attachment.

[0110] In other implementations of the present application, the software structures of the mobile phone 100 and PC 200 may also be other forms of structures.

[0111] In one implementation of the present application, after the mobile phone 100 and the PC 200 establish an NFC communication connection and the mobile phone 100 and the PC 200 enable a collaborative function between each other, the PC 200 can directly access the sandbox file in the mobile phone 100 .

[0112] See Figure 5A In one implementation of the present application, the mobile phone 100 and the PC 200 establish an NFC communication connection, and the setting interface 201 can be displayed on the display interface of the PC 200. The setting interface 201 includes a "turn on multi-screen collaboration" control. Figure 5A As shown, if PC200 detects (or receives) a user's click operation on the "Turn on multi-screen collaboration" control, for example, PC200 detects that the user clicks the "Turn on multi-screen collaboration" control with the mouse, PC200 sends a collaboration request to the mobile phone 100.

[0113] After receiving the cooperation request from PC 200, mobile phone 100 displays Figure 5AThe display interface shown includes a reminder message 101 "Please confirm whether to allow PC200 to collaborate". If the mobile phone 100 detects that the user clicks the "Confirm" control, the mobile phone 100 sends a response message to the PC200 to agree to collaborate. After PC200 receives the response message, the PC200 and the mobile phone 100 start the collaboration function between the two. PC200 updates the aforementioned setting interface 201 and displays the following Figure 5B The updated setting interface 202 shown in FIG. 20 shows that the PC 200 and the mobile phone 100 have enabled the collaborative function between the two, and the PC 200 can perform collaborative operations on the mobile phone 100 .

[0114] Please continue to see Figure 5B After the PC 200 and the mobile phone 100 start the collaboration function between them, the mobile phone 100 sends the display interface displayed by the mobile phone 100 (for example, the main desktop of the mobile phone 100 displayed by the mobile phone 100) as the first shared interface to the PC 200. The PC 200 receives the first shared interface sent by the mobile phone 100 and displays the following on the display interface of the PC 200: Figure 5B The second sharing interface 2031 corresponding to the first sharing interface is shown as a sharing interface. The user can perform collaborative operations on the mobile phone 100 by operating the second sharing interface 2031 displayed on the PC 200.

[0115] In this implementation, the second sharing interface can be partially identical to the first sharing interface. For example, the second sharing interface 2031 also includes prompt information such as "multi-screen collaboration" at the top compared to the first sharing interface displayed on the mobile phone 100, or the second sharing interface 2031 has a different interface display ratio than the first sharing interface displayed on the mobile phone 100.

[0116] Of course, in other implementations of the present application, the second sharing interface and the first sharing interface may also be completely identical.

[0117] Please continue to see Figure 5B In one implementation of the present application, the second sharing interface 2031 includes an icon and application name corresponding to the mailbox application in the mobile phone 100. If the PC 200 detects that the user clicks on the icon or application name of the mailbox application, the PC 200 opens the mailbox application and displays the following information: Figure 5C The mailbox application interface 2032 shown. The mailbox application interface 2032 includes multiple emails corresponding to the inbox, such as emails from "xxxxxx.@163.com" and emails from "Zhang San" and "Xiao Wang". The mailbox application interface 2032 also includes the receipt time of each email, as well as information and controls such as compose email, search, and more.

[0118] Please continue to see Figure 5CIf the PC 200 detects that the user clicks on the email from "xxxxxx.@163.com" in the mailbox application interface 2032, the PC 200 displays the following Figure 5D The email display interface 2033 shown in FIG. The email display interface 2033 includes the sender information "xxxxxx.@163.com", the recipient information "******.@163.com", and the image file "IMG_0094.JPG" as an email attachment (an email attachment may also be referred to as an email attachment file). In addition, the email display interface 2033 also includes a "Download" control corresponding to the email attachment.

[0119] If PC200 detects that the user clicks the "Download" control corresponding to the "IMG_0094.JPG" image file as an email attachment (a click operation is an example of a triggering operation), PC200 sends an access request to the mobile phone 100. The access request includes the access action information of the user clicking the mouse corresponding to the user's click operation on the "Download" control and the coordinate information of the location where the user clicks on the sharing interface. PC200 requests the mobile phone 100 to obtain the soft link, soft link path, and the correspondence between the soft link path and fd corresponding to the aforementioned email attachment through the access request. Then, PC200 first determines the soft link and fd corresponding to the soft link path based on the obtained soft link path corresponding to the email attachment sent by the mobile phone 100. Then, PC200 can directly access the email attachment based on the soft link and fd. For example, PC200 can directly download the email attachment. After downloading the email attachment, PC200 can display the following information: Figure 5E The display interface shown is that the PC 200 directly opens the "IMG_0094.JPG" picture file that is successfully downloaded as an email attachment.

[0120] The file access method provided by this implementation allows PC200 to directly access the email attachments inside the mailbox application in the mobile phone 100 based on the soft link path, soft link, and the correspondence between the soft link path and fd sent by the mobile phone 100, which can effectively improve the effect of PC200's collaborative operation and interaction with the mobile phone 100, and improve the user experience.

[0121] In another implementation of this application, see Figure 6 , the tablet computer is used as an example of PC200, and PC200 establishes the aforementioned NFC communication connection with the mobile phone 100, and enables the collaborative function between the two.

[0122] See Figure 7AIn another implementation of the present application, PC200 turns on the collaborative function with the mobile phone 100, and PC200 displays the mail display interface 2051 corresponding to the mailbox application. The mail attachment included in the mail display interface 2051 is the document file "meeting file.docx", and the mail display interface 2051 includes a "download" control corresponding to the mail attachment. If PC200 detects that the user clicks on the "download" control, PC200 determines that it has received the user's trigger operation on the mail attachment, and PC200 sends an access request to the mobile phone 100 to obtain the soft link corresponding to the mail attachment, the path of the soft link, and the correspondence between the path of the soft link and fd. Then PC200 downloads the mail attachment according to the soft link, the path of the soft link, and the correspondence between the path of the soft link and fd. After downloading the mail attachment, PC200 can directly open the successfully downloaded mail attachment and display the following information: Figure 7B Document display interface 2052 is shown.

[0123] In another implementation of the present application, the user can edit the document file through PC200. For example, if PC200 detects that the user double-clicks the document display interface 2052, PC200 displays the following Figure 7C The document editing interface 2053 shown in FIG. 20 shows a diagram of a user editing a document file. In addition, if the PC 200 detects that the user clicks the "Finish" control, the PC 200 saves the edited document file.

[0124] In this application, the document file can be a document file in a format such as Word, PPT, TXT, etc., and of course, it can also be a document file of other types.

[0125] The file access method provided by this implementation allows PC200 to directly access the email attachments inside the mailbox application in the mobile phone 100 based on the soft link path, soft link, and the correspondence between the soft link path and fd sent by the mobile phone 100, which can effectively improve the effect of PC200's collaborative operation and interaction with the mobile phone 100, and improve the user experience.

[0126] In this application, PC 200 may also refer to a notebook computer, a small notebook computer, an ultrabook, etc. The manner in which the PC 200 implements sandbox file access with the mobile phone 100 is the same as described above and will not be described in detail here.

[0127] In one implementation of the present application, after the mobile phone 100 and PC 200 establish an NFC communication connection, the mobile phone 100 and PC 200 can enable the collaborative function between the two and share data such as the shared directory in the aforementioned file sharing module, so that PC 200 can directly operate the sandbox file in the mobile phone 100.

[0128] See Figure 8 In one implementation of the present application, the process of enabling the collaboration function between the mobile phone 100 and the PC 200 and sharing data such as a shared directory includes the following steps:

[0129] S101, the PC client application in the PC 200 initiates (sends) a handshake message to the mobile client application in the mobile phone 100 via the NFC communication network between the PC 200 and the mobile phone 100. The handshake message is a request to start a collaborative function between the two.

[0130] S102, after the mobile client application in mobile phone 100 receives the handshake message sent by the PC client application in PC200, it initiates (sends) a confirmation message to the PC client application in PC200 through the NFC communication network, that is, mobile phone 100 sends a message to PC200 to confirm the activation of the collaborative function between the two.

[0131] After receiving the confirmation message, the PC client application in PC 200 starts a collaborative function with the mobile client application in mobile phone 100 .

[0132] Furthermore, in one implementation of the present application, after the mobile phone 100 and the PC 200 start the collaboration function between the two, the PC 200 displays the aforementioned Figure 7A The mobile client application in mobile phone 100 shares a shared interface with mobile phone 100, through which PC 200 can collaboratively operate mobile phone 100. Furthermore, the PC client application in PC 200 and the mobile client application in mobile phone 100 activate their respective file sharing modules to share the aforementioned shared directory and other data. The process by which the file sharing modules in PC 200 and mobile phone 100 share the shared directory and other data includes the following steps:

[0133] At step S103, the file sharing module in PC 200 initiates (sends) a handshake message to the file sharing module in mobile phone 100 via the aforementioned NFC communication network between PC 200 and mobile phone 100. For example, after receiving a request to access a sandbox file from a PC client application, the mobile client application instructs the file sharing module in PC 200 to initiate the handshake message to the file sharing module in mobile phone 100. The process by which the mobile client application receives a request to access a sandbox file from a PC client application will be described later.

[0134] S104 , after receiving the handshake message sent by the file sharing module in the PC 200 , the file sharing module in the mobile phone 100 sends a confirmation message to the file sharing module in the PC 200 via the NFC communication network between the PC 200 and the mobile phone 100 .

[0135] S105: After the file sharing module in PC 200 receives the confirmation message from the file sharing module in mobile phone 100, the file sharing module in PC 200 and the file sharing module in mobile phone 100 are activated, a connection is established between the file sharing module in PC 200 and the file sharing module in mobile phone 100, and data such as a shared directory is shared between the file sharing module in PC 200 and the file sharing module in mobile phone 100. For example, the file sharing module in mobile phone 100 shares the shared directory in the file sharing module with the file sharing module in PC 200, and the file sharing module in PC 200 shares the shared directory in the file sharing module with the file sharing module in mobile phone 100, thereby achieving two-way sharing of the shared directory between PC 200 and mobile phone 100.

[0136] In addition, the file sharing module in the mobile phone 100 can also share the data structure of the file sharing module with the file sharing module of the PC 200 , and the file sharing module in the PC 200 can also share the data structure in the file sharing module with the file sharing module of the mobile phone 100 .

[0137] In another implementation of the present application, the mobile phone 100 can also share the shared directory and other data in the file sharing module in the mobile phone 100 to the PC 200 in real time, so that the PC 200 can obtain the shared directory and other data in the file sharing module in the mobile phone 100 for the aforementioned access to the sandbox file in the mobile phone 100, so as to realize the one-way sharing of the shared directory and other data between the PC 200 and the mobile phone 100.

[0138] In another implementation of the present application, the aforementioned S101 may be that the mobile client application in the mobile phone 100 initiates a handshake message to the PC client application in the PC 200 via the NFC communication network between the mobile phone 100 and the PC 200. The aforementioned S102 may be that after the PC client application in the PC 200 receives the handshake message sent by the mobile client application in the mobile phone 100, it may initiate a confirmation message to the mobile client application in the mobile phone 100 via the NFC communication network to enable the collaborative function between the two.

[0139] In another implementation of the present application, the aforementioned S103 and S104 may also be initiated by the file sharing module in PC200 to initiate a handshake message, and the mobile client application in mobile phone 100 replies with a confirmation message, which will not be repeated here.

[0140] In one implementation of the present application, after the collaboration function is enabled between PC 200 and mobile phone 100, PC 200 can see the shared interface sent by mobile phone 100, and PC 200 can enter the mailbox application of mobile phone 100 through the shared interface sent by mobile phone 100, and open the email attachments in the mailbox application. Figure 7A As shown, the email attachment in the mailbox application includes a document attachment, and the user can click on the email attachment to enable PC 200 to access the email attachment. In this application, PC 200 can directly download, open, and perform other operations on the email attachment in the mailbox application in mobile phone 100.

[0141] See Figure 9 In one implementation of the present application, PC 200 directly operates on the email attachment in mobile phone 100, including the following steps:

[0142] S201, PC200 displays the above Figure 7A The mail display interface 2051 shown in FIG. 200, if the PC client application in the PC 200 detects that Figure 7A As shown, the user clicks the "Download" control corresponding to the email attachment in the mailbox application in the email display interface 2051 corresponding to the mobile client application (the click operation is an example of a triggering operation). The PC client application in PC200 sends an access request to the mobile client application in the mobile phone 100 through the communication channel corresponding to the NFC communication connection established between PC200 and the mobile phone 100, requesting to download and open the email attachment.

[0143] The PC client application sends an access request to the mobile client application. The access request includes the action type and action area information corresponding to the triggering action. The action type information is the aforementioned access action information of the user clicking the "Download" control, and the action area information is the coordinate information of the location where the PC client application detected the user clicking the "Download" control on the shared interface.

[0144] At step S202, the mobile client application receives the access request and, by parsing the received access request, identifies that PC 200 intends to download and open the email attachment. The mobile client application then calls an internal interface to initiate a URI retrieval request to the mailbox application to obtain the URI string corresponding to the email attachment. The URI retrieval request includes identification information for the email attachment, such as the URI "mail@mail.com," indicating that PC 200 intends to download and open the email attachment.

[0145] S203: The mailbox application receives the URI acquisition request, determines the email attachment according to the URI acquisition request, and sends the URI character string corresponding to the email attachment to the mobile client application.

[0146] Because the mobile client application is in the whitelist of the email application, after the email application authorizes the mobile client application, it sends the URI string corresponding to the email attachment to the mobile client application, so that the mobile client application can obtain the URI string normally.

[0147] After the mobile client application obtains the URI string, it uses the URI string as the source path and calls the soft link interface to map the file represented by the URI string to the shared directory maintained by the file sharing module, generating a soft link. The internal implementation of the mobile client calling the soft link to create a soft link includes the following steps:

[0148] S204, after the mobile client application obtains the URI string, it uses the URI string as the source path, calls the soft link interface of the file sharing module in the mobile phone 100, and sends the URI string to the file sharing module in the mobile phone 100.

[0149] The soft link interface may be, for example, a symlink interface.

[0150] S205: The file sharing module in the mobile phone 100 calls the aidl interface provided by the ContentProvider module and sends an fd acquisition request to the ContentProvider module to acquire the fd of the email attachment represented by the URI. The fd acquisition request includes the aforementioned URI string.

[0151] S206: The ContentProvider includes the correspondence between the URI strings and file names (fds) of various files in mobile phone 100. After receiving the third request, the ContentProvider determines the file name (fd) of the email attachment represented by the URI string included in the fd request based on the fd request, and sends the fd to the file sharing module in mobile phone 100, returning the fd to the file sharing module in mobile phone 100. fd is a non-negative integer, such as 1.

[0152] Then, the file sharing module in the mobile phone 100 creates a soft link in the shared directory of the file sharing module, and organizes the path and fd of the soft link into a corresponding relationship and stores them in the data structure of the file sharing module.

[0153] A soft link is a file created in a shared directory. The path of the soft link refers to the path of the file. The file itself points to another file entity. Opening the file actually opens the file it points to, such as a shortcut.

[0154] S207, the shared file module in the mobile phone 100 synchronizes (sends) the soft link of the email attachment in the shared directory in the shared file module to the shared directory in the shared module in PC200 in PC200 through the communication channel between the mobile phone 100 and PC20, and synchronizes the data structure of the file sharing module in the mobile phone 100 to the data structure of the shared module in PC200, so as to realize the sharing and synchronization of data such as the soft link and the correspondence between the soft link path and fd.

[0155] S208 , the mobile phone 100 sends the path of the soft link corresponding to the email attachment to the mobile client application in the mobile phone 100 .

[0156] S209 , the mobile client application sends the path of the soft link of the email attachment to the PC client application in the PC 200 , ie, returns the path of the soft link of the email attachment to the PC client application in the PC 200 .

[0157] S210, after receiving the path of the soft link of the email attachment, the PC client application directly calls the system, so that the system ultimately calls the open interface of the file sharing module in PC 200 and sends an open request to the file sharing module in PC 200, where the open request includes the path of the soft link of the email attachment. The open interface is an interface for opening the email attachment, and the input parameter of the open interface is the path of the soft link, so that the PC client application can access the path of the soft link and determine the soft link corresponding to the path of the soft link from the file sharing module in PC 200.

[0158] S211: After receiving the open request, the file sharing module in PC 200 determines the soft link corresponding to the soft link path in the file sharing module in PC 200 based on the soft link path of the email attachment included in the open request, and determines the file directory (FD) corresponding to the soft link path. The file sharing module in PC 200 then sends the FD to the PC client application.

[0159] After the PC client application in PC200 obtains fd, it can directly read and write the file through the location information of the mailbox file and fd included in the soft link. The location information of the mailbox file can be the absolute path of the mailbox file mentioned above, which can be determined according to the URI mentioned above.

[0160] The file access method provided by this implementation is that the mobile phone 100 creates a soft link for the email attachment that the PC 200 requests to access and stores it in a shared directory in the file sharing module in the mobile phone 100, that is, mapping the email attachment to the shared directory, and storing the correspondence between the soft link path and the file directory in the data structure in the file sharing module in the mobile phone 100. The mobile phone 100 also shares the shared directory, data structure and other data in the file sharing module of the mobile phone 100 with the file sharing module in the PC 200. The PC 200 can obtain the soft link corresponding to the email attachment of the mobile phone 100 that is requested to be accessed from the file sharing module in the PC 200, and can link to the email attachment based on the soft link. In addition, the PC 200 determines the file directory required to access the email attachment based on the soft link, thereby enabling the PC 200 to access the email attachment.

[0161] In another implementation of this application, see Figure 10 After PC 200 and mobile phone 100 establish a network communication connection and enable the collaboration function between the two, PC 200 can create file A as a shared directory in the file sharing module of PC 200 for all sandbox files in PC 200, and mobile phone 100 can create file B as a shared directory in the file sharing module of mobile phone 100 for all sandbox files in mobile phone 100. PC 200 then shares or synchronizes the file metadata of file A as a shared directory in the file sharing module of PC 200 with file B as a shared directory in the file sharing module of mobile phone 100. The file metadata includes the soft link of the aforementioned sandbox file and the correspondence between the path of the soft link and the file directory. Mobile phone 100 shares or synchronizes the file metadata shared by file B as a shared directory in the file sharing module of mobile phone 100 with file A as a shared directory in the file sharing module of PC 200. After PC 200 receives a user's access operation to a sandbox file in mobile phone 100, PC 200 may obtain from mobile phone 100 the path of the soft link corresponding to the sandbox file that PC 200 requested to access, and determine from the file sharing module in PC 200 the soft link and fd to directly access the sandbox file based on the path of the soft link. After mobile phone 100 receives a user's access operation to a sandbox file in PC 200, mobile phone 100 may obtain from PC 200 the path of the soft link corresponding to the sandbox file that mobile phone 100 requested to access, and determine from the file sharing module in mobile phone 100 the corresponding soft link and fd to directly access the file based on the path of the soft link.

[0162] In this implementation, file sharing modules are created in the mobile phone 100 and PC200 respectively, and the shared directories and data structures in the file sharing modules in the mobile phone 100 and the PC200 are shared with each other, so that the file sharing module in the mobile phone 100 and the file sharing module in the PC200 maintain a shared directory, and the shared directories under different devices have the same name. The file sharing module has network communication capabilities and distributed capabilities. On the two devices, mobile phone 100 and PC200, where the file sharing modules are deployed, the file metadata of different devices will be synchronized. The files created in the shared directory of the mobile phone 100 device (such as the aforementioned soft link) can be accessed through the network on PC200, and conversely, the files created on PC200 can also be accessed on the mobile phone 100.

[0163] In some other implementations of the present application, the aforementioned soft link may also be another mapping file (also called a mirror file) corresponding to the sandbox file, and PC 200 may determine the address of the sandbox file based on the mapping file. Of course, the aforementioned fd may also be other file index information required for accessing the sandbox file, and PC 200 may determine the sandbox file to be opened or read or written based on the file index information.

[0164] In this application, the aforementioned mailbox application may also be any other type of application in the mobile phone 100, such as a social application, a web browser application, a video application, a music application, or other multimedia playback application. The aforementioned sandbox file may also be other types of files.

[0165] In this application, sandbox files can be documents, images, and other files corresponding to the application, as well as application configuration files, cached data, database files, etc. Sandbox files can also be called private files of the application.

[0166] In this application, the user triggering operation on the sandbox file detected by PC 200 may be detecting a click of the mouse on the "Download" control corresponding to the sandbox file, detecting a touch operation on the "Download" control corresponding to the sandbox file, detecting a click of the sandbox file, or detecting a swipe operation on the display interface where the sandbox file is located. Correspondingly, the aforementioned operation type information and operation area information may be information corresponding to the triggering operation, which will not be further described here.

[0167] In the present application, the method of enabling the collaborative function between the mobile phone 100 and the PC 200 may also be other methods.

[0168] In this application, the mobile phone 100 and the PC 200 can establish a network communication connection with each other or establish a communication connection based on other types of wireless local area networks (WLAN). The mobile phone 100 and the PC 200 can also establish a short-range communication connection through a "touch and click" method and open the aforementioned collaborative application to enable the collaborative function.

[0169] In this application, a sandbox file may also refer to an application-private file corresponding to an application in an electronic device.

[0170] In this application, the mobile phone 100 may also be an electronic device such as a tablet computer, a wearable device, etc., and the PC 200 may also be other electronic devices such as a television, a smart screen, etc.

[0171] See Figure 11 , Figure 11 The figure shows a schematic diagram of the structure of an electronic device 900 provided according to one embodiment of the present application. The electronic device 900 may include one or more processors 901 coupled to a controller hub 904. For at least one embodiment, the controller hub 904 communicates with the processor 901 via a multi-drop bus such as a front-side bus (FSB), a point-to-point interface such as a QuickPath Interconnect (QPI), or a similar connection. The processor 901 executes instructions that control general types of data processing operations. In one embodiment, the controller hub 904 includes, but is not limited to, a graphics memory controller hub (GMCH) (not shown in the figure) and an input / output hub (IOH) (which may be on a separate chip) (not shown in the figure), wherein the GMCH includes a memory and a graphics controller and is coupled to the IOH.

[0172] The electronic device 900 may also include a coprocessor 906 and a memory 902 coupled to the controller hub 904. Alternatively, one or both of the memory 902 and the GMCH may be integrated within the processor 901 (as described herein), with the memory 902 and the coprocessor 906 coupled directly to the processor 901 and the controller hub 904, with the controller hub 904 being in a single chip with the IOH.

[0173] The memory 902 may be, for example, a dynamic random access memory (DRAM), a phase change memory (PCM), or a combination of the two.

[0174] In one embodiment, the coprocessor 906 is a special-purpose processor, such as, for example, a high-throughput Many Integrated Core (MIC) processor, a network or communication processor, a compression engine, a graphics processor, a general-purpose graphics processing unit (GPGPU), or an embedded processor. The optional nature of the coprocessor 906 is indicated by a dashed line in FIG. Figure 11 middle.

[0175] In one embodiment, the electronic device 900 may further include a network interface card (NIC) 903. The network interface 903 may include a transceiver for providing a radio interface for the electronic device 900, thereby communicating with any other suitable device (such as a front-end module, antenna, etc.). In various embodiments, the network interface 903 may be integrated with other components of the electronic device 900. The network interface 903 may implement the functions of the communication unit in the above-mentioned embodiments.

[0176] The electronic device 900 may further include input / output (I / O) devices 905. The I / O devices 905 may include: a user interface designed to enable a user to interact with the electronic device 900; a peripheral component interface designed to enable peripheral components to interact with the electronic device 900; and / or sensors designed to determine environmental conditions and / or location information related to the electronic device 900.

[0177] It is worth noting that Figure 11 This is for illustrative purposes only. Figure 11 It is shown that the electronic device 900 includes multiple devices such as a processor 901, a controller hub 904, a memory 902, etc. However, in actual applications, the devices using the methods of the present application may only include a part of the devices of the electronic device 900, for example, it may only include the processor 901 and the NIC 903. Figure 11 The properties of the optional devices are shown with dotted lines.

[0178] One or more tangible, non-transitory computer-readable media for storing data and / or instructions may be included in the memory of the electronic device 900. The computer-readable storage medium stores instructions, and more specifically, stores temporary and permanent copies of the instructions.

[0179] In the present application, the electronic device 900 may be a terminal device such as a mobile phone, a tablet computer, a personal digital assistant (PDA), or a desktop computer. The instructions stored in the memory of the electronic device may include instructions that, when executed by at least one unit in the processor, cause the electronic device to implement the file access method mentioned above.

[0180] See Figure 12 , Figure 12 FIG2 is a schematic diagram of the structure of a SoC (System on Chip) 1000 provided according to an embodiment of the present application. Figure 12 1000. Similar components have the same reference numerals. Furthermore, dashed boxes indicate optional features of a more advanced SoC 1000. The SoC 1000 can be used in any electronic device according to the present application, and can implement corresponding functions depending on the device in which it is used and the instructions stored therein.

[0181] exist Figure 12 In the embodiment, SoC 1000 includes: an interconnect unit 1002 coupled to a processor 1001; a system agent unit 1006; a bus controller unit 1005; an integrated memory controller unit 1003; a set of one or more coprocessors 1007, which may include integrated graphics logic, an image processor, an audio processor, and a video processor; a static random access memory (SRAM) unit 1008; and a direct memory access (DMA) unit 1004. In one embodiment, the coprocessor 1007 includes a special-purpose processor, such as a network or communication processor, a compression engine, a GPGPU, a high-throughput MIC processor, or an embedded processor.

[0182] The SRAM unit 1008 may include one or more computer-readable media for storing data and / or instructions. The computer-readable storage medium may store instructions, specifically, temporary and permanent copies of the instructions. The instructions may include instructions that, when executed by at least one unit in the processor 1001, cause the electronic device to implement the file access method described above.

[0183] It should be noted that the terms "first", "second", etc. are only used for distinction and description, and cannot be understood as indicating or implying relative importance.

[0184] It should be noted that in the accompanying drawings, some structural or method features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be required. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. In addition, the inclusion of structural or method features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may not be included or may be combined with other features.

[0185] Although the present application has been illustrated and described with reference to certain preferred embodiments of the present application, those skilled in the art will appreciate that the above descriptions are provided as further details of the present application in conjunction with specific embodiments, and that the specific implementation of the present application should not be limited to these descriptions. Those skilled in the art may make various changes in form and detail, including simple deductions or substitutions, without departing from the spirit and scope of the present application.

Claims

1. A file access method, characterized in that: Applicable to a communication system comprising a first electronic device and a second electronic device, The method comprises: The first electronic device sends a handshake message to the second electronic device, wherein the handshake message is a request to enable a collaborative function between the first electronic device and the second electronic device; After receiving the handshake message, the second electronic device sends a confirmation message to the first electronic device; After the first electronic device receives the confirmation message, the first electronic device and the second electronic device establish a communication connection, wherein the communication connection is used to enable a collaborative function between the first electronic device and the second electronic device; The first electronic device displays the sharing interface sent by the second electronic device, where the sharing interface includes a sandbox file corresponding to the application in the second electronic device; The first electronic device receives a user triggering operation on the sandbox file and sends an access request to the second electronic device; The second electronic device receives the access request and determines, according to the access request, mapping information corresponding to the sandbox file, the mapping information including a mapping file corresponding to the sandbox file, a path of the mapping file, and a correspondence between the path of the mapping file and file index information of the sandbox file; The second electronic device sends the mapping information to the first electronic device; The first electronic device receives the mapping information and accesses the sandbox file corresponding to the application in the second electronic device according to the mapping information.

2. The file access method according to claim 1, wherein: The second electronic device determines, according to the access request, mapping information corresponding to the sandbox file, including: The second electronic device determines the sandbox file according to the access request; The second electronic device determines a uniform resource identifier corresponding to the sandbox file, and determines file index information corresponding to the uniform resource identifier according to the uniform resource identifier; The second electronic device determines the mapping information according to the uniform resource identifier and the file index information.

3. The file access method according to claim 1, wherein: The first electronic device accessing the sandbox file according to the mapping information includes: The first electronic device determines the mapping file and the file index information according to the path of the mapping file; The first electronic device accesses the sandbox file according to the mapping file and the file index information.

4. The file access method according to any one of claims 1 to 3, characterized in that: The mapping file is a soft link file, and the mapping file includes the location information of the sandbox file.

5. The file access method according to any one of claims 1 to 3, characterized in that: The file index information is a file descriptor.

6. The file access method according to any one of claims 1 to 3, characterized in that: The access request includes operation type information and operation area information corresponding to the trigger operation.

7. A file access method, characterized in that: Applied to a communication system including a first electronic device and a second electronic device, the method includes: The first electronic device sends a handshake message to the second electronic device, wherein the handshake message is a request to enable a collaborative function between the first electronic device and the second electronic device; After receiving the handshake message, the second electronic device sends a confirmation message to the first electronic device; After the first electronic device receives the confirmation message, the first electronic device and the second electronic device establish a communication connection, wherein the first electronic device includes a first collaborative application and a first file sharing module, and the second electronic device includes a second collaborative application, a second file sharing module, and a target operation application, and the communication connection is used to enable a collaborative function between the first electronic device and the second electronic device; The first coordinated application displays the shared interface of the second electronic device sent by the second coordinated application, where the shared interface includes a sandbox file corresponding to the target operating application in the second electronic device; The first collaborative application receives a user trigger operation on the sandbox file and sends an access request to the second collaborative application; The second collaborative application receives the access request and, based on the access request, causes the second file sharing module to determine mapping information corresponding to the sandbox file, the mapping information including a mapping file corresponding to the sandbox file, a path of the mapping file, and a correspondence between the path of the mapping file and file index information of the sandbox file; The second file sharing module sends the mapping file and the correspondence between the path of the mapping file and the file index information of the sandbox file to the first file sharing module, and the second file sharing module sends the path of the mapping file to the second collaborative application; The second collaborative application sends the path of the mapping file to the first collaborative application; The first collaborative application receives the path of the mapping file, determines the mapping file and the file index information corresponding to the path of the mapping file from the second file sharing module according to the path of the mapping file, and accesses the sandbox file corresponding to the target operation application in the second electronic device according to the mapping file and the file index information.

8. The file access method according to claim 7, wherein: The second electronic device further includes a content provider module, and the second collaborative application causes the second file sharing module to determine mapping information corresponding to the sandbox file according to the access request, including: The second collaborative application determines the sandbox file according to the access request; The second collaborative application obtains a uniform resource identifier corresponding to the sandbox file from the target operation application corresponding to the sandbox file, and sends the uniform resource identifier to the second file sharing module; The second file sharing module receives the uniform resource identifier and obtains file index information corresponding to the uniform resource identifier from the content provider module according to the uniform resource identifier; The second file sharing module generates the mapping file based on the uniform resource identifier and the file index information and stores it in the shared directory of the second file sharing module, determines the path of the mapping file, and determines the correspondence between the path of the mapping file and the file index information and stores it in the data structure of the second file sharing module.

9. The file access method according to claim 8, wherein: The method further comprises: The second collaborative application calls the soft link interface of the second file sharing module to send the uniform resource identifier to the second file sharing module so that the second file sharing module determines the mapping information.

10. The file access method according to claim 8, wherein: The second file sharing module obtains file index information corresponding to the uniform resource identifier from the content provider module according to the uniform resource identifier through the Android interface definition language interface of the content provider module.

11. The file access method according to any one of claims 7 to 10, characterized in that: The mapping file is a soft link file, and the mapping file includes the location information of the sandbox file.

12. The file access method according to any one of claims 7 to 10, characterized in that: The file index information is a file descriptor.

13. The file access method according to any one of claims 7 to 10, characterized in that: The access request includes operation type information and operation area information corresponding to the trigger operation.

14. A file access method, characterized in that: Applied to a first electronic device, the method includes: The first electronic device sends a handshake message to the second electronic device, wherein the handshake message is a request to enable a collaborative function between the first electronic device and the second electronic device; After the first electronic device receives the confirmation message sent by the second electronic device, the first electronic device establishes a communication connection with the second electronic device, wherein the communication connection is used to enable a collaborative function between the first electronic device and the second electronic device; The first electronic device displays the sharing interface sent by the second electronic device, where the sharing interface includes a sandbox file corresponding to the application in the second electronic device; The first electronic device receives a user triggering operation on the sandbox file and sends an access request to the second electronic device; The first electronic device receives the mapping information sent by the first electronic device, and accesses the sandbox file corresponding to the application in the second electronic device according to the mapping information. The mapping information is the information corresponding to the sandbox file determined by the second electronic device according to the access request. The mapping information includes the mapping file corresponding to the sandbox file, the path of the mapping file, and the correspondence between the path of the mapping file and the file index information of the sandbox file.

15. A file access method, characterized in that: Applied to a second electronic device, the method includes: After receiving the handshake message sent by the first electronic device, the second electronic device sends a confirmation message to the first electronic device; After the first electronic device receives the confirmation message, the second electronic device establishes a communication connection with the first electronic device, wherein the communication connection is used to enable a collaborative function between the second electronic device and the first electronic device; The second electronic device receives the access request sent by the first electronic device, and determines, based on the access request, mapping information corresponding to the sandbox file requested to be accessed by the first electronic device, the mapping information including a mapping file corresponding to the sandbox file, a path of the mapping file, and a correspondence between the path of the mapping file and file index information of the sandbox file, the access request being a request generated by the first electronic device receiving a user's triggering operation on the sandbox file, and the sandbox file being a file corresponding to an application in the second electronic device included in a sharing interface sent by the second electronic device and displayed by the first electronic device; The second electronic device sends the mapping information to the first electronic device, so that the first electronic device accesses the sandbox file corresponding to the application in the second electronic device according to the mapping information.

16. A communication system, characterized in that: comprising a first electronic device and a second electronic device, The first electronic device is used to send a handshake message to the second electronic device, wherein the handshake message is a request to enable a collaborative function between the first electronic device and the second electronic device; The second electronic device is configured to send a confirmation message to the first electronic device after receiving the handshake message; After the first electronic device receives the confirmation message, the first electronic device and the second electronic device establish a communication connection; The first electronic device is used to display the sharing interface sent by the second electronic device, where the sharing interface includes a sandbox file corresponding to the application in the second electronic device; The first electronic device is further configured to receive a user trigger operation on the sandbox file and send an access request to the second electronic device; The second electronic device is configured to receive the access request and determine, based on the access request, mapping information corresponding to the sandbox file, the mapping information including a mapping file corresponding to the sandbox file, a path of the mapping file, and a correspondence between the path of the mapping file and file index information of the sandbox file; The second electronic device is further configured to send the mapping information to the first electronic device; The first electronic device is further configured to receive the mapping information and access the sandbox file corresponding to the application in the second electronic device according to the mapping information.

17. An electronic device, characterized in that: include: a memory for storing a computer program, wherein the computer program includes program instructions; A control component for executing program instructions to enable the electronic device to execute the file access method as described in any one of claims 1 to 6, or to enable the electronic device to execute the file access method as described in any one of claims 7 to 13, or to enable the electronic device to execute the file access method as described in claim 14, or to enable the electronic device to execute the file access method as described in claim 15.

18. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which includes program instructions. The program instructions are executed by a computer to enable the electronic device to execute the file access method described in any one of claims 1 to 6, or to enable the electronic device to execute the file access method described in any one of claims 7 to 13, or to enable the electronic device to execute the file access method described in claim 14, or to enable the electronic device to execute the file access method described in claim 15.

Images