CN114546969A

CN114546969A - File sharing method and device and electronic equipment

Info

Publication number: CN114546969A
Application number: CN202110051249.5A
Authority: CN
Inventors: 陈念; 陈群华; 李岳朋
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-11-24
Filing date: 2021-01-14
Publication date: 2022-05-27
Also published as: WO2022111469A1

Abstract

The application provides a file sharing method, a file sharing device and electronic equipment, wherein in the method, an installation package of a first application program is obtained, wherein the installation package of the first application program comprises a first file and a first identifier, and the first identifier indicates that a shared object of the first file comprises a second application program; and providing the access right of the first file to the second application program according to the first identification. Implementing the method may cause a specified application (e.g., application B) to share files specified in application a. In this way, data sharing between applications can be achieved, and sharing of sharable files of one application by all applications and sharing of all data of one application by other applications can be avoided.

Description

File sharing method and device and electronic equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a file sharing method and apparatus, and an electronic device.

Background

Electronic devices such as personal computers and smart phones have become an indispensable part of people's lives. A plurality of applications are typically installed on these electronic devices. The plurality of application programs can provide a plurality of services such as weather information, shopping, instant messaging, photographing and the like for the user. Each application typically stores data related to the operation of the application in a directory of the file system of the electronic device. The application program can access the stored related data according to the running requirement.

In order to ensure the stability and the safety of the operation of the whole system. Typically, the operating system of the electronic device will provide an application sandbox mechanism for each application in the electronic device. The sandbox mechanism is a security mechanism that provides an isolated environment for running programs. That is, each application program can only access the data of the application program, and cannot access the data of other application programs. By adopting the safety mechanism, certain application programs can be prevented from maliciously accessing data of other application programs. In practice, however, data needs to be shared between some applications, for example, application B needs to share application a data (e.g., a file of application a stored in the file system of the electronic device). But sharing data between applications is difficult due to the security mechanisms of the operating system in the electronic device.

Therefore, how to share data between applications safely and conveniently is a problem to be solved urgently.

Disclosure of Invention

By the method, the specified file can be shared to the specified application program, and the file used for sharing can be prevented from being maliciously accessed by other application programs. Therefore, data can be safely and conveniently shared among the application programs.

In a first aspect, the present application provides a file sharing method, which may include: acquiring an installation package of a first application program, wherein the installation package of the first application program comprises a first file and a first identifier, and the first identifier indicates that a shared object of the first file comprises a second application program; and providing the access right of the first file to the second application program according to the first identification.

By implementing the file sharing method provided by the first aspect, the specified file can be shared to the specified application. And the electronic equipment only needs to establish a sharing relation according to the first identifier in the installation package of the first application program and provide the access right of the first file. When the user uses the electronic equipment, no additional operation is needed to set the sharing authority of the first file. If the other application programs of the electronic equipment are not the shared objects of the first file indicated by the first identification, the other application programs of the electronic equipment do not have the authority of accessing the first file. In this way, malicious access of the first file by other applications may be avoided. Therefore, data sharing between the application programs can be safely and conveniently carried out.

In one possible implementation manner, providing access rights of the first file to the second application program according to the first identifier includes: reading a first identifier when the electronic equipment installs the first application program according to the installation package of the first application program; and providing the access right of the first file to the second application program according to the first identifier.

In a possible implementation manner, providing access to the first file to the second application according to the first identifier includes: and adding the second application program into a sharing group of the first file according to the first identification, wherein the sharing group is used for indicating the application programs with the authority of accessing the first file.

In one possible implementation manner, adding the identifier of the second application program to the shared group of the first file according to the first identifier includes: when the first identification is determined to contain the identification of the second application program, adding the second application program into the sharing group of the first file; the identifier of the second application program comprises an identifier carried in an installation package of the second application program.

Further, the identifier of the second application program may be a public key of the second application program, and when it is determined that the identifier of the second application program is included in the first identifier, the second application program is added to the shared group of the first file, specifically, the method includes: and when the public key of the second application program is determined to be contained in the first identification, adding the public key of the second application program into the sharing group of the first file.

In one possible implementation manner, adding the second application to the shared group of the first file according to the first identifier includes: and adding the identifier of the second application program into the sharing group of the first file according to the first identifier, wherein the identifier of the second application program comprises the identifier which is allocated to the second application program by the electronic equipment when the second application program is installed.

Further, the identification of the second application may be a UID assigned to the second application by the electronic device. The UID of each application in the electronic device is unique. UIDs for the same application in different electronic devices may be different. In this way, the identifier of the other application program can be effectively prevented from being tampered with as the identifier of the second application program. Therefore, malicious access of the first file by other application programs can be effectively reduced. In this way, security for data sharing between applications may be provided.

In one possible implementation manner, adding the identifier of the second application program to the shared group of the first file according to the first identifier includes: when the second application program is installed, the identifier of the second application program is distributed to the first application program; and adding the identifier of the second application program into the sharing group of the first file according to the first identifier.

In a possible implementation manner, before adding the identifier of the second application program to the shared group of the first file according to the first identifier, the method further includes: when the first application program is installed, establishing a sharing relation indicated in the first identifier; the sharing relationship indicates that the shared object of the first file includes the second application.

In a possible implementation manner, after providing the access right of the first file to the second application program according to the first identifier, the method further includes: receiving an access request of a second application program to the first file; confirming that the second application program has the access right of the first file; the data of the first file is provided to the second application.

In a second aspect, there is provided a file sharing apparatus, which may include:

an acquisition module, operable to: acquiring an installation package of a first application program, wherein the installation package of the first application program comprises a first file and a first identifier, and the first identifier indicates that a shared object of the first file comprises a second application program;

a permission setting module operable to: and providing the access right of the first file to a second application program according to the first identifier.

In one possible implementation, the permission setting module may be configured to:

and adding the second application program into a sharing group of the first file according to the first identifier, wherein the sharing group is used for indicating the application program with the authority of accessing the first file.

When the first identification is determined to contain the identification of the second application program, adding the second application program into the sharing group of the first file; the identifier of the second application program comprises an identifier carried in an installation package of the second application program. E.g. the public key of the second application.

an identification of the second application is added to the shared group of the first file based on the first identification, the identification of the second application including an identification assigned to the second application when the second application is installed, such as a UID of the second application.

when the second application program is installed, the identifier of the second application program is distributed to the second application program;

and adding the identifier of the second application program into the sharing group of the first file according to the first identifier.

when the first application program is installed, establishing a sharing relation indicated in the first identifier; the sharing relationship describes that the shared object of the first file comprises the second application program.

In a possible implementation manner, the obtaining module may be further configured to: receiving an access request of a second application program to the first file; the permission setting module may be further operable to: confirming that the second application program has the access right of the first file;

The file sharing apparatus may further include: providing a module for: the data of the first file is provided to the second application.

The file sharing apparatus provided in the second aspect may add the second application program to the shared group of the first file in the installation package of the first application program according to the first identifier in the installation package of the first application program. The second application has access to the first file. In this way, the first file may be shared not only with the designated application. And preventing other application programs in the file sharing device from maliciously accessing the file. The second application can only access the first file in the first application, and not all files of the first application. In this way, the normal operation of the first application program can be prevented from being influenced.

In a third aspect, the present application provides an electronic device, comprising: a processor and a memory; the memory is used for storing program codes, and the processor is used for calling the program codes to enable the electronic equipment to execute the file sharing method in any one of the possible implementation modes of the above aspects.

In a fourth aspect, a computer program product is provided, which includes instructions, when executed on an electronic device, to cause the electronic device to perform the file sharing method in any one of the possible implementations of the above aspects.

In a fifth aspect, a computer-readable storage medium is provided, which includes instructions, when the instructions are executed on an electronic device, so that the electronic device executes a file sharing method in any one of the possible implementation manners of the foregoing aspects.

Drawings

Fig. 1 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;

FIG. 2 is a software block diagram of an electronic device provided in an embodiment of the present application;

FIG. 3 is a flowchart of an application development and installation process provided by an embodiment of the present application;

FIG. 4 is a block diagram of a logic implementation of a file sharing method according to an embodiment of the present application;

fig. 5 is a schematic flowchart of a file sharing method according to an embodiment of the present application;

fig. 6 is a schematic flowchart of a file sharing method according to an embodiment of the present application;

fig. 7 is a schematic flowchart of a file sharing method according to an embodiment of the present application;

fig. 8 is a schematic diagram of a file sharing apparatus according to an embodiment of the present application.

Detailed Description

The terminology used in the following embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in the specification of the present application and the appended claims, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the listed items.

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of embodiments of the application, unless stated otherwise, "plurality" means two or more.

In order to enable data sharing between applications, in some embodiments, when a developer develops an application a, a developer may add a uifilesharingenabled (application supported files sharing) key to a file info. Then, the developer puts the file a that can be shared in the application a under the documents directory in the electronic device. In this way, other applications can access data in file A of application A.

In the above embodiment, the file a of the application a may be shared. However, the application programs that start the file sharing function in the electronic device can share the file a. Thus, the applications that can share file a are not sufficiently singular.

In still other embodiments, to enable data sharing between application A and application B. The developer may set shareduserID in the manifest. When the electronic device installs the application program, the same user ID, that is, UID, is assigned to the application program having the same shareduserID. Thus, application A and application B can access data from one another. Application B can access all data of application a. Thus, application B can access all data of application a, and if it receives improper operation with application B, it may affect the normal operation of application a.

The application provides a file sharing method and electronic equipment, and the method can enable a designated application program (such as an application program B) to share a file designated in an application program A. In this way, data sharing between applications can be achieved, and sharing of sharable files of one application by all applications and sharing of all data of one application by other applications can be avoided. The following describes a file sharing method and an electronic device provided in an embodiment of the present application in detail with reference to the accompanying drawings.

An exemplary electronic device 100 provided by embodiments of the present application is first described.

Fig. 1 is a schematic structural diagram of an electronic device 100 according to an embodiment of the present application.

The following describes an embodiment specifically by taking the electronic device 100 as an example. It should be understood that electronic device 100 may have more or fewer components than shown, may combine two or more components, or may have a different configuration of components. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

The electronic device 100 may include: the mobile terminal includes a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 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 screen 194, a Subscriber Identity Module (SIM) card interface 195, and the like. 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, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or combine certain components, or split certain components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: 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 memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

The controller may be, among other things, a neural center and a command center of the electronic device 100. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K via an I2C interface, such that the processor 110 and the touch sensor 180K communicate via an I2C bus interface to implement the touch functionality of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to implement a function of answering a call through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a bluetooth headset.

MIPI interfaces may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the capture functionality of electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

The SIM interface may be used to communicate with the SIM card interface 195, implementing functions to transfer data to or read data from the SIM card.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transmit data between the electronic device 100 and a peripheral device. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The interface may also be used to connect other electronic devices, such as AR devices and the like.

It should be understood that the connection relationship between the modules according to the embodiment of the present invention is only illustrative, and is not limited to the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160 so that electronic device 100 can communicate with networks and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. 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).

The electronic device 100 implements display functions via the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, with N being a positive integer greater than 1.

The electronic device 100 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 100 can be realized through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The internal memory 121 may include one or more Random Access Memories (RAMs) and one or more non-volatile memories (NVMs).

The random access memory may include static random-access memory (SRAM), dynamic random-access memory (DRAM), synchronous dynamic random-access memory (SDRAM), double data rate synchronous dynamic random-access memory (DDR SDRAM), such as fifth generation DDR SDRAM generally referred to as DDR5 SDRAM, and the like;

the nonvolatile memory may include a magnetic disk storage device, a flash memory (flash memory).

The FLASH memory may include NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. according to the operation principle, may include single-level cell (SLC), multi-level cell (MLC), three-level cell (TLC), four-level cell (QLC), etc. according to the level order of the memory cell, and may include universal FLASH memory (UFS), embedded multimedia memory Card (eMMC), etc. according to the storage specification.

The random access memory may be read and written directly by the processor 110, may be used to store executable programs (e.g., machine instructions) of an operating system or other programs in operation, and may also be used to store data of users and applications, etc.

The nonvolatile memory may also store executable programs, data of users and application programs, and the like, and may be loaded into the random access memory in advance for the processor 110 to directly read and write.

The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The electronic apparatus 100 can listen to music through the speaker 170A or listen to a handsfree call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the electronic apparatus 100 receives a call or voice information, it can receive voice by placing the receiver 170B close to the ear of the person.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, perform directional recording, and so on.

The headphone interface 170D is used to connect a wired headphone. The headset interface 170D may be the USB interface 130, or may be a 3.5mm open mobile electronic device platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A can be of a wide variety, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic apparatus 100 may also calculate the touched position from the detection signal of the pressure sensor 180A. In some embodiments, the touch operations that are applied to the same touch position but different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

The gyro sensor 180B may be used to determine the motion attitude of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., the x, y, and z axes) may be determined by gyroscope sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects a shake angle of the electronic device 100, calculates a distance to be compensated for by the lens module according to the shake angle, and allows the lens to counteract the shake of the electronic device 100 through a reverse movement, thereby achieving anti-shake. The gyroscope sensor 180B may also be used for navigation, somatosensory gaming scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude, aiding in positioning and navigation, from barometric pressure values measured by barometric pressure sensor 180C.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip holster using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the opening and closing state of the leather sheath or the opening and closing state of the flip cover, the automatic unlocking of the flip cover is set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity can be detected when the electronic device 100 is stationary. The method can also be used for recognizing the posture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, taking a picture of a scene, electronic device 100 may utilize range sensor 180F to range for fast focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light to the outside through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there are no objects near the electronic device 100. The electronic device 100 can utilize the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear for talking, so as to automatically turn off the screen to achieve the purpose of saving power. The proximity light sensor 180G may also be used in a holster mode, a pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense ambient light brightness. Electronic device 100 may adaptively adjust the brightness of display screen 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 180L may also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 can utilize the collected fingerprint characteristics to unlock the fingerprint, access the application lock, photograph the fingerprint, answer an incoming call with the fingerprint, and so on.

The temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 implements a temperature processing strategy using the temperature detected by temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 performs a reduction in performance of a processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, the electronic device 100 heats the battery 142 when the temperature is below another threshold to avoid the low temperature causing the electronic device 100 to shut down abnormally. In other embodiments, when the temperature is lower than a further threshold, the electronic device 100 performs boosting on the output voltage of the battery 142 to avoid abnormal shutdown due to low temperature.

The touch sensor 180K is also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation acting thereon or nearby. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 194. In other embodiments, the touch sensor 180K may be disposed on a surface of the electronic device 100, different from the position of the display screen 194.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic apparatus 100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic apparatus 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be attached to and detached from the electronic device 100 by being inserted into the SIM card interface 195 or being pulled out of the SIM card interface 195. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as communication and data communication.

Fig. 2 is a block diagram of a software structure of the electronic device 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the system is divided into four layers, an application layer, an application framework layer, a Runtime (Runtime) and system library, and a kernel layer, from top to bottom.

The application layer may include a series of application packages.

As shown in fig. 2, the application package may include applications (also referred to as applications) such as camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, package manager, meta-capability manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions for the electronic device 100. Such as management of call status (including connection, hangup, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog interface. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

A package Manager (Bundle Manager) may provide a package management Service (BMS) for the application. The BMS can be used for realizing the functions of application installation and uninstallation, component query matching, authority management and the like. When the application program is installed, the BMS can verify the integrity of the installation package of the application program through a cloud public key preset in the device. The BMS may also be configured to decompress the installation package of the application to obtain the public key publicity of the application. The BMS may query whether the application can share files of other applications according to the public key of the application. If so, the BMS may add the UID of the application to the group of users that may share the file.

A meta-capability Manager (property Manager) may provide a meta-capability management Service (AMS) for an application. AMS may be used for application lifecycle management. For example, the AMS may be primarily responsible for the pulling, management, destruction, etc. of application processes.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), two-dimensional graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provides a fusion of two-Dimensional (2-Dimensional, 2D) and three-Dimensional (3-Dimensional, 3D) layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing 3D graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The kernel layer at least comprises a display driver, a camera driver, an audio driver, a sensor driver and a virtual card driver.

The following describes exemplary workflow of the software and hardware of the electronic device 100 in connection with capturing a photo scene.

When the touch sensor 180K receives a touch operation, a corresponding hardware interrupt is issued to the kernel layer. The kernel layer processes the touch operation into an original input event (including touch coordinates, a time stamp of the touch operation, and other information). The raw input events are stored at the kernel layer. And the application program framework layer acquires the original input event from the kernel layer and identifies the control corresponding to the input event. Taking the touch operation as a touch click operation, and taking a control corresponding to the click operation as a control of a camera application icon as an example, the camera application calls an interface of an application framework layer, starts the camera application, further starts a camera drive by calling a kernel layer, and captures a still image or a video through the camera 193.

In the embodiment of the present application, the application a may be referred to as a first application, and the application B may be referred to as a second application. File a may be referred to as a first file.

The method in the embodiments of the present application will be described in detail below with reference to the hardware and software mechanisms of the exemplary electronic device 100. The embodiment of the application provides a file sharing method. In the method, an identifier for sharing the file A to the application program B is written in an installation package of the application program A. When the application program A and the application program B are installed in the mobile phone, the mobile phone can add the identifier of the application program B into the sharing group of the sharable file A. Thus, application B can access file A at runtime. In the embodiment of the present application, the application program may also be simply referred to as an application.

The file A can be shared with the application program B, namely, the application program B can access the file A, read the data of the file A and execute the file A. Applications in the shared group for file a may each access file a.

Firstly, the process from application development and uploading to the application market to application downloading from the application market by the mobile phone is briefly described with reference to the attached drawings. As shown in fig. 3. Taking application B as an example, the application development and uploading to the application market, and the downloading of the application from the application market to the mobile phone may include the following steps:

A. application development and upload to application marketplace

1. The developer generates a public-private key pair, public key publickeyB and private key privatekeyB for application B.

The developer of application B may develop a public-private key pair for application B in the device in which application B is developed. Such as application B public-private key pair 301 shown in fig. 3. Public-private key pair 301 may include a public key publickeyB and a private key privatekeyB. It will be appreciated that the public and private keys are presented in pairs, which can decrypt each other. The public key can decrypt the encrypted content, and only the private key can decrypt the encrypted content. The private key encrypts the content, and only the public key can decrypt the content. Encrypting a public key and decrypting a private key; private key signature, public key verification. The public key is open to the outside and the private key is kept secret. The terminal may obtain the public key of the application from the installation package of the application.

2. The developer applies for the signed certificate of application B to the application marketplace.

The developer may upload the public key of the application program B to the application market to apply for the corresponding application signature certificate. Such as application B signing certificate 302 shown in fig. 3. The public key publickeyB of the application B may be included in the application B signature certificate. The signature certificate of the application B can be used to identify the developer identity, and can also contain basic developer information.

The application market, also called APP STORE, is an electronic application STORE that provides fee-charging or free game and application download services for electronic devices such as mobile devices, mobile phones, tablet computers, and the like.

3. And developing the application B by a developer to obtain a source program package of the application B.

The developer develops application B and gets a source package for application B, such as source package 303 for application B shown in fig. 3. The source package may contain a plurality of files, each of which may contain source code written in a particular format.

4. And the developer carries out self-signing on the application program B to obtain the on-shelf installation package of the application program B.

And the developer carries out self-signature on the application program B by using the private key privatekeyB of the application program B to obtain self-signature information signatureB. And the developer puts the self-signature information signatureB and the public key publickeyB into the program package of the application program B to obtain the on-shelf installation package of the application program B. Such as the on-shelf installation package 304 for application B shown in fig. 3.

5. And the developer signs the installation package on the shelf of the application program B by using a private key of the application market to obtain a downloading installation package of the application program B.

The developer uploads the on-shelf installation package of application B to the application marketplace. And the application market signs the on-shelf installation package of the application program B by using an application market private key to obtain signature information signature. Applying the market and putting the signature information signature into an on-shelf installation package of the application program B to form a download installation package of the application program B. For example, the download installation package 306 of application B shown in fig. 3.

The application market holds a pair of uniform public and private keys. Such as application market public and private key pair 305 shown in fig. 3. The application market public and private key pair 305 may include an application market public key and an application market private key. When all the application programs are uploaded to the application market, the application market can sign the uploaded installation package of the application programs by using the private key to obtain signature information. The public key of the application market can verify the signature information.

B. Downloading and installing application program from application market by mobile phone

6. The mobile phone downloads the download installation package of the application program B from the application market, takes out the signature in the download installation package of the application program B, uses the application market public key stored in the mobile phone to check the signature, after the signature passes, the mobile phone takes out the publickeyB in the download installation package to check the signature of the signatureB, and if the signature is successfully checked, the application program B can be installed.

After the mobile phone downloads the download installation package of the application program B from the application market, the BMS in the mobile phone can take out the signature information signature in the download installation package of the application program B, and the signature of the signature information signature can be verified by using an application market public key preset in the mobile phone. When the download installation package of the application program B is tampered, signature information signature verification in the download installation package of the application program B may fail. If the signature verification fails, the mobile phone fails to install the download installation package, and the installation is quitted. And if the verification label passes, the source of the downloaded installation package of the application program is legal.

And after the signature information signature check passes, the BMS in the mobile phone takes out the self-signature information signature B and the public key publickey B in the download installation package of the application program B. And the BMS checks the self-signature information signatureB through the public key publickeyB. And if the verification passes, the mobile phone can successfully install the application program B. The source package, the self-signature information signatureB and the public key publickeyB of the application program B are not tampered, and the application program B can be successfully installed only when the publickeyB is the public key matched with the self-signature signatureB.

Fig. 4 shows an implementation block diagram of a file sharing method provided in an embodiment of the present application. As shown in fig. 4, in the block diagram of the file sharing method according to the embodiment of the present disclosure, the file sharing method may include a download installation package 401 of an application a, a package management service BMS402, and a download installation package 403 of an application B; wherein:

Installation package 401 of application a may include

files

4011 and 4012. So, the file 4011 writes a code for sharing a file having a file name getHilink.so to an application having a public key of "abcdfgh". The file 4012 is a file having a file name of getHilink. File 4012 may be decompressed from installation package 401 for application a.

The package management service BMS402 is provided by the package manager in fig. 2. The package management service BMS402 may save the correspondence 4021 between the file with the file name gethigh.so and the application with the publickey "abcdfgh" in the file 4011. The BMS402 establishes the shared group 4022 of the file having the file name gethilink. The correspondence 4021 and the shared group 4022 may be stored in a database. publickeyB of application B is "abcdefgh" when application B is installed, the BMS may add the UID of application B (e.g., the UIDB) to the shared group 4022.

The download installation package 402 of application B may contain the public key publickeyB of application B. pubickeyb may be "abcdfgh".

In this way, a shared group of the file having the file name getHilink.so is established by the BMS402, and the UID of the application B is added to the shared group of the file having the file name getHilink.so. Application B has the right to read a file with the executable file name gethilink.

A file sharing method provided in an embodiment of the present application is described in detail below with reference to the accompanying drawings. Fig. 5 shows a flowchart of a file sharing method according to an embodiment of the present application. As shown in fig. 5, a file sharing method provided in an embodiment of the present application may include:

s100, the electronic equipment responds to the operation A and obtains an installation package of the application program A.

The user may obtain the installation package of application a in the application marketplace of the electronic device. Operation a may be an operation in which the user acquires the installation package of application a, for example, operation a may be an operation in which the user downloads the installation package of application a from the application market. Referring to the description of fig. 3, it can be understood that the installation package of the application a downloaded by the user from the application market may include the source package of the application a, the public key of the application a, and the self-signature information of the application a. The installation package of application a may be referred to herein as a download installation package of application a. The process of generating the application a and uploading the application to the application market to form the downloaded installation package on the application a may refer to the description in fig. 3, and is not described herein again.

S101, the electronic device determines that an installation package of an application program A carries a first identifier, wherein the first identifier is used for indicating that a file A in the installation package of the application program A is shared to a shared object, and the shared object is an application program which can access the file A.

The electronic device may read the first identifier from the installation package of application a. The first identification may be source code in a source package of application a. The first identifier is used for indicating that the file A in the installation package of the application program A is shared to the shared object. The shared object is an application program that can access file a. It will be appreciated that the developer of application a may contract with developers of other applications to share certain files of application a to other applications. In this way, other application programs can call and read the data of the file a, and realize the function provided by the source code in the file a.

The first identifier may be as follows:

Profile.json:

so "// designating a shareable file name as" getHilink.

The shared object of < public key > abcdfgh </public key > </share >/file "getHilink

The first identifier may specify a file that can be shared in the application a and an object that can be shared by the file. In the embodiment of the present application, the file a may be the above-mentioned first identification file "gethilink. The shared object of the file a may be an application program whose public key is "abcdfgh". The electronic device may decompress the file "getHilink. so" to an application installation, e.g.,/data/appA/lib, when installing application A. The electronic device may synchronize the correspondence between the file a (e.g., the file "gethigh. so") and the shared object (e.g., the application program whose public key is "abcdfgh") in the BMS according to the first identifier, for example, the content in the profile information. The BMS may store a correspondence between a file a (e.g., the file "gethigh. so") and a shared object (e.g., an application with public key "abcdfgh") in a database.

It will be appreciated that a developer may share a file a in application a to multiple shared objects. The developer may also share multiple files in application a to one or more shared objects.

It can be understood that, different files are shared in the application programs, different shared objects of the shared files are different, and the content in the first identifier is also different, and the specific content of the first identifier is not limited in this embodiment of the application.

S102, the electronic equipment establishes a sharing group of the file A based on the first identification.

The electronic devices may establish a shared group of the file a through the BMS. The BMS may generate a shared Group ID (GID) of the file a. The User ID (UID) of all applications that can share file a and the UID of application a may be included in the shared group of file a. If the electronic equipment does not install the application program which can be shared by the specified file A in the first identification, only the UID of the application program A is in the sharing group. Where the UID may be used to identify an application.

When the electronic device installs the application, the BMS in the electronic device may assign the UID to the application. The UID of the application does not change during the time the application is present on the electronic device. And one application can only have one UID.

In the embodiment of the present application, based on a shared file, applications in an electronic device can be divided into three types: file owner users, group users, other users. An application that provides shared files may be referred to as a file owner user. Within a shared group that shares files, other applications besides the application that provides the file may be referred to as group users. Applications in the electronic device that may not share the shared file may be referred to as other users. Different types of applications have different permissions for sharable files. The file owner user has the right to read, write and execute the file, the group user has the right to read, execute and not write the file, and other users cannot read, write or execute the shared file.

S103, the electronic equipment responds to the operation B and obtains an installation package of the application program B.

The user may obtain the installation package of application B in the application marketplace of the electronic device. Operation B may be an operation in which the user acquires the installation package of application B, for example, operation B may be an operation in which the user downloads the installation package of application B from the application market. Referring to the description in fig. 3, it can be understood that the installation package of the application B downloaded by the user from the application market may include the source package of the application B, the public key of the application B, and the self-signature information of the application B. The installation package of application B may be referred to herein as a download installation package of application B. The process of generating the application B and uploading the application B to the application market to form the downloaded installation package on the application B may refer to the description in fig. 3, and is not described herein again.

And S104, the electronic equipment determines that the application program B is a shared object of the file A according to the identifier of the application program B and the first identifier.

The electronic device may obtain the identifier of the application B in the download installation package of the application B. Specifically, the identification of application B may be the public key publickeyB of application B. For example, the publickeyB of application B is "abcdfgh". The first identifier indicates that the file a of the application program a is shared to the application program of which publickeyB is "abcdfgh". In this way, the electronic device may determine that the application B is a shared object of the file a according to the identifier of the application B and the first identifier.

And S105, adding the application program B into the sharing group of the file A by the electronic equipment.

The electronic device may add the UID of application B to a user group that shares file a (e.g., file "gethilink. If the GID of the user group of the file is 1001, the UID of the application A is 1001, and the UID of the application B is 1002. Then, the sharing group with file a having GID of 1001 includes two users: UID 1001 (application a) and UID1002 (application B). Here, the UID of the owner (e.g., application a) of the shared file (e.g., file a) may be the same as the GID of the user group sharing the file. However, the UIDs of different applications are not the same.

After the electronic device adds the application program B to the sharing of the file a, when the application program B calls the file a, the application program B may read the data in the file a and the executable file a. When the application program B runs, the AMS is responsible for the life cycle management of the application program B.

It is understood that, when the electronic device performs step S102, the BMS in the electronic device may obtain the public key publickeyA of the application a. The BMS determines whether the file shared to the application program A exists in the electronic equipment or not according to publickeyA, and if so, the electronic equipment can add the application program A into the sharing group of the file. Further, the UID of application A may be added to the shared group for the file.

By the file sharing method provided by the embodiment of the application, the electronic device can share the specified file in the application program A, namely the file A, to the specified application program, such as the application program B. Thus, application B can access the file and execute file A. But file a is not accessible to, nor executable by, other programs in the electronic device. Therefore, the application program A can share the file A to the application program B, and malicious access of the file A of the application program A by other application programs in the electronic equipment is avoided.

In the present application, a developer of the application a writes the first identifier in the source package of the application a. The first identification indicates that file a of application a is shared to application B. For example, the developer of application a may write the first identifier in the profile file of the source package of application a. The electronic device may install the application a first or the application B first. When the application B is installed in the electronic device first, a file sharing method provided in an embodiment of the present application may be executed according to the steps shown in fig. 6.

Fig. 6 shows a schematic flowchart of a file sharing method provided in an embodiment of the present application, and as shown in fig. 6, the file sharing method provided in the embodiment of the present application may include:

s200, the electronic equipment responds to the operation B and obtains an installation package of the application program B.

S201, the electronic equipment determines whether a file A which can be shared by an application program B exists in the electronic equipment; if yes, step S202 is executed, and if not, step S203 is executed.

The electronic device may obtain the identifier of the application B, for example, the public key publickeyB of the application B, from the installation package of the application B. The electronic device can determine whether there is a file shared to application B in the electronic device based on publickeyB. And if the BMS has the corresponding relation between the publickeyB and the shared file, the electronic equipment determines that the electronic equipment has the file shared to the application program B. The electronic device may perform step S202. And if the BMS does not have the corresponding relation between the publickeyB and the shared file, the electronic equipment determines that the file which is not shared to the application program B in the electronic equipment. The electronic device may perform step S203.

S202, adding the application program B into the sharing group of the file A by the electronic equipment.

The electronic device may add the UID of application B to a user group that shares file a (e.g., file "gethilink. For example, the GID of the user group of the file is 1001. The owner of file a is application a, whose UID is 1001. The UID of application B is 1002. Then, the sharing group with file a having GID of 1001 includes two users: UID 1001 (application a) and UID 1002 (application B). Here, the UID of the owner (e.g., application a) of the shared file (e.g., file a) may be the same as the GID of the user group sharing the file. However, the UIDs of different applications are not the same.

When the electronic device installs the application, the BMS in the electronic device may assign the UID to the application. The UID of the application program does not change during the existence of the application program in the electronic device. And one application can only have one UID.

Step S202 may refer to the description in step S105.

S203, the electronic equipment responds to the operation A and obtains an installation package of the application program A.

It is understood that the operation a and the operation B of the user may be discontinuous operations. That is, the user may perform operation a after a first period of time after performing operation B. For example, the user may perform the operation of installing application a three days later than the operation of installing application B. The first time period may be 30 minutes, 1 day, or 1 month, which is not limited in the embodiment of the present application.

S204, the electronic equipment determines that the installation package of the application program A carries a first identifier, and the first identifier indicates that the file A in the installation package of the application program A is shared to the application program B.

The electronic device may read the first identifier from the installation package of application a. The first identification may be source code in a source package of application a. The first identifier is used for indicating that the file A in the installation package of the application program A is shared to the application program B. It is understood that the developer of application a may agree with the developer of application B to share file a of application a to application B. Thus, the application program B can call and read the data of the file A and realize the function provided by the source code in the file A.

The first identifier may be as follows:

Profile.json:

< share name ═ getHilink.so' >/indicates that the sharable file name is "getHilink.so"

Application program with public key of abcdfgh/file of getHilink so as to obtain shared object of abcdfgh/file

The first identifier may specify a file that can be shared in the application a and an object that can be shared by the file. In the embodiment of the present application, the file a may be the first identification file "gethirink. The shared object of the file a may be an application program whose public key is "abcdfgh". The public key of application B is "abcdfgh". Thus, the first identification indicates that file a is shared to application B.

The electronic device may decompress the file "getHilink. so" to an application installation, e.g.,/data/appA/lib, when installing application A. The electronic device may synchronize the correspondence between the file a (e.g., the file "gethigh. so") and the shared object (e.g., the application program whose public key is "abcdfgh") in the BMS according to the first identifier, for example, the content in the profile information. The BMS may store a correspondence between a file a (e.g., the file "gethigh. so") and a shared object (e.g., an application with public key "abcdfgh") in a database.

S205, the electronic equipment adds the application program B into the sharing group of the file A.

Step S205 may refer to the description in step S105 or step S202.

When an application B of the electronic device wants to access a file a of the application a, the electronic device needs to determine whether the application B has a right to access the application a. And if the application program B is in the sharing group of the file A, the electronic equipment determines that the application program B has the authority of accessing the application program A, otherwise, the electronic equipment determines that the application program B does not have the authority of accessing the application program A. Here, reference may be specifically made to a flowchart of the file sharing method shown in fig. 7.

Fig. 7 illustrates a file sharing method provided in an embodiment of the present application, and as shown in fig. 7, the file sharing method provided in the embodiment of the present application may include:

s300, responding to user operation, calling a file A by an application program B in the electronic equipment, wherein the file A is a file in an installation package of the application program A.

The user operation may be an operation in which the user can click an icon of the application B in the main interface of the electronic device. In response to the user operation, the electronic device starts the application B. The application may call file a when started. The user operation may also be an operation in which the user clicks a control in the user interface of the application program B. In response to the user operation, the application B calls the file a. File a is a file in the installation package of application a. The file a may be an executable file, that is, the file a is a file that the electronic device can load for execution.

S301, the electronic device determines whether the application program B is in a sharing group of the file A, wherein the sharing group of the file A is used for indicating that the application program in the sharing group of the file A has the authority of accessing the file A, the sharing group of the file A is established by the electronic device according to a first identifier in an installation package of the application program A, and the first identifier is used for indicating a sharing object of the file A. If yes, go to step S302 a; if not, go to step S302 b.

The electronic device may determine whether the application is in the shared group for file a based on the UID of application B. Specifically, the electronic device may check whether the UID of application B exists in the shared group of file a in the BMS. The sharing group of the file A is used for indicating that an application program in the sharing group of the file A has the authority of accessing the file A, the sharing group of the file A is established by the electronic equipment according to a first identifier in an installation package of the application program A, and the first identifier is used for indicating a sharing object of the file A.

Further, the electronic device may first check whether application B is the application that provides file a. If so, the electronic device may perform step S302 a. If not, the electronic device checks to see if the application is in the shared group for file A. If so, the electronic device may determine the authority of the application program in the sharing group of the file a set by the system. If the application in the sharing group of the system configuration file a can read the file a and also execute the file a, the electronic device may execute step S302 a.

Here, it can be understood that, when the electronic device installs the application a, the BMS in the electronic device may assign the application a with a UID unique to the application a on the electronic device, such as the UIDA. The BMS may decompress the resource files in the download installation package of application a at some path of the system. At this time, the electronic device may set the user owner of the files and folders under the path as the UID of the application a, for example, the user owner of the file a as the UIDA. Meanwhile, the electronic device may set the GID of the sharing group of the file a as the UID of the application a. When the electronic device installs the application B, the BMS parses to the file a that the application B can share the application a. The BMS may trigger the system of the electronic device to add the UID of application B to the shared group of file a. For example, the BMS may trigger the system to execute a gpasssw command to add the UID of application B to the shared group for file A. There are various ways for the system of the electronic device to add the UID of the application B to the shared group of the file a, which is not limited in the embodiment of the present application.

Here, how the electronic device constructs the shared group of the file a may refer to the description in the above step S100 to step S105, or step S200 to step S205, and is not described herein again.

S302a, the electronic device provides the data of the file a to the application B.

If application B is in the shared group of files, the electronic device allows application B to access the files. The electronic device may provide the data of file a to application B. That is, application B can read the data of file A and application B can execute file A.

S302B, the electronic equipment determines that the application program B fails to call the file A.

If the electronic device determines that application B is not in the shared group for file A, then application B does not have the authority to invoke file A. The electronic device determines that application B failed to invoke file a. The user interface of application B may display a prompt for a failure to invoke file a, such as "no access rights", "access failure", and so on. There is no limitation on how the electronic device specifically prompts the application B to fail to call the file a.

By the method provided by the embodiment of the application, the application program B can access the file A only when the electronic device determines that the application program B is a member of the sharing group of the file A. Thus, file a can be shared with more than just the designated application. And preventing other application programs in the electronic equipment from maliciously accessing the file A. Application B can only access file A in application A, not all files of application A. In this way, the normal operation of the application program a can be prevented from being affected.

Fig. 8 is a schematic diagram of a file sharing apparatus according to an embodiment of the present application. As shown in fig. 8, the file sharing apparatus 800 may include an obtaining module 801 and a permission setting module 802; wherein:

an obtaining module 801, configured to: the method comprises the steps of obtaining an installation package of a first application program, wherein the installation package of the first application program comprises a first file and a first identifier, and the first identifier indicates that a shared object of the first file comprises a second application program.

An authority setting module 802, configured to: and providing the access right of the first file to the second application program according to the first identifier.

In one possible implementation, the permission setting module 802 may be configured to:

and adding the identifier of the second application program into the sharing group of the first file according to the first identifier, wherein the identifier of the second application program comprises the identifier assigned to the second application program when the second application program is installed, such as the UID of the second application program.

when the second application program is installed, distributing the identifier of the second application program to the second application program;

when the first application program is installed, establishing a sharing relation indicated in the first identifier; the sharing relationship describes that the shared object of the first file comprises the second application program. For example, the sharing relationship between the file with the file name getHilink. so shown in the correspondence relationship 4021 in FIG. 4 and the application with the publickey "abcdfgh".

In one possible implementation, the obtaining module 801 may be configured to receive an access request of the second application program to the first file.

In one possible implementation, the permission setting module 802 may be configured to confirm that the second application has the first file with access permission.

In a possible implementation manner, the file sharing apparatus 800 may further include a providing module 803; wherein:

the providing module 803 may be used to provide the data of the first file to the second application.

It is understood that the file sharing apparatus 800 may implement the file sharing method described in steps S100 to S105 shown in fig. 5, the file sharing method described in steps S200 to S205 shown in fig. 6, and the file sharing method described in steps S300 to S302a and step S302b shown in fig. 7. Specifically, the method comprises the following steps:

the acquisition module 801 may be configured to perform step S100, step S103, step 200, and step 203.

The authority setting module 802 may be configured to execute step S101, step 102, step S104, step S105, step S201, step 202, step S204, step S205, and step S300, step S301.

The providing module 803 may be used for executing the steps S302a, S302 b.

The file sharing device provided by the embodiment of the application can add the second application program into the sharing group of the first file in the installation package of the first application program according to the first identifier in the installation package of the first application program. The second application has access to the first file. In this way, the first file may be shared not only with the designated application. And preventing other application programs in the file sharing device from maliciously accessing the file. The second application can only access the first file in the first application, and not all files of the first application. In this way, the normal operation of the first application program can be prevented from being influenced.

The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and these modifications or substitutions do not depart from the scope of the technical solutions of the embodiments of the present application.

As used in the above embodiments, the term "when …" may be interpreted to mean "if …" or "after …" or "in response to determining …" or "in response to detecting …", depending on the context. Similarly, depending on the context, the phrase "at the time of determination …" or "if (a stated condition or event) is detected" may be interpreted to mean "if the determination …" or "in response to the determination …" or "upon detection (a stated condition or event)" or "in response to detection (a stated condition or event)".

In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk), among others.

Those skilled in the art can understand that all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer readable storage medium and can include the processes of the method embodiments described above when executed. And the aforementioned storage medium includes: various media capable of storing program codes, such as ROM or RAM, magnetic or optical disks, etc.

Claims

1. A file sharing method is applied to electronic equipment and is characterized by comprising the following steps:

acquiring an installation package of a first application program, wherein the installation package of the first application program comprises a first file and a first identifier, and the first identifier indicates that a shared object of the first file comprises a second application program;

and providing the access right of the first file for the second application program according to the first identifier.

2. The method of claim 1, wherein providing the second application with access to the first file according to the first identifier comprises:

reading the first identifier when the electronic equipment installs the first application program according to the installation package of the first application program;

And providing the access right of the first file to the second application program according to the first identification.

3. The method of claim 2, wherein providing the second application with access to the first file according to the first identifier comprises:

4. The method of claim 3, wherein the adding the identifier of the second application to the shared group of the first file according to the first identifier comprises:

when the first identifier is determined to contain the identifier of the second application program, adding the second application program into the sharing group of the first file; the identifier of the second application program comprises an identifier carried in an installation package of the second application program.

5. The method of claim 3, wherein the joining the second application to the shared group of the first file according to the first identifier comprises:

And adding the identifier of the second application program into the sharing group of the first file according to the first identifier, wherein the identifier of the second application program comprises the identifier which is allocated to the second application program by the electronic equipment when the second application program is installed.

6. The method of claim 5, wherein the adding the identifier of the second application to the shared group of the first file according to the first identifier comprises:

when the second application program is installed, the first application program is allocated with the identification of the second application program;

7. The method of any of claims 1-6, wherein after providing the second application with access to the first file based on the first identifier, the method further comprises:

receiving an access request of the second application program to the first file;

confirming that the second application program has the access right of the first file;

providing the data of the first file to the second application.

8. A file sharing apparatus, characterized in that the file sharing apparatus comprises:

an acquisition module to: acquiring an installation package of a first application program, wherein the installation package of the first application program comprises a first file and a first identifier, and the first identifier indicates that a shared object of the first file comprises a second application program;

a permission setting module for: and providing the access right of the first file for the second application program according to the first identifier.

9. The apparatus of claim 8, wherein the permission setting module is configured to:

reading the first identifier when the first application program is installed according to the installation package of the first application program;

10. The apparatus of claim 9, wherein the permission setting module is configured to:

11. The apparatus of claim 10, wherein the permission setting module is configured to:

When the first identification contains the identification of the second application program, adding the second application program into the sharing group of the first file; the identifier of the second application program comprises an identifier carried in an installation package of the second application program.

12. The apparatus of claim 9, wherein the permission setting module is configured to:

and adding the identifier of the second application program into the sharing group of the first file according to the first identifier, wherein the identifier of the second application program comprises the identifier allocated to the second application program when the second application program is installed.

13. The apparatus of claim 12, wherein the permission setting module is configured to:

14. The apparatus of any one of claims 8-13, wherein the obtaining module is configured to:

The permission setting module is used for: confirming that the second application program has the access right of the first file;

the device further comprises:

providing a module for: providing the data of the first file to the second application.

15. An electronic device, comprising a processor and a memory; the memory is configured to store program code, and the processor is configured to invoke the program code to cause the electronic device to perform the method of any of claims 1-7.

16. A computer program product comprising instructions which, when run on an electronic device, cause the electronic device to perform the method of any of claims 1-7.

17. A computer-readable storage medium comprising instructions that, when executed on an electronic device, cause the electronic device to perform the method of any of claims 1-7.