WO2017088528A1 - 配置信息管理方法及装置、操作维护中心或基站 - Google Patents

配置信息管理方法及装置、操作维护中心或基站 Download PDF

Info

Publication number
WO2017088528A1
WO2017088528A1 PCT/CN2016/094653 CN2016094653W WO2017088528A1 WO 2017088528 A1 WO2017088528 A1 WO 2017088528A1 CN 2016094653 W CN2016094653 W CN 2016094653W WO 2017088528 A1 WO2017088528 A1 WO 2017088528A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
configuration data
value
base station
result
Prior art date
Application number
PCT/CN2016/094653
Other languages
English (en)
French (fr)
Inventor
刘萍
叶小仁
唐雄
张恒
王喜
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017088528A1 publication Critical patent/WO2017088528A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0866—Checking the configuration
    • H04L41/0869—Validating the configuration within one network element

Definitions

  • This document relates to, but is not limited to, the field of communications, and in particular, to a configuration information management method and apparatus, an operation and maintenance center or a base station.
  • the configuration authentication of the service function of the base station also causes the service performance to be degraded or even completely locked. Please refer to the following configuration authentication example:
  • Configuration authentication includes two types, one is a switch type, and the other is a numeric type.
  • the specific authentication algorithm is as shown in Table 2.
  • the configuration data is configured according to the preset configuration value of the background network management system. If the default configuration value of the configuration data exceeds the authorized configuration value, the actual configuration of the configuration data can only be determined according to the authorized configuration value, such as configuration data Y.
  • the authorized configuration value of the bandwidth is 500 megabytes (M).
  • M megabytes
  • the default configuration of the bandwidth configured by the network management system is less than 500 Mbps
  • the default configuration value of the bandwidth allowed for the authentication is configured. If the default configuration value of the bandwidth is greater than 500 M, the configuration authentication limits the actual effective bandwidth to 500 M.
  • the limitation of configuration authentication can also result in degraded or even closed business performance.
  • network maintenance personnel may need to spend a lot of time searching for massive configuration data without knowing it, so as to determine whether the performance degradation of the base station is due to the impact of configuration authentication; moreover, the network maintenance personnel will directly authorize the network.
  • the performance degradation caused by the configuration is regarded as a problem of the performance of the base station, thereby performing unnecessary maintenance on the base station.
  • the performance degradation caused by configuration authentication is a common occurrence. If network maintenance personnel need to perform cause location or blind maintenance every time they find that service performance is degraded, the human resources spent are immeasurable.
  • the embodiment of the invention provides a configuration information management method and device, an operation and maintenance center or a base station, which can obtain configuration data that the actual effective value of the base station side is inconsistent with the background preset configuration value when the service performance is degraded or even closed.
  • the embodiment of the invention provides a configuration information management method, including:
  • the configuration result of each configuration data of the service function configuration is obtained, where the configuration result includes: a background preset configuration value of each of the configuration data, and each of the The actual effective value of the base station side of the configuration data;
  • the configuration information management method further includes: updating the configuration data that is inconsistent between the actual effective value of the base station and the background preset configuration value in the configuration result to the historical inconsistency information table.
  • the manner of updating the configuration data that is inconsistent with the background preset configuration value in the configuration result of the configuration result to the historical inconsistency information table includes:
  • the method further includes: deleting the inconsistency information in the historical inconsistency information table according to the configuration data that is consistent with the background preset configuration value in the configuration result.
  • the process of deleting the inconsistency information in the historical inconsistency information table includes:
  • the method further includes: the configuration result further includes a base station side authorization configuration value of each configuration data, and after obtaining the configuration data that the actual effective value of the base station side is inconsistent with the background preset configuration value,
  • the background preset configuration value of the configuration data that is inconsistent with the background preset configuration value and the base station side authorization configuration value of the configuration data are compared, and the limited reason of the configuration data is determined.
  • the limited reasons for determining the configuration data include:
  • the limited reason for determining the configuration data includes a limitation of the configuration authentication
  • the limited reason for determining the configuration data is limited by the performance of the base station itself.
  • the method further includes: comparing the actual effective value of the configuration data base station side with the authorization of the base station side when the judgment result is yes and the service function configuration authentication is the numeric configuration data. If the actual value of the configuration data base station is smaller than the authorized configuration value of the configuration data base station side, determining the limited reason of the configuration data also includes being limited by the performance of the base station itself.
  • the embodiment of the invention further provides a configuration information management apparatus, including:
  • the configuration result obtaining module is configured to obtain a configuration result of each configuration data of the service function configuration after the service function configuration authentication of the base station is completed, where the configuration result includes a background preset configuration value of each of the configuration data. And an actual effective value of the base station side of each of the configuration data;
  • the inconsistent data obtaining module is configured to obtain, according to the configuration result, configuration data that the actual effective value of the base station side is inconsistent with the background preset configuration value.
  • the configuration information management apparatus further includes: an inconsistency information update module, where the inconsistency information update module is configured to update the configuration data in which the actual effective value of the base station side and the background preset configuration value in the configuration result are inconsistent to historical inconsistency information. In the table.
  • the inconsistency information update module includes at least one of a direct add submodule and a deduplication add submodule:
  • the directly adding sub-module is configured to directly add the configuration data that is inconsistent with the background preset configuration value in the configuration result to the historical inconsistency information table;
  • the de-duplication adding sub-module is configured to remove the configuration data that exists in the historical inconsistency information table and the configuration result in the historical inconsistency information table, and add the configuration data in the configuration result. Go to the historical inconsistency information table.
  • the method further includes an inconsistency information deleting module, where the inconsistency information deleting module is configured to perform inconsistency information in the historical inconsistency information table according to the configuration data that the actual effective value of the base station side and the background preset configuration value are consistent in the configuration result. delete.
  • the inconsistency information deleting module includes:
  • a judging sub-module configured to determine whether configuration data of the configuration result of the configuration data of the service function is consistent with the background preset configuration value in the historical inconsistency information table
  • Deleting the sub-module, setting to delete the calendar when the judgment result of the judging sub-module is YES The configuration data in the inconsistency information table.
  • the method includes a restricted cause analysis module, where the restricted cause analysis module is configured to compare a background preset configuration value of the configuration data that is inconsistent with a background preset configuration value of the base station side and the configuration data.
  • the base station side authorizes the configuration value to determine the limited reason of the configuration data.
  • the restricted reason analysis module includes a restricted judgment submodule, a first determining submodule, and a second determining submodule:
  • the restricted judgment sub-module is configured to determine whether the background preset configuration value of the configuration data is limited by the base station-side authorized configuration value;
  • the first determining submodule is configured to determine, when the determining result of the determining submodule is YES, that the limited reason for the configuration data includes a limitation of configuration authentication;
  • the second determining submodule is configured to determine that the limited reason of the configuration data is limited by the performance of the base station when the determining result of the determining submodule is NO.
  • the restricted reason analysis module further includes a comparison submodule and a third determining submodule:
  • the comparison sub-module is configured to compare the actual effective value of the configuration data base station side with the base station side authorization when the determination result of the restricted determination sub-module is YES and the service function configuration authentication is the numeric configuration data.
  • the third determining submodule is configured to determine, when the configuration data base station side actual effective value is smaller than the configuration data base station side authorized configuration value, the limited reason for determining the configuration data, and further includes receiving, by the base station, performance limitation.
  • An embodiment of the present invention further provides an operation and maintenance center or a base station, including the configuration information management apparatus as described above.
  • Embodiments of the present invention also provide a computer readable storage medium storing computer executable instructions for performing any of the methods described above.
  • the embodiment of the present invention provides a configuration information management method and device, an operation and maintenance center, or a base station. After the configuration information management device completes the service function configuration authentication, the configuration result of each configuration data in the configuration authentication is obtained, and then the configuration is performed. The preset configuration value and the actual effective value are analyzed to obtain configuration data whose actual effective value is inconsistent with the preset configuration value. Let the network maintainer The staff does not need to waste time and cause the reasoning when the business function is limited due to non-fault reasons, thereby saving manpower and material resources and optimizing resource allocation.
  • FIG. 1 is a flowchart of a configuration information management method according to Embodiment 1 of the present invention.
  • FIG. 2 is a flowchart of updating a history inconsistency information table by a deduplication adding manner according to Embodiment 1 of the present invention
  • FIG. 3 is a flowchart of deleting historical inconsistency information according to Embodiment 1 of the present invention.
  • FIG. 4 is a schematic diagram of a configuration information management apparatus according to Embodiment 2 of the present invention.
  • FIG. 5 is a schematic diagram of another configuration information management apparatus according to Embodiment 2 of the present invention.
  • FIG. 6 is a schematic diagram of the restricted cause analysis module of FIG. 5;
  • FIG. 7 is another schematic diagram of the restricted cause analysis module of FIG. 5;
  • FIG. 8 is a schematic diagram of another configuration information management apparatus according to Embodiment 2 of the present invention.
  • the configuration result of each configuration data of the configuration authentication is obtained, and the preset configuration value and the actual effective value in the configuration result are analyzed, and the actual effective value can be directly obtained.
  • the configuration data that is inconsistent with the preset configuration value hereinafter, the configuration data whose actual effective value is different from the preset configuration value is simply referred to as “inconsistent configuration data”.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • This embodiment provides a configuration information management method. Specifically, refer to FIG. 1:
  • the background network management system sends a preset configuration information to the foreground base station after the preset configuration of each configuration data is sent.
  • the background network management performs bulk data transmission to the foreground base station, and each configuration data is The preset configuration value is transmitted to the base station side.
  • the preset configuration value is received by the foreground base station to receive the service function configuration authentication.
  • the specific algorithm for the authentication can refer to Table 1 and Table 2. It can be understood that the configuration information management method provided in this embodiment is not only applicable to Table 1 And the authentication algorithm shown in Table 2 should also be applied to other authentication algorithms.
  • the configuration result of each configuration data of the service function configuration is obtained.
  • the configuration result includes the preset configuration value, the authorization configuration value, and the final actual effective value of the configuration data.
  • the configuration data in the obtained configuration result is analyzed, and the actual effective value and the preset configuration value are compared, and it is determined which configuration data in the configuration of the service function configuration is restricted. Generally, the actual value of the configuration data is less than or equal to the default configuration value. If the actual value of the configuration data is consistent with the preset configuration value, the configuration data is not restricted in the configuration authentication. If the actual effective value is less than the preset configuration value, the configuration data is limited in the configuration authentication.
  • the occurrence of inconsistent configuration data is generally affected by two factors: one is the performance of the base station itself. When the base station itself fails or has other performance problems, the actual effective value of the configuration data may be affected. Another factor is configuration authentication. When the status or size of the preset configuration value of the configuration data does not meet the authorized configuration value of the configuration data, the actual effective value of the configuration data can only be determined according to the authorization configuration value. In this case, the actual effective value of the configuration data must also be inconsistent with its preset configuration value.
  • the embodiment further provides a configuration data management method, and further includes: analyzing the reason that the inconsistent data is limited after obtaining the configuration data that the actual effective value of the base station side is inconsistent with the background preset configuration value. To further analyze the specific cause of the inconsistent configuration data, you need to analyze the default configuration value and the authorized configuration value of the inconsistent configuration data to determine whether the background preset configuration value of the inconsistent configuration data is limited to the authorized configuration value of the base station.
  • the size of the preset configuration value in the background necessarily exceeds the range allowed by the base station side to allow the configuration data to appear;
  • the status indicated by the default configuration value of the configuration data in the background must be inconsistent with the status represented by the authorization configuration value on the base station side. Determine whether the background preset configuration value of the inconsistent configuration data is limited by the authorized configuration value of the base station side. In fact, it is determined whether the background preset configuration value of the configuration data meets the requirements of the authorized configuration value of the base station side.
  • the reason for determining that the inconsistent configuration data is limited is affected by the performance of the base station; when the actual effective value is limited by the authorized configuration value, it is determined that the inconsistent configuration data is limited.
  • the reason includes the impact of the configuration authentication.
  • the reason for determining that the inconsistent configuration data is limited includes the impact of the configuration authentication, and the configuration authentication is a numeric configuration data right, the inconsistent configuration data may be further compared.
  • the actual effective value and the size of the authorized configuration value when the actual effective value of the inconsistent configuration data is less than the authorized configuration value, determining the limited reason for the inconsistent configuration data also includes being limited by the performance of the base station itself, for example, giving the background a certain
  • the default configuration value of the configuration data is 1600.
  • the base station side limits the authorized configuration value of the configuration data to 1500.
  • the actual effective value of the configuration data is 1400.
  • the configuration data is configured.
  • the background preset configuration value is limited by the authorized configuration value, but only for limited reasons The actual value should take effect as 1500 instead of 1400.
  • the inconsistent configuration data may be added to the current inconsistency information table, where the current inconsistency information table includes all preset configuration values and actual effective values in the configuration authentication. Inconsistent configuration data.
  • the historical inconsistency information table obtained by each configuration authentication is combined to form a historical inconsistency information table, so the inconsistent configuration data determined in the configuration authentication may be updated to the history obtained after the last configuration authentication.
  • adding inconsistent configuration data to the historical inconsistency information table may be before or after analyzing the specific limited reason for the inconsistent configuration data. There are two ways to update the historical inconsistency information table:
  • a configuration data may participate in multiple function configuration authentication. If the configuration data is in each configuration authentication, the actual effective value of the base station side is inconsistent with the preset configuration value of the background side, as shown in Table 4. Configuration data 5, then there are many records about this configuration data, but the configuration results other than the latest configuration results do not make much sense. Therefore, in the embodiment, another way of adding and re-adding is adopted: when it is determined that a certain inconsistent configuration data already exists in the historical inconsistency information table, the record of the inconsistent configuration data in the historical inconsistency information table is deleted. And add the current inconsistency record of the configuration data to the historical inconsistency information table. The de-duplication method is used to update the historical inconsistency information shown in Table 3, and another new historical inconsistency information table is obtained, as shown in Table 5:
  • the process of updating the history inconsistency information table by the re-adding method shown in FIG. 2 and the history inconsistency information deleting process shown in FIG. 3 can remove the redundant information in the historical inconsistency information table, and make the historical inconsistency information table more streamlined.
  • the flow of the configuration information management method provided in this implementation may be performed at the base station, or all of them may be performed on an Operation and Maintenance Center (OMC). It can be understood that part of the process may be performed on the base station, and another part may be executed. Executed by the OMC.
  • OMC Operation and Maintenance Center
  • the historical inconsistency information table may be sent to the OMC.
  • the OMC determines that the configuration data is limited because the impact of the configuration authentication can further remind the user or the network maintenance personnel that the network maintenance personnel will not misunderstand the configuration data because the base station Performance issues.
  • the configuration result of the configuration data is obtained by the base station, and the configuration result is sent to the OMC, and the OMC analyzes the restricted reason of the inconsistent configuration data.
  • the OMC obtains the configuration data is limited by the direct acquisition of the configuration result analysis, or is obtained indirectly through the base station obtaining the historical inconsistency information table.
  • the OMC provided in this embodiment obtains the historical inconsistency information table. The network maintenance personnel and users can query the historical inconsistency information table in the OMC to understand which configuration data is limited after the configuration authentication.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • This embodiment provides a configuration information management apparatus. Please refer to FIG. 4:
  • the configuration information management apparatus 40 provided in this embodiment includes a configuration result acquisition module 401 and an inconsistency data acquisition module 402.
  • the configuration result obtaining module 401 is configured to obtain a configuration result of each configuration data of the service function configuration after the service function configuration authentication of the base station is completed.
  • the obtained configuration result includes the preset configuration value of each configuration data background, the authorization configuration value of the base station side, and the actual effective value of the base station side.
  • the inconsistency data obtaining module 402 is configured to obtain configuration data that the actual effective value of the base station side does not match the preset configuration value of the background according to the configuration result.
  • the background network management system sends a preset configuration information to the foreground base station after the default configuration of each configuration data is obtained.
  • the background network management system performs batch data to the foreground base station. Transmission, transmitting the preset configuration value of each configuration data to the base station side.
  • the preset configuration value is received by the foreground base station to receive the service function configuration authentication.
  • the specific algorithm for the authentication can refer to Table 1 and Table 2. It can be understood that the object managed by the configuration information management apparatus provided by this embodiment is not only passed.
  • the configuration data for authentication performed by the authentication algorithms shown in Tables 1 and 2 should also be applied to configuration data using other authentication algorithms.
  • the configuration result obtaining module 401 obtains the configuration result of each configuration data of the service function configuration, and the general configuration result includes the preset configuration value, the authorization configuration value, and the final actual configuration data. Effective value.
  • the inconsistency data obtaining module 402 analyzes the configuration data in the obtained configuration result, compares the actual effective value with the preset configuration value, and determines which configuration data is involved in the configuration function authentication of the service function. limit. Generally, the actual value of the configuration data is less than or equal to the default configuration value. If the actual value of the configuration data is consistent with the preset configuration value, the configuration data is not restricted in the configuration authentication. If the actual effective value is less than the preset configuration value, the configuration data is limited in the configuration authentication.
  • the configuration information management device 40 includes a configuration result acquisition module 401 and an inconsistency data acquisition module 402, and includes a restricted reason analysis module 403. Please refer to FIG. 5 for obtaining the actual base station side in the inconsistency data acquisition module 402.
  • the restricted cause analysis module 403 analyzes the limited configuration data to obtain the reason that the limited configuration data is limited.
  • inconsistent configuration data is generally affected by two factors: one is the performance of the base station itself. When the base station itself fails or other performance problems, the actual effective value of the configuration data may be affected. Another factor is configuration authentication.
  • the actual effective value of the configuration data can only be determined according to the authorization configuration value. In this case, the actual effective value of the configuration data must also be inconsistent with its preset configuration value.
  • the restricted reason analysis module 403 includes a restricted determination submodule 4031, a first determination submodule 4032, and a second determination submodule 4033.
  • the restricted judgment sub-module 4031 is configured to determine whether the background preset configuration value of the inconsistent configuration data is limited by the authorized configuration value of the base station side, and the authentication configuration for the numeric type is determined by the background preset configuration value.
  • the size of the preset configuration value in the background must exceed the range that allows the configuration data to appear on the base station side.
  • the status indicated by the default configuration value of the configuration data in the background is inevitable. It is inconsistent with the status represented by the authorization configuration value on the base station side.
  • the restricted judgment sub-module 4031 determines whether the background preset configuration value of the inconsistent configuration data is limited by the authorized configuration value of the base station side, and actually determines whether the background preset configuration value of the configuration data meets the requirements of the authorized configuration value of the base station side. .
  • the determination result of the restricted judgment sub-module 4031 is NO, that is, when the actual effective value is not limited by the authorized configuration value
  • the second determining sub-module 4033 determines that the inconsistent configuration data is limited due to the performance of the base station itself. Because in this case, only the base station's own performance degradation or failure will cause the background preset configuration value to be inconsistent with the actual effective value of the base station side.
  • the restricted cause analysis module 403 in the configuration information management apparatus 40 in another example provided by the embodiment includes a restriction determination submodule 4031, a first determination submodule 4032, and a second determination submodule 4033.
  • the comparison sub-module 4034 and the third determination sub-module 4035 are further included. As shown in FIG.
  • the comparison sub-module 4034 And comparing the actual effective value of the inconsistent configuration data with the authorized configuration value.
  • the comparison result of the comparison submodule 4034 is that the actual effective value of the inconsistent configuration data is less than the authorized configuration value
  • the third determining submodule 4035 determines the inconsistent configuration data.
  • the limitation of the configuration is also limited by the performance of the base station. For example, the preset configuration value of the configuration data in the background is 1600, and the base station side limits the authorized configuration value of the configuration data to 1500, and after configuration authentication, The actual effective value of the configuration data is 1400. In this case, the background preset configuration value of the configuration data is subject to the authorized configuration value. System, but if only because of limited practical value should take effect as 1500 instead of 1400.
  • the configuration information management apparatus 40 of the present embodiment further includes an inconsistency information update module 404 and an inconsistency information deletion module 405 in addition to the configuration result obtaining module 401 and the inconsistency data obtaining module 402.
  • the inconsistent configuration data may be added to the current inconsistency information table, where the current inconsistency information table includes all preset configuration values and actual effective values in the configuration authentication. Inconsistent configuration data.
  • the inconsistency is more
  • the new module 403 integrates the current inconsistency information table obtained after each configuration authentication, and forms a historical inconsistency information table.
  • the inconsistency information updating module 404 sets the inconsistent configuration determined in the configuration authentication.
  • the inconsistency information update module 404 updates the inconsistent configuration data to the historical inconsistency information table before or after analyzing the specific reason for the inconsistent configuration data.
  • the inconsistency information update module 404 for updating the configuration data in which the actual effective value of the base station side in the configuration result is inconsistent with the preset configuration value in the background to the historical inconsistency information table includes directly adding the submodule 4041 and the deduplicating adder.
  • the direct addition submodule 4041 is set to directly add inconsistent configuration data to the historical inconsistency information table.
  • the update method is simple and fast, and no additional judgment or processing is required.
  • the inconsistent configuration data added by the sub-module 4041 may be added.
  • the historical inconsistency information table may accumulate more records, and the data of the configuration result is huge.
  • a configuration data can participate in multiple function configuration authentication. If the configuration data is in the configuration authentication, the actual effective value of the base station side is inconsistent with the preset configuration value of the background side, then the submodule is directly added. The 4041 needs to add a record of this configuration data multiple times, but the configuration results other than the latest configuration result do not make much sense.
  • the de-addition sub-module 4042 is further included in the embodiment, and the de-addition sub-module 4042 is configured to determine whether an inconsistent configuration data already exists in the historical inconsistency information table, and when the determination result is already existing, Delete the record of the inconsistent configuration data in the historical inconsistency information table, and add the inconsistent record of the configuration data in the configuration result to the historical inconsistency information table.
  • the information deletion module 405 is configured to delete the inconsistency information in the historical inconsistency information table according to the configuration data in which the actual effective value of the base station side and the preset configuration value in the background are consistent.
  • the specific inconsistency information deleting module 405 includes: a determining submodule 4051 and a deleting submodule 4052.
  • the determining sub-module 4051 is configured to determine whether the configuration data of the actual effective value of the base station side and the preset configuration value of the background in the configuration result of the configuration data of the secondary service function are in the historical inconsistency information table. If a certain configuration data already exists in the history information table, then the deletion sub-module 4052 is needed to delete the inconsistency information of the configuration data from the historical inconsistency information table, so as to ensure that all records recorded in the historical inconsistency information table are Information that is inconsistent with each configuration data.
  • each of the above-described modules or steps of the present invention can be implemented by a general-purpose computing device, which can be centralized on a single computing device or distributed across multiple computing devices.
  • they can be implemented by program code executable by the computing device, so that they can be stored in a storage medium (Read Only Memory (ROM) or Random Access Memory (RAM).
  • ROM Read Only Memory
  • RAM Random Access Memory
  • the memory, the disk, the optical disk are executed by the computing device, and in some cases, the steps shown or described may be performed in an order different from that herein, or they may be separately fabricated into an integrated circuit module.
  • multiple modules or steps of them can be implemented as a single integrated circuit module. Therefore, the invention is not limited to any particular combination of hardware and software.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the embodiment further provides a base station, which includes the configuration information management apparatus provided in the second embodiment. After the base station obtains the configuration result of the configuration data, obtains the inconsistent configuration data, and updates the inconsistent configuration data to the historical inconsistency information table, the historical inconsistency information table can be sent to the Operation and Maintenance Center (OMC). .
  • OMC Operation and Maintenance Center
  • This embodiment provides an Operation and Maintenance Center (OMC), which includes the configuration information management apparatus provided in Embodiment 2.
  • OMC Operation and Maintenance Center
  • the OMC obtains the historical inconsistency information table, and the OMC provides the historical inconsistency information table, and the network is obtained by the OMC. Maintenance personnel and users can query the historical inconsistency information table in the OMC to understand which configuration data is limited after the configuration authentication.
  • Embodiments of the present invention also provide a computer readable storage medium storing computer executable instructions for performing any of the methods described above.
  • the instructions are related to hardware (eg, a processor) that can be stored in a computer readable storage medium, such as a read only memory, a magnetic disk, or an optical disk.
  • a computer readable storage medium such as a read only memory, a magnetic disk, or an optical disk.
  • all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits.
  • each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program in a storage and a memory by a processor. / instruction to achieve its corresponding function.
  • the invention is not limited to any specific form of combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种配置信息管理方法及装置、操作维护中心或基站，包括：在基站的业务功能配置鉴权完成后，获取该次业务功能配置的每一个配置数据的配置结果，所述配置结果中包含：每一个配置数据的后台预设配置值以及每一个配置数据的基站侧实际生效值；根据所述配置结果得到基站侧实际生效值与后台预设配置值不一致的配置数据。

Description

配置信息管理方法及装置、操作维护中心或基站 技术领域
本文涉及但不限于通讯领域，尤其涉及一种配置信息管理方法及装置、操作维护中心或基站。
背景技术
在进行业务功能进行配置时，极有可能出现业务功能的性能下降甚至是被锁定的情况，但出现业务功能性能下降的原因并不是单一的，除去基站本身的性能问题导致的业务功能性能下降以外，基站对业务功能的配置鉴权也同样会让业务性能下降甚至是完全被锁定，请参考如下的配置鉴权示例：
配置鉴权包括两种类型，一种开关型，另一种为数值型。
请结合表1，开关型的配置鉴权，当授权配置值为“开”，若后台网管给配置数据的预设配置值也为“开”时，则基站侧给予该配置数据的实际生效值也为“开”，如表1中的配置数据1；当授权配置值为“关”，即使后台网管给配置数据的预设配置值为“开”，该配置数据的实际生效值也只能为“关”，如表1中的配置数据3。
表1
Figure PCTCN2016094653-appb-000001
针对数值型的配置鉴权，其具体的鉴权算法如表2所示，当后台网管给配置数据的预设配置值不超过授权配置值时，则按照后台网管的预设配置值对配置数据进行实际配置，如配置数据X；当后台网管给配置数据的预设配置值超过了授权配置值时，则配置数据的实际配置只能根据授权配置值进行确定，如配置数据Y。比如，带宽的授权配置值为500兆(M)，当后台网管为带宽配置预设配置小于500M时，配置鉴权允许带宽的预设配置值作为 其实际生效值；而当带宽的预设配置值大于500M时，配置鉴权则限制实际生效的带宽为500M。
表2
Figure PCTCN2016094653-appb-000002
从上述示例可知，配置鉴权的限制也会导致业务性能下降甚至是关闭。但是网络维护人员在不知情的情况下可能需要花费大量的时间对海量的配置数据进行查找，从而确定基站性能下降是否是因为配置鉴权的影响；更有甚者，网络维护人员会直接将授权配置导致的业务性能下降当作基站性能的问题，从而对基站进行不必要的检修。而配置鉴权而导致的业务性能下降的情况是在经常发生的，如果网络维护人员每一次发现业务性能下降都需要进行原因定位或者进行盲目的检修，那么花费的人力资源是不可估量的。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种配置信息管理方法及装置、操作维护中心或基站，能够当业务性能下降甚至是被关闭时，获取基站侧实际生效值与后台预设配置值不一致的配置数据。
本发明实施例提供一种配置信息管理方法，包括：
在基站的业务功能配置鉴权完成后，获取该次业务功能配置的每一个配置数据的配置结果，所述配置结果中包含：每一个所述配置数据的后台预设配置值以及每一个所述配置数据的基站侧实际生效值；
根据所述配置结果得到基站侧的实际生效值与后台的预设配置值不一致的配置数据。
可选的，配置信息管理方法还包括：将所述配置结果中基站侧实际生效值与后台预设配置值不一致的所述配置数据更新到历史不一致信息表中。
可选的，将所述配置结果中基站侧实际生效值与后台预设配置值不一致的所述配置数据更新到所述历史不一致信息表中的方式包括：
直接将所述配置结果中基站侧实际生效值与后台预设配置值不一致的所述配置数据添加到所述历史不一致信息表中；
或，在所述历史不一致信息表中去除所述历史不一致信息表与所述配置结果中同时存在的所述配置数据，并将所述配置结果中的该配置数据添加到所述历史不一致信息表中。
可选的，还包括：根据所述配置结果中基站侧实际生效值与后台预设配置值一致的所述配置数据对历史不一致信息表中的不一致信息进行删除。
可选的，对所述历史不一致信息表中不一致信息进行删除的过程包括：
判断该次业务功能配置的各所述配置数据的所述配置结果中基站侧实际生效值与后台预设配置值一致的所述配置数据在所述历史不一致信息表中是否存在；
若存在，则删除所述历史不一致信息表中的该配置数据。
可选的，还包括：所述配置结果中还包括每一个配置数据的基站侧授权配置值，在得到基站侧实际生效值与后台预设配置值不一致的配置数据之后，
比较基站侧实际生效值与后台预设配置值不一致的所述配置数据的后台预设配置值与所述配置数据的基站侧授权配置值，确定所述配置数据的受限原因。
可选的，确定所述配置数据的受限原因包括：
判断该配置数据的后台预设配置值是否受限于基站侧授权配置值；
当判断结果为是时，判定所述配置数据的受限原因包括受配置鉴权的限制；
当判定结果为否时，判定所述配置数据的受限原因为受基站自身性能限制。
可选的，还包括：当判断结果为是，且进行业务功能配置鉴权的为数值型配置数据时，比较所述配置数据基站侧的实际生效值与基站侧的所述授权 配置值的大小，若所述配置数据基站侧的实际生效值小于所述配置数据基站侧的所述授权配置值，则判定所述配置数据的受限原因同时还包括受基站自身性能限制。
本发明实施例还提供一种配置信息管理装置，包括：
配置结果获取模块，设置为在基站的业务功能配置鉴权完成后，获取该次业务功能配置的每一个配置数据的配置结果，所述配置结果包含每一个所述配置数据的后台预设配置值以及每一个所述配置数据的基站侧的实际生效值；
不一致数据获取模块，设置为根据所述配置结果得到基站侧实际生效值与后台预设配置值不一致的配置数据。
可选的，配置信息管理装置还包括：不一致信息更新模块，所述不一致信息更新模块设置为将所述配置结果中基站侧实际生效值与后台预设配置值不一致的配置数据更新到历史不一致信息表中。
可选的，所述不一致信息更新模块包括直接添加子模块与去重添加子模块两者中的至少一个：
所述直接添加子模块设置为直接将所述配置结果中基站侧实际生效值与后台预设配置值不一致的所述配置数据添加到所述历史不一致信息表中；
所述去重添加子模块设置为在所述历史不一致信息表中去除所述历史不一致信息表与所述配置结果中同时存在的所述配置数据，并将所述配置结果中的该配置数据添加到所述历史不一致信息表中。
可选的，还包括不一致信息删除模块，所述不一致信息删除模块设置为根据所述配置结果中基站侧实际生效值与后台预设配置值一致的配置数据对历史不一致信息表中的不一致信息进行删除。
可选的，所述不一致信息删除模块包括：
判断子模块，设置为判断该次业务功能配置的各配置数据的配置结果中基站侧实际生效值与后台预设配置值一致的配置数据在所述历史不一致信息表中是否存在；
删除子模块，设置为当所述判断子模块的判断结果为是时，删除所述历 史不一致信息表中的该配置数据。
可选的，还包括受限原因分析模块，所述受限原因分析模块设置为比较基站侧实际生效值与后台预设配置值不一致的所述配置数据的后台预设配置值与所述配置数据的基站侧授权配置值，确定所述配置数据的受限原因。
可选的，所述受限原因分析模块包括受限判断子模块、第一确定子模块和第二确定子模块：
所述受限判断子模块设置为判断该配置数据的后台预设配置值是否受限于基站侧授权配置值；
所述第一确定子模块设置为当所述判断子模块的判断结果为是时，判定所述配置数据的受限原因包括受配置鉴权的限制；
所述第二确定子模块设置为当所述判断子模块的判断结果为否时，判定所述配置数据的受限原因为受基站自身性能限制。
可选的，所述受限原因分析模块还包括比较子模块和第三确定子模块：
所述比较子模块设置为当所述受限判断子模块的判断结果为是，且进行业务功能配置鉴权的为数值型配置数据时，比较所述配置数据基站侧实际生效值与基站侧授权配置值的大小；
所述第三确定子模块设置为当所述配置数据基站侧实际生效值小于所述配置数据基站侧授权配置值时判定所述配置数据的受限原因同时还包括受基站自身性能限制。
本发明实施例还提供一种操作维护中心或基站，包括如上所述的配置信息管理装置。
本发明实施例还提出了一种计算机可读存储介质，存储有计算机可执行指令，计算机可执行指令用于执行上述描述的任意一个方法。
本发明实施例的有益效果是：
本发明实施例提供配置信息管理方法及装置、操作维护中心或基站，通过在配置信息管理装置在业务功能配置鉴权完成后，获取此次配置鉴权中各个配置数据的配置结果，然后对配置结果中的预设配置值以及实际生效值进行分析，获取到实际生效值与预设配置值不一致的配置数据。让网络维护人 员不需要在业务功能因非故障原因受限的情况下浪费时间进行原因定位，从而节省了人力物力，优化了资源配置。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明实施例一提供的配置信息管理方法流程图；
图2为本发明实施例一提供的以去重添加方式更新历史不一致信息表的流程图；
图3为本发明实施例一提供的历史不一致信息删除流程图；
图4为本发明实施例二提供的一种配置信息管理装置示意图；
图5为本发明实施例二提供的另一种配置信息管理装置示意图；
图6为图5中受限原因分析模块的一种示意图；
图7为图5中受限原因分析模块的另一种示意图；
图8为本发明实施例二提供的另一种配置信息管理装置示意图。
本发明的实施方式
下面通过具体实施方式结合附图对本发明作进一步详细说明。
本发明实施例通过在配置鉴权结束后，获取参与此次配置鉴权的每一个配置数据的配置结果，对配置结果中的预设配置值、实际生效值进行分析，可以直接获取实际生效值与预设配置值不一致的配置数据(以下将“实际生效值与预设配置值不一致的配置数据”简称为“不一致配置数据”)
为了更好阐述本发明，下面通过具体实施方式结合附图对本发明作进一步详细说明。
实施例一：
本实施例提供一种配置信息管理方法，具体的，请参考图1：
S101，在基站的业务功能配置鉴权完成后，获取该次业务功能配置的每一个配置数据的配置结果；
S102，根据所述配置结果得到基站侧实际生效值与后台预设配置值不一 致的配置数据。
在配置鉴权过程中，后台网管给出了每一个配置数据的预设配置后，会向前台基站发起预设配置信息同步，一般后台网管向前台基站进行批量数据传输，将每一个配置数据的预设配置值传输给基站侧。预设配置值在前台基站会接收业务功能配置鉴权，鉴权的具体算法可以参照表1和表2，可以理解的是本实施例提供的配置信息管理方法并不仅仅只适用于通过表1和表2所示的鉴权算法，也应当适用于其他鉴权算法。
当业务功能配置鉴权完成后，获取到该次业务功能配置的每一个配置数据的配置结果，一般地配置结果里面包含配置数据的预设配置值、授权配置值以及最终的实际生效值，对获取到的配置结果中的配置数据进行分析，比较实际生效值与预设配置值，就可以确定出参与此次业务功能配置鉴权中哪些配置数据受到了限制。一般来说，配置数据的实际生效值会小于或等于其预设配置值，若配置数据的实际生效值与其预设配置值一致，说明该配置数据在此次配置鉴权中并未受限；若实际生效值小于预设配置值，则说明该配置数据在该次配置鉴权中受到了限制。出现不一致配置数据一般是受以下两个因素的影响：一个是基站自身的性能，当基站自身出现故障或其他性能上的问题，配置数据的实际生效值可能会因此受到影响。另一个因素就是配置鉴权，当配置数据的预设配置值的状态或者大小不符合该配置数据的授权配置值时，该配置数据的实际生效值就只能依据授权配置值来确定，在这种情况下，配置数据的实际生效值也必然与其预设配置值不一致。
本实施例还提供一种配置数据管理方法，还包括：在获取到基站侧实际生效值与后台预设配置值不一致的配置数据后，对不一致数据受限的原因进行分析。为了进一步分析不一致配置数据受限的具体原因，需要对该不一致配置数据的预设配置值与授权配置值进行分析，判断不一致配置数据的后台预设配置值是否受限于基站侧的授权配置值，针对数值型配置鉴权，当后台预设配置值受限于基站侧的授权配置值时，后台的预设配置值的大小必然超出基站侧允许该配置数据出现的范围；针对开关型配置鉴权，后台给配置数据的预设配置值所表征的状态必然与基站侧的授权配置值所表征的状态不一致。判断不一致配置数据的后台预设配置值是否受限于基站侧的授权配置值， 实际上也就是判断配置数据的后台预设配置值是否符合基站侧的授权配置值的要求。当实际生效值并没有受到授权配置值的限制，则判定该不一致配置数据受限的原因为受基站自身性能的影响；当实际生效值受到授权配置值的限制，则判定该不一致配置数据受限的原因包括配置鉴权的影响；可选的，当判定不一致配置数据受限的原因包括配置鉴权的影响，且进行配置鉴权的为数值型配置数据权时，还可以进一步比较该不一致配置数据的实际生效值与授权配置值的大小，当该不一致配置数据的实际生效值小于授权配置值，则判定该不一致配置数据的受限原因同时还包括受基站自身性能限制，例如，后台给某一配置数据的预设配置值是1600，基站侧将该配置数据的授权配置值限定为1500，而经过配置鉴权后，该配置数据的实际生效值为1400，在这种情况下，该配置数据的后台预设配置值受到授权配置值的限制，但是若只是因为受限的原因，实际生效值应该为1500而非1400。
当确定配置数据的预设配置与实际配置不一致后，可以将该不一致配置数据添加到当前不一致信息表中，当前不一致信息表中包含此次配置鉴权中所有的预设配置值与实际生效值不一致的配置数据。将每次配置鉴权后得到的当前不一致信息表综合在一起就形成了历史不一致信息表，所以也可以将此次配置鉴权中确定的不一致配置数据更新到上次配置鉴权后获得的历史不一致信息表中，添加不一致的配置数据到历史不一致信息表中可以是在分析不一致配置数据具体的受限原因之前或者之后。具体的更新历史不一致信息表的方式有以下两种：
直接将不一致配置数据添加到历史不一致信息表中。这种更新方式简单、快捷，不需要做其他额外的判断与处理。若上次配置鉴权后获得的历史不一致信息表如表3所示：
表3
Figure PCTCN2016094653-appb-000003
在本次配置鉴权后将配置数据5和8添加至表3中，得到新的历史不一 致信息表，如表4：
表4
Figure PCTCN2016094653-appb-000004
采用上述更新方式在多次功能配置鉴权后，可能会积累较多的记录，配置结果的数据量庞大。另外，一项配置数据可以参与多次功能配置鉴权，若该项配置数据在每一次配置鉴权中都是基站侧的实际生效值与后台侧的预设配置值不一致，如表4中的配置数据5，那么关于此项配置数据的记录很多，但是除最近一次配置结果以外的其他配置结果并没有太大的意义。所以可选地，在本实施例中采用另一种去重添加的方式：当判断某一不一致配置数据在历史不一致信息表中已经存在的时候，删除历史不一致信息表中该不一致配置数据的记录，并将该配置数据当前的不一致记录添加到历史不一致信息表中。采用去重添加方式来更新表3所示的历史不一致信息，得到另一种新的历史不一致信息表，如表5：
表5
Figure PCTCN2016094653-appb-000005
可选的，本实施例中，提供以去重添加方式更新历史不一致信息表的流程，请参考图2：
S201，开始；
S202，选择配置数据的唯一编码、配置数据对应的管理对象名称以及管 理对象属性作为第一主关键字；
S203，遍历历史不一致信息表，判断历史不一致信息表中是否包含第一主关键字；
S204，若判断结果为是，则用当前配置结果中第一主关键字对应的配置数据替换历史不一致信息表中第一主关键字对应的配置数据，然后转至S206结束流程；
S205，若判断结果为否，则在历史不一致信息表中新建第一主关键字，并添加第一关键字对应的不一致配置数据，然后转至S206结束流程；
S206，结束。
在上述流程中，仅涉及到了在历史信息表中当前受限配置数据的新增与修改，并未对之前受限，当前已经不再受限的配置数据进行管理。当某项配置数据在之前的配置鉴权过程中存在过实际生效值其预设配置值不一致的情况，该配置数据的配置结果已经被录入历史不一致信息表中，但是在当前的配置鉴权过程中，其实际生效值已经与预设配置值相同，并不需要再记录在历史不一致信息表中，这时候需要将历史不一致信息表中该不一致信息删除掉，判断某一配置数据的实际生效值符合其预设配置值的要求时，开启历史不一致信息删除流程，具体的请参考图3所示：
S301，开始；
S302，选择配置数据的唯一编码、配置数据对应的管理对象名称以及管理对象属性作为第二主关键字；
S303，遍历历史不一致信息表，判断历史不一致信息表中是否包含第二主关键字；
S304，若判断结果为是，删除历史不一致信息表中第二主关键字所对应的不一致信息，然后转至S305结束流程；
S305，结束。
上述图2所示的以重添加方式更新历史不一致信息表的流程与图3所示的历史不一致信息删除流程能够去除历史不一致信息表中的冗余信息，使历史不一致信息表更加精简。
本实施提供的配置信息管理方法的流程可以全部在基站执行，也可以全部在操作维护中心(Operation and Maintenance Center，OMC)上执行，可以理解的是，也可以一部分流程在基站上执行，另一部分由OMC执行。
当上述流程全部在基站上执行时，执行结束后，可以将在历史不一致信息表发送给OMC。
当上述流程全部在OMC上执行时，在OMC确定出配置数据的受限是因为配置鉴权的影响时，可以进一步提醒用户或者网络维护人员，让网络维护人员不致误会配置数据受限是因为基站的性能问题。
当上述流程部分在基站上执行，另一部分由OMC执行时，例如由基站获取配置数据的配置结果，并将配置结果发送给OMC，由OMC对不一致配置数据的受限原因进行分析。
无论OMC获取到配置数据受限的原因是通过其本身直接获取配置结果分析得到，还是通过基站获取到历史不一致信息表而间接得到，另外，本实施例提供的OMC在获取到历史不一致信息表后，网络维护人员和用户可以在OMC查询历史不一致信息表，从而了解此次配置鉴权后，有哪些配置数据受限。
实施例二：
本实施例提供一种配置信息管理装置，请参考图4：
本实施例提供的配置信息管理装置40包括配置结果获取模块401和不一致数据获取模块402。
配置结果获取模块401设置为在基站的业务功能配置鉴权完成后，获取该次业务功能配置的每一个配置数据的配置结果。获取的配置结果中包含每一个配置数据后台的预设配置值、基站侧的授权配置值以及基站侧的实际生效值。
不一致数据获取模块402设置为根据配置结果得到基站侧的实际生效值与后台的预设配置值不一致的配置数据。
在配置鉴权过程中，后台网管给出了每一个配置数据的预设配置后，会向前台基站发起预设配置信息同步，一般后台网管向前台基站进行批量数据 传输，将每一个配置数据的预设配置值传输给基站侧。预设配置值在前台基站会接收业务功能配置鉴权，鉴权的具体算法可以参照表1和表2，可以理解的是本实施例提供的配置信息管理装置管理的对象并不仅仅是于通过表1和表2所示的鉴权算法进行鉴权的配置数据，也应当适用于使用其他鉴权算法的配置数据。
当业务功能配置鉴权完成后，配置结果获取模块401获取到该次业务功能配置的每一个配置数据的配置结果，一般配置结果里面包含配置数据的预设配置值、授权配置值以及最终的实际生效值。可选的，不一致数据获取模块402对获取到的配置结果中的配置数据进行分析，比较实际生效值与预设配置值，就可以确定出参与此次业务功能配置鉴权中哪些配置数据受到了限制。一般来说，配置数据的实际生效值会小于或等于其预设配置值，若配置数据的实际生效值与其预设配置值一致，说明该配置数据在此次配置鉴权中并未受限；若实际生效值小于预设配置值，则说明该配置数据在该次配置鉴权中受到了限制。
在本实施例中，配置信息管理装置40除了包括配置结果获取模块401和不一致数据获取模块402以外，还包括受限原因分析模块403，请参考图5在不一致数据获取模块402获取到基站侧实际生效值与后台预设配置值不一致的配置数据后，受限原因分析模块403会对受限的配置数据进行分析，得到受限的配置数据受限的原因。从理论上来说，出现不一致配置数据一般是受以下两个因素的影响：一个是基站自身的性能，当基站自身出现故障或其他性能上的问题，配置数据的实际生效值可能会因此受到影响。另一个因素就是配置鉴权，当配置数据的预设配置值的状态或者大小不符合该配置数据的授权配置值时，该配置数据的实际生效值就只能依据授权配置值来确定，在这种情况下，配置数据的实际生效值也必然与其预设配置值不一致。
为了进一步分析不一致配置数据受限的具体原因，请参考图6，受限原因分析模块403包括：受限判断子模块4031、第一确定子模块4032和第二确定子模块4033。
受限判断子模块4031设置为判断不一致配置数据的后台预设配置值是否受限于基站侧的授权配置值，针对数值型配置鉴权，当后台预设配置值受 限于基站侧的授权配置值时，后台的预设配置值的大小必然超出基站侧允许该配置数据出现的范围；针对开关型配置鉴权，后台给配置数据的预设配置值所表征的状态必然与基站侧的授权配置值所表征的状态不一致。受限判断子模块4031判断不一致配置数据的后台预设配置值是否受限于基站侧的授权配置值，实际上也就是判断配置数据的后台预设配置值是否符合基站侧的授权配置值的要求。当受限判断子模块4031的判断结果为否，即当实际生效值并没有受到授权配置值的限制时，第二确定子模块4033判定该不一致配置数据受限的原因为受基站自身性能的影响，因为在这种情况下，只有基站出现自身的性能下降或是故障才会引起后台预设配置值与基站侧的实际生效值不一致。当受限判断子模块4031的判断结果为是，即当实际生效值受到授权配置值的限制，则判定该不一致配置数据受限的原因包括配置鉴权的影响。可选地，本实施例提供的另一种示例中的配置信息管理装置40中的受限原因分析模块403除了包括受限判断子模块4031、第一确定子模块4032和第二确定子模块4033以外，还包括比较子模块4034和第三确定子模块4035，如图7，当受限判断子模块4031的判断结果为是，且进行配置鉴权的为数值型配置数据权时，比较子模块4034进一步比较该不一致配置数据的实际生效值与授权配置值的大小，当比较子模块4034的比较结果为该不一致配置数据的实际生效值小于授权配置值，第三确定子模块4035判定该不一致配置数据的受限原因同时还包括受基站自身性能限制，例如，后台给某一配置数据的预设配置值是1600，基站侧将该配置数据的授权配置值限定为1500，而经过配置鉴权后，该配置数据的实际生效值为1400，在这种情况下，该配置数据的后台预设配置值受到授权配置值的限制，但是若只是因为受限的原因，实际生效值应该为1500而非1400。
请参考图8，本实施例提供的配置信息管理装置40除了包括上述配置结果获取模块401、不一致数据获取模块402外，还包括：不一致信息更新模块404和不一致信息删除模块405。
当确定配置数据的预设配置与实际配置不一致后，可以将该不一致配置数据添加到当前不一致信息表中，当前不一致信息表中包含此次配置鉴权中所有的预设配置值与实际生效值不一致的配置数据。当然，若不一致信息更 新模块403将每次配置鉴权后得到的当前不一致信息表综合在一起，就会形成历史不一致信息表，在本实施例中，不一致信息更新模块404将此次配置鉴权中确定的不一致配置数据更新到上次配置鉴权后获得的历史不一致信息表中，不一致信息更新模块404更新不一致的配置数据到历史不一致信息表中可以是在分析不一致配置数据具体的受限原因之前或者之后。具体的，用于将配置结果中基站侧的实际生效值与后台的预设配置值不一致的配置数据更新到历史不一致信息表中的不一致信息更新模块404包括直接添加子模块4041和去重添加子模块4042：
直接添加子模块4041设置为直接将不一致配置数据添加到历史不一致信息表中。采用直接添加子模块4041进行更新时，更新方式简单、快捷，不需要做其他额外的判断与处理。
在多次功能配置鉴权后，直接添加子模块4041添加的不一致配置数据可能较多，历史不一致信息表中可能会积累较多的记录，配置结果的数据量庞大。另外，一项配置数据可以参与多次功能配置鉴权，若该项配置数据在每一次配置鉴权中都是基站侧的实际生效值与后台侧的预设配置值不一致，那么直接添加子模块4041需要多次添加此项配置数据的记录，但是除最近一次配置结果以外的其他配置结果并没有太大的意义。所以可选地，在本实施例中还包括去重添加子模块4042，去重添加子模块4042设置为判断某一不一致配置数据在历史不一致信息表中是否已经存在，当判断结果为已经存在时，删除历史不一致信息表中该不一致配置数据的记录，并将此次配置结果中该配置数据的不一致记录添加到历史不一致信息表中。
同样的，假设一项配置数据参与多次配置鉴权，那么可能会存在这样的情况：在上一次的配置鉴权结果中，该项配置数据的实际生效值与其预设配置值不一致，但是，在当前的配置鉴权中，该配置数据的实际生效值已经与其预设配置值一致了，此时，需要删除历史不一致信息表中该项配置数据的不一致信息，这时候，就需要用到不一致信息删除模块405，不一致信息删除模块405设置为根据配置结果中基站侧的实际生效值与后台的预设配置值一致的配置数据对历史不一致信息表中的不一致信息进行删除。具体的不一致信息删除模块405包括：判断子模块4051和删除子模块4052。
具体的，判断子模块4051设置为判断该次业务功能配置的每一个配置数据的配置结果中基站侧的实际生效值与后台的预设配置值一致的配置数据在历史不一致信息表中是否存在，若某一项配置数据在历史信息表中已经存在，那么就需要利用删除子模块4052将该项配置数据的不一致信息从历史不一致信息表中删除掉，以保证历史不一致信息表中记录的都是各个配置数据不一致的信息。
显然，本领域的技术人员应该明白，上述本发明的每一个模块或每一个步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储介质(只读存储器(ROM，Read Only Memory)或随机存取存储器(RAM，Random Access Memory)、磁碟、光盘)中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成一个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。所以，本发明不限制于任何特定的硬件和软件结合。
实施例三：
本实施例还提供一种基站，该基站包括实施例二提供的配置信息管理装置。当基站获取到配置数据的配置结果，获取到不一致配置数据，并将不一致的配置数据更新到历史不一致信息表之后，可以将在历史不一致信息表发送给操作维护中心(Operation and Maintenance Center，OMC)。
本实施例提供一种操作维护中心(Operation and Maintenance Center，OMC)，该OMC包括实施例二提供的配置信息管理装置。
无论OMC获取到配置数据受限的原因是通过其本身直接获取配置结果分析得到，还是通过基站获取到历史不一致信息表而间接得到，本实施例提供的OMC在获取到历史不一致信息表后，网络维护人员和用户可以在OMC查询历史不一致信息表，从而了解此次配置鉴权后，有哪些配置数据受限。
本发明实施例还提出了一种计算机可读存储介质，存储有计算机可执行指令，计算机可执行指令用于执行上述描述的任意一个方法。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储与存储器中的程序/指令来实现其相应功能。本发明不限于任何特定形式的硬件和软件的结合。
以上内容是结合具体的实施方式对本发明所作的进一步详细说明，不能认定本发明的具体实施只局限于这些说明。对于本发明所属技术领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干简单推演或替换，都应当视为属于本发明的保护范围。
工业实用性
上述技术方案节省了人力物力，优化了资源配置。

Claims (17)

  1. 一种配置信息管理方法，包括：
    在基站的业务功能配置鉴权完成后，获取该次业务功能配置的每一个配置数据的配置结果，所述配置结果中包含：每一个配置数据的后台预设配置值以及每一个配置数据的基站侧实际生效值；
    根据所述配置结果得到基站侧实际生效值与后台预设配置值不一致的配置数据。
  2. 如权利要求1所述的配置信息管理方法，还包括：将所述配置结果中基站侧实际生效值与后台预设配置值不一致的所述配置数据更新到历史不一致信息表中。
  3. 如权利要求2所述的配置信息管理方法，其中，将所述配置结果中基站侧实际生效值与后台预设配置值不一致的所述配置数据更新到所述历史不一致信息表中的方式包括：
    直接将所述配置结果中基站侧实际生效值与后台预设配置值不一致的所述配置数据添加到所述历史不一致信息表中；
    或，在所述历史不一致信息表中去除所述历史不一致信息表与所述配置结果中同时存在的所述配置数据，并将所述配置结果中的该配置数据添加到所述历史不一致信息表中。
  4. 如权利要求1-3任一项所述的配置信息管理方法，还包括：根据所述配置结果中基站侧实际生效值与后台预设配置值一致的所述配置数据对历史不一致信息表中的不一致信息进行删除。
  5. 如权利要求4所述的配置信息管理方法，其中，所述对历史不一致信息表中不一致信息进行删除，包括：
    判断该次业务功能配置的每一个所述配置数据的所述配置结果中基站侧实际生效值与后台预设配置值一致的所述配置数据在所述历史不一致信息表中是否存在；
    若存在，则删除所述历史不一致信息表中的该配置数据。
  6. 如权利要求1-3任一项所述的配置信息管理方法，还包括：
    所述配置结果中还包括每一个配置数据的基站侧授权配置值；在得到基站侧实际生效值与后台预设配置值不一致的配置数据之后，
    比较基站侧实际生效值与后台预设配置值不一致时的所述配置数据的后台预设配置值与所述配置数据的基站侧授权配置值，确定所述配置数据的受限原因。
  7. 如权利要求6任一项所述的配置信息管理方法，其中，确定所述配置数据的受限原因包括：
    判断该配置数据的后台预设配置值是否受限于基站侧授权配置值；
    当判断结果为是时，判定所述配置数据的受限原因包括受配置鉴权的限制；
    当判定结果为否时，判定所述配置数据的受限原因为受基站自身性能限制。
  8. 如权利要求7所述的配置信息管理方法，还包括：
    当判断结果为是，且进行业务功能配置鉴权的为数值型配置数据时，比较所述配置数据基站侧实际生效值与基站侧的所述授权配置值的大小，若所述配置数据基站侧实际生效值小于所述配置数据基站侧的所述授权配置值，则判定所述配置数据的受限原因同时还包括受基站自身性能限制。
  9. 一种配置信息管理装置，包括：
    配置结果获取模块，设置为在基站的业务功能配置鉴权完成后，获取该次业务功能配置的每一个配置数据的配置结果，所述配置结果中包含：每一个所述配置数据的后台预设配置值以及每一个所述配置数据后台的基站侧实际生效值；
    不一致数据获取模块，设置为根据所述配置结果得到基站侧实际生效值与后台预设配置值不一致的配置数据。
  10. 如权利要求9所述的配置信息管理装置，还包括：不一致信息更新模块，所述不一致信息更新模块设置为将所述配置结果中基站侧实际生效值与后台预设配置值不一致的配置数据更新到历史不一致信息表中。
  11. 如权利要求10所述的配置信息管理装置，其中，所述不一致信息更新模块包括直接添加子模块与去重添加子模块两者中的至少一个：
    所述直接添加子模块设置为直接将所述配置结果中基站侧实际生效值与后台预设配置值不一致的所述配置数据添加到所述历史不一致信息表中；
    所述去重添加子模块设置为在所述历史不一致信息表中去除所述历史不一致信息表与所述配置结果中同时存在的所述配置数据，并将所述配置结果中的该配置数据添加到所述历史不一致信息表中。
  12. 如权利要求9-11任一项所述的配置信息管理装置，还包括不一致信息删除模块，所述不一致信息删除模块设置为根据所述配置结果中基站侧实际生效值与后台预设配置值一致的配置数据对历史不一致信息表中的不一致信息进行删除。
  13. 如权利要求12所述的配置信息管理装置，其中，所述不一致信息删除模块包括：
    判断子模块，设置为判断该次业务功能配置的各配置数据的配置结果中基站侧实际生效值与后台预设配置值一致的配置数据在所述历史不一致信息表中是否存在；
    删除子模块，设置为当所述判断子模块的判断结果为是时，删除所述历史不一致信息表中的该配置数据。
  14. 如权利要求9-11任一项所述的配置信息管理装置，还包括受限原因分析模块，所述受限原因分析模块设置为比较基站侧实际生效值与后台预设配置值不一致的所述配置数据的后台预设配置值与所述配置数据的基站侧授权配置值，确定所述配置数据的受限原因。
  15. 如权利要求14所述的配置信息管理装置，其中，所述受限原因分析模块包括受限判断子模块、第一确定子模块和第二确定子模块：
    所述受限判断子模块设置为判断该配置数据的后台预设配置值是否受限于基站侧授权配置值；
    所述第一确定子模块设置为当所述判断子模块的判断结果为是时，判定所述配置数据的受限原因包括受配置鉴权的限制；
    所述第二确定子模块设置为当所述判断子模块的判断结果为否时，判定所述配置数据的受限原因为受基站自身性能限制。
  16. 如权利要求15所述的配置信息管理装置，所述受限原因分析模块还包括比较子模块和第三确定子模块：
    所述比较子模块设置为当所述受限判断子模块的判断结果为是，且进行业务功能配置鉴权的为数值型配置数据时，比较所述配置数据基站侧实际生效值与基站侧授权配置值的大小；
    所述第三确定子模块设置为当所述配置数据基站侧实际生效值小于所述配置数据基站侧授权配置值时判定所述配置数据的受限原因同时还包括受基站自身性能限制。
  17. 一种操作维护中心或基站，包括如权利要求9-16任一项所述的配置信息管理装置。
PCT/CN2016/094653 2015-11-27 2016-08-11 配置信息管理方法及装置、操作维护中心或基站 WO2017088528A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510856621.4 2015-11-27
CN201510856621.4A CN106817711A (zh) 2015-11-27 2015-11-27 配置信息管理方法及装置、操作维护中心或基站

Publications (1)

Publication Number Publication Date
WO2017088528A1 true WO2017088528A1 (zh) 2017-06-01

Family

ID=58762977

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/094653 WO2017088528A1 (zh) 2015-11-27 2016-08-11 配置信息管理方法及装置、操作维护中心或基站

Country Status (2)

Country Link
CN (1) CN106817711A (zh)
WO (1) WO2017088528A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109327324A (zh) * 2017-08-01 2019-02-12 国基电子（上海）有限公司 验证方法、电子装置、管理服务器及计算机可读存储介质
CN108632078B (zh) * 2018-03-13 2021-07-23 网宿科技股份有限公司 一种配置的获取方法
CN113839803A (zh) * 2020-06-24 2021-12-24 中兴通讯股份有限公司 配置网元数据的方法和装置、电子设备、存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1867123A (zh) * 2006-03-29 2006-11-22 华为技术有限公司 一种基站平滑升级的方法及装置
CN101087449A (zh) * 2007-07-02 2007-12-12 华为技术有限公司 调整电调塔放增益的方法、系统及基站
US20120002557A1 (en) * 2010-06-30 2012-01-05 4G Neuron, D.O.O. Method for Self Organizing Network Operation
CN102945262A (zh) * 2012-10-19 2013-02-27 大唐移动通信设备有限公司 一种rnc配置数据对比方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1867123A (zh) * 2006-03-29 2006-11-22 华为技术有限公司 一种基站平滑升级的方法及装置
CN101087449A (zh) * 2007-07-02 2007-12-12 华为技术有限公司 调整电调塔放增益的方法、系统及基站
US20120002557A1 (en) * 2010-06-30 2012-01-05 4G Neuron, D.O.O. Method for Self Organizing Network Operation
CN102945262A (zh) * 2012-10-19 2013-02-27 大唐移动通信设备有限公司 一种rnc配置数据对比方法和装置

Also Published As

Publication number Publication date
CN106817711A (zh) 2017-06-09

Similar Documents

Publication Publication Date Title
US9959306B2 (en) Partition-based index management in hadoop-like data stores
US9652271B2 (en) Autonomously managed virtual machine anti-affinity rules in cloud computing environments
US10552247B2 (en) Real-time monitoring alert chaining, root cause analysis, and optimization
JP6325001B2 (ja) 階層データ構造のノードにおいて再帰的イベントリスナを用いる方法およびシステム
US10229208B2 (en) Optimization of query execution
US9405589B2 (en) System and method of optimization of in-memory data grid placement
US20170193034A1 (en) Object data updating method and apparatus in an object storage system
US20180025007A1 (en) Method and system for adaptive processing of resource usage records
CN112650576A (zh) 资源调度方法、装置、设备、存储介质及计算机程序产品
WO2017088528A1 (zh) 配置信息管理方法及装置、操作维护中心或基站
US20200379670A1 (en) Method, apparatus, and computer program product for determining usage change rate of storage system
CN105260639A (zh) 一种脸部识别系统的数据更新的方法及装置
US10152383B2 (en) Expedited device backup, wipe, and enrollment
US10509767B2 (en) Systems and methods for managing snapshots of a file system volume
US9058470B1 (en) Actual usage analysis for advanced privilege management
US20210068025A1 (en) Optimizing private network during offload for user equipment performance parameters
US20130275546A1 (en) Systems and methods for the automated migration from enterprise to cloud storage
US9286055B1 (en) System, method, and computer program for aggregating fragments of data objects from a plurality of devices
CN113378093A (zh) 资源发布策略的确定方法、装置、电子设备及存储介质
US20180322412A1 (en) Ticket Routing
US20210328887A1 (en) Method for performing task processing on common service entity, common service entity, apparatus and medium for task processing
US10609180B2 (en) Facilitating dynamic establishment of virtual enterprise service platforms and on-demand service provisioning
US20150106899A1 (en) System and method for cross-cloud identity matching
CN109286532A (zh) 云计算系统中告警信息的管理方法和装置
CN111488117A (zh) 用于管理元数据的方法、电子设备和计算机可读介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16867755

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16867755

Country of ref document: EP

Kind code of ref document: A1