CN107784227A - Onboard system applies guard method and device - Google Patents

Onboard system applies guard method and device Download PDF

Info

Publication number
CN107784227A
CN107784227A CN201711168780.0A CN201711168780A CN107784227A CN 107784227 A CN107784227 A CN 107784227A CN 201711168780 A CN201711168780 A CN 201711168780A CN 107784227 A CN107784227 A CN 107784227A
Authority
CN
China
Prior art keywords
application
list
onboard system
killed
value
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
Application number
CN201711168780.0A
Other languages
Chinese (zh)
Inventor
胡仲阳
王辉耀
方杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Water World Co Ltd
Original Assignee
Shenzhen Water World Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Water World Co Ltd filed Critical Shenzhen Water World Co Ltd
Priority to CN201711168780.0A priority Critical patent/CN107784227A/en
Publication of CN107784227A publication Critical patent/CN107784227A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/51Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Storage Device Security (AREA)

Abstract

Guard method and device are applied present invention is disclosed a kind of onboard system, wherein method includes:Onboard system reaches the condition of cleaning background application, starts the program for killing application;Obtain running background application, the background application belonged on default white list is placed in first list, the background application that will not belong on white list is placed in second list, white list refer to can not killed application list;Abandon killing the application in first list.Onboard system of the invention applies guard method and device, and the application for running onboard system is excessive and needs are killed when applying, and ensures that core application will not be killed.

Description

Onboard system applies guard method and device
Technical field
The present invention relates to onboard system to use field, and especially relate to onboard system applies guard method and dress Put.
Background technology
With the development of society, the living standard more and more higher of people, the functional requirement to automobile is also more and more diversified. The onboard system of present automobile typically uses android system, there is many applications in onboard system, including most basic navigation, Radio, air-conditioning, the in-car entertainment activity of also abundant people have audio player, video player, DVD player, bluetooth etc., The various applications such as the reverse image of driving are also aided in, are onboard system control.
Android system has a kind of OOM KILLER mechanism, and it can enable oneself in the case where Installed System Memory exhausts Algorithm, to operating each application generation oom_adj values, the value is directly proportional with the internal memory of occupancy, then that oom_adj values is inclined The kill (kill) of high application selectivity falls, and is running memory vacating space, avoids low memory and system occur can not add The failures such as load.And on this basis, it is easy to some important applications of kill, bad experience is brought to user.
The content of the invention
The main object of the present invention applies guard method and device for a kind of onboard system of offer, protects onboard system Core application, system is avoided to be killed when clearing up automatically.
In order to realize foregoing invention purpose, the present invention proposes a kind of guard method of applying of onboard system, including step:
Onboard system reaches the condition of cleaning background application, starts the program for killing application;
The application of running background is obtained, the background application belonged on default white list is placed in first list, will The background application being not belonging on white list is placed in second list, white list refer to can not killed application list;
Abandon killing the application in first list.
Further, the condition of the onboard system cleaning background application, including:
The CPU of onboard system runtime value is higher than the first preset value.
Further, the background application that will not belong on white list is wrapped after being placed on the step in second list Include:
The application in second list is killed according to default rule.
Further, it is described according to default rule kill second list on application the step of include:
The adj values respectively applied in the second list are obtained, wherein, the adj values represent the killed preferential system of application Number;
The application in the second list is killed successively according to the order of adj values from high to low, until CPU runtime value is small When default second preset value, stop the program for killing application.
Further, the acquisition methods of the adj values, including:
According to the run time and frequency of application, adjusted value is generated;
Adjusted value is multiplied by default weight coefficient corresponding to the application, draws the adj values.
The present invention also proposes a kind of application protection device of onboard system, including:
Starting module, the condition of cleaning background application is reached for onboard system, start the program for killing application;
Acquisition module, for obtaining the application of running background, the background application belonged on white list is placed on first In list, the background application that will not belong on white list is placed in second list, and white list refers to killed to apply List;
Module is abandoned, for abandoning killing the application in first list.
Further, the starting module includes:
Value cell is run, for judging that the CPU runtime value of onboard system is higher than the first preset value.
Further, the application protection device of the onboard system also includes:
Module is killed, for killing the application in second list according to default rule.
Further, the kill module includes:
Preferred number unit, for obtaining the adj values respectively applied in the second list, wherein, the adj values represent should With killed preferred number;
Unit is killed, for killing the application in the second list successively according to the order of adj values from high to low, until When CPU runtime value is less than default second preset value, stop the program for killing application.
Further, the preferred number unit includes:
Adjusted value subelement, for the run time and frequency according to application, generate adjusted value;
Weight subelement, default weight coefficient corresponding to the application is multiplied by for adjusted value, draws the adj values.
Compared with prior art, the beneficial effects of the invention are as follows:The application of onboard system operation is excessive and needs kill should Important application is protected guarantee in advance and is not killed by used time, user.The application being not protected is arranged according to significance level Sequence, unessential application is preferentially killed, preferably experienced to user.The application being not protected is set into weight coefficient, optimization is killed Stubbornly refuse the sequencing of protected application.
Brief description of the drawings
Fig. 1 is the onboard system of one embodiment of the invention using guard method schematic flow sheet;
Fig. 2 is the onboard system of one embodiment of the invention using guard method schematic flow sheet;
Fig. 3 is the onboard system of one embodiment of the invention using guard method schematic flow sheet;
Fig. 4 is the onboard system of one embodiment of the invention using guard method schematic flow sheet;
Fig. 5 is the application protection device structural representation of the onboard system of one embodiment of the invention;
Fig. 6 is the application protection device structural representation of the onboard system of one embodiment of the invention;
Fig. 7 is the application protection device structural representation of the onboard system of one embodiment of the invention;
Fig. 8 is the structural representation of the kill module using protection device of the onboard system of one embodiment of the invention;
Fig. 9 is the structural representation of the preferred number unit using protection device of the onboard system of one embodiment of the invention Figure.
The realization, functional characteristics and advantage of the object of the invention will be described further referring to the drawings in conjunction with the embodiments.
Embodiment
It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, it is not intended to limit the present invention.
Reference picture 1, the embodiment of the present invention provide a kind of guard method of applying of onboard system, including step:
S1, onboard system reach the condition of cleaning background application, start the program for killing application;
S2, the application for obtaining running background, the background application belonged on white list is placed in first list, will not The background application belonged on white list is placed in second list, white list refer to can not killed application title list;
S3, abandon killing the application in first list.
In the present embodiment, when onboard system run or reach cleaning background application condition, influenceing onboard system just Often use, be triggered to trigger mechanism, than if desired for when the low memory of onboard system, system is killed with regard to automatic start and applied Program, discharge running memory, it is ensured that onboard system have abundance running memory.But because the application having is heavier Will, user needs important application real time execution, is reluctant to be killed.White list is exactly the inventory of the name of these important applications, When starting the program for killing application, the program of running background is compared with white list one by one, if background application is white On list, then it is placed in first list, if background application is placed in second list not on white list, therefore starts and kill Killed application is placed in first list after dead program, then the application in the list is abandoned killing.
Reference picture 2, further, the condition of the onboard system cleaning background application, including:
S11, the CPU runtime value of onboard system are higher than the first preset value.
In the present embodiment, CPU runtime value, refer to the ratio for the running memory that CPU takes, if CPU runtime values are too high, surpass Go out the size of running memory, internal memory can be caused to overflow, whole application exception, in some instances it may even be possible to allow whole system to collapse.Set First preset value, such as the first preset value are arranged to 85%, when the ratio of the running memory of CPU occupancy is higher than 85%, explanation System may collapse, thus send the signal for killing application, mitigate CPU operation, running memory is discharged space, protect Hinder the normal operation of whole onboard system.If CPU is less than the first preset value, illustrates the load for being also not reaching to saturation, also fill The running memory space of foot, it can also continue to open application, application need not be killed.
Reference picture 3, further, the background application that will not belong on white list are placed on the step in second list Also include afterwards:
S4, according to default rule kill second list on application.
In the present embodiment, after CPU runtime value is higher, it is necessary to kill the application that can be killed.According to user not Same demand, different rules is set to kill the application in second list.Specifically, such as kill all should in second list With, or kill the application of the internal memory half in the top in second list.Its default rule purpose is for guarantee and killed Before onboard system is returned to trigger mechanism after dead application, allow onboard system can be with normal use.
Reference picture 4, further, described killed according to default rule include in second list using the step of S4:
S41, the adj values respectively applied in the second list are obtained, wherein, the adj values represent that application is killed excellent First coefficient;
S42, application in the second list is killed according to the order of adj values from high to low successively, until CPU operation When value is less than default second preset value, stop the program for killing application.
Wherein, step S42 detailed process is:
S421, after killing the application of adj values highest, obtain CPU current runtime value;
S422, judge whether current runtime value is higher than the second preset value, if so, then return to step S421;
S423, if it is not, stop it is described kill application program.
In the present embodiment, adj values with can be with killed rank positive correlation.Using more inessential, the rank that can be killed is got over It is high.Adj values are higher, should using it is fewer.If some using time it is very long, the adj values that generate can relatively It is low, it is more likely that to be the application that user needs to be commonly used, if will cross meeting user after its kill and opened the application again, obtained Mistake is not repaid, therefore is killed successively from high to low according to the adj values of application, and the process priority for making often not apply is killed.This hair Bright purpose is to kill unessential application after the runtime value of onboard system is too high, ensures the stable fortune of whole onboard system OK.Therefore during application is killed, CPU current runtime value is also monitored in real time, if kill will be applied very low to CPU When, onboard system also be able to need not just be killed with very outstanding quickly state operation, then remaining application.Kill application Make runtime value low to can ensure that onboard system quickly runs.Its second preset value is that quickly operation is run system with non-rapid Critical value, thus the second preset value is lower than the first preset value, such as it is arranged to 40%.Therefore adj value highest applications are killed Afterwards, CPU runtime value is also obtained, judges whether runtime value is less than the second preset value, if after killing an application, CPU runtime value is 50%, then continues to kill the application that adj values are number two, if killing the application that adj values are number two Afterwards, CPU runtime value is 35%, less than the second preset value, then stops killing application, onboard system continues normal operation.Need It should be noted that kill adj values highest application after, in second list the application be just not present, in original second list The high application of adj values second is just updated to adj value highest applications, therefore is killed successively according to the height of adj values, according to the stream Journey always kills adj values highest application in current second list.
Further, the acquisition process of the adj values includes:
According to the run time and frequency of application, adjusted value is generated;
Adjusted value is multiplied by default weight coefficient corresponding to the application, draws the adj values.
In the present embodiment, although because the time of some applications operation is short, and it is not in white list, is again Important, user is not intended to this application can be compared this in system using setting in advance by preferential kill, user Low weight coefficient so that although time short frequency that the application uses is low, but its adj value is still than relatively low.Also have Although using using relatively frequently, inessential for user, user wishes that this application is prior by preferential kill, user Higher weight coefficient is set to the application in system.For example, user likes listening to radio, by this application of radio Weight coefficient be arranged to 0.5, user is very familiar to road conditions, less using navigation, by the weight system for this application of navigating Number is arranged to 1.5.After onboard system operation a period of time, CPU runtime value is higher, it is necessary to kill some applications.Radio and Navigation is not the run time that system is applied according to the two and the conventional frequency used, to calculate receipts in white list The importance value of sound machine is 100, and then with 50 weight coefficients 0.5 for being multiplied by radio, the adj values for drawing radio are 50;Simultaneously The importance value for calculating navigation is 80, and then with 80 weight coefficients 1.5 for being multiplied by navigation, the adj values for drawing navigation are 120.System System is preferential to kill the higher navigation application of adj values when killing application program.
In summary, the application guard method of onboard system of the invention, the application of onboard system operation is excessive and needs When killing application, important application is protected guarantee in advance and is not killed by user.The adj values of inessential application are obtained, it is excellent Unessential application is first killed, is preferably experienced to user.Will be not protected application set weight coefficient, optimization kill not by The sequencing of the application of protection.
Reference picture 5-9, the present invention also propose the application protection device of the onboard system of an embodiment, including:
Starting module 1, the condition of cleaning background application is reached for onboard system, start the program for killing application;
Acquisition module 2, for obtaining the application of running background, the background application belonged on white list is placed on first In list, the background application that will not belong on white list is placed in second list, and white list refers to killed to apply Title list;
Module 3 is abandoned, for abandoning killing the application in first list.
In the present embodiment, when onboard system run or reach cleaning background application condition, influenceing onboard system just Often use, be triggered to trigger mechanism, than if desired for when the low memory of onboard system, starting module 1 is killed with regard to automatic start The program extremely applied, discharges running memory, it is ensured that onboard system has the running memory of abundance.But because the application having is ratio More important, user needs important application real time execution, is reluctant to be killed.White list is exactly the clear of the name of these important applications Single, when starting the program for killing application, the program of running background is compared acquisition module 2 with white list one by one, if Background application is then placed in first list on white list, if background application is placed on second list not on white list It is interior, therefore killed application is placed in first list by acquisition module 2 after startup kill program, and then abandon module Application in 3 pairs of lists is abandoned killing, and plays a part of protecting the application.
Further, the starting module 1 includes:
Value cell 11 is run, for judging that the CPU runtime value of onboard system is higher than the first preset value.
In the present embodiment, CPU runtime value refers to the ratio for the running memory that CPU takes, and is obtained if running value cell 11 CPU runtime values it is too high, beyond the size of running memory, internal memory can be caused to overflow, whole application exception, in some instances it may even be possible to allow Whole system is collapsed.Set the first preset value, such as the first preset value to be arranged to 85%, make the ratio of the running memory of CPU occupancy When example is higher than 85%, explanation system may collapse, thus issue unit 12 sends the signal for killing application, mitigates CPU fortune OK, running memory is discharged space, ensure the normal operation of whole onboard system.If CPU is less than the first preset value, explanation The load of saturation is also not reaching to, also has sufficient running memory space, can also continue to open application, need not kill should With.
Further, the application protection device of the onboard system also includes:
Module 4 is killed, for killing the application in second list according to default rule.
In the present embodiment, after CPU runtime value is higher, it is necessary to kill module 4 and kill the application that can be killed.According to The different demands of user, different rules is set to kill the application in second list.Specifically, such as kill in second list All applications, or kill the application of the internal memory half in the top in second list.Its default rule purpose is for Before onboard system is returned to trigger mechanism after guarantee kill application, allow onboard system can be with normal use.
Further, the kill module 4 includes:
Preferred number unit 41, for obtaining the adj values respectively applied in the second list, wherein, the adj values represent Using killed preferred number;
Unit 42 is killed, for killing the application in the second list successively according to the order of adj values from high to low, directly When being less than default second preset value to CPU runtime value, stop the program for killing application.
Wherein, killing unit 42 includes:
Highest subelement 421 is killed, after killing the application of adj values highest, obtains CPU current runtime value;
Judgment sub-unit 422, for judging whether current runtime value is higher than the second preset value;
First judges subelement 423, if being higher than the second preset value for current runtime value, calls and kills unit 42;
Second judges subelement 424, if being not higher than the second preset value for current runtime value, stops the kill application Program.
In the present embodiment, adj values with can be with killed rank positive correlation.Using more inessential, the rank that can be killed is got over High adj values are higher, should using it is fewer.If some using time it is very long, the adj values that generate can relatively It is low, it is more likely that to be the application that user needs to be commonly used, if will cross meeting user after its kill and opened the application again, obtained Do not repay mistake, therefore kill adj value kill from high to low of the unit 42 according to application, the process priority for making often not apply is killed Extremely.The purpose of the present invention is to kill unessential application after the runtime value of onboard system is too high, ensures whole onboard system Stable operation.Therefore during application is killed, CPU current operation will also be obtained in real time by killing highest subelement 421 Value, at the same judgment sub-unit 422 judge current runtime value whether less than ensure onboard system it is outstanding quickly run it is second pre- If value, if will apply kill to CPU it is very low when, second judges that subelement 424 judges CPU current runtime value less than or equal to pre- If value, onboard system is set also need not just to be killed with very outstanding quickly state operation, then remaining application, therefore Second judges that subelement 424 stops killing the program of application.Killing application makes runtime value low to can ensure that onboard system is quick Operation.Its second preset value is the system critical value that quickly operation is run with non-rapid, thus the second preset value is more default than first Value is low, such as is arranged to 40%.Therefore after killing the application of adj values highest, CPU runtime value is also obtained, is judged sub single Member 422 judges whether runtime value is less than the second preset value, if after killing an application, CPU runtime value is 50%, then First judgement subelement 423 judges be higher than the second preset value, calls and kills highest subelement 421 and continue kill adj values ranking the Two application, if after killing the application that adj values are number two, CPU runtime value is 35%, and second judges subelement 424 Judge that runtime value is less than the second preset value, then stop killing application, onboard system continues normal operation.It should be noted that Kill adj values highest application after, in second list the application be just not present, adj values second are high in original second list Application be just updated to adj value highest applications, therefore kill according to the height of adj values, always killed according to the flow successively Adj value highest applications in current second list.
Further, the preferred number unit 41 includes:
Adjusted value subelement 411, for the run time and frequency according to application, generate adjusted value;
Weight subelement 412, default weight coefficient corresponding to the application is multiplied by for adjusted value, draws the adj values.
In the present embodiment, although because the time of some applications operation is short, and it is not in white list, is again Important, user is not intended to this application can be compared this in system using setting in advance by preferential kill, user Low weight coefficient so that although time short frequency that the application uses is low, but its adj value is still than relatively low.Also have Although using using relatively frequently, inessential for user, user wishes that this application is prior by preferential kill, user Higher weight coefficient is set to the application in system.For example, user likes listening to radio, by this application of radio Weight coefficient be arranged to 0.5, user is very familiar to road conditions, less using navigation, by the weight system for this application of navigating Number is arranged to 1.5.After onboard system operation a period of time, CPU runtime value is higher, it is necessary to kill some applications.Radio and Navigation is not in white list, and importance value subelement 411 is according to the run time that the two are applied and the conventional frequency used Rate, the importance value for calculating radio are 100, and then 50 weight coefficients 0.5 for being multiplied by radio of weight subelement 412, are obtained The adj values for going out radio are 50;The importance value that importance value subelement 411 calculates navigation simultaneously is 80, then weight subelement 412 with 80 weight coefficients 1.5 for being multiplied by navigation, and the adj values for drawing navigation are 120.System is preferentially killed when killing application program The higher navigation application of dead adj values.
In summary, the application protection device of onboard system of the invention, the application of onboard system operation is excessive and needs When killing application, important application is protected guarantee in advance and is not killed by user.By the application being not protected according to important Degree sorts, and preferentially kills unessential application, is preferably experienced to user.The application being not protected is set into weight coefficient, The sequencing for the application being not protected is killed in optimization.
The preferred embodiments of the present invention are the foregoing is only, are not intended to limit the scope of the invention, every utilization The equivalent structure or equivalent flow conversion that description of the invention and accompanying drawing content are made, or directly or indirectly it is used in other correlations Technical field, be included within the scope of the present invention.

Claims (10)

1. a kind of onboard system applies guard method, it is characterised in that including step:
Onboard system reaches the condition of cleaning background application, starts the program for killing application;
The application of running background is obtained, the background application belonged on default white list is placed in first list, will not be belonged to Be placed in the background application on white list in second list, white list refer to can not killed application list;
Abandon killing the application in first list.
2. onboard system as claimed in claim 1 applies guard method, it is characterised in that the onboard system cleaning backstage The condition of application, including:
The CPU of onboard system runtime value is higher than the first preset value.
3. onboard system as claimed in claim 1 applies guard method, it is characterised in that described to will not belong on white list The step that is placed in second list of background application after include:
The application in second list is killed according to default rule.
4. onboard system as claimed in claim 3 applies guard method, it is characterised in that described to be killed according to default rule The step of application in dead second list, includes:
The adj values respectively applied in the second list are obtained, wherein, the adj values represent to apply killed preferred number;
The application in the second list is killed successively according to the order of adj values from high to low, until CPU runtime value is less than in advance If the second preset value when, stop it is described kill application program.
5. onboard system as claimed in claim 4 applies guard method, it is characterised in that the acquisition methods of the adj values, Including:
According to the run time and frequency of application, adjusted value is generated;
Adjusted value is multiplied by default weight coefficient corresponding to the application, draws the adj values.
A kind of 6. application protection device of onboard system, it is characterised in that including:
Starting module, the condition of cleaning background application is reached for onboard system, start the program for killing application;
Acquisition module, for obtaining the application of running background, the background application belonged on white list is placed on first list Interior, the background application that will not belong on white list is placed in second list, white list refer to can not killed application name It is single;
Module is abandoned, for abandoning killing the application in first list.
7. the application protection device of onboard system as claimed in claim 6, it is characterised in that the starting module includes:
Value cell is run, for judging that the CPU runtime value of onboard system is higher than the first preset value.
8. the application protection device of onboard system as claimed in claim 6, it is characterised in that also include:
Module is killed, for killing the application in second list according to default rule.
9. the application protection device of onboard system as claimed in claim 8, it is characterised in that the kill module includes:
Preferred number unit, for obtaining the adj values respectively applied in the second list, wherein, the adj values represent to apply quilt The preferred number of kill;
Unit is killed, for killing the application in the second list successively according to the order of adj values from high to low, until CPU Runtime value when being less than default second preset value, stop the program for killing application.
10. the application protection device of onboard system as claimed in claim 9, it is characterised in that the preferred number unit bag Include:
Adjusted value subelement, for the run time and frequency according to application, generate adjusted value;
Weight subelement, default weight coefficient corresponding to the application is multiplied by for adjusted value, draws the adj values.
CN201711168780.0A 2017-11-21 2017-11-21 Onboard system applies guard method and device Pending CN107784227A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711168780.0A CN107784227A (en) 2017-11-21 2017-11-21 Onboard system applies guard method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711168780.0A CN107784227A (en) 2017-11-21 2017-11-21 Onboard system applies guard method and device

Publications (1)

Publication Number Publication Date
CN107784227A true CN107784227A (en) 2018-03-09

Family

ID=61430841

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711168780.0A Pending CN107784227A (en) 2017-11-21 2017-11-21 Onboard system applies guard method and device

Country Status (1)

Country Link
CN (1) CN107784227A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109815054A (en) * 2019-01-11 2019-05-28 广州小鹏汽车科技有限公司 A kind of vehicle entertainment system fault recovery method and device

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104298613A (en) * 2014-09-29 2015-01-21 广州金山网络科技有限公司 Method for cleaning up system memory and terminal device
WO2016000544A1 (en) * 2014-06-30 2016-01-07 北京金山安全软件有限公司 Method of processing application cpu usage rate anomaly, and device and mobile terminal
CN106250216A (en) * 2016-07-21 2016-12-21 宇龙计算机通信科技(深圳)有限公司 A kind of method clearing up internal memory and terminal
CN106407010A (en) * 2016-09-06 2017-02-15 北京珠穆朗玛移动通信有限公司 Internal memory management method and mobile terminal
CN107220076A (en) * 2016-09-27 2017-09-29 华为技术有限公司 A kind of method for recovering internal storage and device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016000544A1 (en) * 2014-06-30 2016-01-07 北京金山安全软件有限公司 Method of processing application cpu usage rate anomaly, and device and mobile terminal
CN104298613A (en) * 2014-09-29 2015-01-21 广州金山网络科技有限公司 Method for cleaning up system memory and terminal device
CN106250216A (en) * 2016-07-21 2016-12-21 宇龙计算机通信科技(深圳)有限公司 A kind of method clearing up internal memory and terminal
CN106407010A (en) * 2016-09-06 2017-02-15 北京珠穆朗玛移动通信有限公司 Internal memory management method and mobile terminal
CN107220076A (en) * 2016-09-27 2017-09-29 华为技术有限公司 A kind of method for recovering internal storage and device

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109815054A (en) * 2019-01-11 2019-05-28 广州小鹏汽车科技有限公司 A kind of vehicle entertainment system fault recovery method and device

Similar Documents

Publication Publication Date Title
US10335690B2 (en) Automatic video game highlight reel
US20070005926A1 (en) Method for managing a memory in mobile terminal
US20090318235A1 (en) Game system, game terminal therefor, and server device therefor
US20230083591A1 (en) Vector-space framework for evaluating gameplay content in a game environment
CN110466525B (en) Uphill auxiliary control method, device, equipment and storage medium
CN107450985B (en) Memory management method, mobile terminal and storage medium
DE102015103999A1 (en) Load Estimation for Mobile Function Integration
CN107784227A (en) Onboard system applies guard method and device
CN113032268B (en) Software testing method, device and storage medium
CN104484038B (en) The control method and device of smart machine
CN110267718A (en) Game application activation system and method
CN112416549A (en) Process management method and device, electronic equipment and storage medium
US9089779B2 (en) Game control apparatus for a sacrifice command in a game
WO2019156751A1 (en) Identifying revevant gameplay content for a game environment usinbg a vector-space framework
JP5752839B1 (en) GAME PROVIDING DEVICE AND GAME PROVIDING DEVICE PROGRAM
JP2013015968A (en) Platform device, program, and system
CN111107429A (en) Method, apparatus and computer readable storage medium for improving performance of television system
CN108174245B (en) Method and system for presenting dynamic content based on video data
DE102015207652A1 (en) PROXY LIFE CYCLE MANAGEMENT FOR ONE VEHICLE
CN107741885A (en) Affairs and business association method, interconnected system based on CS frameworks
CN113082705A (en) Game scene switching method and device, computer equipment and storage medium
CN112887138A (en) Network equipment adding method, system, terminal and storage medium
KR101990100B1 (en) Server and method for providing tutorial contents
CN111013138A (en) Voice control method and device, electronic equipment and storage medium
JP3881361B1 (en) Sound output device, sound output method and program

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for 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: 20180309