CN107766177A - Boot optimization method, device, storage medium and terminal equipment - Google Patents

Abstract

The embodiments of the present application provide a method, device, storage medium and terminal device for boot optimization, which determine the boot-related file associated with the boot-up of the terminal device; when the system core process restart is detected, detect whether the boot-related file is damaged; if a damaged boot-related file is detected, perform exception processing on the damaged boot-related file. The embodiment of the present application has the advantage that the boot process can be optimized.

Description

Boot optimization method, device, storage medium and terminal equipment

technical field

The embodiments of the present application relate to the field of smart terminals, and in particular to a boot optimization method, device, storage medium, and terminal equipment.

Background technique

With the development of mobile smart terminal devices, the Android (Android) system has developed into a mainstream operating system in smart terminals. When the Android system is started, it is necessary to call the key files and configuration files associated with the system. These key files and configuration files are generally generated when the terminal device is used for the first time. In the subsequent startup process, the above key files and configuration files need to be called to achieve normal startup. If the system of the terminal device is not updated during subsequent use, or If the system settings are changed, the same key files and configuration files will be invoked every time the system is turned on.

The above-mentioned key files and configuration files are generally stored in the eMMC (Embedded Multi Media Card, embedded memory) of the smart terminal, and the above-mentioned key files and configuration files may be damaged when the smart terminal is used improperly. For example, eMMC will inevitably have bad blocks during use. Bad blocks refer to factors such as sudden power failure or external vibration during the reading and writing process of the storage device, which makes the magnetic head of the storage device more likely to scratch the medium. If the bad block happens to be where the above key files or configuration files are located, the configuration files will be damaged, which will cause the phone to fail to boot normally and affect the user's use, so it needs to be optimized.

Contents of the invention

Embodiments of the present application provide a boot optimization method, device, storage medium, and terminal device, which can optimize a boot process.

In the first aspect, the embodiment of the present application provides a startup optimization method, including:

Determine the boot associated file associated with the boot of the terminal device;

When it is detected that the system core process is restarted, it is detected whether the boot-related file is damaged;

If a damaged boot association file is detected, abnormal processing is performed on the damaged boot association file.

In the second aspect, the embodiment of the present application provides a boot optimization device, including:

A file determination module, configured to determine a boot-related file associated with the boot of the terminal device;

A damage detection module, configured to detect whether the boot-associated file is damaged when it is detected that the system core process restarts;

The exception processing module is used to perform abnormal processing on the damaged boot associated file if a damaged boot associated file is detected.

In a third aspect, the embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the boot optimization method as described in the embodiment of the present application is implemented.

In the fourth aspect, the embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the implementation of the present application is implemented. A startup optimization method described in the example.

In the boot optimization method provided in the embodiment of the present application, by determining the boot-related file associated with the boot of the terminal device; when the system core process is detected to be restarted, it is detected whether the boot-related file is damaged; if the damaged If there is no boot associated file, abnormal processing will be performed on the damaged boot associated file. In the embodiment of the present application, by detecting whether the system core process is restarted, it can be judged whether it is necessary to detect whether the boot-related file is damaged, so as to avoid the problem that the boot cannot be started due to the damage of the boot-related file. By adopting the above technical solution, the boot process can be optimized.

Description of drawings

FIG. 1 is a schematic flow chart of a startup optimization method provided in an embodiment of the present application;

FIG. 2 is a schematic flowchart of another boot optimization method provided in the embodiment of the present application;

FIG. 3 is a schematic flow chart of another startup optimization method provided by the embodiment of the present application;

FIG. 4 is a schematic diagram of the use of the boot command provided by the embodiment of the present application;

FIG. 5 is a structural block diagram of a boot optimization device provided in an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.

Detailed ways

The technical solution of the present application will be further described below in conjunction with the accompanying drawings and through specific implementation methods. It should be understood that the specific embodiments described here are only used to explain the present application, but not to limit the present application. In addition, it should be noted that, for the convenience of description, only some structures related to the present application are shown in the drawings but not all structures.

Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the steps as sequential processing, many of the steps may be performed in parallel, concurrently, or simultaneously. Additionally, the order of steps may be rearranged. The process may be terminated when its operations are complete, but may also have additional steps not included in the figure. The processing may correspond to a method, function, procedure, subroutine, subroutine, or the like.

Terminal devices include smartphones, tablets, and other Android-based terminal devices. When the terminal device starts up, it generally starts the system core process, and the system core process calls the boot-up associated file associated with the boot-up to complete the boot-up operation. If the boot-related file is abnormal or damaged, the system core process cannot call the boot-related file, and the boot operation cannot be completed.

Figure 1 is a schematic flowchart of a boot optimization method provided by an embodiment of the present invention. The method can be executed by a boot optimization device, wherein the device can be implemented by software and/or hardware, and generally can be integrated in a terminal device or can be integrated In other electronic devices installed with an operating system. As shown in Figure 1, the method includes:

S110. Determine a startup-associated file associated with startup of the terminal device.

Wherein, the start-up associated file may be a file called from system files when the terminal device starts up. The boot-associated file may include a boot-up key file and/or a boot-up configuration file. The boot-up key file includes a key file that needs to be invoked by a core service associated with boot-up. The core service includes a power management service, a sensor management service, Bluetooth management service, startup phone registration service and Activity management service, etc., the key files for startup are stored in the data/system directory. The boot configuration file includes the configuration file that needs to be read when booting, and the boot configuration file is stored in the data/property directory.

Among them, if the terminal device does not choose to update the system, or change the boot setting information of the system, the boot key file and boot configuration file called each time the terminal device is started are the same, so it can be counted every time the terminal device starts The boot-up key file and boot configuration file of the core service that will be called at time, and determined as the boot-up associated file. The start-up associated file may be a single file, or all files in a folder, and all the start-up associated files associated with the start-up of the terminal device shall be statistically determined.

S120. When it is detected that the system core process is restarted, detect whether the boot-related file is damaged.

Optionally, the system core process includes a system service process, such as a SystemServer process and/or a Zygote process. When the Android system starts, the first process to be started is the init process. The Zygote process is hatched from the init process. The Zygote process is the core of the Android system. Most of the application processes and system processes of the Android system are generated by the Zygote process. , including the SystemServer process. The Zygote process is the parent process of the SystemServer process. When the Android system is started, the SystemServer process is started by the Zygote process, and the SystemServer process calls the boot-related files, starts the key services of the system, and enters the normal boot operation. The SystemServer process is used to start various services of the system. All kinds of system services used by the user to use the terminal device are started in the system service process. If the application program (APP, Application) installed on the terminal device needs to use various system services , it is also necessary to obtain the handles of various service objects through communication with the system service process in order to perform corresponding operations. There are multiple system threads in the system service process, providing core services of all systems, including core services associated with booting.

When the core service in the SystemServer process starts up, it invokes the boot key file and the boot configuration file for booting. And if the called start-up key file or the start-up configuration file is damaged, it will cause the Zygote process or the SystemServer process to be "killed", that is, end the operation of the Zygote process or the SystemServer process. Among them, if the SystemServer process crashes abnormally and is "killed", the Zygote process will end its operation by itself. And if Zygote is "killed", it will also end the running of the SystemServer process. After the Zygote process or the SystemServer process is "killed", the Zygote process will restart and start the SystemServer process again. Therefore, if the system core process restarts, it means that there may be damaged files in the boot-related files. Therefore, when the restart of the system core process is detected, all the boot-related files determined by the detection are traversed to find the damaged boot-related files.

Optionally, when it is detected that the process identifier of the system core process changes, it is detected whether the boot-related file is damaged.

Wherein, a process identifier (PID, Process Identifier) is an identity when the process is running. When the process is running, the system will automatically assign a unique process identifier to the process. When the process finishes running, the process identifier previously used by the process will be reclaimed by the system, and may also be assigned to another new process.

The Zygote process or SystemServer process is initially started when the terminal device is turned on, and the system will assign a unique process identifier to the Zygote process or SystemServer process and store the process identifier. After the Zygote process or the SystemServer process is restarted, the system will assign a new process identifier to the Zygote process or the SystemServer process again. Therefore, by judging whether the process identifier of the Zygote process or the SystemServer process changes, it can be judged whether the system core process is restarted, and then it can be judged whether it is necessary to detect the boot-related files. By detecting whether the process identifier changes, it is possible to quickly detect whether the system core process is restarted without continuously detecting the working process of the system core process, which can improve detection efficiency.

Optionally, when the restart of the system core process is detected, the boot-related file is read and parsed to determine whether the boot-related file throws an exception; when the boot-related file throws an exception, it is determined to be damaged.

Wherein, throwing an exception (Throw Exception) is a program processing action in JAVA, that is, the function is compiled successfully, but cannot be executed, and it can be determined whether the boot-related file is damaged by throwing an exception. Read the boot-related file and analyze it to determine whether the boot-related file throws an exception. If an exception is thrown, it means that the boot-related file cannot be executed and is determined to be damaged.

S130. If a damaged boot-related file is detected, abnormal processing is performed on the damaged boot-related file.

Wherein, the exception handling may be repairing or rebuilding the damaged boot association file.

Optionally, the abnormal handling of the damaged boot association file includes:

Delete the damaged boot association file and regenerate it, or obtain a backup boot association file to replace the damaged boot association file.

Optionally, after the damaged boot association file is deleted and then regenerated, it can be regenerated through a system preset program after deleting the damaged boot association file, or can be regenerated by obtaining a corresponding service from a server through networking.

Optionally, obtaining a backup boot association file to replace a damaged boot association file may be obtained by obtaining a backup boot association file from a backup file stored in the system and replacing the damaged boot association file. Obtain the backup boot association file and replace it, and restore the boot association file when the system default program is damaged or the system cannot be connected to the Internet.

It should be noted that if the boot-related file is damaged due to a bad block in the eMMC, that is, the location where the original boot-related file is stored has been damaged, so after restoring the damaged boot-related file, the new boot-related file will be randomly stored. The new storage location on the eMMC, and the location of the bad block will no longer be stored.

Fig. 2 is a schematic flowchart of another startup optimization method provided by the embodiment of the present application. On the basis of the technical solution provided by the above embodiment, the method includes:

S110. Determine a startup-associated file associated with startup of the terminal device.

S120. When it is detected that the system core process is restarted, detect whether the boot-related file is damaged.

S130. If a damaged boot-related file is detected, abnormal processing is performed on the damaged boot-related file. Wherein, for specific implementation manners of the above operations, reference may be made to relevant descriptions above, and details are not repeated here.

S140. Report the damaged boot-related file to the background monitoring terminal.

Optionally, report the associated information of the damaged boot-associated file to the background monitoring terminal. The associated information includes the attribute information and damage-associated information of the boot-associated file, which may include the file name, storage directory, and damage exception handling information of the boot-associated file. . The relevant attribute information of the boot-associated file can be obtained through the file name and the storage directory of the boot-up file, and the location where the boot-associated file is damaged can be known through the damage exception processing information, and damage-associated information such as abnormal handling information used to restore the boot-associated file. And report the related information of the damaged boot-related files to the background monitoring terminal, so that the administrator of the background monitoring terminal can count the damage of the boot-related files, obtain the boot-related files that are more likely to be damaged during the boot process of the terminal device, and then assist in optimizing the system boot process.

Fig. 3 is a schematic flowchart of another startup optimization method provided by the embodiment of the present application. On the basis of the technical solution provided by the above embodiment, the method includes:

S100. Record the current time as the first boot time when the power-on instruction is received.

Wherein, the power-on command may be a received external power-on command, as shown in FIG. 4 , the user manually presses the power-on button to power on the terminal device and start the command. The boot command can also be an internal boot command, such as the automatic boot command set by the system. When the set condition is reached, the internal boot command will be issued to trigger the system boot. Record the time when the power-on instruction is received as the first power-on time, that is, the initial time of the power-on operation.

S110. Determine a startup-associated file associated with startup of the terminal device.

S120. When it is detected that the system core process is restarted, detect whether the boot-related file is damaged.

S130. If a damaged boot-related file is detected, abnormal processing is performed on the damaged boot-related file. Wherein, for specific implementation manners of the above operations, reference may be made to relevant descriptions above, and details are not repeated here.

S141. Monitor the system broadcast.

S142. Record the current time as the second power-on time when the start-up broadcast is heard.

S143. Report the damaged boot-related file, the first boot time, and the second boot time to the background monitoring terminal.

Optionally, report the associated information of the damaged boot-related file, the first boot time and the second boot time to the background monitoring terminal. Wherein, the associated information of the boot-associated file includes the attribute information and damage-associated information of the boot-associated file, and may include the file name, storage directory and damage exception handling information of the boot-associated file. The relevant attribute information of the boot-associated file can be obtained through the file name and the storage directory of the boot-up file, and the location where the boot-associated file is damaged can be known through the damage exception processing information, and damage-associated information such as abnormal handling information used to restore the boot-associated file.

Wherein, the start-up broadcast is a global start-up broadcast sent after the system start-up is completed, that is, after the start-up operation has been successfully completed. By monitoring the system broadcast, when the boot broadcast is heard, the current time is recorded as the second time, that is, the time when the boot operation is successfully completed. Through the first boot time and the second boot time, that is, the initial time of the boot operation and the time when the boot operation is successfully completed, the time consumed by the entire boot operation of the system this time can be determined, including the time consumed by the restart of the system core process time, the time consumed for detecting the boot-related files, the time consumed for abnormal processing of the boot-related files, and the time consumed for restarting after the boot-related files are restored. By reporting the associated information of the first boot time, the second boot time, and the boot associated file to the background monitoring terminal, the administrator of the background monitoring terminal can count the damage of the boot associated file and the corresponding boot time after the boot association is damaged. The time consumed by the operation can further assist the administrator to optimize the booting process of the system.

It should be noted that when a boot command is received, the execution sequence of the operation of recording the current time as the first boot time and determining the boot associated file associated with the boot of the terminal device is not limited to this, and may also be executed first Determine the operation of the boot-associated file associated with the boot-up of the terminal device.

FIG. 5 is a structural block diagram of a boot optimization device provided by an embodiment of the present application, and the device can execute a boot optimization method. As shown in Figure 5, the device includes:

A file determination module 210, configured to determine a boot-related file associated with the boot of the terminal device;

The damage detection module 220 is used to detect whether the boot-related file is damaged when it is detected that the system core process is restarted;

The abnormal processing module 230 is configured to perform abnormal processing on the damaged boot-related file if a damaged boot-related file is detected.

A boot optimization device provided in an embodiment of the present application determines whether the boot-related file associated with the boot of the terminal device is detected; when the system core process is restarted, detects whether the boot-related file is If there is no boot associated file, abnormal processing will be performed on the damaged boot associated file. The boot optimization device can judge whether it is necessary to detect whether the boot-related file is damaged by detecting whether the system core process is restarted, so as to avoid the problem that the boot cannot be started due to the damage of the boot-related file. By adopting the above technical solution, the boot process can be optimized.

Optionally, the damage detection module is specifically used for:

When it is detected that the process identifier of the system core process changes, it is detected whether the boot associated file is damaged.

Optionally, the damage detection module is specifically used for:

When it is detected that the system core process restarts, read and parse the boot-related file to determine whether the boot-related file throws an exception;

Optionally, the exception handling module is specifically used for:

Delete the damaged boot association file and regenerate it, or obtain a backup boot association file to replace the damaged boot association file.

Optionally, the boot optimization device also includes:

The first reporting module is used to report the damaged boot-related file to the background monitoring terminal.

Optionally, the boot optimization device also includes:

The first time determination module is used to record the current time as the first boot time when receiving the boot command;

The broadcast monitoring module is used to monitor the system broadcast;

The second time determination module is used to record the current time as the second power-on time when the start-up broadcast is heard;

The second reporting module is used to report the damaged boot-related file, the first boot time and the second boot time to the background monitoring terminal.

Optionally, the boot-associated file includes a boot-up key file and/or a boot-up configuration file;

Correspondingly, the system core process includes a system service process.

A storage medium containing computer-executable instructions provided in an embodiment of the present application, the computer-executable instructions are not limited to the boot optimization operation described above, and may also execute a boot optimization method provided in any embodiment of the present application related operations.

storage medium - any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media such as CD-ROMs, floppy disks or tape drives; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc. ; non-volatile memory, such as flash memory, magnetic media (eg hard disk or optical storage); registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. Also, the storage medium may be located in a first computer system in which the program is executed, or may be located in a different second computer system connected to the first computer system through a network such as the Internet. The second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations, such as in different computer systems connected by a network. The storage medium may store program instructions (eg embodied as computer programs) executable by one or more processors.

An embodiment of the present application provides a terminal device, and the terminal device can be integrated with a boot optimization device provided in the embodiment of the present application. FIG. 6 is a schematic structural diagram of a terminal device provided in an embodiment of the present application. As shown in Figure 6, the terminal device may include: a housing (not shown in the figure), a touch screen (not shown in the figure), a touch button (not shown in the figure), a memory 301, a central processing unit (Central Processing Unit, CPU) 302 (also known as processor, hereinafter referred to as CPU), a circuit board (not shown in the figure) and a power circuit (not shown in the figure). The circuit board is placed inside the space surrounded by the housing; the CPU 302 and the memory 301 are arranged on the circuit board; the power supply circuit is used to supply power to each circuit or device of the terminal device The memory 301 is used to store executable program codes; the CPU302 executes a computer program corresponding to the executable program codes by reading the executable program codes stored in the memory 301, to achieve the following steps:

Determine the boot associated file associated with the boot of the terminal device;

When it is detected that the system core process is restarted, it is detected whether the boot-related file is damaged;

If a damaged boot association file is detected, abnormal processing is performed on the damaged boot association file. The terminal device also includes: peripheral interface 303, RF (Radio Frequency, radio frequency) circuit 305, audio circuit 306, speaker 311, power management chip 308, input/output (I/O) subsystem 309, touch screen 312, other Input/control devices 310 and external ports 304 , these components communicate via one or more communication buses or signal lines 307 .

It should be understood that the illustrated terminal device 300 is only an example of a terminal device, and the terminal device 300 may have more or fewer components than those shown in the figure, and two or more components may be combined, Or can have a different component configuration. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.

The following describes in detail the terminal device used for optimizing booting provided by this embodiment, and the terminal device takes a mobile phone as an example.

Memory 301, the memory 301 can be accessed by the CPU 302, the peripheral interface 303, etc., the memory 301 can include a high-speed random access memory, and can also include a non-volatile memory, such as one or more disk storage devices, flash memory devices , or other volatile solid-state storage devices.

Peripheral interface 303 , which can connect the input and output peripherals of the device to CPU 302 and memory 301 .

The I/O subsystem 309 , the I/O subsystem 309 can connect input and output peripherals on the device, such as a touch screen 312 and other input/control devices 310 , to the peripheral interface 303 . I/O subsystem 309 may include a display controller 3091 and one or more input controllers 3092 for controlling other input/control devices 310 . Among them, one or more input controllers 3092 receive electrical signals from or send electrical signals to other input/control devices 310, which may include physical buttons (push buttons, rocker buttons, etc.) ), dials, slide switches, joysticks, click wheels. It should be noted that the input controller 3092 can be connected to any of the following: a keyboard, an infrared port, a USB interface, and a pointing device such as a mouse.

A touch screen 312, the touch screen 312 is an input interface and an output interface between the user terminal device and the user, and displays visual output to the user, and the visual output may include graphics, text, icons, videos, and the like.

The display controller 3091 in the I/O subsystem 309 receives electrical signals from the touch screen 312 or sends electrical signals to the touch screen 312 . The touch screen 312 detects the contact on the touch screen, and the display controller 3091 converts the detected contact into an interaction with the user interface object displayed on the touch screen 312, that is, realizes human-computer interaction, and the user interface object displayed on the touch screen 312 can be a running Icons for games, icons for networking to appropriate networks, etc. It is worth noting that the device may also include an optical mouse, which is a touch-sensitive surface that does not display visual output, or that is an extension of a touch-sensitive surface formed by a touch screen.

The RF circuit 305 is mainly used to establish communication between the mobile phone and the wireless network (that is, the network side), and realize data reception and transmission between the mobile phone and the wireless network. Such as sending and receiving short messages, e-mails, etc. Specifically, the RF circuit 305 receives and sends RF signals, which are also called electromagnetic signals, and the RF circuit 305 converts electrical signals into electromagnetic signals or converts electromagnetic signals into electrical signals, and communicates with communication networks and other devices through the electromagnetic signals to communicate. RF circuitry 305 may include known circuitry for performing these functions including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC ( COder-DECoder, Codec) Chipset, Subscriber Identity Module (Subscriber Identity Module, SIM) and so on.

The audio circuit 306 is mainly used to receive audio data from the peripheral interface 303 , convert the audio data into electrical signals, and send the electrical signals to the speaker 311 .

The speaker 311 is used to restore the voice signal received by the mobile phone from the wireless network through the RF circuit 305 into sound and play the sound to the user.

The power management chip 308 is used for power supply and power management for the hardware connected to the CPU 302 , the I/O subsystem and the peripheral interface.

The terminal device provided in the embodiment of the present application can optimize the booting process.

The boot optimization device, storage medium, and terminal device provided in the above embodiments can execute a boot optimization method provided in any embodiment of the present application, and have corresponding functional modules and beneficial effects for executing the method. For technical details not exhaustively described in the foregoing embodiments, reference may be made to a boot optimization method provided in any embodiment of the present application.

Note that the above are only preferred embodiments and technical principles used in this application. Those skilled in the art will understand that the present application is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the present application. Therefore, although the present application has been described in detail through the above embodiments, the present application is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the present application, and the present application The scope is determined by the scope of the appended claims.

Claims (10)

1. one kind start optimization method, it is characterised in that including：

It is determined that the start associated with associated with the starting up of terminal device；

When detecting that system core process is restarted, detect whether the start associated with damages；

If detecting the start associated with of damage, abnormality processing is carried out to the start associated with of damage.

2. the method as described in claim 1, it is characterised in that when detecting that system core process is restarted, opened described in detection Whether machine associated with damages, including：

When the Process identifier for detecting system core process changes, detect whether the start associated with damages.

3. the method as described in claim 1, it is characterised in that when detecting that system core process is restarted, opened described in detection Whether machine associated with damages, including：

When detecting that system core process is restarted, read and parse the start associated with to determine the start association text Part whether throw exception；

Wherein, in the start associated with throw exception, it is judged to damaging.

4. the method as described in claim 1, it is characterised in that the start associated with of described pair of damage carries out abnormality processing bag Include：

Will damage start associated with delete after regenerate, or obtain the start associated with of backup to replace opening for damage Machine associated with.

5. the method as described in any one of Claims 1-4, it is characterised in that associate text in the start for detecting damage After part, in addition to：

The start associated with of damage is reported into background monitoring end.

6. the method as described in any one of Claims 1-4, it is characterised in that when detecting that system core process is restarted, inspection Survey it is described start associated with whether damage before, in addition to：

When receiving starting up's instruction, record current time was the first available machine time；

Correspondingly, after the start associated with for detecting damage, in addition to：

Monitoring system is broadcasted；

When listening to starting up's broadcast, record current time was the second available machine time；

The start associated with of damage, the first available machine time and the second available machine time are reported into background monitoring end.

7. the method as described in any one of Claims 1-4, it is characterised in that it is crucial that the start associated with includes start File and/or start configuration file；

Correspondingly, the system core process includes system service process.

8. one kind start optimization device, it is characterised in that including：

File determining module, for the start associated with for determining to associate with the starting up of terminal device；

Detection module is damaged, for when detecting that system core process is restarted, detecting whether the start associated with damages；

Exception processing module, if the start associated with for detecting damage, the start associated with of damage is carried out Abnormality processing.

9. a kind of computer-readable recording medium, is stored thereon with computer program, it is characterised in that the program is held by processor The start optimization method as any one of claim 1 to 7 is realized during row.

10. a kind of terminal device, it is characterised in that including memory, processor and storage are on a memory and can be in processor The computer program of operation, it is characterised in that realize such as claim 1 to 7 described in the computing device during computer program Start optimization method described in any one.