CN105511879A - Multi-system starting method based on timer as well as intelligent terminal - Google Patents
Multi-system starting method based on timer as well as intelligent terminal Download PDFInfo
- Publication number
- CN105511879A CN105511879A CN201510916326.3A CN201510916326A CN105511879A CN 105511879 A CN105511879 A CN 105511879A CN 201510916326 A CN201510916326 A CN 201510916326A CN 105511879 A CN105511879 A CN 105511879A
- Authority
- CN
- China
- Prior art keywords
- operating system
- timer
- timer event
- event
- intelligent terminal
- 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
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000015654 memory Effects 0.000 claims description 23
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000004590 computer program Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000001413 cellular effect Effects 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000002618 waking effect Effects 0.000 description 1
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/4401—Bootstrapping
- G06F9/4406—Loading of operating system
- G06F9/441—Multiboot arrangements, i.e. selecting an operating system to be loaded
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
An embodiment of invention provides a multi-system starting method based on a timer as well as an intelligent terminal. The method comprises steps as follows: the timer continuously keeps timing after shutdown or sleep of the intelligent terminal, and when appointed time for a pre-stored timer event is up, an enabled instruction carries the appointed time and is sent to a boot program module; after the boot program module receives the enabled instruction, if the intelligent terminal is in a shutdown state, startup operation is executed, and the timer event matched with the appointed time in the enabled instruction and a pre-stored operating system identification corresponding to the timer event are acquired; whether a corresponding system is started up or not is determined by the boot program module according to the acquired operating system identification; if yes, the acquired timer event is sent to the operating system after startup; otherwise, the operating system is started up, and the acquired timer event is sent to the operating system after startup. With the adoption of the embodiment, the startup disorder of the operating system can be avoided.
Description
Technical Field
The invention relates to the technical field of intelligent terminals, in particular to a multi-system starting method based on a timer and an intelligent terminal.
Background
In China, intelligent terminals such as smart phones and tablet computers are widely popularized. The intelligent terminal can realize a plurality of timing functions depending on the timer therein. Such as a timed power on/off, a timed power on alarm clock, etc.
For the intelligent terminal installed with the single operating system, the timer-based system starting method can comprise the following steps: the intelligent terminal correspondingly stores the specified time input by the user and the starting instruction before the shutdown; after the power-off, the timer still executes the timing operation; when the timer determines that the timing reaches the stored specified time, the bootstrap program is awakened; and starting the operating system by the bootstrap program according to the stored starting instruction.
However, the inventor of the present invention finds that the current intelligent terminal installed with multiple operating systems generally does not have the function of starting up at regular time. If the method for starting the intelligent terminal of the single operating system at a fixed time is directly applied to the intelligent terminal of the multiple operating systems, the phenomenon that the operating systems are started disorderly is likely to occur.
For example, an operating system a and an operating system B are installed and run in the intelligent terminal; after receiving the appointed time and the starting instruction input by the user, the operating system correspondingly stores the appointed time and the starting instruction input by the user; when the timer continues to count time after being shut down and the timing is determined to reach the stored specified time, the bootstrap program is awakened; the bootstrap program may start the operating system B or start the operating system a according to the stored boot instruction, or may start both the operating systems a and B, thereby causing a phenomenon that the operating systems are started disorderly; if the user desires to boot operating system a and actually boots operating system B, the user experience is poor.
Therefore, it is necessary to provide a multi-system starting method based on a timer and an intelligent terminal to start an operating system specified by a user at a fixed time, so as to avoid starting disorder of the operating system and improve user experience.
Disclosure of Invention
The invention provides a multi-system starting method and an intelligent terminal based on a timer, aiming at the defects of the existing system starting mode based on the timer, and aims to solve the problem of disordered starting of an operating system in the prior art.
According to one aspect, an embodiment of the present invention provides a multi-system starting method based on a timer, including:
the timer keeps timing after the intelligent terminal is shut down or is dormant, and when the pre-stored timer event is determined to reach the specified time, the specified time is carried in the starting instruction and is sent to the bootstrap module;
after the bootstrap module receives the starting instruction, if the intelligent terminal is determined to be in a shutdown state, executing a startup operation, and acquiring a timer event matched with the specified time in the starting instruction and a prestored identification of an operating system corresponding to the timer event;
the bootstrap module determines whether the corresponding operating system is started or not according to the acquired identification of the operating system; if so, sending the acquired timer event to the started operating system; if not, the operating system is started, and the acquired timer event is sent to the started operating system.
According to another aspect, an embodiment of the present invention further provides an intelligent terminal, including: at least two operating systems, a timer, and a bootstrap module; wherein,
the timer is used for continuing timing after the intelligent terminal is powered off or is in a dormant state, and when the pre-stored timer event is determined to reach the designated time, the designated time is carried in the starting instruction to be sent;
the bootstrap module is used for executing a startup operation if the intelligent terminal is determined to be in a shutdown state after receiving the startup instruction, and acquiring a timer event matched with the specified time in the startup instruction and a pre-stored identification of an operating system corresponding to the timer event; determining whether the corresponding operating system is started or not according to the acquired identification of the operating system; if so, sending the acquired timer event to the started operating system; if not, the operating system is started, and the acquired timer event is sent to the started operating system.
In the embodiment of the invention, the timer continues to count time after the intelligent terminal is shut down or is dormant, and when the pre-stored timer event is determined to reach the specified time, a starting instruction carrying the specified time is sent to the bootstrap module. And the bootstrap module starts the intelligent terminal which is shut down and acquires a timer event matched with the specified time and a corresponding pre-stored identification of the operating system. Because the timer event is usually input by the user in advance, the bootstrap module starts the corresponding operating system according to the identifier of the operating system, which is pre-stored corresponding to the timer event, and can be considered as starting the operating system specified by the user instead of starting the operating system irrelevant to the acquired identifier, so that the starting disorder of the operating system is avoided, and the experience of the intelligent terminal user is improved.
Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
The foregoing and/or additional aspects and advantages of the present invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a schematic frame diagram of an internal structure of an intelligent terminal according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a method for timer-based multi-system startup according to an embodiment of the present invention;
fig. 3 is a schematic frame diagram of an internal structure of a bootstrap module according to an embodiment of the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are illustrative only and should not be construed as limiting the invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
As will be appreciated by those skilled in the art, a "terminal" as used herein includes both devices having a wireless signal receiver, which are devices having only a wireless signal receiver without transmit capability, and devices having receive and transmit hardware, which have devices having receive and transmit hardware capable of two-way communication over a two-way communication link. Such a device may include: a cellular or other communication device having a single line display or a multi-line display or a cellular or other communication device without a multi-line display; PCS (personal communications service), which may combine voice, data processing, facsimile and/or data communications capabilities; a PDA (personal digital assistant), which may include a radio frequency receiver, a pager, internet/intranet access, web browser, notepad, calendar and/or GPS (global positioning system) receiver; a conventional laptop and/or palmtop computer or other device having and/or including a radio frequency receiver. As used herein, a "terminal" or "terminal device" may be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or situated and/or configured to operate locally and/or in a distributed fashion at any other location(s) on earth and/or in space. As used herein, a "terminal device" may also be a communication terminal, a web terminal, a music/video playing terminal, such as a PDA, an MID (mobile internet device), and/or a mobile phone with music/video playing function, and may also be a smart tv, a set-top box, and the like.
The inventor of the present invention considers that a timer and a bootstrap module that can keep running even after the present intelligent terminal is powered off can be provided in the intelligent terminal. The timer can continue to count time after the intelligent terminal is powered off or is in a dormant state, and when the pre-stored timer event is determined to reach the specified time, the bootstrap module is notified. The bootstrap module can start up the intelligent terminal and acquire a timer event matched with the specified time and a corresponding pre-stored identification of the operating system. It is understood that the timer event is usually input by a user before the intelligent terminal is powered off or hibernated; the bootstrap module starts the corresponding operating system according to the identifier of the operating system which is pre-stored correspondingly to the timer event, and the operating system appointed by the user is considered to be started instead of the operating system which is irrelevant to the acquired identifier, so that the starting disorder of the operating system is avoided, and the experience of the intelligent terminal user is improved.
The technical solution of the embodiments of the present invention is specifically described below with reference to the accompanying drawings.
The intelligent terminal in the embodiment of the present invention may be a terminal device such as a smart phone and a tablet computer, and a frame diagram of an internal structure thereof is shown in fig. 1, and may include: a timer 101, a bootstrap module 102 and at least two operating systems.
The timer 101 may be physical hardware, such as a circuit with a timing function; the timer 101 may also be a combination of physical hardware and a program, such as a program having a timing function and a circuit carrying and allowing the program.
The timer 101 is mainly used for timing according to a timer event, and details will be described later.
The bootstrap module 102 may be physical hardware, such as a circuit having a function of booting the smart terminal, waking up the smart terminal to boot, or booting an operating system to boot; the bootstrap module 102 may also be a combination of physical hardware and programs, such as a program and a circuit that carries and allows the program to boot the smart terminal for boot, wake the smart terminal for boot, or boot the operating system for boot.
The bootstrap module 102 is mainly used to boot the intelligent terminal, wake up the intelligent terminal to boot, or boot the operating system to boot, and the specific content will be described in detail later.
The operating system of the intelligent terminal in the embodiment of the invention can be a Linux operating system or a Unix operating system in the traditional sense, and can also be an Android system, a Ubuntu system, a Meego system and the like derived based on the Linux operating system.
The operating system of the intelligent terminal in the embodiment of the invention can be an operating system based on a safety enhancement SELinux module, and can also be an operating system based on a container in accordance with the Linux container virtualization technology.
Specifically, the technician may create a container in the intelligent terminal and install an operating system in the container by using the linux container virtualization technology. Each container is configured with an independent hardware resource access authority configuration, and an operating system of the container can independently access hardware resources, such as CPUs (central processing units), IO (input output) devices and the like.
Preferably, as shown in fig. 1, the intelligent terminal according to the embodiment of the present invention may be provided with a plurality of operating systems.
Before the intelligent terminal is powered off or is in a dormant state, at least one operating system is operated in the intelligent terminal, and after the operating system receives the appointed time input by a user and the appointed operation information corresponding to the appointed time, the operating system generates a corresponding event identifier.
Specifically, after receiving appointed time input by a user and appointed operation information corresponding to the appointed time through a timer setting interface, an operating system determines that the user needs to execute appointed operation according to the appointed time in the operating system; and generating an event identifier for the corresponding specified time and the specified operation information.
In fact, the designated time input by the user may be a designated time or a designated time period, and the designated time period may be converted to each other.
Specifically, after receiving a specified time period input by a user, the operating system may determine the specified time according to the current time when the specified time period is received and the specified time period. For example, if the specified period of time for which the operating system receives the user input is 1 hour, and the current time of receiving the specified period of time for 1 hour is 8 o 'clock, it may be determined that the specified time is 9 o' clock. Otherwise, the operating system may determine the designated time period according to the current time when the designated time is received and the designated time.
The specified operation information input by the user includes one of the following operations: alarm clock operation information, power-on operation information, and the like. In actual operation, the power-on operation information may be represented by default no-operation information.
The operating system generates a corresponding timer event according to the received designated time, the designated operation information and the generated event identifier, and starts the timer 101.
Specifically, the operating system generates a timer event for the received specified operation information; and correspondingly carrying the received appointed time, the appointed operation information and the generated event identifier in the generated timer event, and then starting the timer 101. The timer 101 counts the time according to the specified time in the timer event, and the specific method of timing is well known to those skilled in the art and will not be described herein.
Preferably, each operating system in the intelligent terminal according to the embodiment of the present invention may generate a plurality of timer events. A timer event has a unique event identification.
Further, the operating system in the intelligent terminal according to the embodiment of the present invention may also carry the identifier of the program related to the specified operation information in the timer event. The program to which the specified operation information relates may be a program that executes a specified operation based on the specified operation information after execution.
In the intelligent terminal according to the embodiment of the present invention, the operating system stores the generated timer event and the identifier of the operating system in a designated area of the nonvolatile memory of the intelligent terminal according to the embodiment of the present invention. The non-volatile memory may include at least one of: flash memory, EEPROM (electrically erasable programmable read-only memory), and the like.
Preferably, in the intelligent terminal according to the embodiment of the present invention, the identifier of the operating system may be a number or a character string.
For example, if the container-based operating system and the non-container-based Android system are installed in the intelligent terminal according to the embodiment of the present invention, the identifier of the container-based operating system may be 1, and the identifier of the Android system may be 2; or the identifier of the container-based operating system can be yuanxin, and the identifier of the Android system can be Android.
Preferably, in the intelligent terminal according to the embodiment of the present invention, the operating system may store all timer events generated by the operating system and the identifier of the operating system in a designated area of the nonvolatile memory of the intelligent terminal.
In fact, at least two operating systems in the intelligent terminal according to the embodiment of the present invention may store the respective generated timer events and the respective identifiers in a designated area of a nonvolatile memory of the intelligent terminal in a corresponding manner.
For example, in a designated area of a nonvolatile memory of the smart terminal, a timer event a designated for 8 o 'clock is stored in association with an identifier "yuanxin" of the operating system, and a timer event B designated for 9 o' clock and 30 min is stored in association with an identifier "android" of the operating system.
Further, in the embodiment of the present invention, the timer event and the identifier of the operating system may be stored in a designated area of the nonvolatile memory of the intelligent terminal in a linked list manner. Specifically, each row in the linked list stores a timer event and an identifier of the operating system corresponding to the timer event.
In practical operation, in the embodiment of the present invention, at least two operating systems in the intelligent terminal may generate timer events with the same specified time, and store the timer events with the same specified time in correspondence with respective identifiers.
For example, in a designated area of the nonvolatile memory of the smart terminal, a timer event designated for 9 o 'clock is stored in correspondence with the identifier "yuanxin" of the operating system, and a timer event designated for 9 o' clock is stored in correspondence with the identifier "android" of the operating system.
Based on the correspondingly stored timer event and the identifier of the operating system, a flow diagram of the timer-based multi-system starting method according to the embodiment of the present invention is shown in fig. 2, and includes the following steps:
s201: the timer 101 continues to count time after the intelligent terminal is powered off or is in a sleep state, and when it is determined that the pre-stored timer event reaches the specified time, the specified time is carried in the start instruction and is sent to the bootstrap module 102.
Specifically, the timer 101 continues to count time after the intelligent terminal is turned off or hibernated, and matches the real-time timing result with the specified time in each timer event according to the event identifier of each timer event pre-stored in the specified area of the nonvolatile memory of the intelligent terminal, and determines that the matching result is the consistent timer event.
The timer 101 determines, for each timer event whose matching result is consistent, that the timer event reaches a specified time, and sends the specified time in the timer event to the bootstrap module 102 along with a start instruction.
S202: after receiving the start instruction, the bootstrap module 102 determines whether the intelligent terminal is in a shutdown state; if yes, go to step S203; otherwise, step S208 is performed.
Specifically, after receiving the start instruction, the bootstrap module 102 queries the state of the intelligent terminal, and determines whether the intelligent terminal is in a shutdown state; if yes, go to step S203; otherwise, step S208 is performed. The specific method for querying the state of the intelligent terminal is well known to those skilled in the art, and is not described herein again.
Preferably, after receiving the start instruction, the bootstrap module 102 determines whether a sender of the start instruction is the timer 101; if yes, inquiring the state of the intelligent terminal; otherwise, the received starting instruction is ignored. The specific method for confirming the sender of the start command is well known in the art and will not be described herein.
For example, if the boot program module 102 determines that the sender of the start instruction is a power key circuit or a circuit that outputs the start instruction according to the received restart instruction, the received start instruction is ignored.
S203: the bootstrap module 102 performs a boot operation.
Specifically, the bootstrap module 102 powers on hardware circuits of the intelligent terminal except for the timer 101, circuits related to the bootstrap module 102, and the nonvolatile memory, and starts a preset operating system.
S204: the bootstrap module 102 obtains a timer event matching the specified time in the start instruction and a pre-stored identification of the operating system corresponding to the timer event.
Specifically, the bootstrap module 102 parses the specified time from the start instruction; for each timer event in a designated area of a nonvolatile memory, acquiring designated time in the timer event, comparing the designated time in the timer event with the designated time in a starting instruction, and if the comparison result is consistent, determining that the timer event is matched with the designated time in the starting instruction, and acquiring the timer event; the bootstrap module 102 proceeds to retrieve the identification of the operating system stored in correspondence with the timer event.
For example, the bootstrap module 102 determines a timer event matching the specified time of 8 o' clock, obtains the timer event, and obtains the operating system identifier "yunaxin" stored in correspondence with the timer event.
Preferably, the bootstrap module 102 can obtain at least two timer events matching the specified time in the same start instruction, and the identifier of the operating system corresponding to each timer event.
That is, the bootstrap module 102 may obtain at least two timer events having the same specified time and corresponding to the identifications of different operating systems, and the identification of the operating system corresponding to each of the timer events.
For example, the bootstrap module 102 may obtain two timer events that specify both times as 9 o' clock, and obtain the operating system identification "yuanxin" corresponding to one timer event, and "android" corresponding to the other timer event.
For each timer event in the designated area of the non-volatile memory, if the comparison result is determined to be inconsistent, the bootstrap module 102 determines that the timer event is not matched with the designated time in the start instruction, and ignores the timer event.
S205: the bootstrap module 102 determines whether the corresponding operating system is started according to the obtained identifier of the operating system; if not, go to step S206; if yes, go to step S207.
Specifically, for the timer event obtained in the step S204, in this step, according to the identifier of the operating system corresponding to the timer event obtained in the step S204, the bootstrap module 102 queries the running state of the operating system, and determines whether the operating system is started; if not, go to step S206; if yes, go to step S207. The specific method for querying the operating state of the operating system is a common technical means of those skilled in the art, and is not described herein again.
Preferably, the bootstrap module 102, for each acquired timer event matching the specified time in the same start instruction, queries the running state of the operating system one by one according to the identifier of the operating system corresponding to the timer event, and determines whether the operating system has been started.
For example, the bootstrap module 102 queries, for the acquired timer event a and timer event B that match 9 o' clock, the running state of the operating system identified as "yuanxin" according to "yuanxin" corresponding to the timer event a, and determines whether the operating system has been started. Then, according to the "android" corresponding to the timer event a, the operating state of the operating system identified as "android" is queried, and whether the operating system is started or not is determined.
S206: the bootstrap module 102 starts the corresponding operating system and sends the acquired timer event to the started operating system.
Specifically, the bootstrap module 102 starts the operating system determined not to be started in step S205. After determining that the operating system is started, the timer event obtained in step S204 is sent to the started operating system.
Preferably, for each timer event with the same specified time in the step S205, the bootstrap module 102 starts an operating system according to a preset starting sequence in this step for its corresponding un-started operating system, and after determining that the operating system is started, sends the corresponding timer event obtained in the step S204 to the started operating system; then, the bootstrap module 102 starts another operating system, and after determining that the other operating system has been started, sends the corresponding timer event to the other operating system; until all the un-started operating systems determined in the above step S205 are completely started, the corresponding timer event is sent.
For example, the bootstrap module 102 may, in response to the timer events a and B having the same designated time in step S205, start the "yuanxin" operating system for the un-started "yuanxin" and "android" operating systems corresponding to the timer events a and B, and after determining that the "yuanxin" operating system has been started, send the corresponding timer event a to the "yuanxin" operating system; and then starting the 'android' operating system, and after determining that the 'android' operating system is started, sending a corresponding timer event B to the 'android' operating system.
After receiving the timer event, the started operating system analyzes designated operation information from the timer event; and operating according to the analyzed specified operation information.
For example, if the specified operation information analyzed from the received timer event by the operating system is the boot operation information, it is determined that the operation is completed.
Preferably, the started operating system parses specified operating information from the received timer event, determines a program related to the parsed specified operating information according to program registration information in the system, and sends the received timer event to the program after starting the program or confirming the start of the program; causing the program to operate in accordance with the received timer event.
For example, the started operating system analyzes alarm clock operation information from the received timer event, determines a program related to the alarm clock operation information as an alarm clock program according to program registration information in the system, and sends the received timer event to the alarm clock program after the alarm clock program is started or the alarm clock program is confirmed to be started; the alarm clock program is operated according to the designated time in the received timer event and the alarm clock operation information.
S207: the bootstrap module 102 sends the acquired timer event to the started operating system.
The specific method of this step is consistent with the method for the bootstrap module 102 to send the acquired timer event to the started operating system in step S205, and details thereof are not repeated here.
S208: the bootstrap module 102 determines whether the intelligent terminal is in a sleep state; if yes, go to step S209; otherwise, step S204 is executed.
S209: after the bootstrap module 102 executes the wake-up operation, step S204 is executed.
Specifically, the bootstrap module 102 wakes up the hardware circuit in the sleep state except the related circuits of the timer 101 and the bootstrap module 102 and the nonvolatile memory in the intelligent terminal, and starts up the preset operating system. The specific wake-up method is well known to those skilled in the art and will not be described herein. After that, step S204 is executed.
In fact, in step S206 or S207, after the bootstrap module 102 sends the acquired timer event to the started operating system, the timer event and the identifier of the operating system stored in correspondence with the timer event may be deleted from the designated area of the non-volatile memory of the smart terminal.
Preferably, the intelligent terminal in the embodiment of the present invention, by using the timer-based multi-system starting method, can start different operating systems to execute corresponding operations according to timer events with different specified times.
For example, the timer 101 and the bootstrap module 102 in the smart terminal start the "yuanxin" operating system at 8 o 'clock according to the timer event a with the designated time of 8 o' clock by using the above timer-based multi-system start method; based on timer event B, which has a specified time of 9 o 'clock and 30 minutes, the "android" operating system is started at 9 o' clock and 30 minutes.
Preferably, the intelligent terminal deletes the timer event a after the operating system of "yuanxin" is started at 8 o' clock, which can reduce the workload of the bootstrap module 102 for obtaining the timer event; and the bootstrap module 102 is prevented from mistakenly acquiring the timer event a and mistakenly starting the "yuanxin" operating system, further preventing the operating system from starting disorderly.
Preferably, according to the timer-based multi-system starting method, a schematic frame diagram of an internal structure of the bootstrap module 102 in the embodiment of the present invention is shown in fig. 3, and includes: an event and system identification acquisition unit 301 and a system activation unit 302.
The event and system identifier obtaining unit 301 is configured to, after receiving a start instruction sent by the timer 101, if it is determined that the intelligent terminal is in a power-off state, execute a power-on operation, and obtain a timer event that matches specified time in the start instruction and a pre-stored identifier of an operating system corresponding to the timer event.
The system starting unit 302 is configured to determine whether the corresponding operating system is started according to the event and the identifier of the operating system acquired by the system identifier acquiring unit 301; if so, sending the acquired timer event to the started operating system; if not, the operating system is started, and the event and the timer event acquired by the system identifier acquisition unit 301 are sent to the started operating system.
Preferably, as shown in fig. 3, the bootstrap module 102 further includes: the event and system identification deletion unit 303.
The event and system identifier deleting unit 303 is configured to delete the identifier of the corresponding pre-stored timer event and operating system after the system starting unit 302 sends the acquired timer event to the started operating system.
Specifically, after the system starting unit 302 sends the acquired timer event to the started operating system, the event and system identifier deleting unit 303 may further delete the timer event and the identifier of the operating system stored in correspondence with the timer event from a designated area of the nonvolatile memory of the smart terminal.
The method for implementing the functions of the event and system identifier obtaining unit 301, the system starting unit 302, and the event and system identifier deleting unit 303 may be configured to refer to the specific contents of the process steps shown in fig. 2, which is not described herein again.
In the embodiment of the invention, the timer continues to count time after the intelligent terminal is shut down or is dormant, and when the pre-stored timer event is determined to reach the specified time, a starting instruction carrying the specified time is sent to the bootstrap module. And the bootstrap module starts the intelligent terminal which is shut down and acquires a timer event matched with the specified time and a corresponding pre-stored identification of the operating system. Because the timer event is usually input by the user in advance, the bootstrap module starts the corresponding operating system according to the identifier of the operating system, which is pre-stored corresponding to the timer event, and can be considered as starting the operating system specified by the user instead of starting the operating system irrelevant to the acquired identifier, so that the starting disorder of the operating system is avoided, and the experience of the intelligent terminal user is improved.
In addition, in the embodiment of the present invention, the bootstrap module may pass the timer event to the program related to the specified operation information in the timer event through the operating system, and the program may complete the specified operation.
Furthermore, in the embodiment of the present invention, the timer is matched with the bootstrap module, and the operating systems corresponding to the timer events can be sequentially started according to the timer events with the same designated time; the operating system corresponding to the timer event may also be started at different specified times according to the timer event having different specified times.
In addition, in the embodiment of the invention, the bootstrap module can wake up the intelligent terminal which is dormant, acquire the timer event matched with the specified time and the identifier of the corresponding prestored operating system, and start the corresponding operating system according to the acquired identifier; that is to say, when the intelligent terminal is in a dormant state, the embodiment of the invention can also start the operating system specified by the user and prevent the operating system irrelevant to the acquired identifier from being started, thereby avoiding the starting disorder of the operating system and improving the experience of the intelligent terminal user.
Those skilled in the art will appreciate that the present invention includes apparatus directed to performing one or more of the operations described in the present application. These devices may be specially designed and manufactured for the required purposes, or they may comprise known devices in general-purpose computers. These devices have stored therein computer programs that are selectively activated or reconfigured. Such a computer program may be stored in a device (e.g., computer) readable medium, including but not limited to any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magnetic-optical disks, ROMs (Read-only memories), RAMs (random access memories), EPROMs (erasable programmable Read-only memories), EEPROMs (electrically erasable programmable Read-only memories), flash memories, magnetic cards, or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a bus. That is, a readable medium includes any medium that stores or transmits information in a form readable by a device (e.g., a computer).
It will be understood by those within the art that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. Those skilled in the art will appreciate that the computer program instructions may be implemented by a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implement the features specified in the block or blocks of the block diagrams and/or flowchart illustrations of the present disclosure.
Those of skill in the art will appreciate that various operations, methods, steps in the processes, acts, or solutions discussed in the present application may be alternated, modified, combined, or deleted. Further, various operations, methods, steps in the flows, which have been discussed in the present application, may be interchanged, modified, rearranged, decomposed, combined, or eliminated. Further, steps, measures, schemes in the various operations, methods, procedures disclosed in the prior art and the present invention can also be alternated, changed, rearranged, decomposed, combined, or deleted.
The foregoing is only a partial embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A multi-system starting method based on a timer is characterized by comprising the following steps:
the timer keeps timing after the intelligent terminal is shut down or is dormant, and when the pre-stored timer event is determined to reach the specified time, the specified time is carried in the starting instruction and is sent to the bootstrap module;
after the bootstrap module receives the starting instruction, if the intelligent terminal is determined to be in a shutdown state, executing a startup operation, and acquiring a timer event matched with the specified time in the starting instruction and a prestored identification of an operating system corresponding to the timer event;
the bootstrap module determines whether the corresponding operating system is started or not according to the acquired identification of the operating system; if so, sending the acquired timer event to the started operating system; if not, the operating system is started, and the acquired timer event is sent to the started operating system.
2. The method according to claim 1, further comprising, before the intelligent terminal is powered off or hibernated:
the operating system receives the appointed time input by the user and the appointed operation information corresponding to the appointed time, and then generates a corresponding event identifier;
and the operating system generates a corresponding timer event according to the received appointed time, the appointed operation information and the generated event identifier, and starts the timer.
3. The method of claim 2, wherein after generating the corresponding timer event, further comprising:
and the operating system correspondingly stores the generated timer event and the identifier of the operating system into a designated area of a nonvolatile memory of the intelligent terminal.
4. The method according to claim 1, wherein the sending the acquired timer event to the started operating system specifically includes:
the operating system determines a program related to appointed operation information in the received timer event and sends the timer event to the program; causing the program to operate in accordance with the received timer event.
5. The method of claim 1, wherein after sending the obtained timer event to the operating system after starting, further comprising:
and deleting the corresponding prestored identifier of the timer event and the operating system.
6. An intelligent terminal, comprising: at least two operating systems, a timer, and a bootstrap module; wherein,
the timer is used for continuing timing after the intelligent terminal is powered off or is in a dormant state, and when the pre-stored timer event is determined to reach the designated time, the designated time is carried in the starting instruction to be sent;
the bootstrap module is used for executing a startup operation if the intelligent terminal is determined to be in a shutdown state after receiving the startup instruction, and acquiring a timer event matched with the specified time in the startup instruction and a pre-stored identification of an operating system corresponding to the timer event; determining whether the corresponding operating system is started or not according to the acquired identification of the operating system; if so, sending the acquired timer event to the started operating system; if not, the operating system is started, and the acquired timer event is sent to the started operating system.
7. The intelligent terminal of claim 6, wherein the bootstrap module comprises:
the event and system identification acquisition unit is used for executing a startup operation if the intelligent terminal is determined to be in a shutdown state after receiving the startup instruction, and acquiring a timer event matched with the specified time in the startup instruction and an identification of an operating system prestored corresponding to the timer event;
the system starting unit is used for determining whether the corresponding operating system is started or not according to the event and the identifier of the operating system acquired by the system identifier acquiring unit; if so, sending the acquired timer event to the started operating system; if not, the operating system is started, and the event and the timer event acquired by the system identification acquisition unit are sent to the started operating system.
8. The intelligent terminal according to claim 7,
the operating system is used for generating a corresponding event identifier after receiving appointed time input by a user and appointed operation information corresponding to the appointed time before the intelligent terminal is powered off or dormant; and generating a corresponding timer event according to the received specified time, the specified operation information and the generated event identifier, and starting the timer.
9. The intelligent terminal of claim 8,
and the operating system is also used for correspondingly storing the generated timer event and the identifier of the operating system into a specified area of a nonvolatile memory of the intelligent terminal after the corresponding timer event is generated.
10. The intelligent terminal of claim 7, wherein the bootstrap module further comprises:
and the event and system identifier deleting unit is used for deleting the corresponding prestored identifiers of the timer event and the operating system after the system starting unit sends the acquired timer event to the started operating system.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510916326.3A CN105511879A (en) | 2015-12-11 | 2015-12-11 | Multi-system starting method based on timer as well as intelligent terminal |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510916326.3A CN105511879A (en) | 2015-12-11 | 2015-12-11 | Multi-system starting method based on timer as well as intelligent terminal |
Publications (1)
Publication Number | Publication Date |
---|---|
CN105511879A true CN105511879A (en) | 2016-04-20 |
Family
ID=55719889
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201510916326.3A Pending CN105511879A (en) | 2015-12-11 | 2015-12-11 | Multi-system starting method based on timer as well as intelligent terminal |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN105511879A (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106453413A (en) * | 2016-11-29 | 2017-02-22 | 北京元心科技有限公司 | Method and device for applying SELinux security policy in multi-system |
CN106534147A (en) * | 2016-11-29 | 2017-03-22 | 北京元心科技有限公司 | Method and device for selecting and applying SELinux security policy in multi-system |
CN107357615A (en) * | 2017-06-30 | 2017-11-17 | 广东欧珀移动通信有限公司 | Method for starting terminal, device, storage medium and electronic equipment |
CN108233968A (en) * | 2016-12-21 | 2018-06-29 | 联芯科技有限公司 | The control method and control device of digital RF interface |
CN110308934A (en) * | 2018-03-22 | 2019-10-08 | 龙芯中科技术有限公司 | HPET driving method and device, readable storage medium storing program for executing and electronic equipment |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1308276A (en) * | 2000-02-09 | 2001-08-15 | 国际商业机器公司 | Method and system of preselecting operation system loaded in subsequent boot process |
CN101859260A (en) * | 2010-05-14 | 2010-10-13 | 中国科学院计算技术研究所 | Timer management device and management method for operating system |
CN103324469A (en) * | 2012-03-21 | 2013-09-25 | 腾讯科技(深圳)有限公司 | Timer implementation method and device |
CN104821990A (en) * | 2015-04-29 | 2015-08-05 | 努比亚技术有限公司 | Intelligent terminal power-off alarm clock realization method and intelligent terminal |
-
2015
- 2015-12-11 CN CN201510916326.3A patent/CN105511879A/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1308276A (en) * | 2000-02-09 | 2001-08-15 | 国际商业机器公司 | Method and system of preselecting operation system loaded in subsequent boot process |
CN101859260A (en) * | 2010-05-14 | 2010-10-13 | 中国科学院计算技术研究所 | Timer management device and management method for operating system |
CN103324469A (en) * | 2012-03-21 | 2013-09-25 | 腾讯科技(深圳)有限公司 | Timer implementation method and device |
CN104821990A (en) * | 2015-04-29 | 2015-08-05 | 努比亚技术有限公司 | Intelligent terminal power-off alarm clock realization method and intelligent terminal |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106453413A (en) * | 2016-11-29 | 2017-02-22 | 北京元心科技有限公司 | Method and device for applying SELinux security policy in multi-system |
CN106534147A (en) * | 2016-11-29 | 2017-03-22 | 北京元心科技有限公司 | Method and device for selecting and applying SELinux security policy in multi-system |
CN106453413B (en) * | 2016-11-29 | 2019-06-25 | 北京元心科技有限公司 | Method and device for applying SELinux security policy in multi-system |
CN106534147B (en) * | 2016-11-29 | 2019-08-27 | 北京元心科技有限公司 | Method and device for selecting and applying SELinux security policy in multi-system |
CN108233968A (en) * | 2016-12-21 | 2018-06-29 | 联芯科技有限公司 | The control method and control device of digital RF interface |
CN108233968B (en) * | 2016-12-21 | 2020-05-12 | 辰芯科技有限公司 | Control method and control device of digital radio frequency interface |
CN107357615A (en) * | 2017-06-30 | 2017-11-17 | 广东欧珀移动通信有限公司 | Method for starting terminal, device, storage medium and electronic equipment |
CN110308934A (en) * | 2018-03-22 | 2019-10-08 | 龙芯中科技术有限公司 | HPET driving method and device, readable storage medium storing program for executing and electronic equipment |
CN110308934B (en) * | 2018-03-22 | 2022-03-29 | 龙芯中科(成都)技术有限公司 | HPET driving method and device, readable storage medium and electronic equipment |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN105511879A (en) | Multi-system starting method based on timer as well as intelligent terminal | |
US11200101B2 (en) | Managing applications for power conservation | |
KR101689450B1 (en) | Method and apparatus for enhancing a hibernate and resume process using user space synchronization | |
EP2871825B1 (en) | Method for enabling shutdown alarm clock and mobile terminal | |
US9098301B2 (en) | Electronic device and booting method | |
US11507647B2 (en) | Fingerprint-based login system, microcontroller unit, fingerprint-based power assembly, and electronic terminal | |
US9554187B2 (en) | Smart television system and turn-on and turn-off method thereof | |
US20100138838A1 (en) | Method for executing scheduled task | |
CN106020875B (en) | Firmware update management method and device of embedded terminal | |
CN108040292B (en) | Television standby starting method, television and computer readable storage medium | |
US20170177406A1 (en) | Methods for managing a service or application for a smart device and a smart device utilizing the same | |
WO2017219861A1 (en) | Method and device for controlling system start-up mode | |
CN106843943B (en) | STM32 microprocessor program architecture design method | |
CN107360165B (en) | Terminal device, cloud server and method and device for managing and controlling operating system | |
CN101847188A (en) | Software protection method for security device based on clock and security device | |
WO2018010596A1 (en) | Mode switching method and device | |
CN106484075B (en) | Method and device for adjusting application program wake-up time | |
US20150228137A1 (en) | Wireless access control to a locking device | |
CN109992375B (en) | Information processing method, information processing device, computer equipment and computer readable storage medium | |
CN102722392A (en) | Method and system for software operation | |
CN102855428A (en) | Security control method of computer and computer | |
CN109429313B (en) | Information interaction method, functional equipment, terminal, server and storage medium | |
US11079817B2 (en) | Electronic device and method of starting the same | |
WO2014176893A1 (en) | Method and device for powering off mobile terminal | |
US7526662B2 (en) | Method and apparatus for secure module restoration |
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: 20160420 |