Version file updating method and device, base station and storage medium

Abstract

The embodiment of the invention provides a version file updating method and device, a base station and a storage medium. The method comprises the steps that the name of a first version file and the version number of the first version file recorded in a board card configuration file are determined; each first version file corresponds to one hardware implementation type of one board card; determining the name of a second version file currently operated by the base station and the version number of the second version file; wherein each second version file corresponds to one hardware implementation type of one board card; matching the first version file with the second version file, and determining a difference version file; downloading the difference version file from the version server, and updating the version file based on the difference version file. The method and the device are used for accurately downloading the required version file by taking the hardware implementation type of the board card as fine granularity, saving the time required by the version upgrading process, saving the disk space of the board card and improving the operation efficiency of a base station.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a version file updating method, device, base station and storage medium. Background Art

[0002] Base stations contain multiple types of boards, each of which requires loading a version file during startup. As operator requirements gradually converge, the version code layer has evolved from single-mode versions supporting only FDD (Frequency Division Dual) and NR (New Radio) to dual-mode or multi-mode versions supporting FDD NR, TDD (Time Division Duplexing) NR, TDD LTE (Long Term Evolution), FDD LTE, and NB IoT (Narrow Band Internet of Things).

[0003] In terms of hardware physics, as my country's chip technology continues to make new breakthroughs and other high-tech materials continue to develop and apply, the types of boards and cards are gradually developing towards the characteristics of rich hardware implementation types, controllable costs, and higher compatibility.

[0004] For example, a board used to implement a certain function may have multiple hardware implementation types, and each hardware implementation type has a corresponding version file.

[0005] Currently, when a version file needs to be updated, if the version package clipping switch is turned on, the version files for all hardware implementation types supported by each application type must be downloaded to the base station based on the pre-planned board configuration. This fails to minimize and accurately download to the version storage path, thus affecting the operation of files in the version storage path.

[0006] If the version package clipping switch is off, the base station will download all version files after decompressing the version package to the version storage path. This one-size-fits-all download method will cause unnecessary consumption of disk space. Summary of the Invention

[0007] The purpose of the embodiments of the present application is to provide a version file update method, device, base station, and storage medium to achieve fine-grained downloading of required version files based on the hardware implementation type of the board, thereby saving the time required for the version upgrade process, saving board disk space, and improving base station operating efficiency. The specific technical solution is as follows:

[0008] In a first aspect of the present application, a method for updating a version file is provided, which is applied to a base station. The method includes

[0009] Determine the name of the first version file recorded in the board configuration file and the version number of the first version file; wherein, each of the first version files corresponds to a hardware implementation type of a board;

[0010] Determine the name of the second version file currently running on the base station and the version number of the second version file; wherein, each of the second version files corresponds to a hardware implementation type of a board;

[0011] Match the first version file and the second version file to determine the differential version file;

[0012] Download the differential version file from the version server and update the version file based on the differential version file.

[0013] Optionally, the differential version file includes: a first version file corresponding to the same board and having a different name from the second version file due to different hardware implementation types; and / or a first version file corresponding to the same hardware implementation type of the same board but having a different version number from the second version file; and / or a version file corresponding to a newly added board that is missing from the second version file due to the addition of the new board.

[0014] Optionally, the board configuration file is updated in response to a change in the board or a change in the version file corresponding to the board.

[0015] Optionally, the base station is pre-configured with version server configuration information; the version server configuration information includes: the IP address of the version server and the login information of the version server;

[0016] The step of downloading the differential version file from the version server includes:

[0017] Based on the version server configuration information, access the version server, query and download the differential version file on the version server.

[0018] Optionally, the download path of the differential version file is the running storage path of the base station.

[0019] Optionally, the step of updating the version file based on the differential version file includes: transferring the second version file currently running on the base station to an alternate path and loading and running the differential version file.

[0020] In a second aspect of the present application, a base station is provided, including a memory, a transceiver, and a processor:

[0021] A memory for storing computer programs; a transceiver for transmitting and receiving data under the control of the processor; a processor for reading the computer programs in the memory and performing the following operations:

[0022] Determine the name of the first version file recorded in the board configuration file and the version number of the first version file; wherein, each of the first version files corresponds to a hardware implementation type of a board;

[0023] Determine the name of the second version file currently running on the base station and the version number of the second version file; wherein, each of the second version files corresponds to a hardware implementation type of a board;

[0024] Match the first version file and the second version file to determine the differential version file;

[0025] Download the differential version file from the version server and update the version file based on the differential version file. Optionally, the differential version file includes: a first version file corresponding to the same board and having a different name from the second version file due to different hardware implementation types; and / or a first version file corresponding to the same hardware implementation type of the same board but having a different version number from the second version file; and / or a version file corresponding to a newly added board that is missing in the second version file due to the addition of the new board.

[0026] Optionally, the board configuration file is updated in response to a change in the board or a change in the version file corresponding to the board.

[0027] Optionally, the base station is pre-configured with version server configuration information; the version server configuration information includes: the IP address of the version server and the login information of the version server;

[0028] The step of downloading the differential version file from the version server specifically includes:

[0029] Based on the version server configuration information, access the version server, query and download the differential version file on the version server.

[0030] Optionally, the download path of the differential version file is the running storage path of the base station.

[0031] Optionally, the step of updating the version file based on the differential version file specifically includes: transferring the second version file currently running on the base station to an alternate path and loading and running the differential version file.

[0032] In the third aspect of the present application, there is provided a version file update device applied to a base station, the device includes:

[0033] A first determination module, configured to determine the name of the first version file recorded in the board configuration file and the version number of the first version file; wherein, each of the first version files corresponds to a hardware implementation type of a board.

[0034] A second determination module, configured to determine the name of the second version file currently running on the base station and the version number of the second version file; wherein, each of the second version files corresponds to a hardware implementation type of a board.

[0035] A matching module, configured to match the first version file and the second version file to determine a differential version file.

[0036] An update module, configured to download the differential version file from a version server and update the version file based on the differential version file.

[0037] Optionally, the differential version file includes: a first version file corresponding to the same board and having a different name from the second version file due to different hardware implementation types; and / or a first version file corresponding to the same hardware implementation type of the same board but having a different version number from the second version file; and / or a version file corresponding to a newly added board that is missing from the second version file due to the addition of the board.

[0038] Optionally, the board configuration file is updated in response to a change in the board or a change in the version file corresponding to the board.

[0039] Optionally, the base station is pre-configured with version server configuration information; the version server configuration information includes: the IP address of the version server and the login information of the version server.

[0040] The update module is specifically configured to: access the version server based on the version server configuration information, query and download the differential version file on the version server.

[0041] Optionally, the download path of the differential version file is the running storage path of the base station.

[0042] Optionally, the update module is specifically configured to: transfer the second version file currently running on the base station to an alternate path and load and run the differential version file.

[0043] In a fourth aspect of the present application, a computer-readable storage medium is provided, in which a computer program is stored, and when the computer program is executed by a processor, the steps of any version file update method provided by the embodiments of the present application are implemented.

[0044] In a fifth aspect of the present application, there is also provided a computer program product including instructions, which, when running on a computer, cause the computer to execute the version file update method described in any one of the above.

[0045] Advantageous effects of the embodiments of the present application:

[0046] The version file update method, device, base station and storage medium provided by the embodiments of the present application, the base station determines the name and version number of the first version file recorded in the board configuration file; wherein, each first version file corresponds to a hardware implementation type of a board; determines the name and version number of the second version file currently running on the base station; wherein, each second version file corresponds to a hardware implementation type of a board; matches the first version file and the second version file to determine the differential version file; downloads the differential version file from the version server, and updates the version file based on the differential version file.

[0047] It can be seen that the differential version file is determined by matching the name and version number of the first version file recorded in the board configuration file and the name and version number of the second version file currently running on the base station. Since it is considered that there may be multiple hardware implementation types for the boards of the same application type, and the version files corresponding to each hardware implementation type are different, in the case where the hardware implementation type of the board changes, the determined differential version file is the version file corresponding to the changed hardware implementation type of the board, and only the version file corresponding to the changed hardware implementation type needs to be downloaded. With the continuous breakthroughs in chip technology and the continuous development and application of other high-tech materials, the types of hardware implementation types of boards of the same application type are gradually enriched. Therefore, in the process of version file update, only downloading the version file corresponding to a single required hardware implementation type can reduce the number of files downloaded to the base station, save the time required for the version upgrade process, and can also greatly save the board disk space and improve the operation efficiency of the base station.

[0048] Moreover, in the embodiments of the present application, the base station actively initiates the version update process. The base station does not need to upload any files to the management station, so the management station does not need to process a large number of files uploaded by many base stations at the same time, which will not cause a high load on the management station, and the way of the base station actively performing version update is more convenient for operation and maintenance.

[0049] Of course, it is not necessary for any product or method implementing the present application to achieve all the above advantages at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other embodiments can also be obtained based on these drawings.

[0051] Figure 1 A schematic diagram of a system architecture applicable to the embodiments of the present application;

[0052] Figure 2 A schematic flowchart of a method for updating a version file provided by the embodiments of the present application;

[0053] Figure 3 Another schematic flowchart of a method for updating a version file provided by the embodiments of the present application;

[0054] Figure 4 A schematic structural diagram of a version file updating device provided by the embodiments of the present application;

[0055] Figure 5 A schematic structural diagram of a base station provided by the embodiments of the present application. Detailed implementation manners

[0056] In the embodiments of the present application, the term "and / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0057] In the embodiments of the present application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0058] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0059] The technical solutions provided by the embodiments of this application can be applied to a variety of systems, especially 5G systems. For example, the applicable systems can be the global system of mobile communication (GSM) system, code division multiple access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) general packet radio service (GPRS) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, long term evolution advanced (LTE-A) system, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) system, 5G New Radio (NR) system, etc. Both terminal devices and network devices are included in these multiple systems. The system may also include a core network part, such as an evolved packet system (EPS), 5G system (5GS), etc.

[0060] A base station contains multiple types of boards, and the boards need to load version files during startup. Currently, when the version file needs to be updated, if the version package trimming switch is in the open state, then according to the pre-planned board configuration, for each type of board with an application type, all version files of the hardware implementation types supported by this application type need to be downloaded to the base station. In this way, it is impossible to download to the version storage path in a minimized and precise manner, thus affecting the operation of the files in the version storage path.

[0061] If the version package trimming switch is in the closed state, then all version files after decompressing the version package will be downloaded to the version storage path. Such a one-size-fits-all download method will cause unnecessary consumption of disk space.

[0062] To solve the above technical problems, the embodiments of this application provide a method for updating version files. For the convenience of understanding, first, in combination with Figure 1 the system architecture applicable to the embodiments of this application will be described. Figure 1FIG. 0 shows a schematic diagram of a system architecture applicable to embodiments of the present application. The system architecture in the embodiments of the present application includes: base station 110, base station 111, base station 112, version server 113, and configuration information update device 114. As an example, Figure 1 FIG. 0 shows the connection relationships between three base stations and the version server, as well as the connection relationships between the three base stations and the configuration information update device.

[0063] Among them, the version server 113 can be a device for storing version files corresponding to the board cards. Whenever a new version file is released, the version server will download the new version package file from the server that releases the version file and decompress it to obtain each version package file. The version server communicates with the base stations during network transmission.

[0064] The configuration information update device 114 can be a device for storing and updating the board card configuration files, such as a computer used by the management personnel, etc. The board card configuration files are dynamically updated as the board cards change and the version files corresponding to the board cards are updated. The base stations obtain the board card configuration files from the configuration information update device 114.

[0065] For the manner in which the base stations obtain the board card configuration files from the configuration information update device 114, the embodiments of the present application do not make any limitations, and various implementation manners can be adopted.

[0066] As an example, the configuration information update device 114 is connected to multiple base stations and stores the board card configuration files corresponding to each base station. When the board cards of a certain base station change or the version files corresponding to the board cards are updated, the management personnel perform corresponding updates on the board card configuration files corresponding to the base station stored in the configuration information update device 114, and then manually import the updated board card configuration files into the base station.

[0067] As another example, for each base station, after the board cards of the base station change or the version files corresponding to the board cards are updated, the management personnel update the corresponding board card configuration files. The base stations can periodically access the configuration information update device 114 and download the new board card configuration files corresponding to themselves. Specifically, in the manner of ordinary patch files, using specific maintenance tools, such as LMT (Local Maintenance Terminal) or WebLMT (Web-based Local Maintenance Terminal), the files are downloaded to the default patch path of the base stations.

[0068] Figure 2 FIG. 21 exemplarily shows a flowchart of a version file update method provided by the embodiments of the present application, as Figure 2 shown, the method includes the following steps:

[0069] S201: Determine the name of the first version file and the version number of the first version file recorded in the board configuration file; wherein, each first version file corresponds to a hardware implementation type of a board.

[0070] In the embodiments of the present application, there are various types of boards in the base station. The application types are distinguished based on the functions of the boards. For example, there are main control boards for main control, baseband boards for implementing baseband signal processing, and the like.

[0071] For boards of the same application type, there can be multiple hardware implementation types. The hardware implementation types are distinguished based on the materials of the boards, the hardware structures of the boards, or the production platforms of the boards, etc. Specifically, with the continuous breakthroughs in chip technology and the continuous development and application of other high-tech materials, boards that achieve the same function can be produced using different materials, different technical means, or different production platforms. The hardware structures of the produced boards may be different, but they can be used as boards of the same application type.

[0072] For example, if the industry can produce three types of main control boards, then there are three hardware implementation types of the main control board. Correspondingly, each hardware implementation type corresponds to a version file.

[0073] In the embodiments of the present application, the base station obtains the board configuration file corresponding to itself. The board configuration file records the hardware implementation types of all the boards on the base station, the names of the version packet files corresponding to the hardware implementation types of the boards, and the version numbers.

[0074] The board configuration file can be a file in tabular form. As an example, see Table 1, which shows the board configuration file in tabular form.

[0075]

[0076] Table 1

[0077] As shown in Table 1, the board configuration file records the names of the n boards included in the base station, the hardware implementation types of each board, the names of the version packet files corresponding to the hardware implementation types of the boards, and the version numbers.

[0078] Taking board 1 as an example for illustration, if the industry can produce five types of board 1, then there are five hardware implementation types of board 1. Since different version packet files need to be loaded for boards 1 of different hardware implementation types, the five hardware implementation types of board 1 respectively correspond to five names of version packet files.

[0079] As shown in the above table, the hardware implementation type of board 1 is Type2 (type 2), the name of the version packet file corresponding to board 1 with the hardware implementation type of Type2 is "Xxx", and the version number of this version packet file is 1.2.

[0080] To distinguish it from the version packet file actually running in the base station, the version packet file in the board configuration file is denoted as the first version file.

[0081] In addition, the board configuration file can also record the slot where each board is located. For example, referring to Table 2, Table 2 shows the board configuration file in tabular form.

[0082]

[0083] Table 2

[0084] As shown in Table 2, the board configuration file also records the slot where each board is located.

[0085] In this step, the base station reads the latest obtained board configuration file to determine the hardware implementation type of each board in the base station, the name and version number of the corresponding first version file.

[0086] S202: Determine the name and version number of the second version file currently running in the base station; where each second version file corresponds to a hardware implementation type of a board.

[0087] [[ID=2۴]]After the base station starts, it needs to run the version packet files corresponding to each board. Since the base station has not updated the version packet files yet, the version packet files currently running in the base station are the version packet files to be updated. For the sake of easy description, they are denoted as the second version files.

[0088] S203: Match the first version file and the second version file to determine the differential version file.

[0089] In the embodiments of the present application, the first version file and the second version file are matched to further determine the differential version file. Since the first version file recorded in the board configuration file can be understood as the new version file and needs to be updated to the base station, and the second version file currently running in the base station can be understood as the old version file, that is, the version file to be updated, the differential version file can be understood as: the version file that belongs to the first version file but does not belong to the second version file.

[0090] S204: Download the differential version file from the version server and update the version file based on the differential version file.

[0091] As described above, whenever a new version file is released, the version server downloads the new version package file from the server that released the version file and decompresses it to obtain each version sub-package file. That is, the version server stores the new version sub-package files corresponding to various boards and the hardware implementation types of various boards. Therefore, after determining the differential version file, the version server can be accessed to download the differential version file from the version server.

[0092] Applying the version file update method for a base station provided by the embodiments of the present application, the base station determines the name and version number of the first version file recorded in the board configuration file; wherein, each first version file corresponds to a hardware implementation type of a board; determines the name and version number of the second version file currently running on the base station; wherein, each second version file corresponds to a hardware implementation type of a board; matches the first version file and the second version file to determine the differential version file; downloads the differential version file from the version server, and updates the version file based on the differential version file.

[0093] It can be seen that the differential version file is determined by matching the name and version number of the first version file recorded in the board configuration file and the name and version number of the second version file currently running on the base station. Since it is considered that there may be multiple hardware implementation types for the same application type of board, and the version files corresponding to each hardware implementation type are different, in the case where the hardware implementation type of the board changes, the determined differential version file is the version file corresponding to the changed hardware implementation type of the board, and only the version file corresponding to the changed hardware implementation type needs to be downloaded. With the continuous breakthroughs in chip technology and the continuous development and application of other high-tech materials, the types of hardware implementation types of the same application type of board are gradually enriched. Therefore, in the process of version file update, only downloading the version file corresponding to the required single hardware implementation type can reduce the number of files downloaded to the base station, save the time required for the version upgrade process, and greatly save the board disk space, improving the operation efficiency of the base station.

[0094] Moreover, in the embodiments of the present application, the version update process is actively initiated by the base station side. The base station does not need to upload any files to the management station, so the management station does not need to process a large number of files uploaded by many base stations at the same time, which will not cause a high load on the management station. And the way that the base station actively updates the version is more convenient for operation and maintenance.

[0095] In one embodiment of the present application, the differential version file includes: a first version file corresponding to the same board card, whose name is different from that of the second version file due to different hardware implementation types; and / or a first version file corresponding to the same hardware implementation type of the same board card, but with a different version number from that of the second version file; and / or a version file corresponding to the newly added board card that is missing in the second version file due to the addition of a new board card.

[0096] Specifically, there are several cases where the first version file and the second version file are different, as follows:

[0097] 1) The hardware implementation type of the board card has changed. For example, a board card of a certain application type has been replaced, and the hardware implementation type has changed. The board card configuration file records the name of the first version file corresponding to the changed hardware implementation type, which is different from the name of the second version file corresponding to the hardware implementation type before the change. In this case, the differential version file is the first version file corresponding to the same board card, whose name is different from that of the second version file due to different hardware implementation types.

[0098] 2) The board card has not changed, that is, the hardware implementation type has not changed either. However, for one or more board cards, a new version file has been released by the system, that is, the version number of the version file has changed. That is, the version number of the first version file is the new version number, and the version number of the second version file is the old version number. In this case, the differential version file is the first version file corresponding to the same hardware implementation type of the same board card, but with a different version number from that of the second version file.

[0099] 3) New board cards have been added due to reasons such as capacity expansion. In the case of adding new board cards, new slots will be occupied. Therefore, it is possible to determine whether new board cards have been added through the slot information in the board card configuration file. Since the first version file contains the version file corresponding to the newly added board card, and the second version file does not contain the version file corresponding to the newly added board card, in this case, the differential version file is the version file corresponding to the newly added board card that is missing in the second version file due to the addition of a new board card.

[0100] It can be seen that in the embodiment of the present application, for various situations such as the change of the hardware implementation type of the board card, the change of only the version number of the version file corresponding to the board card, and the addition of new board cards, the differential version file can be determined by matching the name and version number of the first version file recorded in the board card configuration file and the name and version number of the second version file currently running on the base station. It is possible to minimize and accurately determine the version file to be downloaded, reduce the number of files downloaded to the base station, save the time required for the version upgrade process, and greatly save the board card disk space, improving the operation efficiency of the base station. Especially during batch upgrade and maintenance, board card replacement or capacity expansion, each base station can trigger the update of the version file by itself, improving the update efficiency.

[0101] In one embodiment of the present application, the board configuration file is updated in response to a change in the board or a change in a version file corresponding to the board.

[0102] For example, when a board card changes (including but not limited to adding a new board card, changing a board card to a different hardware implementation type), or when the version file corresponding to the board card is updated, the administrator can update the information in the board card configuration file accordingly based on the changed situation, and the base station can obtain the updated board card configuration file in a specific manner.

[0103] In one embodiment of the present application, the base station is pre-configured with version server configuration information; the version server configuration information includes: the IP address of the version server and login information of the version server. Downloading the differential version file from the version server includes: accessing the version server based on the version server configuration information, querying and downloading the differential version file from the version server.

[0104] The login information may include a user name and password required to log in to the version server.

[0105] Specifically, the base station can pre-configure a version server configuration table, which contains the version server IP address, login username, and password. In addition, the table can also contain a switch flag indicating whether the download is effective immediately after completion.

[0106] Therefore, after the base station determines the difference version file, it accesses the version server through the pre-configured version server configuration table and queries the difference version file on the version server. The specific query method is not limited. For example, it can be retrieved according to the board, hardware implementation type, version number, etc. corresponding to the difference version file, and the required difference version file can be queried from the version package file stored in the version server, and then the difference version file can be downloaded.

[0107] In one embodiment of the present application, the download path of the differential version file may be an operating storage path of the base station.

[0108] Specifically, in the embodiment of the present application, the differential version files downloaded by the base station from the version server are not stored in the base station's storage path, such as disk space, but are directly downloaded to a running storage path that can be directly executed, which can also be understood as running storage space. Therefore, the base station does not need to specifically save the downloaded files, avoiding the long-term occupation of disk space by downloaded files due to untimely cleaning, further saving disk space. The saved disk storage space can provide more development space for the storage of files such as operation and maintenance location of product problems, log records, and performance indicators.

[0109] In one embodiment of the present application, the steps of updating the version file based on the differential version file include: transferring the second version file currently running on the base station to the backup path and loading and running the differential version file.

[0110] Specifically, after the base station downloads the required version file from the version server, it transfers the currently running version file to the backup path, and then loads and runs the newly downloaded file. Therefore, even if a failure occurs during the update, the old version file can be retrieved again from the backup path to ensure the basic operation of the base station and avoid excessive impact on the base station caused by the failure of the version file update.

[0111] To introduce the above method flow more clearly, an example is also provided in the embodiment of the present application. Figure 3 Another schematic flow diagram of the version file update method provided by the embodiment of the present application is shown. The method includes the following steps:

[0112] Step S301: The version server updates the version package file and the version sub-package file after decompressing the version file package.

[0113] Step S302: The base station performs cutover or base station reset.

[0114] Step S303: The base station starts up, reads the board hardware type, version number, and file name in the board configuration file, and matches them one by one with the version file currently running on the base station.

[0115] Step S304: Determine whether they are consistent. If not, execute Step S305; if so, execute Step S306.

[0116] Step S305: The base station downloads the specified sub-package file from the version server.

[0117] Step S306: The base station loads the currently running file.

[0118] Step S307: The base station loads the downloaded file.

[0119] Step S308: The base station runs normally after loading the file.

[0120] Step S309: End.

[0121] It can be seen that after the transmission cutover or reset of the entire base station occurs, when the base station starts to run, the base station reads the board hardware type, file name, and version number in the board configuration file, and matches them one by one with the version files currently running on the current base station. If the file name and version number match the version file currently running on the base station, the download step is skipped, and the base station selects to load the currently running file; when the match is inconsistent, the base station finds the small packet file after decompression of the corresponding version on the version server according to the version number filled in the version server configuration table, and downloads the small packet file with the specified name and version number to the base station.

[0122] After the base station downloads the minimum set of required files, it automatically resets and loads to make the new version file take effect.

[0123] Therefore, if the board on the base station changes, such as replacing the board, after updating the board configuration file and importing it into the base station, and then performing operations such as transmission cutover or reset on the base station, the version download process can be triggered again.

[0124] It can be seen that for scenarios such as upgrading, daily operation and maintenance, or expansion, when adding multimode, etc., only the board type configuration file corresponding to the network element needs to be supplemented. For example, when adding a new hardware type board, the information corresponding to the board is supplemented, including the slot number of the new board, the board hardware type, and the single-mode file name or multimode file name or file version number corresponding to this type. In this way, when a new board type or file match is inconsistent, the upgrade will be downloaded, and thus, the on-demand loading of the version file is realized.

[0125] See Figure 4 , which is a schematic structural diagram of a version file update device provided by an embodiment of the present application, including the following modules:

[0126] The first determination module 401 is used to determine the name and version number of the first version file recorded in the board configuration file; wherein, each first version file corresponds to a hardware implementation type of a board.

[0127] The second determination module 402 is used to determine the name and version number of the second version file currently running on the base station; wherein, each second version file corresponds to a hardware implementation type of a board.

[0128] The matching module 403 is used to match the first version file and the second version file to determine the differential version file.

[0129] The update module 404 is used to download the differential version file from the version server and update the version file based on the differential version file.

[0130] It can be seen that the different version files are determined by matching the name and version number of the first version file recorded in the board configuration file with the name and version number of the second version file currently running on the base station. Since it is considered that there may be multiple hardware implementation types for boards of the same application type, and the version files corresponding to each hardware implementation type are different, in the case where the hardware implementation type of the board changes, the determined different version file is the version file corresponding to the changed hardware implementation type of the board, and only the version file corresponding to the changed hardware implementation type needs to be downloaded. With the continuous breakthroughs in chip technology and the continuous development and application of other high-tech materials, the types of hardware implementation types of boards of the same application type are gradually enriched. Therefore, during the process of updating version files, only downloading the version file corresponding to a single required hardware implementation type can reduce the number of files downloaded to the base station, save the time required for the version upgrade process, and greatly save the board disk space, improving the operation efficiency of the base station.

[0131] Moreover, in the embodiment of the present application, the version update process is actively initiated by the base station side. The base station does not need to upload any files to the management station, so the management station does not need to process a large number of files uploaded by many base stations at the same time, which will not cause a high load on the management station. And the way that the base station actively updates the version is more convenient for operation and maintenance.

[0132] In an embodiment of the present application, the different version files include: the first version file corresponding to the same board and having a different name from the second version file due to different hardware implementation types; and / or the first version file corresponding to the same hardware implementation type of the same board but having a different version number from the second version file; and / or the version file corresponding to the newly added board is missing in the second version file due to the addition of a new board.

[0133] In an embodiment of the present application, the board configuration file is updated in response to a change in the board or a change in the version file corresponding to the board.

[0134] In an embodiment of the present application, the base station is pre-configured with version server configuration information; the version server configuration information includes: the IP address of the version server and the login information of the version server;

[0135] The update module is specifically configured to: based on the version server configuration information, access the version server, and query and download different version files on the version server.

[0136] In an embodiment of the present application, the update module is specifically configured to: transfer the second version file currently running on the base station to an alternate path and load and run the different version file.

[0137] It should be noted here that the above device provided by the embodiments of the present invention can implement all the method steps implemented by the above method embodiments, and can achieve the same technical effects. Therefore, the same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0138] An embodiment of the present application also provides a base station, as Figure 5 shown, including: a transceiver 500, configured to receive and send data under the control of a processor 510.

[0139] Among them, in Figure 5 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits of one or more processors represented by the processor 510 and a memory represented by the memory 520 are linked together. The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art. Therefore, they will not be further described herein. The bus interface provides an interface. The transceiver 500 may be multiple elements, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium, and these transmission mediums include wireless channels, wired channels, optical fiber cables, and other transmission mediums. The processor 510 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 510 when performing operations.

[0140] The processor 510 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD), and the processor may also adopt a multi-core architecture.

[0141] A memory 520, configured to store a computer program; a transceiver 500, configured to receive and send data under the control of the processor 510; a processor 510, configured to read the computer program in the memory and perform the following operations:

[0142] Determine the name and version number of the first version file recorded in the board configuration file; wherein, each first version file corresponds to a hardware implementation type of a board;

[0143] Determine the name and version number of the second version file currently running on the base station; wherein, each second version file corresponds to a hardware implementation type of a board;

[0144] Match the first version file and the second version file to determine the differential version file;

[0145] Download the differential version file from the version server and update the version file based on the differential version file.

[0146] The memory may include a Random Access Memory (RAM), or may also include a Non-Volatile Memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located far away from the aforementioned processor.

[0147] The aforementioned processor may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0148] It can be seen that the differential version file is determined by matching the name and version number of the first version file recorded in the board configuration file and the name and version number of the second version file currently running on the base station. Considering that there may be multiple hardware implementation types for the boards of the same application type, and the version files corresponding to each hardware implementation type are different. When the hardware implementation type of the board changes, the determined differential version file is the version file corresponding to the changed hardware implementation type of the board, and only the version file corresponding to the changed hardware implementation type needs to be downloaded. With the continuous breakthroughs in chip technology and the continuous development and application of other high-tech materials, the types of hardware implementation types of boards of the same application type are gradually enriched. Therefore, during the version file update process, only downloading the version file corresponding to the required single hardware implementation type can reduce the number of files downloaded to the base station, save the time required for the version upgrade process, and greatly save the disk space of the board, improving the operation efficiency of the base station.

[0149] Moreover, in the embodiments of the present application, the version update process is actively initiated by the base station side. The base station does not need to upload any files to the management station, so the management station does not need to process a large number of files uploaded by many base stations at the same time, which will not cause a high load on the management station, and the method of the base station actively performing version update is more convenient for operation and maintenance.

[0150] In one embodiment of the present application, the differential version file includes: a first version file corresponding to the same board card, whose name is different from that of the second version file due to different hardware implementation types; and / or a first version file corresponding to the same hardware implementation type of the same board card, but with a different version number from the second version file; and / or a version file corresponding to a newly added board card that is missing in the second version file due to the addition of the board card.

[0151] In one embodiment of the present application, the board card configuration file is updated in response to a change in the board card or a change in the version file corresponding to the board card.

[0152] In one embodiment of the present application, the base station is pre-configured with version server configuration information; the version server configuration information includes: the IP address of the version server and the login information of the version server.

[0153] Downloading the differential version file from the version server specifically includes:

[0154] Based on the version server configuration information, access the version server, query and download the differential version file on the version server.

[0155] In one embodiment of the present application, the download path of the differential version file is the running storage path of the base station.

[0156] In one embodiment of the present application, the steps of updating the version file based on the differential version file specifically include: transferring the second version file currently running on the base station to an alternate path and loading and running the differential version file.

[0157] In another embodiment provided by the present application, a computer-readable storage medium is further provided. A computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps of any of the above version file update methods are implemented.

[0158] The processor-readable storage medium may be any available medium or data storage device accessible by the processor, including but not limited to magnetic memories (such as floppy disks, hard disks, magnetic tapes, magneto-optical discs (MO), etc.), optical memories (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor memories (such as ROM, EPROM, EEPROM, non-volatile memories (NANDFLASH), solid-state drives (SSD)).

[0159] In another embodiment provided by the present application, a computer program product containing instructions is further provided. When it runs on a computer, the computer is caused to execute any of the version file update methods in the above embodiments.

[0160] In the above embodiments, they can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or a wireless manner (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

[0161] It should be noted that, in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including", or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or device that includes a series of elements includes not only those elements but also other elements that are not explicitly listed, or also includes elements that are inherent to such process, method, article, or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article, or device that includes the element.

[0162] Each embodiment in this specification is described in a related manner. The same or similar parts among the embodiments can be referred to each other, and the differences between each embodiment and other embodiments are emphasized. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.

[0163] The above are only the preferred embodiments of the present application and are not used to limit the protection scope of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A method for updating version files, characterized in that Applied to a base station, the method includes: Determine the name of the first version file recorded in the board configuration file and the version number of the first version file; wherein, each of the first version files corresponds to a hardware implementation type of a board; Determine the name of the second version file currently running on the base station and the version number of the second version file; wherein, each of the second version files corresponds to a hardware implementation type of a board; Match the first version file and the second version file to determine the differential version file; Download the differential version file from the version server and update the version file based on the differential version file.

2. The method according to claim 1, wherein: The differential version file includes: a first version file corresponding to the same board and having a different name from the second version file due to different hardware implementation types; and / or a first version file corresponding to the same hardware implementation type of the same board but having a different version number from the second version file; and / or a version file corresponding to a newly added board that is missing in the second version file due to the addition of the board.

3. The method according to claim 1, wherein The board configuration file is updated in response to a change in the board or a change in the version file corresponding to the board.

4. The method according to claim 1, wherein The base station is pre-configured with version server configuration information; The version server configuration information includes: the IP address of the version server, the login information of the version server; The downloading of the differential version file from the version server includes: Based on the version server configuration information, access the version server, query and download the differential version file on the version server.

5. The method according to any one of claims 1-4, characterized in that, The download path of the differential version file is the running storage path of the base station.

6. The method according to any one of claims 1 to 4, characterized in that The step of updating the version file based on the differential version file includes: transferring the second version file currently running on the base station to an alternate path and loading and running the differential version file.

7. A version file update device, characterized in that, Applied to a base station, the apparatus includes: A first determination module, configured to determine the name of the first version file recorded in the board configuration file and the version number of the first version file; wherein, each of the first version files corresponds to a hardware implementation type of a board; A second determination module, configured to determine the name of the second version file currently running on the base station and the version number of the second version file; wherein, each of the second version files corresponds to a hardware implementation type of a board; A matching module, configured to match the first version file and the second version file to determine the differential version file; An update module, configured to download the differential version file from the version server and update the version file based on the differential version file.

8. A base station, characterized in that, Including a memory, a transceiver, and a processor: The memory is used to store computer programs; the transceiver is used to transmit and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: Determine the name of the first version file recorded in the board configuration file and the version number of the first version file; wherein, each of the first version files corresponds to a hardware implementation type of a board; Determine the name of the second version file currently running on the base station and the version number of the second version file; wherein, each of the second version files corresponds to a hardware implementation type of a board. Match the first version file and the second version file to determine the differential version file. Download the differential version file from the version server and update the version file based on the differential version file.

9. The base station according to claim 8, wherein The differential version file includes: a first version file corresponding to the same board and having a different name from the second version file due to different hardware implementation types; and / or a first version file corresponding to the same hardware implementation type of the same board but having a different version number from the second version file; and / or a version file corresponding to a newly added board that is missing in the second version file due to the addition of the new board.

10. The base station according to claim 8, wherein The board configuration file is updated in response to a change in the board or a change in the version file corresponding to the board.

11. The base station according to claim 8, characterized in that, The base station is pre-configured with version server configuration information. The version server configuration information includes: the IP address of the version server and the login information of the version server. The downloading of the differential version file from the version server specifically includes: Based on the version server configuration information, access the version server, query and download the differential version file on the version server.

12. The base station according to any one of claims 8-11, characterized in that, The download path of the differential version file is the running storage path of the base station.

13. The base station according to any one of claims 8-11, characterized in that, The step of updating the version file based on the differential version file specifically includes: transferring the second version file currently running on the base station to an alternate path and loading and running the differential version file.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps described in any one of claims 1-6 are implemented.

Images