CN121174192A - Constraint verification methods, apparatus, systems, computer equipment, and readable storage media - Google Patents

Abstract

This application relates to a constraint verification method, apparatus, system, computer equipment, and readable storage medium. At the pico base station side, an operation instruction to be verified is acquired. If the operation instruction meets the initial verification conditions, at least one target configuration constraint rule matching the operation instruction is determined from the preset configuration constraint verification rule library corresponding to the pico base station. Based on the target configuration constraint rule, constraint verification is performed on the changed configuration data carried by the operation instruction. If the changed configuration data passes the constraint verification, the changed configuration data is synchronized to the device network management system. This single-end verification mechanism avoids the problem of complex development and maintenance and high manpower consumption caused by the strong coupling between the device network management system and the pico base station in configuration constraint rules in traditional technologies. It achieves decoupling between the device network management system and the pico base station, effectively improving the scalability and flexibility of configuration parameter constraint verification.

Description

Constraint verification method, constraint verification device, constraint verification system, computer equipment and readable storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a constraint verification method, device, system, computer device, and readable storage medium.

Background

The pico-cell is used as a key access device for improving network coverage and capacity, and is widely applied to indoor and high-density hot spot areas such as markets, office buildings and transportation hubs by virtue of the advantages of flexible deployment, accurate coverage and the like. However, in the operation and maintenance management of the current pico base station, there is a significant drawback in configuring the constraint checking mechanism. In the conventional technology, the same constraint rule is generally defined and implemented independently on the device network management side and the pico base station side, and verification is performed when the configuration is issued or the local operation is performed. The double-end synchronous verification mode causes a large amount of repeated work, increases the complexity and cost of development and maintenance, and has huge overall manpower consumption.

Aiming at the problems of complex development and maintenance and large manpower consumption caused by strong coupling between a network manager and a leather base station in the conventional technology, no effective solution is proposed at present.

Disclosure of Invention

Based on this, it is necessary to provide a constraint checking method, an apparatus, a system, a computer device and a readable storage medium for solving the above technical problems.

In a first aspect, the present application provides a constraint checking method applied to a pico base station, where the pico base station is in communication connection with a device network manager, the method includes:

Acquiring an operation instruction to be checked;

If the operation instruction to be checked meets the initial check condition, determining at least one target configuration constraint rule matched with the operation instruction to be checked from a preset configuration constraint check rule library corresponding to the leather base station;

Based on the target configuration constraint rule, performing constraint verification on the change configuration data carried by the operation instruction to be verified;

And synchronizing the change configuration data to the equipment network manager under the condition that the change configuration data passes constraint verification.

In one embodiment, the determining, from a preset configuration constraint verification rule base corresponding to the pico base station, at least one target configuration constraint rule matched with the operation instruction to be verified includes:

Determining an instantiation path corresponding to the operation instruction to be checked based on the operation instruction to be checked;

And according to the instantiation path, determining at least one target configuration constraint rule matched with the operation instruction to be verified from the preset configuration constraint verification rule base.

In one embodiment, the change configuration data includes an operation command, an operation object and a parameter to be configured corresponding to the operation object, and the performing constraint verification on the change configuration data carried by the operation command to be verified based on the target configuration constraint rule includes:

Based on the target configuration constraint rule, carrying out parameter integrity verification on the parameter to be configured to obtain a corresponding integrity verification result;

If the integrity check result is the missing necessary parameter, a first message is generated, and the first message is fed back to a target maintenance terminal for missing parameter error prompt, wherein the target maintenance terminal is one of a device network management maintenance terminal and a pico-base station maintenance terminal.

In one embodiment, the change configuration data includes an operation command, an operation object and a parameter to be configured corresponding to the operation object, the pico base station is configured with a preset configuration database, and the constraint checking of the change configuration data carried by the operation command to be checked based on the target configuration constraint rule includes:

identifying the operation type of the operation command;

If the operation type is an add command or a delete command, searching an associated object with a dependency relationship with the operation object in the preset configuration database;

and generating a second message based on the retrieved association object, and feeding the second message back to a target maintenance terminal for carrying out association error prompt, wherein the target maintenance terminal is one of a device network management maintenance terminal and a pico-base station maintenance terminal.

In one embodiment, the change configuration data includes an operation command, an operation object and a parameter to be configured corresponding to the operation object, the pico base station is configured with a preset configuration database, and the synchronizing the change configuration data to the device network manager includes:

writing the change configuration data into the preset configuration database under the condition that the change configuration data passes constraint verification;

Synchronizing the change configuration data to the equipment network manager based on an adaptation layer file issued by the pico base station along with the version;

The adaptation layer file refers to a metadata file for ensuring that the pico-base station and the equipment network management configuration semantics are consistent.

In one embodiment, the pico base station is deployed with a preset configuration database, the preset configuration database comprises a plurality of configuration objects, and the method further comprises:

In the starting stage of the pico-base station, performing constraint verification on each configuration object in the preset configuration database based on the preset configuration constraint verification rule base;

If the abnormal configuration object with the constraint verification failure exists in the preset configuration database, generating a third message corresponding to the abnormal configuration object, and feeding the third message back to the pico-base maintenance terminal for alarm display.

In one embodiment, the method further comprises:

The operation instruction to be checked is initially checked, wherein the initial check at least comprises semantic grammar validity check, operation command validity check, operation object validity check and parameter value validity check;

if the operation instruction to be checked passes the initial check, determining that the operation instruction to be checked meets an initial check condition.

In a second aspect, the present application provides a constraint checking apparatus, the apparatus comprising:

The acquisition module is used for acquiring an operation instruction to be checked;

the matching module is used for determining at least one target configuration constraint rule matched with the operation instruction to be checked from a preset configuration constraint check rule library corresponding to the leather base station if the operation instruction to be checked meets the initial check condition;

the verification module is used for carrying out constraint verification on the change configuration data carried by the operation instruction to be verified based on the target configuration constraint rule;

and the synchronization module is used for synchronizing the change configuration data to the equipment network manager under the condition that the change configuration data passes the constraint verification.

In a third aspect, the application provides a constraint verification system, which comprises an equipment network manager and at least one pico base station, wherein the pico base station is in communication connection with the equipment network manager;

the pico base station is used for executing the constraint checking method.

In a fourth aspect, the present application provides a computer device comprising a memory storing a computer program and a processor implementing the steps of the method as described above when the computer program is executed by the processor.

In a fifth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the steps of the method as described above.

In a sixth aspect, the application provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the method as described above.

The constraint verification method is applied to the pico-base station, the pico-base station is in communication connection with the equipment network manager, an operation instruction to be verified is obtained, if the operation instruction to be verified meets initial verification conditions, at least one target configuration constraint rule matched with the operation instruction to be verified is determined from a preset configuration constraint verification rule base corresponding to the pico-base station, constraint verification is conducted on change configuration data carried by the operation instruction to be verified based on the target configuration constraint rule, and the change configuration data are synchronized to the equipment network manager under the condition that the change configuration data pass the constraint verification. By adopting the single-end checking mechanism, the problems of complex development and maintenance and large manpower consumption caused by strong coupling between the equipment network manager and the pico-base station on configuration constraint rules in the traditional technology are avoided, decoupling between the equipment network manager and the pico-base station is realized, and the expansibility and flexibility of configuration parameter constraint checking are effectively improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the related art, the drawings that are needed in the description of the embodiments of the present application or the related technologies will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other related drawings may be obtained according to these drawings without inventive effort to those of ordinary skill in the art.

FIG. 1 is a schematic diagram of a constraint verification system in one embodiment;

FIG. 2 is a flow diagram of a constraint verification method in one embodiment;

FIG. 3 is a flow chart illustrating a parameter integrity checking step in one embodiment;

FIG. 4 is a flow chart illustrating the correlation verification step in one embodiment;

FIG. 5 is a flowchart illustrating a process for synchronizing configuration data according to one embodiment;

FIG. 6 is a schematic diagram of a preliminary verification in one embodiment;

FIG. 7 is a schematic diagram of a constraint verification system in accordance with one embodiment;

FIG. 8 is a flow chart of a constraint verification method in one embodiment;

FIG. 9 is a flow chart of a constraint verification method in another embodiment;

FIG. 10 is a block diagram of a constraint checking apparatus in one embodiment;

FIG. 11 is an internal block diagram of a computer device in one embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

The parameter configuration of the eNodeB/gNodeB base station is an indispensable key link in the scenes of new construction, capacity expansion, relocation and the like. The method has various operation modes, including but not limited to real-time configuration of parameters of the target base station through equipment network management, localized operation through a near-end maintenance platform of the base station, or rapid deployment through importing configuration data files under the scenes of batch opening and the like. In this process, how to effectively ensure the validity and effectiveness of the service parameters manually configured by the user or the parameters in the imported configuration data file has become a key factor for determining whether the base station can be successfully started or operated successfully.

In the current technical practice, especially in the field of macro station equipment, a common configuration constraint verification method mainly comprises the steps of synchronously defining OCL (Object Constraint Language) rules at two ends of a base station and matched equipment network management, or directly defining constraint logic at the equipment side, and ensuring that the network management side realizes the same verification mechanism so as to realize cross-system consistency management and control. This mode is viable in the context of macro stations being commercially large-scale and of adequate resources. However, in the field of pico-base stations, since the commercial scale is far smaller than macro-base stations and wide deployment has not been achieved in three major operator networks, there is a certain congenital deficiency in both the commercial application and the technical development. Under this background, the "double-ended synchronization check" mechanism that is the main stream in the macro station field is difficult to be directly applied to the pico-cell scenario, and mainly faces the following challenges:

first, the double-end implementation mechanism has high development cost, and is difficult to copy and popularize.

The macro station usually adopts a mode of realizing the same constraint check logic at both ends of the pico base station and the equipment network manager. However, for the manufacturers of the leather base station equipment with smaller scale and limited development resources, the mode means repeated development and continuous maintenance at the network management side, and the mode belongs to remarkable resource waste. Especially, in the face of the business requirement of frequent change of clients, if synchronous updating of the check rules at both ends is required, the check rules are difficult to support continuously from the aspects of technical implementation difficulty and human resource investment, and expandability and agile response capability are lacking.

Second, multi-vendor, multi-device environments exacerbate the synergistic complexity.

In practical deployment, the device network manager often needs to uniformly manage multiple types of devices, such as CPE, eNodeB, gNodeB, and may access the pico-cell devices from different vendors. Because each manufacturer has differences in parameter model, constraint semantics and implementation modes, if the network management side is required to perform technical alignment for each type of equipment and each configuration constraint, and continuously synchronize the frequently-changed technical details, huge communication cost and maintenance burden are brought. The technology consistency, the manpower matching and the solution coordination face real bottlenecks, and complete and efficient cross-manufacturer coordination is difficult to realize.

Aiming at the problems, the application provides a constraint verification method, which aims to concentrate constraint verification logic on a pico-cell equipment side to realize that the pico-cell independently completes constraint verification of changed configuration data, and a matched equipment network management side only needs to carry out minimized matching without participating in development and maintenance of specific business constraint rules, so that decoupling between the equipment network management and the pico-cell is realized, and the expansibility and flexibility of constraint verification of configuration parameters are effectively improved.

In one embodiment, as shown in fig. 1, fig. 1 is a schematic structural diagram of a constraint checking system in one embodiment, and the application provides a constraint checking system, which comprises a device network manager and at least one pico base station, wherein the pico base station is in communication connection with the device network manager.

The device network manager is used for centrally managing a plurality of pico-base stations, wherein the pico-base stations refer to small cellular network devices and are used for enhancing wireless signal coverage and capacity of a specific area.

In an exemplary embodiment, the pico-base station and device network management communication method may be implemented by, but is not limited to, using a standard protocol, such as TR069 protocol, which is not specifically limited herein.

In one embodiment, as shown in fig. 2, fig. 2 is a flow chart of a constraint checking method in one embodiment, and the constraint checking method is applied to a pico base station and comprises the following steps:

Step S201, obtain the operation instruction to be verified.

The operation instruction to be checked is triggered by a user operating a target operation object on the target maintenance terminal. The target maintenance terminal is one of a device network management maintenance terminal and a pico-base station maintenance terminal. In an exemplary embodiment, if the user operates the target object at the device network management maintenance terminal, the corresponding operation instruction to be checked is issued to the pico base station through the device network management maintenance terminal, and if the user operates the target object at the pico base station maintenance terminal, the corresponding operation instruction to be checked is issued to the pico base station through the pico base station maintenance terminal.

The operation command is a control command for indicating a specific management action executed on a target operation object, and the type and behavior semantics of the configuration operation are defined. The operation commands may include, but are not limited to, add commands, modify commands, delete commands. An operation object refers to a logical or physical entity acted upon by an operation command, i.e., a management object instance to which configuration data pertains. It is understood that the operation object is a manageable unit in the pico-base station configuration model, such as a cell, a physical port, IPv4, VLan, etc. And the parameters to be configured belong to a group of specific configuration attributes of the operation object and target values thereof, and are used for describing the expected state of the operation object after being changed. The parameters to be configured include a set of key-value pairs of parameter names and parameter values.

The specific form of the operation instruction to be checked may be, but not limited to, a custom configuration command, or an operation command based on an MML command (MAN MACHINE Language), or a parameter configuration request directly issued by a RPC (Remote Procedure Call) method based on a TR069 protocol, where the parameter configuration request may carry a parameter node path (PARAMETER PATH) and a target parameter value according with the TR181 data model specification.

In one exemplary embodiment, when the operation instruction to be verified adopts an MML command, the operation instruction to be verified is in the format of [ operation command type ] [ operation object type ]: parameter 1= [ value 1], [ parameter 2= [ value 2],.

In an exemplary embodiment, a user sets a target operation object on an equipment network management maintenance terminal or a pico-base station maintenance terminal, and then the equipment network management maintenance terminal or the pico-base station maintenance terminal issues an operation instruction to be checked to the pico-base station in an MML command format. The device network management side performs message transmission through an RPC method (SetParaValues/AddObject/DeleteObject and a corresponding response method).

Step S202, if the operation instruction to be checked meets the initial check condition, determining at least one target configuration constraint rule matched with the operation instruction to be checked from a preset configuration constraint check rule base corresponding to the leather base station.

The initial verification condition is used for ensuring that the operation instruction to be verified has basic legality, integrity and processibility before entering the target configuration constraint rule matching and depth constraint verification process, and preventing an invalid or malicious instruction from triggering a subsequent verification process. In an exemplary embodiment, after receiving a user operation and issuing an operation instruction to be verified (i.e., an MML command) of an OAM (Operations, administration, AND MAINTENANCE) process, the pico base station performs parsing and identifying (for example, identifying whether the operation instruction to be verified is a configuration command or a maintenance command) corresponding to the operation instruction to be verified, and further detects and determines validity of the operation instruction to be verified, for example, detects and determines whether each parameter name is correct and whether a parameter value is within a value range thereof, so as to complete preliminary verification. If the preliminary verification is not passed, returning a corresponding alarm to carry out error prompt.

The preset configuration constraint verification rule base is defined and developed on the pico-base station side, and is completely invisible to the equipment network management side. It should be noted that, in the conventional technology, a rule is generally defined by OCL (Object Constraint Language), however, in the actual implementation process, the OCL is completely dependent on the respective technical capabilities of the equipment manufacturer, and is not specific to the development language and the technical platform, and the target language for deriving the rule is also completely dependent on the development language and related supporting tools applied by the base station platform. Based on the definition, the derivation and the development of the base transceiver station configuration object and the configuration constraint rule are completed based on the configuration data specification model tool.

In an exemplary embodiment, the data specification model may be configured by using a standardized data specification model, for example, models such as TR181, TR196, TR098, etc., which need to be adaptively selected according to the actual application scenario, which is not specifically limited herein.

The generalized model tree exists only in theory. In practical application, specific object definition is needed to be made by combining business field module division and the like of a leather base station equipment manufacturer based on a model tree similar to a TR181 data model due to the reasons of hardware performance, implementation cost, technical difference, product evolution road sign difference, version iteration difference and the like of each manufacturer, and the like, and finally, the model tree finally appears in a product and solution matching in a MOC (Module Object Class ) form, for example, in gNodeB products in an NR mode, cellConfig nodes and parameters under the TR181 data model are very many, and for a generalized model tree, the model tree cannot be directly edited and developed by taking the model tree as a root node, and the model tree must be further subdivided into subdivision scenes such as cell parameters, access parameters and the like for interfacial, object and instantiation definition.

In one exemplary embodiment, in defining constraint rules, various implementations may be employed for different levels of configuration parameters:

For parameter level basic constraints (such as parameter types, value ranges, enumeration legitimacy, etc.), declarations can be made directly based on the TR181 data model specification at the parameter node definition stage. Such definitions are typically embodied in a companion XML configuration description file and its corresponding XSD (XML Schema Definition) file.

For constraints of standardized data formats (such as an IPv4 address, an IPv6 address, a PLMN ID, and the like), regular expressions can be used for unified definition, and when user configuration data triggers database operation of corresponding configuration data nodes, the regular expressions are automatically triggered to detect and execute.

For association constraints among parameters in the object, the definition can be directly performed in the object level of the configuration data specification model based on the expanded grammar or annotation format agreed in the field of the pico-cell. For example, custom tags or script logic are introduced on the basis of the TR181 model to describe dependency, mutex or conditional constraint relationships between parameters. In addition, a rule export mechanism can be defined, and the constraint rule is exported in a form of an independent file (such as JSON and XML), so that version management and updating are facilitated. The constraint rules between the objects may also be defined in a similar manner and derived from the association constraint between the parameters in the objects, which are not limited herein.

In addition, for the definition and the derivation of constraint relations among multiple instances of the same class or the same object, the constraint rules belong to post-verification constraint rules, and may or may not be triggered in time in the configuration process, but may be triggered in the protocol stack starting process.

It should be noted that, all constraint rules are defined, maintained and executed locally at the pico-cell side, so that the device network manager does not need to participate in the implementation process, single-ended closed-loop management of configuration constraint rules is realized, and development complexity and maintenance cost caused by synchronization of traditional double-ended rules are avoided.

It should be noted that, the number of the constraint rules of the target configuration is related to the operation instruction to be verified, and is not specifically limited herein.

Step S203, constraint verification is carried out on the change configuration data carried by the operation instruction to be verified based on the target configuration constraint rule.

The constraint verification at least comprises parameter type verification in the operation objects, parameter value range verification, parameter relation verification among parameters in the operation objects (such as parameter value constraint relation, parameter inclusion relation and the like), parameter constraint relation verification among the operation objects (such as parameter value constraint relation and parameter limitation relation among the operation objects), and parameter integrity verification.

Step S204, synchronizing the change configuration data to the device network manager under the condition that the change configuration data passes the constraint verification.

In an exemplary embodiment, the method for synchronizing the change configuration data to the device network manager may be to synchronize the change configuration data to the device network manager based on an adaptation layer file issued by the pico base station along with the version, where the adaptation layer file refers to a metadata file for ensuring that the pico base station and the device network manager have consistent configuration semantics. The adaptation layer file may be, but is not limited to, an XML file.

It should be noted that, between the pico-base station and the device network manager, the negotiation and alignment of semantics and grammar are performed based on an adaptation layer file issued by the pico-base station along with the version, where the adaptation layer file includes operation objects related to various services supported by the pico-base station current version, and parameter definitions and object model information associated with each operation object, and each operation object definition includes one or more information including an operation name, an object name, a parameter type, a parameter value, necessary online help, and the like.

It can be understood that, based on the adaptation layer file, the device network manager can realize cooperation (i.e. consistency of corresponding version) with the pico-base station device only by receiving the adaptation layer file, whether in a configuration change synchronization mechanism (such as parameter issuing and status reporting) or in a static parameter definition and adaptation layer model analysis process.

The method comprises the steps of enabling a user to send an operation instruction to be verified, carrying change configuration data, to a pico base station through the target maintenance terminal when the target maintenance terminal operates a target operation object, conducting preliminary verification on the operation instruction to be verified through the pico base station, generating corresponding messages to feed back the operation instruction to the target maintenance terminal to give an alarm if the operation instruction to be verified does not meet initial verification conditions, determining at least one target configuration constraint rule matched with the operation instruction to be verified from a preset configuration constraint verification rule base corresponding to the pico base station if the operation instruction to be verified meets the initial verification conditions, conducting constraint verification on the change configuration data carried by the operation instruction to be verified based on the target configuration constraint rule, for example, conducting parameter type verification in the operation object, parameter value range verification, parameter relation verification among parameters in the operation object, parameter constraint relation verification among the operation object and the like, and synchronizing the change configuration data to a network management device through an adaptation layer file provided by the pico base station side under the condition that the change configuration data passes the constraint verification.

In the embodiment, the constraint verification of the operation instruction to be verified is realized on the pico-cell side, and the operation instruction is directly synchronized to the equipment network manager side under the condition that the constraint verification passes, so that the equipment network manager does not need to participate in specific service constraint verification.

In one embodiment, determining at least one target configuration constraint rule matched with an operation instruction to be checked from a preset configuration constraint check rule base corresponding to a pico base station, including the following steps:

step 1, determining an instantiation path corresponding to an operation instruction to be checked based on the operation instruction to be checked.

The instantiation path refers to a specific parameter node path corresponding to an operation instruction to be checked.

In an exemplary embodiment, the method for determining the instantiation path corresponding to the operation instruction to be checked based on the operation instruction to be checked may be that a preset configuration data specification model is obtained, and the instantiation path corresponding to the operation instruction to be checked is determined based on the operation instruction to be checked and the configuration data specification model, for example, by analyzing changed configuration data of the operation instruction to be checked and combining with the configuration data specification model (for example, a TR181 data model), to obtain the parameter node instantiation path corresponding to the operation instruction to be checked.

And 2, determining at least one target configuration constraint rule matched with the operation instruction to be checked from a preset configuration constraint check rule base according to the instantiation path.

If the operation instruction to be checked meets the initial check condition, analyzing the operation instruction to be checked to obtain corresponding changed configuration data, generating a corresponding instantiation path by combining a preset configuration data specification model, further taking the instantiation path as an index, and matching in a preset configuration constraint check rule base to determine all target configuration constraint rules related to the operation instruction to be checked.

In the embodiment, the path is instantiated, so that the regular quick positioning and accurate matching can be realized, and the efficiency and reliability of constraint verification are improved.

In one embodiment, as shown in FIG. 3, FIG. 3 is a flow chart of a parameter integrity checking step in one embodiment, wherein the step of performing constraint checking on change configuration data carried by an operation instruction to be checked based on a target configuration constraint rule comprises the following steps:

Step S301, parameter integrity verification is carried out on parameters to be configured based on target configuration constraint rules, and corresponding integrity verification results are obtained.

The parameters to be configured belong to a group of specific configuration attributes of the operation object and target values thereof, and are used for describing the expected state of the operation object after being changed. The parameters to be configured include a set of key-value pairs of parameter names and parameter values.

Wherein the integrity check result includes a missing mandatory parameter and parameter integrity.

Step S302, if the integrity check result is that the necessary parameters are missing, a first message is generated, and the first message is fed back to the target maintenance terminal to carry out missing parameter error prompt.

The first message at least carries a first error code and a missing configuration parameter list. The first error code is used for representing that the current verification failure is caused by 'the parameter to be configured lacks the necessary parameter', and the missing configuration parameter list is used for indicating a user to supplement the complete configuration parameter. It should be noted that the first error Code may be, but is not limited to, defined based on the Fault Code structure in the TR069 protocol, which is not limited herein. The Fault Code is a structure body in the TR069 standard protocol, and the response Code (error Code) and the response message (character string) returned by the pico-base station side can be expanded according to the product requirement, which is not specifically limited herein.

In an exemplary embodiment, the first message may be, but is not limited to, an MML response format, or a custom response message, or a response message based on the TR069 protocol corresponding to the RPC method.

It should be noted that, the error code in the application is defined in the adaptation layer file at the leather base station side, so that the application can be decoupled with the equipment network management side better, and repeated development caused by FaultCode error code ID and character string content corresponding to the requirement or negotiation definition at the leather base station side at the equipment network management side is avoided.

The target maintenance terminal is one of a device network management maintenance terminal and a pico-base station maintenance terminal.

In an exemplary embodiment, if the operation instruction to be checked is issued through the device network management maintenance terminal, the target maintenance terminal is the device network management maintenance terminal, and if the integrity check result is that the necessary parameters are missing, the OAM process is transferred to the TR069 interface module, and the first message (such as an MML command message) is carried by a corresponding RPC response method, and is returned to the device network management maintenance terminal. The device network manager only needs to analyze the MML message presented therein. The user can perform the next operation through the error description in the MML message prompt. Meanwhile, the user can check and confirm the online help information matched with the page according to the online help information, and confirm the corresponding configuration constraint verification notice in detail.

In another embodiment, if the operation instruction to be checked is issued through the pico-cell maintenance terminal, the target maintenance terminal is the pico-cell maintenance terminal, and if the integrity check result is that the necessary parameters are missing, the operation instruction is returned in a first message (MML command message) form through the OAM process of the pico-cell and presented to the pico-cell maintenance terminal. The user carries out corresponding operation according to the missing parameter error prompt, and meanwhile, based on the online help page of the operation command, the user can check the corresponding constraint verification relation description to carry out detailed confirmation and subsequent operation.

In this embodiment, by performing parameter integrity check on the change configuration data, generating a first message when the integrity check result is that the necessary parameter is missing, and feeding back the first message to the target maintenance terminal to perform missing parameter error prompt, the integrity of the input data is ensured, and the operation efficiency of the user is improved through a first message feedback mechanism.

In one embodiment, as shown in FIG. 4, FIG. 4 is a flow chart of a relevance verification step in one embodiment, wherein the constraint verification of the change configuration data carried by the operation instruction to be verified based on the target configuration constraint rule comprises the following steps:

In step S401, the operation type of the operation command is identified.

The operation command refers to a control instruction for indicating a specific management action executed on a target operation object, and defines the type and behavior semantics of the configuration operation. The operation type of the operation command may include, but is not limited to, an add command, a modify command, and a delete command.

In step S402, if the operation type is an add command or a delete command, the associated object having a dependency relationship with the operation object is retrieved from the preset configuration database.

The pico-base station is provided with a preset configuration database, wherein the preset configuration database is a local database maintained by the pico-base station side. The preset configuration database comprises a plurality of configuration objects.

Wherein, the associated object refers to a configuration object which has logical dependency or binding with the operation object.

Step S403, a second message is generated based on the searched association object, and the second message is fed back to the target maintenance terminal for carrying out association error prompt.

The second message at least carries a second error code, an associated object list and dependency relation details, wherein the second error code is used for representing that the operation object depends on other configuration objects, the associated object list comprises at least one associated object on which the operation object depends or is depended, and the dependency relation details comprise specific dependency types, dependency conditions and operation constraints between the operation object and each associated object.

In an exemplary embodiment, the second message may be, but is not limited to, an MML response format, or a custom response message, or a response message based on the TR069 protocol for the corresponding RPC method.

It should be noted that the second error Code may be, but is not limited to, defined based on the Fault Code structure in the TR069 protocol, which is not specifically limited herein. The Fault Code is a structure body in the TR069 standard protocol, and the response Code (error Code) and the response message (character string) returned by the pico-base station side can be expanded according to the product requirement, which is not specifically limited herein.

The target maintenance terminal is one of a device network management maintenance terminal and a pico-base station maintenance terminal.

The method comprises the steps of detecting an operation command in change configuration data carried by an operation command to be checked, identifying the operation type of the operation command in the change configuration data carried by the operation command to be checked, searching an associated object with a dependency relationship in a preset configuration database locally deployed on a leather base station based on the operation object in the change configuration data if the operation type is an addition command or a deletion command, generating a second message based on the searched associated object, and feeding back the second message to a target maintenance terminal to prompt configuration association errors. For example, when the operation type is ADD operation, whether the preset configuration database contains the node which needs to be newly added at this time or not and whether the operation of the ADD needs to depend on other objects or not are required to be detected, if the dependency relationship exists, the dependent associated object is required to be searched, whether the associated object exists or not is detected, and corresponding prompt is carried out.

In this embodiment, by identifying the operation type of the operation command, and searching the association object having a dependency relationship with the operation object in the preset configuration database when the operation type is the add command or the delete command, generating the second message based on the searched association object and feeding back the second message to the target maintenance terminal for performing the association error prompt, potential conflict can be identified before configuration change, service interruption caused by misoperation is prevented, and configuration operation safety and controllability are improved.

In one embodiment, as shown in fig. 5, fig. 5 is a flow chart of a change configuration data synchronization step in one embodiment, and in the case that the change configuration data passes the constraint check, the change configuration data is synchronized to the device network manager, which includes the following steps:

In step S501, when the change configuration data passes the constraint check, the change configuration data is written into the preset configuration database.

The method includes the steps that based on a target database interface function corresponding to an operation instruction to be checked, changing configuration data are written into a preset configuration database, and meanwhile, the updated preset configuration database is synchronized to a device network manager, so that the device network manager updates a self-deployed database according to the updated preset configuration database.

Step S502, based on the adaptation layer file issued by the pico base station along with the version, the change configuration data is synchronized to the equipment network manager.

The adaptation layer file refers to a metadata file for ensuring that the configuration semantics of the pico base station and the equipment network manager are consistent.

It should be noted that, between the pico-base station and the device network manager, the negotiation and alignment of semantics and grammar are performed based on an adaptation layer file issued by the pico-base station along with the version, where the adaptation layer file includes operation objects related to various services supported by the pico-base station current version, and parameter definitions and object model information associated with each operation object, and each operation object definition includes one or more information including an operation name, an object name, a parameter type, a parameter value, necessary online help, and the like.

It can be understood that, based on the adaptation layer file, the device network manager can realize the coordination (i.e. the consistency of the corresponding version) with the pico-base station device only by receiving the adaptation layer file, whether in the configuration change synchronization mechanism (such as parameter issuing and status reporting) or in the static parameter definition and adaptation layer model analysis process.

In an exemplary embodiment, under the condition that the change configuration data passes constraint verification, the change configuration data is written into a preset configuration database, and based on an adaptation layer file issued by the pico-base station along with the version, the change configuration data is synchronized to the equipment network manager, so that decoupling of the pico-base station side and the equipment network manager side is realized, and the problem of repeated verification of the equipment network manager side is effectively avoided.

In one embodiment, the pico base station is deployed with a preset configuration database, the preset configuration database comprises a plurality of configuration objects, and the constraint checking method further comprises the following steps:

step1, in the starting stage of the pico-base station, constraint verification is carried out on each configuration object in a preset configuration database based on a preset configuration constraint verification rule base.

Wherein the initiation phase may be a protocol stack initiation phase, wherein a protocol stack may be understood as a collection of base station software, e.g. functions of the various modules of the BBU software part, collectively referred to as "protocol stack".

And step 2, if an abnormal configuration object with constraint verification failure exists in the preset configuration database, generating a third message corresponding to the abnormal configuration object, and feeding the third message back to the pico-base maintenance terminal for alarm display.

It should be noted that if a configuration data file error occurs, the pico-base station may fail to start, so that constraint verification needs to be performed on each configuration object in the preset configuration database in the pico-base station start stage.

The third message at least carries a third error code, an abnormal configuration object list and verification failure reason details, wherein the third error code is used for representing that abnormal configuration is detected in a starting stage, the abnormal configuration object list comprises at least one abnormal configuration object which fails to be verified, and the verification failure reason details comprise constraint rule types and details violated by each abnormal configuration object. It should be noted that the third error Code may be, but is not limited to, defined based on the Fault Code structure in the TR069 protocol, which is not specifically limited herein.

In an exemplary embodiment, the third message may be, but is not limited to, an MML response format, or a custom response message, or a response message based on the TR069 protocol for the corresponding RPC method.

In the starting stage of the pico-base station, the constraint verification is carried out on each configuration object in a preset configuration database based on a preset configuration constraint verification rule base, if an abnormal configuration object with failed constraint verification exists in the preset configuration database, a third message corresponding to the abnormal configuration object is generated, and the third message is fed back to the pico-base station maintenance terminal for alarm display.

In this embodiment, in the starting stage of the pico-cell, constraint verification is performed on each configuration object in the preset configuration database, so that reliable starting and stable operation of the pico-cell device can be ensured, and meanwhile, configuration objects in the preset configuration database are ensured to conform to configuration constraint rule definition, so that manually modified data nodes are prevented from entering the system, and timely verification prompt and alarm report are performed on important configuration constraint relations.

In one embodiment, the constraint verification method further comprises the steps of:

step 1, performing initial verification on an operation instruction to be verified.

The initial verification at least comprises semantic grammar validity verification, operation command validity verification, operation object validity verification and parameter value validity verification.

And step 2, if the operation instruction to be checked passes the initial check, determining that the operation instruction to be checked meets the initial check condition.

The method comprises the steps of obtaining an operation instruction to be checked by a pico-base station, carrying out initial checking such as semantic grammar validity checking, operation command validity checking, operation object validity checking, parameter value validity checking and the like on the operation instruction to be checked, determining that the operation instruction to be checked meets initial checking conditions if the operation instruction to be checked passes all the initial checking, generating a fourth message if the operation instruction to be checked does not pass any one of the initial checking, and feeding the fourth message back to a pico-base station maintenance terminal or a device network management maintenance terminal for alarm display, wherein the fourth message at least carries a fourth error code, and the fourth error code is used for representing the error type of initial checking failure.

In this embodiment, the operation instruction to be checked is initially checked, so that the operation instruction to be checked can be ensured to have basic legality, integrity and processibility before entering the target configuration constraint rule matching and deep constraint checking flow, and the subsequent checking flow is prevented from being triggered by an invalid or malicious instruction.

In a specific embodiment, when a user operates a target operation object (configuration/maintenance object) on the device network management maintenance terminal or the pico-base station maintenance terminal, the user may use the standard TR069 protocol to interact with each other in an RPC method, or use a custom json message, or use an MML protocol to interact with each other, which is not limited herein specifically.

In a specific embodiment, a complete constraint verification process is implemented on the pico-base station device, and only limited matching is performed on the pico-base station device, which means that when the pico-base station device side issues with a version, a corresponding adaptation layer file is provided to the pico-base station device, wherein the adaptation layer file includes a network management matching model file corresponding to the pico-base station device side model one by one, and the network management matching model file includes an operation command (adding, modifying or deleting), an operation object (node name, or maintaining an operation function name), a parameter name, a parameter type, a parameter ID, a parameter value range, a corresponding online help file name, and a matched online help file, and definitions (codeValue, faultString) of FaultCode based on a TR069 protocol. It can be understood that the adaptation layer file is used as a reference standard matched with the device network manager, so that the device network manager only needs to issue instructions, does not need to pay attention to the logic inside the pico-base station device and the specific implementation method of configuration constraint verification, realizes decoupling of the device network manager and the pico-base station, and improves the applicability and expandability of the constraint verification method.

In one embodiment, the navigational tree is defined on the pico base station side and provided to the device network manager in the form of an adaptation layer file (typically an XML file or other format of part of the content). The device network manager analyzes the structural elements according to the adaptation layer file, dynamically generates a corresponding management page and displays the parameter values, and can facilitate the management of the device network manager and the matched pico-base station device based on the parameter values. And meanwhile, the configuration constraint check logic is completely arranged on the pico-base station side for execution, so that the service coupling of the equipment network manager in the parameter management process is relieved, and the system development and maintenance cost is reduced.

It should be noted that the display content of the navigation tree node is organized based on the function set provided by the pico-cell product, each equipment manufacturer can autonomously define the node hierarchical structure and the presentation mode of the navigation tree according to the product planning path or the user interface design style, and the function sub-interface associated with the navigation tree comprises the functions of configuration management, maintenance operation, software upgrading, alarm management, performance monitoring and log management of the base station.

In one particular embodiment, the preliminary verification is performed with reference to FIG. 6, wherein checkParamValueUInt is used to check the parameter values of the unsigned integer type to ensure that they are within the specified unsigned integer range. checkParamValueInt for checking parameter values of signed integer types to ensure that they are within a specified signed integer range. checkParamValueDateTime for checking parameter values of date, date time or time type, ensuring that they are correctly formatted and conform to the expected time frame. checkParamValueString checking the parameter values of various character string types, including IP address, subnet mask, enumeration value, etc., to ensure that the format is correct and meets the specific rules. checkParamValueDouble for checking the parameter values of the double-precision floating point number type, ensuring that they are within a reasonable numerical range. checkParamValueBoolean for checking the value of a boolean type parameter, ensuring that it is a valid boolean value (e.g. true or false).

Wherein checkParamValueUInt includes, xsd unsignedByte, unsigned byte type, corresponding to C/C++ type uint8_t. xsd unsignedShort unsigned short integer, corresponding to C/C++ type uint16_t. xsd unsignedInt unsigned integer, corresponding to C/C++ type uint32_t. xsd unsignedLong unsigned integer, corresponding to C/C++ type uint64_t.

CheckParamValueInt includes xsd: byte type, corresponding to C/C++ type int8_t. xsd is short, short integer, corresponding to C/C++ type int16_t. xsd, int, integer, corresponding to the C/C++ type int32_t. xsd, long, corresponding to C/C++ type int64_t.

CheckParamValueDateTime includes xsd: DATE type, corresponding to custom type DATE. xsd, dateTime, date and time type, corresponding to custom type DATETIME. xsd is TIME, TIME type, and corresponding custom type TIME.

CheckParamValueString includes an IPv 4-IPv 4 address string, corresponding to a custom type IPv4.IPv6 address character string, corresponding to user-defined type IPv6.IP is IPv4 or IPv6 address character string corresponding to user-defined type IPv4/IPv6. NET-subnet mask string, corresponding to custom type submask. SELECT, enumerate the type string, correspond to custom type enum. STR is a common character string corresponding to custom type string.

CheckParamValueDouble includes xsd double-precision floating point number type, corresponding to C/C++ double.

CheckParamValueBoolean includes xsd: boolean type, corresponding to C/C++ type boost.

In a specific embodiment, the constraint verification system comprises a device network manager and at least one pico base station, wherein the pico base station is in communication connection with the device network manager. The pico base station is configured to perform the constraint checking method described in any one of the above embodiments. Referring to fig. 7, the device network manager at least includes a network manager maintenance station LMT, a device network manager server, a device network manager MML module, and a device network manager adaptation layer module. The pico base station at least comprises a base station near-end maintenance platform webLMT, a network management agent module, an MML module, a model resource management module, a configuration agent module, a DB module, a verification rule agent module, a service verification module and the like.

The MML module is used for performing preliminary verification on the operation instruction to be verified, for example, completing the lexical and grammatical analysis of the MML command and the basic verification of the parameter node (including parameter type, parameter value and the like). The configuration agent module is used for completing the conversion from the operation instruction to be checked (MML command or custom instruction) to the parameter node instantiation path, searching in the corresponding preset configuration database DB according to the defined operation command (adding, modifying) and other instructions, and judging whether the operated object exists, is repeated or not and the logic conversion from the parameter value to the actual data. The configuration agent module is also used for matching the corresponding preset configuration constraint check rule base according to the parameter list carried by the operation instruction to be checked (adding/modifying and the like), accurately matching the corresponding preset configuration constraint rule base to the target configuration constraint rule to be triggered, executing the preset configuration constraint rule one by one, continuously matching the next target configuration constraint rule if the execution is successful, and otherwise, directly returning a check prompt to the target maintenance terminal. For different maintenance terminals, the corresponding operation response message format can be encapsulated according to the implementation of the maintenance terminals, and the operation response message format can be an MML response message, or a custom response message, or a response message based on a TR069 protocol and corresponding to an RPC method, and the corresponding error prompt is carried through FaultCode, so that the equipment network management side can perform corresponding conversion and display according to the adaptation layer file provided by the pico base station side.

In a specific embodiment, taking the base transceiver station maintenance terminal to initiate constraint verification as an example, referring to fig. 8, the detailed steps are as follows:

First, the initialization phase:

Initialization of the protocol stack (here mainly the OAM process-related emphasis).

The initialization of the MML module of the pico-cell mainly completes the flow initialization of processing tasks and the loading and analysis processing of model resource files, wherein the loading processing comprises MML commands, pages of various functions defined by a GUI interface, parameter meanings, parameter value ranges and the like.

And loading the model resource management module, wherein in the process of loading the MML module, an interface of the module is called to finish loading related contents of the model resource, and the loading of contents such as field names, field IDs, various prompt information resources, error code resources, check rule resource libraries, various association rule definition resource libraries and the like of various multilingual resources (Chinese and English) is mainly contained.

The initialization process mainly comprises loading a preset configuration constraint check rule base, initializing a check rule agent module, initializing a service check rule module, calling an MIB interface, completing registration of the MIB of the check rule, and completing initialization of webLMT processes. Wherein:

Second, user login phase:

With the login operation of the user, after the login information of the user is input, the TCP connection between the foreground and the background is performed webLMT. TCP connection between web background process and OAM process. In the initialization process webLMT, the loading of the navigation tree is completed, and after the login of the corresponding user is successful, the complete navigation tree node, all levels of submenus contained below the complete navigation tree node and pages with corresponding functions are displayed on webLMT.

Third, constraint verification phase:

The user performs configuration change operations (either for GUI configuration changes or for MML configuration changes) on webLMT pages as needed. webLMT the foreground assembles json message and sends it to the web background process and further forwards it to the OAM process (web proxy module) for transfer to the MML module. In the MML module, grammar and lexical analysis of the MML are finished first, and whether the MML belongs to a maintenance command or a configuration command is further identified. The MML module further forwards the configuration object to the configuration proxy module for processing the configuration flow, wherein the corresponding relation from the MML command character string instruction to the specific service object is analyzed, and in the module, whether the currently operated configuration object exists, whether the parameters are complete, whether the parameter values accord with the service constraint relation and the like are analyzed according to the MML command. In the configuration agent module, the specific service object identified according to the MML command character string further updates the service verification rule parameter path, wherein the service verification rule corresponding to the specific configuration object is arranged above the service verification rule. And the configuration agent module is used for completing the analysis of all parameter values and calling the MIB interface (interface function for operating the DB file), wherein the MIB interface mainly comprises (operation interfaces such as addition, modification and deletion), and in the corresponding modification interface, a specific check rule is identified according to a specific parameter path corresponding to the carried specific parameter value, and the calling of the corresponding check rule is further triggered. Or return a list of parameters that the client lacks because of the lack of necessary parameters. And if the verification rule is successfully executed, triggering the operation of writing into the DB file, otherwise, returning to the corresponding page according to the error prompt, and prompting the user to perform the corresponding operation.

In a specific embodiment, taking the device network management maintenance terminal to initiate constraint verification as an example, referring to fig. 9, the detailed steps are as follows:

The pico base station and the equipment network manager communicate based on https information, and the bottom layer of the TR069 protocol is also a TCP connection. On the ACS equipment network management, after the user performs configuration change operations such as configuration parameter setting and the like on the designated base station, the configuration change operations are issued to the pico-base station equipment by a corresponding RPC method.

And the CpeToAcs interface module of the pico-base station completes TCP information issued by the ACS equipment network management and forwards the TCP information to the TR069 proxy module for parameter analysis and flow connection of the RPC method.

When the device network manager supports the MML command, the TR069 proxy module directly forwards the MML module to perform configuration flow processing, which is consistent with the processing flow of the MML module/OAM and the later in fig. 8. In fig. 9, mainly related to the docking scenario of the non-MML command, the TR069 proxy module triggers the call of the corresponding interface function (add, modify or delete) of the MIB interface module, where "add", "delete" mainly relates to checking whether the configuration object exists (add), whether the configuration object does not exist (delete), and so on. Verification rule calls mainly involve modification links to configuration parameter values (involving "add", "modify" objects or parameters). In the MIB interface function calling process, a check rule agent module is triggered, and calling execution of the corresponding service check rule is further identified. And performing verification rule matching according to the user input parameters, triggering verification execution of the corresponding rule when the user input parameters are completely matched, performing DB file writing operation after successful execution, and otherwise, returning an error prompt.

It can be understood that the constraint verification method of the application can be realized by the equipment network manager and the pico-base station equipment at the same time or directly by the pico-base station equipment, and when the corresponding configuration constraint verification function is realized by the pico-base station equipment alone, the equipment network manager only needs to perform corresponding perception, and the perception capability can comprise error verification prompts fed back through the pico-base station and online help (for parameter constraint verification description or object-level constraint verification prompt description) provided by the pico-base station equipment.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a constraint verification device for realizing the constraint verification method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of one or more constraint verification devices provided below may be referred to the limitation of the constraint verification method hereinabove, and will not be repeated herein.

In an exemplary embodiment, as shown in fig. 10, there is provided a constraint checking apparatus, including an acquisition module 1001, a matching module 1002, a checking module 1003, and a synchronization module 1004, wherein:

an obtaining module 1001, configured to obtain an operation instruction to be verified;

the matching module 1002 is configured to determine, if the operation instruction to be checked meets the initial check condition, at least one target configuration constraint rule matching the operation instruction to be checked from a preset configuration constraint check rule library corresponding to the pico base station;

the verification module 1003 is configured to perform constraint verification on the change configuration data carried by the operation instruction to be verified based on the target configuration constraint rule;

And the synchronization module 1004 is configured to synchronize the change configuration data to the device network manager if the change configuration data passes the constraint verification.

The constraint verification device realizes constraint verification of the operation instruction to be verified on the pico-cell side, and is directly synchronized to the equipment network manager side under the condition that the constraint verification is passed, so that the equipment network manager does not need to participate in specific service constraint verification.

In one embodiment, the matching module 1002 is further configured to:

determining an instantiation path corresponding to the operation instruction to be checked based on the operation instruction to be checked;

According to the instantiation path, at least one target configuration constraint rule matched with the operation instruction to be checked is determined from a preset configuration constraint check rule library.

In one embodiment, the change configuration data includes an operation command, an operation object, and a parameter to be configured corresponding to the operation object, and the verification module 1003 is further configured to:

Based on the target configuration constraint rule, carrying out parameter integrity verification on the parameters to be configured to obtain a corresponding integrity verification result;

If the integrity check result is the missing necessary parameter, a first message is generated, and the first message is fed back to a target maintenance terminal for error prompt of the missing parameter, wherein the target maintenance terminal is one of a device network management maintenance terminal and a pico-base station maintenance terminal.

In one embodiment, the change configuration data includes an operation command, an operation object, and a parameter to be configured corresponding to the operation object, where the pico base station is configured with a preset configuration database, and the verification module 1003 is further configured to:

identifying the operation type of the operation command;

If the operation type is an add command or a delete command, searching an associated object with a dependency relationship with the operation object in a preset configuration database;

and generating a second message based on the retrieved association object, and feeding the second message back to the target maintenance terminal for carrying out association error prompt, wherein the target maintenance terminal is one of the equipment network management maintenance terminal and the pico-base station maintenance terminal.

In one embodiment, the change configuration data includes an operation command, an operation object, and a parameter to be configured corresponding to the operation object, a preset configuration database is deployed on the pico base station, and the synchronization module 1004 is further configured to:

Writing the change configuration data into a preset configuration database under the condition that the change configuration data passes constraint verification;

synchronizing the changed configuration data to the equipment network manager based on the adaptation layer file issued by the pico base station along with the version;

the adaptation layer file refers to a metadata file for ensuring that the configuration semantics of the pico base station and the equipment network manager are consistent.

In one embodiment, the pico base station is deployed with a preset configuration database, wherein the preset configuration database comprises a plurality of configuration objects, and a verification module 1003 is further configured to:

In the starting stage of the pico-base station, based on a preset configuration constraint verification rule base, performing constraint verification on each configuration object in a preset configuration database;

If an abnormal configuration object with constraint verification failure exists in the preset configuration database, generating a third message corresponding to the abnormal configuration object, and feeding the third message back to the pico-base maintenance terminal for alarm display.

In one embodiment, the verification module 1003 is further configured to:

the method comprises the steps of carrying out initial verification on an operation instruction to be verified, wherein the initial verification at least comprises semantic grammar validity verification, operation command validity verification, operation object validity verification and parameter value validity verification;

if the operation instruction to be checked passes the initial check, determining that the operation instruction to be checked meets the initial check condition.

The various modules in the constraint checking apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one exemplary embodiment, a computer device is provided, which may be a server, and the internal structure thereof may be as shown in fig. 11. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is for storing constraint verification related data. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a constraint checking method.

It will be appreciated by those skilled in the art that the structure shown in FIG. 11 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.

In an embodiment, there is also provided a computer device comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of the method embodiments described above.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are both information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to meet the related regulations.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile memory and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (RESISTIVE RANDOM ACCESS MEMORY, reRAM), magneto-resistive Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computation, an artificial intelligence (ARTIFICIAL INTELLIGENCE, AI) processor, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the present application.

The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims (12)

1. The constraint verification method is characterized by being applied to a pico-base station, wherein the pico-base station is in communication connection with a device network manager, and the method comprises the following steps:

Acquiring an operation instruction to be checked;

If the operation instruction to be checked meets the initial check condition, determining at least one target configuration constraint rule matched with the operation instruction to be checked from a preset configuration constraint check rule library corresponding to the leather base station;

Based on the target configuration constraint rule, performing constraint verification on the change configuration data carried by the operation instruction to be verified;

And synchronizing the change configuration data to the equipment network manager under the condition that the change configuration data passes constraint verification.

2. The method according to claim 1, wherein determining at least one target configuration constraint rule matched with the operation instruction to be checked from a preset configuration constraint check rule base corresponding to the pico base station includes:

Determining an instantiation path corresponding to the operation instruction to be checked based on the operation instruction to be checked;

And according to the instantiation path, determining at least one target configuration constraint rule matched with the operation instruction to be verified from the preset configuration constraint verification rule base.

3. The method of claim 1, wherein the change configuration data includes an operation command, an operation object, and a parameter to be configured corresponding to the operation object, and the performing constraint verification on the change configuration data carried by the operation command to be verified based on the target configuration constraint rule includes:

Based on the target configuration constraint rule, carrying out parameter integrity verification on the parameter to be configured to obtain a corresponding integrity verification result;

If the integrity check result is the missing necessary parameter, a first message is generated, and the first message is fed back to a target maintenance terminal for missing parameter error prompt, wherein the target maintenance terminal is one of a device network management maintenance terminal and a pico-base station maintenance terminal.

4. The method of claim 1, wherein the change configuration data comprises an operation command, an operation object and parameters to be configured corresponding to the operation object, wherein the pico base station is configured with a preset configuration database, and wherein the constraint checking of the change configuration data carried by the operation instruction to be checked based on the target configuration constraint rule comprises:

identifying the operation type of the operation command;

If the operation type is an add command or a delete command, searching an associated object with a dependency relationship with the operation object in the preset configuration database;

and generating a second message based on the retrieved association object, and feeding the second message back to a target maintenance terminal for carrying out association error prompt, wherein the target maintenance terminal is one of a device network management maintenance terminal and a pico-base station maintenance terminal.

5. The method of claim 1, wherein the change configuration data includes an operation command, an operation object, and a parameter to be configured corresponding to the operation object, wherein the pico base station is configured with a preset configuration database, and wherein synchronizing the change configuration data to the device network management if the change configuration data passes constraint verification includes:

writing the change configuration data into the preset configuration database under the condition that the change configuration data passes constraint verification;

Synchronizing the change configuration data to the equipment network manager based on an adaptation layer file issued by the pico base station along with the version;

The adaptation layer file refers to a metadata file for ensuring that the pico-base station and the equipment network management configuration semantics are consistent.

6. The method of claim 1, wherein the pico base station is deployed with a preset configuration database, the preset configuration database comprising a plurality of configuration objects, the method further comprising:

In the starting stage of the pico-base station, performing constraint verification on each configuration object in the preset configuration database based on the preset configuration constraint verification rule base;

If the abnormal configuration object with the constraint verification failure exists in the preset configuration database, generating a third message corresponding to the abnormal configuration object, and feeding the third message back to the pico-base maintenance terminal for alarm display.

7. The method according to claim 1, wherein the method further comprises:

The operation instruction to be checked is initially checked, wherein the initial check at least comprises semantic grammar validity check, operation command validity check, operation object validity check and parameter value validity check;

if the operation instruction to be checked passes the initial check, determining that the operation instruction to be checked meets an initial check condition.

8. A constraint verification device, said device comprising:

The acquisition module is used for acquiring an operation instruction to be checked;

the matching module is used for determining at least one target configuration constraint rule matched with the operation instruction to be checked from a preset configuration constraint check rule library corresponding to the leather base station if the operation instruction to be checked meets the initial check condition;

the verification module is used for carrying out constraint verification on the change configuration data carried by the operation instruction to be verified based on the target configuration constraint rule;

and the synchronization module is used for synchronizing the change configuration data to the equipment network manager under the condition that the change configuration data passes the constraint verification.

9. The constraint verification system is characterized by comprising an equipment network manager and at least one pico base station, wherein the pico base station is in communication connection with the equipment network manager;

The pico base station for performing the constraint checking method of claims 1 to 7.

10. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any one of claims 1 to 7 when the computer program is executed.

11. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any one of claims 1 to 7.

12. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any one of claims 1 to 7.