CN111443951A - System starting method and system starting device - Google Patents

System starting method and system starting device Download PDF

Info

Publication number
CN111443951A
CN111443951A CN201910041389.7A CN201910041389A CN111443951A CN 111443951 A CN111443951 A CN 111443951A CN 201910041389 A CN201910041389 A CN 201910041389A CN 111443951 A CN111443951 A CN 111443951A
Authority
CN
China
Prior art keywords
starting
operating system
rru
firmware
established
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201910041389.7A
Other languages
Chinese (zh)
Inventor
杨娜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
Datang Mobile Communications Equipment Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Datang Mobile Communications Equipment Co Ltd filed Critical Datang Mobile Communications Equipment Co Ltd
Priority to CN201910041389.7A priority Critical patent/CN111443951A/en
Publication of CN111443951A publication Critical patent/CN111443951A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/4401Bootstrapping
    • G06F9/4406Loading of operating system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751Error or fault detection not based on redundancy
    • G06F11/0754Error or fault detection not based on redundancy by exceeding limits
    • G06F11/0757Error or fault detection not based on redundancy by exceeding limits by exceeding a time limit, i.e. time-out, e.g. watchdogs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793Remedial or corrective actions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1417Boot up procedures
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1441Resetting or repowering

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the invention provides a system starting method and a system starting device, which are applied to a base station Radio Remote Unit (RRU), wherein the method comprises the following steps: loading a bootstrap program for booting the starting of the operating system of the RRU; if the starting flag bit is detected to be established, starting a first operating system of the RRU through the bootstrap program; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software. The embodiment of the invention can improve the convenience of repairing the RRU and reduce the operation cost of repairing and installing the RRU.

Description

System starting method and system starting device
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a system startup method and a system startup device.
Background
The RRU (Radio Remote Unit) of the base station is configured to convert a baseband optical signal into a Radio frequency signal at a Remote end, amplify the Radio frequency signal, and transmit the Radio frequency signal.
In practical applications, the RRU is usually deployed near an antenna, such as the top of a tower, and therefore, the RRU needs to be operated by connecting a BBU (Base band Unit) of a Base station through an operation and maintenance machine room and then by using an optical fiber between the BBU and the RRU.
However, when the firmware version or the software version of the RRU fails, the RRU may not be normally started, and the operation and maintenance machine room may not be remotely connected to the RRU, and the RRU may only be repaired by a network port, a serial port, or even a near-end manner such as a JTAG (Joint Test action group) simulator. However, since the RRU is usually deployed at a place close to the antenna, such as the top of the iron tower, a professional is required to climb onto the top of the iron tower to detach the RRU device for repair, and then the RRU device is installed back after the repair is completed, which not only causes difficulty in the repair installation process of the RRU, but also increases the operation cost of the repair installation.
Disclosure of Invention
The embodiment of the invention provides a system starting method and a system starting device, which can reduce the operation cost of RRU repair and installation.
The embodiment of the invention provides a system starting method, which is applied to a base station Radio Remote Unit (RRU), and comprises the following steps:
loading a bootstrap program for booting the starting of the operating system of the RRU;
if the starting flag bit is detected to be established, starting a first operating system of the RRU through the bootstrap program; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software.
The embodiment of the invention provides a system starting device, which is applied to RRU and comprises:
a boot loading module, configured to load a boot program for booting an operating system of the RRU to start;
a first system starting module, configured to start a first operating system of the RRU through the bootstrap program if it is detected that a start flag is established; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software.
The embodiment of the invention has the following advantages:
in the embodiment of the invention, in the starting process of the RRU, after a bootstrap program for guiding the starting of an operating system of the RRU is loaded, whether a starting flag bit is established or not can be detected, and if the starting flag bit is established, a first operating system of the RRU can be started through the bootstrap program; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software.
Because the start flag is established when the second operating system of the RRU fails to start, when the start flag is detected, it indicates that the second operating system of the RRU cannot be started normally, at this time, the first operating system may be started, and may include a first firmware and a first software, where the first firmware may be used to implement normal start of the first operating system, and the first software may be used to implement normal communication between the RRU and the BBU. Therefore, under the condition that the second operating system of the RRU breaks down, the RRU can still be normally started through the first operating system, so that maintenance personnel can remotely access the RRU in an operation and maintenance machine room to remotely repair the RRU without needing a professional to mount the top of the iron tower to disassemble the RRU equipment for repair, the convenience for repairing the RRU can be improved, and the operation cost for repairing and installing the RRU can be reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
FIG. 1 is a flow chart of a first embodiment of a system boot method of the present invention;
FIG. 2 is a flow chart of a second embodiment of a system booting method according to the present invention;
fig. 3 shows a block diagram of an embodiment of the system startup device of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Method embodiment one
Referring to fig. 1, a flowchart of a first embodiment of a system startup method of the present invention is shown, which may specifically include:
step 101, loading a boot program for booting the operating system of the RRU to start;
step 102, if it is detected that a start flag bit is established, starting a first operating system of the RRU through the bootstrap; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software.
The embodiment of the present invention can be applied to a Radio Remote Unit (RRU) of a Base Station, where the Base Station can be a Base Transceiver Station (BTS) in GSM (Global System of Mobile communication) or CDMA (Code Division Multiple Access), an NB (NodeB, Base Station) in WCDMA (Wideband Code Division Multiple Access), an eNB or eNodeB (evolved node b, Base Station) in L TE (L ong Term Evolution), or a Base Station in 5G (fifth generation Mobile communication network).
The embodiment of the present invention may store a first operating system of the RRU in advance, where the first operating system specifically may include: a first firmware and a first software. The first firmware and the first software can be basic versions which are fully verified, and basic functions of starting an operating system, synchronizing optical fibers, remotely accessing, downloading the operating system and the like can be realized. For example, the first firmware can be used to implement normal boot of a first operating system, and the first software can be used to implement normal connectivity of the RRU with the BBU.
It can be understood that the storage location of the first operating system is not limited in the embodiment of the present invention, for example, a dedicated storage area may be reserved in a Flash (Flash EEPROM Memory) for storing the first operating system, and the first operating system and the second operating system may be located in different storage areas.
The second operating system may specifically be a normal version currently used by the RRU, and the second operating system may specifically include: second firmware and second software. The second firmware and the second software can be upgraded versions, and richer functions can be realized.
The start flag bit may be used to indicate a type of an operating system started by the RRU, for example, if the start flag bit is established, a First operating system is started, and if the start flag bit is not established, a second operating system is started, where the start flag bit is established when the second operating system of the RRU fails to start, specifically, after the RRU is powered on, a Boot program for guiding the operating system of the RRU to start, such as a First Stage Boot loader (FSB L), may be loaded, and a second operating system of a normal version is started by the Boot program, and in a process of starting the second operating system, if a failure occurs and results in a failure in starting the second operating system, the start flag bit may be established.
Therefore, through the embodiment of the invention, when the second operating system of the RRU has a fault, the RRU can still be normally started through the first operating system, so that a maintainer can remotely access the RRU in an operation and maintenance machine room, the remote repair of the RRU can be realized, a professional is not required to climb the top of an iron tower to disassemble RRU equipment for repair, the convenience for repairing the RRU can be improved, and the operating cost for repairing and installing the RRU can be reduced.
In an optional embodiment of the present invention, after the first operating system of the RRU is started, the method may further include the following steps:
step S11, repairing a second operating system of the RRU;
step S12, clearing the established starting zone bit;
and step S13, reloading the bootstrap program so as to start the repaired second operating system through the bootstrap program.
In the embodiment of the present invention, when the second operating system is abnormally started, the start flag may be established, and the RRU is restarted, and at this time, the established start flag is detected, and then the first operating system may be started.
Because the first operating system comprises the first software capable of realizing basic functions such as remote connection and network downloading, after the first operating system is successfully started, the RRU can download a problem-free version of the second operating system from a server storing the second operating system through network connection so as to cover the second operating system with an abnormal version in the current RRU, and further realize the automatic repair of the RRU.
After the second operating system of the RRU is repaired, the established start flag bit may be cleared, and the boot program is reloaded to start the repaired second operating system through the boot program.
It can be understood that the specific manner of repairing the second operating system is not limited in the embodiment of the present invention, for example, the second operating system of the current version may be repaired by downloading the second operating system of the new version; or, the specific fault can be repaired in a targeted manner according to the fault of the second operating system.
In an optional embodiment of the invention, the method may further comprise: and recording event information corresponding to the starting flag bit.
Specifically, in the process of starting the second operating system, if an exception occurs, which results in a failed start of the second operating system, a start flag may be established, and in addition, event information corresponding to the establishment of the start flag may be recorded. For example, the event information may include: firmware failure or software failure; among other things, firmware failures may include: CRC (cyclic redundancy Check) Check failure, etc.; software failures may include: failure of software package decompression, etc.
It is to be understood that the embodiment of the present invention does not limit the specific manner of recording the event information. In an application example of the present invention, the start flag may be set to include 8 bits, and each bit may be used to represent a common fault event. For example, the lowest position 1 of the flag bit is started, which indicates that the CRC check of the second firmware fails; the second position 1 of the flag bit is started to indicate that the software package is not decompressed and the like.
After the RRU is powered on, if it is detected that the start flag is established, event information corresponding to the establishment of the start flag may be further determined and recorded according to a bit of a 1 in the start flag, that is, according to the bit of the 1, a failure cause that the second operating system cannot be normally started may be determined, and thus the failure may be automatically repaired. For example, if it is determined that the second firmware in the second operating system fails, a new version of the second firmware may be downloaded from the server to automatically repair the current second firmware; for another example, if it is determined that the second software in the second operating system fails, a new version of the second software may be downloaded from the server to automatically repair the current second software, and so on. Even if some faults which cannot be automatically repaired exist, maintenance personnel can remotely access the RRU in the operation and maintenance machine room through the first operating system to remotely repair the faults.
In the embodiment of the invention, the second operating system can be upgraded, but the first operating system is not upgraded, so that the stability of the first operating system is ensured.
In an optional embodiment of the present invention, after loading a boot program for booting an operating system of the RRU to start, the method may further include: and if the starting flag bit is not established, starting a second operating system of the RRU through the bootstrap program.
Specifically, after the RRU is powered on, a boot program for booting the operating system of the RRU to start may be loaded, and if it is detected that the start flag is not established, which indicates that the second operating system is not abnormal, and the second operating system may be started normally, the second operating system may be started through the boot program.
In an optional embodiment of the present invention, the second operating system may specifically include: the starting of the second operating system of the RRU may specifically include the following steps:
step S21, establishing a starting zone bit;
step S22, starting the second firmware;
step S23, if the second firmware is successfully started, clearing the established start flag, and starting the second software; if the second firmware fails to start, the boot program is reloaded;
step S24, if the second software fails to start, establishing a start flag, and reloading the boot program.
Specifically, before the second operating system is started, a start flag may be established, and then whether to clear the start flag may be determined according to whether the second operating system can normally complete the start.
After the start flag bit is established, the second firmware can be started first, and if the second firmware is started successfully, the established start flag bit can be cleared, and the second software can be started; if the second firmware fails to start, the boot program can be reloaded, in this case, because the start flag bit is not cleared, the start flag bit is detected after the restart, so as to start the first operating system, and automatically repair the second operating system, thereby realizing self-protection and automatic repair of the second firmware under the condition of version upgrade or accidental damage of the second firmware.
In an optional embodiment of the present invention, after the start flag is established and before the second firmware is started, the method may further include the steps of: starting a timer;
after the second firmware is started and before the second software is started, the method may further include the steps of: if the timer is overtime, the bootstrap program is reloaded; and if the timer is not overtime and the second firmware is successfully started, closing the timer.
The timer may specifically be a watchdog timer, and may be configured to prevent a start exception caused by a loading failure of the second firmware. In the starting process of the second firmware, if the abnormal starting condition caused by the firmware version error occurs, the watchdog timer is triggered to reset when the watchdog timer is not closed and no watchdog feeding action exists, and the boot program is reloaded. In this case, since the boot flag is not cleared, it is detected after the reboot that the boot flag is established, so that the first operating system is booted and the second operating system is self-repaired.
After the second firmware is successfully started, the watchdog timer can be closed, and the established start flag bit is cleared, which indicates that the second firmware is not abnormal, and the protection of the second firmware is completed.
In a specific application, the optical interface link configuration of the RRU is completed in software, and if the software version is damaged or there is a problem, the optical fiber link is broken, in this case, a professional is also required to disassemble the RRU device for repair. Therefore, in order to avoid the above situation, the embodiment of the present invention performs self-protection and automatic repair on the second software in the second operating system.
Specifically, after the second firmware is successfully started, the second software may be started, if the second software fails to be started, a start flag bit may be established, and the board is restarted by using the control command word to reload the boot program, and in this case, since the start flag bit is not cleared, it is detected that the start flag bit is established after the restart, so as to start the first operating system and perform self-repair on the second operating system, therefore, in a case where a software package of the second software is damaged, self-protection and automatic repair of the second software may be implemented, and further, a situation that a software version is damaged or an optical fiber is broken due to a problem, and the operation and maintenance machine room cannot remotely access the RRU may be avoided.
To sum up, in the starting process of the RRU, after loading a bootstrap program for guiding the operation system of the RRU to start, the embodiment of the present invention may detect whether a start flag bit is established, and if it is detected that the start flag bit is established, the first operation system of the RRU may be started through the bootstrap program; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software.
Because the start flag is established when the second operating system of the RRU fails to start, when the start flag is detected, it indicates that the second operating system of the RRU cannot be started normally, at this time, the first operating system may be started, and may include a first firmware and a first software, where the first firmware may be used to implement normal start of the first operating system, and the first software may be used to implement normal communication between the RRU and the BBU. Therefore, under the condition that the second operating system of the RRU breaks down, the RRU can still be normally started through the first operating system, so that maintenance personnel can remotely access the RRU in an operation and maintenance machine room to remotely repair the RRU without needing a professional to mount the top of the iron tower to disassemble the RRU equipment for repair, the convenience for repairing the RRU can be improved, and the operation cost for repairing and installing the RRU can be reduced.
Method embodiment two
Referring to fig. 2, a flowchart of a second embodiment of a system startup method of the present invention is shown, which may specifically include:
step 201, power-on reset;
step 202, loading the FSB L;
after the RRU is powered on, the FSB L may be loaded to boot the operating system of the RRU.
Step 203, judging whether a starting flag bit is established; if so, go to step 204; if not, go to step 209;
specifically, if the start flag is established, which indicates that the second operating system fails and cannot be normally started, step 204 is executed to start the first operating system; if the boot flag is not set, indicating that the second operating system can be booted normally, step 209 is performed to boot the second operating system.
Step 204, starting a first firmware;
in a specific application, the uboot (Universal Boot L loader) is an open source code item following the terms of GP L, and is used for system Boot, the first firmware of the embodiment of the present invention may include a first uboot and a first core (kernel), where the first uboot and the first core may be sufficiently verified and stable versions, and the first uboot is used for starting the first kernel (core) of the first operating system.
Step 205, starting first software;
through the first software, the normal communication between the RRU and the BBU can be realized.
Step 206, repairing the second operating system;
specifically, a new version of the second operating system may be downloaded, overwriting the current version of the second operating system; or, the fault can be repaired in a targeted manner according to the fault reason recorded by the starting flag bit.
Step 207, clearing the starting flag bit;
after the second operating system repair is complete, the established boot flag may be cleared.
Step 208, restarting the RRU;
after restarting the RRU, one can jump to step 202 to reload the FSB L and determine if the start flag has been established, and because the start flag has been cleared, the repaired second operating system can be started.
Step 209, establishing a starting zone bit;
the second operating system may be started when it is detected that the start flag is not established, the start flag is established first before the start, and whether to clear the start flag may be determined subsequently according to whether the second operating system can complete the start normally.
Step 210, starting a watchdog timer;
the watchdog timer may be used to prevent a boot exception caused by a second firmware load failure.
Step 211, starting the second firmware;
similar to the first firmware, the second firmware may include a second uboot and a second core. And in the process of starting the second firmware, starting the second uboot firstly, and then starting the second core through the second uboot.
Step 212, judging whether the watchdog timer is overtime, if yes, executing step 202; if not, go to step 213;
specifically, the second uboot is started first, whether the watchdog timer is overtime is judged, if abnormal starting conditions such as a second firmware version error occur, the watchdog timer is not closed and reset is triggered when no dog feeding action exists, at this time, since the starting flag bit is not cleared, step 202 is executed after the watchdog is restarted and the starting flag bit is judged again, so that step 204 can be performed to automatically repair the fault. If the second uboot is successfully started, a second core is started, and similarly, whether the watchdog timer is overtime is judged, if the situation that the start is abnormal due to the error of the version of the second firmware and the like occurs, the watchdog timer is not closed and the watchdog timer is triggered to reset when no dog feeding action exists, at this time, because the start flag bit is not cleared, the step 202 is executed after the restart, and the start flag bit is judged again, so that the step 204 can be entered to automatically repair the fault. Therefore, self-protection and automatic repair of the second firmware can be realized.
Step 213, closing the watchdog timer;
if the second core is successfully started and the watchdog timer has not timed out, the watchdog timer may be turned off.
Step 214, clearing the starting flag bit;
thus, the established boot flag can be cleared if the second firmware boot is successful.
Step 215, starting the second software;
after the second firmware boot is successful, the second software may be launched.
Step 216, judging whether the second software is started abnormally, and if the second software is started abnormally, executing step 217; if no exception occurs, go to step 219;
in the second software starting process, it may be determined whether the second software starting is abnormal, for example, if the second software starting is abnormal due to the failure of decompression of both the main and standby software packages, the start flag may be established, then the RRU is restarted to jump to step 202, and it is determined whether the start flag is established again, so that step 204 may be entered to automatically repair the fault of the second software. Therefore, self-protection and automatic repair of the second software can be realized.
Step 217, establishing a starting zone bit;
step 218, restarting the RRU;
step 219, the start-up procedure ends.
To sum up, the embodiment of the present invention improves the starting process of the RRU, and after loading a bootstrap program for guiding the operation system of the RRU to start, it can be detected whether a start flag bit is established, and if it is detected that the start flag bit is established, the first operation system of the RRU can be started through the bootstrap program; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software.
Because the start flag is established when the second operating system of the RRU fails to start, when the start flag is detected, it indicates that the second operating system of the RRU cannot be started normally, at this time, the first operating system may be started, and may include a first firmware and a first software, where the first firmware may be used to implement normal start of the first operating system, and the first software may be used to implement normal communication between the RRU and the BBU. Therefore, under the condition that the second operating system of the RRU breaks down, the RRU can still be normally started through the first operating system, so that maintenance personnel can remotely access the RRU in an operation and maintenance machine room to remotely repair the RRU without needing a professional to mount the top of the iron tower to disassemble the RRU equipment for repair, the convenience for repairing the RRU can be improved, and the operation cost for repairing and installing the RRU can be reduced.
Device embodiment
Referring to fig. 3, a block diagram of a system startup device of an embodiment of the present invention is shown, and is applied to an RRU, where the device may specifically include:
a boot loading module 301, configured to load a boot program for booting an operating system of the RRU to start;
a first system starting module 302, configured to start a first operating system of the RRU through the bootstrap if it is detected that a start flag is established; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software.
Optionally, the apparatus may further include:
and the second system starting module is used for starting a second operating system of the RRU through the bootstrap program if the starting flag bit is not established.
Optionally, the second operating system may specifically include: the second system starting module may specifically include:
the first establishing module is used for establishing a starting zone bit;
the second firmware starting module is used for starting the second firmware;
the starting judgment module is used for clearing the established starting zone bit and starting the second software if the second firmware is started successfully; if the second firmware fails to start, the boot program is reloaded;
and the second establishing module is used for establishing a starting zone bit and reloading the bootstrap program if the second software fails to start.
Optionally, the apparatus may further include:
the timer starting module is used for starting the timer;
the apparatus may further include:
a timer judgment module, configured to reload the bootstrap program if the timer is overtime; and if the timer is not overtime and the second firmware is successfully started, closing the timer.
Optionally, the apparatus may further include:
the repair module is used for repairing a second operating system of the RRU;
the clearing module is used for clearing the established starting zone bit;
and the reloading module is used for reloading the bootstrap program so as to start the repaired second operating system through the bootstrap program.
Optionally, the apparatus may further include:
and the recording module is used for recording the event information corresponding to the starting marker bit.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The system starting method and the system starting device provided by the invention are described in detail, and the principle and the implementation mode of the invention are explained by applying specific examples, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims (12)

1. A system starting method is applied to a base station Radio Remote Unit (RRU), and comprises the following steps:
loading a bootstrap program for booting the starting of the operating system of the RRU;
if the starting flag bit is detected to be established, starting a first operating system of the RRU through the bootstrap program; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software.
2. The method of claim 1, wherein after loading a boot program for booting an operating system of the RRU to boot, the method further comprises:
and if the starting flag bit is not established, starting a second operating system of the RRU through the bootstrap program.
3. The method of claim 2, wherein the second operating system comprises: the starting of the second operating system of the RRU includes:
establishing a starting zone bit;
starting the second firmware;
if the second firmware is successfully started, clearing the established starting zone bit and starting the second software; if the second firmware fails to start, the boot program is reloaded;
and if the second software fails to be started, establishing a starting zone bit and reloading the bootstrap program.
4. The method of claim 3, wherein after establishing a boot flag and before booting the second firmware, the method further comprises:
starting a timer;
after the second firmware is started, and before the second software is started, the method further comprises:
if the timer is overtime, the bootstrap program is reloaded; and if the timer is not overtime and the second firmware is successfully started, closing the timer.
5. The method of claim 1, wherein after starting the first operating system of the RRU, the method further comprises:
repairing a second operating system of the RRU;
clearing the established starting zone bit;
and reloading the bootstrap program so as to start the repaired second operating system through the bootstrap program.
6. The method according to any one of claims 1 to 5, further comprising:
and recording event information corresponding to the starting flag bit.
7. A system start apparatus, applied to an RRU, the apparatus comprising:
a boot loading module, configured to load a boot program for booting an operating system of the RRU to start;
a first system starting module, configured to start a first operating system of the RRU through the bootstrap program if it is detected that a start flag is established; wherein the start flag is established under the condition that the second operating system of the RRU fails to start; the first operating system includes: a first firmware and a first software.
8. The apparatus of claim 7, further comprising:
and the second system starting module is used for starting a second operating system of the RRU through the bootstrap program if the starting flag bit is not established.
9. The apparatus of claim 8, wherein the second operating system comprises: a second firmware and a second software, the second system boot module comprising:
the first establishing module is used for establishing a starting zone bit;
the second firmware starting module is used for starting the second firmware;
the starting judgment module is used for clearing the established starting zone bit and starting the second software if the second firmware is started successfully; if the second firmware fails to start, the boot program is reloaded;
and the second establishing module is used for establishing a starting zone bit and reloading the bootstrap program if the second software fails to start.
10. The apparatus of claim 9, further comprising:
the timer starting module is used for starting the timer;
the device further comprises:
a timer judgment module, configured to reload the bootstrap program if the timer is overtime; and if the timer is not overtime and the second firmware is successfully started, closing the timer.
11. The apparatus of claim 7, further comprising:
the repair module is used for repairing a second operating system of the RRU;
the clearing module is used for clearing the established starting zone bit;
and the reloading module is used for reloading the bootstrap program so as to start the repaired second operating system through the bootstrap program.
12. The apparatus of any of claims 7 to 11, further comprising:
and the recording module is used for recording the event information corresponding to the starting marker bit.
CN201910041389.7A 2019-01-16 2019-01-16 System starting method and system starting device Pending CN111443951A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910041389.7A CN111443951A (en) 2019-01-16 2019-01-16 System starting method and system starting device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910041389.7A CN111443951A (en) 2019-01-16 2019-01-16 System starting method and system starting device

Publications (1)

Publication Number Publication Date
CN111443951A true CN111443951A (en) 2020-07-24

Family

ID=71626755

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910041389.7A Pending CN111443951A (en) 2019-01-16 2019-01-16 System starting method and system starting device

Country Status (1)

Country Link
CN (1) CN111443951A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114077453A (en) * 2020-08-04 2022-02-22 成都鼎桥通信技术有限公司 Starting method and device of application system and terminal

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102300239A (en) * 2011-09-27 2011-12-28 大唐移动通信设备有限公司 Base station and self-starting method thereof
CN104503859A (en) * 2014-12-29 2015-04-08 长园深瑞继保自动化有限公司 Method for monitoring computer operating system in starting process
CN104834542A (en) * 2015-04-20 2015-08-12 成都亿盟恒信科技有限公司 Method for starting double systems based on embedded Linux equipment
US20170324562A1 (en) * 2016-05-09 2017-11-09 Hewlett Packard Enterprise Development Lp Recovery agents and recovery plans over networks
CN107704258A (en) * 2017-10-27 2018-02-16 深圳市恒扬数据股份有限公司 Uboot upgrade methods, system and terminal device
CN108427611A (en) * 2017-02-14 2018-08-21 北京国基科技股份有限公司 A kind of cloud terminal system dual redundant intelligent starting method and device

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102300239A (en) * 2011-09-27 2011-12-28 大唐移动通信设备有限公司 Base station and self-starting method thereof
CN104503859A (en) * 2014-12-29 2015-04-08 长园深瑞继保自动化有限公司 Method for monitoring computer operating system in starting process
CN104834542A (en) * 2015-04-20 2015-08-12 成都亿盟恒信科技有限公司 Method for starting double systems based on embedded Linux equipment
US20170324562A1 (en) * 2016-05-09 2017-11-09 Hewlett Packard Enterprise Development Lp Recovery agents and recovery plans over networks
CN108427611A (en) * 2017-02-14 2018-08-21 北京国基科技股份有限公司 A kind of cloud terminal system dual redundant intelligent starting method and device
CN107704258A (en) * 2017-10-27 2018-02-16 深圳市恒扬数据股份有限公司 Uboot upgrade methods, system and terminal device

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
卢晶琦,孟庆元编著: "《移动通信理论与实战》", 28 February 2017, 西安电子科技大学出版社 *
邹逢兴主编;邹逢兴,张湘平编著: "《计算机应用系统的故障诊断与可靠性技术基础》", 31 December 1999, 高等教育出版社 *
韩馥儿主编;张雁翔,王毅强,刘勇等副主编: "《中国光纤通信年鉴 2015年版》", 30 November 2015, 上海科学技术文献出版社 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114077453A (en) * 2020-08-04 2022-02-22 成都鼎桥通信技术有限公司 Starting method and device of application system and terminal

Similar Documents

Publication Publication Date Title
EP2456257B1 (en) Method and system for upgrading wireless data card
US8107945B2 (en) Wireless device remote recovery
CN102830984B (en) Method, chip and the communication terminal that firmware updates
EP2878140B1 (en) Wireless firmware upgrades to an alarm security panel
TWI533216B (en) Operating system updating method
KR100952585B1 (en) Method and system for automatic recovery of an embedded operating system
CN109062598A (en) A kind of safe OTA upgrade method and system
CN103106083B (en) A kind of loading method of firmware and device
CN102541595A (en) Method and device for upgrading intelligent device and intelligent device
CN103179551A (en) Over-the-air upgrading method and over-the-air upgrading system
CN103530121A (en) Method of compatibility of multiple hardware platforms by RRU single software version
CN106775873B (en) Method and equipment for updating mobile phone software and acquiring patch file
CN110597545A (en) Hot patch intelligent upgrading method and system based on OTA component
CN111443951A (en) System starting method and system starting device
CN108874410B (en) Patch management method and device
CN106775874A (en) The method for upgrading system of terminal device
CN104991805A (en) Intelligent device and system disaster recovery backup control method thereof
CN112804071A (en) On-line upgrading method, upgrading file providing method, equipment and storage medium
WO2014187401A1 (en) Method and device for remote base station version installation
CN111309388A (en) Automatic rollback system and method for system software version of device
CN113961224B (en) Android-terminal-based application program updating method and system
CN101193396B (en) A forceful upgrade method for remote RF unit software in wireless communication system
CN111949290B (en) Hot patch management method and device, electronic equipment and storage medium
CN114995845A (en) OTA (over the air) upgrading method and device
CN105354060A (en) Wifi module firmware upgrade method and apparatus based on set-top box

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20200724