WO2021232853A1

WO2021232853A1 - Base station data upgrading method, base station and computer-readable medium

Info

Publication number: WO2021232853A1
Application number: PCT/CN2021/074726
Authority: WO
Inventors: 李润心; 韩松; 陈希闯; 米磊
Original assignee: 中兴通讯股份有限公司
Priority date: 2020-05-21
Filing date: 2021-02-01
Publication date: 2021-11-25
Also published as: CN113760312A

Abstract

A base station data upgrading method, a base station and a computer-readable medium. The method comprises: in response to a base station upgrade request, acquiring source version information and source configuration data of a target base station (S1); according to the source version information and target version information, generating an upgrading rule model, and according to the upgrading rule model and the source configuration data, generating target configuration data (S2).

Description

Base station data upgrade method, base station and computer readable medium

Technical field

The present disclosure relates to the field of communication technology, and in particular, to a base station data upgrade method, a base station, and a computer-readable medium.

Background technique

With the development of communication network technology, base station upgrade scenarios have become more complicated. The base station data upgrade method at this stage mostly uses manual configuration of the upgrade wizard, or upgrades according to the version serial number, or upgrades the base station data by upgrading the software for a single version.

However, in the face of hardware structure changes, cross-system, cross-software platform scenarios, there are disadvantages such as complex parameter configuration, large amount of data corresponding to multiple versions of upgrade software, and high development costs; there are needs when facing scenarios with cross-base station versions Upgrade multiple times according to the order of the version number, the upgrade process is redundant, the upgrade speed is slow and the cost is high.

Summary of the invention

The present disclosure aims to solve at least one of the related technical problems, and proposes a base station data upgrade method, a base station, and a computer-readable medium.

To achieve the foregoing objective, in the first aspect, embodiments of the present disclosure provide a method for upgrading base station data, including:

In response to a base station upgrade request, acquiring source version information and source configuration data of the target base station, where the base station upgrade request includes: target version information after the target base station is upgraded;

An upgrade rule model is generated according to the source version information and the target version information, and target configuration data is generated according to the upgrade rule model and the source configuration data.

In the second aspect, the embodiments of the present disclosure also provide a base station, including:

One or more processors;

Storage device, set to store one or more programs;

When the one or more programs are executed by the one or more processors, the one or more processors implement the base station data upgrade method described in any of the foregoing embodiments.

In a third aspect, the embodiments of the present disclosure also provide a computer-readable medium on which a computer program is stored, wherein the program is executed by a processor to implement the base station data upgrade method described in any of the above embodiments Steps in.

Description of the drawings

FIG. 1 is a flowchart of a method for upgrading base station data according to an embodiment of the disclosure;

2 is a flowchart of a specific implementation method of step S2 in an embodiment of the disclosure;

FIG. 3 is a flowchart of another method for upgrading base station data according to an embodiment of the disclosure;

FIG. 4 is a flowchart of yet another method for upgrading base station data according to an embodiment of the disclosure;

5 is a flowchart of another specific implementation method of step S2 in an embodiment of the disclosure;

6 is a structural block diagram of a base station data upgrade system provided in an embodiment of the disclosure;

FIG. 7 is a structural block diagram of another base station data upgrade system provided in an embodiment of the disclosure;

FIG. 8 is a structural block diagram of a base station provided in an embodiment of the disclosure.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the base station data upgrade method, base station, and computer-readable medium provided by the present disclosure will be described in detail below in conjunction with the accompanying drawings.

Hereinafter, example embodiments will be described more fully with reference to the accompanying drawings, but the example embodiments may be embodied in different forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, the purpose of providing these embodiments is to make the present disclosure thorough and complete, and to enable those skilled in the art to fully understand the scope of the present disclosure.

The terms used herein are only used to describe specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "a" and "the" are also intended to include the plural forms, unless the context clearly dictates otherwise. It will also be understood that when the terms "comprising" and/or "made of" are used in this specification, it specifies the presence of the described features, wholes, steps, operations, elements and/or components, but does not exclude the presence or Add one or more other features, wholes, steps, operations, elements, components, and/or groups thereof.

Unless otherwise defined, the meanings of all terms (including technical and scientific terms) used herein are the same as those commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having meanings consistent with their meanings in the context of the related technology and the present disclosure, and will not be interpreted as having idealized or excessive formal meanings, Unless this article specifically defines it as such.

The base station data upgrade method, base station, and computer readable medium provided by the present disclosure can be used to implement base station data upgrade across base station versions, across systems, and across software platforms based on the data plane.

The base station data upgrade method is suitable for cross-version, cross-platform, and cross-system situations, that is, the base station data upgrade in general situations, for example, the base station configuration data upgrade under the condition of no change in the software platform but changes in the hardware structure (for example, an embedded platform) Version upgrade to another embedded platform version), base station configuration data upgrade under software platform changes and hardware structure changes (for example, an embedded platform version is upgraded to a paas platform version), and base station configuration in other situations Data upgrade.

FIG. 1 is a flowchart of a method for upgrading base station data according to an embodiment of the disclosure. As shown in Figure 1, the method includes:

Step S1: In response to the base station upgrade request, obtain source version information and source configuration data of the target base station.

Wherein, the base station upgrade request includes target version information after the target base station is upgraded, and the base station upgrade request may also include the target base station ID and network element ID, etc. The base station upgrade request can be triggered through an application program interface or configuration file.

In some embodiments, when there are multiple target base stations and the number is greater than a preset distributed operation threshold, the base station data upgrade task is offloaded in a micro-service or multi-process manner. Among them, when building a base station data upgrade system that corresponds to the base station data upgrade method, modular, distributed, and micro-service architecture can be used to build the server to deal with complex situations such as a large number of base station upgrades by expanding services and concurrent tasks. The way of offloading increases the processing capacity and reduces the base station upgrade time.

In some embodiments, the source version information includes source version data model information and a source version number, and the target version information includes target version data model information and a target version number; wherein, the source version data model information includes source configuration data objects and source configuration data. Type, source version field unique identifier and source version constraint information; target version data model information includes target configuration data object, target configuration data type, target version field unique identifier, and target version constraint information.

Step S2: Generate an upgrade rule model according to the source version information and the target version information, and generate target configuration data according to the upgrade rule model and the source configuration data.

In some embodiments, the upgrade rule model describes the conversion relationship between the source configuration data and the target configuration data, which is embodied in the form of an xml file, a json file, or a DSL description. Specifically, the upgrade rule model includes source version data identification, target version data identification, rule behavior, and rule algorithm. The target configuration data is generated according to the upgrade rule model and the source configuration data, that is, the source configuration data is converted into the target configuration data using the upgrade rule model.

FIG. 2 is a flowchart of a specific implementation method of step S2 in an embodiment of the disclosure. As shown in Figure 2, in step S2, the step of generating an upgrade rule model according to the source version information and the target version information specifically includes: step S201 to step S203.

Step S201: Determine the mapping relationship between the source version and the target version according to the unique identifier of the source version field and the unique identifier of the target version field, and determine the rule behavior.

The unique identifier of the field is the unique identifier of each data record in the configuration data, and the mapping relationship between the source version and the target version is the mapping relationship between the source configuration data and the target configuration data.

In some embodiments, the rule behavior includes at least one of addition, modification, and forced type conversion.

Step S202: Determine a rule algorithm according to the source version constraint information and the target version constraint information.

Among them, the constraint information is a mandatory verification rule corresponding to the configuration data to ensure the correctness, validity, and integrity of the data.

In some embodiments, the rule algorithm includes at least one of four arithmetic operations, conditional judgments, and constraint judgments.

Step S203: Generate an upgrade rule model according to the rule behavior and the rule algorithm.

In some embodiments, after determining the rule behavior and rule algorithm, an upgrade rule model can be generated according to the basic rule library. The basic rule library includes pre-stored rule behaviors, rule algorithms, and rule sets. The parameter is irrelevant, and it is also reflected in the form of xml file, json file or DSL description.

The embodiments of the present disclosure provide a method for upgrading base station data. The method can be used to generate an upgrade rule model based on the data model information of the base station version before and after the upgrade, and use the upgrade rule model to perform data conversion of the corresponding base station configuration data to complete the base station data upgrade. The process is carried out at the data level, which can realize base station data upgrades across base station versions, across systems, and across software platforms.

FIG. 3 is a flowchart of another method for upgrading base station data provided by an embodiment of the disclosure. As shown in Fig. 3, the method is a specific alternative implementation based on the method shown in Fig. 1. Specifically, after step S2, it further includes: step S3.

Step S3: Verify the target configuration data according to the target version constraint information.

In step S3, the correctness and completeness of the converted configuration data are checked according to the target version constraint information.

FIG. 4 is a flowchart of another method for upgrading base station data according to an embodiment of the disclosure. As shown in Fig. 4, this method is a specific alternative implementation based on the method shown in Fig. 1. Specifically, after step S2, it further includes: step S4.

Step S4: Determine the configuration file format corresponding to the target version according to the target version information, and generate a configuration data file for upgrading the target base station according to the configuration file format and the target configuration data.

In step S4, a configuration data file is generated from the converted configuration data according to the configuration file format corresponding to the target version. The configuration data file can be used to upgrade the target base station. Specifically, the upgrade can be performed directly after the file is generated, or when the file is generated Then return a response and wait for the user event to trigger the upgrade.

FIG. 5 is a flowchart of another specific implementation method of step S2 in an embodiment of the disclosure. . As shown in FIG. 5, in step S2, before the step of generating target configuration data according to the upgrade rule model and the source configuration data, the method further includes: step S2a.

Step S2a: Determine the source data structure corresponding to the source version and the target data structure corresponding to the target version according to the source version data model information and the target version data model information.

In step S2a, the data model corresponding to each version is analyzed and identified according to the data model information, thereby identifying the data structure corresponding to each version, where the data structure includes a table structure, a YANG model, a tree structure, and the like.

Step S2, the step of generating target configuration data according to the upgrade rule model and the source configuration data, specifically includes: step S2b and step S2c.

Step S2b: Perform data structure conversion of the source configuration data according to the source data structure and the target data structure.

Step S2c: Generate target configuration data according to the source configuration data after the upgrade rule model and data structure conversion.

In some embodiments, the upgrade rule model may further include a data structure conversion algorithm, and the upgrade rule model is used to directly perform data conversion and data structure conversion on the source configuration data.

The embodiment of the present disclosure provides a base station data upgrade method, which can be used to identify the data structure corresponding to each version, and use the configuration data after the data structure conversion to perform data conversion.

The method for upgrading base station data provided by the present disclosure will be described in detail below in combination with actual applications.

FIG. 6 is a structural block diagram of a base station data upgrade system provided in an embodiment of the disclosure. Specifically, the base station data upgrade system can be deployed in a base station or on a server. As shown in Figure 6, the user can complete the data upgrade of multiple target base stations at one time through the base station data upgrade system, including the complex situation of cross-version, cross-platform, and cross-system before and after the upgrade. For example, according to user requests, target base stations A1 to An , The base station data upgrade system can realize the unified upgrade of its base station version from the source version B1 to Bm to the cross-platform target version Ck.

Fig. 7 is a structural block diagram of another base station data upgrading system provided in an embodiment of the disclosure. As shown in Figure 7, the corresponding base station data upgrade system can be built on a base station or server in a modular manner. The base station data upgrade system can specifically include a task management module 1, a rule model management module 2, a data management module 3. Data conversion module 4 and data verification module 5.

Specifically, the user terminal sends a base station upgrade request in the form of an application program interface or configuration file through the task interface provided by the task management module 1, where the base station upgrade request includes; the target version information after the target base station is upgraded, the base station upgrade request may Including the target base station ID and network element ID; the task management module 1 receives the base station upgrade request and requests the data management module 3 to obtain the source version information and source configuration data of the target base station, where the source version information includes source version data model information and source Version number, target version information includes target version data model information and target version number, source version data model information includes source configuration data object, source configuration data type, source version field unique identifier and source version constraint information; target version data model information includes Target configuration data object, target configuration data type, target version field unique identifier, and target version constraint information.

The task management module 1 receives the data response returned by the data management module 3, and requests the rule model management module 2 to generate a rule model; after receiving the request, the rule model management module 2 first performs the structure conversion of the configuration data, according to the source version data model Information and target version data model information respectively determine the source data structure corresponding to the source version and the target data structure corresponding to the target version, and perform the data structure conversion of the source configuration data according to the source data structure and target data structure; after the data structure conversion is completed, Determine the mapping relationship between the source version and the target version according to the unique identifier of the source version field and the unique identifier of the target version field, and determine the rule behavior according to the mapping relationship, and then determine the rule algorithm according to the source version constraint information and the target version constraint information, and according to the rule behavior , The rule algorithm and the basic rule library generate an upgrade rule model, and report the model to generate a response.

The task management module 1 receives the model generation response and requests data conversion to the data conversion module 4; after the data conversion module 4 performs data conversion according to the request, the data management module 3 will complete the data conversion configuration data according to the target version information to determine the target The configuration file format corresponding to the version generates a configuration data file for the target base station upgrade; the data verification module 5 verifies the configuration data file according to the target version constraint information. After the verification is completed, the task management module 1 returns the upgrade to the user terminal Respond and upgrade the target base station, or wait for the corresponding user event to trigger the base station upgrade.

FIG. 8 is a structural block diagram of a base station provided in an embodiment of the disclosure. As shown in Figure 8, the base station includes:

One or more processors 6; a storage device 7 configured to store one or more programs; when the one or more programs are executed by the one or more processors 6, the one or more processors 6 realize such as Any base station data upgrade method in the foregoing embodiment.

The embodiments of the present disclosure provide a computer-readable medium on which a computer program is stored, where the program is executed by a processor to implement the steps in any base station data upgrade method in the above-mentioned embodiments.

The embodiments of the present disclosure provide a method for upgrading base station data, a base station, and a computer-readable medium, which can generate an upgrade rule model according to the corresponding version information before and after the upgrade of the base station, and upgrade and convert configuration data according to the upgrade rule model, and perform the upgrade at the data level. The base station upgrade configuration realizes the base station data upgrade under the situation of cross-base station version, cross-system and cross-software platform.

A person of ordinary skill in the art can understand that all or some of the steps in the method disclosed above, and the functional modules/units in the device can be implemented as software, firmware, hardware, and appropriate combinations thereof. In the hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may consist of several physical components. The components are executed cooperatively. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit . Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile data implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media. Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or Any other medium used to store desired information and that can be accessed by a computer. In addition, as is well known to those of ordinary skill in the art, communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media. .

Example embodiments have been disclosed herein, and although specific terms are adopted, they are used and should only be interpreted as general descriptive meanings, and are not used for the purpose of limitation. In some instances, it is obvious to those skilled in the art that, unless clearly indicated otherwise, the features, characteristics, and/or elements described in combination with a specific embodiment may be used alone, or features, characteristics, and/or elements described in combination with other embodiments may be used, Combination of features and/or components. Therefore, those skilled in the art will understand that various changes in form and details can be made without departing from the scope of the present disclosure as set forth by the appended claims.

Claims

A method for upgrading base station data includes:

In response to a base station upgrade request, acquiring source version information and source configuration data of the target base station, where the base station upgrade request includes: target version information after the target base station is upgraded;

An upgrade rule model is generated according to the source version information and the target version information, and target configuration data is generated according to the upgrade rule model and the source configuration data.
The base station data upgrade method according to claim 1, wherein the source version information includes: source version data model information and a source version number; the target version information includes: target version data model information and a target version number;

Wherein, the source version data model information includes at least one of the following: source configuration data object, source configuration data type, source version field unique identifier, and source version constraint information; the target version data model information includes at least one of the following: target The configuration data object, the target configuration data type, the unique identifier of the target version field, and the target version constraint information.
The base station data upgrade method according to claim 2, wherein the step of generating an upgrade rule model according to the source version information and the target version information comprises:

Determine the mapping relationship between the source version and the target version according to the unique identifier of the source version field and the unique identifier of the target version field, and determine the rule behavior;

Determining a rule algorithm according to the source version constraint information and the target version constraint information;

The upgrade rule model is generated according to the rule behavior and the rule algorithm.
The method for upgrading base station data according to claim 3, wherein the rule behavior includes at least one of addition, modification, and forced type conversion; and the rule algorithm includes at least one of four arithmetic operations, conditional judgments and constraint judgments One.
The base station data upgrade method according to claim 2, wherein after the step of generating target configuration data according to the upgrade rule model and the source configuration data, the method further comprises:

The target configuration data is verified according to the target version constraint information.
The base station data upgrade method according to claim 1, wherein after the step of generating target configuration data according to the upgrade rule model and the source configuration data, the method further comprises:

Determine a configuration file format corresponding to the target version according to the target version information, and generate a configuration data file for upgrading the target base station according to the configuration file format and the target configuration data.
The base station data upgrade method according to claim 2, wherein before the step of generating target configuration data according to the upgrade rule model and the source configuration data, the method further comprises:

Respectively determine the source data structure corresponding to the source version and the target data structure corresponding to the target version according to the source version data model information and the target version data model information;

The step of generating target configuration data according to the upgrade rule model and the source configuration data includes:

Performing the data structure conversion of the source configuration data according to the source data structure and the target data structure;

Generate target configuration data according to the source configuration data converted from the upgrade rule model and the data structure.
The method for upgrading base station data according to claim 1, further comprising:

When there are multiple target base stations, and the number is greater than a preset distributed operation threshold, the base station data upgrade task is offloaded in a micro-service or multi-process manner.
A base station, including:

One or more processors;

Storage device, set to store one or more programs;

When the one or more programs are executed by the one or more processors, the one or more processors implement the base station data upgrade method according to any one of claims 1-8.
A computer-readable medium having a computer program stored thereon, wherein the program is executed by a processor to implement the steps in the base station data upgrade method according to any one of claims 1-8.