CN114024821A - Northbound interface management method and device - Google Patents
Northbound interface management method and device Download PDFInfo
- Publication number
- CN114024821A CN114024821A CN202111131653.XA CN202111131653A CN114024821A CN 114024821 A CN114024821 A CN 114024821A CN 202111131653 A CN202111131653 A CN 202111131653A CN 114024821 A CN114024821 A CN 114024821A
- Authority
- CN
- China
- Prior art keywords
- northbound
- model
- north
- data
- output
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 42
- 238000012545 processing Methods 0.000 claims abstract description 140
- 238000000034 method Methods 0.000 claims abstract description 36
- 238000013507 mapping Methods 0.000 claims abstract description 20
- 238000006243 chemical reaction Methods 0.000 claims abstract description 10
- 230000007246 mechanism Effects 0.000 claims abstract description 8
- 230000005477 standard model Effects 0.000 claims description 10
- 238000004891 communication Methods 0.000 claims description 9
- 230000008569 process Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 9
- 230000008859 change Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000004913 activation Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/20—Network management software packages
Abstract
The embodiment of the invention discloses a management method and a device of a northbound interface. The method comprises the following steps: obtaining a northbound interface driving model corresponding to the northbound interface; the northbound interface driver model comprises: a first north model for describing mapping conversion rules between the north specification model and the equipment business model, a second north model for describing north output file rules and a processing class for describing a north message processing mechanism; after the equipment data are obtained, the equipment data are converted according to a first north model, and north data are obtained; processing the northbound data according to a 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. The embodiment of the invention can reduce the customization difficulty of the northbound interface, and enables the deployment of the network management system to be faster and more efficient.
Description
The application is a divisional application of Chinese patent application (application date: 2018, 6 and 28 months; application number: 201810691802. X; invention and creation name: a management method and device of a northbound interface).
Technical Field
The present invention relates to, but not limited to, the field of wireless communication technologies, and in particular, to a method and an apparatus for managing a northbound interface.
Background
The carrier's northbound specification typically describes the requirements of the northbound model, the output format, and the output path, name, etc. For example, 32.762 specification of 3GPP (3rd Generation Partnership Project) describes the northbound model of E-UTRAN (Evolved Universal Mobile telecommunications System Terrestrial Radio Access Network), and 32.615 specification describes the definition of the output file format. However, the northbound specification description modes of each operator are not uniform, some words and excels are used in formats, and the detailed degree of the expression of the words is different.
In order to adapt to the northbound specifications of different operators, the northbound interface of the telecommunication network management system needs to be implemented differently for each specification, resulting in a large amount of customization and maintenance work. When new changes occur, it is often necessary to expend significant costs to accommodate the changes.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for managing a northbound interface, which can reduce the customization difficulty of the northbound interface, and enable deployment of a network management system to be faster and more efficient.
The embodiment of the invention provides a management method of a northbound interface, which comprises the following steps:
obtaining a northbound interface driving model corresponding to the northbound interface; the northbound interface driver model comprises: a first north model for describing mapping conversion rules between the north specification model and the equipment business model, a second north model for describing north output file rules and a processing class for describing a north message processing mechanism;
after the equipment data are obtained, the equipment data are converted according to a first north model, and north data are obtained;
processing the northbound data according to a 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.
An embodiment of the present invention provides a management device for a northbound interface, including:
the north interface processing module is used for acquiring a processing class for describing a north message processing mechanism from the north interface driving model; processing the northbound data according to the processing class to obtain a northbound output message containing the northbound data;
the north data processing module is used for acquiring a first north model for describing mapping conversion rules between a north standard model and a device business model and a second north model for describing north output file rules from a north interface driving model; and after the device data is acquired, converting the device data according to the first northbound model to acquire northbound data, and processing the northbound data according to the second northbound model to acquire a northbound output file.
An embodiment of the present invention provides a computer-readable storage medium, where a management program of a northbound interface is stored on the computer-readable storage medium, and when the management program of the northbound interface is executed by a processor, the steps of the method for managing the northbound interface are implemented.
According to the management method and device of the northbound interface provided by the embodiment of the invention, a first northbound model is established for the attribute mapping relation between the northbound standard model of each operator and the equipment provider model, a second northbound model is established for the northbound output file rule, a processing class is established for the northbound message processing mechanism, and after equipment data is obtained, the equipment data is converted according to the first northbound model to obtain the northbound data; processing the northbound data according to a second northbound model to obtain a northbound output file; or processing the northbound data by using a processing class to obtain a northbound output message containing the northbound data. By encapsulating the change in the model and the processing class, the northbound data processing framework is kept stable, thereby reducing the customization difficulty of the northbound interface and enabling the deployment of the network management system to be faster and more efficient.
Drawings
FIG. 1 is a flowchart of a method for managing a northbound interface according to an embodiment of the present invention;
FIG. 2 is a diagram of a management apparatus of a northbound interface according to an embodiment of the present invention;
FIG. 3 is a block diagram of a northbound interface processing framework in an example of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
The Open System Interconnect (OSI) management framework provides a mechanism to monitor and control network and System resources, which are represented as management objects (also referred to as managed objects). A management object refers to an abstract representation of a resource within a managed system, while a resource may generally refer to any physical or logical object that is managed. Typical physical resources are transport devices, routers, interface boards, modems, etc., and typical logical resources are communication protocols, applications, network services, etc.
In a TMN (telecommunications Management Network) Network Management system, Managed resources are accessed through an MOC (Managed Object Class). The MOC is an information model that defines the attributes, operations, behaviors, notifications, etc. of managed objects.
As shown in fig. 1, an embodiment of the present invention provides a method for managing a northbound interface, including:
step S110, obtaining a northbound interface driving model corresponding to the northbound interface; the northbound interface driver model comprises: a first north model for describing mapping conversion rules between the north specification model and the equipment business model, a second north model for describing north output file rules and a processing class for describing a north message processing mechanism;
step S120, after the equipment data are obtained, the equipment data are converted according to a first north model, and north data are obtained;
step S130, processing the northbound data according to a 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.
In this embodiment, the equipment quotient model and the northbound specification model are models based on a management object class MOC. The device vendor model may be a device vendor provided model in the prior art, and the northbound specification model may be an operator provided model in the prior art.
In this embodiment, data of the device may be queried through the internal interface, or data reported by the device may be received; wherein the device data includes: configuration information, performance parameters, alarm information, etc.;
in some embodiments, the converting the device data according to the first north model to obtain north data includes:
determining an equipment provider model and an attribute value of the equipment provider model according to the equipment data;
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. In some embodiments, the first northbound model is described by an XML (Extensible Markup Language) Language; the first northbound model may also be described in other languages, such as the Groovy language.
In some embodiments, the northbound output file rule may include: file format rules describing the format of the output file, and naming rules describing the output path and file name of the output file.
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.
In some embodiments, the processing the northbound data according to the second northbound model to obtain a northbound output file includes:
taking the northbound data as an input of a file format model;
obtaining the value of a grammar label according to the input and a grammar rule defined by a file format model;
and generating a north direction output file according to the grammar label and the value of the grammar label.
Wherein the grammar rule includes: xml (Extensible Markup Language) grammar rules, csv (Comma-Separated Values) grammar rules, txt grammar rules, and the like.
In some embodiments, the processing the northbound data according to the second northbound model to obtain a northbound output file further includes:
taking a north-oriented standard model and attribute values and/or user input corresponding to the north-oriented data as input of a file storage parameter model;
obtaining the value of the output object label according to the input and a naming rule defined by the file storage parameter model;
generating a file name and a storage path of a northbound output file according to the output object label and the value of the output object label;
and outputting the north output file which accords with the naming rule to a generated storage path.
In this embodiment, the processing classes are used to describe complex processing logic, and these complex processing logic are not suitable for being described by a DSL (Domain specific Language) Language or an XML (extensible markup Language) Language.
In some embodiments, processing the northbound data according to a processing class to obtain a northbound output message including the northbound data includes:
and acquiring a corresponding processing class according to the type of the message sent to the superior network manager, encoding the northbound data through the processing class, packaging the encoded northbound data in the message according to a communication protocol, and calling a protocol stack interface to send the message to the superior network manager.
The message sent to the upper level network manager includes, for example: an alarm message;
in some embodiments, before obtaining the northbound interface driver model, the method further comprises:
reading the northbound model packet to generate parameters of a opening interface; the northbound model package is a set of northbound interface driver models;
determining a northbound interface driving model corresponding to the northbound interface according to the input parameters received from the opening interface;
and opening a northbound interface and initiating data subscription to the equipment data source.
In some embodiments, the method further comprises:
receiving the message of the upper network management;
decoding the message of the upper network manager;
acquiring a corresponding processing class according to a decoding result, and processing and responding to the request carried in the message through the processing class;
in some embodiments, the method further comprises:
loading the updated northbound model package; the northbound model package is a set of northbound interface driver models;
obtaining a northbound model patch corresponding to the northbound interface from the updated northbound model package; the northbound model patch is generated according to updated operator northbound specifications.
The embodiment of the invention takes the north model package as a core to construct a north processing framework, and completes the communication, flow interaction and data processing with a superior NMS (Network Management System). The change is encapsulated in the northbound model packet, the northbound processing framework is kept stable, the change of the northbound model packet can take effect in real time, the opening and customization capacity of the northbound interface is greatly enhanced, the new requirements of users in the 5G (fifth generation mobile communication technology) era on operation and maintenance are met, and new characteristics can be deployed more quickly and efficiently.
As shown in fig. 2, an embodiment of the present invention provides a management apparatus for a northbound interface, including:
a northbound interface processing module 201, configured to obtain a processing class for describing a northbound message processing mechanism from the northbound interface driver model; processing the northbound data according to the processing class to obtain a northbound output message containing the northbound data;
the north data processing module 202 is configured to obtain, from the north interface driver model, a first north model for describing a mapping conversion rule between the north canonical model and the device business model and a second north model for describing a north output file rule; after the device data are obtained, the device data are converted according to the first northbound model to obtain northbound data, and the northbound data are processed according to the second northbound model to obtain a northbound output file;
in this embodiment, the northbound interface processing module is configured to implement a function required by the northbound specification of the operator. For example, the northbound specification requires to support an alarm synchronization function, a northbound interface driving model has a processing class for implementing the alarm synchronization function, and then the northbound interface processing module implements the function by calling the processing class in the model packet. Different operator specifications have different requirements on the implementation mode of the northbound interface, some of the requirements are implemented by Corba (Common Object Request Broker Architecture) technology, and some of the requirements are implemented by SOAP (Simple Object Access Protocol) technology.
The north data processing module is used for acquiring the first north model and the second north model from the north interface driving model, completing conversion from the equipment data to the north standard data, and generating a north data file or a north message.
In this embodiment, the equipment quotient model and the northbound specification model are models based on a management object class MOC. The device vendor model may be a device vendor provided model in the prior art, and the northbound specification model may be an operator provided model in the prior art.
In this embodiment, data of the device may be queried through the internal interface, or data reported by the device may be received; wherein the device data includes: configuration information, performance parameters, alarm information, etc.;
in some embodiments, the northbound data processing module 202 is configured to perform a conversion process on the device data according to the first northbound model to obtain northbound data in the following manner: determining an equipment provider model and an attribute value of the equipment provider model according to the equipment data; 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.
In some embodiments, the northbound output file rule may include: file format rules describing the format of the output file, and naming rules describing the output path and file name of the output file.
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.
In some embodiments, the northbound data processing module 202 is configured to process the northbound data according to the second northbound model in the following manner to obtain a northbound output file: taking the northbound data as an input of a file format model; obtaining the value of a grammar label according to the input and a grammar rule defined by a file format model; and generating a north direction output file according to the grammar label and the value of the grammar label.
In some embodiments, the northbound data processing module 202 is further configured to process the northbound data according to the second northbound model in the following manner to obtain a northbound output file: taking a north-oriented standard model and attribute values and/or user input corresponding to the north-oriented data as input of a file storage parameter model; obtaining the value of the output object label according to the input and a naming rule defined by the file storage parameter model; generating a file name and a storage path of a northbound output file according to the output object label and the value of the output object label; and outputting the north output file which accords with the naming rule to a generated storage path.
In some embodiments, the northbound interface processing module 201 is configured to process the northbound data according to the processing class in the following manner to obtain a northbound output message including the northbound data: and acquiring a corresponding processing class according to the type of the message sent to the superior network manager, encoding the northbound data through the processing class, packaging the encoded northbound data in the message according to a communication protocol, and calling a protocol stack interface to send the message to the superior network manager.
In some embodiments, the northbound interface processing module 201 is further configured to read the northbound model packet, and generate parameters for opening the interface; the northbound model package is a set of northbound interface driver models; determining a northbound interface driving model corresponding to the northbound interface according to the input parameters received from the opening interface; and opening a northbound interface and initiating data subscription to the equipment data source.
In some embodiments, the northbound interface processing module 201 is further configured to receive a message from a higher level network manager; decoding the message of the upper network manager; acquiring a corresponding processing class according to a decoding result, and processing and responding to the request carried in the message through the processing class;
in some embodiments, the northbound interface processing module 201 is further configured to load the updated northbound model package; the northbound model package is a set of northbound interface driver models; obtaining a northbound model patch corresponding to the northbound interface from the updated northbound model package; the northbound model patch is generated according to updated operator northbound specifications.
The embodiment of the invention constructs a north processing frame by taking the north model packet as a core to complete communication, flow interaction and data processing with a superior network management system. The change encapsulation is in the northbound model package, the northbound processing frame is stable, the change of the northbound model package can be effective in real time, the opening and customization capacity of the northbound interface is greatly enhanced, the new requirements of users on operation and maintenance in the 5G era are met, and new characteristics can be deployed more quickly and efficiently.
The embodiment of the invention provides a management device of a northbound interface, which comprises:
the management program of the northbound interface realizes the steps of the management method of the northbound interface when being executed by the processor.
The memory may be implemented, for example, by any type or combination of volatile and non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The processor may be a Central Processing Unit (CPU), a field programmable logic array (FPGA), a single chip Microcomputer (MCU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or other logic operation device with data processing capability and/or program execution capability.
An embodiment of the present invention provides a computer-readable storage medium, where a management program of a northbound interface is stored on the computer-readable storage medium, and when the management program of the northbound interface is executed by a processor, the steps of the method for managing the northbound interface are implemented.
The computer readable storage medium may be Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The northbound model package is the core of the northbound processing framework, and examples 1-3 below illustrate the modeling methods of the first and second northbound models. The north processing frame utilizes the north model packet to complete communication, flow interaction and data processing with a superior network management system. Examples 4 to 7 illustrate the management method of the northbound interface in terms of a northbound interface activation flow, a northbound interface uplink data processing flow, a northbound interface downlink instruction processing flow, a northbound interface northbound model package upgrading flow, and the like.
Example 1
The present example provides a modeling method for a mapping relationship between a northbound specification model and a device business model. The northbound specification model and the equipment vendor model both follow the TMN specification and are described based on the MOC model. The mapping relation between the northbound specification model and the equipment quotient model is embodied on the attribute mapping of the MOC. The mapping relationship between the attributes comprises: input, mapping function, and output. The mapping description of the attributes may also support multiple versions, as the device vendor model version managed by the NMS may be one or more sets.
As shown in the following xml file, the mapping relationship between the northbound specification model and the equipment manufacturer model is modeled by using xml language, and a first northbound model file is generated.
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 (10)
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:
determining an equipment provider model and an attribute value of the equipment provider model according to the equipment data;
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;
obtaining the value of a grammar label according to the input and a grammar rule defined by a file format model;
and generating a north direction output file according to the grammar label and the value of the grammar label.
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;
generating a file name and a storage path of a northbound output file according to the output object label and the value of the output object label;
and outputting the north output file which accords with the naming rule to a generated storage path.
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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111131653.XA CN114024821A (en) | 2018-06-28 | 2018-06-28 | Northbound interface management method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111131653.XA CN114024821A (en) | 2018-06-28 | 2018-06-28 | Northbound interface management method and device |
| CN201810691802.XA CN109150583A (en) | 2018-06-28 | 2018-06-28 | A kind of management method and device of northbound interface |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810691802.XA Division CN109150583A (en) | 2018-06-28 | 2018-06-28 | A kind of management method and device of northbound interface |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114024821A true CN114024821A (en) | 2022-02-08 |
Family
ID=64802613
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111131653.XA Pending CN114024821A (en) | 2018-06-28 | 2018-06-28 | Northbound interface management method and device |
| CN201810691802.XA Pending CN109150583A (en) | 2018-06-28 | 2018-06-28 | A kind of management method and device of northbound interface |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810691802.XA Pending CN109150583A (en) | 2018-06-28 | 2018-06-28 | A kind of management method and device of northbound interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN114024821A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114928663A (en) * | 2022-06-02 | 2022-08-19 | 蜂助手股份有限公司 | Method and device for recognizing callback message |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112051990A (en) * | 2019-06-06 | 2020-12-08 | 烽火通信科技股份有限公司 | Network management northbound interface model adaptation method and system |
| CN113347194B (en) * | 2021-06-17 | 2023-03-24 | 北京百度网讯科技有限公司 | Data transmission method, data transmission device, electronic apparatus, storage medium, and program product |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101262470A (en) * | 2007-06-20 | 2008-09-10 | 中兴通讯股份有限公司 | A north interface for peeling the interface and its interaction method with users |
| CN105187225A (en) * | 2015-06-08 | 2015-12-23 | 清华大学 | Method and system for multi-domain heterogeneous interconnected network management based on PCE (path computation element) |
| WO2016131295A1 (en) * | 2015-07-16 | 2016-08-25 | 中兴通讯股份有限公司 | Northbound data conversion method and device |
| CN108011736A (en) * | 2016-10-27 | 2018-05-08 | 中兴通讯股份有限公司 | A kind of method and apparatus for configuring north orientation model |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101478430A (en) * | 2009-02-04 | 2009-07-08 | 浪潮通信信息系统有限公司 | Method for centralized flexible message processing |
| CN106533729A (en) * | 2015-09-14 | 2017-03-22 | 大唐移动通信设备有限公司 | Northbound interface management method and system |
-
2018
- 2018-06-28 CN CN202111131653.XA patent/CN114024821A/en active Pending
- 2018-06-28 CN CN201810691802.XA patent/CN109150583A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101262470A (en) * | 2007-06-20 | 2008-09-10 | 中兴通讯股份有限公司 | A north interface for peeling the interface and its interaction method with users |
| CN105187225A (en) * | 2015-06-08 | 2015-12-23 | 清华大学 | Method and system for multi-domain heterogeneous interconnected network management based on PCE (path computation element) |
| WO2016131295A1 (en) * | 2015-07-16 | 2016-08-25 | 中兴通讯股份有限公司 | Northbound data conversion method and device |
| CN108011736A (en) * | 2016-10-27 | 2018-05-08 | 中兴通讯股份有限公司 | A kind of method and apparatus for configuring north orientation model |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114928663A (en) * | 2022-06-02 | 2022-08-19 | 蜂助手股份有限公司 | Method and device for recognizing callback message |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109150583A (en) | 2019-01-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| DK2914022T3 (en) | Device management method, middleware and machine-to-machine communication platform, device and system | |
| WO2017054531A1 (en) | Yang model-based compiling method, and corresponding interface, component, and system | |
| WO2018059137A1 (en) | Internet of things terminal access device and method, and computer storage medium | |
| EP1793529A1 (en) | A method and system for configuring network devices through an operations support system interface | |
| CN114024821A (en) | Northbound interface management method and device | |
| KR20060099392A (en) | Dynamic service generation for legacy components | |
| CN110768820B (en) | Data communication method based on SNMP (simple network management protocol) and related equipment | |
| CN112688952B (en) | Message processing method, device, radio remote unit and medium | |
| CN105049256A (en) | Method and system for realizing universal custom interface message | |
| CN100411355C (en) | Information service hierarchy inheritance relation realizing method in network management interface | |
| US10289462B1 (en) | Systems and methods for integration of websphere optimized local adapters with the spring framework | |
| CN113296987B (en) | Interface calling method and device for calling module, computer equipment and storage medium | |
| Li et al. | Efficient oneM2M protocol conversion platform based on NB-IoT access | |
| CN109600776B (en) | Data interaction method, device and equipment | |
| WO2010048815A1 (en) | Method and system for developing and installing network management features of services | |
| US11973660B1 (en) | Method and system for data model mapping for network management | |
| CN111355601A (en) | Information transmission method and device | |
| CN110134467B (en) | Parameter configuration processing method and device, storage medium and processor | |
| CN108737525A (en) | A kind of Web service system based on REST frameworks | |
| CN115065594A (en) | Data configuration method, device, equipment, readable storage medium and program product | |
| CN115118569B (en) | Request processing method, request processing device, network management equipment and readable storage medium | |
| WO2023170447A1 (en) | Generating distinguished names for non-object-oriented models | |
| Belaıd et al. | A framework for monitoring and reconfiguration of components using dynamic transformation | |
| CN117319164A (en) | Intent interaction method, device and system | |
| CN115913931A (en) | Interface adaptation method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220208 |