WO2022100141A1

WO2022100141A1 - Plug-in management method, system and apparatus

Info

Publication number: WO2022100141A1
Application number: PCT/CN2021/107524
Authority: WO
Inventors: 王恒铭; 王众豪; 孙京阳; 黄振宇
Original assignee: 华为技术有限公司
Priority date: 2020-11-11
Filing date: 2021-07-21
Publication date: 2022-05-19
Also published as: CN114546511A

Abstract

A plug-in management method, system and apparatus, which relate to the technical field of terminals. The method comprises: receiving request information for requesting to run a micro application (S401); determining a plug-in corresponding to the request information (S402); acquiring feature information of the plug-in (S403); and scheduling the plug-in according to the feature information (S404). In the means for scheduling a plug-in, the impact of a plug-in on process running is considered and the plug-in can be reasonably scheduled, and thus load balancing during process running is further implemented, such that a micro application framework can smoothly run, improving user experience.

Description

Plug-in management method, system and device

This application claims the priority of the Chinese patent application with the application number 202011255737.X and the application name "plug-in management method, system and device" filed with the State Intellectual Property Office of China on November 11, 2020, the entire contents of which are incorporated by reference in this application.

technical field

The present application relates to the field of terminal technologies, and in particular, to a plug-in management method, system, and device.

Background technique

With the popularization of the use of smart phones, the number of mobile phone applications (applications, APPs) also shows an explosive growth trend. The mobile phone interface and storage space are gradually being occupied by more and more APPs. In this context, micro-apps stand out. Micro application refers to a small application that is highly focused on one function. It has the characteristics of easy access to services, no need to install and uninstall, and it can be used immediately. Micro application has become a new mode of mobile application development due to its advantages of lightness and ease of use. Micro-applications use a plug-in framework to load functions in a plug-in form, which is conducive to the decoupling, updating and expansion of functional modules. Based on the advantages of the micro-application plug-in framework, some complex applications and super-applications also generally use the micro-application plug-in framework to run multiple micro-applications in a plug-in form to provide users with multi-functional services.

In the prior art, when allocating processes to micro-application plug-ins, the plug-in framework can schedule the plug-ins according to the number of plug-ins. Usually, in order to balance the number of plug-ins in the process, the plug-ins are scheduled to the process with a smaller number of current plug-ins. middle.

However, the above-mentioned scheduling method of the plug-in is prone to phenomena such as excessively fast energy consumption or slow response when the process is running, which affects the user's experience.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a plug-in management method, system and device. After receiving request information for requesting to run a micro-application, the plug-in corresponding to the request information is determined, the characteristic information of the plug-in that affects the process operation is obtained, and the characteristic information of the plug-in is obtained according to the characteristic information of the plug-in. The plug-in can be scheduled into the process. The plug-in scheduling method in this micro-application considers the impact of the plug-in on the process operation, and the plug-in can be reasonably scheduled to achieve load balance when the process is running, so that the micro-application framework It can run smoothly and improve the user experience.

In this embodiment of the present application, the first device includes a terminal device; the second device includes a cloud device.

In a first aspect, an embodiment of the present application provides a plug-in management method, including: receiving request information for requesting to run a micro-application; determining a plug-in corresponding to the request information; wherein the plug-in is used to implement part or all of the functions of the micro-application; obtaining The feature information of the plug-in; wherein, the feature information includes the information that the plug-in affects the running of the process; the plug-in is scheduled according to the feature information. In this way, since the impact of the plug-in on the process operation is considered, the plug-in can be reasonably scheduled, so as to achieve load balancing when the process is running, so that the micro-application framework can run smoothly and improve the user's experience.

In a possible implementation manner, the feature information includes one or more of the following: load information, security level information, associated plug-in information, runtime information or plug-in priority information. In this way, more reasonable scheduling of the plug-in can be performed according to different characteristic information of the plug-in.

In a possible implementation manner, the plug-in is set in a process adapted to the characteristic information of the plug-in; or, the plug-in is disabled according to the characteristic information. In this way, you can choose to disable some unsafe or inappropriate plug-ins according to different characteristic information of the plug-ins, so as to improve the security plug-ins of process running.

In a possible implementation manner, the characteristic information includes load information, and the predicted load of the first process that can be used to run the plug-in is calculated according to the load information; the predicted load of the first process is that when the plug-in is set in the first process, the first process The total load of the first process is multiple; the plug-in is set in the first target process; the first target process is the process of the first process whose predicted load does not exceed the first load threshold. In this way, in process scheduling, it is possible to predict whether the first process exceeds the load threshold when the plug-in is scheduled to the first process. By setting the plug-in in the first target process whose predicted load does not exceed the load threshold, the first process after scheduling can be avoided. When the load threshold is exceeded in the process, load balancing is realized when the process is running.

In a possible implementation manner, the feature information includes security level information, and when the security level information indicates that the plug-in is a security plug-in, the plug-in is allocated in a process that can be used to run the plug-in; or, when the security level information indicates that the plug-in is In the case of a risky plug-in, the plug-in is allocated in an independent process; or, when the security level information indicates that the plug-in is an abnormal plug-in, the plug-in is disabled. In this way, a more appropriate scheduling policy can be implemented for the plug-ins according to plug-ins of different security levels, such as allocating risk plug-ins to independent processes or disabling abnormal plug-ins, etc., so as to improve the security of process operation. The independent process for running the risk plug-in may be a preset process dedicated to running the risk plug-in.

It can be understood that the independent process may be a concept corresponding to the dependent process. For example, the independent process is dedicated to running risk plug-ins, and the dependent process may be used to run multiple types of plug-ins. The independent process in the embodiments of the present application is used to represent the role of the process, and does not constitute a limitation on the process name or the like.

In a possible implementation manner, the security level information includes a process crash probability caused by a plug-in, a memory leak probability caused by a plug-in, or a probability calculated according to the process crash probability and the memory leak probability; when the security level information is less than the first value , indicating that the plug-in is a safe plug-in; when the security level information is greater than or equal to the first value and less than or equal to the second value, it means that the plug-in is a risky plug-in; when the security level information is greater than the second value, it means that the plug-in is an abnormal plug-in.

It can be understood that, in this implementation manner, the smaller the value of the security level information is, the safer it is for illustration, and in another possible implementation manner, the larger the value of the security level information, the more secure it is for illustration. , for example, when the security level information is greater than the first value, it means that the plug-in is an abnormal plug-in; when the security level information is less than or equal to the first value and greater than or equal to the second value, it means that the plug-in is a risk plug-in; when the security level information is less than or equal to the second value The second value indicates that the plug-in is a secure plug-in. The embodiment of the present application does not specifically limit the determination of the plug-in type.

It should be noted that in the above steps, the static descriptions of "indicates that the plug-in is a safe plug-in", "indicates that the plug-in is a risk plug-in", and "indicates that the plug-in is an abnormal plug-in" are for the purpose of clearly distinguishing the types of plug-ins and facilitating the understanding of the solution. , and does not constitute a limitation on the steps. For example, in the specific code implementation, the code execution logic may be based on the result of comparing the specific value of the security level information with the first value and the second value to perform the assignment or disabling operation of the plug-in, without "indicating that the plug-in is a security plug-in", " Steps such as "Indicates that the plugin is a risky plugin" and "Indicates that the plugin is an abnormal plugin".

In a possible implementation manner, the characteristic information further includes load information, and when the security level information indicates that the plug-in is a secure plug-in, the predicted load that can be used to run the second process of the security plug-in is calculated according to the load information of the security plug-in; The predicted load of the second process is the total load of the second process when the security plug-in is set in the second process; the number of the second process is multiple; the security plug-in is set in the second target process, and the second target process is the second process. In the process, the predicted load does not exceed the second load threshold of the process. In this way, abnormal plug-ins can be disabled, and normal plug-ins can be reasonably scheduled, so as to prevent abnormal plug-ins from affecting the normal operation of other plug-ins in the current process, and realize load balance when the process is running.

In a possible implementation manner, the feature information includes associated plug-in information, the plug-in is set in a third process, and the third process is a process that runs a relevant plug-in related to the associated plug-in information. In this way, if the associated plug-ins are set in the same process, when the process is running, multiple associated plug-ins can be run at the same time. Since the resources read between the associated plug-ins are the same, the operation of reading the same resource multiple times can be reduced. Energy consumption, thereby reducing the energy consumption of the process running.

In a possible implementation manner, the related plug-ins include: the same plug-ins as the resources read by the plug-ins.

In a possible implementation manner, a feature information file from the second device is received; the feature information file includes feature information of multiple plug-ins calculated by the second device; and the features of the plug-in are obtained from the feature information file according to the plug-in identifier information. In this way, due to the limited computing power of the first device and the reason that the first device also needs to perform tasks such as plug-in scheduling, in order not to affect other services of the first device, the service of computing the plug-in feature information can be handed over to a company with a stronger computing power. Dedicated second equipment to perform. Since the second device usually has powerful computing capabilities, the second device calculates the feature information of the plug-in, which can reduce the amount of computation of the first device and save the computing resources of the first device.

In a possible implementation manner, the method further includes: sending process-related information in the first device to the second device, where the process-related information is used to calculate the feature information file. In this way, the second device can use the process-related information to calculate the feature information file more conveniently.

In a possible implementation manner, the process-related information includes one or more of the following: a process name, a list of plug-ins, a memory ratio, a CPU usage rate of a central processing unit, or exception information.

In a possible implementation manner, the feature information is determined by using a machine learning model; wherein, the machine learning model is obtained by training using process-related sample information. In this way, due to the powerful learning and computing capabilities of the machine learning model, the process-related sample information can be fully trained, and the machine learning model can be used to obtain more accurate feature information.

In a possible implementation manner, the process-related sample information includes one or more of the following: process name, plug-in list, memory ratio, CPU usage rate of the central processing unit, or exception information.

In a second aspect, an embodiment of the present application provides a plug-in management method, which acquires process-related information; calculates a feature information file according to the process-related information, the feature information file includes feature information of multiple plug-ins, and the feature information of the plug-in includes the process running by the plug-in. Affecting information; sending a feature information file to the first device. In this way, since the impact of the plug-in on the process operation is considered, the plug-in can be reasonably scheduled, so as to achieve load balancing when the process is running, so that the micro-application framework can run smoothly and improve the user's experience.

In a possible implementation manner, the feature information includes one or more of the following: load information, security level information, associated plug-in information, runtime information or plug-in priority information. In this way, more reasonable scheduling of plug-ins can be performed according to different characteristic information.

In a possible implementation manner, the security level information includes a process crash probability caused by a plug-in, a memory leak probability caused by a plug-in, or a probability calculated according to the process crash probability and the memory leak probability. In this way, more accurate security level information of the plug-in can be obtained.

In a possible implementation manner, the machine learning model is trained according to the process-related information; the feature information file is output by using the machine learning model. In this way, the machine learning model can be used to obtain more accurate feature information.

In a possible implementation manner, the process-related information of the multiple devices is obtained from the multiple devices periodically; or, the process-related information sent by the multiple devices when the process is abnormal is obtained. In this way, more accurate feature information can be obtained based on more process-related information.

In a third aspect, an embodiment of the present application provides a plug-in management apparatus, where the plug-in management apparatus may be a terminal device, or may be a chip or a chip system in the terminal device. The plug-in management apparatus may include a processing unit and a communication unit. When the plug-in management apparatus is a terminal device, the processing unit may be a processor, and the communication unit may be a communication interface or an interface circuit. The plug-in management apparatus may further include a storage unit, which may be a memory. The storage unit is used for storing instructions, and the processing unit executes the instructions stored in the storage unit, so that the terminal device implements the plug-in management method described in the first aspect or any possible implementation manner of the first aspect. When the plug-in management apparatus is a chip or a chip system in the terminal device, the processing unit may be a processor, and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin or a circuit, or the like. The processing unit executes the instructions stored in the storage unit, so that the terminal device implements the plug-in management method described in the first aspect or any possible implementation manner of the first aspect. The storage unit may be a storage unit (eg, a register, a cache, etc.) in the chip, or a storage unit (eg, a read-only memory, a random access memory, etc.) located outside the chip in the terminal device.

Exemplarily, the processing unit is used to receive request information for requesting to run the micro-application; the processing unit is used to determine the plug-in corresponding to the request information; wherein, the plug-in is used to implement part or all of the functions of the micro-application; for acquiring the feature information of the plug-in; wherein, the feature information includes the information that the plug-in affects the running of the process; the processing unit is used for scheduling the plug-in according to the feature information.

In a possible implementation manner, the feature information includes one or more of the following: load information, security level information, associated plug-in information, runtime information or plug-in priority information.

In a possible implementation manner, the processing unit is specifically configured to set the plug-in in a process adapted to the characteristic information of the plug-in; or, disable the plug-in according to the characteristic information.

In a possible implementation manner, the characteristic information includes load information, and the processing unit is specifically configured to calculate the predicted load of the first process that can be used to run the plug-in according to the load information; the predicted load of the first process is to set the plug-in in the first process, the total load of the first process; the number of the first process is multiple; the processing unit is specifically used to set the plug-in in the first target process; the first target process is the first process, and the predicted load does not exceed the first target process. A load threshold process.

In a possible implementation manner, the feature information includes security level information, and when the security level information indicates that the plug-in is a security plug-in, the processing unit is specifically configured to allocate the plug-in to a process that can be used to run the plug-in; When the security level information indicates that the plug-in is a risk plug-in, the processing unit is specifically used to allocate the plug-in to an independent process; or, in the case where the security level information indicates that the plug-in is an abnormal plug-in, the processing unit is specifically used to disable the plug-in .

In a possible implementation manner, the feature information further includes load information, and in the case that the security level information indicates that the plug-in is a security plug-in, the processing unit is specifically configured to calculate the second data that can be used to run the security plug-in according to the load information of the security plug-in. The predicted load of the process; the predicted load of the second process is the total load of the second process when the security plug-in is set in the second process; the number of the second process is multiple; the processing unit is specifically used to set the security plug-in in the second process. Among the two target processes, the second target process is a process in the second process whose predicted load does not exceed the second load threshold.

In a possible implementation manner, the feature information includes associated plug-in information, and the processing unit is specifically configured to set the plug-in in a third process, where the third process is a process that runs a relevant plug-in related to the associated plug-in information.

In a possible implementation manner, the communication unit is specifically configured to receive a feature information file from the second device; the feature information file includes feature information of multiple plug-ins calculated by the second device; the processing unit is specifically configured to to obtain the feature information of the plug-in from the feature information file.

In a possible implementation manner, the method further includes: a communication unit, specifically configured to send the process-related information in the first device to the second device, where the process-related information is used to calculate the feature information file.

In a possible implementation manner, the processing unit is specifically configured to use a machine learning model to determine feature information; wherein, the machine learning model is obtained by training with process-related sample information.

In a fourth aspect, an embodiment of the present application provides a plug-in management apparatus. The plug-in management apparatus may be a cloud device, or may be a chip or a chip system in the cloud device. The plug-in management apparatus may include a processing unit and a communication unit. When the plug-in management apparatus is a cloud device, the processing unit may be a processor, and the communication unit may be a communication interface or an interface circuit. The plug-in management apparatus may further include a storage unit, which may be a memory. The storage unit is used for storing instructions, and the processing unit executes the instructions stored in the storage unit, so that the cloud device implements the plug-in management method described in the second aspect or any possible implementation manner of the second aspect. When the plug-in management apparatus is a chip or a chip system in the cloud device, the processing unit may be a processor, and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin or a circuit, or the like. The processing unit executes the instructions stored in the storage unit, so that the cloud device implements the plug-in management method described in the second aspect or any possible implementation manner of the second aspect. The storage unit may be a storage unit (eg, a register, a cache, etc.) in the chip, or a storage unit (eg, a read-only memory, a random access memory, etc.) located outside the chip in the cloud device.

Exemplarily, the processing unit is used to obtain process-related information; the processing unit is used to calculate a feature information file according to the process-related information, the feature information file includes the feature information of multiple plug-ins, and the feature information of the plug-in includes the plug-in generated by the process running. Affected information; a communication unit for sending a feature information file to the first device.

In a possible implementation manner, the security level information includes a process crash probability caused by a plug-in, a memory leak probability caused by a plug-in, or a probability calculated according to the process crash probability and the memory leak probability.

In a possible implementation manner, the processing unit is specifically configured to train a machine learning model according to process-related information; and output a feature information file by using the machine learning model.

In a possible implementation manner, the processing unit is specifically configured to periodically acquire process-related information of multiple devices from multiple devices; or, acquire process-related information sent by multiple devices when the processes are abnormal.

In a fifth aspect, the embodiments of the present application provide a computer-readable storage medium, in which a computer program or instruction is stored, and when the computer program or instruction is run on a computer, the computer is made to execute the first aspect and the first aspect. The plug-in management method described in any one of the implementation manners of the second aspect.

In a sixth aspect, an embodiment of the present application provides a computer program product including instructions, which, when the instructions are executed on a computer, cause the computer to execute the plug-in management method described in any one of the implementation manners of the first aspect and the second aspect.

In a seventh aspect, an embodiment of the present application provides a plug-in management system, and the system includes any one or more of the following: the third aspect and the plug-in management apparatus described in various possible implementations of the third aspect, and the fourth aspect and the plug-in management apparatus described in various possible implementation manners of the fourth aspect.

In an eighth aspect, an embodiment of the present application provides a plug-in management device, the device includes a processor and a storage medium, the storage medium stores an instruction, and when the instruction is executed by the processor, any implementation manner of the first aspect and the second aspect is implemented. Describes the plugin management method.

In a ninth aspect, the present application provides a chip or a chip system, the chip or chip system includes at least one processor and a communication interface, the communication interface and the at least one processor are interconnected by a line, and the at least one processor is used for running a computer program or instruction, The plug-in management method described in any one of the implementation manners of the first aspect and the second aspect is performed.

Wherein, the communication interface in the chip may be an input/output interface, a pin, a circuit, or the like.

In a possible implementation, the chip or chip system described above in this application further includes at least one memory, where instructions are stored in the at least one memory. The memory may be a storage unit inside the chip, such as a register, a cache, etc., or a storage unit of the chip (eg, a read-only memory, a random access memory, etc.).

In a tenth aspect, the present application provides a computer program product, the computer program product stores instructions, and when the instructions are executed by one or more processors, implements the plug-in management method in any of the foregoing aspects or implementations.

It should be understood that the third to tenth aspects of the present application correspond to the technical solutions of the first to second aspects of the present application, and the beneficial effects obtained by each aspect and the corresponding feasible implementation manner are similar, and will not be repeated here. .

Description of drawings

FIG. 1 is a schematic structural diagram of a terminal device 100 according to an embodiment of the present application;

FIG. 2 is a software structural block diagram of a terminal device 100 provided by an embodiment of the present application;

3 is a schematic diagram of a framework of an application program provided by an embodiment of the present application;

4 is a schematic flowchart of a plug-in management method provided by an embodiment of the present application;

5 is a schematic interface diagram of a user-triggered micro-application plug-in provided by an embodiment of the present application;

6 is a schematic interface diagram of another user-triggered micro-application plug-in provided by an embodiment of the present application;

7 is a schematic interface diagram of still another user-triggered micro-application plug-in provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of a plug-in scheduling provided by an embodiment of the present application;

FIG. 9 is a schematic flowchart of acquiring feature information according to an embodiment of the present application;

10 is a schematic diagram of the framework of a plug-in management system provided by an embodiment of the present application;

11 is a schematic flowchart of data collection and reporting provided by an embodiment of the present application;

12 is a schematic flowchart of a plug-in feature analysis provided by an embodiment of the present application;

13 is a schematic flowchart of a problem plug-in identification provided by an embodiment of the present application;

FIG. 14 is a schematic flowchart of implementing plug-in load balancing provided by an embodiment of the present application;

15 is a schematic structural diagram of a plug-in management apparatus provided by an embodiment of the present application;

FIG. 16 is a schematic diagram of the hardware structure of a plug-in management apparatus provided by an embodiment of the present application;

FIG. 17 is a schematic structural diagram of a chip provided by an embodiment of the present application.

Detailed ways

In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with basically the same function and effect. For example, the first value and the second value are only used to distinguish different values, and do not limit their order. Those skilled in the art can understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like are not necessarily different.

It should be noted that, in this application, words such as "exemplary" or "for example" are used to represent examples, illustrations or illustrations. Any embodiment or design described in this application as "exemplary" or "such as" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present the related concepts in a specific manner.

In this application, "at least one" means one or more, and "plurality" means two or more. "And/or", which describes the association relationship of the associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, which can indicate: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A, B can be singular or plural. The character "/" generally indicates that the associated objects are an "or" relationship. "At least one item(s) below" or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .

In the scenario where the plug-in framework may be used to allocate processes for micro-application plug-ins, usually in order to balance the number of plug-ins in the process, the plug-in will be scheduled according to the number of plug-ins, and the plug-in can be scheduled to a process with a smaller number of plug-ins in the current process middle. This coarse-grained plug-in scheduling method ignores the differences between plug-ins. Since different plug-ins consume different resources at runtime, this coarse-grained plug-in scheduling method may cause unbalanced intra-process load. question. In addition, in the above plug-in scheduling process, the isolation of normal plug-ins and problem plug-ins is not considered, so that the operation of the problem plug-in may affect the operation of other normal plug-ins in the process, which causes the micro-application to appear stuck during operation. Symptoms such as pauses, slow response, etc., affect the user's experience.

Therefore, an embodiment of the present application provides a plug-in management method. After receiving request information for requesting to run a micro-application, the plug-in corresponding to the request information is determined, and the characteristic information of the plug-in that affects the process operation is obtained. The plug-in is scheduled into the process. The plug-in scheduling method in this micro-application considers the impact of the plug-in on the process operation, and the plug-in can be reasonably scheduled to achieve load balancing when the process is running, so that the micro-application framework can be stable. run to enhance the user experience.

The embodiments of the present application are applied to a terminal device. In order to better understand the methods of the embodiments of the present application, the following first introduces the structure of the terminal device to which the embodiments of the present application are applied.

Exemplarily, FIG. 1 shows a schematic structural diagram of a terminal device 100 . The terminal 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, a battery 142, an antenna 1, an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, buttons 190, motor 191, indicator 192, camera 193, display screen 194, and Subscriber identification module (subscriber identification module, SIM) card interface 195 and so on. 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, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the terminal device 100 . In other embodiments of the present application, the terminal device 100 may include more or less components than those shown in the drawings, or combine some components, or separate some components, or arrange different components. The illustrated components may 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 (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (neural-network processing unit, NPU), etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

The controller can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold 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 called from memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby increasing the efficiency of the system.

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, a universal asynchronous transceiver (universal asynchronous transmitter) 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 (universal serial bus, USB) interface, etc.

The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 can be respectively coupled to the touch sensor 180K, the charger, the flash, the camera 193 and the like through different I2C bus interfaces. For example, the processor 110 may couple the touch sensor 180K through the I2C interface, so that the processor 110 and the touch sensor 180K communicate with each other through the I2C bus interface, so as to realize the touch function of the terminal device 100 .

The I2S interface can be used for audio communication. In some embodiments, the processor 110 may contain 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 can transmit audio signals to the wireless communication module 160 through the I2S interface, so as to realize the function of answering calls through a Bluetooth headset.

The PCM interface can also be used for audio communications, sampling, quantizing and encoding 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 can 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 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 typically used to connect the processor 110 with 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 implement the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface, so as to realize the function of playing music through the Bluetooth headset.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . MIPI interfaces include camera serial interface (CSI), display serial interface (DSI), etc. In some embodiments, the processor 110 communicates with the camera 193 through the CSI interface, so as to realize the shooting function of the terminal device 100 . The processor 110 communicates with the display screen 194 through the DSI interface to implement the display function of the terminal device 100 .

The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface may 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 the like. The GPIO interface can also be configured as I2C interface, I2S interface, UART interface, MIPI interface, etc.

The USB interface 130 is an interface that conforms to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like. The USB interface 130 can be used to connect a charger to charge the terminal device 100, and can also be used to transmit data between the terminal device 100 and peripheral devices. It can also be used to connect headphones to play audio through the headphones. The 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 embodiments of the present application is a schematic illustration, and does not constitute a structural limitation of the terminal device 100 . In other embodiments of the present application, the terminal device 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.

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

The power management module 141 is used for connecting 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 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, 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 charge management module 140 may also be provided in the same device.

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

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Antennas in terminal device 100 may be used to cover single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, the antenna 1 can be multiplexed as a diversity antenna of the 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 wireless communication solution including 2G/3G/4G/5G, etc. applied on the terminal device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA) and the like. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and then turn it into an electromagnetic wave for radiation through 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 may be provided in the same device as at least part of the modules of the processor 110 .

The modem processor may include a modulator and a demodulator. Wherein, 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. Then the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and passed to the application processor. The application processor outputs sound signals through audio devices (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or videos 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 independent of the processor 110, and may 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 terminal device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (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 can also receive the signal to be sent from the processor 110 , perform frequency modulation on it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2 .

In some embodiments, the antenna 1 of the terminal 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 terminal device 100 can communicate with the network and other devices through wireless communication technology. Wireless communication technologies may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Broadband Code Division Multiple Access (CDMA) address (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou satellite navigation system (BDS), quasi-zenith satellite system (quasi-zenith satellite system) , QZSS) and/or satellite based augmentation systems (SBAS).

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

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

The terminal device 100 can realize the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194 and the application processor.

The ISP is used to process the data fed back by the camera 193 . For example, when taking a photo, the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing, converting it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin tone. 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 .

Camera 193 is used to capture still images or video. The object is projected through the lens to generate an optical image onto 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 transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other formats of image signals. In some embodiments, the terminal device 100 may include 1 or N cameras 193 , where N is a positive integer greater than 1.

A digital signal processor is used to process digital signals, in addition to processing digital image signals, it can also process other digital signals. For example, when the terminal device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy, and the like.

Video codecs are used to compress or decompress digital video. The terminal device 100 may support one or more video codecs. In this way, the terminal device 100 can play or record videos in various encoding formats, for example, moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4 and so on.

The NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transfer mode between neurons in the human brain, it can quickly process the input information, and can continuously learn by itself. Applications such as intelligent cognition of the terminal device 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal 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 to save files like music, video etc in external memory card.

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

The terminal device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playback, recording, etc.

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

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

The receiver 170B, also referred to as "earpiece", is used to convert audio electrical signals into sound signals. When the terminal device 100 answers a call or a voice message, the voice can be answered by placing the receiver 170B close to the human ear.

The microphone 170C, also called "microphone" or "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 a human mouth, and input the sound signal into the microphone 170C. The terminal device 100 may be provided with at least one microphone 170C. In other embodiments, the terminal device 100 may be provided with two microphones 170C, which may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the terminal device 100 may further be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.

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

The pressure sensor 180A is used to sense pressure signals, and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 180A may be provided on the display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, and the like. The capacitive pressure sensor may be comprised of at least two parallel plates of conductive material. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The terminal device 100 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the terminal device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The terminal device 100 may also calculate the touched position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities may correspond to different operation instructions.

The gyro sensor 180B may be used to determine the motion attitude of the terminal device 100 . In some embodiments, the angular velocity of the end device 100 about three axes (ie, the x, y and z axes) may be determined by the gyro sensor 180B. The gyro sensor 180B can be used for image stabilization. Exemplarily, when the shutter is pressed, the gyro sensor 180B detects the shaking angle of the terminal device 100, calculates the distance to be compensated by the lens module according to the angle, and allows the lens to offset the shaking of the terminal device 100 through reverse motion to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenarios.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, the terminal device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist in positioning and navigation.

The magnetic sensor 180D includes a Hall sensor. The terminal device 100 can detect the opening and closing of the flip holster using the magnetic sensor 180D. In some embodiments, when the terminal device 100 is a flip machine, the terminal device 100 can detect the opening and closing of the flip according to the magnetic sensor 180D. Further, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, characteristics such as automatic unlocking of the flip cover are set.

The acceleration sensor 180E can detect the magnitude of the acceleration of the terminal device 100 in various directions (generally three axes). The magnitude and direction of gravity can be detected when the terminal device 100 is stationary. It can also be used to identify the posture of terminal devices, and can be used in applications such as horizontal and vertical screen switching, pedometers, etc.

Distance sensor 180F for measuring distance. The terminal device 100 can measure the distance through infrared or laser. In some embodiments, when shooting a scene, the terminal device 100 can use the distance sensor 180F to measure the distance to achieve fast focusing.

Proximity light sensor 180G may include, for example, light emitting diodes (LEDs) and light detectors, such as photodiodes. The light emitting diodes may be infrared light emitting diodes. The terminal device 100 emits infrared light to the outside through the light emitting diode. The terminal 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 terminal device 100 . When insufficient reflected light is detected, the terminal device 100 may determine that there is no object near the terminal device 100 . The terminal device 100 can use the proximity light sensor 180G to detect that the user holds the terminal device 100 close to the ear to talk, so as to automatically turn off the screen to save power. Proximity light sensor 180G can also be used in holster mode, pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense ambient light brightness. The terminal device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the terminal device 100 is in a pocket, so as to prevent accidental touch.

The fingerprint sensor 180H is used to collect fingerprints. The terminal device 100 can use the collected fingerprint characteristics to realize fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering incoming calls with fingerprints, and the like.

The temperature sensor 180J is used to detect the temperature. In some embodiments, the terminal device 100 uses the temperature detected by the temperature sensor 180J to execute the temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold value, the terminal device 100 reduces the performance of the processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the terminal device 100 heats the battery 142 to avoid abnormal shutdown of the terminal device 100 caused by the low temperature. In some other embodiments, when the temperature is lower than another threshold, the terminal device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

Touch sensor 180K, also called "touch device". 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, also called a “touch screen”. The touch sensor 180K is used to detect a touch operation on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to touch operations may be provided through display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the terminal device 100 , which is different from the position where the display screen 194 is located.

The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human voice. The bone conduction sensor 180M can also contact the pulse of the human body and receive the blood pressure beating signal. In some embodiments, the bone conduction sensor 180M can also be disposed in the earphone, combined with the bone conduction earphone. The audio module 170 can analyze the voice signal based on the vibration signal of the voice part vibrating bone mass obtained by the bone conduction sensor 180M, so as to realize the voice function. The application processor can analyze the heart rate information based on the blood pressure beat signal obtained by the bone conduction sensor 180M, and realize the function of heart rate detection.

The keys 190 include a power-on key, a volume key, and the like. Keys 190 may be mechanical keys. It can also be a touch key. The terminal device 100 may receive key input and generate key signal input related to user settings and function control of the terminal device 100 .

Motor 191 can generate vibrating cues. The motor 191 can be used for vibrating alerts for incoming calls, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, playing audio, etc.) can correspond to different vibration feedback effects. The motor 191 can also correspond to different vibration feedback effects for touch operations on different areas of the display screen 194 . Different application scenarios (for example: time reminder, 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 state, the change of the power, and can also be used to indicate a message, a missed call, a notification, and the like.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be contacted and separated from the terminal device 100 by inserting into the SIM card interface 195 or pulling out from the SIM card interface 195 . The terminal device 100 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card and so on. Multiple cards can be inserted into the same SIM card interface 195 at the same time. Multiple cards can be of the same type or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The terminal device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the terminal device 100 adopts an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100 .

The software system of the terminal device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture, and the like. The embodiments of the present application take an Android system with a layered architecture as an example to exemplarily describe the software structure of the terminal device 100 .

Exemplarily, FIG. 2 is a software structural block diagram of a terminal device 100 provided by an embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime (Android runtime) and a system library, and a 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, calendar, phone, map, phone, music, settings, mailbox, video, social, 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 window managers, content providers, resource managers, view systems, notification managers, and so on.

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

Content providers are used to store and retrieve data and make these data accessible to applications. Data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone book, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. View systems can be used to build applications. A display interface can consist 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 resource manager provides various resources for the application, such as localization strings, icons, pictures, layout files, video files and so on.

The notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages, and can disappear automatically after a brief pause without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also display notifications in the status bar at the top of the system in the form of graphs or scroll bar text, such as notifications of applications running in the background, and notifications on the screen in the form of dialog windows. For example, text information is prompted in the status bar, a prompt sound is issued, the terminal device vibrates, and the indicator light flashes.

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

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

The application layer and the application framework layer run in virtual machines. 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 lifecycle management, stack management, thread management, safety and exception management, and garbage collection.

A system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

The Surface Manager is used to manage the display subsystem and provides a fusion 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 a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG and PNG, etc.

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

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 drivers, camera drivers, audio drivers, and sensor drivers.

It should be noted that, the plug-in management method provided by the embodiment of the present application may be executed at the application program layer and the application program architecture layer in FIG. 2 .

The workflow of the software and hardware of the terminal device 100 is exemplarily described below in conjunction with a scenario in which an application program is started or an interface switching occurs in an application program.

When the touch sensor 180K receives a touch operation, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes touch operations into raw input events (including touch coordinates, touch strength, timestamps of touch operations, etc.). Raw input events are stored at the kernel layer. The application framework layer obtains the original input event from the kernel layer, and identifies the control corresponding to the input event.

The following describes in detail the operation process of setting the application function split screen in the application program provided by the embodiments of the present application and the display process of the split screen function interface with reference to the accompanying drawings. It should be noted that, “at the time of” in the embodiments of the present application may be the moment when a certain situation occurs, or it may be within a period of time after the occurrence of a certain situation, and the embodiment of the present application does not do this. limited.

In this embodiment of the present application, the electronic device 100 may be used for split-screen display of multiple functions of an application. Specifically, the electronic device 100 may be a mobile phone, a tablet computer, a smart watch, a smart bracelet, a smart earphone, a smart glasses, or other terminal devices with a display screen, etc., which are not limited in this embodiment of the present application.

Now, taking the electronic device 100 as a terminal device as an example, the implementation of a micro-application plug-in management method under the framework of an application (application, APP) (or possibly called an application) by the terminal device will be described.

Exemplarily, FIG. 3 is a schematic diagram of a framework of an application program provided by an embodiment of the present application.

As shown in FIG. 3 , the application 300 may include other micro-applications such as a micro-application 301 and a micro-application 302 . The micro-application 301 may include: plug-in 3031, plug-in 3032, plug-in 3041, plug-in 3042 and other plug-ins. The scenario shown in FIG. 3 can be understood as: the micro application may include other functions such as function 303 and function 304 .

It can be understood that one application may include multiple micro-applications, one micro-application may include multiple functions, and one function may correspond to one or more plug-ins. In the scenario of running micro-applications, a process is the basic unit of scheduling by the system. When the user triggers the running of the micro-application, the terminal device can schedule the plug-in corresponding to the trigger operation to the process to run.

Exemplarily, when the user triggers the function 303, the terminal device will schedule other plug-ins such as plug-ins 3031 and 3032 in the function 303; when the user triggers the function 304, the terminal device will schedule the plug-ins 3041 and 3042 in the function 304. Wait for other plug-ins for scheduling; the terminal device schedules the plug-in corresponding to the function to the corresponding process to run.

In the scenario provided by the embodiment of the present application, the terminal device can load and run multiple micro-applications in the form of plug-ins, so as to provide users with diversified services. At the same time, the loading of micro-applications often needs to depend on the application framework environment. Among them, micro-applications are run in the application in the form of one or more plug-ins. Understandably, the application framework runs on the end device. The application framework can manage plugins in microapps and schedule plugins to run in processes.

It can be understood that the embodiments of the present application are applicable to the above application scenarios for micro-application plug-in management. Wherein, the embodiment of the present application uses a scenario in which the micro-application plug-in management method can be implemented as an example, and other specific application scenarios are not limited.

The vocabulary described in the embodiments of the present application will be described below. It can be understood that the description is for explaining the embodiments of the present application more clearly, and does not necessarily constitute a limitation on the embodiments of the present application.

The micro-applications described in the embodiments of this application may be small-scale applications that are highly focused on one function, and their loading and running often depend on the framework environment. For example, when running a social application applet in a social application, the social application can be understood as a framework environment, and the operation of the applet must depend on the framework of the social application before it can be loaded and run. It is understandable that there is no way for this applet to run without social networking.

The plug-ins described in the embodiments of the present application may be functional components of the micro-application, and the micro-application runs in the framework in the form of one or more plug-ins. For example, in a micro-app, the user has many functions that can be triggered, and the user can click any function to trigger the loading of the plug-in corresponding to the function.

The dynamic loading described in the embodiments of the present application may be a mechanism for allowing the system to load and use the software corresponding to the loading process at runtime.

The process described in the embodiments of the present application may be a running activity of a program in a computer on a certain data set, which is the basic unit of resource allocation and scheduling by the system, and the system may allocate resources to the process.

The framework described in the embodiments of the present application may be a framework in the context of Internet technology (internet technology, IT), and specifically refers to a support structure with certain constraints designed to solve an open problem. In this structure, more components can be expanded and placed according to specific problems, so that a complete solution to the problem can be constructed more quickly and easily. For example, the framework in this embodiment of the present application specifically refers to a container carrier responsible for loading, running, and managing micro-application plug-ins. The framework is not only responsible for loading and running the micro-application plug-in, but also needs to provide the scheduling and management capabilities of the micro-application plug-in. In addition, the framework can create several processes, and allocate each micro-application plug-in to different processes according to a certain allocation principle. Generally speaking, the number of micro-application plug-ins is much larger than the number of processes.

The plug-in framework described in the embodiments of the present application may be a container carrier dynamically loaded in the form of a plug-in using a plug-in technology, which may be an APP in essence. Implementing a plug-in framework can realize the mutual call between plug-in code loading and the framework, the mutual access between plug-in resource loading and the framework, and the management of the plug-in life cycle. For example, plug-in frameworks enable dynamic loading of plug-ins in micro-apps.

The process allocation described in the embodiments of the present application may be that the terminal device allocates the micro-application plug-ins to different processes to run.

The process snapshot described in the embodiment of the present application may be a statistical snapshot that records the current process in the system and the data in the process.

The load described in the embodiment of the present application may be: measuring the resource consumption of the process in which the plug-in is running when it is running. For example, load is determined by two metrics, memory and power consumption.

The cloud computing platform (or cloud platform or cloud device, etc.) described in the embodiments of this application may be services based on hardware resources and software resources, and the cloud platform may provide other capabilities such as computing, network, and storage.

The machine learning described in the embodiments of the present application may be a mathematical model or a computational model that imitates the structure and function of a biological neural network, and is used to estimate or approximate a function. The machine learning model needs to be trained with a large number of samples. After the model is trained, the machine learning model can be used to make predictions.

The installation-free running application package (android application package, APK) described in the embodiment of the present application can be understood as a plug-in, and the APP that supports the plug-in in the installation-free running APK loads and runs the plug-in at runtime, and some less commonly used APPs can be loaded and run. The functional modules of APP are made into plug-ins, which reduces the size of the installation package, realizes the dynamic expansion of APP functions, and facilitates the decoupling and update expansion between functional modules.

Hereinafter, the technical solutions of the present application will be described in detail through specific embodiments. It should be noted that the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

Exemplarily, FIG. 4 is a schematic flowchart of a plug-in management method provided by an embodiment of the present application. As shown in Figure 4, the method may include the following steps:

S401. Receive request information for requesting to run a micro-application.

In this embodiment of the present application, the request information may be request information sent after the user triggers the micro-application through a trigger operation. The terminal device can receive request information for requesting to run the micro-application. Exemplarily, when the user triggers to start the micro-application, or when a certain function in the micro-application is triggered, request information for requesting to run the micro-application can be sent, and the terminal device receives the request information.

Wherein, the user's trigger operation may include: single click operation, multiple click operation, touch operation (the touch information of the touch operation may include touch coordinates, touch force or time stamp of the touch operation and other types of touch information), sliding Other types of trigger actions such as actions, drag actions, and/or long-press actions. It can be understood that, the specific trigger operation is not limited in the embodiment of the present application.

Exemplarily, FIG. 5 is a schematic interface diagram of a user-triggered micro-application plug-in according to an embodiment of the present application.

As shown in a in FIG. 5, the interface may be the home screen of the terminal device, and the home screen may include one or more of the following application icons: setting icon, calendar icon, social icon 501, data icon and other types of application icons. When the user triggers the social icon 501 through a trigger operation such as clicking, dragging or long pressing on the home screen, the terminal device responds to the user's operation to trigger the social icon 501, and the terminal device enters the interface as shown in b in Figure 5 .

In the interface shown in b in FIG. 5 , when the user triggers the discovery control 502 by clicking, dragging, or long pressing in the interface, the terminal device responds to the user triggering the operation of the discovery control 502, and the terminal device enters the The interface shown in c in Figure 5.

As shown in c in Figure 5, the interface may include one or more of the following functional controls: sweep controls, shake controls, nearby friend controls, game controls, applet controls 503 or other Type of functional control. When the user triggers the applet control 503 by clicking, dragging or long pressing in the interface, the terminal device enters the interface as shown in FIG. 6 in response to the user triggering the operation of the applet control 503 .

As shown in FIG. 6, the interface may include one or more of the following applet controls: My applet control, video applet control, reading applet control, shopping applet control 601, takeaway applet controls or other types of applet controls. During the process of the user opening any applet as shown in FIG. 6 , the terminal device may receive request information for requesting to run the micro-application.

Exemplarily, when the user triggers the shopping applet control 601 through a trigger operation such as clicking, dragging, or long pressing in the interface, the terminal device responds to the trigger operation, and the terminal device receives the request information for running the micro-application, and the terminal device responds to the trigger operation. The device schedules the plug-in corresponding to the opening shopping applet control 601 to a corresponding process to run, and the terminal device enters the interface shown in FIG. 7 .

As shown in Figure 7, the interface may include one or more of the following functional controls: a new control today, a supermarket control, a train ticket control, a coupon control, a recharge center control 701, a feature center control, and a pet control , category controls, or other types of functional controls. During the process of the user triggering any function of the applet as shown in FIG. 7 , the terminal device may receive request information for requesting to run the micro-application.

Exemplarily, when the user triggers the recharge center control 701 through a trigger operation such as clicking, dragging or long pressing in the interface, the request information for running the function in the micro-application is sent, and the terminal device responds to the trigger operation and receives the To run the function request information in the micro-application, the terminal device schedules the plug-in corresponding to the recharge center control 701 to a corresponding process to run, and the terminal device can enter the interface corresponding to the recharge center control 701 .

To sum up, when the user triggers the opening of the micro application, or when triggering a function in the micro application, the request information for requesting to run the micro application can be sent. The plug-in management method provided in the embodiment performs plug-in scheduling.

It should be noted that the user interfaces of the terminal equipment shown in the above Figures 5 to 7 are only used for examples, and do not constitute a limitation to the embodiments of the present application. The operations in the page switching scene are all user operations in the embodiments of the present application.

In a possible implementation manner, entering the application opening scene or the page switching scene may also be automatically triggered by the terminal device, which is not specifically limited in this embodiment of the present application.

S402. Determine the plug-in corresponding to the request information.

In this embodiment of the present application, after receiving the request information for running the micro-application sent by the user triggering the micro-application, the terminal device parses one or more plug-ins corresponding to the request information. This plugin is used to implement some or all of the functionality of the microapp.

Exemplarily, when the user opens the micro-application, or triggers a function in the micro-application, request information for requesting to run the micro-application can be sent, and the terminal device receives the request information and determines the plug-in corresponding to the request information.

For example, as shown in the interface shown in FIG. 7 , when the user triggers the recharge center function control 701, the terminal device responds to the request information, and the terminal device searches for one or more plug-ins corresponding to the recharge center function control 701, and subsequently the terminal device will One or more plug-ins corresponding to the function control are dispatched to the corresponding process to run, and the terminal device can display the interface corresponding to the function control.

S403. Obtain feature information of the plug-in.

In this embodiment of the present application, the feature information is information that the plug-in affects the running of the process.

Exemplarily, the association relationship between the plug-in and the feature information is obtained in advance, and after the plug-in is acquired, the feature information of the plug-in is searched according to the association relationship; After acquiring the plug-in, input the plug-in into the model, and use the model to output the feature information of the plug-in. It can be understood that, in this embodiment of the present application, the method for acquiring the feature information of the plug-in is not limited.

In a possible implementation manner, the characteristic information of the plug-in may include one or more of the following: load information, security level information, associated plug-in information, running time information, plug-in priority information or other types of characteristic information. It can be understood that the feature information of the plug-in may also include other contents according to the actual application scenario, and the feature information of the plug-in is not limited in this embodiment of the present application.

Exemplarily, the load information of the plug-in is information that identifies the memory and power consumption of the plug-in when running. The load information of each plug-in in the process is differentiated, and it can be understood that the load information of each plug-in may be the same or different.

Exemplarily, the security level information of the plug-in is information identifying plug-ins with different risk levels of the plug-in, and a corresponding scheduling policy is executed according to the security level information of each plug-in.

Exemplarily, the associated plug-in information of the plug-ins is information that identifies related plug-ins that have an association relationship between the plug-ins. The related plug-ins are the plug-ins that read the same resources.

Exemplarily, the running time information of the plug-in is information that identifies the time consumed by the plug-in when running.

Exemplarily, the priority information of the plug-in is information that identifies the frequency at which the user runs the plug-in. The higher the frequency that the user runs the plug-in, the higher the priority of the plug-in.

S404. Schedule the plug-in according to the feature information.

In the embodiment of the present application, different plug-in scheduling policies are executed according to different feature information of the plug-in.

Exemplarily, the characteristic information of the plug-in may include load information of the plug-in. When scheduling the plug-in according to the characteristic information, the predicted load of the process that can be used to run the plug-in may be calculated, and the predicted load may be the prediction of the process assuming that the plug-in is set in the process. Total load, the plugin can be set in any process whose predicted load does not exceed the load threshold set by the system. The load threshold may be the highest load value allocated by the terminal device to the process running the micro-application.

Exemplarily, the feature information of the plug-in may include the security level information of the plug-in. For example, the security level information may identify the plug-in as a security plug-in, a risk plug-in or an abnormal plug-in. In the process of the plug-in, or set the risk plug-in in a separate process set by the system, or disable the abnormal plug-in.

Exemplarily, the feature information of the plug-in may include priority information of the plug-in, and according to the priority information of the plug-in, a plug-in with a high priority may be scheduled to a process with a current high priority.

It can be understood that the plug-in scheduling according to the feature information of the plug-in may also include other contents according to the actual application scenario, and the method for scheduling the plug-in according to the feature information is not limited in this embodiment of the present application.

The plug-in management method provided by the embodiment of the present application can perform reasonable scheduling based on characteristic information between plug-ins, realize load balancing of process operation, enable the micro-application framework to run smoothly, and further improve the user's sense of experience.

On the basis of the embodiment corresponding to FIG. 4 , in a possible implementation manner, S404 includes: setting the plug-in in a process adapted to the feature information of the plug-in.

In a possible implementation manner, the characteristic information includes load information, and setting the plug-in in a process that is compatible with the characteristic information of the plug-in according to the characteristic information of the plug-in includes: calculating the first process that can be used to run the plug-in according to the load information of the plug-in. Predicted load; the predicted load of the first process is the total load of the first process when the plug-in is set in the first process; the number of the first process is multiple. The plug-in is set in a first target process; the first target process is a process in the first process whose predicted load does not exceed the first load threshold.

Exemplarily, as shown in FIG. 8 , running in process 801 are: plug-in 8011, plug-in 8012, plug-in 8013 and plug-in 8014; running in process 802: plug-in 8021, plug-in 8022 and plug-in 8023; running in process 803: plug-in 8031 and plugin 8032. The micro-app contains plugins 804 , plugins 805 , plugins 806 , and plugins 807 that are not yet running.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information of the plug-in 804 . Calculate the predicted load of the process 801 , the process 802 or the process 803 by placing the plug-in 804 in the process 801 , the process 802 or the process 803 . The predicted load of the process 801 is the sum of the load information of the plug-in 804 and the total load of the four plug-ins running in the process 801; the predicted load of the process 802 is the load information of the plug-in 804 and the three plug-ins running in the process 802. The predicted load of the process 803 is the sum of the load information of the plug-in 804 and the total load of the two plug-ins running in the process 803 . It can be understood that the predicted load is to estimate the total load of the process after the plug-in to be scheduled is scheduled to the process. In a specific application, there may be no execution steps for scheduling the plug-in to the process.

Determine the relationship between the predicted load of the process 801, the predicted load of the process 802, or the predicted load of the process 803 and the first load threshold of the process. When the predicted load of the process 801 , the predicted load of the process 802 or the predicted load of the process 803 does not exceed the first load threshold, the plug-in 804 is scheduled to any one of the process 801 , the process 802 or the process 803 . When the predicted load of the process 801 does not exceed the first load threshold, and the predicted load of the process 802 and the predicted load of the process 803 both exceed the first load threshold, the plug-in 804 may be scheduled into the process 801 . In process scheduling, it is possible to predict whether the first process exceeds the load threshold when the plug-in is scheduled to the first process. Setting the plug-in in the first target process whose predicted load does not exceed the load threshold can avoid the occurrence of the first process after scheduling. When the load threshold is exceeded, load balancing is realized when the process is running.

In a possible implementation manner, the feature information includes associated plug-in information of the plug-in, and setting the plug-in in a process adapted to the feature information of the plug-in according to the feature information of the plug-in includes: setting the plug-in in a third process, the third process For processes that run related plugins with associated plugin information. The related plugins include: plugins that have the same resources as the plugins read.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the associated plug-in information of the plug-in 804 . Get the related plugins in the process that read the same resources as plugin 804. When the resources read by the plug-in 8021 and the plug-in 804 are the same, the plug-in 804 can be scheduled to the process 802 where the plug-in 8021 is located.

In a possible implementation manner, the feature information includes the running time information of the plug-in, and setting the plug-in in a process suitable for the feature information of the plug-in according to the feature information of the plug-in, including: obtaining the running time of each running plug-in in the process. , to set the plug-ins to be scheduled in a process whose running duration of each plug-in is similar to the running duration of the plug-in to be scheduled.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the runtime information of the plug-in 804 . Get the running time of plugin 8011, plugin 8012, plugin 8013, plugin 8014, plugin 8021, plugin 8022, plugin 8023, plugin 8031, and plugin 8032 in the process. The relationship between the running time of the plug-in 804 and the running time of each plug-in is determined. When the difference between the running duration of the plug-in to be scheduled and the running duration of one of the above plug-ins does not exceed the preset threshold set by the system, the plug-in to be scheduled is scheduled to the process where the plug-in is located. When the difference between the running time of the plug-in 804 and the running time of the plug-in 8021 does not exceed the preset threshold, the plug-in 804 may be scheduled to the process 802 where the plug-in 8021 is located. When the process is running, multiple associated plug-ins can be run at the same time. Since the resources read between the associated plug-ins are the same, the energy consumption of performing multiple operations of reading the same resource can be reduced, thereby reducing the energy consumption of the process running. .

In a possible implementation manner, the feature information includes the priority information of the plug-in, and the plug-in is set in a process suitable for the feature information of the plug-in according to the feature information of the plug-in, including: obtaining the priority of each plug-in and each running process. The priority of the plug-in with high priority is set in the corresponding process with high priority. The priority of the plug-in may be determined according to the frequency of triggering the plug-in by the user, and the higher the frequency of triggering the plug-in by the user, the higher the priority of the plug-in; the priority of the process may be preset for the process by the terminal device.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the priority information of the plug-in 804 , the plug-in 805 , or the plug-in 806 . Get the priority of each running process. When the priority of the plug-in 804 is higher, the plug-in 804 can be scheduled to the process 801 with the higher priority set by the system. When the priority of the plug-in 805 is low, the plug-in can be scheduled to the process 802 with a low priority set by the system. When the priority information of the plug-in 806 meets neither the high priority nor the low priority, the plug-in may be scheduled to the process 803 with the default priority set by the system. The plug-ins with high priority are preferentially scheduled to the corresponding processes to ensure the normal implementation of the more important functions in the micro-application.

On the basis of the embodiment corresponding to FIG. 4 , in a possible implementation manner, S404 includes: disabling the plug-in according to the feature information.

In a possible implementation, the feature information includes security level information, and the plugin is set in a process that is compatible with the feature information of the plugin according to the feature information of the plugin, including: when the security level information indicates that the plugin is a security plugin The plug-in is allocated in a process that can be used to run the plug-in; or, in the case where the security level information indicates that the plug-in is a risk plug-in, the plug-in is allocated in a separate process; or, in the case where the security level information indicates that the plug-in is an abnormal plug-in, Disable plugins.

The security level information may include a process crash probability caused by a plug-in, a memory leak probability caused by a plug-in, or a probability calculated according to the process crash probability and the memory leak probability. When the security level information is less than the first value, it means that the plug-in is a security plug-in; when the security level information is greater than or equal to the first value and less than or equal to the second value, it means that the plug-in is a risk plug-in; when the security level information is greater than or equal to the first value, it means the plug-in is a risk plug-in; The second value indicates that the plug-in is an abnormal plug-in. Among them, the probability of a process crash caused by the plugin is the ratio of the total number of times the plugin appears in the crash process to the total number of process crashes when the process crashes due to the exception of the plugin; the probability of memory leak caused by the plugin is , when a memory leak occurs in a process due to an exception of the plug-in, the ratio of the total number of times the plug-in appears in the memory leak process to the total number of process memory leaks. The first value and the second value are thresholds of the security level information set by the terminal device to identify the type of the plug-in.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information of the plug-in 804 , the plug-in 805 or the plug-in 806 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 , the plug-in 805 or the plug-in 806 . When the plug-in 804 is a normal plug-in, the plug-in is allocated to the process 801 that can run the plug-in. When the plug-in 805 is a risk plug-in, the plug-in is allocated to an independent process 802 set by the terminal device. When the plug-in 806 is an abnormal plug-in, the plug-in is disabled, and an error report of the plug-in 806 is sent to the terminal device. Execute a more appropriate scheduling policy for plug-ins according to plug-ins of different security levels.

On the basis of the embodiment corresponding to FIG. 4 , in a possible implementation manner, S404 includes: according to the plurality of characteristic information of the plug-in, the plug-in may be set in a process suitable for the plurality of characteristic information of the plug-in.

In a possible implementation, the feature information includes load information and security level information, and according to the feature information of the plugin, the plugin is set in a process that is compatible with the feature information of the plugin, including: when the security level information indicates that the plugin is a secure plugin. , calculate the predicted load of the second process that can be used to run the security plug-in according to the load information of the security plug-in; the predicted load of the second process is the total load of the second process when the security plug-in is set in the second process; The number is multiple; the security plug-in is set in the second target process, and the second target process is a process in the second process whose predicted load does not exceed the second load threshold.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information and security level information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled using the load information of the plug-in. The process of scheduling the plug-in by using the load information of the plug-in will not be repeated.

When the plug-in 804 is a risk plug-in, the plug-in is allocated to an independent process 802 set by the terminal device. When the plug-in 804 is an abnormal plug-in, the plug-in is disabled, and an error report of the plug-in 804 can be sent to the terminal device.

In a possible implementation, the feature information includes the load information of the plug-in and the associated plug-in information, and the plug-in is set in a process suitable for the feature information of the plug-in according to the feature information of the plug-in, including: calculating the prediction of the process according to the load characteristics of the plug-in. Load, the plug-in is set in the process of running the relevant plug-in related to the associated plug-in information, and the predicted load of the process does not exceed the load threshold set by the terminal device.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information of the plug-in 804 and the associated plug-in information. Obtain the related plug-ins with the same resources read by the plug-in 804 in the process. When the resources read by the plug-in 8011 or the plug-in 8021 and the plug-in 804 are the same, the plug-in 804 is represented, and the plug-in 8011 or the plug-in 8021 is a related plug-in.

Calculate the predicted load of the process 801 or process 802 where the plug-in 804 is located, and determine the relationship between the predicted load of the process 801 or the predicted load of the process 802 and the load threshold of the process. When the predicted load of the process 801 and the process 802 does not exceed the load threshold, the plug-in 804 can be scheduled to any process of the process 801 or the process 802. When the predicted load of the process 801 does not exceed the load threshold, and the predicted load of the process 803 exceeds the load threshold, the plug-in 804 is scheduled to the process 801 .

In a possible implementation, the feature information includes load information and running duration information of the plug-in, and according to the feature information of the plug-in, the plug-in is set in a process that is compatible with the feature information of the plug-in, including: according to the load information of the plug-in. The predicted load of the process of the plug-in, calculate the predicted running time of the process that can be used to run the plug-in according to the running time of the plug-in, and set the plug-in in the process where the product of the predicted load and the predicted running time does not exceed the threshold set by the system .

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information and the running duration information of the plug-in 804 . The plug-in is set in the process 801, the process 802 or the process 803, and the predicted load of each process of the process 801, the process 802 or the process 803 and the predicted running time of each process are calculated. The predicted running duration of the process 801 is the sum of the running duration information of the plugin 804 and the total running duration of the four plugins running in the process 801 ; the predicted running duration of the process 802 is the running duration information of the plugin 804 and the The sum of the total running time of the three running plug-ins; the predicted running time of the process 803 is the sum of the running time information of the plug-in 804 and the total running time of the two plug-ins running in the process 803 . It can be understood that predicting the running time is to estimate the total running time of the process after the plug-in to be scheduled is scheduled to the process. In a specific application, there may be no execution steps for scheduling the plug-in to the process.

Determine the relationship between the product of the predicted load of each of the process 801, the process 802 or the process 803 and the predicted running time of each process and the threshold value set by the system. The plug-in 804 is scheduled to a process in which the product of the predicted load of the process and the predicted running time of the process does not exceed the threshold set by the system. When the product of the predicted load of each process of the process 801, the process 802 or the process 803 and the predicted running time of each process does not exceed the threshold set by the system, the plug-in 804 can be scheduled to any one of the process 801, the process 802 or the process 803. in progress.

In a possible implementation manner, the feature information includes load information and priority information of the plug-in, and according to the feature information of the plug-in, the plug-in is set in a process suitable for the feature information of the plug-in, including: obtaining the priority and running status of each plug-in. The priority of each process is set, and the plug-in with high priority is set in the corresponding process with high priority, and the predicted load of the process does not exceed the load threshold set by the terminal device.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information and priority information of the plug-in 804 . When the priority of the plug-in 804 is higher, the plug-in is scheduled to the process 801 or the process 802 with the higher priority set by the system. When the priority of the process 801 is the same as that of the process 802, the plug-in is scheduled using the load information of the plug-in.

The calculation places the plug-in 804 in the process 801 or the process 802, the predicted load of the process 801 or the predicted load of the process 802. Determine the relationship between the predicted load of the process 801 or the predicted load of the process 802 and the load threshold of the process. When the predicted load of the process 801 does not exceed the load threshold, and the predicted load of the process 802 exceeds the load threshold, the plug-in 804 is scheduled into the process 801 .

In a possible implementation, the feature information includes the security level information of the plug-in and the associated plug-in information, and according to the feature information of the plug-in, the plug-in is set in a process suitable for the feature information of the plug-in, including: the security level information indicates that the plug-in is safe. In the case of a plugin, set the plugin to run in the same process as the associated plugin associated with the associated plugin information.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information of the plug-in 804 and the associated plug-in information. The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled using the plug-in associated plug-in information. The process of scheduling the plug-in using the associated plug-in information of the plug-in will not be repeated. When the plug-in 804 is identified as a risk plug-in or an abnormal plug-in, the security level information of the plug-in is used for scheduling, and the process of scheduling the plug-in using the security level information of the plug-in will not be repeated.

In a possible implementation manner, the feature information includes the security level information and runtime length information of the plug-in, and according to the feature information of the plug-in, the plug-in is set in a process suitable for the feature information of the plug-in, including: the security level information indicates that the plug-in is safe. In the case of plug-ins, obtain the running duration of each running plug-in in the process, and set the plug-in to be scheduled in a process whose running duration is similar to that of the plug-in to be scheduled.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information and the running duration information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled by using the running time information of the plug-in. The process of scheduling the plug-in by using the running time information of the plug-in will not be described again. When the plug-in 804 is identified as a risk plug-in or an abnormal plug-in, the security level information of the plug-in is used for scheduling, and the process of scheduling the plug-in using the security level information of the plug-in will not be repeated.

In a possible implementation manner, the feature information includes the security level information and priority information of the plug-in, and according to the feature information of the plug-in, the plug-in is set in a process suitable for the feature information of the plug-in, including: the security level information indicates that the plug-in is safe. In the case of plug-ins, obtain the priority of each plug-in and the priority of each running process, and set the plug-in with high priority in the corresponding process with high priority.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information and priority information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled using the priority information of the plug-in. The process of scheduling the plug-in using the priority information of the plug-in will not be described again. When the plug-in 804 is identified as a risk plug-in or an abnormal plug-in, the security level information of the plug-in is used for scheduling, and the process of scheduling the plug-in using the security level information of the plug-in will not be repeated.

In a possible implementation manner, the feature information includes plug-in associated plug-in information and running duration information, and the plug-in is set in a process suitable for the plug-in feature information according to the plug-in feature information, including: in the acquisition process, each running The running time of the plug-in is set in the process of running the relevant plug-in related to the associated plug-in information, and the running time of each plug-in in the process is similar to the running time of the plug-in to be scheduled.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the associated plug-in and runtime information of the plug-in 804 . Get the related plugins in the process that read the same resources as plugin 804, and the running time of plugins 8011, 8012, 8013, 8014, 8021, 8022, 8023, 8031, and 8032 in the current process . When the resources read by the plug-in 8011 or the plug-in 8021 and the plug-in 804 are the same, it means that the plug-in 8011 or the plug-in 8021 and the plug-in 804 are related plug-ins.

Use the plugin's runtime information to schedule plugins. Obtains the running time of each plug-in of plug-in 8011, plug-in 8012, plug-in 8013, plug-in 8014, plug-in 8021, plug-in 8022, and plug-in 8023 in the process where the relevant plug-in is located. The relationship between the running time of the plug-in 804 and the running time of each plug-in is determined. When the difference between the running duration of the plug-in to be scheduled and the running duration of one of the above plug-ins does not exceed the preset threshold set by the system, the plug-in to be scheduled is scheduled to the process where the plug-in is located. When the difference between the running time of the plug-in 804 and the running time of the plug-in 8021 does not exceed the preset threshold, the plug-in 804 is scheduled to the process 802 where the plug-in 8021 is located.

In a possible implementation manner, the feature information includes associated plugin information and priority information of the plugin, and according to the feature information of the plugin, the plugin is set in a process that is compatible with the feature information of the plugin, including: obtaining the priority and ongoing status of each plugin. The priority of each running process, the plug-in with high priority is set in the corresponding process with high priority, and the process satisfies that the plug-in to be scheduled and the related plug-in related to the associated plug-in information run in the same process.

Exemplarily, in the scheduling scenario shown in FIG. 8 , the user performs scheduling according to the associated plug-in information and priority information of the plug-in 804 .

You can first determine the scope of the process according to the plug-in's associated plug-in information, and then use the plug-in priority information to select an appropriate process for scheduling. Obtain the related plug-ins that have the same resources read by the plug-in 804 in the process. When the resources read by the plug-in 8011 or the plug-in 8021 and the plug-in 804 are the same, the plug-in 804 and the plug-in 8011 or the plug-in 8021 are represented as related plug-ins. It is determined that the plug-in can be scheduled in process 801 or process 802 that satisfies the associated plug-in information. Reuse the priority information of the plug-in to schedule the plug-in. The plug-in 804 is scheduled to the process 801 with a higher priority of the process set by the system.

It is also possible to first determine the scope of the process according to the priority information of the plug-in, and then use the associated plug-in information of the plug-in to select an appropriate process for scheduling. When the priority of the plug-in 804 is relatively high, and the priorities of the process 801 and the process 802 set by the terminal device are both relatively high, the related information of the plug-in is further used to schedule the plug-in. When the plug-in 804 and the plug-in 8013 in the process 801 are mutually related plug-ins, the plug-in is scheduled to the process 801 .

In a possible implementation manner, the feature information includes the runtime length information and priority information of the plug-in, and according to the feature information of the plug-in, the plug-in is set in a process suitable for the feature information of the plug-in, including: obtaining the priority and the current status of each plug-in. For the priority of each running process, the plug-in with high priority is set in the corresponding process with high priority, and the process with high priority satisfies that the running duration of each plug-in in the process is similar to that of the plug-in to be scheduled.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the runtime information of the plug-in 804 and the priority information of the plug-in. in the process. When the priority of the plug-in 804 is higher, the plug-in is scheduled to the process 801 or the process 802 with a higher priority set by the system. When the priority of the process 801 is the same as that of the process 802, the plug-in is scheduled using the information of the running time of the plug-in.

Obtains the running time of each plug-in 8011, plug-in 8012, plug-in 8013, plug-in 8014, plug-in 8021, plug-in 8022, and plug-in 8023 in the process where the relevant plug-in is located. The relationship between the running time of the plug-in 804 and the running time of each plug-in is determined. When the difference between the running duration of the plug-in to be scheduled and the running duration of one of the above plug-ins does not exceed the preset threshold set by the system, the plug-in to be scheduled is scheduled to the process where the plug-in is located. When the difference between the running time of the plug-in 804 and the running time of the plug-in 8021 does not exceed the preset threshold, the plug-in 804 is scheduled to the process 802 where the plug-in 8021 is located.

In a possible implementation, the feature information includes the security level information, load information and associated plugin information of the plug-in, and according to the feature information of the plug-in, the plug-in is set in a process suitable for the feature information of the plug-in, including: indicating in the security level information. When the plug-in is a secure plug-in, the predicted load of the process is calculated according to the load characteristics of the plug-in, and the plug-in is set in the process of running the relevant plug-in related to the associated plug-in information, and the predicted load of the process does not exceed the load threshold set by the terminal device. .

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information of the plug-in 804 and the associated plug-in information. The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled using the load information of the plug-in and the associated plug-in information. The process of scheduling the plug-in by using the load information of the plug-in and the associated plug-in information will not be described again. When the plug-in 804 is identified as a risk plug-in or an abnormal plug-in, the security level information of the plug-in is used for scheduling, and the process of scheduling the plug-in using the security level information of the plug-in will not be repeated.

In a possible implementation manner, the feature information includes the security level information, load information and running time information of the plug-in, and the plug-in is set in a process suitable for the feature information of the plug-in according to the feature information of the plug-in, including: indicating in the security level information. If the plug-in is a secure plug-in, calculate the predicted load of the process that can be used to run the plug-in according to the load information of the plug-in, calculate the predicted running time of the process that can be used to run the plug-in according to the running time of the plug-in, and set the plug-in to the predicted load. The product of the predicted running time does not exceed the threshold set by the system in the process.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information, load information and running duration information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled by using the load information and running time information of the plug-in. The process of scheduling the plug-in by using the load information and the running time information of the plug-in will not be repeated. When the plug-in 804 is identified as a risk plug-in or an abnormal plug-in, the security level information of the plug-in is used for scheduling, and the process of scheduling the plug-in using the security level information of the plug-in will not be repeated.

In a possible implementation manner, the feature information includes the security level information, load information and priority information of the plug-in, and the plug-in is set in a process suitable for the feature information of the plug-in according to the feature information of the plug-in, including: indicating in the security level information. If the plug-in is a security plug-in, obtain the priority of each plug-in and the priority of each running process, and set the plug-in with high priority in the corresponding process with high priority, and the predicted load of the process does not exceed the terminal The load threshold set by the device.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information, load information and priority information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled using the load information and priority information of the plug-in. The process of scheduling the plug-in by using the load information and priority information of the plug-in will not be repeated. When the plug-in 804 is identified as a risk plug-in or an abnormal plug-in, the security level information of the plug-in is used for scheduling, and the process of scheduling the plug-in using the security level information of the plug-in will not be repeated.

In a possible implementation manner, the feature information includes the security level information of the plug-in, the associated plug-in information and the running duration information, and the plug-in is set in a process suitable for the feature information of the plug-in according to the feature information of the plug-in, including: in the security level information Indicates that when the plug-in is a secure plug-in, obtain the running time of each plug-in running in the process, set the plug-in in the process of running the relevant plug-in related to the associated plug-in information, and the running time of each plug-in in the process is related to the to-be-scheduled plug-in. The runtime of the plugin is similar.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information of the plug-in 804 , the associated plug-in information and the running duration information. The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled by using the plug-in associated plug-in information and runtime information of the plug-in. The process of scheduling the plug-in using the plug-in associated plug-in information and runtime information of the plug-in will not be repeated. When the plug-in 804 is identified as a risk plug-in or an abnormal plug-in, the security level information of the plug-in is used for scheduling, and the process of scheduling the plug-in using the security level information of the plug-in will not be repeated.

In a possible implementation, the feature information includes the security level information of the plug-in, associated plug-in information and priority information, and according to the feature information of the plug-in, the plug-in is set in a process suitable for the feature information of the plug-in, including: in the security level information Indicates that when the plug-in is a secure plug-in, obtain the priority of each plug-in and the priority of each running process, and set the plug-in with high priority in the corresponding process with high priority, which satisfies the relationship between the plug-in to be scheduled and the Related plugins related to plugin information run in the same process.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information, associated plug-in information and priority information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled using its associated plug-in information and priority information. The process of scheduling a plug-in by using the plug-in associated plug-in information and priority information of the plug-in will not be repeated. When the plug-in 804 is identified as a risk plug-in or an abnormal plug-in, the security level information of the plug-in is used for scheduling, and the process of scheduling the plug-in using the security level information of the plug-in will not be repeated.

In a possible implementation, the feature information includes the security level information, runtime information and priority information of the plug-in, and according to the feature information of the plug-in, the plug-in is set in a process suitable for the feature information of the plug-in, including: in the security level information Indicates that when the plug-in is a security plug-in, obtain the priority of each plug-in and the priority of each running process, and set the plug-in with high priority in the corresponding process with high priority, and the process with high priority satisfies The running duration of each plugin in the process is similar to the running duration of the plugin to be scheduled.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information, running duration information and priority information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled by using the running time information and priority information of the plug-in. The process of scheduling the plug-in by using the running time information and the priority information of the plug-in will not be repeated. When the plug-in 804 is identified as a risk plug-in or an abnormal plug-in, the security level information of the plug-in is used for scheduling, and the process of scheduling the plug-in using the security level information of the plug-in will not be repeated.

In a possible implementation manner, the feature information includes the load information of the plug-in, the associated plug-in information and the running time length information, and according to the feature information of the plug-in, the plug-in is set in a process that is suitable for the feature information of the plug-in, including: setting the plug-in to run. The relevant plug-in related to the relevant plug-in information is located in the process, and the product of the predicted load of the process and the predicted running time does not exceed the threshold set by the system.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information of the plug-in 804 , the associated plug-in information and the running duration information. Obtain the related plug-ins that have the same resources read by plug-in 804 in the process. When the resources read by plug-in 8011 or plug-in 8021 and plug-in 804 are the same, it indicates that plug-in 804 and plug-in 8011 or plug-in 8021 are related plug-ins. The process 801 and process 802 schedule plugins. Use the load information and runtime information of the plug-in to schedule plug-ins. The process of scheduling the plug-in by using the load information and the running time information of the plug-in will not be repeated.

In a possible implementation, the feature information includes load information, priority information and running duration information of the plug-in, and according to the feature information of the plug-in, the plug-in is set in a process suitable for the feature information of the plug-in, including: obtaining the priority of each plug-in. and the priority of each running process, set the plug-in with high priority in the corresponding process with high priority, and the product of the predicted load of the process with high priority and the predicted running time does not exceed the system setting the threshold value.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information, priority information and running duration information of the plug-in 804 . When the priority of the plug-in 804 is higher, the plug-in is scheduled to the process 801 or the process 802 with a higher priority set by the system.

When the priority of the process 801 is the same as that of the process 802, the plug-in is scheduled by using the load information and running time information of the plug-in. The process of scheduling the plug-in by using the load information and the running time information of the plug-in will not be repeated.

In a possible implementation, the feature information includes load information of the plug-in, associated plug-in information and priority information, and the plug-in is set in a process suitable for the feature information of the plug-in according to the feature information of the plug-in, including: obtaining the priority of each plug-in. Rank and the priority of each running process, set the plug-in with high priority in the corresponding process with high priority, this process satisfies that the plug-in to be scheduled and the related plug-in related to the related plug-in information are running in the same process, the process It is also satisfied that the predicted load of the process does not exceed the load threshold set by the terminal device.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information, associated plug-in information and priority information of the plug-in 804 . Obtain the relevant plug-ins in the process with the same resources read by the plug-in 804, and obtain the priority of each running process.

When the priority of the plug-in 804 is high, and the priorities of the process 801, the process 802 and the process 803 set by the terminal device are all high, the plug-in is scheduled by using the related information of the plug-in. When the plug-in 804 and the plug-in 8013 in the process 801 and the plug-in 8023 in the process 802 are mutually related plug-ins, the plug-in can be scheduled into the process 801 or the process 802 .

Using the load information of the plug-in, the plug-in 804 is set in the process 801 or the process 802 , the predicted load of the process 801 or the predicted load of the process 802 is calculated. Determine the relationship between the predicted load of the process 801 or the predicted load of the process 802 and the load threshold of the process. When the predicted load of the process 801 does not exceed the load threshold, and the predicted load of the process 802 exceeds the load threshold, the plug-in 804 is scheduled into the process 801 .

When none of the process 801, the process 802 and the process 803 can simultaneously satisfy the load information, associated plug-in information and priority information of the plug-in, the abnormal situation scheduled by the plug-in 804 is sent to the terminal device.

In a possible implementation, the feature information includes associated plugin information, runtime information and priority information of the plugin, and the plugin is set in a process that is compatible with the feature information of the plugin according to the feature information of the plugin, including: obtaining the information of each plugin. The priority and the priority of each running process, the plug-in with high priority is set in the corresponding process with high priority, the process satisfies that the plug-in to be scheduled and the related plug-in related to the associated plug-in information are running in the same process, and The process also satisfies that the running duration of each plug-in in the process is similar to the running duration of the plug-in to be scheduled.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the associated plug-in information, runtime information and priority information of the plug-in 804 . Obtain the related plug-ins that have the same resources read by the plug-in 804 in the process. When the resources read by the plug-in 8011, the plug-in 8021 or the plug-in 8031 and the plug-in 804 are the same, it indicates that the plug-in 804 and the plug-in 8011, the plug-in 8021, or the plug-in 8031 are related plug-ins. Determine that the plug-in can be scheduled in process 801, process 802, or process 803 that satisfies the associated plug-in information

Schedule plugins using the plugin's priority information. When the priority of the plug-in 804 is relatively high, and the priorities of the process 801 and the process 803 set by the terminal device are both relatively high, the plug-in is further scheduled by using the running time information of the plug-in.

In the process 801 and the process 803 that satisfy the associated plug-in information and priority information: the plug-in 8011 , the plug-in 8012 , the plug-in 8013 , the plug-in 8014 , the plug-in 8031 , and the plug-in 8032 each plug-in running time is obtained. The relationship between the running time of the plug-in 804 and the running time of each plug-in is determined. When the difference between the running duration of the plug-in to be scheduled and the running duration of one of the above plug-ins 8011, 8012, 8013, 8014, 8031 and 8032 does not exceed the preset threshold, the to-be-scheduled plug-in will be scheduled. into the process in which the plugin resides. When the difference between the running time of the plug-in 804 and the running time of the plug-in 8031 does not exceed the preset threshold, the plug-in 804 is scheduled to the process 803 where the plug-in 8031 is located.

In a possible implementation, the feature information includes the security level information of the plug-in, load information, associated plug-in information and runtime length information, and the plug-in is set in a process that is compatible with the plug-in's feature information according to the plug-in's feature information, including: When the security level information indicates that the plug-in is a secure plug-in, the plug-in is set in the process where the relevant plug-in related to the associated plug-in information is running, and the product of the predicted load of the process and the predicted running time does not exceed the threshold set by the system. .

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information, load information, associated plug-in information and running duration information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled by using the security level information, associated plug-in information and running time information of the plug-in. The process of scheduling the plug-in by using the associated plug-in information, the associated plug-in information and the running time information of the plug-in will not be repeated.

In a possible implementation manner, the feature information includes the security level information, load information, priority information and runtime length information of the plug-in, and the plug-in is set in a process that is compatible with the feature information of the plug-in according to the feature information of the plug-in, including: The security level information indicates that when the plug-in is a security plug-in, the priority of each plug-in and the priority of each running process are obtained, and the plug-in with high priority is set in the corresponding process with high priority, and the priority is high. The product of the predicted load of the process and the predicted running time does not exceed the threshold set by the system.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information, load information, priority information and running duration information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled by using the load information, priority information and running time information of the plug-in. The process of scheduling the plug-in by using the load information, priority information and running time information of the plug-in will not be described again.

In a possible implementation, the feature information includes the security level information of the plug-in, load information, associated plug-in information and priority information, and the plug-in is set in a process suitable for the feature information of the plug-in according to the feature information of the plug-in, including: The security level information indicates that when the plug-in is a security plug-in, obtain the priority of each plug-in and the priority of each running process, and set the plug-in with high priority in the corresponding process with high priority. The plug-in and related plug-ins related to the associated plug-in information run in the same process, and the process also satisfies that the predicted load of the process does not exceed the load threshold set by the terminal device.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information, load information, associated plug-in information and priority information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled by using the load information, associated plug-in information and priority information of the plug-in. The process of scheduling the plug-in by using the load information, associated plug-in information and priority information of the plug-in will not be described again.

In a possible implementation, the feature information includes the security level information of the plug-in, the associated plug-in information, the running duration information and the priority information, and the plug-in is set in a process suitable for the feature information of the plug-in according to the feature information of the plug-in, including: When the security level information indicates that the plug-in is a security plug-in, obtain the priority of each plug-in and the priority of each running process, and set the plug-in with high priority in the corresponding process with high priority. The scheduling plugin and related plugins related to the associated plugin information run in the same process, and the process also satisfies that the running duration of each plugin in the process is similar to the running duration of the plugin to be scheduled.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information, associated plug-in information, runtime information and priority information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is used to associate plug-in information, runtime information and priority information to schedule the plug-in. The process of scheduling the plug-in by using the associated plug-in information, running time information and priority information of the plug-in will not be repeated.

In a possible implementation manner, the feature information includes the load information of the plug-in, associated plug-in information, running time information and priority information, and the plug-in is set in a process suitable for the plug-in feature information according to the plug-in feature information, including: obtaining: The priority of each plug-in and the priority of each running process, the plug-in with high priority is set in the corresponding process with high priority, and the process satisfies that the plug-in to be scheduled and the related plug-in related to the associated plug-in information are running in the same process. , and the process also satisfies that the running duration of each plugin in the process is similar to the running duration of the plugin to be scheduled.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the load information of the plug-in 804 , the associated plug-in information, the running time information and the priority information. Obtain the relevant plug-ins in the process with the same resources read by the plug-in 804, and obtain the priority of each running process.

Schedule plugins using the plugin's load information and the plugin's runtime. In the process 801 and the process 802 satisfying the associated plug-in information and priority information, the running time of each process of the plug-in 8011 , the plug-in 8012 , the plug-in 8013 , the plug-in 8014 , the plug-in 8021 , the plug-in 8022 and the plug-in 8023 is obtained. The relationship between the running time of the plug-in 804 and the running time of each plug-in is determined. When the difference between the running duration of the plug-in to be scheduled and the running duration of one of the above plug-ins 8011, 8012, 8013, 8014, 8021, 8022 and 8023 does not exceed the preset threshold, the Scheduled plugins are scheduled into the process where the plugin resides. When the difference between the running time of the plug-in 804 and the running time of the plug-in 8013 does not exceed the preset threshold, the plug-in 804 is scheduled to the process 801 where the plug-in 8013 is located.

In a possible implementation, the feature information includes the security level information of the plug-in, load information, associated plug-in information, runtime information and priority information, and the plug-in is set in a process that is compatible with the plug-in's feature information according to the plug-in's feature information. , including: when the security level information indicates that the plug-in is a security plug-in, obtain the priority of each plug-in and the priority of each running process, and set the plug-in with high priority in the corresponding process with high priority. The process satisfies that the plug-in to be scheduled and the related plug-in related to the associated plug-in information run in the same process, and the process also satisfies that the running time of each plug-in in the process is similar to that of the plug-in to be scheduled.

Exemplarily, in the scheduling scenario shown in FIG. 8 , when the user performs scheduling according to the security level information, load information, associated plug-in information, runtime information and priority information of the plug-in 804 . The plug-in type of the plug-in is determined according to the security level information of the plug-in 804 . When the plug-in 804 is a normal plug-in, the plug-in is scheduled using the load information, associated plug-in information, running time information and priority information of the plug-in. The process of scheduling the plug-in by using the load information, associated plug-in information, running time information and priority information of the plug-in will not be repeated.

It can be understood that, in the information scheduling plug-in scenario provided by the embodiment of the present application using the combination of the feature information of the above plug-ins, when the process 801, the process 802, and the process 803 cannot satisfy the feature information of the above plug-ins at the same time. If the information is combined with each other, the abnormal situation scheduled by the plug-in 804 is sent to the terminal device.

It can be understood that, in this embodiment of the present application, there is no limitation on the order in which plug-in scheduling is performed according to security level information, load information, associated plug-in information, running duration information, and priority information. According to different feature information of the plug-in, more reasonable scheduling can be performed on the plug-in.

On the basis of the embodiment corresponding to FIG. 4 , in a possible implementation manner, S403 includes: using a machine learning model to determine the feature information of the plug-in; wherein, the machine learning model is obtained by training using process-related sample information. In this embodiment of the present application, the terminal device may be used to calculate the feature information of the plug-in, or the cloud device may be used to calculate the feature information of the plug-in.

In a possible implementation manner, in the terminal device, the feature information of the plug-in is determined by using a machine learning model.

Exemplarily, using the machine learning model to determine the feature information of the plug-in, the process includes but is not limited to the following steps:

S4031. Obtain process-related sample information.

The sample information related to the process includes one or more of the following: process name, plug-in list, memory ratio, CPU usage of the central processing unit, or abnormal information. Exemplarily, the process name can be the identification symbol set by the terminal device to identify different processes; the plug-in list can be the name list of the plug-ins currently running by the process; the memory ratio can be the amount of the memory of the terminal device occupied by the process. Percentage; the CPU usage rate of the central processing unit can be the percentage of the CPU of the process in the terminal device; the exception information can indicate whether the process information is collected when the process is abnormal, and when the process information is collected when the process is abnormal, The value of the exception information is true. When the process information is not collected when the process is abnormal, the value of the exception information is false.

The acquired process-related sample information may be obtained by acquiring process-related information from one terminal device multiple times; or may be obtained by acquiring process-related information from multiple terminal devices. It can be understood that the manner of acquiring process-related sample information may vary according to actual scenarios, and the manner of acquiring process-related sample information is not limited in this embodiment of the present application.

S4032. Input the process-related sample information into a machine learning model for training.

Exemplarily, the process-related sample information is input into the machine learning model, and the load information of the plug-in is output; the loss function is used to compare the gap between the predicted load information of the plug-in output by the model and the actual load information of the plug-in; If the difference between the predicted load information and the plug-in's actual load information does not satisfy the loss function, adjust the parameters of the model and continue training; until the difference between the output plug-in's predicted load information and the plug-in's actual load information satisfies the loss function, the model training ends , and get a machine learning model that can determine the load information of the plug-in.

S4033: Input the process-related information into the machine learning model, and output the feature information of the plug-in.

Terminal devices use process snapshots to obtain process-related information. The process-related information includes: one or more of the following: process name, plug-in list, memory ratio, CPU usage of the central processing unit, or abnormal information.

By inputting process-related information into the trained machine learning model, the feature information of the plug-in can be output. Taking the feature information including load information as an example, the load information of the plug-in can be the weight corresponding to the plug-in in the machine learning model.

Exemplarily, the load information Value _load of the plug-in can be expressed as:

Value _load = w ₁ x ₁ +w ₂ x ₂ +…+w _n x _n

Among them, w _n is the weight corresponding to the plug-in in the machine learning model, and w _n represents the load information of the plug-in x _n when it is running.

It can be understood that, the embodiment of the present application does not limit the manner of determining the feature information of the plug-in.

In a possible implementation manner, in addition to the above-mentioned use of the machine learning model to determine the feature information, a statistical method can also be used to obtain the feature information of the plug-in.

Exemplarily, the security level information of the plug-in is obtained by using a statistical method. The terminal device acquires the process-related information of the process, and uses the process-related information to calculate the security level information of the plug-in. The security level information may include: a process crash probability caused by a plug-in, a memory leak probability caused by a plug-in, or a probability calculated according to the process crash probability and the memory leak probability.

The process crash probability P _xn caused by the plug-in can be:

P _xn =PNum _xn /PNum _tatal

Among them, PNum _xn is the total number of times the plugin appears in the crash process, and PNum _tatal is the total number of process crashes.

The memory leak probability L _xn caused by this plugin can be:

L _xn =LNum _xn /LNum _tatal

Among them, LNum _xn is the total number of plug-ins in the memory leak process, and LNum _tatal is the ratio of the total number of process memory leaks;

The probability calculated according to the process crash probability and the memory leak probability may be the weight of the process crash probability and the memory leak probability. It can be understood that, in the embodiments of the present application, the value of the weight in the weighting and the manner of acquiring the plug-in feature information are not limited. The powerful learning and computing capabilities of the machine learning model can fully train the process-related samples, and the machine learning model can be used to obtain more accurate feature information.

Exemplarily, FIG. 9 is a schematic flowchart of acquiring feature information according to an embodiment of the present application. The second device (for example, a cloud device) can use other types of methods such as machine learning models or statistical methods to calculate the feature information of the plug-in. As shown in Figure 9, the method may include but is not limited to the following steps:

S901. The second device acquires process-related information in the first device (for example, a terminal device).

In this embodiment of the present application, the timing for the second device to acquire the process-related information in the first device may be: periodically acquiring process-related information of multiple devices from multiple devices; or, process-related information sent when the process is abnormal.

S902. The second device calculates the feature information file according to the process-related information.

In this embodiment of the present application, the feature information file includes feature information of a plurality of plug-ins, and the feature information of the plug-ins includes information that the plug-ins affect the running of the process. The method for calculating the feature information file may be to use machine learning, statistical methods or other types of computing methods to calculate the feature information of the plug-in, and store the feature information of the plug-in in the feature information file. The method for calculating feature information by using a machine learning model or a statistical model will not be described again.

S903. The second device sends the feature information file to the first device.

S904. The first device acquires the feature information of the plug-in from the feature information file according to the identifier of the plug-in.

The plug-in's identifier can represent the characteristic information of the plug-in.

Through the above S901-S904, the feature information of the plug-in can be calculated in the second device, and the feature information file containing the feature information of the plug-in can be sent to the first device. The first device may perform scheduling of the plug-in using the characteristic information of the plug-in in the characteristic information file of the plug-in. In this embodiment of the present application, the scheduling method of the plug-in is not described again.

In this embodiment of the present application, the plug-in feature information may also be calculated from the first device. Due to the limited computing capability of the first device and the reason that the first device still needs to perform tasks such as plug-in scheduling, in order not to affect other services of the first device, The business of calculating the feature information of the plug-in can be performed by a second device with stronger computing power and a special purpose. Since the second device usually has powerful computing capabilities, the feature information of the plug-in is calculated by the second device, which can reduce the amount of computation of the first device and save the computing resources of the first device.

Corresponding to the embodiment of FIG. 9, exemplarily, FIG. 10 provides a schematic frame diagram of a plug-in management system. As shown in FIG. 10 , the plug-in management system consists of an external request generation module 1001 , a request processing module 1002 , a plug-in scheduling module 1003 , an operation management module 1004 , a return call result 1005 , a cloud platform 1006 and an intelligent management module 1007 .

It should be noted that the steps performed by the external request generation module 1001 can be implemented in the application layer in FIG. 2 , and the request processing module 1002 , the plug-in scheduling module 1003 , the operation management module 1004 , and the return call result 1005 can be implemented in the application framework layer. , the steps performed by the cloud platform 1006 and the intelligent management module 1007 . In a possible implementation manner, the cloud platform 1006 may not be in the terminal device shown in FIG. 2 .

The external request generating module 1001 is configured to generate request information for requesting to run the micro-application based on user triggering.

The request processing module 1002 is configured to determine a specific plug-in that needs to be scheduled for the request information.

The plug-in scheduling module 1003 is used to manage the plug-in scheduling. For example, the plug-in scheduling module 1003 may include: process allocation 1031 and plug-in loading 1032. The process allocation 1031 is used for allocating plug-ins to processes, and the plug-in loading 1032 loads and runs the plug-in.

The operation management module 1004 is used to manage the process. For example, the operation management module 1004 may include: operation monitoring 1041 and data reporting 1042, the operation monitoring 1041 can obtain the operation information of each process, and the data reporting 1042 can report the operation information to the cloud platform 1006.

The cloud platform 1006 can be used for the feature analysis of the plug-in in the process. For example, the cloud platform can use the feature analysis 1061 to perform the feature analysis of the plug-in, so as to obtain the feature file 1062.

The cloud platform 1006 can send the feature file 1062 to the intelligent management module 1007 and store it locally. The terminal device can use the feature file to perform intelligent management 1007 of plug-ins, for example, identification of problem plug-ins 1072 and load balancing plug-in process allocation 1073 .

The intelligent management module 1007 can store the feature file 1062 locally, and can use the feature file 1062 to perform feature file management 1071 , problem identification 1072 and load balancing 1073 subsequently.

Based on the schematic diagram of the framework corresponding to FIG. 10 , as shown in FIG. 11 , it shows a schematic diagram that the operation monitoring 1041 can obtain the operation information of each process, and the data reporting 1042 can report the operation information to the cloud platform 1006 .

As shown in FIG. 11 , the operation monitoring 1041 may include a process snapshot 1105 and an operation monitoring 1107. The terminal device uses the process snapshot 1105 to collect the process snapshot information (or process-related information) of the framework process 1106 when it is running, and the operation monitoring 1107 collects the process The snapshot information is encapsulated based on the data encapsulation 1108, and the process snapshot information is reported to the cloud platform based on the data reporting 1109.

Among them, the process snapshot can be expressed as:

ProcessSnopshot={PName, PluginList, %MEN, %CPU, Exception}

Among them, PName is the name of the process, PluginList is the list of plug-in names currently running in the process, %MEN is the percentage of memory used by the process, %CPU is the percentage of CPU occupied by the process, and the Exception is the exception information. The value is true or false. When the process snapshot is collected when an exception occurs, the value is true.

The reporting time of the process snapshot, Time _report , can be:

Time _report = k×Time _collect (k∈N and k>1)

Among them, Time _collect is the collection time of the process snapshot.

Based on the schematic diagram of the framework corresponding to FIG. 10 , exemplarily, FIG. 12 shows a schematic diagram of the cloud platform obtaining a feature file by using process snapshot information.

As shown in FIG. 12 , the cloud platform obtains the process name, plug-in list, memory ratio and CPU usage obtained by the process snapshot 1201 , and the cloud platform uses the feature analysis 1202 to analyze the features of the plug-ins. For example, signature analysis 1202 may include load signature analysis 1221 and anomaly signature analysis 1222. The load characteristic analysis 1221 can analyze the process snapshot information to obtain the load information of the plug-in. For example, Value _load can satisfy the following formula.

Value _load =f(%MEN,%CPU)

Or it can be understood that the value _load of the load information of the plug-in is related to the memory ratio and CPU usage of the terminal device.

The abnormal feature analysis 1222 can analyze the process snapshot information to obtain the security level information of the plug-in.

For example, the plug-in's security level information Strategy can be expressed as:

Among them, no meansure means normal allocation without additional measures, safe mode means safe mode, forbidden mode means disabled mode. The calculation process of the security level information is not repeated here.

The cloud platform can analyze the feature information of the plug-in to obtain a feature file 1203, and the terminal device can download the feature file 1203 from the cloud platform. Furthermore, the terminal device can use the feature file 1203 to perform plug-in scheduling.

Exemplarily, as shown in FIG. 13 , after receiving the external request 1301 , the terminal device performs plug-in identification 1302 according to the characteristic information file of the plug-in and adopts different problem handling strategies 1303 .

For example, for a security plugin whose security level information is less than a%, the plugin is set to run in a process suitable for the feature information of the plugin; for a risk plugin whose security level information is between a% and b%, Assign the plug-in to an independent process set by the system to run; for the abnormal plug-in whose security level information is greater than b%, disable the plug-in, and send the plug-in error report to the terminal.

Exemplarily, as shown in FIG. 14 , when the terminal device identifies the plug-in as a secure plug-in, load balancing 1402 can be implemented according to load information of the plug-in, for example, plug-in allocation 1403 based on plug-in allocation 1403 to allocate plug-ins in the adaptive process. Further, the terminal device can execute the update process load 1404 to obtain the latest process information and the like.

The methods of the embodiments of the present application have been described above with reference to FIG. 4 to FIG. 14 , and the following describes the plug-in management apparatuses provided by the embodiments of the present application for executing the above methods. Those skilled in the art can understand that the methods and apparatuses can be combined and referenced with each other, and a plug-in management apparatus provided by the embodiments of the present application can perform the steps performed by the terminal device in the above-mentioned plug-in management method. Another plug-in management apparatus may perform the steps performed by the cloud device in the plug-in management method in the above embodiment.

As shown in FIG. 15 , FIG. 15 shows a schematic structural diagram of a plug-in management apparatus provided by an embodiment of the present application. The plug-in management apparatus may be a terminal device or a cloud device in the embodiment of the present application, or may be applied to a terminal device or The chip of the cloud device. The plug-in management apparatus includes: a processing unit 151 and a communication unit 152 . The communication unit 152 is used for supporting the plug-in management apparatus to perform the steps of sending or receiving information, and the processing unit 151 is used for supporting the plug-in management apparatus to perform the steps of information processing.

In a possible embodiment, the plug-in management apparatus may further include: a storage unit 153 . The processing unit 151, the communication unit 152, and the storage unit 153 are connected through a communication bus.

The storage unit 153 may include one or more memories, and the memories may be devices in one or more devices or circuits for storing programs or data.

The storage unit 153 may exist independently, and is connected to the processing unit 151 of the plug-in management apparatus through a communication bus. The storage unit 153 may also be integrated with the processing unit.

The plug-in management apparatus may be used in a communication device, circuit, hardware component or chip.

Taking the plug-in management apparatus as an example of a chip or a chip system of a terminal device or a cloud device in the embodiment of the present application, the communication unit 152 may be an input or output interface, a pin, a circuit, or the like. Exemplarily, the storage unit 153 may store computer execution instructions of the method on the side of the terminal device or the cloud device, so that the processing unit 151 executes the method on the side of the terminal device or the cloud device in the foregoing embodiments. The storage unit 153 may be a register, a cache or a RAM, etc., and the storage unit 153 may be integrated with the processing unit 151 . The storage unit 153 may be a ROM or other types of static storage devices that may store static information and instructions, and the storage unit 153 may be independent of the processing unit 151 .

An embodiment of the present application provides a plug-in management apparatus, and the plug-in management apparatus includes one or more modules for implementing the methods in the steps included in the foregoing FIG. 4 to FIG. 14 , and the one or more modules may be combined with the foregoing The steps of the method in the steps contained in FIGS. 4-14 correspond.

FIG. 16 is a schematic diagram of a hardware structure of a plug-in management apparatus provided by an embodiment of the present application. For the hardware structure of the terminal device or the cloud device in the embodiments of the present application, reference may be made to the schematic diagram of the hardware structure of the plug-in management apparatus shown in FIG. 16 . The plug-in management apparatus includes a processor 161, a communication line 164 and at least one communication interface (the communication interface 163 is exemplified in FIG. 16 for illustration).

The processor 161 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the programs of the present application. integrated circuit.

Communication line 164 may include a path to communicate information between the aforementioned components.

The communication interface 163, using any transceiver-like device, is used to communicate with other devices or communication networks, such as Ethernet, wireless local area networks (WLAN), RAN, and the like.

Possibly, the plug-in management apparatus may further include a memory 162 .

The memory 162 may be read-only memory (ROM) or other type of static storage device that can store static information and instructions, random access memory (RAM) or other type of static storage device that can store information and instructions It can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, CD-ROM storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being executed by a computer Access any other medium without limitation. The memory may exist independently and be connected to the processor through communication line 164 . The memory can also be integrated with the processor.

The memory 162 is used for storing computer-executed instructions for executing the solutions of the present application, and the execution is controlled by the processor 161 . The processor 161 is configured to execute the computer-executed instructions stored in the memory 162, thereby implementing the plug-in management methods provided by the following embodiments of the present application.

Possibly, the computer-executed instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

In a specific implementation, as an embodiment, the processor 161 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 16 .

In a specific implementation, as an embodiment, the plug-in management apparatus may include multiple processors, such as the processor 161 and the processor 165 in FIG. 16 . Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

FIG. 17 is a schematic structural diagram of a chip 170 provided by an embodiment of the present invention. The chip 170 includes one or more (including two) processors 1710 and a communication interface 1730 .

In a possible embodiment, the chip 170 shown in FIG. 17 further includes a memory 1740, which may include a read-only memory and a random access memory, and provides the processor 1710 with operation instructions and data. A portion of memory 1740 may also include non-volatile random access memory (NVRAM).

In some embodiments, memory 1740 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set of them:

In this embodiment of the present invention, the corresponding operation is performed by calling the operation instruction stored in the memory 1740 (the operation instruction may be stored in the operating system).

A possible implementation manner is: the structure of the chips used by the terminal device or the cloud device is similar, and different devices may use different chips to realize their respective functions.

The processor 1710 controls the operation of the terminal device or the cloud device, and the processor 1710 may also be referred to as a central processing unit (central processing unit, CPU). Memory 1740 may include read-only memory and random access memory, and provides instructions and data to processor 1710 . A portion of memory 1740 may also include non-volatile random access memory (NVRAM). For example, the memory 1740, the communication interface 1730, and the memory 1740 are coupled together through the bus system 1720, wherein the bus system 1720 may include a power bus, a control bus, a status signal bus, and the like in addition to a data bus. However, for clarity of illustration, the various buses are labeled as bus system 1720 in FIG. 17 .

The above communication unit may be an interface circuit or a communication interface of the device for receiving signals from other devices. For example, when the device is implemented in the form of a chip, the communication unit is an interface circuit or a communication interface used by the chip to receive or transmit signals from other chips or devices.

The methods disclosed in the above embodiments of the present invention may be applied to the processor 1710 or implemented by the processor 1710 . The processor 1710 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method may be completed by an integrated logic circuit of hardware in the processor 1710 or an instruction in the form of software. The above-mentioned processor 1710 may be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (field-programmable gate array, FPGA) or Other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. Various methods, steps, and logical block diagrams disclosed in the embodiments of the present invention can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present invention may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory 1740, and the processor 1710 reads the information in the memory 1740, and completes the steps of the above method in combination with its hardware.

In a possible implementation manner, the communication interface 1730 is used to perform the steps of receiving and sending the terminal device or the cloud device in the embodiments shown in FIGS. 4-14 . The processor 1710 is configured to execute the processing steps of the terminal device or the cloud device in the embodiments shown in FIGS. 4-14 .

In the above-described embodiments, the instructions stored by the memory for execution by the processor may be implemented in the form of a computer program product. The computer program product can be pre-written in the memory, or downloaded and installed in the memory in the form of software.

A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. Computer instructions may be stored on or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center over a wire (e.g. coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to transmit to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be stored by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated. Useful media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, digital versatile disc (DVD)), or semiconductor media (eg, solid state disk (SSD)), etc. .

Embodiments of the present application also provide a computer-readable storage medium. The methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media can include both computer storage media and communication media and also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium that can be accessed by a computer.

As one possible design, the computer readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium intended to carry or in an instruction or data structure The required program code is stored in the form and can be accessed by the computer. Also, any connection is properly termed a computer-readable medium. For example, if you use coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies (such as infrared, radio, and microwave) to transmit software from a website, server, or other remote source, coaxial cable, fiber optic cable , twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, DVD, floppy disk, and blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

The embodiments of the present application also provide a computer program product. The methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware or any combination thereof. If implemented in software, it 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 the above-mentioned computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the above-mentioned method embodiments are generated. The aforementioned computer may be a general purpose computer, a special purpose computer, a computer network, a base station, a terminal, or other programmable devices.

It can be understood that, the various numbers and numbers involved in the embodiments of the present application are only for the convenience of description, and are not used to limit the scope of the embodiments of the present application. In the embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not imply the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not constitute the implementation process of the embodiments of the present application. any restrictions.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features thereof can be equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the embodiments of the present application. range.

Claims

A plug-in management method, characterized in that, applied to a first device, comprising:

Receive request information for requesting to run the micro-application;

Determine the plug-in corresponding to the request information; the plug-in is used to implement part or all of the functions of the micro-application;

Acquiring feature information of the plug-in; the feature information includes the information that the plug-in affects the running of the process;

The plug-in is scheduled according to the feature information.
The method according to claim 1, wherein the feature information includes one or more of the following: load information, security level information, associated plug-in information, runtime information or plug-in priority information.
The method according to claim 1 or 2, wherein the scheduling the plug-in according to the characteristic information comprises:

setting the plug-in in a process adapted to the characteristic information of the plug-in;

Alternatively, the plug-in is disabled according to the feature information.
The method according to any one of claims 1-3, wherein the characteristic information includes load information, and the scheduling the plug-in according to the characteristic information comprises:

Calculate the predicted load of the first process that can be used to run the plug-in according to the load information; the predicted load of the first process is the total load of the first process when the plug-in is set in the first process ; the number of the first process is multiple;

The plug-in is set in a first target process; the first target process is a process in the first process whose predicted load does not exceed a first load threshold.
The method according to any one of claims 1-3, wherein the feature information includes security level information, and the scheduling the plug-in according to the feature information includes:

When the security level information indicates that the plug-in is a security plug-in, assigning the plug-in to a process that can be used to run the plug-in;

Or, when the security level information indicates that the plug-in is a risk plug-in, the plug-in is allocated in an independent process; the independent process is a preset process for running the risk plug-in;

Alternatively, when the security level information indicates that the plug-in is an abnormal plug-in, the plug-in is disabled.
The method according to claim 5, wherein the security level information comprises a process crash probability caused by the plug-in, a memory leak probability caused by the plug-in, or according to the process crash probability and the memory leak probability the calculated probability;

When the security level information is less than the first value, it indicates that the plug-in is a security plug-in;

When the security level information is greater than or equal to the first value and less than or equal to the second value, it indicates that the plug-in is a risk plug-in;

When the security level information is greater than the second value, it indicates that the plug-in is an abnormal plug-in.
The method according to claim 5 or 6, wherein the characteristic information further includes load information, and the scheduling the plug-in according to the characteristic information comprises:

In the case that the security level information indicates that the plug-in is the security plug-in, the predicted load of the second process that can be used to run the security plug-in is calculated according to the load information of the security plug-in; the prediction of the second process The load is the total load of the second process when the security plug-in is set in the second process; the number of the second process is multiple;

The security plug-in is set in a second target process, where the second target process is a process in the second process whose predicted load does not exceed a second load threshold.
The method according to any one of claims 1-3, wherein the characteristic information includes associated plug-in information, and the scheduling the plug-in according to the characteristic information comprises:

The plug-in is set in a third process, where the third process is a process for running a related plug-in related to the associated plug-in information.
The method according to claim 8, wherein the related plug-in comprises: the same plug-in as the resource read by the plug-in.
The method according to any one of claims 1-9, wherein the acquiring feature information of the plug-in comprises:

receiving a feature information file from a second device; the feature information file includes feature information of multiple plug-ins calculated by the second device;

According to the identification of the plug-in, the characteristic information of the plug-in is obtained from the characteristic information file.
The method of claim 10, further comprising:

Sending process-related information in the first device to the second device, where the process-related information is used to calculate the feature information file.
The method according to claim 11, wherein the process-related information includes one or more of the following: process name, plug-in list, memory ratio, CPU usage rate of central processing unit, or exception information.
The method according to any one of claims 1-9, wherein the acquiring feature information of the plug-in comprises:

The feature information is determined by using a machine learning model; wherein, the machine learning model is obtained by training using process-related sample information.
The method according to claim 13, wherein the process-related sample information includes one or more of the following: process name, plug-in list, memory ratio, central processing unit (CPU) usage rate, or exception information.
A plug-in management method, characterized in that, applied to a second device, the method comprising:

Get process related information;

Calculate a feature information file according to the process-related information, where the feature information file includes feature information of a plurality of plug-ins, and the feature information of the plug-ins includes the information that the plug-in affects the running of the process;

Send the feature information file to the first device.
The method according to claim 15, wherein the feature information includes one or more of the following: load information, security level information, associated plug-in information, runtime information or plug-in priority information.
The method according to claim 16, wherein the security level information comprises a process crash probability caused by the plug-in, a memory leak probability caused by the plug-in, or according to the process crash probability and the memory leak probability Calculated probability.
The method according to any one of claims 15-17, wherein the process-related information includes one or more of the following: a process name, a list of plug-ins, a memory ratio, a CPU usage rate of a central processing unit, or Exception information.
The method according to any one of claims 15-18, wherein the calculating the feature information file according to the process-related information comprises:

Train a machine learning model according to the process-related information;

The feature information file is output using the machine learning model.
The method according to any one of claims 15-19, wherein the acquiring process-related information comprises:

Periodically obtain process-related information of the multiple devices from multiple devices;

Or, acquire process-related information sent by the multiple devices when the process is abnormal.
A plug-in management device, comprising: a processor and a communication interface;

The communication interface is used to perform the operation of sending and receiving in the plug-in management method according to any one of claims 1-14, or performing the sending and receiving operation in the plug-in management method according to any one of claims 15-20. operation; the processor executes the instruction to perform the processing or control operation in the plug-in management method according to any one of claims 1-14, or executes the operation according to any one of claims 15-20. The operation that is processed or controlled in the plugin management method.
A chip, characterized in that the chip includes at least one processor and a communication interface, the communication interface is coupled to the at least one processor, and the at least one processor is used to run a computer program or instructions to implement the claim The plug-in management method according to any one of claims 1-14, or to implement the plug-in management method according to any one of claims 15-20; the communication interface is used to communicate with other modules other than the chip to communicate.
A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, and when the instructions are executed by one or more processors, the implementation of any one of claims 1-14 is implemented. The plug-in management method described above, or implement the plug-in management method according to any one of claims 15-20.
A computer program product, wherein instructions are stored in the computer program product, and when the instructions are executed by one or more processors, the plug-in management according to any one of claims 1-14 is implemented method, or implement the plug-in management method according to any one of claims 15-20.