WO2021104259A1

WO2021104259A1 - Method and terminal for data sharing between fast application and native application

Info

Publication number: WO2021104259A1
Application number: PCT/CN2020/131133
Authority: WO
Inventors: 舒玉华
Original assignee: 华为技术有限公司
Priority date: 2019-11-27
Filing date: 2020-11-24
Publication date: 2021-06-03
Also published as: CN112860445A; CN112860445B

Abstract

Embodiments of the present application relate to the technical field of terminals. Disclosed are a method and terminal for data sharing between a fast application and a native application. The terminal comprises a fast application engine, a fast application access proxy, an operating system, a first fast application, and a first native application. The method comprises: the fast application engine registers the first fast application to the fast application access proxy; the fast application access proxy registers the first fast application to the operating system to form a first fast application access proxy instance; the first fast application access proxy instance and the first native application share data by using a data sharing mechanism between native applications to obtain shared data of the first native application; and the first fast application obtains, from the first fast application access proxy instance by means of the fast application access proxy, the shared data of the first native application. The risk of unauthorized access of the fast application can be reduced, and data sharing between the fast application and the native application is efficiently and securely achieved.

Description

Method and terminal for data sharing between fast application and native application

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office, application number 201911183286.0, and application titled "A method and terminal for data sharing between fast applications and native applications" on November 27, 2019, and its entire contents Incorporated in this application by reference.

Technical field

The embodiments of the present application relate to the field of terminal technology, and in particular, to a method and terminal for data sharing between a fast application and a native application.

Background technique

A native application is a software program for a specific platform or device that can run directly on the operating system of the terminal. Generally speaking, native applications need to be installed on the terminal before they can be used by users.

Kuaiapp is a new application ecosystem jointly launched by several major Android mobile phone manufacturers in China based on the hardware platform. It does not need to be downloaded and installed, just click and use. Quick apps are developed using front-end technology stacks, native rendering, and have the dual advantages of H5 pages and native apps, with no installation, no storage, one-key direct access, and direct update push. The fast application framework program is deeply integrated into the terminal software system of various manufacturers. The fast application runs inside the fast application framework program, and cannot be directly controlled by the terminal's operating system like a native application.

There are scenarios for data sharing between fast apps and native apps. However, since the operating system of the terminal cannot effectively manage the data access permissions of the fast application, the problem of unauthorized access to the fast application may occur. How to efficiently and securely share data between fast apps and native apps is a problem that needs to be solved.

Summary of the invention

The embodiment of the present application provides a method and terminal for data sharing between a fast application and a native application, which can efficiently and securely share data between the fast application and the native application.

In the first aspect, the embodiments of the present application provide a method for sharing data between a fast application and a native application, which is applied to a terminal. The terminal includes a fast application engine, a fast application access agent, an operating system, a first fast application, and a first native application. Application, the method can include:

The fast application engine registers the first fast application to the fast application access agent; the fast application access agent registers the first fast application to the operating system to form the first fast application access agent instance; the first fast application access agent instance and the first native application The data sharing mechanism between native applications is adopted for data sharing, and the shared data of the first native application is obtained; the first fast application obtains the shared data of the first native application from the first fast application access agent instance through the fast application access agent.

Since the first fast application obtains the shared data of the first native application through the first fast application access proxy instance, the first fast application access proxy instance and the first native application adopt the data sharing mechanism between native applications for data sharing, which can reduce the speed The risk of unauthorized access to the data of the native application by the application enables efficient and safe data sharing between the fast application and the native application.

In combination with the first aspect, in a possible design method, the fast application engine registering the first fast application to the fast application access agent includes: the fast application engine registers the authorized access information between the first fast application and the first native application to Quick application access agent; among them, the authorized access information between the first quick application and the first native application includes: the identification of the first quick application resource installation package, the certificate fingerprint of the first quick application resource installation package, and the identification of the first native application , And the requested data. For example, the identifier of the first fast application resource installation package may be the package name of the first fast application resource installation package, and the identifier of the first native application may be the package name of the first native application.

In combination with the first aspect, in a possible design method, the fast application access agent registers the first fast application to the operating system to form the first fast application access agent instance, and the fast application access agent combines the first fast application with the first fast application. The authorized access information between native applications is saved to the first fast application access proxy instance. In this way, the first fast application access proxy instance can obtain the corresponding relationship between the first fast application and the first native application according to the authorized access information.

With reference to the first aspect, in a possible design manner, the identification of the first fast application access agent instance corresponds to the identification of the first fast application resource installation package, and the certificate fingerprint of the first fast application access agent instance corresponds to the first fast application resource installation package. There is a one-to-one correspondence between the certificate fingerprints of the quick application resource installation package.

With reference to the first aspect, in a possible design manner, the quick application engine registering the first quick application to the quick application access agent further includes: the quick application access agent returns the first quick application to the first quick application for data access Encryption key. In this way, when the first fast application requests to access the shared data of the first native application, the encryption key can be used to encrypt the data requested to be shared.

In combination with the first aspect, in a possible design approach, the data sharing mechanism between native applications includes: Content Provider, or shared preferences sharedPreferences.

With reference to the first aspect, in a possible design manner, the data sharing between native applications is provided with data access permissions, and the data access permissions are controlled by the operating system.

In combination with the first aspect, in a possible design approach, the fast application access agent belongs to the operating system or belongs to the fast application engine.

In a second aspect, an embodiment of the present application provides a terminal, which includes a fast application engine, a fast application access agent, an operating system, a first fast application, and a first native application. Among them, the fast application engine is used to register the first fast application to the fast application access agent; the fast application access agent is used to register the first fast application to the operating system to form an instance of the first fast application access agent; the first fast application Access proxy instance, used to share data with the first native application using the data sharing mechanism between native applications, and obtain the shared data of the first native application; the first fast application, used to access the proxy from the first fast application through the fast application access proxy The instance obtains the shared data of the first native application.

In combination with the second aspect, in a possible design method, the fast application engine is specifically used to register the authorized access information between the first fast application and the first native application to the fast application access agent; the first fast application and the first native application The authorized access information between native applications includes: the identification of the first quick application resource installation package, the certificate fingerprint of the first quick application resource installation package, the identification of the first native application, and the data requested for access.

With reference to the second aspect, in a possible design manner, the fast application access agent is also used to save the authorized access information between the first fast application and the first native application to the first fast application access agent instance.

With reference to the second aspect, in a possible design manner, the identifier of the first fast application access agent instance corresponds to the identifier of the first fast application resource installation package, and the certificate fingerprint of the first fast application access agent instance corresponds to the first fast application resource installation package. There is a one-to-one correspondence between the certificate fingerprints of the quick application resource installation package.

With reference to the second aspect, in a possible design manner, the fast application access agent is also used to return to the first fast application the encryption key of the first fast application for data access.

In combination with the second aspect, in a possible design method, the operating system is used to control data access permissions for data sharing between native applications.

In combination with the second aspect, in a possible design approach, the fast application access agent belongs to the operating system or belongs to the fast application engine.

In a third aspect, embodiments of the present application provide a terminal, which can implement the method of data sharing between a fast application and a native application described in the first aspect, which can be implemented by software, hardware, or by hardware executing corresponding software. method. In one possible design, the terminal may include a processor and a memory. The processor is configured to support the terminal to perform the corresponding function in the method of the first aspect described above. The memory is used for coupling with the processor, and it stores the necessary program instructions and data of the terminal.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium. The computer-readable storage medium includes computer instructions. When the computer instructions run on a terminal, the terminal executes any of the above-mentioned aspects and possible The method of data sharing between the fast application and the native application described in the design method.

In the fifth aspect, the embodiments of the present application provide a computer program product. When the computer program product runs on a computer, the computer executes the fast applications and native applications described in any of the above aspects and possible design methods. The method of data sharing between applications.

For the technical effects brought by the terminal described in the second aspect, the terminal described in the third aspect, the computer-readable storage medium described in the fourth aspect, and the computer program product described in the fifth aspect, please refer to the first aspect and The technical effects brought about by its different design methods will not be repeated here.

Description of the drawings

FIG. 1 is a schematic diagram of the hardware structure of an electronic device to which a method for data sharing between a fast application and a native application provided by an embodiment of the application is applicable;

2 is a schematic diagram of the software architecture of an electronic device to which a method for data sharing between a fast application and a native application provided by an embodiment of the application is applicable;

Figure 3 is a schematic diagram of a fast application running process;

Figure 4 is a schematic diagram of the architecture of a terminal running a fast application;

FIG. 5A is a schematic diagram of an example of a native application scenario;

Figure 5B is a schematic diagram of an example of a fast application scenario;

Figure 6A is a schematic diagram 1 of a data sharing method between a fast application and a native application;

Fig. 6B is a second schematic diagram of a data sharing method between a fast application and a native application;

FIG. 7 is a first schematic flowchart of a method for data sharing between a fast application and a native application according to an embodiment of the application;

FIG. 8 is a second schematic flowchart of a method for data sharing between a fast application and a native application according to an embodiment of the application;

FIG. 9 is a third flowchart of a method for data sharing between a fast application and a native application provided by an embodiment of the application.

Detailed ways

The method for sharing data between a fast application and a native application provided in an embodiment of the present application can be applied to a terminal. The terminal can be a portable computer (such as a mobile phone), a tablet computer, a notebook computer, a personal computer (PC), a wearable electronic device (such as a smart watch), augmented reality (AR)\virtual reality (virtual reality) , VR) equipment, on-board computer, etc. The following embodiments do not specifically limit the specific form of the terminal.

Please refer to FIG. 1, which shows a schematic structural diagram of an electronic device 100. The electronic device 100 may be the terminal described in this embodiment.

As shown in FIG. 1, the electronic device 100 may include 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, and a battery 142 , Antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193 , Display screen 194, subscriber identification module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

It can be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than those shown in the figure, or combine certain components, or split certain components, or arrange different components. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

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

The controller may be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching instructions and executing instructions.

A memory may also be provided in the processor 110 to store instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can store instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. Repeated accesses are avoided, the waiting time of the processor 110 is reduced, and the efficiency of the system is improved.

In some embodiments, the processor 110 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, and a universal asynchronous transmitter/receiver (universal asynchronous) interface. receiver/transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and / Or Universal Serial Bus (USB) interface, etc.

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor, the charger, the flash, the camera 193, etc., respectively through different I2C bus interfaces. For example, the processor 110 may couple the touch sensor through an I2C interface, so that the processor 110 and the touch sensor communicate through the I2C bus interface, so as to realize the touch function of the electronic device 100.

The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled with the audio module 170 through an I2S bus to implement communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit audio signals to the wireless communication module 160 through an I2S interface, so as to realize the function of answering calls through a Bluetooth headset.

The PCM interface can also be used for audio communication to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through 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 realize the function of answering calls through the Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

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

The MIPI interface can be used to connect the processor 110 with the display screen 194, the camera 193 and other peripheral devices. The MIPI interface includes a camera serial interface (camera serial interface, CSI), a display serial interface (display serial interface, DSI), and so on. In some embodiments, the processor 110 and the camera 193 communicate through a CSI interface to implement the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate through a DSI interface to realize the display function of the electronic device 100.

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

The USB interface 130 is an interface that complies with the USB standard specification, and specifically may be a Mini USB interface, a Micro USB interface, a USB Type C interface, and so on. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and peripheral devices. It can also be used to connect earphones and play audio through earphones. This interface can also be used to connect other electronic devices, such as AR devices.

It can be understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely a schematic description, and does not constitute a structural limitation of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection modes in the foregoing embodiments, or a combination of multiple interface connection modes.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive the charging input of the wired charger through the USB interface 130. In some embodiments of wireless charging, the charging management module 140 may receive the wireless charging input through the wireless charging coil of the electronic device 100. While the charging management module 140 charges the battery 142, it can also supply power to the electronic device through the power management module 141.

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 charging management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle times, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

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

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

The mobile communication module 150 can provide a wireless communication solution including 2G/3G/4G/5G and the like 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 can receive electromagnetic waves by the antenna 1, and perform processing such as filtering, amplifying and transmitting the received electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor, and convert it into electromagnetic waves for radiation via the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110. In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is 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 an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be provided in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), and global navigation satellites. System (global navigation satellite system, GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (infrared, IR) and other wireless communication solutions. 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, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be sent from the processor 110, perform frequency modulation, amplify, and convert it into electromagnetic waves to radiate through the antenna 2.

In some embodiments, the antenna 1 of the electronic device 100 is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc. The GNSS may include the global positioning system (GPS), the global navigation satellite system (GLONASS), the Beidou navigation satellite system (BDS), and the quasi-zenith satellite system (quasi). -zenith satellite system, QZSS) and/or satellite-based augmentation systems (SBAS).

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

The display screen 194 is used to display images, videos, and the like. The display screen 194 includes a display panel. The display panel can adopt liquid crystal display (LCD), organic light-emitting diode (OLED), active matrix organic light-emitting diode or active-matrix organic light-emitting diode (active-matrix organic light-emitting diode). AMOLED, flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, and N is a positive integer greater than one.

The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

The ISP is used to process the data fed back from the camera 193. For example, when taking a picture, the shutter is opened, the light is transmitted to the photosensitive element of the camera through the lens, the light signal is converted into an electrical signal, and the photosensitive element of the camera transfers the electrical signal to the ISP for processing and transforms it into an image visible to the naked eye. ISP can also optimize the image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and is projected to the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transfers the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other formats of image signals. In some embodiments, the electronic device 100 may include one or N cameras 193, and N is a positive integer greater than one.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the electronic device 100 selects the frequency point, the digital signal processor is used to perform Fourier transform on the energy of the frequency point.

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 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, and so on.

NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, for example, the transfer mode between human brain neurons, it can quickly process input information, and it can also continuously self-learn. Through the NPU, applications such as intelligent cognition of the electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, and so on.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, so as to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example, save music, video and other files in an external memory card.

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

The electronic device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. For example, music playback, recording, etc.

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

The speaker 170A, also called "speaker", is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music through the speaker 170A, or listen to a hands-free call.

The receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a call or voice message, it can receive the voice by bringing the receiver 170B close to the human ear.

The microphone 170C, also called "microphone", "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can make a sound by approaching the microphone 170C through the human mouth, and input the sound signal into 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, which can implement noise reduction functions in addition to collecting sound signals. In other embodiments, the electronic device 100 may also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and realize directional recording functions.

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

The button 190 includes a power button, a volume button, and so on. The button 190 may be a mechanical button. It can also be a touch button. The electronic device 100 may receive key input, and generate key signal input related to user settings and function control of the electronic device 100.

The motor 191 can generate vibration prompts. The motor 191 can be used for incoming call vibration notification, and can also be used for touch vibration feedback. For example, touch operations applied to different applications (such as photographing, audio playback, etc.) can correspond to different vibration feedback effects. Acting on touch operations in different areas of the display screen 194, the motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminding, receiving information, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

The indicator 192 can be an indicator light, which can be used to indicate the charging status, power change, and can also be used to indicate messages, missed calls, notifications, and so on.

The SIM card interface 195 is used to connect to the SIM card. The SIM card can be inserted into the SIM card interface 195 or pulled out from the SIM card interface 195 to achieve contact and separation with the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, and N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. The same SIM card interface 195 can insert multiple cards at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can 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 call and data communication. In some embodiments, the electronic device 100 adopts an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present invention takes an Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100.

FIG. 2 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present invention.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Communication between layers through software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.

The application layer can include a series of application packages.

As shown in Figure 2, the application package can include applications such as camera, gallery, calendar, phone, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 2, the application framework layer can include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and so on.

The window manager is used to manage window programs. The window manager can obtain the size of the display screen, determine whether there is a status bar, lock the screen, take a screenshot, etc.

The content provider is used to store and retrieve data and make these data accessible to applications. The data may include videos, images, audios, phone calls made and received, browsing history and bookmarks, phone book, etc.

The view system includes visual controls, such as controls that display text, controls that display pictures, and so on. The view system can be used to build applications. The display interface can be composed of one or more views. For example, a display interface that includes a short message notification icon may include a view that displays text and a view that displays pictures.

The phone manager is used to provide the communication function of the electronic device 100. For example, the management of the call status (including connecting, hanging up, etc.).

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

The notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and it can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, and so on. The notification manager can also be a notification that appears in the status bar at the top of the system in the form of a chart or a scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, text messages are prompted in the status bar, prompt sounds, electronic devices vibrate, and indicator lights flash.

Android runtime includes core libraries and virtual machines. Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one part is the function functions that the java language needs to call, and the other part is the core library of Android.

The application layer and application framework layer run in a virtual machine. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

The system library can include multiple functional modules. For example: surface manager (surface manager), media library (media libraries), 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL), etc.

The surface manager is used to manage the display subsystem and provides a combination of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support multiple audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing.

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

The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

The method for sharing data between a fast application and a native application provided in the embodiment of the present application can be applied to the above-mentioned terminal. Native applications are installed on the terminal; for example, the aforementioned camera, gallery, calendar, phone, map, navigation, WLAN, Bluetooth, music, video, SMS and other applications. In the embodiments of the present application, native applications include applications pre-installed on the terminal and third-party applications installed on the terminal. Quick app is free of installation and can be accessed through entrances such as notification bar, negative one screen, voice assistant, global search, browser, and application market. 3, the server 32 includes a developer platform 321 and an application warehouse 322, and the terminal 31 includes a scene entry 311, a quick application 312, and a quick application engine 313. The quick application 312 is used in the form of a resource package (RPK). The warehouse 322 is released, and the quick application engine 313 runs on the terminal 31 instead of the operating system 314 running on the terminal 31 directly like native applications. The user can invoke the quick application engine 313 by clicking on the scene entry 311. The fast application engine 313 downloads the data of the fast application from the server 32 and caches it in the fast application engine 313 to improve the efficiency of subsequent data acquisition. The fast application 312 runs on the fast application engine platform 313 and is displayed to users. Please continue to refer to FIG. 4, on the terminal side, the user enters the quick application through the scene entry 311, and the quick application runs on the quick application engine 313. The fast application engine 313 is an application program that runs on the application layer of the operating system 314.

There are scenarios for data sharing between fast apps and corresponding native apps. For example, there is a demand scenario for sharing the device list between the smart home fast application and the smart home native application.

Exemplarily, as shown in Figure 5A, a native smart home application is installed on the terminal. Users can enter the native smart home application by clicking on the icon "Smart Life" on the desktop. The main interface of "Smart Life" includes "My Device", which can display a list of smart devices registered in the smart home system. Take the entry of a negative one-screen entry into the smart home fast application as an example. As shown in Figure 5B, the user can enter the negative screen by sliding the screen from left to right on the desktop of the terminal. One negative screen includes quick search 501, sports health 502, quick application 503, situational intelligence 504, news 505 and other parts. Among them, the quick search 501 is used to search for local or online content according to user input; the sports health 502 is used to display sports-related information, such as the number of steps taken, energy consumed, walking distance, etc.; the quick application 503 is used to recommend or self Define the shortcut function entry; the contextual intelligence 504 is used to recommend contextual cards according to the user's usage habits. For example, the contextual intelligence 504 includes the smart home quick application display interface 506, and the smart home quick application display interface 506 can display the smart devices registered in the smart home system The list; News 505 is used to recommend news content according to the user’s usage habits. Since both the smart home fast application and the smart home native application need to display the list of smart devices registered in the smart home system, the smart home fast application and the smart home native application need to share the information of the smart devices registered in the smart home system.

In an implementation manner of the prior art, please refer to FIG. 6A, data sharing is implemented between the fast application and the native application through a server. Native applications synchronize static data or dynamic data to the server. When the user clicks to use the fast app corresponding to the native application, the fast app obtains static data or dynamic data from the server. In this method, the data sharing between the fast application and the corresponding native application needs to pass through the server, which depends on the network connection between the terminal and the server; the efficiency of data synchronization may cause the fast application interface to render slowly and the user experience is poor; and it also consumes users bandwidth.

In another implementation manner of the prior art, please refer to FIG. 6B, the fast application and the native application realize data sharing through the data sharing mechanism between the fast application engine and the native application (for example, the content provider mechanism of Android). The access relationship between the fast application and the native application is determined by the fast application engine. In this method, the fast application runs on the fast application engine, and the operating system does not recognize the application type of the fast application, and cannot perform targeted system authorization authorization for the fast application, and authorization processing for data sharing with the native application; The application engine controls the permission of the fast application and the authorization control of data sharing with the native application. Due to the lack of an operating system-level access authorization mechanism, there is a risk that other fast apps may gain unauthorized access to native application data.

The embodiment of the present application provides a method for data sharing between a fast application and a native application. In the terminal, the operating system performs authorization and control of data sharing between the fast application and the native application, which can efficiently and securely exchange data between the fast application and the native application. Data sharing between.

Multiple fast applications can be run on the terminal, and multiple native applications can be installed. There is a correspondence between some fast apps and native apps. For example, fast application A corresponds to native application A, and fast application B corresponds to native application B. Quick apps and corresponding native apps can be apps developed by the same manufacturer and provide the same functions. Exemplarily, a negative one-screen smart home quick application corresponds to a native smart home application; a negative one-screen express query quick application corresponds to a native express query application. Only the corresponding fast apps and native apps can share data, otherwise there will be the problem of unauthorized access to data. For example, a negative one-screen smart home fast application needs to display information such as the name, icon, and device connection status of the smart device on the interface, and needs to obtain the data of this information. The corresponding smart home native application may have obtained and saved the data from the server. . The native smart home application can share these data with the smart home fast application. However, the data saved in the native application of smart home cannot be shared by the express application, otherwise there will be a data leakage problem. In the method for data sharing between a fast application and a native application provided by the embodiment of the present application, the operating system of the terminal saves and manages the corresponding relationship between the fast application and the native application, and performs access permission control on the data sharing between the fast application and the native application. In this way, data can be shared between fast apps and native apps efficiently and securely.

Please refer to Figure 7, fast application A3121 corresponds to native application A318, and fast application B3122 corresponds to native application B3182. The quick application A3121 and the quick application B3122 run on the quick application engine 313 of the terminal 31 respectively. The native application A3181 and the native application B3182 run on the operating system 314 respectively. The terminal 31 also includes a quick application access agent 315, which can generate two quick application access agent instances (such as the quick application access agent instance A316 and the quick application access agent instance B317 in FIG. 7) correspondingly. Of course, it can also be Contains two quick application access agents, one quick application access agent generates one quick application access agent instance (not shown in the figure) respectively, and the quick application access agent 315 may be located in the operating system 314 or the quick application engine 313, for example, The fast application access agent 315 may be located at the application framework layer of the operating system 314.

When the quick application A3121 or the quick application B3122 runs for the first time, or the user subscribes to the quick application A3121 or the quick application B3122 for the first time, the quick application access agent instance registration can be performed in the operating system 314 through the quick application access agent 315. After fast application A3121 registers fast application access agent instance in operating system 314 through fast application access agent 315, it forms fast application access agent instance A316; fast application B3122 registers fast application access agent instance in operating system 314 through fast application access agent 315 Then, the fast application access proxy instance B317 is formed. The operating system 314 can perform application management on the quick application access agent instance A316 and the quick application access agent instance B317; that is, the operating system 314 can equate the quick application access agent instance A316 and the quick application access agent instance B317 to the native application for application Management, data access authority control for quick application access agent instance A316 and quick application access agent instance B317. The operating system 314 controls the quick application access proxy instance A316 and the native application A3181 corresponding to the quick application A3121 to share data through the native inter-application data sharing mechanism, and controls the quick application access proxy instance B317 to the native application B3182 corresponding to the quick application B3122 through the native application. Data sharing mechanism for data sharing. Further, the quick application access agent instance A316 can send or receive shared data to or from the quick application A3121 through the quick application access agent 315, thereby completing the data sharing between the quick application A3121 and the native application A3181; the quick application access agent instance B317 can The quick application access agent 315 sends or receives shared data to or from the quick application B3122, thereby completing data sharing between the quick application B3122 and the native application B3182.

In this way, the operating system 314 manages the correspondence between the fast application A3121 and the native application A3181, and the correspondence between the fast application B3122 and the native application B3182, to ensure that the data sharing process between the fast application and the native application is carried out safely and efficiently. Avoid unauthorized access to data by apps.

In the following, taking data sharing between the smart home quick application and the smart home native application as an example, the method for data sharing between the quick application and the native application provided in the embodiment of the present application will be introduced in detail.

The smart home fast application and the smart home native application share data through the fast application access agent, and the smart home fast application needs to be registered in the operating system of the terminal first.

Please refer to Figure 8, the process of registering the smart home application in the operating system of the terminal may include:

S801. The smart home fast application downloads the fast application resource installation package from the fast application platform through the fast application engine.

When the smart home fast app is used for the first time, the fast app resource installation package is downloaded from the fast app platform through the fast app engine. The fast application platform may be an application warehouse on a server. After downloading the quick application resource installation package, the quick application engine obtains the identification, certificate fingerprint and other information of the smart home quick application resource installation package.

S802. The quick application engine loads the smart home quick application resource installation package.

S803. The quick application engine registers the smart home quick application with the quick application access agent.

In some examples, after the quick application engine loads the smart home quick application resource installation package, it can immediately register the smart home quick application with the quick application access agent. In other examples, after the quick application engine loads the smart home quick application resource installation package, when needed (for example, when it receives a request from the smart home quick application to access the shared data of the native application), it registers the smart home with the quick application access agent Quickly apply.

In one implementation, the quick application engine registers the authorized access information between the smart home quick application and the corresponding smart home native application to the quick application access agent. Among them, the authorized access information between the smart home app and the corresponding smart home native application may include: the identification of the smart home app resource installation package, the certificate fingerprint of the smart home app resource installation package, and the smart home corresponding to the smart home app The identity of the native application, and the data requested to be accessed, etc. Exemplarily, the identifier of the smart home application resource installation package may be the package name of the smart home application resource installation package, and the identifier of the smart home native application may be the package name of the smart home native application.

Exemplarily, the registration interface is as follows:

public bool fastappRegister(String fastappPackageName, String fastappFingerPrint, String nativeappPackageName, OBJECT shareData).

Among them, fastappPackageName represents the package name of the fast app resource installation package, fastappFingerPrint represents the certificate fingerprint of the fast app resource installation package, nativeappPackageName represents the package name of the native application, and shareData represents the data requested to be accessed.

The fast application access agent generates and returns the encryption key for data access of the smart home fast application. The smart home fast application obtains the encryption key.

S804. The fast application access agent performs registration of the fast application access agent instance in the operating system.

The fast application access agent dynamically applies to the operating system (for example, the application management module of the operating system) for the fast application access agent instance corresponding to the smart home fast application to form the corresponding fast application access agent instance A. The quick application access agent instance A is registered in the operating system, and the operating system saves the information of the quick application access agent instance A, and then the application management of the quick application access agent instance A can be performed.

Among them, in one implementation, the identification of the quick application access agent instance A is the same as the identification of the smart home quick application resource installation package, and the certificate fingerprint of the quick application access agent instance A is the same as the certificate fingerprint of the smart home quick application resource installation package . In another implementation, there is a one-to-one mapping between the identification of the quick application access agent instance A and the identification of the smart home quick application resource installation package, and the certificate fingerprint of the quick application access agent instance A and the smart home quick application resource installation There is a one-to-one mapping between the package certificate fingerprints.

It should be noted that the package name of the smart home quick application resource installation package is different from the APK package name of other native applications in the operating system.

In an implementation manner, the fast application access agent can also log off the fast application access agent instance in the operating system. After the quick application access agent instance A corresponding to the smart home quick application logs out of the operating system, the operating system no longer controls and manages the data access authority of the quick application access agent instance A (ie, the smart home quick application).

S805. The quick application access agent saves the authorized access information between the smart home quick application and the corresponding smart home native application to the quick application access agent instance A.

In this way, the quick application access agent instance A obtains the authorized access information between the smart home quick application and the corresponding smart home native application. Among them, the authorized access information between the smart home app and the corresponding smart home native application includes: the identification of the smart home app resource installation package, the certificate fingerprint of the smart home app resource installation package, and the smart home native app corresponding to the smart home app The identity of the application, and the requested data, etc.

After the smart home fast application registers with the operating system through the fast application access agent, and the corresponding fast application access agent instance is formed, the smart home fast application can share data with the native smart home application under the control and management of the operating system.

Please refer to Figure 9, the process of the smart home fast application accessing the shared data of the smart home native application can include:

S901. The smart home fast application calls the inter-application data access interface of the fast application engine to request access to the shared data of the corresponding native application.

When the smart home fast application needs to access the shared data of the smart home native application, it calls the inter-application data access interface of the fast application engine to request access to the shared data of the native application.

In an implementation manner, when the inter-application data access interface is called, the data that the smart home fast application requests to access is encrypted by the encryption key for the smart home fast application data access obtained in S803.

S902. The fast application engine sends a request message for the smart home fast application to call the inter-application data access interface to the fast application access agent.

In one implementation, a transparent access tunnel is established between the fast application engine and the fast application access agent, and a request message for the smart home fast application to call the inter-application data access interface is sent. For example, a transparent access tunnel can be established based on message communication methods such as Android interface definition language (AIDL) and Messager.

S903. The fast application access agent sends a request message for the smart home fast application to call the inter-application data access interface to the fast application access agent instance A.

In one implementation, the quick application access agent receives the request message of the smart home quick application to call the inter-application data access interface, decrypts the data requested by the smart home quick application, and sends the smart home to the quick application access agent instance A The fast application calls the request message of the inter-application data access interface.

S904. The fast application access agent instance A accesses the shared data of the native application of the smart home through the data sharing mechanism between the native applications.

The quick application access agent instance A accesses the shared data of the smart home native application according to the data requested by the smart home quick application in the request message of the smart home quick application to call the inter-application data access interface through the native inter-application data sharing mechanism. Among them, the data sharing mechanism between native applications can adopt the data sharing mechanism between the native applications of the Android operating system in general technology, such as Content Provider, shared preferences, etc.; details are not described here.

In the native data sharing mechanism between applications, the operating system controls access to data between applications. For example, the operating system saves the correspondence between the quick application access agent instance A and the smart home native application during the quick application registration process, and allows the quick application access agent instance A to access the shared data of the smart home native application.

In one implementation, in S805 of the quick application registration process, the quick application access agent instance A obtains the authorized access information between the smart home quick application and the corresponding smart home native application, including: the smart home quick application resource installation package Identification, the certificate fingerprint of the smart home application resource installation package, the identification of the smart home native application corresponding to the smart home application, and the data requested to be accessed, etc. The quick application access proxy instance A determines the corresponding smart home native application through the identification of the smart home native application, and requests the smart home native application to access its shared data. The native smart home application verifies the authorization information such as the identification of the quick application access agent instance A according to the data access authority control mechanism of the operating system. If the verification is passed, the data requested to be accessed by the smart home fast application is sent to the fast application access agent instance A.

After the quick application access agent instance A obtains the shared data, it can use the quick application access agent to send the obtained shared data to the smart home quick application. In this way, the smart home fast application obtains the shared data of the smart home native application.

It should be noted that the process for the native smart home application to access the shared data of the smart home fast application is similar to the process for the smart home fast app to access the shared data of the smart home native application.

In an example, the operating system performs permission control on the data access request of the native smart home application. For example, during the quick application registration process, the operating system saves the correspondence between the quick application access agent instance A and the smart home native application, and allows the smart home native application to access the shared data of the quick application access agent instance A. When the native smart home application needs to access the shared data of the corresponding smart home fast application, it sends a data sharing request message to the fast application access agent instance A.

In S805 of the quick application registration process, the quick application access agent instance A obtains the authorized access information between the smart home quick application and the corresponding smart home native application, including: the identification of the smart home quick application resource installation package, and the smart home quick application resource The certificate fingerprint of the installation package, the identification of the smart home native application corresponding to the smart home fast application, and the data requested to be accessed, etc. After the fast application access agent instance A receives the data sharing request message of the smart home native application, it verifies the identity of the smart home native application. If the verification is passed, it is determined that the native smart home application is allowed to access the shared data of the smart home fast application.

The quick application access proxy instance A sends the received data sharing request message to the quick application engine through the quick application access agent, and the quick application engine uses the corresponding relationship between the quick application access agent instance A and the smart home quick application to share the data sharing request message Send to the smart home app.

After receiving the data sharing request message, the smart home fast application sends the shared data to the fast application access agent through the fast application engine. The quick application access agent sends the shared data of the smart home quick application to the quick application access agent instance A according to the corresponding relationship between the quick application access agent instance A and the smart home quick application.

The smart home native application accesses the shared data of the quick application access agent instance A through the data sharing mechanism between the native applications, that is, accesses the shared data of the smart home quick application.

In the method for data sharing between a fast application and a native application provided by the embodiments of the present application, the fast application running on the fast application engine registers with the operating system through the fast application access agent to form a corresponding fast application access agent instance. The fast application access proxy instance can share data with the native application using the native inter-application data sharing mechanism of the operating system. In this way, the data sharing between the fast application and the native application can be realized within the terminal, and the data access authority is controlled by the operating system, and the data sharing process is safe and efficient. In addition, the fast application access agent instance and the native application use the native inter-application data sharing mechanism of the operating system in the conventional technology for data sharing, without the need to modify the operating system's native inter-application data sharing mechanism, and the scalability is good.

It can be understood that, in order to implement the above-mentioned functions, the above-mentioned terminal includes hardware structures and/or software modules corresponding to each function. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the embodiments of the present application.

The embodiment of the present application also provides a computer storage medium in which computer program code is stored. When the processor of the electronic device executes the computer program code, the electronic device executes the terminal execution in FIG. 7 or FIG. 8 or FIG. 9 The relevant method steps implement the method in the above-mentioned embodiment.

The embodiment of the present application also provides a computer program product, which when the computer program product runs on a computer, causes the computer to execute the relevant method steps executed by the terminal in FIG. 7 or FIG. 8 or FIG. 9 to implement the method in the foregoing embodiment.

Among them, the computer storage media or computer program products provided in the embodiments of the present application are used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods provided above. The effect will not be repeated here.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above-mentioned functional modules is used as an example. In practical applications, the above-mentioned functions can be allocated according to needs. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed device and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be It can be combined or integrated into another device, or some features can be omitted or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

In addition, the functional units in the various embodiments of the present application may be integrated into one processor, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of a software product, and the software product is stored in a storage medium. It includes several instructions to make a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, ROM, magnetic disk, or optical disk and other media that can store program codes.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any change or replacement within the technical scope disclosed in this application shall be covered by the protection scope of this application. . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A method for data sharing between a quick application and a native application is applied to a terminal, the terminal includes a quick application engine, a quick application access agent, an operating system, a first quick application, and a first native application, wherein the Methods include:

The quick application engine registers the first quick application to the quick application access agent;

The fast application access agent registers the first fast application to the operating system to form a first fast application access agent instance;

The first fast application access agent instance and the first native application use a data sharing mechanism between native applications to share data, and obtain shared data of the first native application;

The first fast application obtains the shared data of the first native application from the first fast application access proxy instance through the fast application access proxy.
The method according to claim 1, wherein the quick application engine registering the first quick application to the quick application access agent comprises:

The quick application engine registers the authorized access information between the first quick application and the first native application to the quick application access agent; the authorized access between the first quick application and the first native application The information includes: the identification of the first quick application resource installation package, the certificate fingerprint of the first quick application resource installation package, the identification of the first native application, and the data requested to be accessed.
The method according to claim 2, wherein after the quick application access agent registers the first quick application to the operating system to form a first quick application access agent instance, the method further comprises:

The quick application access agent saves the authorized access information between the first quick application and the first native application to the first quick application access agent instance.
The method according to claim 2 or 3, wherein:

The identification of the first quick application access agent instance corresponds to the identification of the first quick application resource installation package, and the certificate fingerprint of the first quick application access agent instance corresponds to the identification of the first quick application resource installation package. There is a one-to-one correspondence between certificate fingerprints.
The method according to any one of claims 2-4, wherein the quick application engine registering the first quick application to the quick application access agent further comprises:

The fast application access agent returns to the first fast application an encryption key for the first fast application for data access.
The method according to any one of claims 1 to 5, wherein the data sharing mechanism between native applications includes: Content Provider, or shared preferences sharedPreferences.
The method according to any one of claims 1 to 6, wherein the data sharing between native applications is provided with data access permissions, and the data access permissions are controlled by the operating system.
The method according to any one of claims 1-7, wherein the fast application access agent belongs to the operating system or belongs to the fast application engine.
A terminal, which is characterized by comprising: a fast application engine, a fast application access agent, an operating system, a first fast application, and a first native application,

The quick application engine is used to register the first quick application to the quick application access agent;

The quick application access agent is used to register the first quick application to the operating system to form an instance of the first quick application access agent;

The first fast application access agent instance is used to share data with the first native application using a data sharing mechanism between native applications, and obtain shared data of the first native application;

The first fast application is configured to obtain shared data of the first native application from the first fast application access proxy instance through the fast application access proxy.
The terminal according to claim 9, wherein:

The quick application engine is specifically configured to register authorized access information between the first quick application and the first native application to the quick application access agent; the first quick application and the first native application The authorized access information includes: the identification of the first quick application resource installation package, the certificate fingerprint of the first quick application resource installation package, the identification of the first native application, and the data requested for access.
The terminal according to claim 10, wherein:

The quick application access agent is further configured to save the authorized access information between the first quick application and the first native application to the first quick application access agent instance.
The terminal according to claim 10 or 11, wherein:

The identification of the first quick application access agent instance corresponds to the identification of the first quick application resource installation package, and the certificate fingerprint of the first quick application access agent instance corresponds to the identification of the first quick application resource installation package. There is a one-to-one correspondence between certificate fingerprints.
The terminal according to any one of claims 10-12, wherein:

The fast application access agent is further configured to return to the first fast application an encryption key for the first fast application for data access.
The terminal according to any one of claims 9-13, wherein:

The operating system is used to perform data access permission control on data sharing between the native applications.
The terminal according to any one of claims 9-14, wherein:

The fast application access agent belongs to the operating system or belongs to the fast application engine.
A terminal, characterized in that the terminal includes: a processor and a memory; the memory is coupled with the processor; the memory is used to store computer program code; the computer program code includes computer instructions, when the When the processor executes the above computer instructions, it causes the terminal to execute the method according to any one of claims 1-8.
A computer-readable storage medium, wherein the computer-readable storage medium includes computer instructions, which when the computer instructions are run on a terminal, cause the terminal to execute any one of claims 1-8 Methods.
A computer program product, characterized in that, when the computer program product runs on a computer, the computer is caused to execute the method according to any one of claims 1-8.