CN116088970B

CN116088970B - Method for controlling application call and related device

Info

Publication number: CN116088970B
Application number: CN202210590857.8A
Authority: CN
Inventors: 鲍志学; 孙文涌
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-05-27
Filing date: 2022-05-27
Publication date: 2024-04-09
Anticipated expiration: 2042-05-27
Also published as: CN116088970A

Abstract

The embodiment of the application provides a method for controlling application call and a related device, and relates to the technical field of terminals. The method comprises the following steps: judging whether the first application is a target type application based on a package manager service PMS of the terminal equipment, wherein the target type application comprises a system application and an application with a preset identifier in the terminal equipment, and the system application is an application which does not support unloading in the terminal equipment; when the first application is a target type application, the first application is allowed to call the second application. Therefore, the terminal equipment automatically determines the decision of allowing the system application and the application with the preset identifier to call the associated application based on the PMS, and the phenomenon that the associated application cannot be normally called due to incomplete coverage of a trust list or untimely updating and the like in the prior art can be improved, so that the abnormal running of the application program of the terminal equipment is caused.

Description

Method for controlling application call and related device

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a method and an apparatus for controlling application invocation.

Background

With the development of terminal technology, more Applications (APP) can be supported in terminal devices. Some applications in the terminal device may pull up the operation of other associated applications when in use, and pulling up the operation of associated applications in the terminal device may result in an increase in power consumption of the terminal device.

In some implementations, the terminal device may set the trust list, so that when the application pulls up other applications, only the application in the trust list is allowed to pull up other applications, so that the number of times that the associated application is pulled up when the application runs can be reduced, and power consumption is reduced.

However, in the above implementation, there is a phenomenon that causes an application of the terminal device to function abnormally.

Disclosure of Invention

The embodiment of the application calling control method and related device has the advantages that the terminal equipment automatically determines the decision of allowing the system application and the application with the preset identifier to call the associated application based on the packet manager service (package manager service, PMS), and the phenomenon that the associated application cannot be normally called due to incomplete coverage or untimely updating of a trust list and the like in the prior art can be improved, so that the application program of the terminal equipment is abnormally operated can be further caused.

In a first aspect, an embodiment of the present application provides a method for controlling application invocation, where the method includes: detecting that the first application will invoke the second application; judging whether the first application is a target type application based on a package manager service PMS of the terminal equipment, wherein the target type application comprises a system application and an application with a preset identifier in the terminal equipment, and the system application is an application which does not support unloading in the terminal equipment; when the first application is a target type application, the first application is allowed to call the second application.

Therefore, the terminal equipment automatically determines the decision of allowing the system application and the application with the preset identifier to call the associated application based on the PMS, and the phenomenon that the associated application cannot be normally called due to incomplete coverage of a trust list or untimely updating and the like in the prior art can be improved, so that the abnormal running of the application program of the terminal equipment is caused.

In a possible implementation manner, the first application invokes the second application in an activity manner, and the method further includes: when the first application is not the target type application, determining whether to allow the first application to call the second application according to the running state of the first application.

In this way, it is possible to realize

In one possible implementation, the running state of the first application includes whether the first application has a visible activity in the foreground, and determining whether to allow the first application to call the second application according to the running state of the first application includes: when the first application has visible activity in the foreground, allowing the first application to call the second application; or when the first application does not have visible activity in the foreground, prohibiting the first application from calling the second application. In this way, if the user can trigger the first application, the first application can be allowed to call the second application, so that the triggering behavior of the user can be normally executed by the terminal, and if the user cannot trigger the first application, the first application can be forbidden to call the second application, so that the power consumption of the terminal equipment is reduced.

In a possible implementation manner, the running state of the first application includes whether the first application has visible activity in the foreground within a preset duration from a first time, where the first time is a time when the first application will call the second application, and determining whether to allow the first application to call the second application according to the running state of the first application includes: when the first application has visible activity in the foreground within the preset duration, allowing the first application to call the second application; or when the first application does not have visible activity in the foreground within the preset time, prohibiting the first application from calling the second application. In this way, it can be accurately determined whether the first application is likely to have user triggers based on whether the first application has visible activity in the foreground. In this way, a period of time that the second application can be invoked can be reserved for the first application with the visible activity in the foreground, so that the invocation of the second application can be realized even if the first application has a delay in running.

In a possible implementation manner, the first application invokes the second application in a broadcast or service manner, and the method further includes: when the first application is not the target type application, judging whether the second application has a started process or not; when the second application has a started process, allowing the first application to call the second application; or when the second application does not have the started process, prohibiting the first application from calling the second application. In this way, when the second application has a starting process, the calling of the second application does not cause more power consumption, so that the first application can be allowed to call the second application, and the second application can assist the running of the first application. When the second application does not have a starting process, the second application needs to be started in a cold mode, and more power consumption is caused, so that the first application can be forbidden to call the second application, and the power consumption of the terminal equipment is reduced.

In one possible implementation, detecting that a first application will invoke a second application includes: starting a first application, wherein a starting program of the first application is provided with a timing alarm; when the timing time of the timing alarm arrives, an alarm management service in an application framework layer of the trigger terminal equipment detects that the first application will call the second application. Because the timing alarm may be executed later than the starting of the first application, when the timing time of the timing alarm arrives, the method and the device trigger the alarm management service in the application framework layer of the terminal device to detect that the first application will call the second application, and the method and the device can enable control over calling among applications which lag in starting triggering to be achieved.

In one possible implementation manner, before determining whether the first application is the target type application, the method further includes: judging whether the second application is allowed to be called; judging whether the first application is a target type application or not, comprising: when the second application is allowed to be called, whether the first application is a target type application or not is judged. In this way, it may be determined whether to allow the first application to invoke the second application based on the user's settings for the second application, more consistent with the user's intent.

Determining whether the second application is allowed to be invoked, comprising: judging whether the flag bit triple of the second application is a preset value. In this way, it can be conveniently determined whether the second application is allowed to be invoked based on the flag bit.

In a second aspect, an embodiment of the present application provides an apparatus for controlling application invocation, where the apparatus for controlling application invocation may be a terminal device, or may be a chip or a chip system in the terminal device. The means for controlling the invocation of the application may comprise a processing unit. The processing unit is configured to implement the first aspect or any method related to processing in any possible implementation manner of the first aspect. The processing unit may be a processor when the means for controlling the invocation of the application is a terminal device. The means for controlling the invocation of the application may further comprise a storage unit, which may be a memory. The storage unit is configured to store instructions, and the processing unit executes the instructions stored in the storage unit, so that the terminal device implements a method described in the first aspect or any one of possible implementation manners of the first aspect. The processing unit may be a processor when the means for controlling the invocation of the application is a chip or a system of chips within the terminal device. The processing unit executes instructions stored by the storage unit to cause the terminal device to implement a method as described in the first aspect or any one of the possible implementations of the first aspect. The memory unit may be a memory unit (e.g., a register, a cache, etc.) in the chip, or a memory unit (e.g., a read-only memory, a random access memory, etc.) located outside the chip in the terminal device.

The processing unit is for detecting that the first application will invoke the second application; judging whether the first application is a target type application based on a package manager service PMS of the terminal equipment, wherein the target type application comprises a system application and an application with a preset identifier in the terminal equipment, and the system application is an application which does not support unloading in the terminal equipment; when the first application is a target type application, the first application is allowed to call the second application.

In a possible implementation manner, the first application invokes the second application in an activity manner, and the processing unit is further configured to determine, according to an running state of the first application, whether to allow the first application to invoke the second application when the first application is not a target type application.

In a possible implementation manner, the running state of the first application includes whether the first application has a visible activity in the foreground, and the processing unit is specifically configured to allow the first application to call the second application when the first application has the visible activity in the foreground; or when the first application does not have visible activity in the foreground, prohibiting the first application from calling the second application.

In a possible implementation manner, the running state of the first application includes whether the first application has a visible activity in the foreground within a preset duration from a first time, where the first time is a time when the first application will call the second application, and the processing unit is specifically configured to allow the first application to call the second application when the first application has the visible activity in the foreground within the preset duration; or when the first application does not have visible activity in the foreground within the preset time, prohibiting the first application from calling the second application.

In a possible implementation manner, the first application invokes the second application in a broadcast or service manner, and the processing unit is further configured to determine whether the second application has a started process when the first application is not a target type application; when the second application has a started process, allowing the first application to call the second application; or when the second application does not have the started process, prohibiting the first application from calling the second application.

In a possible implementation manner, the processing unit is specifically configured to start the first application, where a timing alarm is set in a start program of the first application; when the timing time of the timing alarm arrives, an alarm management service in an application framework layer of the trigger terminal equipment detects that the first application will call the second application.

In a possible implementation manner, the processing unit is further configured to determine whether the second application is allowed to be invoked; when the second application is allowed to be called, whether the first application is a target type application or not is judged.

In one possible implementation manner, the processing unit is specifically configured to determine whether the flag bit triple of the second application is a preset value.

In a third aspect, embodiments of the present application provide an electronic device comprising a processor and a memory, the memory being for storing code instructions, the processor being for executing the code instructions to perform the method described in the first aspect or any one of the possible implementations of the first aspect.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored therein a computer program or instructions which, when run on a computer, cause the computer to perform the method of controlling application invocation described in the first aspect or any one of the possible implementations of the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when run on a computer, causes the computer to perform the method of controlling application invocation described in the first aspect or any one of the possible implementations of the first aspect.

In a sixth aspect, the present application provides a chip or chip system comprising at least one processor and a communication interface, the communication interface and the at least one processor being interconnected by wires, the at least one processor being adapted to execute a computer program or instructions to perform the method of controlling application invocation described in the first aspect or any one of the possible implementations of the first aspect. The communication interface in the chip can be an input/output interface, a pin, a circuit or the like.

In one possible implementation, the chip or chip system described above in the present application further includes at least one memory, where the at least one memory has instructions stored therein. The memory may be a memory unit within the chip, such as a register, a cache, etc., or may be a memory unit of the chip (e.g., a read-only memory, a random access memory, etc.).

It should be understood that, the second aspect to the sixth aspect of the present application correspond to the technical solutions of the first aspect of the present application, and the beneficial effects obtained by each aspect and the corresponding possible embodiments are similar, and are not repeated.

Drawings

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

fig. 2 is a schematic diagram of a software framework of an electronic device according to an embodiment of the present application

FIG. 3 is a schematic diagram of interaction between software modules according to an embodiment of the present disclosure;

FIG. 4 is a software module interaction diagram provided in an embodiment of the present application;

FIG. 5 is a schematic flow chart of controlling application call according to an embodiment of the present application;

FIG. 6 is a schematic flow chart of controlling application invocation according to an embodiment of the present application;

FIG. 7 is a schematic diagram of an interface according to an embodiment of the present disclosure;

Fig. 8 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed Description

In order to facilitate the clear description of the technical solutions of the embodiments of the present application, the following simply describes some terms and techniques related to the embodiments of the present application:

1. alarm: alarm is a class provided by android (android) for completing Alarm clock type timed tasks, and Alarm supports both disposable timed tasks and recurring timed tasks. The software system in the terminal device may manage the services for interacting with Alarm through a timing management (Alarm manager) service (Alarm manager service) in Alarm manager.

2. Activity: activity is one of four components of android, and is a visual interface operated by a user; it provides a window for the user to complete the operating instructions.

3. Other terms

In the embodiments of the present application, the words "first," "second," and the like are used to distinguish between identical or similar items that have substantially the same function and effect. For example, the first chip and the second chip are merely for distinguishing different chips, and the order of the different chips is not limited. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" 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 related concepts in a concrete fashion.

In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

4. Terminal equipment

The terminal device in the embodiment of the present application may also be any form of electronic device, for example, the electronic device may include a handheld device with an image processing function, an in-vehicle device, and the like. For example, some electronic devices are: a mobile phone, tablet, palm, notebook, mobile internet device (mobile internet device, MID), wearable device, virtual Reality (VR) device, augmented reality (augmented reality, AR) device, wireless terminal in industrial control (industrial control), wireless terminal in unmanned (self driving), wireless terminal in teleoperation (remote medical surgery), wireless terminal in smart grid (smart grid), wireless terminal in transportation security (transportation safety), wireless terminal in smart city (smart city), wireless terminal in smart home (smart home), cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, public computing device or other processing device connected to wireless modem, vehicle-mounted device, wearable device, terminal device in 5G network or evolving land mobile terminal (public land mobile network), and the like, without limiting the examples of this.

By way of example, and not limitation, in embodiments of the present application, the electronic device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, in the embodiment of the application, the electronic device may also be a terminal device in an internet of things (internet of things, ioT) system, and the IoT is an important component of future information technology development, and the main technical characteristic of the IoT is that the article is connected with a network through a communication technology, so that man-machine interconnection and an intelligent network for internet of things are realized.

The electronic device in the embodiment of the application may also be referred to as: a terminal device, a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, a user equipment, or the like.

In an embodiment of the present application, the electronic device or each network device includes a hardware layer, an operating system layer running above the hardware layer, and an application layer running above the operating system layer. The hardware layer includes hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processes through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address book, word processing software, instant messaging software and the like.

By way of example, fig. 1 shows a schematic diagram of an electronic device.

The electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of 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, such as: 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), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces 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 receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

It should be understood that the connection relationship between the modules illustrated in the embodiments of the present invention is only illustrative, and does not limit the structure of the electronic device. In other embodiments of the present application, the electronic device may also use different interfacing manners in the foregoing embodiments, or a combination of multiple interfacing manners.

The electronic device implements display functions via 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 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 change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix or active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (flex), a mini, micro led, micro-OLED, quantum dot light-emitting diode (quantum dot lightemitting diodes, QLED), a low-temperature polycrystalline oxide (low temperature polycrystalline oxide, LTPO), or the like. In some embodiments, the electronic device may include 1 or N display screens 194, N being a positive integer greater than 1.

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

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer-executable program code that includes instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device (e.g., audio data, phonebook, etc.), and so forth. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 110 performs various functional applications of the electronic device and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor. For example, a method of controlling application invocation of embodiments of the present application may be performed.

It will be appreciated that fig. 1 is a schematic diagram illustrating a structure of an electronic device, and the electronic device may include fewer or more structures, which is not specifically limited in the embodiments of the present application.

When the terminal device is operating, software support loaded in the terminal device is required in addition to some or all of the hardware support shown in fig. 1. The software loaded in the terminal device may include system software and may also include APPs that are dependent on the implementation of the system software, and some APPs may pull up the start or operation of other APPs when they start or operate.

In some implementations, in order to prevent illegal applications or reduce power consumption of the terminal device, the terminal device may set a trust list, so that when an application calls other applications, only the applications in the trust list are allowed to call other applications, so that the number of times that the associated applications are called when the application runs can be reduced, and the effects of preventing illegal applications and reducing power consumption are achieved.

However, it can be understood that the update speed of the APP is faster, the new APP is always continuously flushed, some APPs need to be assisted by other applications when being started or running, and the trust list always has the condition of untimely update or insufficient coverage, and the part of APPs cannot call other applications because of being updated in the new people list in time, so that the part of APPs runs abnormally.

In view of this, in the embodiment of the present application, whether the application allows to call other applications may be implemented based on the characteristics of the application managed in the PMS, and because any application needs to report some performance or capability to the terminal device when being loaded into the terminal device, the characteristics of each application can be timely and accurately obtained in the terminal device PMS, and further, when the application is controlled based on the characteristics of the application, whether the application allows to call other applications or not may be more accurately and timely controlled, so that an abnormal phenomenon of application running caused by prohibiting call between applications may be improved.

The following describes a software architecture diagram of an electronic device in a method for controlling application invocation according to an embodiment of the present application.

The software system of the electronic device may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the invention takes an android system with a layered architecture as an example, and illustrates the software structure of electronic equipment.

Fig. 2 is a schematic software structure of an electronic device according to an embodiment of the present application.

The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages.

As shown in fig. 2, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layer may include an activity manager (activity manager service, AMS), a package manager service (package manager service, PMS), a timing management service (alarm manager service), timing initiation management (alarm startup manager), a content provider, a view system, a resource manager, a notification manager, and the like.

The activity manager may be used to manage the running state of the application, e.g., the activity manager may flag whether the application is a foreground application, etc.

The package manager service may be used to manage the type of application, which may be adaptively partitioned based on different application scenarios.

The timing management service may be used to manage task classes of alarm.

Timing launch management may be used to manage whether launch policies are allowed when alarm invokes other programs.

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

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

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

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

Android run time includes a core library and virtual machines. Android run time is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

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

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc.

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

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

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

The kernel layer is a layer between hardware and software. The kernel layer at least comprises a timer drive, a touch panel drive, an LCD/LED screen drive, a display drive, a Bluetooth drive, a WIFI drive, a keyboard drive, a shared memory drive, an audio drive and the like.

The hardware may be an audio device, a bluetooth device, a camera device, a sensor device, etc.

By way of example, in connection with the software framework of fig. 2, fig. 3 shows a simplified schematic diagram of application a invoking application B with alarm.

As shown in fig. 3, when the application a starts, a timing alarm may be set in the application a, where the timing alarm is used to pull up the start of the application B when a timing time is reached, the timing management service (alarm manager service) may manage the timing alarm, and trigger timer timing based on a timer driver (timer driver), and when the timer timing time arrives, the timer driver triggers the timing management service to perform the given timing alarm, and the timing management service instructs the timing start management (alarm start up manager) that the application a wants to invoke the start of the application B, and the timing start management may intercept or release the start of the application B based on a type of the application a, whether the application a is a foreground application, an operation state of the application B, and so on, and may reduce power consumption if the start of the application B is intercepted, and assist in realizing a function of the application a after the start of the application B if the start is released. The specific implementation of intercepting or releasing the start of the application B based on the type of the application a, whether the application a is a foreground application, the running state of the application B, and the like will be described in the following embodiments, and will not be described herein.

It will be appreciated that both alarm manager service and alarm start up manager may be modules implemented using Java encoded program code. By way of example, fig. 4 shows a schematic diagram of interactions between Java code modules in a terminal device.

As shown in fig. 4, both awareappstartuppolicy.java and precision maker.java may be code modules for implementing alarm start up manager and alarm manager service.java may be code modules for implementing alarm manager service.

The rules for controlling application start and other rules in the embodiment of the present application may be included in the DeciseMaker.java, and after initialization, the Aware AppStartup policy.java may obtain the rules for application start and control from the DeciseMaker.java.

When the alarm timing in the alarm manager service.java arrives, the alarm manager service.java can send information to the awareappstartuppolicy.java to trigger the alarm.

The awareappstartuppolicy.java can determine whether alarm is self-starting based on alarm parameters (parameters), and the self-starting can be understood as starting without calling other applications, and can be started. The awareappstartuppolicy.java can also determine whether the application of alarm is an exemption application, and if so, can start. If the application is not self-initiated or exempt, rules in the DeciseMaker. Java may be used to determine if alarm is allowed to invoke the initiation of other applications.

The method for controlling application call in the embodiment of the present application is described in detail below through specific embodiments. The following embodiments may be combined with each other or implemented independently, and the same or similar concepts or processes may not be described in detail in some embodiments.

By way of example, fig. 5 illustrates a method for controlling application invocation according to an embodiment of the present application. The method comprises the following steps:

s501: it is detected that the first application will invoke the second application.

In this embodiment of the present application, the first application and the second application may be any application downloaded in the terminal device, where the first application may be understood as a calling party application or a pulling party application, and the second application may be understood as a called application or a pulling application.

Invoking the second application by the first application may include: the first application invokes the start of the second application, or the first application invokes the execution of certain processes in the second application, etc. The first application may, for example, invoke the second application by means of activity, service or broadcast, etc.

In this embodiment, the manner in which the first application is detected to call the second application may include, but is not limited to, one or more of the following: the method comprises the steps of detecting that a first application triggers and calls a second application in an activity mode, detecting that the first application triggers and calls the second application in a service mode, and detecting that the first application triggers and calls the second application in a broadcast mode.

S502: and judging whether the first application is a target type application based on the PMS of the terminal equipment, wherein the target type application comprises a system application and an application with a preset identifier in the terminal equipment, and the system application is an application which does not support unloading in the terminal equipment.

In the embodiment of the application, the application can be distinguished between overseas application and domestic application. Overseas applications may be understood as applications marked with preset identifiers, and the specific content of the preset identifiers is not specifically limited in the embodiments of the present application. Domestic applications may be understood as applications other than overseas applications, and domestic applications may also be labeled with domestic application identifications.

Domestic applications may also be distinguished as system applications and third party applications. A system application may refer to an application that is downloaded by default in the terminal device and that does not support uninstallation, the system application may or may not have APP icons that are visible to the user, or may be understood as being invisible to the user. A third party application may refer to an application in the terminal device that supports flexible user download and uninstallation, the third party application typically having APP icons visible to the user.

The target type application may be understood as an application allowing calling other applications in the embodiment of the present application, and the target type application includes at least an overseas application and a system application.

In this embodiment of the present application, the PMS may include information of an application type, and the terminal device may obtain the type of the first application based on the information of each application in the PMS, and further determine whether the first application is a target type application.

S503: when the first application is a target type application, the first application is allowed to call the second application.

In the embodiment of the application, when the terminal device determines that the first application is the target type application, the terminal device allows the first application to call the second application, for example, allows the second application to be started.

It will be appreciated that since the system application is typically the application that is important when the system is running, disabling the calling behavior of the system application may result in the terminal device not functioning properly. Overseas applications may need to implement some functions with other applications, which may cause the overseas application to function improperly if the calling behavior of the overseas application is disabled. Therefore, in the embodiment of the present application, if the first application is determined to be the target type application, the calling behavior of the first application is allowed, so that the phenomenon that the application in the terminal device runs abnormally can be improved.

In summary, in the embodiment of the application, the terminal device determines the decision of allowing the system application and the application with the preset identifier to call the associated application based on the PMS by itself, so that the phenomenon that the associated application cannot be normally called due to incomplete coverage of the trust list or untimely updating and the like in the prior art can be improved, and the abnormal running of the application program of the terminal device is further caused.

Optionally, based on the embodiment of fig. 5, fig. 6 shows a flowchart of a specific method for controlling application invocation according to an embodiment of the present application. As shown in fig. 6, the method includes:

s601: it is detected that the first application will invoke the second application.

In a possible implementation manner, the implementation of S601 may include starting a first application, where a starting program of the first application is provided with a timing alarm; when the timing time of the timing alarm arrives, an alarm management service in an application framework layer of the trigger terminal equipment detects that the first application will call the second application.

It can be appreciated that, because the timing alarm may be executed later than the start of the first application, when the timing time of the timing alarm arrives, the method and the device trigger the alarm management service in the application framework layer of the terminal device to detect that the first application will call the second application, which can enable the embodiment of the application to implement control of the call between applications that lags from the start trigger.

S602: and judging whether the first application is a target type application or not based on the PMS of the terminal equipment.

In a possible implementation manner, S602 further includes: judging whether the second application is allowed to be called; s602 includes: when the second application is allowed to be called, whether the first application is a target type application or not is judged.

It will be appreciated that if the second application is not allowed to be invoked, the first application cannot implement the invocation of the second application. Whether the second application is allowed to be invoked may be by default or may be set by the user.

By way of example, FIG. 7 illustrates an interface diagram that sets whether a second application is allowed to be invoked. The setting application of the terminal equipment can comprise a system manager, a user clicks a system manager control to enter an interface shown in fig. 7, application starting management can be realized in the interface shown in fig. 7, each application can correspond to an automatic starting switch, and when the corresponding automatic starting switch of the application is started, the application is allowed to be called. For example, when the second application is application B, application B corresponds to auto-start switch 701, and when auto-start switch 701 is in the on state, the second application is allowed to be invoked, and when auto-start switch 701 is in the off state, the second application is not allowed to be invoked.

In one possible implementation, the on and off states of the auto-start switch may be identified using a flag bit. Determining whether the second application is allowed to be invoked, including: judging whether the flag bit triple of the second application is a preset value. The preset value may be any set value, for example, when the three state is 0, the automatic start switch is in an on state, when the three state is 1, the automatic start switch is in an off state, or when the three state is 1, the automatic start switch is in an on state, and when the three state is 0, the automatic start switch is in an off state.

When the second application is allowed to be invoked, a determination may be continued as to whether the first application is a target type application.

When the first application is a target type application, the first application is allowed to call the second application.

When the first application is not a target type application, the following possible implementations may be included.

In a first possible implementation manner, the first application invokes the second application in an activity manner, and after S602, the method further includes: when the first application is not the target type application, determining whether to allow the first application to call the second application according to the running state of the first application.

The running state of the first application may include any state capable of reflecting whether the user can trigger the first application, if the user can trigger the first application, the first application may be allowed to call the second application, so that the triggering behavior of the user may be normally executed by the terminal, and if the user cannot trigger the first application, the first application may be prohibited from calling the second application, so as to reduce power consumption of the terminal device.

For example, the running state of the first application may include whether the first application is running in the foreground or in the background. When the first application is running in the foreground, the first application has visible activity in the foreground. The method may include:

S603a: judging whether the running state of the first application comprises whether the first application has visible activity in the foreground or whether the first application has visible activity in the foreground within a preset time length from a first moment, wherein the first moment is the moment when the first application will call the second application.

For example, when a first application has a visible activity in the foreground, allowing the first application to call a second application; or when the first application does not have visible activity in the foreground, prohibiting the first application from calling the second application.

Or when the first application has visible activity in the foreground within the preset duration, allowing the first application to call the second application; or when the first application does not have visible activity in the foreground within the preset time, prohibiting the first application from calling the second application.

In a second possible implementation manner, the first application invokes the second application in a broadcast or service manner, and the method further includes after S602:

s603b: it is determined whether the second application has a started process.

When the second application has a started process, the first application is allowed to call the second application. Because the second application already has a starting process, invoking the second application does not cause more power consumption, the first application may be allowed to invoke the second application, so that the second application may assist in the running of the first application.

Or when the second application does not have the started process, prohibiting the first application from calling the second application. Because the second application has no starting process, the second application needs to be started in a cold way, and more power consumption can be caused, so that the first application can be forbidden to call the second application, and the power consumption of the terminal equipment can be reduced.

In a third possible implementation manner, when the first application is not the target type application, it may also be determined whether the first application is a three-way PUSH software development kit (software development kit, SDK) other than the terminal device service provider, if the first application is the three-way PUSH SDK other than the terminal device service provider, the first application is not allowed to call the second application, and if the first application is not the three-way PUSH SDK other than the terminal device service provider, the first possible implementation manner or the second possible implementation manner described above when the first application is not the target type application is executed.

In summary, when the first application adopts activity, service or broadcast to call the second application, the embodiment of the application has flexible control modes, so that the power consumption of the terminal equipment is reduced and the abnormal operation of the application in the terminal equipment is improved to be balanced.

The foregoing description of the solution provided in the embodiments of the present application has been mainly presented in terms of a method. To achieve the above functions, it includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the various illustrative method steps described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

According to the embodiment of the application, the function modules of the device for realizing the method for controlling application call can be divided according to the method example, for example, each function module can be divided corresponding to each function, and two or more functions can be integrated in one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.

Fig. 8 is a schematic structural diagram of a chip according to an embodiment of the present application. Chip 1100 includes one or more (including two) processors 1101, communication lines 1102, a communication interface 1103, and a memory 1104.

In some implementations, the memory 1104 stores the following elements: executable modules or data structures, or a subset thereof, or an extended set thereof.

The method described in the embodiments of the present application may be applied to the processor 1101 or implemented by the processor 1101. The processor 1101 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuitry in hardware in the processor 1101 or instructions in software. The processor 1201 may be a general purpose processor (e.g., a microprocessor or a conventional processor), a digital signal processor (digital signal processing, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), an off-the-shelf programmable gate array (field-programmable gate array, FPGA) or other programmable logic device, discrete gates, transistor logic, or discrete hardware components, and the processor 1101 may implement or perform the methods, steps, and logic blocks related to the processes disclosed in the embodiments of the present application.

The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a state-of-the-art storage medium such as random access memory, read-only memory, programmable read-only memory, or charged erasable programmable memory (electrically erasable programmable read only memory, EEPROM). The storage medium is located in the memory 1104, and the processor 1101 reads information in the memory 1104 and performs the steps of the above method in combination with its hardware.

The processor 1101, the memory 1104, and the communication interface 1103 may communicate with each other via a communication line 1102.

In the above 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 may be written in the memory in advance, or may be downloaded in the form of software and installed in the memory.

Embodiments of the present application also provide a computer program product comprising one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL), or wireless (e.g., infrared, wireless, microwave, etc.), or semiconductor medium (e.g., solid state disk, SSD)) or the like.

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. Computer readable media can include computer storage media and communication media and can include any medium that can transfer a computer program from one place to another. The storage media may be any target media that is accessible by a computer.

As one possible design, the computer-readable medium may include compact disk read-only memory (CD-ROM), RAM, ROM, EEPROM, or other optical disk memory; the computer readable medium may include disk storage or other disk storage devices. Moreover, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the 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, digital versatile disc (digital versatile disc, DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Claims

1. A method of controlling application invocation, for application to a terminal device, the method comprising:

detecting that the first application will invoke the second application;

judging whether the first application is a target type application or not based on a package manager service PMS of the terminal equipment, wherein the target type application comprises a system application and an application with a preset identifier in the terminal equipment, and the system application is an application which does not support unloading in the terminal equipment;

Allowing the first application to call the second application when the first application is the target type application;

when the first application is not the target type application, judging whether the first application is a three-party PUSH software development kit except a terminal equipment service provider;

if the first application is a three-party PUSH software development kit except a terminal equipment service provider, the first application is not allowed to call the second application;

if the first application is not a three-party PUSH software development kit except for a terminal equipment service provider and the first application calls the second application in an activity mode, determining whether the first application is allowed to call the second application or not according to the running state of the first application;

the running state of the first application includes whether the first application has visible activity in the foreground, and the determining whether to allow the first application to call the second application according to the running state of the first application includes:

allowing the first application to call the second application when the first application has visible activity in the foreground;

and when the first application does not have visible activity in the foreground, prohibiting the first application from calling the second application.

2. The method of claim 1, wherein the running state of the first application includes whether the first application has a visible activity in the foreground within a preset time period from a first time point, the first time point being a time point when the first application will call the second application, and the determining whether to allow the first application to call the second application according to the running state of the first application includes:

when the first application has visible activity in the foreground within the preset duration, allowing the first application to call the second application;

or when the first application does not have visible activity in the foreground within the preset time, prohibiting the first application from calling the second application.

3. The method of claim 1, wherein if the first application is not a three-way PUSH software development kit other than a terminal device service provider and the first application invokes the second application in a broadcast or service manner, the method further comprises:

judging whether the second application has a started process or not;

allowing the first application to call the second application when the second application has a started process;

Or when the second application does not have the started process, prohibiting the first application from calling the second application.

4. A method according to any of claims 1-3, wherein the detecting that the first application will invoke the second application comprises:

starting the first application, wherein a starting program of the first application is provided with a timing alarm;

triggering an alarm management service in the terminal device application framework layer to detect that the first application will call a second application when the timing time of the timing alarm arrives.

5. A method according to any one of claims 1-3, wherein before determining whether the first application is a target type application, further comprising:

judging whether the second application is allowed to be called or not;

the determining whether the first application is a target type application includes: and when the second application is allowed to be called, judging whether the first application is a target type application or not.

6. The method of claim 5, wherein the determining whether the second application is allowed to be invoked comprises:

judging whether the flag bit triple of the second application is a preset value or not.

7. A terminal device, comprising: a memory for storing a computer program, and a processor for executing the computer program to perform the method of controlling application invocation of any of claims 1-6.

8. A computer readable storage medium storing instructions that, when executed, cause a computer to perform the method of controlling application invocation of any of claims 1-6.

9. A computer program product comprising a computer program which, when run, causes an electronic device to perform the method of any of claims 1-6.