CN106095520A - A kind of limit the method and device that third-party application mutually starts - Google Patents
A kind of limit the method and device that third-party application mutually starts Download PDFInfo
- Publication number
- CN106095520A CN106095520A CN201610617524.4A CN201610617524A CN106095520A CN 106095520 A CN106095520 A CN 106095520A CN 201610617524 A CN201610617524 A CN 201610617524A CN 106095520 A CN106095520 A CN 106095520A
- Authority
- CN
- China
- Prior art keywords
- application
- party
- blacklist
- starts
- destination service
- 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.)
- Pending
Links
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
Abstract
The present invention proposes and a kind of limits the method and device that third-party application mutually starts, the method includes: when the first application starts destination service, if the application belonging to described destination service is the second application, it is judged that whether the first application is same application with the second application；Described second application is third-party application；When the first application is not same application with the second application, it is judged that whether the second application is in blacklist, if second applies in blacklist, then No starting second is applied.Present invention could apply in the terminal of Android system, by judge to start the source of the application of destination service and through blacklist examination forbid third-party application that user undesirably runs on backstage stealthily startup optimization, can effectively solve the terminal operating card that the application of terminal running background causes more pause, slack-off problem.
Description
Technical field
The present invention relates to end application technical field, particularly relate to a kind of limit the side that third-party application mutually starts
Method and device.
Background technology
In the android project increased income, the service that oneself realizes can be supplied to it by the way of export by application
Its application program uses.As long as applying the service by oneself realizes to share out by the way of export, other application program
When binding this service, the application belonging to this service will be activated, it is not necessary to user operation.
Along with the popularization and application program of Android platform gets more and more, the application of each company is intended to more run,
Reach the effect more preferably runed.After an application A is clicked on operation by user, A can be by binding the service of other application
Mode deactivation with company or associated application B, C, D etc., no matter A the most really needs to use these to service.This
Sample results in the substantial amounts of user of in Android system running background it is not expected that the application that uses, consumes CPU and internal memory money
Source, the problem such as cause terminal operating card to pause, slack-off.
Summary of the invention
The technical problem to be solved in the present invention is to provide and a kind of limits the method and device that third-party application mutually starts,
Prevent what user from undesirably running to apply the automatic operation on backstage.
The technical solution used in the present invention is, the method that described restriction third-party application mutually starts, including:
When the first application starts destination service, if the application belonging to described destination service is the second application, it is judged that first
Whether application is same application with the second application；Described second application is third-party application；
When the first application is not same application with the second application, it is judged that whether second apply in blacklist, if the
Two apply in blacklist, then No starting second is applied.
Further, described method also includes:
When the first application is same application with the second application, start the second application to use described destination service.
Further, described method also includes:
If the second application is not in blacklist, then start the second application to use described destination service.
Further, the acquisition mode of the application in described blacklist, including:
Receive, by user setup interface, the application that user chooses from the third-party application downloaded, join blacklist
In.
Further, described method, also include:
Before judging whether the first application is same application with the second application, first judge that described first application is system
Application or third-party application, when judging that described first application is third-party application, then judge the first application and the second application
Whether it is same application.
The present invention also provides for a kind of limiting the device that third-party application mutually starts, including:
First judge module, for when the first application starts destination service, if the application belonging to described destination service is
Second application, it is judged that whether the first application is same application with the second application；Described second application is third-party application；
Second judge module, for when the first application is not same application with the second application, it is judged that the second application is
No in blacklist, if second applies in blacklist, then No starting second is applied.
Further, described first judge module, it is additionally operable to:
When the first application is same application with the second application, start the second application to use described destination service.
Further, described second judge module, it is additionally operable to:
If the second application is not in blacklist, then start the second application to use described destination service.
Further, described device, also include:
Blacklist acquisition module, for receiving what user chose from the third-party application downloaded by user setup interface
Application, joins in blacklist.
Further, described first judge module, it is additionally operable to:
Before judging whether the first application is same application with the second application, first judge that described first application is system
Application or third-party application, when judging that described first application is third-party application, then judge the first application and the second application
Whether it is same application.
Using technique scheme, the present invention at least has the advantage that
The method and device that restriction third-party application of the present invention mutually starts, can apply to Android system
In terminal, by judging the source of the application of startup destination service and forbidding that user undesirably runs through blacklist examination
Third-party application on backstage stealthily startup optimization, can effectively solve terminal running background and apply the terminal operating caused more
Card, slack-off problem.
Accompanying drawing explanation
Fig. 1 be first embodiment of the invention limit the method flow diagram that mutually starts of third-party application；
Fig. 2 be second embodiment of the invention limit the method flow diagram that mutually starts of third-party application；
Fig. 3 be third embodiment of the invention limit the method flow diagram that mutually starts of third-party application；
Fig. 4 be fourth embodiment of the invention limit the method flow diagram that mutually starts of third-party application；
Fig. 5 is the device composition structural representation that the third-party application of fifth embodiment of the invention mutually starts；
Fig. 6 is the device composition structural representation that the third-party application of sixth embodiment of the invention mutually starts；
Fig. 7 is the user setup interface schematic diagram of tenth embodiment of the invention；
Fig. 8 is that the restriction application of tenth embodiment of the invention mutually starts logic flow schematic diagram.
Detailed description of the invention
By further illustrating the technological means and effect that the present invention taked by reaching predetermined purpose, below in conjunction with accompanying drawing
And preferred embodiment, after the present invention is described in detail such as.
First embodiment of the invention, a kind of limits the method that third-party application mutually starts, as it is shown in figure 1, include following
Concrete steps:
Step S101, when the first application starts destination service, if the application belonging to described destination service is the second application,
Judge whether the first application is same application with the second application；Described second application is third-party application.
Concrete, the situation that the embodiment of the present invention belongs to third-party application only for the destination service started is judged,
If the destination service started belongs to system application, then directly initiate destination service, it is not necessary to do further judgement and process.
Step S102, when the first application is not same application with the second application, it is judged that whether the second application is in black name
Dan Zhong, if second applies in blacklist, then No starting second is applied.
Concrete, the acquisition mode of the application in described blacklist, including:
Receive, by user setup interface, the application that user chooses from the third-party application downloaded, join blacklist
In.
Second embodiment of the invention, a kind of limits the method that third-party application mutually starts, method described in the present embodiment with
First embodiment is roughly the same, and difference is, as in figure 2 it is shown, in the described method of the present embodiment, step S102 (in fig. 2 by
Step S102-a labelling), also include:
When the first application is same application with the second application, start the second application to use described destination service.
Concrete, if it is determined that going out the first application with the second application is same application in the embodiment of the present invention, then illustrate not
There is situation about starting mutually between application, the simply service of an application call self, the embodiment of the present invention is to this situation also
It is not added with intervening, but directly initiates destination service.
Third embodiment of the invention, a kind of limits the method that third-party application mutually starts, method described in the present embodiment with
First embodiment is roughly the same, and difference is, as it is shown on figure 3, in the described method of the present embodiment, step S102 (in figure 3 by
Step S102-b labelling), also include:
If the second application is not in blacklist, then start the second application to use described destination service.
Fourth embodiment of the invention, a kind of limits the method that third-party application mutually starts, method described in the present embodiment with
First embodiment is roughly the same, and difference is, as shown in Figure 4, in the described method of the present embodiment, step S101 (in the diagram by
Step S101-a labelling), also include:
Before judging whether the first application is same application with the second application, first judge that described first application is system
Application or third-party application, when judging that described first application is third-party application, then judge the first application and the second application
Whether it is same application.
Fifth embodiment of the invention, corresponding with first embodiment, it is mutual that the present embodiment introduces one restriction third-party application
The device started, as it is shown in figure 5, include consisting of part:
First judge module 501, is used for when the first application starts destination service, if the application belonging to described destination service
It is the second application, it is judged that whether the first application is same application with the second application；Described second application is third-party application；
Second judge module 502, for when the first application is not same application with the second application, it is judged that the second application
Whether in blacklist, if second applies in blacklist, then No starting second is applied.
Sixth embodiment of the invention, a kind of limits the device that third-party application mutually starts, method described in the present embodiment with
5th embodiment is roughly the same, and difference is, as shown in Figure 6, the described device of the present embodiment, also include:
Blacklist acquisition module 503, selects from the third-party application downloaded for receiving user by user setup interface
The application taken, joins in blacklist.
Seventh embodiment of the invention, a kind of limits the device that third-party application mutually starts, method described in the present embodiment with
5th embodiment is roughly the same, and difference is, the first judge module 501 in the described device of the present embodiment, is additionally operable to:
When the first application is same application with the second application, start the second application to use described destination service.
Eighth embodiment of the invention, a kind of limits the device that third-party application mutually starts, method described in the present embodiment with
5th embodiment is roughly the same, and difference is, the second judge module 502 in the described device of the present embodiment, is additionally operable to:
If the second application is not in blacklist, then start the second application to use described destination service.
Ninth embodiment of the invention, a kind of limits the device that third-party application mutually starts, method described in the present embodiment with
5th embodiment is roughly the same, and difference is, the first judge module 501 in the described device of the present embodiment, is additionally operable to:
Before judging whether the first application is same application with the second application, first judge that described first application is system
Application or third-party application, when judging that described first application is third-party application, then judge the first application and the second application
Whether it is same application.
Tenth embodiment of the invention, the present embodiment is on the basis of above-described embodiment, as a example by android mobile phone, knot
Close accompanying drawing 7～8 and introduce the application example of a present invention.
The technical scheme general design idea of the embodiment of the present invention is: add No starting user according to man machine interface black
After list, system will perform the startup logic to application according to this blacklist.
The method that mutually starts of third-party application that limits of the embodiment of the present invention is divided into two parts:
Part I: the foundation of blacklist
As it is shown in fig. 7, provide the user a user setup interface, enter particular by adding " blacklist " in arranging
Mouth realizes, and after user selects, the interface that calling system provides, the restriction application that list is passed to system is mutually opened
Dynamic logic.
Part II: the restriction application of system mutually starts logic
As shown in Figure 8, the restriction application mutually startup logic of this system comprises the following steps:
Step 1, starts source and starts destination service.Startup source is the application starting destination service.
Step 2, Android system adds the inspection in startup source starting when source starts destination service, check that startup source is
The no system for Android system is applied, the most then perform step 5, otherwise perform step 3.
Step 3, it is judged that whether the application belonging to startup source and described destination service is same application, if then performing step
Rapid 5, otherwise perform step 4.
Step 4, it is judged that the application belonging to described destination service whether in blacklist, the most then performs step 6, otherwise
Perform step 5.
Step 5, starts the application belonging to described destination service.
Step 6, application belonging to destination service described in No starting.
The embodiment of the present invention is mainly by providing user's human-computer interaction interface to arrange blacklist, and then system is by this list
Limiting being actuated for before these application mutually, the application reaching undesirably to run user carries out limiting the mesh run
's.Can effectively solve the android mobile phone running background Mobile phone card that causes of application more pause, slack-off problem.
By the explanation of detailed description of the invention, it should the technological means that the present invention can be taked by reaching predetermined purpose and
Effect is able to more deeply and concrete understanding, but appended diagram is only to provide reference and purposes of discussion, is not used for this
Invention is any limitation as.
Claims (10)
1. one kind limits the method that third-party application mutually starts, it is characterised in that including:
When the first application starts destination service, if the application belonging to described destination service is the second application, it is judged that the first application
Whether it is same application with the second application；Described second application is third-party application；
When the first application is not same application with the second application, it is judged that whether the second application is in blacklist, if second should
Be used in blacklist, then No starting second is applied.
The method that restriction third-party application the most according to claim 1 mutually starts, it is characterised in that described method is also wrapped
Include:
When the first application is same application with the second application, start the second application to use described destination service.
The method that restriction third-party application the most according to claim 1 mutually starts, it is characterised in that described method is also wrapped
Include:
If the second application is not in blacklist, then start the second application to use described destination service.
The method that restriction third-party application the most according to claim 1 mutually starts, it is characterised in that in described blacklist
The acquisition mode of application, including:
Receive, by user setup interface, the application that user chooses from the third-party application downloaded, join in blacklist.
5. the method mutually started according to the restriction third-party application according to any one of Claims 1 to 4, it is characterised in that
Described method, also includes:
Before judging whether the first application is same application with the second application, first judge that described first application is system application
Or third-party application, when judging that described first application is third-party application, then judges whether the first application applies with second
It it is same application.
6. one kind limits the device that third-party application mutually starts, it is characterised in that including:
First judge module, for when the first application starts destination service, if the application belonging to described destination service is second
Application, it is judged that whether the first application is same application with the second application；Described second application is third-party application；
Second judge module, for when the first application is not same application with the second application, it is judged that whether the second application exists
In blacklist, if second applies in blacklist, then No starting second is applied.
The device that restriction third-party application the most according to claim 6 mutually starts, it is characterised in that described first judges
Module, is additionally operable to:
When the first application is same application with the second application, start the second application to use described destination service.
The device that restriction third-party application the most according to claim 6 mutually starts, it is characterised in that described second judges
Module, is additionally operable to:
If the second application is not in blacklist, then start the second application to use described destination service.
The device that restriction third-party application the most according to claim 6 mutually starts, it is characterised in that described device, also
Including:
Blacklist acquisition module, should for chosen from the third-party application downloaded by user setup interface reception user
With, join in blacklist.
10. the device mutually started according to the restriction third-party application according to any one of claim 6～9, it is characterised in that
Described first judge module, is additionally operable to:
Before judging whether the first application is same application with the second application, first judge that described first application is system application
Or third-party application, when judging that described first application is third-party application, then judges whether the first application applies with second
It it is same application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610617524.4A CN106095520A (en) | 2016-08-01 | 2016-08-01 | A kind of limit the method and device that third-party application mutually starts |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610617524.4A CN106095520A (en) | 2016-08-01 | 2016-08-01 | A kind of limit the method and device that third-party application mutually starts |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106095520A true CN106095520A (en) | 2016-11-09 |
Family
ID=57479882
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610617524.4A Pending CN106095520A (en) | 2016-08-01 | 2016-08-01 | A kind of limit the method and device that third-party application mutually starts |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106095520A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109284040A (en) * | 2018-08-28 | 2019-01-29 | 珠海格力电器股份有限公司 | Application management method, device and terminal and computer storage medium |
| CN110489171A (en) * | 2018-05-11 | 2019-11-22 | 珠海市魅族科技有限公司 | Method for controlling mobile terminal, mobile terminal and storage medium |
| CN110580179A (en) * | 2018-05-21 | 2019-12-17 | 中国移动通信有限公司研究院 | information processing method and device, electronic device and storage medium |
| CN114528033A (en) * | 2020-11-03 | 2022-05-24 | 成都鼎桥通信技术有限公司 | Control method, control device, electronic device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140257903A1 (en) * | 2013-03-08 | 2014-09-11 | Art2Wave Inc. | Scheduling system |
| CN104462980A (en) * | 2014-12-30 | 2015-03-25 | 北京奇虎科技有限公司 | Authority management method, device and system of application programs and mobile terminal |
| CN104915224A (en) * | 2015-04-24 | 2015-09-16 | 青岛海信电器股份有限公司 | Processing method and device of affiliate application |
| CN105446811A (en) * | 2015-12-30 | 2016-03-30 | 广东欧珀移动通信有限公司 | Application process associated starting method and associated starting apparatus |
-
2016
- 2016-08-01 CN CN201610617524.4A patent/CN106095520A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140257903A1 (en) * | 2013-03-08 | 2014-09-11 | Art2Wave Inc. | Scheduling system |
| CN104462980A (en) * | 2014-12-30 | 2015-03-25 | 北京奇虎科技有限公司 | Authority management method, device and system of application programs and mobile terminal |
| CN104915224A (en) * | 2015-04-24 | 2015-09-16 | 青岛海信电器股份有限公司 | Processing method and device of affiliate application |
| CN105446811A (en) * | 2015-12-30 | 2016-03-30 | 广东欧珀移动通信有限公司 | Application process associated starting method and associated starting apparatus |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110489171A (en) * | 2018-05-11 | 2019-11-22 | 珠海市魅族科技有限公司 | Method for controlling mobile terminal, mobile terminal and storage medium |
| CN110580179A (en) * | 2018-05-21 | 2019-12-17 | 中国移动通信有限公司研究院 | information processing method and device, electronic device and storage medium |
| CN109284040A (en) * | 2018-08-28 | 2019-01-29 | 珠海格力电器股份有限公司 | Application management method, device and terminal and computer storage medium |
| CN109284040B (en) * | 2018-08-28 | 2020-08-11 | 珠海格力电器股份有限公司 | Application management method, device and terminal and computer storage medium |
| CN114528033A (en) * | 2020-11-03 | 2022-05-24 | 成都鼎桥通信技术有限公司 | Control method, control device, electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106095520A (en) | A kind of limit the method and device that third-party application mutually starts | |
| CN108268024B (en) | Vehicle diagnosis method, device, terminal and computer-readable storage medium | |
| CN102779255B (en) | Method and device for judging malicious program | |
| CN105528225A (en) | Application loading method and loading apparatus | |
| CN108521644B (en) | Network access method, equipment and system | |
| CN105824664B (en) | Application program launching monitoring method, device and terminal device | |
| CN103596246B (en) | Recover the method and terminal of data service | |
| CN103226491B (en) | A kind of method and device that Application Status are set | |
| CN102946486A (en) | Background application automatic clearing method based on mobile phone and mobile phone | |
| CN105912925B (en) | A kind of forbidden moves terminal installs the method and system of related application automatically | |
| CN104809589A (en) | Order processing method and device | |
| CN104134036B (en) | Method and device for obtaining Root permission | |
| CN104021336A (en) | Information processing method and device | |
| CN107105415B (en) | System and method for vehicle-mounted equipment user registration and equipment binding | |
| CN103885873A (en) | Automated integration testing method | |
| CN105101162A (en) | Method and device for automatically loading MBN (ModemConfiguration Binary File) | |
| CN103065083A (en) | Method and system for monitoring application program interface of intelligent mobile terminal | |
| CN104936157A (en) | Mobile phone number bound account acquisition method and system | |
| CN102999252A (en) | Application preloading method, device and terminal for unlocking interface | |
| CN103220662B (en) | A kind of processing method of application program and mobile terminal | |
| CN105893019A (en) | User manual calling-out method and apparatus for smartphone | |
| CN106709337A (en) | Malicious bundled software processing method and apparatus | |
| CN104636249A (en) | Generation system and method of debugging information of application program | |
| CN113609417A (en) | Method, device, equipment and medium for processing mobile terminal page | |
| CN105848254B (en) | The control method and system of roaming data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20161109 |