CN102684894B - Method and device for realizing northboundbound interface - Google Patents

Method and device for realizing northboundbound interface Download PDF

Info

Publication number
CN102684894B
CN102684894B CN201110054410.0A CN201110054410A CN102684894B CN 102684894 B CN102684894 B CN 102684894B CN 201110054410 A CN201110054410 A CN 201110054410A CN 102684894 B CN102684894 B CN 102684894B
Authority
CN
China
Prior art keywords
order
cli
parameter
command
pending
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.)
Active
Application number
CN201110054410.0A
Other languages
Chinese (zh)
Other versions
CN102684894A (en
Inventor
张青龙
柳大伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201110054410.0A priority Critical patent/CN102684894B/en
Priority to PCT/CN2011/073152 priority patent/WO2012119340A1/en
Publication of CN102684894A publication Critical patent/CN102684894A/en
Application granted granted Critical
Publication of CN102684894B publication Critical patent/CN102684894B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04Network management architectures or arrangements
    • H04L41/044Network management architectures or arrangements comprising hierarchical management structures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/0226Mapping or translating multiple network management protocols

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a method and device for realizing a northbound interface. The method comprises the following steps: storing the mapping relationship information of a trade language 1(TL1) command and a command line interface (CLI) configuration set; after a TL1 command to be executed is received, inquiring the mapping relationship information of a TL1 command and the CLI configuration set to obtain the CLI configuration set corresponding to the TL1 command to be executed; for the CLI command in the CLI configuration set, if a configuration parameter is contained, inquiring the command parameter of the TL1 command to be executed, which corresponds to the configuration parameter; and replacing the configuration parameter of the CLI command by the inquired parameter value corresponding to the command parameter to finish conversion to the CLI command from the TL1 command. In the implementation mode, the TL1 command can be dynamically loaded with different service logic handle class treatment, and therefore the deficiency that an EMS (element management system) northbound interface needs to be developed again is made up when the network element version is updated.

Description

A kind of method and device of realizing northbound interface
Technical field
The present invention relates to the field of network management of communication system, relate in particular to a kind of method and device of realizing northbound interface.
Background technology
Along with the high speed development of telecommunication industry, the scale of communication network constantly expands, and device category and networking mode also become increasingly complex and variation.At present, the equipment of each operator often equipment of You Duojia different vendor forms jointly, there is Element management system (the Element Management System of own equipment in each manufacturer, EMS), but unified interface information model and data target cannot be provided between these Element management systems, the centralized management of network has been brought to difficulty.
For the problems referred to above, in order to realize the unified management to the whole network, the hope of office side can be set up comprehensive network management system (Network Management System on the basis of the network management system of disperseing at present, NMS), this just requires each manufacturer in own distinctive Element management system, provide the unified interface towards integrated network management system, i.e. northbound interface.Northbound interface can shield the otherness between each Element management system and equipment, realizes the integrated management to different vendor, different network type, reduces the complexity of network management.
Common northbound interface agreement has CORBA (Common Object Request Broker Architecture), FTP (file transfer protocol (FTP)), XML (SOAP/Web Service), SNMP (Simple Network Management Protocol) and TL1 (transaction language 1) at present.Wherein:
The OO application program system standard of a kind of standard that CORBA Shi You OMG OMG works out.By Object Request Broker (ORB), objects services, communal facility, domain interface and application interface, formed.Its core is Object Request Broker ORB, and ORB provides a kind of mechanism, by this mechanism, and the request of sending that object can be transparent and reception response.The shortcoming of corba interface is too huge and complicated, and docking debug difficulties and autgmentability are poor, and when interface changes, docking both sides will recompilate, and development cost is high.
FTP interface refers to that webmaster is regularly by the Information generation file of needs, and comprehensive network management obtains these files by File Transfer Protocol and resolves according to the form of appointment.FTP interface mode is suitable for the situation that the downward layer of upper strata webmaster webmaster obtains big data quantity, is unsuitable for the situation that requirement of real-time is higher, is not also suitable for the situation that upper strata webmaster operates EMS.
XML (SOAP/Web Service) is a kind of light weight, simple, the agreement based on XML, and it is designed to exchange structurized information on WEB.The shortcoming of XML interface is that redundant data is large, and efficiency of transmission is lower, and the XML using in message must resolve at every turn, and analyzing efficiency is relatively low, and control of authority is cumbersome.
SNMP is by a set of NMP based on UDP of ietf definition, is simple and easy to use, is actual network management industrial standard.SNMP manages based on Manager/Agent model, adopts management information base (Management Information Base, MIB) and relevant command set to carry out information interaction, and SNMP Trap is the message active reporting mechanism in snmp protocol.The shortcoming of SNMP interface is that comprehensive network management NMS can not directly carry out by EMS the order issuing service operation of CLI (Command Line Interface, command line interface) mode.At present traditional command line interface CLI has become the interface that most of equipment vendors generally support, therefore adopting the mode of command line interface to be configured network element is the mainstream technology means that current network management system adopts.
TL1 is a kind of telecommunication administration agreement of the standard connecting based on TCP, and TL1 docking is simple, and debugging is convenient, favorable expandability, easy to understand and use.In order to support integrated network management system to carry out sending down service, TL1 northbound interface need to be provided in Element management system, TL1 northbound interface is on the one hand for receiving TL1 command request, on the other hand for completing TL1 order to adaptation and the transfer process of concrete CLI order, realization is mutual with concrete network element, operator adopts TL1 agreement to carry out sending down service becomes first-selection at field of telecommunications, and from actual service condition, TL1 has become the most widely used northbound interface agreement at present.
The feature of existing TL1 northbound interface exploitation is: for each TL1 order, developer's (application side) will pay close attention to the processing problem of TL1 agreement itself, comprise that the parsing, TL1 order of TL1 protocol format are to the mapping of concrete device command, the packing of message response form and returning etc.Therefore this development mode has been brought following problem:
(1) exploitation threshold is higher, developer's focus is too many, developer not only will pay close attention to service logic itself, also to pay close attention to the parsing of TL1 protocol information, the other problemses such as the authority of TL1 order, security control and daily record, therefore, this development mode is unfavorable for the separation of focus, the efficiency of exploitation is low, safeguards also more difficult.
(2) traditional TL1 northbound interface lacks the centralized control to TL1 message.Due to developer's otherness itself, the different style that its message is returned, the consistency of message structure is poor.
(3) extensibility is not enough, and when network element version is upgraded or newly increased a kind of network element of newtype, the northbound interface program of webmaster must synchronously be upgraded.
(4) automaticity of TL1 Message Processing is not high.Existing development mode is used different Business Processing classes to process different TL1 orders mostly, does not set up TL1 order to automatic mapping and the composition mechanism of concrete CLI order, and dynamic adaptable is poor.
Summary of the invention
The technical problem to be solved in the present invention is to provide a kind of method and device of realizing northbound interface, realizes TL1 request message is carried out to standardization.
For solving the problems of the technologies described above, a kind of method that realizes northbound interface of the present invention, comprising:
Set up knowledge base, the mapping relations information of store transaction language 1 (TL1) order and command line interface (CLI) config set;
After receiving pending TL1 order, the mapping relations information of inquiry TL1 order and CLI config set, obtains CLI config set corresponding to pending TL1 order;
For the CLI order in CLI config set, if contain configuration parameter, inquire about the command parameter of the pending TL1 order corresponding with configuration parameter, adopt the parameter value of the corresponding command parameter inquiring to replace the configuration parameter of CLI order, complete pending TL1 order to the conversion of CLI order.
Further, in knowledge base, also store the mapping relations information of CLI parameter reference and TL1 command parameter;
The command parameter of inquiring about the pending TL1 order corresponding with configuration parameter comprises: according to the parameter reference of configuration parameter, the mapping relations information of inquiry CLI parameter reference and TL1 command parameter, obtains the command parameter of the pending TL1 order that the parameter reference of configuration parameter is corresponding.
Further, adopt the configuration parameter of the parameter value replacement CLI order of the corresponding command parameter inquiring to comprise:
After receiving pending TL1 order, preserve the command parameter of pending TL1 order and the mapping relations information of parameter value; After the command parameter of pending TL1 order corresponding to the parameter reference that obtains configuration parameter, inquire about the command parameter of pending TL1 order and the mapping relations information of parameter value, obtain parameter value corresponding to command parameter, adopt resulting parameter value to replace the configuration parameter of CLI order.
Further, in knowledge base, also store parameter value mapping relations information;
After parameter value corresponding to the command parameter that obtains pending TL1 order, also in query parameter values mapping relations information, whether comprise command parameter, if comprised, adopt the mapping value corresponding to parameter value of this command parameter in parameter value mapping relations information to replace the configuration parameter of CLI order.
Further, at least corresponding CLI config set with managed object class (MOC) information and version information sign of TL1 order in the mapping relations information of TL1 order and CLI config set;
The mapping relations information of inquiry TL1 order and CLI config set, obtaining CLI config set corresponding to pending TL1 order comprises: in pending TL1 order, comprise net element information, after receiving pending TL1 order, according to net element information, read MOC information and the version information of network element, according to MOC information and the version information of network element, from the mapping relations information of TL1 order and CLI config set, inquiry obtains CLI config set corresponding to pending TL1 order.
Further, also comprise:
After completing the configuration parameter of the parameter value replacement CLI order that adopts the corresponding command parameter inquiring, the CLI order obtaining is joined in CLI command group to be issued;
If the CLI order in CLI config set, does not include configuration parameter, directly this CLI order is joined in CLI command group;
Completing pending TL1 order after the conversion of CLI order, CLI command group is issued to corresponding network element.
Further, also comprise:
Set up control of authority file, configure user, user allow the territory under the operation of execution and the network element of operation;
After receiving pending TL1 order, resolve control of authority file, to issuing user and the pending TL1 order of pending TL1 order, carry out legitimacy authentication.
Further, also comprise:
In knowledge base, also store the command format of TL1 order, to after issuing the user of pending TL1 order and pending TL1 command authorization and passing through, according to the command format of pending TL1 order, pending TL1 order is carried out to syntactic analysis.
Further, also comprise:
In knowledge base, also store the request frequency threshold value of TL1 order, after the syntactic analysis of pending TL1 order is passed through, request frequency to pending TL1 order is analyzed, whether the request frequency that judges pending TL1 order exceeds request frequency threshold value, if surpassed, refuse pending TL1 order.
Further, also comprise:
In knowledge base, also store the processing mode sign of TL1 order, when the request frequency of pending TL1 order does not exceed request frequency threshold value, according to the processing mode of the pending TL1 order of processing mode sign judgement of pending TL1 order, if processing mode, for adopting transparent transmission to process, is carried out the step of the mapping relations information of inquiry TL1 order and CLI config set; If processing mode is for adopting business logic processing class to process, the path of reading the business logic processing class of pending TL1 order from knowledge base, according to this path, carries out corresponding business logic processing class.
Further, a kind of device of realizing northbound interface, comprising: knowledge base and command mapping assembling entity, wherein:
Knowledge base, the mapping relations information for store transaction language 1 (TL1) order with command line interface (CLI) config set;
Command mapping assembling entity, for after receiving pending TL1 order, the mapping relations information of inquiry TL1 order and CLI config set, obtains CLI config set corresponding to pending TL1 order; For the CLI order in CLI config set, if contain configuration parameter, inquire about the command parameter of the pending TL1 order corresponding with configuration parameter, adopt the parameter value of the corresponding command parameter inquiring to replace the configuration parameter of CLI order, complete pending TL1 order to the conversion of CLI order.
Further, knowledge base, also for storing the mapping relations information of CLI parameter reference and TL1 command parameter;
When command mapping is assembled the command parameter of the pending TL1 order that object query is corresponding with configuration parameter, it is the parameter reference according to configuration parameter, the mapping relations information of inquiry CLI parameter reference and TL1 command parameter, obtains the command parameter of the pending TL1 order that the parameter reference of configuration parameter is corresponding.
Further, command mapping assembling entity, also for after receiving pending TL1 order, is preserved the command parameter of pending TL1 order and the mapping relations information of parameter value;
When command mapping assembling entity adopts the parameter value of the corresponding command parameter inquiring to replace the configuration parameter of CLI order, after the command parameter of pending TL1 order corresponding to the parameter reference that obtains configuration parameter, inquire about the command parameter of pending TL1 order and the mapping relations information of parameter value, obtain parameter value corresponding to command parameter, adopt resulting parameter value to replace the configuration parameter of CLI order.
Further, also comprise authentication entity, wherein:
Authentication entity, for setting up control of authority file, configure user, user allow the territory under the operation of execution and the network element of operation; After receiving pending TL1 order, resolve control of authority file, to issuing user and the pending TL1 order of pending TL1 order, carry out legitimacy authentication.
Further, also comprise syntactic analysis entity, wherein:
Knowledge base, also for storing the command format of TL1 order;
Authentication entity, to after issuing the user of pending TL1 order and pending TL1 command authorization and passing through, calls syntactic analysis entity;
Syntactic analysis entity, for according to the command format of pending TL1 order, carries out syntactic analysis to pending TL1 order.
Further, also comprise the adaptive entity of request, wherein:
Knowledge base, also for storing the request frequency threshold value of TL1 order;
Syntactic analysis entity after the syntactic analysis of pending TL1 order is passed through, the adaptive entity of call request;
Ask adaptive entity, for the request frequency to pending TL1 order, analyze, judge whether the request frequency of pending TL1 order exceeds request frequency threshold value, if surpassed, refuse pending TL1 order.
Further, also comprise service processing entity, wherein:
Knowledge base, also for storing the processing mode sign of TL1 order;
Command mapping assembling entity, also for when asking adaptive entity to judge that the request frequency of pending TL1 order does not exceed request frequency threshold value, according to the processing mode of the pending TL1 order of processing mode sign judgement of pending TL1 order, if processing mode, for adopting transparent transmission to process, is carried out the mapping relations information of inquiry TL1 order and CLI config set; If processing mode, for adopting business logic processing class to process, is called service processing entity;
Service processing entity, for read the path of the business logic processing class of pending TL1 order from knowledge base, according to this path, carries out corresponding business logic processing class.
In sum, present embodiment is for TL1 order, can be according to the difference of NE type and version, dynamically generation CLI order issues and is given to network element, for TL1 order, also can the different business logic processing class of dynamic load process, thereby made up when network element version is upgraded, EMS northbound interface also needs to re-start the deficiency of exploitation, the development and maintenance cost of northbound interface is reduced greatly, and, present embodiment adopts unified Message Processing and order issuing mechanism to TL1 order, and adopt unified safety, daily record and transaction management, improved development efficiency, for newly-increased TL1 order, without the code that remodifies EMS webmaster, only need to revise the configuration file of knowledge base, can complete the adjustment of EMS, can reach the object of customer in response demand rapidly.
Accompanying drawing explanation
Fig. 1 is the application scenarios figure of TL1 northbound interface;
Fig. 2 is the functional block diagram of the device of realizing northbound interface of present embodiment;
Fig. 3 is the process chart of the method that realizes northbound interface of present embodiment.
Embodiment
The implementation method of the northbound interface of present embodiment and device can be realized the function of TL1 northbound interface dynamic self-adapting, request for upper strata webmaster, in conjunction with local knowledge base and NE type, carry out Dynamic Inference decision-making, generate intelligently the CLI order mutual with network element, and unified Message Processing and return mechanisms is provided.Can inject neatly concrete business logic processing class, special TL1 request is processed simultaneously.The message processing procedure of TL1 northbound interface is transparent to business logic processing class, is convenient to concentrate one's energy to process service logic, has realized effective separation of focus.The TL1 northbound interface that present embodiment realizes has good dynamic self-adapting ability, can improve significantly the development efficiency of northbound interface, fast the changes in demand of customer in response.
Below in conjunction with accompanying drawing and concrete embodiment, the present invention is further described.
Fig. 1 is position and the application scenarios of TL1 northbound interface in EMS, the TL1 northbound interface of present embodiment is deployed in the server end of EMS, receive the TL1 north orientation request of the NMS on upper strata, and complete conversion and the adaptation that TL1 asks CLI order, realize the configuration to network element.
Fig. 2 is the device of realizing northbound interface of present embodiment, comprising: authentication entity, syntactic analysis entity, ask adaptive entity, command mapping assembling entity, service processing entity and order to issue entity, wherein:
Authentication entity is responsible for received all TL1 requests to carry out unified control of authority, refusal illegal request.
The grammer that syntactic analysis entity is responsible for message packet detects, Exception Filter message.
Ask adaptive entity to be responsible for the frequent degree analysis of request, prevent malicious attack behavior, and whether generate CLI order/command group according to TL1 knowledge base dynamic decision, or request is assigned to service processing entity processes.
Service processing entity is responsible for for there being the order of special processing demand to process.
Order issues entity and is responsible for that CLI order/command group is issued to concrete network element and completes corresponding transaction rollback processing.
For realizing the method for present embodiment, need to set up in advance control of authority file and knowledge base.
Set up control of authority file, the different user in Upper NM Station is carried out to Authority and Domain Based Management management.Control of authority file can configure a plurality of different users, and different user can have different operating rights.Control of authority file comprises operation and the affiliated territory of operating equipment that user, user can carry out.Control of authority file not only can configure the TL1 command entries that allows user to carry out, and also can configure the scope of the MOC example that allows user's operation.
The control of authority file of the XML of take is below illustrated as example.
In superincumbent control of authority file, two users of admin and test have been set up.
Alloperation=" true " represents that admin user can issue the TL1 order that all northbound interfaces are supported.
Alldomain=" true " represents that admin user can operate all MOC examples.
Test user can only carry out " IP-BND-ACLLNK-PORT " order, and this user can only issue TL1 order in the MOC example ranges of domain constraint simultaneously.The scope of MOC example can be an independent network element, can be also a group NEs.
Set up semi-structured or structural knowledge storehouse, TL1 northbound interface can carry out comprehensive reasoning decision-making by knowledge base according to the north orientation TL1 request of the NMS receiving, dynamically generates concrete CLI order and is issued to equipment.
In knowledge base, store following content:
(1) TL1 order is to the conversion relevant information of network element CLI order.
(2) mapping relations of network element version and concrete CLI order.
(3) TL1 order is to the mapping relations of concrete service logic class.
Particularly, the foundation of knowledge base has two kinds of modes, and a kind of is that the mode in usage data storehouse is set up structural knowledge storehouse, and another kind is to use the mode of configuration file to set up semi-structured knowledge base.
The TL1 order " IP-TL1-ACLLINK-PORT " of take is below example, illustrates in the mode of configuration file and sets up knowledge base:
Present embodiment is converted to TL1 order the method for CLI order as described in Figure 3, comprising:
301:EMS receives after the TL1 command request of NMS, resolves the command parameter of device type, IP address of equipment, TL1 command name and input and the Hash mapping table (nameValueHashTable) of parameter value that obtain network element under the upper current user's name of NMS, EMS from this request;
302: the authentication entity in northbound interface, according to user's name, command name, is resolved control of authority file user and TL1 order are carried out to authentication;
303: if authentication is passed through, perform step 304; Otherwise, execution step 313;
304: authentication entity calls the syntactic analysis that syntactic analysis entity carries out TL1 order, syntactic analysis entity, according to the command format of this TL1 order in knowledge base, carries out syntactic analysis to the TL1 order receiving;
305: syntactic analysis entity judges whether syntactic analysis is passed through, and by performing step 306, asks frequent degree analysis; Otherwise, execution step 313;
306: the adaptive entity of syntactic analysis entity call request, ask adaptive entity to be analyzed the request frequent degree of TL1 order, with the safety problem that prevents that unauthorized user malicious attack from bringing;
The TL1 request frequency threshold value of every order is stored in knowledge base, and the maxfreg=10 describing as above-mentioned configuration file represents the TL1 command request that surpasses 10 times per minute, and EMS refusal further operates.
307: ask adaptive entity to judge whether the request frequent degree analysis of TL1 order is passed through, by performing step 308; Otherwise, execution step 313;
308: ask adaptive entity according to the processing mode sign of this TL1 order configuring in knowledge base, the concrete processing mode of judgement TL1 order;
309: if adopt transparent transmission to process, perform step 310; Otherwise, execution step 312;
The processing mode sign that " useEMS " in knowledge base is TL1 order " IP-TL1-ACLLINK-PORT ", useEMS=" false " represents to adopt transparent transmission to process, useEMS=" true " represents the path of reading business logic processing class from businessClassName, adopts business logic processing class to process.
310: ask adaptive entity that TL1 order is entrusted to command mapping and assembling entity, command mapping and assembling entity are assembled into CLI order by TL1 order;
The detailed step of order assembling is as follows:
Steps A 1: read MOC and the version information of network element according to net element information (as IP address), search CLI config set corresponding to TL1 order according to MOC and version information in the mapping relations information of the TL1 order from knowledge base and CLI config set;
CLI config set is the value value collection that in above-mentioned configuration file, cliCommand is corresponding.At least corresponding CLI config set with MOC information and version information sign of TL1 order in the mapping relations information of TL1 order and CLI config set.
Steps A 2: for CLI config set corresponding to TL1 order, scan the value value (CLI order) of cliCommand from top to bottom, contain configuration parameter (param) in the CLI order scanning if current, perform step A3; Otherwise, the value value of the current cliCommand scanning is added in CLI command group to be issued;
Steps A 3: the parameter reference (being the value of the index in cliCommand) that parses the configuration parameter in steps A 2, the mapping relations of CLI parameter reference and TL1 command parameter are stored in the TL1-param node of knowledge base, the parameter value of the TL1 command parameter that parameter reference is corresponding can be shown directly to find by nameValueHashTable, the mapping relations information of preserving command parameter and parameter value in nameValueHashTable table, the parameter value of the TL1 command parameter obtaining is replaced to $ { the paramx} part of cliCommand, and the content after replacing is added in CLI command group to be issued,
Attention: also comprise parameter value mapping relations information (<value-map>) for some TL1 orders in knowledge base, in nameValueHashTable table, find after the value of parameter name, if can find this parameter name between <value-map> label, need to adopt the emsMapValue corresponding to value (mapping value of nmsValue) of this parameter to replace $ { the paramx} part of CLI command template.
After completing for the whole cliCommand scannings under a network element version and MOC, completed the structure of CLI command group.
311: order issues entity CLI command group is issued to corresponding network element, after issuing successfully, carries out the record of Operation Log.
312: service processing entity reads the path of the business logic processing class in businessClassName in knowledge base, carry out concrete business logic processing class and process;
313: build TL1 response message, return to upper layer NMS NMS.
In present embodiment, can also expand TL1 knowledge base, realize the management to knowledge base.
TL1 knowledge base is stored in the server end of network management system.The expansion of TL1 knowledge base can be used the graphic user interface of client to input, this makes the webmaster Dynamic expansion knowledge base that can be in operation, therefore, present embodiment has stronger dynamic adaptable to the dynamic requests of NMS, comprises TL1 command name, command syntax format, TL1 parameter name, TL1 parameter type and TL1 parameter area etc.The mapping relations of the mapping relations of CLI order, CLI parameter and TL1 parameter and NMS parameter and EMS parameter.
The organizational form of the knowledge base based on database is one to one with the organizational form of knowledge base based on configuration file, and the organizational form that knowledge base based on database is concrete is as follows, can be divided into following four tables.
Table one: TL1 order base attribute table
Table two: TL1 parameter list
The mapping relations table of table three: MOC and version and CLI order
Table four: NMS and EMS parameter value mapping relations table
With IP-BND-ACLLNK-PORT order, the knowledge base based on database mode is that example explanation is converted to TL1 order the method for CLI order, comprising below:
Step B1: resolve and obtain command name IP-BND-ACLLNK-PORT, according to DIP (device IP), obtain MOC type and concrete network element version, the value of each TL1 parameter is respectively: IFNAME=gei_2/1, ACLID=200, DIRECTION=0, stores the mapping relations of parameter name and value in Hash table (nameValueHashTable) into;
Step B2: according to MOC type and network element version, in scan table three, order the CLI command template interface $ { param1} that IP-BND-ACLLNK-PORT is corresponding, according to interface $ { index 1 look-up table two that param1} is corresponding, obtain the corresponding IFNAME of index 1 (port title), the value gei_2/1 that searches IFNAME from nameValueHashTable replaces $, and { param 1}, obtains CLI order interface gei_2/1 and adds CLI command group;
Similarly, the value 200 that finds ACLID replaces $ { param2}, find the value 0 of DIRECTION, by reading table 4 (NMS and EMS parameter value mapping relations table), be converted in, { param3}, generates second command ip access-group 200in and joins CLI command group to replace $;
Step B3: call instruction issues entity the order of CLI command group is issued to concrete network element.
By step B1 and B2, obtain concrete command group as follows:
interface?gei_2/1;
ip?access-group?200in。
The function of this CLI order is by ACL binding physical interface gei_2/1 Inbound.
From above step, can find out, present embodiment can generate CLI command group based on Analysis of Knowledge Bases Reasoning decision-making automatically according to the TL1 request of upper strata webmaster EMS, also request minute can be tasked to concrete service logic class processes simultaneously, its unified message parse has been realized the effective separated of focus with security management mechanism, can greatly improve the development efficiency of northbound interface, also there is good autgmentability and versatility simultaneously.
Obviously, those skilled in the art should be understood that, above-mentioned each entity of the present invention, each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on the network that a plurality of calculation elements form, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in storage device and be carried out by calculation element, or they are made into respectively to each integrated circuit entity, or their a plurality of entities or step are made into single integrated circuit entity to be realized.Like this, the present invention is not restricted to any specific hardware and software combination.
The foregoing is only embodiments of the invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any modification of making, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.

Claims (16)

1. a method that realizes northbound interface, comprising:
Set up knowledge base, the mapping relations information of the 1TL1 order of store transaction language and command line interface CLI config set;
After receiving pending TL1 order, inquire about the mapping relations information of described TL1 order and CLI config set, obtain CLI config set corresponding to described pending TL1 order;
For the CLI order in described CLI config set, if contain configuration parameter, inquire about the command parameter of the described pending TL1 order corresponding with described configuration parameter, the parameter value of the corresponding command parameter that employing inquires is replaced the configuration parameter of described CLI order, completes described pending TL1 order to the conversion of CLI order;
At least corresponding CLI config set with managed object class MOC information and version information sign of TL1 order in the mapping relations information of described TL1 order and CLI config set;
The mapping relations information of the described TL1 order of described inquiry and CLI config set, obtaining CLI config set corresponding to described pending TL1 order comprises: in described pending TL1 order, comprise net element information, after receiving described pending TL1 order, according to described net element information, read MOC information and the version information of network element, according to MOC information and the version information of described network element, from the mapping relations information of described TL1 order and CLI config set, inquiry obtains CLI config set corresponding to described pending TL1 order.
2. the method for claim 1, is characterized in that:
In described knowledge base, also store the mapping relations information of CLI parameter reference and TL1 command parameter;
The command parameter of the described pending TL1 order that described inquiry is corresponding with described configuration parameter comprises: according to the parameter reference of described configuration parameter, inquire about the mapping relations information of described CLI parameter reference and TL1 command parameter, obtain the command parameter of the described pending TL1 order that the parameter reference of described configuration parameter is corresponding.
3. method as claimed in claim 2, is characterized in that, the configuration parameter that the parameter value of the corresponding command parameter that described employing inquires is replaced described CLI order comprises:
After receiving described pending TL1 order, preserve the command parameter of described pending TL1 order and the mapping relations information of parameter value; After the command parameter of described pending TL1 order corresponding to the parameter reference that obtains described configuration parameter, inquire about the command parameter of described pending TL1 order and the mapping relations information of parameter value, obtain parameter value corresponding to command parameter, adopt resulting parameter value to replace the configuration parameter of described CLI order.
4. method as claimed in claim 3, is characterized in that:
In described knowledge base, also store parameter value mapping relations information;
After parameter value corresponding to the command parameter that obtains described pending TL1 order, also inquire about in described parameter value mapping relations information and whether comprise described command parameter, if comprised, adopt the mapping value corresponding to parameter value of this command parameter in described parameter value mapping relations information to replace the configuration parameter of described CLI order.
5. method as claimed in claim 3, is characterized in that, also comprises:
At the parameter value that completes the corresponding command parameter that described employing inquires, replace after the configuration parameter of described CLI order, the CLI order obtaining is joined in CLI command group to be issued;
If the CLI order in described CLI config set, does not include configuration parameter, directly this CLI order is joined in described CLI command group;
Completing described pending TL1 order after the conversion of CLI order, described CLI command group is issued to corresponding network element.
6. method as claimed in claim 3, is characterized in that, also comprises:
Set up control of authority file, configure user, user allow the territory under the operation of execution and the network element of operation;
After receiving described pending TL1 order, resolve described control of authority file, to issuing user and the described pending TL1 order of described pending TL1 order, carry out legitimacy authentication.
7. method as claimed in claim 6, is characterized in that, also comprises:
In described knowledge base, also store the command format of TL1 order, to after issuing the user of described pending TL1 order and described pending TL1 command authorization and passing through, according to the command format of described pending TL1 order, described pending TL1 order is carried out to syntactic analysis.
8. method as claimed in claim 7, is characterized in that, also comprises:
In described knowledge base, also store the request frequency threshold value of TL1 order, after the syntactic analysis of described pending TL1 order is passed through, request frequency to described pending TL1 order is analyzed, whether the request frequency that judges described pending TL1 order exceeds request frequency threshold value, if surpassed, refuse described pending TL1 order.
9. method as claimed in claim 8, is characterized in that, also comprises:
In described knowledge base, also store the processing mode sign of TL1 order, when the request frequency of described pending TL1 order does not exceed described request frequency threshold value, according to the processing mode of the described pending TL1 order of processing mode sign judgement of described pending TL1 order, if processing mode, for adopting transparent transmission to process, is carried out the step of the mapping relations information of the described TL1 order of described inquiry and CLI config set; If processing mode is for adopting business logic processing class to process, the path of reading the business logic processing class of described pending TL1 order from described knowledge base, according to this path, carries out corresponding business logic processing class.
10. a device of realizing northbound interface, comprising: knowledge base and command mapping assembling entity, wherein:
Described knowledge base, for the mapping relations information of the 1TL1 order of store transaction language and command line interface CLI config set;
Described command mapping assembling entity, for after receiving pending TL1 order, inquires about the mapping relations information of described TL1 order and CLI config set, obtains CLI config set corresponding to described pending TL1 order; For the CLI order in described CLI config set, if contain configuration parameter, inquire about the command parameter of the described pending TL1 order corresponding with described configuration parameter, the parameter value of the corresponding command parameter that employing inquires is replaced the configuration parameter of described CLI order, completes described pending TL1 order to the conversion of CLI order;
At least corresponding CLI config set with managed object class MOC information and version information sign of TL1 order in the mapping relations information of described TL1 order and CLI config set;
The mapping relations information of the described TL1 order of described inquiry and CLI config set, obtaining CLI config set corresponding to described pending TL1 order refers to: in described pending TL1 order, comprise net element information, after receiving described pending TL1 order, according to described net element information, read MOC information and the version information of network element, according to MOC information and the version information of described network element, from the mapping relations information of described TL1 order and CLI config set, inquiry obtains CLI config set corresponding to described pending TL1 order.
11. devices as claimed in claim 10, is characterized in that:
Described knowledge base, also for storing the mapping relations information of CLI parameter reference and TL1 command parameter;
When described command mapping is assembled the command parameter of the described pending TL1 order that object query is corresponding with described configuration parameter, it is the parameter reference according to described configuration parameter, inquire about the mapping relations information of described CLI parameter reference and TL1 command parameter, obtain the command parameter of the described pending TL1 order that the parameter reference of described configuration parameter is corresponding.
12. devices as claimed in claim 11, is characterized in that:
Described command mapping assembling entity, also for after receiving described pending TL1 order, is preserved the command parameter of described pending TL1 order and the mapping relations information of parameter value;
When described command mapping assembling entity adopts the parameter value of the corresponding command parameter inquiring to replace the configuration parameter of described CLI order, after the command parameter of described pending TL1 order corresponding to the parameter reference that obtains described configuration parameter, inquire about the command parameter of described pending TL1 order and the mapping relations information of parameter value, obtain parameter value corresponding to command parameter, adopt resulting parameter value to replace the configuration parameter of described CLI order.
13. devices as claimed in claim 12, is characterized in that, also comprise authentication entity, wherein:
Described authentication entity, for setting up control of authority file, configure user, user allow the territory under the operation of execution and the network element of operation; After receiving described pending TL1 order, resolve described control of authority file, to issuing user and the described pending TL1 order of described pending TL1 order, carry out legitimacy authentication.
14. devices as claimed in claim 13, is characterized in that, also comprise syntactic analysis entity, wherein:
Described knowledge base, also for storing the command format of TL1 order;
Described authentication entity, to after issuing the user of described pending TL1 order and described pending TL1 command authorization and passing through, calls described syntactic analysis entity;
Described syntactic analysis entity, for according to the command format of described pending TL1 order, carries out syntactic analysis to described pending TL1 order.
15. devices as claimed in claim 14, is characterized in that, also comprise the adaptive entity of request, wherein:
Described knowledge base, also for storing the request frequency threshold value of TL1 order;
Described syntactic analysis entity, after the syntactic analysis of described pending TL1 order is passed through, calls the adaptive entity of described request;
The adaptive entity of described request, analyzes for the request frequency to described pending TL1 order, judges whether the request frequency of described pending TL1 order exceeds request frequency threshold value, if surpassed, refuses described pending TL1 order.
16. devices as claimed in claim 15, is characterized in that, also comprise service processing entity, wherein:
Described knowledge base, also for storing the processing mode sign of TL1 order;
Described command mapping assembling entity, while also not exceeding described request frequency threshold value for the request frequency in the described pending TL1 order of the adaptive entity judgement of described request, according to the processing mode of the described pending TL1 order of processing mode sign judgement of described pending TL1 order, if processing mode, for adopting transparent transmission to process, is carried out the mapping relations information of the described TL1 order of described inquiry and CLI config set; If processing mode, for adopting business logic processing class to process, is called described service processing entity;
Described service processing entity, for read the path of the business logic processing class of described pending TL1 order from described knowledge base, according to this path, carries out corresponding business logic processing class.
CN201110054410.0A 2011-03-07 2011-03-07 Method and device for realizing northboundbound interface Active CN102684894B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201110054410.0A CN102684894B (en) 2011-03-07 2011-03-07 Method and device for realizing northboundbound interface
PCT/CN2011/073152 WO2012119340A1 (en) 2011-03-07 2011-04-22 Method and apparatus for implementing north interface

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201110054410.0A CN102684894B (en) 2011-03-07 2011-03-07 Method and device for realizing northboundbound interface

Publications (2)

Publication Number Publication Date
CN102684894A CN102684894A (en) 2012-09-19
CN102684894B true CN102684894B (en) 2014-12-10

Family

ID=46797430

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201110054410.0A Active CN102684894B (en) 2011-03-07 2011-03-07 Method and device for realizing northboundbound interface

Country Status (2)

Country Link
CN (1) CN102684894B (en)
WO (1) WO2012119340A1 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104503768B (en) * 2015-01-04 2018-05-04 华为技术有限公司 A kind of application programming interface call method and equipment
CN106656599A (en) * 2016-12-22 2017-05-10 浙江鹏信信息科技股份有限公司 Method and system for sending network data configuration instruction
CN109274518B (en) * 2018-07-30 2021-11-23 咪咕音乐有限公司 Equipment management method and device and computer readable storage medium
CN111723036B (en) * 2019-03-22 2023-04-04 华为技术有限公司 Data processing method, related device and computer storage medium
CN110472064A (en) * 2019-07-17 2019-11-19 陕西千山航空电子有限责任公司 A kind of health management system arranged design constructing method based on unmanned plane flight data

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5991814A (en) * 1997-07-10 1999-11-23 Alcatel Method and apparatus for controlling command line transfer to a network element
US6263366B1 (en) * 1996-12-31 2001-07-17 Mci Communications Corporation System and method therefor of translating a message having a given format for usage in an operations system
CN1829221A (en) * 2005-03-02 2006-09-06 华为技术有限公司 Traditional affair language interface transfer device and method
CN101009591A (en) * 2005-12-01 2007-08-01 阿尔卡特公司 Method and system for configuring network devices through an operations support system interface
CN101079755A (en) * 2007-07-03 2007-11-28 中兴通讯股份有限公司 Configuration method of network element management system
CN101621401A (en) * 2008-06-30 2010-01-06 华为技术有限公司 Network management configuration method based on northbound interface and device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101079737B (en) * 2007-06-08 2012-05-23 中兴通讯股份有限公司 An automatic structuring and parsing method and system of command line interface command

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6263366B1 (en) * 1996-12-31 2001-07-17 Mci Communications Corporation System and method therefor of translating a message having a given format for usage in an operations system
US5991814A (en) * 1997-07-10 1999-11-23 Alcatel Method and apparatus for controlling command line transfer to a network element
CN1829221A (en) * 2005-03-02 2006-09-06 华为技术有限公司 Traditional affair language interface transfer device and method
CN101009591A (en) * 2005-12-01 2007-08-01 阿尔卡特公司 Method and system for configuring network devices through an operations support system interface
CN101079755A (en) * 2007-07-03 2007-11-28 中兴通讯股份有限公司 Configuration method of network element management system
CN101621401A (en) * 2008-06-30 2010-01-06 华为技术有限公司 Network management configuration method based on northbound interface and device

Also Published As

Publication number Publication date
CN102684894A (en) 2012-09-19
WO2012119340A1 (en) 2012-09-13

Similar Documents

Publication Publication Date Title
US10892952B2 (en) Supporting compilation and extensibility on unified graph-based intent models
US11689419B2 (en) Supporting concurrency for graph-based high level configuration models
Schoenwaelder Overview of the 2002 IAB network management workshop
US20200313980A1 (en) Supporting near real time service level agreements
WO2001084329A1 (en) Network management method and system
CN102684894B (en) Method and device for realizing northboundbound interface
US20130326050A1 (en) Method of Organic Cloud Discovery and Transformation of Network Assets
US20230308348A1 (en) Server to support client data models from heterogeneous data sources
Abeck Network Management know it all
JPWO2006051599A1 (en) Resource management program, resource management method, and resource management apparatus
Hemid Facilitation of The OpenDaylight Architecture
Bieszczad et al. Management of heterogeneous networks with intelligent agents
Saheb et al. Auto-discovery and monitoring of network resources: Snmp-based network mapping and fault management
van der Meer et al. Ubiquitous Smart Space Management
CN114301775B (en) Method and device for managing stock service and computer readable storage medium
Pavlou OSI Systems Management, Internet SNMP and ODP/OMG CORBA as Technologies for Telecommunications Network Management
Jovanovic et al. Managing Network Elements in the ComputerNetwork
Lyu Literature review on standards for data structuring in physical layer of optical network.
Li et al. Design of General SDN Controller System Framework for Multi-domain Heterogeneous Networks
O’Connor State of Art Survey: Intra-domain and Inter-domain Management of Smart Space Environments
Cridlig et al. XBGP‐MAN: an XML management architecture for BGP
Höfig et al. Document-based network and system management: utilizing autonomic capabilities for enterprise management integration
KR100547224B1 (en) a method and a device for the purpose of integrated network management based on components
Schoenwaelder RFC3535: Overview of the 2002 IAB Network Management Workshop
Lin et al. Research on information models and modelling methods of the new generation of OSS for data management

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant