CN106201574B - Application interface starting method and device - Google Patents
Application interface starting method and device Download PDFInfo
- Publication number
- CN106201574B CN106201574B CN201610473746.3A CN201610473746A CN106201574B CN 106201574 B CN106201574 B CN 106201574B CN 201610473746 A CN201610473746 A CN 201610473746A CN 106201574 B CN106201574 B CN 106201574B
- Authority
- CN
- China
- Prior art keywords
- application
- application program
- source
- identifier
- starting
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides a starting method and a device of an application interface, wherein the starting method comprises the steps of receiving a starting request of the application interface, judging whether a source application program initiating the starting request is an application program running in the foreground, further judging whether the application interface belongs to the source application program if the source application program is judged to be the application program running in the foreground, and starting the application interface if the application interface belongs to the source application program; according to the scheme, only the application program operated in the foreground is allowed to start the application interface of the application program, and compared with the prior art, the safety of starting the application interface is improved.
Description
Technical Field
The invention relates to the technical field of terminals, in particular to a method and a device for starting an application interface.
Background
Along with the development of the intelligent terminal, the intelligent terminal has more and more functions which can be compatible with each other, so that the life of a user is enriched, and convenience is brought to the user. With the increasingly integrated life and the improved application functions of mobile terminal equipment, great convenience is brought to users and the user experience is improved.
In order to implement various functions to meet various needs of users, a smart terminal typically installs various application programs (which may be simply referred to as applications). These applications typically launch one or more application interfaces (i.e., user-viewable program interfaces) when they are running.
However, sometimes an application interface for application launch is not necessary. For example, a pop-up interface (e.g., an advertising interface) that an application launches while running in the background may be displayed in the foreground, interfering with the normal operation of the application running in the foreground; for another example, an application program in operation may wake up an application interface (e.g., a payment interface of payment software) of another application program through mutual wake-up between the application programs, and may cause misoperation of a user to cause unnecessary loss.
Therefore, the unnecessary application interface for starting the application program may cause interruption or crash of the application program running in the foreground, and even cause misoperation of the user to cause unnecessary loss, so that the safety of the application interface starting method in the prior art is low, and further improvement is needed.
Disclosure of Invention
The embodiment of the invention provides a method and a device for starting an application interface, which can improve the starting safety of the application interface.
The embodiment of the invention provides a starting method of an application interface, which comprises the following steps:
receiving a starting request of an application interface;
judging whether the source application program initiating the starting request is an application program running in a foreground or not;
if the source application program is judged to be the application program running in the foreground, further judging whether the application interface belongs to the source application program;
and if the application interface belongs to the source application program, starting the application interface.
Further, the step of determining whether the source application program initiating the start request is an application program running in the foreground specifically includes:
acquiring an application identifier of a source application program which initiates the starting request;
acquiring an application identifier of an application program running in a foreground to obtain an application identifier set;
judging whether an application identifier which is the same as the application identifier of the source application program exists in the application identifier set or not;
if so, determining that the source application program initiating the starting request is the application program running in the foreground.
Further, the step of determining whether the application interface belongs to the source application program specifically includes:
judging whether the application identifier of the source application program is a target application identifier, wherein the target application identifier is the application identifier of the application program to which the application interface belongs;
if so, determining that the application interface belongs to the source application program.
Further, the starting request carries a component identifier corresponding to the application interface, and the step of starting the application interface specifically includes:
determining a corresponding target component according to the component identifier;
and creating a corresponding application interface according to the target component.
Further, the starting method further comprises the following steps:
if the source application program initiating the starting request is judged not to be the application program running in the foreground or the application interface is judged not to belong to the source application program, further judging whether the source application program requires to return an execution result of the starting request;
and if the judgment is that the source application program requires to return the execution result of the starting request, sending the information that the starting request is rejected to the source application program.
Further, the starting method further comprises the following steps:
if the source application program initiating the starting request is judged not to be the application program running in the foreground or the application interface is judged not to belong to the source application program, the information that the starting request is rejected is sent to a terminal system, and the information is added into a log file of the terminal system.
Correspondingly, an embodiment of the present invention further provides a device for starting an application interface, including:
the receiving module is used for receiving a starting request of an application interface;
the first judgment module is used for judging whether the source application program initiating the starting request is an application program running in a foreground or not;
the second judgment module is used for further judging whether the application interface belongs to the source application program or not when the first judgment module judges that the application interface belongs to the source application program;
and the execution module is used for starting the application interface when the second judgment module judges that the second judgment module is yes.
Further, the first determining module specifically includes:
the first obtaining submodule is used for obtaining an application identifier of a source application program which sends the starting request;
the second obtaining submodule is used for obtaining the application identifier of the application program running in the foreground so as to obtain an application identifier set;
the judging submodule is used for judging whether the application identifier which is the same as the application identifier of the source application program exists in the application identifier set or not; if so, determining that the source application program initiating the starting request is the application program running in the foreground.
Further, the second determining module is specifically configured to:
judging whether the application identifier of the source application program is a target application identifier, wherein the target application identifier is the application identifier of the application program to which the application interface belongs; if so, determining that the application interface belongs to the source application program.
Further, the start request carries a component identifier corresponding to the application interface, and the execution module specifically includes:
the determining submodule is used for determining a corresponding target component according to the component identifier;
and the creating sub-module is used for creating a corresponding application interface according to the target component.
The embodiment of the invention receives a starting request of an application interface, judges whether a source application program initiating the starting request is an application program running in the foreground, if the source application program is the application program running in the foreground, further judges whether the application interface belongs to the source application program, and if the application interface belongs to the source application program, starts the application interface; according to the scheme, whether a source application program is an application program running in a foreground is judged firstly, then whether the application interface belongs to the source application program is further judged, and the application interface is started only when the application program running in the foreground requests to start the application interface of the application program.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for starting an application interface according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a method for starting an application interface according to a second embodiment of the present invention;
fig. 3a is a schematic structural diagram of a starting apparatus of a first application interface according to a third embodiment of the present invention;
fig. 3b is a schematic structural diagram of a starting apparatus of a second application interface according to a third embodiment of the present invention;
fig. 3c is a schematic structural diagram of a third application interface starting apparatus according to a third embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention provides a method and a device for starting an application interface, which are respectively described in detail below.
Example one
The embodiment will be described from the perspective of a starting apparatus of an application interface, where the apparatus may be specifically integrated in a terminal, and the terminal may be a smart phone, a tablet computer, or other devices.
A starting method of an application interface comprises the following steps: receiving a starting request of an application interface, judging whether a source application program initiating the starting request is an application program running in the foreground, if the source application program is judged to be the application program running in the foreground, further judging whether the application interface belongs to the source application program, and if the application interface belongs to the source application program, starting the application interface.
As shown in fig. 1, the specific process of the starting method of the application interface may be as follows:
s101, receiving a starting request of an application interface.
Specifically, in an operating system (e.g., an Android system) of the terminal, starting an application interface of any application program must start a corresponding Activity component (an interface component, one of the four most important components in the Android system), and when the Activity component is created, the Activity component lays out a file according to its own interface to generate a corresponding application interface, and then the application interface is displayed through a window management service of the system and presented to a user. In the operating system, the Activity components corresponding to the startup application interface all have a uniform program entry, that is, a startActivity function (interface startup function) in the Activity management service (Activity manager service). Any application program wishing to launch an application interface must send a request to the system to launch the application interface to invoke a startActivity function in the system to launch the corresponding Activity component. The application interface started by the application program through the startActivity function can be the interface of the application program itself or the interface of other application programs.
In practical applications, there are various ways for an application program to send a start request of an application interface to an operating system, for example, a user clicks a button on a main interface of an application program (the button functions as another interface for starting the application program), and the application program immediately initiates a start request of the application interface to the system to respond to the user's operation; for another example, an application is set to be started regularly, and when the time point of the timed start is reached, the application automatically initiates a start request of an application interface to the system to start the application. After the application program initiates a starting request of an application interface, the terminal receives the starting request and processes the starting request.
S102, judging whether the source application program initiating the starting request is the application program running in the foreground.
In a specific application, in order to prevent an application program running in a background from calling a startActivity function in a system to create an application interface (e.g., an advertisement interface) and thereby affecting a user, it is necessary to determine whether the application program initiating a start request of the application interface is running in a foreground, where the specific determination process may include the following steps:
acquiring an application identifier of a source application program which initiates the starting request;
acquiring an application identifier of an application program running in a foreground to obtain an application identifier set;
and judging whether the application identifier which is the same as the application identifier of the source application program exists in the application identifier set.
Specifically, when an application initiates a start request of an application interface to a terminal system to call a startActivity function in the system, the start request includes parameters required by the startActivity function, for example, an initiator of the start request (i.e., a source application program that initiates the start request), an owner of the application interface (i.e., a target application program that the application interface belongs to), and the terminal system may obtain an application identifier of the source application program that initiates the start request through the parameters, where the application identifier may be a package name of the application program installed in the system (e.g., a package name of a WeChat application program installed in the system is com.
Subsequently, the terminal system acquires the application identifier of the application program running in the foreground. Specifically, the application running in the foreground of the terminal may be one or more (for example, when the terminal may display in a split screen manner, multiple application running in the foreground may exist at the same time), the terminal may obtain, through an activity management service (activity manager service), an application identifier of the application running in the foreground, where the type of the application identifier is the same as the type of the obtained application identifier of the source application, and when multiple applications run in the foreground at the same time, the application identifiers of the multiple applications form an application identifier set.
Then, the terminal system determines whether an application identifier identical to the application identifier of the source application program exists in the application identifier set. Specifically, the terminal system may compare the application identifier of the source application program with the application identifiers in the application identifier set one by one to make a determination. When the application identifier identical to the application identifier of the source application program exists in the application identifier set, it may be determined that the source application program initiating the start request is an application program running in the foreground, and then step S103 is performed.
S103, judging whether the application interface belongs to the source application program.
As will be appreciated by those skilled in the art, an application interface is a component in an application program. In a specific application, in order to prevent an application program from starting an application interface of another application program and causing an influence on a user, it is necessary to determine whether the application interface requested to be started belongs to the source application program. There are various methods for achieving this determination, and for example, the determination may be made by:
and judging whether the application identifier of the source application program is a target application identifier, wherein the target application identifier is the application identifier of the application program to which the application interface belongs.
Specifically, the terminal system may obtain, through parameters carried in the received start request, an application program, that is, a target application program, to which the application interface belongs, and also obtain an application identifier of the target application program, where the type of the application identifier is the same as the type of the obtained application identifier of the source application program, and the obtained application identifier of the target application program is the target application identifier.
And then, the terminal system compares the acquired target application identifier with the acquired application identifier of the source application program, and judges whether the acquired target application identifier and the acquired application identifier of the source application program are the same. If the two are the same, the application identifier of the source application program is the target application identifier, and at this time, it may be determined that the application interface requested to be started belongs to the source application program, and then step S104 is executed.
And S104, starting the application interface.
Specifically, when the application interface requested to be started belongs to the source application program, the terminal system starts the corresponding application interface according to the starting request. The starting of the application interface may specifically include the following steps:
determining a corresponding target component according to the component identifier carried by the starting request and corresponding to the application interface;
and creating a corresponding application interface according to the target component.
Specifically, parameters carried by a start request initiated by a source application program include a component identifier of an application interface requested to be started, a terminal system obtains the component identifier of the application interface according to the parameters in the received start request, then determines a target component according to the component identifier, and calls a startActivity function in the system to start the target component, so as to create the application interface corresponding to the target component.
Preferably, when it is determined in step S102 that the source application initiating the start request is not an application running in the foreground, or when it is determined in step S103 that the application interface does not belong to the source application, the terminal system rejects starting the application interface, that is, rejects the start request, and at this time, the start method of the application interface may further include the following steps:
judging whether the source application program requires to return an execution result of the starting request or not;
and if so, sending information that the starting request is rejected to the source application program.
Specifically, the start request initiated by the source application program may include information on whether an execution result needs to be returned, for example, a flag bit is set in the start request, the flag bit being 1 indicates that the execution result needs to be returned, the flag bit being 0 indicates that the execution result does not need to be returned, and the terminal system may determine whether the source application program requires to return the execution result of the start request by using the flag bit in the received start request.
And when the source application program is judged to require to return the execution result of the starting request, sending the information that the starting request is rejected to the source application program so that the source application program can know the execution result of the starting request, thereby avoiding the application program from being blocked due to the fact that the source application program continuously waits for the starting of the requested application interface.
Preferably, when it is determined in step S102 that the source application initiating the start request is not an application running in the foreground, or when it is determined in step S103 that the application interface does not belong to the source application, the terminal system rejects starting the application interface, that is, rejects the start request, and at this time, the start method of the application interface may further include the following steps:
and sending the information that the starting request is rejected to a terminal system, and adding the information into a log file of the terminal system.
Specifically, after rejecting the start request, information that the start request is rejected may be reported to the terminal system, and the information may be added to a log file of the terminal system, where the information may include information such as a reason why the start request was rejected and a time when the start request was rejected.
As can be seen from the above, in the method for starting an application interface provided in the embodiment of the present invention, the method includes receiving a start request of an application interface, determining whether a source application program initiating the start request is an application program running in the foreground, if the source application program is the application program running in the foreground, further determining whether the application interface belongs to the source application program, and if the application interface belongs to the source application program, starting the application interface; according to the scheme, whether a source application program is an application program running in a foreground is judged firstly, then whether the application interface belongs to the source application program is further judged, and the application interface is started only when the application program running in the foreground requests to start the application interface of the application program.
Example two
The method for starting the application interface according to the first embodiment will be described in further detail below by way of example.
In this embodiment, a starting device of an application interface is specifically integrated in a smart phone, and a starting method of an application interface in a smart phone is taken as an example to be described in detail.
As shown in fig. 2, the specific process of the starting method of the application interface may be as follows:
s201, receiving a starting request of an application interface.
Specifically, there are various ways for the smart phone to receive the start request of the application interface, for example, a user clicks a button on a main interface of an application program (the button functions as another interface for starting the application program), the application program immediately initiates a start request of the application interface to the system to respond to the operation of the user, and then the smart phone receives the start request; for another example, an application is set to be started regularly, when the time point of the timed start is reached, the application automatically initiates a start request of an application interface to the system to start the application, and then the smartphone receives the start request.
S202, acquiring the application identification of the source application program which initiates the starting request.
Specifically, when an application program initiates a start request of an application interface to a smartphone system to call a startActivity function in the system, the start request includes parameters required by the startActivity function, for example, an initiator of the start request (i.e., a source application program that initiates the start request), and an owner of the application interface (i.e., a target application program that the application interface belongs to), and the smartphone system can obtain an application identifier of the source application program that initiates the start request through the parameters, where the application identifier may be a package name of the application program installed in the system (for example, the package name of a wechat application program installed in the system is com.
S203, acquiring the application identifier of the application program running in the foreground to obtain an application identifier set.
Specifically, one or more application programs running in the foreground of the smartphone may be obtained through an activity management service (activitymanager service), the type of the application identifier is the same as the type of the obtained application identifier of the source application program, and when a plurality of application programs simultaneously run in the foreground, the application identifiers of the plurality of application programs form an application identifier set.
S204, judging whether the application identifier set has the application identifier which is the same as the application identifier of the source application program.
Specifically, the smartphone system may compare the application identifier of the source application program with the application identifiers in the application identifier set one by one to determine, when the application identifier of the source application program is the same as a certain application identifier in the application identifier set, it may be determined that an application identifier that is the same as the application identifier of the source application program exists in the application identifier set, and then step S205 is executed; when the application identifier of the source application program is not the same as all the application identifiers in the application identifier set, it is determined that the application identifier same as the application identifier of the source application program does not exist in the application identifier set, and then step S208 is executed.
S205, determine whether the application identifier of the source application program is a target application identifier, where the target application identifier is an application identifier of an application program to which the application interface belongs.
Specifically, the smartphone system may obtain, through parameters carried in the received start request, an application program, that is, a target application program, to which the application interface belongs, and also obtain an application identifier of the target application program, where the type of the application identifier is the same as the type of the obtained application identifier of the source application program, and the obtained application identifier of the target application program is the target application identifier.
And then, the smart phone system compares the acquired target application identifier with the acquired application identifier of the source application program, and judges whether the acquired target application identifier and the acquired application identifier are the same. If the two are the same, the application identifier of the source application program is determined to be the target application identifier, and then step S206 is executed; if the two are not the same, it is determined that the application identifier of the source application program is not the target application identifier, and then step S208 is executed.
And S206, determining a corresponding target component according to the component identifier carried by the starting request and corresponding to the application interface.
Specifically, parameters carried by a starting request initiated by a source application program include a component identifier of an application interface requested to be started, the smart phone system obtains the component identifier of the application interface according to the parameters in the received starting request, and then determines a target component according to the component identifier.
And S207, creating a corresponding application interface according to the target component.
Specifically, after the target component is determined, a startActivity function in the system is called to start the target component, so as to create an application interface corresponding to the target component.
S208, judging whether the source application program requires to return the execution result of the starting request.
Specifically, the start request initiated by the source application program may include information on whether an execution result needs to be returned, for example, a flag bit is set in the start request, where the flag bit is 1 and indicates that the execution result needs to be returned, and the flag bit is 0 and indicates that the execution result does not need to be returned, and the smartphone system may determine, through the flag bit in the received start request, whether the source application program requires to return the execution result of the start request, and if it determines that the execution result needs to be returned, then step S209 is executed.
S209, sends information that the start request is rejected to the source application.
And when the source application program is judged to require to return the execution result of the starting request, sending the information that the starting request is rejected to the source application program so that the source application program can know the execution result of the starting request, thereby avoiding the application program from being blocked due to the fact that the source application program continuously waits for the starting of the requested application interface.
As can be seen from the above, the method for starting an application interface provided in the embodiment of the present invention includes receiving a start request of an application interface, obtaining an application identifier of a source application program that initiates the start request, obtaining an application identifier of an application program that runs in a foreground, to obtain an application identifier set, determining whether an application identifier that is the same as the application identifier of the source application program exists in the application identifier set, if an application identifier that is the same as the application identifier of the source application program exists in the application identifier set, continuing to determine whether the application identifier of the source application program is a target application identifier, if the application identifier of the source application program is the target application identifier, determining a corresponding target component according to a component identifier that is carried by the start request and corresponds to the application interface, and creating a corresponding application interface according to the target component, if the application identifier that is the same as the application identifier of the source application program does not exist in the application identifier set or the source application program does not exist in the application identifier set If the application identifier of the sequence is not the target application identifier, continuing to judge whether the source application program requires to return the execution result of the starting request, and if so, sending information that the starting request is rejected to the source application program; the scheme is characterized in that when an application identifier which is the same as the application identifier of the source application program exists in an application identifier set and the application identifier of the source application program is a target application identifier, a corresponding application interface is created, when the application identifier set does not have the application identifier which is the same as the application identifier of the source application program or the application identifier of the source application program is not the target application identifier and the source application program requires to return an execution result of the start request, information that the start request is rejected is sent to the source application program, compared with the prior art, the scheme only allows the application program running in the foreground to start the application interface of the scheme, but not allows the application program running in the background to start the application interface, and also does not allow the application program running in the foreground to start the application interfaces of other application programs, and the information that the start request is rejected can be sent to the source application program after the start request of the application interfaces is rejected, the safety of starting the application interface is improved.
EXAMPLE III
In order to better implement the method, an embodiment of the present invention further provides an application interface starting apparatus, where the application interface starting apparatus may be integrated in a terminal, and the terminal may be a smart phone, a tablet computer, or other device.
As shown in fig. 3a, the starting device of the application interface may include: the receiving module 301, the first determining module 302, the second determining module 303, and the executing module 304 are described in detail as follows:
the receiving module 301 is configured to receive a start request of an application interface;
the first determining module 302 is configured to determine whether a source application initiating the start request is an application running in a foreground;
the second determining module 303 is configured to further determine whether the application interface belongs to the source application program when the first determining module 302 determines that the application interface belongs to the source application program;
the executing module 304 is configured to start the application interface when the second determining module 303 determines that the application interface is yes.
Preferably, as shown in fig. 3b, the first determining module 302 may include: the first obtaining submodule 3021, the second obtaining submodule 3022, and the determining submodule 3023 are specifically as follows:
the first obtaining sub-module 3021, configured to obtain an application identifier of a source application program that sends the start request;
the second obtaining sub-module 3022 is configured to obtain an application identifier of an application program running in the foreground, so as to obtain an application identifier set;
the determining submodule 3023 is configured to determine whether an application identifier that is the same as the application identifier of the source application program exists in the application identifier set; if yes, the source application program which initiates the starting request is determined to be the application program which runs in the foreground.
Preferably, the initiation request carries a component identifier corresponding to the application interface, as shown in fig. 3c, the executing module 304 may include: determining submodule 3041 and creating submodule 3042 specifically include the following:
the determining submodule 3041, configured to determine a corresponding target component according to the component identifier;
the creating sub-module 3042 is configured to create a corresponding application interface according to the target component.
As can be seen from the above, in the starting apparatus for an application interface provided in the embodiment of the present invention, the receiving module 301 receives a starting request of the application interface, the first determining module 302 determines whether a source application initiating the starting request is an application running in the foreground, the second determining module 303 further determines whether the application interface belongs to the source application when the first determining module 302 determines that the source application is the foreground, and the executing module 304 starts the application interface when the second determining module 303 determines that the source application is the foreground; according to the scheme, whether a source application program is an application program running in a foreground is judged firstly, then whether the application interface belongs to the source application program is further judged, and the application interface is started only when the application program running in the foreground requests to start the application interface of the application program.
In specific implementation, the above modules may be implemented as independent entities, or may be combined arbitrarily to be implemented as the same or several entities, and specific implementation of the above modules may refer to the foregoing method embodiments, which are not described herein again.
It should be noted that, as one of ordinary skill in the art would understand, all or part of the steps in the methods of the above embodiments may be implemented by hardware related to instructions of a program, where the program may be stored in a computer-readable storage medium, and the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
The method and the device for starting the application interface provided by the embodiment of the invention are described in detail, a specific example is applied in the text to explain the principle and the implementation mode of the invention, and the description of the embodiment is only used for helping to understand the method and the core idea of the invention; meanwhile, for those skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (11)
1. A starting method of an application interface is characterized by comprising the following steps:
when a source application program is in a running state, receiving a starting request of an application interface;
judging whether the source application program initiating the starting request is an application program running in a foreground or not;
if the source application program is judged to be the application program running in the foreground, further judging whether the application interface belongs to the source application program;
if the application interface belongs to the source application program, starting the application interface so that the source application program starts the application interface of the source application program.
2. The starting method according to claim 1, wherein the step of determining whether the source application program initiating the start request is an application program running in a foreground specifically includes:
acquiring an application identifier of a source application program which initiates the starting request;
acquiring an application identifier of an application program running in a foreground to obtain an application identifier set;
judging whether an application identifier which is the same as the application identifier of the source application program exists in the application identifier set or not;
if so, determining that the source application program initiating the starting request is the application program running in the foreground.
3. The starting method according to claim 2, wherein the step of determining whether the application interface belongs to the source application program specifically includes:
judging whether the application identifier of the source application program is a target application identifier, wherein the target application identifier is the application identifier of the application program to which the application interface belongs;
if so, determining that the application interface belongs to the source application program.
4. The starting method according to claim 1, wherein the starting request carries a component identifier corresponding to the application interface, and the step of starting the application interface specifically includes:
determining a corresponding target component according to the component identifier;
and creating a corresponding application interface according to the target component.
5. The startup method according to claim 1, characterized in that the startup method further comprises:
if the source application program initiating the starting request is judged not to be the application program running in the foreground or the application interface is judged not to belong to the source application program, further judging whether the source application program requires to return an execution result of the starting request;
and if the judgment is that the source application program requires to return the execution result of the starting request, sending the information that the starting request is rejected to the source application program.
6. The startup method according to claim 1, characterized in that the startup method further comprises:
if the source application program initiating the starting request is judged not to be the application program running in the foreground or the application interface is judged not to belong to the source application program, the information that the starting request is rejected is sent to a terminal system, and the information is added into a log file of the terminal system.
7. An apparatus for launching an application interface, comprising:
the receiving module is used for receiving a starting request of an application interface when a source application program is in a running state;
the first judgment module is used for judging whether the source application program initiating the starting request is an application program running in a foreground or not;
the second judgment module is used for further judging whether the application interface belongs to the source application program or not when the first judgment module judges that the application interface belongs to the source application program;
and the execution module is used for starting the application interface when the second judgment module judges that the second judgment module is yes, so that the source application program starts the application interface of the source application program.
8. The starting device according to claim 7, wherein the first determining module specifically comprises:
the first obtaining submodule is used for obtaining an application identifier of a source application program which sends the starting request;
the second obtaining submodule is used for obtaining the application identifier of the application program running in the foreground so as to obtain an application identifier set;
the judging submodule is used for judging whether the application identifier which is the same as the application identifier of the source application program exists in the application identifier set or not; if so, determining that the source application program initiating the starting request is the application program running in the foreground.
9. The starting device according to claim 8, wherein the second determination module is specifically configured to:
judging whether the application identifier of the source application program is a target application identifier, wherein the target application identifier is the application identifier of the application program to which the application interface belongs; if so, determining that the application interface belongs to the source application program.
10. The starting device according to claim 7, wherein the starting request carries a component identifier corresponding to the application interface, and the execution module specifically includes:
the determining submodule is used for determining a corresponding target component according to the component identifier;
and the creating sub-module is used for creating a corresponding application interface according to the target component.
11. A storage medium having stored thereon a computer program which, when run on a computer, causes the computer to perform the steps of the method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610473746.3A CN106201574B (en) | 2016-06-22 | 2016-06-22 | Application interface starting method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610473746.3A CN106201574B (en) | 2016-06-22 | 2016-06-22 | Application interface starting method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106201574A CN106201574A (en) | 2016-12-07 |
| CN106201574B true CN106201574B (en) | 2020-02-14 |
Family
ID=57461046
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610473746.3A Active CN106201574B (en) | 2016-06-22 | 2016-06-22 | Application interface starting method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106201574B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106126232B (en) * | 2016-06-22 | 2018-07-27 | 广东欧珀移动通信有限公司 | A kind of interface startup method and device |
| CN107220077B (en) | 2016-10-20 | 2019-03-19 | 华为技术有限公司 | Using the management-control method and management and control devices of starting |
| CN106874086B (en) * | 2017-01-25 | 2019-11-05 | 北京安云世纪科技有限公司 | A kind of processing method, device and the mobile terminal of application program self-starting |
| CN106802819B (en) * | 2017-01-25 | 2020-02-14 | 北京安云世纪科技有限公司 | Application program self-starting processing method and device and mobile terminal |
| CN106874089B (en) * | 2017-01-25 | 2019-11-05 | 北京安云世纪科技有限公司 | A kind of processing method, device and the mobile terminal of application program self-starting |
| CN106874048B (en) * | 2017-01-25 | 2019-11-05 | 北京安云世纪科技有限公司 | A kind of processing method, device and the mobile terminal of application program self-starting |
| CN106843977B (en) * | 2017-01-25 | 2019-11-05 | 北京安云世纪科技有限公司 | A kind of processing method, device and the mobile terminal of application program self-starting |
| CN106874088B (en) * | 2017-01-25 | 2019-11-05 | 北京安云世纪科技有限公司 | A kind of processing method, device and the mobile terminal of application program self-starting |
| WO2019061331A1 (en) * | 2017-09-29 | 2019-04-04 | 深圳传音通讯有限公司 | Method, apparatus and readable storage medium for blocking app-to-app wake-up |
| CN109542531B (en) * | 2018-10-26 | 2021-11-23 | 创新先进技术有限公司 | File layout adjustment method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103605524A (en) * | 2013-11-26 | 2014-02-26 | 广东欧珀移动通信有限公司 | Method and device for running programs on mobile terminal in split-screen manner |
| CN104714725A (en) * | 2011-12-31 | 2015-06-17 | 北京奇虎科技有限公司 | Display method and device of floating window |
| CN105094551A (en) * | 2015-07-24 | 2015-11-25 | 联想(北京)有限公司 | Information processing method and electronic equipment |
| CN105094280A (en) * | 2015-07-07 | 2015-11-25 | 北京奇虎科技有限公司 | Method, apparatus and system for improving standby performance of intelligent terminal |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104077521B (en) * | 2013-03-25 | 2017-11-24 | 联想(北京)有限公司 | Information processing method and device |
| CN105512549A (en) * | 2015-12-02 | 2016-04-20 | 珠海市君天电子科技有限公司 | Application program intercepting method and device |
-
2016
- 2016-06-22 CN CN201610473746.3A patent/CN106201574B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104714725A (en) * | 2011-12-31 | 2015-06-17 | 北京奇虎科技有限公司 | Display method and device of floating window |
| CN103605524A (en) * | 2013-11-26 | 2014-02-26 | 广东欧珀移动通信有限公司 | Method and device for running programs on mobile terminal in split-screen manner |
| CN105094280A (en) * | 2015-07-07 | 2015-11-25 | 北京奇虎科技有限公司 | Method, apparatus and system for improving standby performance of intelligent terminal |
| CN105094551A (en) * | 2015-07-24 | 2015-11-25 | 联想(北京)有限公司 | Information processing method and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106201574A (en) | 2016-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106201574B (en) | Application interface starting method and device | |
| CN106156619B (en) | Application security protection method and device | |
| US20160328241A1 (en) | Data processing method for multiple operating systems and terminal equipment | |
| EP2985695B1 (en) | Method and device for setting application program state | |
| CN104978180B (en) | Unprocessed event prompting method and device and mobile terminal | |
| CN110018765B (en) | Page display method, device, terminal and storage medium | |
| CN110007936B (en) | Data processing method and device | |
| US9489248B2 (en) | Method, apparatus and system for acquiring input events | |
| CN113766487B (en) | Cloud mobile phone information acquisition method, device, equipment and medium | |
| US9727351B2 (en) | Method and device for setting status of application | |
| CN106874020B (en) | Method and device for starting plug-in | |
| CN112738046B (en) | One-key login method, terminal and system server | |
| CN108241515B (en) | Application shortcut establishing method and terminal | |
| CN105975306A (en) | Application program starting management method and application program starting management apparatus for electronic device | |
| CN107710211A (en) | Intelligent terminal system starts method, apparatus and intelligent terminal | |
| CN110659082A (en) | Application program interface display method and device, terminal and storage medium | |
| CN109284137B (en) | Hypervisor-based QNX operating system starting method and device | |
| CN109840113B (en) | Application data processing method and equipment, storage medium and terminal thereof | |
| CN107885548B (en) | System starting method and device | |
| CN113286349B (en) | Personal hot spot connection method, device, terminal and storage medium | |
| CN105025482B (en) | Communication information processing method and equipment thereof | |
| CN107968799B (en) | Information acquisition method, terminal equipment and system | |
| CN110262813B (en) | Method and apparatus for installing applications | |
| WO2016188227A1 (en) | Intelligent terminal shortcut establishment method and device | |
| CN109150951B (en) | Method and device for starting Activity of Android system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant after: OPPO Guangdong Mobile Communications Co., Ltd. Address before: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant before: Guangdong Opel Mobile Communications Co., Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |