Method and device for processing soft firmware version of baseband board on base station and base station

Abstract

The invention provides a soft firmware version processing method and device for a baseband board on a base station and the base station, and relates to the wireless communication technology, and the specific implementation scheme is as follows: determining whether the starting mode of the baseband board is a hard-disk-free starting mode or not; when the starting mode of the baseband board is a hard disk-free starting mode, determining a soft firmware target version file of the baseband board stored under a first path on a main control board of the base station; determining a soft firmware version file of the baseband board stored in the second path on the main control board; and upgrading the soft firmware version of the baseband board based on the soft firmware target version file under the first path and the soft firmware version file under the second path. According to the technical scheme, updating, maintaining and starting of the soft firmware version can be normally carried out under the condition that no hard disk exists on the baseband board of the base station or the hard disk breaks down, the safety and reliability of the soft firmware of the base station are improved, and normal operation is prevented from being affected by hard disk damage or data loss.

Description

Technical Field

[0001] The present disclosure relates to wireless communication technology, and in particular to a method and device for processing the software and firmware version of a baseband board on a base station, a base station, and a storage medium. Background Art

[0002] A wireless communication base station generally includes a main control board and one or more baseband boards. Traditional baseband boards have independent processors, memory, and hard disks. The startup and synchronization / upgrade methods of traditional baseband boards are all based on hard disks.

[0003] However, there is currently a lack of effective means for upgrading and starting the software and firmware of a baseband board without a hard disk. Summary of the invention

[0004] The present invention provides a method and device for processing the software and firmware version of a baseband board on a base station, a base station, and a storage medium.

[0005] According to a first aspect of the present disclosure, a method for processing a software and firmware version of a baseband board on a base station is provided, comprising:

[0006] Determine whether the boot mode of the baseband board is the boot mode without hard disk;

[0007] When the boot mode of the baseband board is a boot mode without a hard disk, determining a target version file of the software and firmware of the baseband board stored in a first path on the main control board of the base station;

[0008] Determine the firmware version file of the baseband board stored in the second path on the main control board;

[0009] The firmware version of the baseband board is upgraded based on the firmware target version file in the first path and the firmware version file in the second path.

[0010] According to a second aspect of the present disclosure, a device for processing a software and firmware version of a baseband board on a base station is provided, comprising:

[0011] The software management main agent module is used to determine whether the boot mode of the baseband board is a boot mode without a hard disk;

[0012] The software management main agent module is also used to determine the target version file of the software and firmware of the baseband board stored in the first path on the main control board of the base station when the startup mode of the baseband board is the non-hard disk startup mode;

[0013] The software management main agent module is also used to determine the software and firmware version file of the baseband board stored in the second path on the main control board;

[0014] The software management main agent module is also used to upgrade the firmware version of the baseband board based on the firmware target version file under the first path and the firmware version file under the second path.

[0015] According to a third aspect of the present disclosure, a base station is provided, including:

[0016] Main control board;

[0017] one or more baseband boards;

[0018] one or more processors;

[0019] The processor is used to call instructions so that the base station executes the method of the first aspect mentioned above.

[0020] According to a fourth aspect of the present disclosure, a processor-readable storage medium is provided, which stores a computer program, and the computer program is used to enable a processor to execute the method of the first aspect.

[0021] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program, and the computer program can implement the method of the first aspect when executed by a processor.

[0022] According to the technical solution disclosed in the present invention, it is possible to update, maintain and start the software and firmware versions normally even when there is no hard disk or the hard disk fails on the baseband board of the base station, thereby improving the security and reliability of the base station software and firmware, avoiding the impact of hard disk damage or data loss on normal operation, and realizing unified management and maintenance of the base station software and firmware, making it convenient to update the software and firmware versions and troubleshoot.

[0023] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure.

[0025] Figure 1 It is a flowchart of a method for processing the software and firmware version of a baseband board on a base station provided according to an embodiment of the present disclosure;

[0026] Figure 2 It is a flowchart of another method for processing the software and firmware version of a baseband board on a base station provided according to an embodiment of the present disclosure;

[0027] Figure 3 It is a flowchart of another method for processing the software and firmware version of a baseband board on a base station provided according to an embodiment of the present disclosure;

[0028] Figure 4 It is a structural block diagram of a software and firmware version processing device of a baseband board on a base station provided according to an embodiment of the present disclosure;

[0029] Figure 5 It is a flowchart of starting a baseband board without a hard disk provided according to an embodiment of the present disclosure;

[0030] Figure 6 It is a flowchart of synchronization / upgrade of software and firmware versions of a baseband board without a hard disk provided in accordance with an embodiment of the present disclosure;

[0031] Figure 7 It is a structural block diagram of a base station provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] In the embodiments of the present disclosure, the term "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0033] The term "plurality" in the embodiments of the present disclosure refers to two or more than two, and other quantifiers are similar thereto.

[0034] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0035] The disclosed embodiments provide a method, device, base station and storage medium for processing the software and firmware version of a baseband board on a base station, so that when there is no hard disk or the hard disk fails on the baseband board of the base station, the software and firmware version and the software version of the EPLD can be updated, maintained and started normally, thereby improving the security and reliability of the base station software and firmware, avoiding the impact of hard disk damage or data loss on normal operation, and realizing unified management and maintenance of the base station software and firmware, which is easier to operate and convenient for updating the software and firmware version and troubleshooting.

[0036] Among them, the method and the device are based on the same application concept. Since the method and the device solve the problem in a similar principle, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0037] Figure 11 is a flowchart of a method for processing the firmware version of a baseband board on a base station provided by an embodiment of the present disclosure. It should be noted that the method involved in the embodiment of the present disclosure can be applied to a network device, which can be a base station. Figure 1 As shown, the method for processing the software and firmware version of the baseband board on the base station includes the following steps:

[0038] Step 101, determining whether the boot mode of the baseband board is a boot mode without a hard disk.

[0039] In some embodiments of the present disclosure, the hardware type of the baseband board may be determined; and based on the hardware type, it may be determined whether the booting mode of the baseband board is a booting mode without a hard disk.

[0040] Optionally, when the hardware version of the baseband board is different, the corresponding startup method is also different. Among them, the hardware version of the baseband board includes with a hard disk or without a hard disk. The startup method of the baseband board with a hard disk is to pre-install a solid-state drive (SSD) on each baseband board and store the startup file in the SSD. When it is necessary to start, read the startup file from the SSD and load the read startup file into the memory. The startup method of the baseband board without a hard disk is different from the startup method of the baseband board with a hard disk. Optionally, when a hard disk failure occurs in a baseband board with a hard disk, it can be regarded as a baseband board without a hard disk. Alternatively, the baseband board in this article can also be a new baseband board, that is, the baseband board can be a baseband board without a hard disk.

[0041] Step 102, when the boot mode of the baseband board is the boot mode without hard disk, determine the target version file of the software and firmware of the baseband board stored in the first path on the main control board of the base station.

[0042] Optionally, when it is determined that the boot mode of the baseband board is a boot mode without a hard disk, it means that the baseband board is a baseband board without a hard disk, or that the hard disk of the baseband board with a hard disk is faulty. At this time, the software and firmware target version file of the baseband board stored in the first path on the main control board of the base station can be used first to facilitate the subsequent use of the software and firmware target version file of the baseband board stored in the first path on the main control board for startup or synchronous upgrade.

[0043] In some embodiments of the present disclosure, the first path may be a software package version path on the main control board. The software package version path on the main control board may be used to store the target version files of the firmware of the baseband board and other software package target version files.

[0044] In some embodiments of the present disclosure, the target version file of the baseband board's firmware can be downloaded from a remote server to a first path on the main control board via a network to uniformly maintain and upgrade the baseband board's firmware version.

[0045] Optionally, in some embodiments, the startup mode of the baseband board is a hard disk startup mode, which means that the baseband board is a hard disk baseband board, and the startup mode of the hard disk baseband board can be used to start the baseband board. For example, the hard disk of the hard disk baseband board stores the startup file and the software and firmware version file. When the hard disk baseband board is started, the hard disk baseband board reads the startup file from the hard disk, loads the startup file into the memory of the hard disk baseband board, and executes the initialization program to complete the startup of the hard disk baseband board.

[0046] Step 103, determine the software and firmware version file of the baseband board stored in the second path on the main control board.

[0047] In some embodiments of the present disclosure, the second path may be a path on the main control board for storing the baseband board version.

[0048] Optionally, the above step of "determining the target version file of the software and firmware of the baseband board stored in the first path on the main control board of the base station" and step 103 can be exchanged in order or executed simultaneously.

[0049] Step 104: Upgrade the firmware version of the baseband board based on the firmware target version file in the first path and the firmware version file in the second path.

[0050] Optionally, in some embodiments, after determining the target version file of the software and firmware under the first path on the main control board and the software and firmware version file of the baseband board stored under the second path, the target version file of the software and firmware of the baseband board and the software and firmware version file of the baseband board are compared. When the comparison result is inconsistent versions or missing versions, the target version file of the software and firmware under the first path on the main control board is copied to the second path on the main control board, and the baseband board that lacks the software and firmware version file is reset to complete the upgrade of the software and firmware version of the baseband board. In the embodiments of the present disclosure, the software and firmware version of the baseband board can be upgraded normally even when there is no hard disk on the baseband board or the hard disk fails, which improves the security and reliability of the base station software and firmware and avoids the normal operation affected by hard disk damage or data loss.

[0051] It should be noted that when the baseband board is started, the hardware version of the baseband board needs to be determined to determine the startup method of the baseband board and check whether the firmware version of the baseband board needs to be upgraded. The hardware presence message sent by the baseband board to the main control board includes the hardware version information of the baseband board. Figure 2 FIG. 1 is a flow chart of another method for processing the software and firmware version of a baseband board on a base station provided by an embodiment of the present disclosure. Figure 2 As shown, the method for processing the software and firmware version of the baseband board on the base station includes the following steps:

[0052] Step 201, after receiving the hardware in-place board message, determine whether the boot mode of the baseband board is a boot mode without a hard disk.

[0053] Among them, in some embodiments, the above-mentioned hardware in place board card message includes a hardware in place message.

[0054] The hardware in-place board message refers to basic operation information during the period when the baseband board is in place. The baseband board in place means that the baseband board is actually powered on and located in a suitable position in the slot.

[0055] The hardware presence message is used to describe the hardware version information of the baseband board to determine the startup method of the baseband board.

[0056] In some embodiments, after receiving the hardware in place board message sent by the baseband board, the main control board of the base station can determine whether the startup mode of the baseband board in the base station is a non-hard disk startup mode. Among them, the optional implementation method of "determining whether the startup mode of the baseband board is a non-hard disk startup mode" can be found in Figure 1 Optional implementations of step 101 and Figure 1 Other related parts in the embodiments involved will not be described in detail here.

[0057] Step 202, when the boot mode of the baseband board is the boot mode without hard disk, determine the target version file of the software and firmware of the baseband board stored in the first path on the main control board of the base station.

[0058] In the embodiments of the present disclosure, step 202 may be implemented in any manner in the embodiments of the present disclosure, and the embodiments of the present disclosure do not limit this and will not be described in detail.

[0059] Step 203, determine the software and firmware version file of the baseband board stored in the second path on the main control board.

[0060] Optionally, the above step of "determining the target version file of the software and firmware of the baseband board stored in the first path on the main control board of the base station" and step 203 can be exchanged in order or executed simultaneously.

[0061] In the embodiments of the present disclosure, step 203 may be implemented in any manner in the embodiments of the present disclosure, and the embodiments of the present disclosure do not limit this and will not be described in detail.

[0062] Step 204: Upgrade the firmware version of the baseband board based on the firmware target version file in the first path and the firmware version file in the second path.

[0063] In some embodiments, when the firmware target version file under the first path is inconsistent with the firmware version file under the second path, or the firmware version file of the baseband board is missing under the second path, the firmware version of the baseband board is upgraded.

[0064] In some embodiments, based on the firmware target version file under the first path and the firmware version file under the second path, the specific implementation method of upgrading the firmware version of the baseband board is: comparing the firmware target version file under the first path with the firmware version file under the second path; determining that the firmware target version file under the first path is inconsistent with the firmware version file under the second path; storing the firmware target version file under the second path to upgrade the firmware version of the baseband board.

[0065] In some embodiments, based on the firmware target version file under the first path and the firmware version file under the second path, the specific implementation method of upgrading the firmware version of the baseband board is: comparing the firmware target version file under the first path with the firmware version file under the second path; if it is determined that the firmware version file of the baseband board is missing under the second path, the firmware target version file under the first path is stored in the second path to upgrade the firmware version of the baseband board.

[0066] In one possible implementation, terms such as "store", "copy", and "duplicate" may be used interchangeably.

[0067] It should be noted that since the baseband board without a hard disk does not have a hard disk to save the software and firmware target version file when it starts up, the software and firmware target version file needs to be stored in the baseband board version path on the main control board so that the underlying driver software can recognize the software and firmware target version file and start the baseband board.

[0068] In some embodiments, if the target version file of the software firmware under the first path is consistent with the software firmware version file under the second path, the baseband board is directly started.

[0069] Step 205: Reset the baseband board that is missing the software and firmware version file.

[0070] In some embodiments of the present disclosure, after the upgrade of the software and firmware version of the baseband board is completed, the baseband board that is missing the software and firmware version file is reset.

[0071] Step 206: After completing the upgrade of the software and firmware version of the baseband board, start the baseband board.

[0072] Optionally, in some embodiments, there may be one or more baseband boards in the base station. When there are multiple baseband boards in the base station, after the software and firmware version of the baseband board under the second path on the main control board is upgraded, the multiple baseband boards can be started directly by identifying the upgraded software and firmware target version under the second path on the main control board and loading the software and firmware target versions of the multiple baseband boards into the memory of the corresponding baseband board.

[0073] In some embodiments, when there are multiple baseband boards in a base station, the software and firmware version upgrade operation can be performed on multiple baseband boards in sequence, or the software and firmware version upgrade operation can be performed on multiple baseband boards in parallel. The software and firmware version upgrade order of the above baseband boards can be determined in combination with the actual startup process of the multiple baseband boards in the base station. This disclosure does not limit this and will not be repeated. Therefore, in the design mode of single main control board and multiple baseband boards, only one management station is needed to manage the base station to complete the version control of multiple baseband boards, which is easier to operate.

[0074] In the embodiment of the present disclosure, the software and firmware version can be upgraded and started normally even when there is no hard disk on the baseband board, which improves the security and reliability of the base station software and firmware and avoids the normal operation affected by hard disk damage or data loss. The unified management and maintenance of the base station software and firmware is realized, which facilitates the software and firmware version update and troubleshooting.

[0075] It should be noted that since the boot mode of the baseband board without hard disk is hard disk-free boot, during the synchronization / upgrade process of the processor firmware files of the baseband board without hard disk, it is only necessary to process the software version upgrade of the EPLD (Erasable Programmable Logic Device) related to the hardware device. Figure 3 FIG. 1 is a flow chart of another method for processing the firmware version of a baseband board on a base station according to an embodiment of the present disclosure. Figure 3 As shown, the method for processing the software and firmware version of the baseband board on the base station includes the following steps:

[0076] Step 301, determining whether the boot mode of the baseband board is a boot mode without a hard disk.

[0077] In the embodiments of the present disclosure, step 301 may be implemented in any manner in the embodiments of the present disclosure, and the embodiments of the present disclosure do not limit this and will not be described in detail.

[0078] Step 302, when the boot mode of the baseband board is the boot mode without hard disk, determine the target version file of the software and firmware of the baseband board stored in the first path on the main control board of the base station.

[0079] In the embodiments of the present disclosure, step 302 may be implemented in any manner in the embodiments of the present disclosure, and the embodiments of the present disclosure do not limit this and will not be described in detail.

[0080] Step 303, determine the software and firmware version file of the baseband board stored in the second path on the main control board.

[0081] Optionally, the above step of "determining the target version file of the software and firmware of the baseband board stored in the first path on the main control board of the base station" and step 303 can be exchanged in order or executed simultaneously.

[0082] In the embodiments of the present disclosure, step 303 may be implemented in any manner in the embodiments of the present disclosure, and the embodiments of the present disclosure do not limit this and will not be described in detail.

[0083] Step 304: Upgrade the firmware version of the baseband board based on the firmware target version file in the first path and the firmware version file in the second path.

[0084] In the embodiments of the present disclosure, step 304 may be implemented in any manner in the embodiments of the present disclosure, and the embodiments of the present disclosure do not limit this and will not be described in detail.

[0085] Step 305, determining the software version file of the EPLD in the memory on the baseband board.

[0086] It should be noted that in some embodiments of the present disclosure, the processor firmware version on the baseband board without hard disk booting also needs to be upgraded. Since the baseband board to be upgraded is booted without hard disk, only the software version of the EPLD related to the hardware device needs to be upgraded.

[0087] Step 306, determining the upgrade results of other software and firmware versions of the baseband board.

[0088] In some embodiments of the present disclosure, after the upgrade of other software and firmware versions of the baseband board is completed, the main control board sends a version synchronization response message to the baseband board to determine that the upgrade of other software and firmware versions of the baseband board is successful. Among them, other software and firmware refers to the software and firmware on the baseband board other than the software of the EPLD.

[0089] Step 307: Upgrade the software version of the EPLD of the baseband board according to the upgrade result and the software version file of the EPLD.

[0090] In one possible implementation, in response to the upgrade result being a successful upgrade, the software target version file of the EPLD stored in the first path is determined; the software version file of the EPLD is compared with the software target version file of the EPLD; when the software version file of the EPLD is inconsistent with the software target version file of the EPLD, the software target version file of the EPLD is sent to the memory of the baseband board.

[0091] It should be noted that when the software version file of EPLD is inconsistent with the software target version file of EPLD, the software target version file of EPLD is downloaded from the main control board to the memory of the baseband board through the remote call driver interface on the base station, and the software target version file of EPLD is reloaded by the underlying driver software. After completing the software version upgrade of the EPLD of the baseband board, the baseband board that has completed the EPLD upgrade automatically resets and sends a reset check message to the main control board. After receiving the reset check message, the main control board determines that the upgrade of the baseband board that needs to upgrade the EPLD is completed, and notifies the baseband board that has completed the upgrade to perform the reset process.

[0092] That is to say, when the software and firmware on the baseband board are synchronously upgraded, it is necessary to ensure that the software of the EPLD on the baseband board and other software and firmware on the baseband board other than the EPLD are successfully upgraded to complete the synchronous upgrade of the baseband board. Optionally, in some embodiments, there may be one or more baseband boards in the base station. When there are multiple baseband boards in the base station, the above steps 301 to 307 may be used for synchronous upgrade for each baseband board.

[0093] In some embodiments, the synchronous upgrade of each baseband board can be performed sequentially, or the synchronous upgrade of multiple baseband boards can be performed in parallel. This disclosure does not limit this and will not be repeated. Therefore, in the design mode of single main control board and multiple baseband boards, only one management station is needed to manage the base station to complete the version control of multiple baseband boards, which is easier to operate.

[0094] In the embodiments of the present disclosure, the firmware version and the software version of the EPLD can be updated, maintained and started normally even when there is no hard disk on the baseband board, which improves the security and reliability of the base station firmware and avoids the normal operation affected by hard disk damage or data loss. The unified management and maintenance of the base station firmware is achieved, which facilitates the firmware version update and troubleshooting. In the design mode of single main control board and multiple baseband boards, only one management station is needed to manage the base station, and the version control of multiple baseband boards can be completed, which is easier to operate.

[0095] Figure 4 It is a structural block diagram of a software and firmware version processing device of a baseband board on a base station provided according to an embodiment of the present disclosure.

[0096] like Figure 4 As shown, the software and firmware version processing device of the baseband board on the base station includes a software management main agent module 401, a device management main agent module 402 and a software management sub-agent module 403.

[0097] The software management main agent module 401 is used to determine whether the boot mode of the baseband board is a boot mode without a hard disk.

[0098] The software management main agent module 401 is also used to determine the target version file of the software and firmware of the baseband board stored in the first path on the main control board of the base station when the startup mode of the baseband board is the non-hard disk startup mode.

[0099] The software management main agent module 401 is also used to determine the software and firmware version file of the baseband board stored in the second path on the main control board.

[0100] The software management main agent module 401 is also used to upgrade the firmware version of the baseband board based on the firmware target version file in the first path and the firmware version file in the second path.

[0101] In some embodiments of the present disclosure, the software management main agent module 401 is specifically used to determine the hardware type of the baseband board; and determine whether the boot mode of the baseband board is a hard disk-free boot mode according to the hardware type.

[0102] In some embodiments of the present disclosure, the software management main agent module 401 is specifically used to compare the software and firmware target version file under the first path with the software and firmware version file under the second path; determine that the software and firmware target version file under the first path is inconsistent with the software and firmware version file under the second path, or that the software and firmware version file of the baseband board is missing under the second path; store the software and firmware target version file in the second path to upgrade the software and firmware version of the baseband board.

[0103] In some embodiments of the present disclosure, the software and firmware version processing device of the baseband board on the base station further includes a device management main agent module 402, which is used to send a hardware in place board card message to the software management main agent module 401.

[0104] The software management main agent module 401 is also specifically used for: after receiving the hardware in place board card message, determining whether the boot mode of the baseband board is the boot mode without hard disk; wherein the hardware in place board card message includes the hardware in place information.

[0105] In some embodiments of the present disclosure, the software management main agent module 401 is further specifically used to reset the baseband board that is missing the software and firmware version file.

[0106] In some embodiments of the present disclosure, the software and firmware version processing device of the baseband board on the base station also includes a software management subagent module 403, which is used to determine whether the startup mode of the baseband board is a hard disk-free startup mode after receiving a synchronization message from the software management main agent module.

[0107] Among them, the software management sub-agent module 403 is specifically used to send a synchronization request message to the software management main agent module when it is determined that the startup mode of the baseband board is a hard disk-free startup mode, and determine whether the software version file of the erasable and programmable logic device EPLD in the memory on the baseband board is consistent with the software target version file of the EPLD stored in the first path.

[0108] In some embodiments of the present disclosure, the software management subagent module 403 is specifically used to receive a synchronization response message sent by the software management main agent module, determine the upgrade results of other software and firmware versions of the baseband board, and upgrade the software version of the EPLD on the baseband board according to the upgrade results and the software version file of the EPLD.

[0109] In some embodiments of the present disclosure, the software management subagent module 403 is specifically used to: in response to an upgrade result being a successful upgrade, determine the software target version file of the EPLD stored in the first path; compare the software version file of the EPLD with the software target version file of the EPLD; when the software version file of the EPLD is inconsistent with the software target version file of the EPLD, send the software target version file of the EPLD to the memory of the baseband board.

[0110] In some embodiments of the present disclosure, the software management sub-agent module 403 is further configured to send a reset check message to the software management main agent module when the EPLD software version of the baseband board is successfully upgraded. The software management main agent module 401 is further configured to notify the baseband board to perform a reset process based on the received reset check message.

[0111] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0112] It is worth noting that the method for processing the software and firmware version of the baseband board on the base station provided in the embodiment of the present disclosure can be applied to the startup of the baseband board without a hard disk and the synchronization / upgrade of the software and firmware version of the baseband board without a hard disk. Optionally, the present disclosure can implement unified version maintenance and upgrade of the baseband board of the wireless communication base station based on the maintenance control system (Operation Maintenance, OM for short) when the local memory is missing or the local memory is damaged. Thereby improving the reliability and flexibility of the wireless communication base station. To facilitate understanding of the software and firmware version processing method of the baseband board on the base station provided in the embodiment of the present disclosure, it is explained below according to the application scenario.

[0113] (1) Booting the baseband board without a hard disk. Figure 5 This is a flowchart of starting a baseband board without a hard disk provided according to an embodiment of the present disclosure. The process of starting a baseband board without a hard disk can be as follows:

[0114] After the software management main agent module receives the hardware in-place board card message sent by the device management main agent module, the hardware version of the baseband board is determined according to the hardware in-place board card message. Among them, the hardware version of the baseband board includes two types: no hard disk and with hard disk. When the hardware version of the baseband board is no hard disk, the startup mode of the baseband board is determined to be no hard disk startup.

[0115] After determining the startup mode of the baseband board, determine the target version file of the baseband board's software and firmware stored in the software package version path on the main control board of the base station, and determine the software and firmware version file of the baseband board stored in the baseband board version path on the main control board.

[0116] After determining the target version file of the baseband board's firmware and the baseband board's firmware version file, compare the two files. If the comparison result shows that the versions are inconsistent or missing, copy the target version file of the baseband board's firmware under the software package version path on the main control board to the baseband board version path on the main control board, and reset the baseband board.

[0117] After completing the reset process, the baseband board can start the operation by loading the software and firmware version file under the baseband board version path on the main control board.

[0118] (2) Synchronize / upgrade the firmware version of the baseband board without a hard disk. Figure 6 The present invention is a flowchart of synchronizing / upgrading the software and firmware version of a baseband board without a hard disk provided in accordance with an embodiment of the present disclosure.

[0119] After determining that the baseband board is booted without a hard disk according to the hardware version, the software management sub-agent module sends a version synchronization request message to the software management main agent module, and compares the software version file of the EPLD in the memory of the baseband board with the software target version file of the EPLD under the software package version path on the main control board.

[0120] After the software management main agent module receives the version synchronization request message, it compares the baseband board's firmware target version file stored in the software package version path on the main control board with the baseband board's firmware version file stored in the baseband board version path on the main control board.

[0121] When the comparison result is inconsistent or missing versions, the target version file of the baseband board's firmware under the software package version path on the main control board is copied to the baseband board version path on the main control board, and a version synchronization response message is sent to the software management subagent module.

[0122] After the software management sub-agent module receives the version synchronization response message, it confirms that the upgrade of other software and firmware versions of the baseband board is completed. When the comparison result of the EPLD software version file in the memory of the baseband board and the EPLD software target version file under the software package version path of the main control board is inconsistent or missing, the EPLD software target version file is sent to the memory of the baseband board to complete the upgrade. The baseband board that completes the EPLD upgrade automatically performs the reset process.

[0123] After the upgrade is completed, the software management sub-agent module sends a reset check message to the software management main agent module. The software management main agent module confirms that the baseband board upgrade is completed and notifies all baseband boards that have completed the software and firmware version upgrade to reset.

[0124] Figure 7It is a structural block diagram of a base station provided according to an embodiment of the present disclosure. The base station may include multiple cells that provide services for terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or other names. The base station may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The base station may also coordinate the attribute management of the air interface. For example, the base station involved in the embodiments of the present disclosure may be a base station (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a base station (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the base station may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.

[0125] like Figure 7 As shown, the base station includes a main control board 701, one or more baseband boards 702, one or more processors 703, a memory 704 and a bus interface.

[0126] The main control board 701 stores the target version file of the software and firmware of the baseband board 702 and the target version file of the software and firmware of the EPLD, which can be used for the software and firmware version management and version upgrade of the baseband board or the processor. The main control board 701 also stores the module corresponding to the software and firmware version processing method of the baseband board on the base station in the embodiment of the present disclosure (for example, the attached Figure 4The software management main agent module 401 and the device management main agent module 402 are shown.

[0127] The baseband board 702 stores the software firmware version file and the software target version file of the EPLD, which can be used for comparison with the software firmware target version file and the software target version file of the EPLD. The baseband board 702 also stores a module corresponding to the software firmware version processing method of the baseband board on the base station in the embodiment of the present disclosure (for example, the attached Figure 4 The software management subagent module 403 is shown.

[0128] Among them, Figure 7 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 703 and memory represented by memory 704. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface.

[0129] The processor 703 is responsible for calling instructions so that the base station executes the method for processing the software and firmware version of the baseband board on the base station provided in the embodiment of the present disclosure. The processor 703 may also be responsible for managing the bus architecture and general processing. The memory 704 may store the data used by the processor 703 when performing operations and the computer program corresponding to the method for processing the software and firmware version of the baseband board on the base station provided in the embodiment of the present disclosure. The processor 703 calls the computer program stored in the memory 704 to execute any of the methods provided in the embodiment of the present disclosure according to the executable instructions obtained.

[0130] Optionally, the processor 703 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array) or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.

[0131] In one implementation, the processor 703 may include a transceiver for implementing the receiving and sending functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0132] In one implementation, the processor 703 may store a computer program, which runs on the processor 703 and enables the base station to execute the method described in the above method embodiment. The computer program may be fixed in the processor 703, in which case the processor 703 may be implemented by hardware.

[0133] Memory 704 is the processor-readable storage medium provided in the present disclosure. Among them, the processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc. In one implementation, the base station may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiment. The processor and transceiver described in the present disclosure can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0134] Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present disclosure.

[0135] The present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0136] The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0137] It should be noted that the division of modules / units in the embodiments of the present disclosure is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module / unit in each embodiment of the present disclosure may be integrated into a processing module / unit, or each module / unit may exist physically separately, or two or more modules / units may be integrated into one unit. The above-mentioned integrated modules / units may be implemented in the form of hardware or in the form of software functional modules / units.

[0138] If the integrated module / unit is implemented in the form of a software function module / unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0139] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) containing computer-usable program code.

[0140] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0141] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0142] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0143] Obviously, those skilled in the art can make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is also intended to include these modifications and variations.

Claims

1. A method for processing the software and firmware version of a baseband board on a base station, characterized in that: include: Determine whether the boot mode of the baseband board is a boot mode without a hard disk; When the boot mode of the baseband board is the hard disk-free boot mode, determining a target version file of the software and firmware of the baseband board stored in a first path on the main control board of the base station; Determine the software and firmware version file of the baseband board stored in the second path on the main control board; The firmware version of the baseband board is upgraded based on the firmware target version file in the first path and the firmware version file in the second path.

2. The method according to claim 1, characterized in that The determining whether the boot mode of the baseband board is a boot mode without a hard disk comprises: Determine the hardware board type of the baseband board; According to the hardware board type, it is determined whether the boot mode of the baseband board is a boot mode without a hard disk.

3. The method according to claim 1, characterized in that The upgrading the firmware version of the baseband board based on the firmware target version file in the first path and the firmware version file in the second path includes: Compare the firmware target version file in the first path with the firmware version file in the second path; Determine that the firmware target version file in the first path is inconsistent with the firmware version file in the second path, or that the firmware version file of the baseband board is missing in the second path; The target version file of the software and firmware is stored in the second path to upgrade the software and firmware version of the baseband board.

4. The method according to any one of claims 1 to 3, characterized in that The determining whether the boot mode of the baseband board is a boot mode without a hard disk comprises: After receiving the hardware in place board card message, determine whether the boot mode of the baseband board is a boot mode without a hard disk; wherein the hardware in place board card message includes hardware in place information; The method further comprises: After completing the upgrade of the software and firmware version of the baseband board, the baseband board is started.

5. The method according to claim 4, characterized in that The method further comprises: Reset the baseband board that is missing the software and firmware version file.

6. The method according to any one of claims 1 to 3, characterized in that The method further comprises: Determine the software version file of the erasable programmable logic device EPLD in the memory of the baseband board; Determine the upgrade results of other software and firmware versions of the baseband board; The software version of the EPLD of the baseband board is upgraded according to the upgrade result and the software version file of the EPLD.

7. The method according to claim 6, characterized in that The step of upgrading the software version of the EPLD of the baseband board according to the upgrade result and the software version file of the EPLD includes: In response to the upgrade result being a successful upgrade, determining a software target version file of the EPLD stored in the first path; Comparing the software version file of the EPLD with the software target version file of the EPLD; When the software version file of the EPLD is inconsistent with the software target version file of the EPLD, the software target version file of the EPLD is sent to the memory of the baseband board.

8. The method according to claim 6, characterized in that The method further comprises: The baseband board is notified to perform a reset process.

9. A software and firmware version processing device for a baseband board on a base station, characterized in that: include: A software management main agent module is used to determine whether the boot mode of the baseband board is a boot mode without a hard disk; The software management main agent module is further used to determine the target version file of the software and firmware of the baseband board stored in the first path on the main control board of the base station when the startup mode of the baseband board is the hard disk-free startup mode; The software management main agent module is also used to determine the software and firmware version file of the baseband board stored in the second path on the main control board; The software management master agent module is also used to upgrade the firmware version of the baseband board based on the firmware target version file under the first path and the firmware version file under the second path.

10. The device according to claim 9, characterized in that The software management main agent module is specifically used for: Determine the hardware board type of the baseband board; According to the hardware board type, it is determined whether the boot mode of the baseband board is a boot mode without a hard disk.

11. The device according to claim 9, characterized in that The software management main agent module is specifically used for: Compare the firmware target version file in the first path with the firmware version file in the second path; Determine that the firmware target version file in the first path is inconsistent with the firmware version file in the second path, or that the firmware version file of the baseband board is missing in the second path; The target version file of the software and firmware is stored in the second path to upgrade the software and firmware version of the baseband board.

12. The device according to any one of claims 9 to 11, characterized in that The device also includes: The device management master agent module is used to send a hardware board presence message to the software management master agent module; The software management master agent module is specifically used to: after receiving the hardware in place board card message, determine whether the boot mode of the baseband board is a boot mode without a hard disk; wherein the hardware in place board card message includes hardware in place information.

13. The device according to claim 12, characterized in that The software management main agent module is also used to reset the baseband board that lacks the software and firmware version file.

14. The device according to any one of claims 9 to 11, characterized in that The device also includes: A software management sub-agent module, configured to determine whether the boot mode of the baseband board is a boot mode without a hard disk after receiving a synchronization message from the software management main agent module; The software management sub-agent module is further used to send a synchronization request message to the software management main agent module when determining that the startup mode of the baseband board is a non-hard disk startup mode, and determine whether the software version file of the erasable programmable logic device EPLD in the memory of the baseband board is consistent with the software target version file of the EPLD stored in the first path; The software management sub-agent module is also used to receive the synchronization response message sent by the software management main agent module, determine the upgrade results of other software and firmware versions of the baseband board, and upgrade the software version of the EPLD on the baseband board according to the upgrade results and the software version file of the EPLD.

15. The device according to claim 14, characterized in that The software management subagent module is specifically used for: In response to the upgrade result being a successful upgrade, determining a software target version file of the EPLD stored in the first path; Comparing the software version file of the EPLD with the software target version file of the EPLD; When the software version file of the EPLD is inconsistent with the software target version file of the EPLD, the software target version file of the EPLD is sent to the memory of the baseband board.

16. The device according to claim 14, characterized in that The software management sub-agent module is further configured to send a reset check message to the software management main agent module when the EPLD software version of the baseband board is successfully upgraded; The software management main agent module is also used to notify the baseband board to perform reset processing based on the received reset check message.

17. A base station, characterized in that: include: Main control board; one or more baseband boards; one or more processors; The processor is used to call instructions so that the base station executes the software and firmware version processing method of the baseband board on the base station according to any one of claims 1-8.

18. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to cause the processor to execute the method according to any one of claims 1 to 8.

Images