After the model (the first northbound model) is available, the mapping process between the northbound specification model and the equipment manufacturer model according to the model may include the following steps:

step 1: analyzing the first northbound Model file into a memory, and sequentially obtaining nrm (Network Resource Model ) moc (equipment manufacturer Model) and attributes, wherein nrmmoc is also a northbound specification Model and is a Model of an operator;

step 2: obtaining values of the emMoc and the attributes from an equipment data source;

and step 3: taking the value obtained in the step (2) as an input, and calling a mapping function (func function) of the first northbound model for conversion to obtain an attribute value of nrm moc;

and 4, step 4: and outputting the attribute and the attribute value of the nrm moc.

Example 2

The present example provides a modeling approach for northbound canonical output data formats. The northbound output data exists in the form of a data file, and the data file format may include: xml, csv, txt, etc. Each format has its own syntax specification (schema) definition. Modeling the output data format of the northbound specification, namely establishing a corresponding relation between the schema element and the value variable.

As shown in the following xml file, the output data format of the north direction specification is modeled by adopting an xml language, and a file format model file is generated.

In the xml file, firstly, a root element of the xml schema is described, secondly, a cycle body element of the xml is described, and then, a value of each tag is described.

With the above model (file format model), generating an output data file of the northbound specification according to the model may include the following steps:

step 1: analyzing the file format model file into a memory;

step 2: taking the attribute and the value of the nrm moc as input, and obtaining the value of each schema tag according to the corresponding relation between the schema tag and the attribute of the file format model;

and step 3: and (3) writing the values obtained in the step (2) according to the schema definition of the file format model to generate a data output file (northbound output file).

Example 3

The present example provides a modeling of other aspects of a northbound output file. For example, a file storage parameter model describing a northbound output file output path and a file name naming rule is established, the idea of modeling is similar to the data output format in example 2, and a relationship between each output data syntax element (schema element) and a specific value is established.

As shown in the following xml file, a file storage parameter model describing the north output file output path and the file name naming rule is established by adopting an xml language, and a file storage parameter model file is generated.

#directory,eg:/ftproot/GD/WX/ZTE/GZ_OMC2/PM/2015061101/

ftpDir:

${'/root/'+＝province+＝'/WX/ZTE/'+＝omcName+＝'/CM/'+＝naf:dateHandle(dirDate,'yyyyMMddHH

')}

#eg:PM-ENB-EUTRANCELLTDD-01-V1.1.0-20151227000000-15-001.csv.zip

fileName:

${elementType+＝'-'+＝nrmMoc+＝'-'+＝hostNo+＝'-'+＝nrmVersion+＝'-'+＝naf:dateHandle(fileNameDate,'yyyyMMddHHmmss')+＝suffix}

In the xml file, firstly, a root element of the xml schema is described, secondly, a cycle body element of the xml is described, and then, a value of each tag is described. The output path refers to a path of an FTP (File Transfer Protocol) server, and values of variables included in the output path and a File name can be input by a user, so that the method can support user customization.

With the above model (file storage parameter model), generating an output path and a file name of the northbound output file according to the model may include the following steps:

step 1: analyzing the file storage parameter model file into a memory;

step 2: taking the attribute and the value of the nrm moc as input, and obtaining the value of each output object label according to the corresponding relation between the output object label and the attribute of the file storage parameter model;

and step 3: and generating an output path and a file name according to the value of the output object label.

And 4, step 4: and transmitting the output path and the file name to a downstream file generation processing part, and outputting the north output file which accords with the naming rule to a generated storage path.

Example 4

The present example provides a flow of opening a northbound interface through a northbound interface processing framework. As shown in fig. 3, the northbound interface processing framework includes: a protocol stack and a northbound model driving device (namely, a northbound interface management device, which is referred to as a device for short); the northbound model driving apparatus includes: the system comprises a north interface processing module and a north data processing module.

The northbound interface opening process may include the following steps:

step 1: inputting a northbound model packet into the device;

step 2: reading the northbound model packet through a centralized opening tool of the northbound tool and generating a northbound interface opening interface parameter to be opened by a user;

and step 3: receiving parameters input by a user on an opening interface;

and 4, step 4: sending a northbound interface opening request to a northbound interface processing module through an opening tool;

and 5: and after receiving the opening request, the northbound interface processing module returns a confirmation response to the opening tool and initiates data subscription to the northbound data processing module.

Example 5

This example provides a flow of processing data through a northbound processing framework, which is the same as example 4.

After the northbound interface is opened, the northbound data processing flow may include the following steps:

step 1: the north orientation data processing module is used for processing a first north orientation model file in the north orientation model package; the first north orientation model describes an attribute mapping relation between a north orientation standard model and an equipment quotient model;

step 2: the north orientation data processing module acquires internal data from an equipment data source, and completes the conversion from the internal data to the north orientation standard data according to the first north orientation model file to obtain north orientation data;

and step 3: if the northbound data is reported in a message mode, executing the step 4, and if the northbound data is reported in a file mode, executing the step 5.

And 4, step 4: the north data processing module sends north data to the north interface processing module, the north interface processing module obtains a corresponding processing class from a north model packet, the north data is coded according to a protocol coding and decoding algorithm through the processing class, the coded north data is encapsulated in a message according to a communication protocol and a protocol stack interface is called to be sent to a superior network manager, and the superior network manager receives the message and then decodes and processes the message, and the process is finished;

the processing class may be a program implemented by Java code, and is used to process a processing flow beyond the DSL (Domain specific Language) Language capability range. Such as the codec processing of the northbound alarm Socket protocol, this part of the processing is very complex and is not suitable for being described by DSL. Therefore, JAVA code is used for realizing a specific coding and decoding process.

And 5: the northbound data processing module acquires a file format model file and a file storage parameter model file from the northbound model package, wherein the file format model is used for describing a northbound output file format, and the file storage parameter model is used for describing a northbound output file output path and a file name naming rule. And (3) inputting the northbound data obtained in the step (2) into a File format model File and a File storage parameter model File, generating a northbound output data File, storing the northbound output data File on a specified path (such as an SFTP (Secure File Transfer Protocol) server), and informing a superior network manager of obtaining the northbound output data File, or informing the superior network manager of obtaining the northbound output data File at regular time.

Example 6

This example provides a flow for processing a higher-level network management instruction through a northbound processing framework, which is the same as example 4.

After the northbound interface is opened, the downlink instruction processing flow may include the following steps:

step 1: the higher-level network manager packages the downlink instruction according to the protocol and then sends the downlink instruction;

step 2: the northbound interface processing module receives a message sent by a higher-level network manager and decodes the message;

and step 3: the northbound interface processing module acquires a corresponding processing class from the northbound model packet according to the decoding result to process and respond to the request carried in the message;

and 4, step 4: the northbound interface processing module encodes the response according to the protocol requirement, calls a protocol stack interface and sends the response to the superior network manager, and the superior network manager decodes and processes the response after receiving the response.

Example 7

The present example provides an upgrade processing flow of a northbound model package, and the northbound interface processing framework is the same as that of example 4.

After the northbound interface is opened, the upgrading process flow of the northbound model package may include the following steps:

step 1: the operator issues a new northbound specification, and the model of the northbound specification changes due to the addition of new characteristics;

step 2: according to the change of the northbound standard model, making a northbound model patch, verifying and then releasing the northbound model patch to the field;

and step 3: implementing a northbound model patch on site through a model management tool in the northbound tool set;

and 4, step 4: the model management tool sends a patch activation message to the northbound interface processing module;

and 5: the north interface processing module informs the north data processing module to update the content of the north model packet;

step 6: and the northbound data processing module loads a new northbound model file and generates data according to the changed northbound model.

The time required by the steps 2 and 3 is very short, and even the steps can be directly implemented on site through a tool, so that the aim of rapid deployment and effectiveness is achieved.

It should be noted that the present invention can be embodied in other specific forms, and various changes and modifications can be made by those skilled in the art without departing from the spirit and scope of the invention.

Claims

1. A management method of a northbound interface comprises the following steps:

obtaining a northbound model package; the northbound model package is a set of northbound interface driving models;

obtaining a northbound interface driving model corresponding to a northbound interface to be managed from the northbound model packet;

converting the acquired equipment data into a north output object according to a preset north processing frame and the acquired north interface driving model; wherein the northbound output complies with an operator northbound specification;

and reporting the northbound output to a superior network management system.

2. A method of managing a northbound interface as claimed in claim 1, wherein the method further comprises:

loading the updated northbound interface driving model under the condition that the northbound specification of the operator is updated;

the method for converting the acquired equipment data into the northbound output according to the preset northbound processing frame and the acquired northbound interface driving model comprises the following steps:

and converting the acquired equipment data into a north output object according to the preset north processing framework and the updated acquired north interface driving model.

3. A method of managing a northbound interface as claimed in claim 1, wherein the northbound interface driving model comprises: a first northbound model, a second northbound model, and a processing class;

the northbound output includes: a north export file, or a north export message;

the first north orientation model is used for describing mapping conversion rules of the equipment quotient model and the north orientation standard model;

the second north model is used for describing the rule of the north output file;

the processing class is used for describing a northbound output message processing mechanism;

the converting the acquired device data into a northbound output, comprising:

converting the equipment data according to the first north model to obtain the north data;

processing the northbound data according to the second northbound model to obtain a northbound output file; or processing the northbound data according to the processing class to obtain a northbound output message containing the northbound data.

4. A management method for a northbound interface as set forth in claim 3, wherein the converting the device data according to the first northbound model to obtain the northbound data includes:

and taking the attribute value of the equipment quotient model as the input of the first northbound model, and calling an attribute mapping function of the first northbound model to convert the input to obtain the attribute value of the northbound standard model as northbound data.

5. A method of managing a northbound interface as claimed in claim 3 or claim 4, wherein the second northbound model includes: the file storage parameter model is used for describing the north output file output path and the file name naming rule;

processing the northbound data according to the second northbound model to obtain a northbound output file, including:

taking the northbound data as an input of a file format model;

6. The method for managing a northbound interface as claimed in claim 5, wherein the processing the northbound data according to the second northbound model to obtain a northbound output file further comprises:

using the northbound data and/or user input as input to the file storage parametric model;

obtaining the value of the output object label according to the input and the naming rule defined by the file storage parameter model;

7. A method as claimed in claim 3 or 4, wherein processing the northbound data according to a processing class to obtain a northbound output message including the northbound data comprises:

according to the processing class, the northbound data is encoded through the processing class, and the encoded northbound data is encapsulated in a northbound output message according to a communication protocol; the processing class corresponds to the type acquisition of a message sent to the superior network management system;

the reporting of the northbound output to a superior network management system includes:

and calling a protocol stack interface to send the northbound output message to the superior network management system.

8. A method as claimed in claim 7, wherein before said processing said northbound data according to a processing class to obtain a northbound output message including said northbound data, said method further comprises:

receiving and decoding the message sent by the superior network management system;

and acquiring a processing class corresponding to the message sent by the superior network management system according to the decoding result, and processing and responding to the request carried in the message sent by the superior network management system through the processing class.

9. A management apparatus of a northbound interface, comprising:

the north interface processing module is used for acquiring a north model packet; the northbound model package is a set of northbound interface driving models; obtaining a northbound interface driving model corresponding to a northbound interface to be managed from the northbound model packet;

the north data processing module is used for converting the acquired equipment data into a north output object according to a preset north processing frame and the acquired north interface driving model; wherein the northbound output complies with an operator northbound specification; and reporting the northbound output to a superior network management system.

10. A computer-readable storage medium having stored thereon a management program for a northbound interface, which when executed by a processor implements a method of managing the northbound interface as claimed in any of claims 1 to 8.