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

Method and device for realizing northboundbound interface Download PDF

Info

Publication number
CN102684894A
CN102684894A CN2011100544100A CN201110054410A CN102684894A CN 102684894 A CN102684894 A CN 102684894A CN 2011100544100 A CN2011100544100 A CN 2011100544100A CN 201110054410 A CN201110054410 A CN 201110054410A CN 102684894 A CN102684894 A CN 102684894A
Authority
CN
China
Prior art keywords
order
parameter
carry out
cli
command
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.)
Granted
Application number
CN2011100544100A
Other languages
Chinese (zh)
Other versions
CN102684894B (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

Images

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

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 enlarges, and device category and networking mode also become increasingly complex and variation.At present; The equipment of each operator is made up of the equipment of how tame different vendor often jointly; All there is Element management system (the Element Management System of own equipment in each manufacturer; EMS), but unified interface information model and data target can't be provided between these Element management systems, the centralized management of network has been brought difficulty.
To the problems referred to above; In order to realize unified management to the whole network; The hope of office side can on the basis of the network management system of disperseing at present, set up comprehensive NMS (Network Management System, NMS), this just requires each manufacturer in own distinctive Element management system; Unified interface towards integrated network management system is provided, i.e. northbound interface.Northbound interface can shield the otherness between each Element management system and the 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 (FTP), XML (SOAP/Web Service), SNMP (Simple Network Management Protocol) and TL1 (transaction language 1) at present.Wherein:
CORBA is the OO application program system standard by a kind of standard of OMG OMG formulation.Form by Object Request Broker (ORB), objects services, communal facility, domain interface and application interface.Its core is the ORB of Object Request Broker, and ORB provides a kind of mechanism, through this mechanism, and request of sending that object can be transparent and reception response.The shortcoming of corba interface is too huge and complicated, and butt joint debug difficulties and autgmentability are poor, and when interface changed, the butt joint both sides will recompilate, and development cost is high.
The FTP interface is meant webmaster regularly with the information spanned file of needs, and comprehensive network management obtains these files through File Transfer Protocol and resolves according to the form of appointment.The FTP interface mode is suitable for the situation that the downward layer of upper strata webmaster webmaster obtains big data quantity, is inappropriate for the situation that real-time is had relatively high expectations, and also is not suitable for the situation that the upper strata webmaster is operated EMS.
XML (SOAP/Web Service) be a kind of light weight, simple, based on the agreement of XML, it is designed to the structurized information of exchange on WEB.The shortcoming of XML interface is that redundant data is big, and efficiency of transmission is lower, and the XML that uses in the message must do parsing at every turn, and analyzing efficiency is relatively low, and control of authority is cumbersome.
SNMP is the NMP that is overlapped based on UDP by one of ietf definition, is simple and easy to usefulness, is actual network management industrial standard.SNMP manages based on the Manager/Agent model, and (Management Information Base MIB) carries out information interaction with relevant command set, and SNMP Trap is that the message in the snmp protocol initiatively reports mechanism to adopt management information base.The shortcoming of SNMP interface is that comprehensive network management NMS can not directly carry out the order issuing service operation of CLI (Command Line Interface, command line interface) mode through EMS.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 that network element is configured is the mainstream technology means that present network management system adopts.
TL1 is a kind of telecommunication administration agreement of the standard that connects based on TCP, and the TL1 butt joint 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 be provided in Element management system, and TL1 northbound interface is used to receive the TL1 command request on the one hand, is used to accomplish the adaptive and transfer process that TL1 orders concrete CLI order on the other hand; Realization is mutual with concrete network element; Operator adopts the TL1 agreement to carry out sending down service becomes first-selection at field of telecommunications, and from the operating position of reality, TL1 has become the most widely used northbound interface agreement at present.
Existing TL1 northbound interface characteristics of development is: to each TL1 order; Developer's (application side) will pay close attention to the handling problem of TL1 agreement itself; Comprise the parsing of TL1 protocol format, the mapping that TL1 orders concrete device command, the packing of message response form and returning etc.Therefore this development mode has been brought following problem:
(1) the exploitation threshold is higher, and developer's focus is too many, and the 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 authority, security control and daily record of TL1 order, therefore, this development mode is unfavorable for the separation of focus; The efficient of exploitation is low, safeguards also relatively difficulty.
(2) traditional T L1 northbound interface lacks the centralized control to TL1 message.Since developer's otherness itself, the different style that its message is returned, and the consistency of message structure is relatively poor.
(3) extensibility is not enough, and when the network element version upgrading perhaps increased a kind of network element of newtype newly, the northbound interface program of webmaster must be upgraded synchronously.
(4) automaticity of TL1 Message Processing is not high.Existing development mode uses the different service process class to handle different TL1 orders mostly, does not set up automatic mapping and composition mechanism that TL1 orders concrete CLI order, and dynamic adaptable is relatively poor.
Summary of the invention
The technical problem that the present invention will solve provides a kind of method and device of realizing northbound interface, realizes the TL1 request message is carried out standardization.
For solving the problems of the technologies described above, a kind of method that realizes northbound interface of the present invention comprises:
Set up knowledge base, the mapping relations information of store transaction language 1 (TL1) order and command line interface (CLI) config set;
Receive wait to carry out TL1 order after, the mapping relations information of inquiry TL1 order and CLI config set obtains waiting to carry out the corresponding CLI config set of TL1 order;
Order for the CLI in the CLI config set; If contain configuration parameter; Then the command parameter of TL1 order is carried out in wait corresponding with configuration parameter of inquiry, adopts the configuration parameter of the parameter value replacement CLI order of the corresponding command parameter that inquires, and accomplishes the conversion that TL1 to be carried out orders the CLI order.
Further, in knowledge base, also store the mapping relations information of CLI parameter reference and TL1 command parameter;
The command parameter that the TL1 order is carried out in wait corresponding with configuration parameter of inquiry comprises: according to the parameter reference of configuration parameter; The mapping relations information of inquiry CLI parameter reference and TL1 command parameter, the command parameter of TL1 order is carried out in corresponding the waiting of parameter reference that obtains configuration parameter.
Further, adopt the configuration parameter of the parameter value replacement CLI order of the corresponding command parameter that inquires to comprise:
Receive wait to carry out TL1 order after, preserve and wait to carry out the command parameter of TL1 order and the mapping relations information of parameter value; After the command parameter of TL1 order is carried out in corresponding the waiting of the parameter reference that obtains configuration parameter; Inquiry waits to carry out the command parameter of TL1 order and the mapping relations information of parameter value; Obtain command parameter corresponding parameters value, adopt the configuration parameter of resulting parameter value replacement CLI order.
Further, in knowledge base, also store parameter value mapping relations information;
After obtaining waiting to carry out the command parameter corresponding parameters value of TL1 order; Also whether comprise command parameter in the query parameter values mapping relations information; If comprise, then adopt the corresponding mapping value of parameter value of this command parameter in the parameter value mapping relations information to replace the configuration parameter of CLI order.
Further, the corresponding at least CLI config set that identifies with managed object class (MOC) information and version information 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 waiting carrying out the corresponding CLI config set of TL1 order comprises: wait to carry out in the TL1 order and comprise net element information, receive wait to carry out the TL1 order after, according to net element information; Read the MOC information and the version information of network element; According to the MOC information and the version information of network element, from the mapping relations information of TL1 order and CLI config set, inquiry obtaining waiting to carry out the corresponding CLI config set of TL1 order.
Further, also comprise:
Behind the configuration parameter of accomplishing the parameter value replacement CLI order of adopting the corresponding command parameter that inquires, the CLI order that obtains is joined in the CLI command group to be issued;
If the order of the CLI in the CLI config set does not include configuration parameter, then directly this CLI order is joined in the CLI command group;
Order the conversion of CLI order at completion TL1 to be carried out after, the CLI command group is issued to corresponding net element.
Further, also comprise:
Set up the control of authority file, the territory under the operation that configure user, user allow to carry out and the network element of operation;
Receive wait to carry out TL1 order after, resolve the control of authority file, to issuing the user that waits to carry out the TL1 order and waiting to carry out the TL1 order and carry out the legitimacy authentication.
Further, also comprise:
In knowledge base, also store the command format of TL1 order,,, treat and carry out TL1 order carrying out syntactic analysis according to the command format of waiting to carry out the TL1 order to after issuing the user that waits to carry out the TL1 order and waiting to carry out the TL1 command authorization and pass through.
Further, also comprise:
In knowledge base, also store the request frequency threshold value of TL1 order; After treating the syntactic analysis of carrying out the TL1 order and passing through; Treating the request frequency of carrying out the TL1 order analyzes; Judge and wait whether the request frequency of carrying out the TL1 order exceeds request frequency threshold value, if surpass, then refusal waits to carry out the TL1 order.
Further, also comprise:
In knowledge base, also storing TL1 process of commands mode identifies; When the request frequency of waiting to carry out the TL1 order does not exceed request frequency threshold value; Identify and judge and wait to carry out TL1 process of commands mode according to waiting to carry out TL1 process of commands mode; If processing mode is handled for the employing transparent transmission, then carry out the step of the mapping relations information of inquiry TL1 order and CLI config set; If processing mode is handled for adopting the business logic processing class, then from knowledge base, read the path of the business logic processing class of waiting to carry out the TL1 order, according to this path, carry out corresponding service logical process class.
Further, a kind of device of realizing northbound interface comprises: knowledge base and command mapping assembling entity, wherein:
Knowledge base is used for the mapping relations information of store transaction language 1 (TL1) order and command line interface (CLI) config set;
Command mapping assembling entity, be used for receive wait to carry out the TL1 order after, the mapping relations information of inquiry TL1 order and CLI config set obtains waiting to carry out the corresponding CLI config set of TL1 order; Order for the CLI in the CLI config set; If contain configuration parameter; Then the command parameter of TL1 order is carried out in wait corresponding with configuration parameter of inquiry, adopts the configuration parameter of the parameter value replacement CLI order of the corresponding command parameter that inquires, and accomplishes the conversion that TL1 to be carried out orders the CLI order.
Further, knowledge base also is used to store the mapping relations information of CLI parameter reference and TL1 command parameter;
When the command parameter of TL1 order is carried out in wait corresponding with configuration parameter of command mapping assembling entity inquiry; It is parameter reference according to configuration parameter; The mapping relations information of inquiry CLI parameter reference and TL1 command parameter, the command parameter of TL1 order is carried out in corresponding the waiting of parameter reference that obtains configuration parameter.
Further, command mapping assembling entity also be used for receive wait to carry out the TL1 order after, preserve and wait to carry out the command parameter of TL1 order and the mapping relations information of parameter value;
When command mapping assembling entity adopts the parameter value of the corresponding command parameter that inquires to replace the configuration parameter of CLI order; Be after the command parameter of TL1 order is carried out in corresponding the waiting of the parameter reference that obtains configuration parameter; Inquiry waits to carry out the command parameter of TL1 order and the mapping relations information of parameter value; Obtain command parameter corresponding parameters value, adopt the configuration parameter of resulting parameter value replacement CLI order.
Further, also comprise authentication entity, wherein:
Authentication entity is used to set up the control of authority file, the territory under the operation that configure user, user allow to carry out and the network element of operation; Receive wait to carry out TL1 order after, resolve the control of authority file, to issuing the user that waits to carry out the TL1 order and waiting to carry out the TL1 order and carry out the legitimacy authentication.
Further, also comprise the syntactic analysis entity, wherein:
Knowledge base also is used to store the command format of TL1 order;
Authentication entity calls the syntactic analysis entity to after issuing the user that waits to carry out the TL1 order and waiting to carry out the TL1 command authorization and pass through;
The syntactic analysis entity is used for according to the command format of waiting to carry out the TL1 order, treats and carries out TL1 order carrying out syntactic analysis.
Further, also comprise the adaptive entity of request, wherein:
Knowledge base also is used to store the request frequency threshold value that TL1 orders;
The syntactic analysis entity after treating the syntactic analysis of carrying out the TL1 order and passing through, the adaptive entity of call request;
Ask adaptive entity, be used to treat the request frequency of carrying out the TL1 order and analyze, judge and wait whether the request frequency of carrying out the TL1 order exceeds request frequency threshold value, if surpass, then refusal waits to carry out the TL1 order.
Further, also comprise service processing entity, wherein:
Knowledge base also is used to store TL1 process of commands mode and identifies;
Command mapping assembling entity; Also be used for when the adaptive entity of request judges that the request frequency of waiting to carry out the TL1 order does not exceed request frequency threshold value; Identify and judge and wait to carry out TL1 process of commands mode according to waiting to carry out TL1 process of commands mode; If processing mode is handled for the employing transparent transmission, then carry out the mapping relations information of inquiry TL1 order and CLI config set; If processing mode is handled for adopting the business logic processing class, then call service processing entity;
Service processing entity is used for reading from knowledge base the path of the business logic processing class of waiting to carry out the TL1 order, according to this path, carries out corresponding service logical process class.
In sum, this execution mode is ordered for TL1, can be according to NE type and version different; Dynamically generation CLI order issues and is given to network element, also can dynamic load different service logical process class handle for the TL1 order, thereby has remedied when network element version is upgraded; The deficiency that the EMS northbound interface also need be developed again; Make the development and maintenance cost of northbound interface reduce greatly, and this execution mode is to TL1 order employing unified Message Processing and order issuing mechanism; And adopt unified safety, daily record and transaction management, improved development efficiency; For newly-increased TL1 order, need not to remodify the code of EMS webmaster, only need to revise the configuration file of knowledge base, can accomplish the adjustment of EMS, can reach the purpose of customer in response demand apace.
Description of drawings
Fig. 1 is the application scenarios figure of TL1 northbound interface;
Fig. 2 is the functional block diagram of device of the realization northbound interface of this execution mode;
Fig. 3 is the process chart of method of the realization northbound interface of this execution mode.
Embodiment
The implementation method of the northbound interface of this execution mode and device can dynamic self-adapting ground the function of realization TL1 northbound interface; Request to the upper strata webmaster; Carry out dynamic reasoning decision-making in conjunction with local knowledge base and NE type; Generate the CLI order mutual intelligently, and unified Message Processing and return mechanisms is provided with network element.Simultaneously can inject concrete business logic processing class neatly, special TL1 request is handled.The message processing procedure of TL1 northbound interface is transparent to the business logic processing class, is convenient to the logic of managing business of concentrating one's energy, and has realized effective separation of focus.The TL1 northbound interface that this execution mode is realized has good dynamic self-adapting ability, can improve the development efficiency of northbound interface significantly, fast the changes in demand of customer in response.
Below in conjunction with accompanying drawing and practical implementation instance 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 this execution mode is deployed in the server end of EMS; Receive the TL1 north orientation request of the NMS on upper strata, and accomplish TL1 and ask the conversion of CLI order and adaptive, realize configuration network element.
Fig. 2 is the device of the realization northbound interface of this execution mode, 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 the unified control of authority of all TL1 requests carrying out that is received, refusal illegal request.
The grammer that the syntactic analysis entity is responsible for message packet detects, and filters unexpected message.
The frequent degree analysis of asking adaptive entity to be responsible for asking prevents the malicious attack behavior, and whether generates CLI order/command group according to TL1 knowledge base dynamic decision, perhaps request is assigned to service processing entity and handles.
Service processing entity is responsible for handling for the order that the special processing demand is arranged.
Order issues entity and is responsible for CLI order/command group is issued to concrete network element and accomplishes correspondent transaction rollback processing.
For the method that realizes this execution mode need be set up control of authority file and knowledge base in advance.
Set up the control of authority file, the different user in the Upper NM Station is carried out the Authority and Domain Based Management management.The control of authority file can dispose a plurality of different users, and different user can have the different operation authority.The control of authority file comprises operation and the affiliated territory of operating equipment that user, user can carry out.The control of authority file not only can dispose the TL1 command entries that allows the user to carry out, and also can dispose the scope of the MOC instance that allows user's operation.
Control of authority file with following XML is that example specifies.
Figure BDA0000049117350000091
In the superincumbent control of authority file, two users of admin and test have been set up.
Alloperation=" true " expression admin user can issue the TL1 order that all northbound interfaces are supported.
Alldomain=" true " expression admin user can operate all MOC instances.
Test user then can only carry out " IP-BND-ACLLNK-PORT " order, and this user can only issue the TL1 order in the MOC example ranges of domain constraint simultaneously.The scope of MOC instance can be an independent network element, also can be a group NEs.
Set up semi-structured or the structural knowledge storehouse, TL1 northbound interface can carry out comprehensive reasoning decision-making through knowledge base according to the north orientation TL1 request of the NMS that receives, dynamically generates concrete CLI order and is issued to equipment.
Store following content in the knowledge base:
(1) TL1 orders the conversion relevant information of network element CLI order.
(2) mapping relations of network element version and concrete CLI order.
(3) TL1 orders the mapping relations of concrete service logic class.
Particularly, knowledge base establish dual mode, a kind of mode of database that is to use is set up the structural knowledge storehouse, another kind is to use the mode of configuration file to set up semi-structured knowledge base.
Be example with TL1 order " IP-TL1-ACLLINK-PORT " below, explain with the mode of configuration file and set up knowledge base:
Figure BDA0000049117350000101
Figure BDA0000049117350000111
Is the method for CLI order like said execution mode of Fig. 3 with the TL1 command conversion, comprising:
After 301:EMS received the TL1 command request of NMS, parsing obtained NMS and goes up the command parameter of device type, IP address of equipment, TL1 command name and the input of network element under current user's name, the EMS and the Hash mapping table (nameValueHashTable) of parameter value from this request;
302: the authentication entity in the northbound interface is resolved the control of authority file user and TL1 order is carried out authentication according to user's name, command name;
303: if authentication is passed through, then execution in step 304; Otherwise, execution in step 313;
304: authentication entity calls the syntactic analysis that the syntactic analysis entity carries out the TL1 order, and the syntactic analysis entity is according to the command format of this TL1 order in the knowledge base, to TL1 order the carrying out syntactic analysis that receives;
305: the syntactic analysis entity judges whether syntactic analysis is passed through, and asks the frequent degree analysis through execution in step 306 then; Otherwise, execution in step 313;
306: the adaptive entity of syntactic analysis entity invokes request, ask adaptive entity that the request frequent degree of TL1 order is analyzed, 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 the knowledge base, and the maxfreg=10 that describes like above-mentioned configuration file representes that per minute surpasses 10 times TL1 command request, and the EMS refusal is further operated.
307: ask adaptive entity to judge whether the request frequent degree analysis of TL1 order is passed through, through execution in step 308 then; Otherwise, execution in step 313;
308: ask adaptive entity to identify, judge the concrete processing mode of TL1 order according to this TL1 process of commands mode that disposes in the knowledge base;
309: if adopt transparent transmission to handle, then execution in step 310; Otherwise, execution in step 312;
" useEMS " in the knowledge base is the processing mode sign of TL1 order " IP-TL1-ACLLINK-PORT "; UseEMS=" false " expression adopts transparent transmission to handle; The business logic processing class is read in useEMS=" true " expression from businessClassName path adopts the business logic processing class to handle.
310: ask adaptive entity that command mapping and assembling entity are entrusted in the TL1 order, command mapping is assembled into the CLI order with the assembling entity with the TL1 order;
The detailed step of order assembling is following:
Steps A 1: read the MOC and the version information of network element according to net element information (like the IP address), search TL1 in the mapping relations information according to MOC and the TL1 order of version information from knowledge base and CLI config set and order corresponding CLI config set;
The CLI config set is the value value collection that cliCommand is corresponding in the above-mentioned configuration file.The corresponding at least CLI config set that identifies with MOC information and version information of TL1 order in the mapping relations information of TL1 order and CLI config set.
Steps A 2: to the corresponding CLI config set of TL1 order, scan the value value (CLI order) of cliCommand from top to bottom, if the current CLI that scans contains configuration parameter (param) in ordering, execution in step A3 then; Otherwise, the value value of the current cliCommand that scans is added in the CLI command group to be issued;
Steps A 3: the parameter reference (being the value of the index among the cliCommand) that parses the configuration parameter in the 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 directly find through the nameValueHashTable table; The mapping relations information of preserving command parameter and parameter value in the nameValueHashTable table; With the parameter value replacement cliCommand De ${paramx} part of the TL1 command parameter that obtains, and the content after will replacing adds in the CLI command group to be issued;
Attention: in knowledge base, also comprise parameter value mapping relations information (< value-map >) for some TL1 orders; After in the nameValueHashTable table, finding the value of parameter title; If between < value-map>label, can find this parameter title, then need adopt the part of the corresponding emsMapValue replacement CLI command template of the value (mapping value of nmsValue) of this parameter.
After accomplishing, promptly accomplished the structure of CLI command group to the whole cliCommand scannings under a network element version and the MOC.
311: order issues entity the CLI command group is issued to corresponding net element, issue successfully after, carry out the record of Operation Log.
312: service processing entity reads the path of the business logic processing class among the businessClassName in the knowledge base, carries out concrete business logic processing class and handles;
313: make up the TL1 response message, return to upper layer NMS NMS.
Can also expand the TL1 knowledge base in this execution mode, realize knowledge-base management.
The TL1 knowledge base is stored in the server end of network management system.The expansion of TL1 knowledge base can use the graphic user interface of client to import; This makes the webmaster storehouse that dynamically expands knowledge that can be in operation; Therefore; This execution mode has stronger dynamic adaptable to the dynamic requests of NMS, comprises TL1 command name, command syntax format, TL1 parameter title, TL1 parameter type and TL1 parameter area etc.CLI order, CLI parameter and the mapping relations of TL1 parameter and the mapping relations of NMS parameter and EMS parameter.
Is one to one based on the organizational form of the knowledge base of database with organizational form based on the knowledge base of configuration file, and the organizational form concrete based on the knowledge base of database is following, can be divided into following four tables.
Table one: TL1 order base attribute table
Figure BDA0000049117350000131
Figure BDA0000049117350000141
Table two: TL1 parameter list
Figure BDA0000049117350000142
The mapping relations table of table three: MOC and version and CLI order
Figure BDA0000049117350000143
Table four: NMS and EMS parameter value mapping relations table
Figure BDA0000049117350000152
Below with IP-BND-ACLLNK-PORT order, be that the example explanation is the method for CLI order with the TL1 command conversion based on the knowledge base of database mode, comprising:
Step B1: resolve and obtain command name IP-BND-ACLLNK-PORT; Obtain MOC type and concrete network element version according to DIP (Device IP); The value of each TL1 parameter is respectively: IFNAME=gei_2/1; ACLID=200, DIRECTION=0 stores the mapping relations of parameter title and value in the Hash table (nameValueHashTable) into;
Step B2: according to MOC type and network element version; The corresponding CLI command template interface ${param1} of order IP-BND-ACLLNK-PORT in the scan table three; Index 1 look-up table two corresponding according to interface ${param1}; Obtain index 1 corresponding IFNAME (port title), from nameValueHashTable, search the value gei_2/1 replacement 1} of IFNAME, obtain CLI order interface gei_2/1 and add the CLI command group;
Similarly; Find the value 200 Ti Huandiao ${param2} of ACLID, find the value 0 of DIRECTION, convert in into through reading table 4 (NMS and EMS parameter value mapping relations table); Ti Huandiao ${param3} generates second command ip access-group 200in and joins the CLI command group;
Step B3: call instruction issues entity the order of CLI command group is issued to concrete network element.
It is following to obtain concrete command group through step B1 and B2:
interface?gei_2/1;
ip?access-group?200in。
The function of this CLI order is that ACL is bound physical interface gei_2/1 Inbound.
Can find out from above step; This execution mode can generate the CLI command group based on knowledge base reasoning decision-making automatically according to the TL1 request of upper strata webmaster EMS; Also can request be divided simultaneously and task concrete service logic class processing; Its unified message parse has realized that with security management mechanism the effective of focus separates, and can improve the development efficiency of northbound interface greatly, also has autgmentability and versatility preferably simultaneously.
Obviously, it is apparent to those skilled in the art that above-mentioned each entity of the present invention, each step can realize with the general calculation device; They can concentrate on the single calculation element; Perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element; Thereby; Can they be stored in the storage device and carry out, perhaps they are made into each integrated circuit entity respectively, perhaps their a plurality of entities or step is made into the single integrated circuit entity and realize by calculation element.Like this, the present invention is not restricted to any specific hardware and software combination.
The above is merely embodiments of the invention, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.All within spirit of the present invention and principle, any modification of being made, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (17)

1. method that realizes northbound interface comprises:
Set up knowledge base, the mapping relations information of store transaction language 1 (TL1) order and command line interface (CLI) config set;
Receive wait to carry out TL1 order after, the mapping relations information of inquiring about said TL1 order and CLI config set obtains the said corresponding CLI config set of TL1 order of waiting to carry out;
Order for the CLI in the said CLI config set; If contain configuration parameter; Then inquire about the said command parameter of waiting carry out TL1 order corresponding with said configuration parameter; The parameter value of the corresponding command parameter that employing inquires is replaced the configuration parameter of said CLI order, accomplishes the conversion that TL1 said to be carried out orders the CLI order.
2. the method for claim 1 is characterized in that:
In said knowledge base, also store the mapping relations information of CLI parameter reference and TL1 command parameter;
Said inquiry said the wait command parameter of carrying out TL1 order corresponding with said configuration parameter comprises: according to the parameter reference of said configuration parameter; Inquire about the mapping relations information of said CLI parameter reference and TL1 command parameter, obtain the corresponding said command parameter of waiting to carry out the TL1 order of parameter reference of said configuration parameter.
3. method as claimed in claim 2 is characterized in that, the configuration parameter that the parameter value of the corresponding command parameter that said employing inquires is replaced said CLI order comprises:
Receive said wait to carry out TL1 order after, preserves said wait to carry out the command parameter that TL1 orders and the mapping relations information of parameter value; After corresponding said of the parameter reference that obtains said configuration parameter waits to carry out the command parameter of TL1 order; Inquire about said wait the to carry out command parameter of TL1 order and the mapping relations information of parameter value; Obtain command parameter corresponding parameters value, adopt resulting parameter value to replace the configuration parameter of said CLI order.
4. method as claimed in claim 3 is characterized in that:
In said knowledge base, also store parameter value mapping relations information;
After obtaining the said command parameter corresponding parameters value of waiting to carry out the TL1 order; Also inquire about in the said parameter value mapping relations information and whether comprise said command parameter; If comprise, then adopt the corresponding mapping value of parameter value of this command parameter in the said parameter value mapping relations information to replace the configuration parameter of said CLI order.
5. method as claimed in claim 3 is characterized in that:
The corresponding at least CLI config set that identifies with managed object class (MOC) information and version information of TL1 order in the mapping relations information of said TL1 order and CLI config set;
The mapping relations information of said TL1 order of said inquiry and CLI config set; Obtain saidly waiting to carry out the corresponding CLI config set of TL1 order and comprising: said wait to carry out in the TL1 order comprise net element information; Receive said wait to carry out TL1 order after; According to said net element information, read the MOC information and the version information of network element, according to the MOC information and the version information of said network element; From the mapping relations information of said TL1 order and CLI config set, inquiry obtaining the said corresponding CLI config set of TL1 order of waiting to carry out.
6. method as claimed in claim 3 is characterized in that, also comprises:
Replace the configuration parameter of said CLI order at the parameter value of the corresponding command parameter that the said employing of completion inquires after, the CLI order that obtains is joined in the CLI command group to be issued;
If the order of the CLI in the said CLI config set does not include configuration parameter, then directly this CLI order is joined in the said CLI command group;
After completion TL1 said to be carried out orders the conversion of CLI order, said CLI command group is issued to corresponding net element.
7. method as claimed in claim 3 is characterized in that, also comprises:
Set up the control of authority file, the territory under the operation that configure user, user allow to carry out and the network element of operation;
Receive said wait to carry out TL1 order after, resolve said control of authority file, to issuing the said user who waits to carry out the TL1 order and saidly waiting to carry out the TL1 order and carry out the legitimacy authentication.
8. method as claimed in claim 7 is characterized in that, also comprises:
In said knowledge base, also store the command format of TL1 order; To issue the said user who waits to carry out the TL1 order and said wait to carry out the TL1 command authorization and pass through after; According to the said command format of waiting to carry out the TL1 order, wait to carry out TL1 order carrying out syntactic analysis to said.
9. method as claimed in claim 8 is characterized in that, also comprises:
In said knowledge base, also store the request frequency threshold value of TL1 order; After the said syntactic analysis of waiting to carry out the TL1 order passed through; The said request frequency of carrying out the TL1 order of waiting is analyzed; Judge that whether the said request frequency of carrying out the TL1 order of waiting exceeds request frequency threshold value, if surpass, then refuses the said TL1 order of waiting to carry out.
10. method as claimed in claim 9 is characterized in that, also comprises:
In said knowledge base, also storing TL1 process of commands mode identifies; When the said request frequency of waiting to carry out the TL1 order does not exceed described request frequency threshold value; Wait to carry out TL1 process of commands mode and identify and judge the said TL1 process of commands mode of waiting to carry out according to said; If processing mode is handled for adopting transparent transmission, then carry out the step of the mapping relations information of said TL1 order of said inquiry and CLI config set; If processing mode is handled for adopting the business logic processing class, then from said knowledge base, read said path of waiting to carry out the business logic processing class of TL1 order, according to this path, carry out corresponding service logical process class.
11. a device of realizing northbound interface comprises: knowledge base and command mapping assembling entity, wherein:
Said knowledge base is used for the mapping relations information of store transaction language 1 (TL1) order and command line interface (CLI) config set;
Said command mapping assembling entity, be used for receive wait to carry out the TL1 order after, the mapping relations information of inquiring about said TL1 order and CLI config set obtains the said corresponding CLI config set of TL1 order of waiting to carry out; Order for the CLI in the said CLI config set; If contain configuration parameter; Then inquire about the said command parameter of waiting carry out TL1 order corresponding with said configuration parameter; The parameter value of the corresponding command parameter that employing inquires is replaced the configuration parameter of said CLI order, accomplishes the conversion that TL1 said to be carried out orders the CLI order.
12. device as claimed in claim 11 is characterized in that:
Said knowledge base also is used to store the mapping relations information of CLI parameter reference and TL1 command parameter;
When said corresponding with said configuration parameter of said command mapping assembling entity inquiry waits to carry out the command parameter that TL1 orders; It is parameter reference according to said configuration parameter; Inquire about the mapping relations information of said CLI parameter reference and TL1 command parameter, obtain the corresponding said command parameter of waiting to carry out the TL1 order of parameter reference of said configuration parameter.
13. device as claimed in claim 12 is characterized in that:
Said command mapping assembling entity also be used for receive said wait to carry out the TL1 order after, preserves said wait to carry out the command parameter that TL1 orders and the mapping relations information of parameter value;
When said command mapping assembling entity adopts the parameter value of the corresponding command parameter that inquires to replace the configuration parameter of said CLI order; Be after corresponding said of the parameter reference that obtains said configuration parameter waits to carry out the command parameter of TL1 order; Inquire about said wait the to carry out command parameter of TL1 order and the mapping relations information of parameter value; Obtain command parameter corresponding parameters value, adopt resulting parameter value to replace the configuration parameter of said CLI order.
14. device as claimed in claim 13 is characterized in that, also comprises authentication entity, wherein:
Said authentication entity is used to set up the control of authority file, the territory under the operation that configure user, user allow to carry out and the network element of operation; Receive said wait to carry out TL1 order after, resolve said control of authority file, to issuing the said user who waits to carry out the TL1 order and saidly waiting to carry out the TL1 order and carry out the legitimacy authentication.
15. device as claimed in claim 14 is characterized in that, also comprises the syntactic analysis entity, wherein:
Said knowledge base also is used to store the command format of TL1 order;
Said authentication entity to issue the said user who waits to carry out the TL1 order and said wait to carry out the TL1 command authorization and pass through after, call said syntactic analysis entity;
Said syntactic analysis entity is used for the command format of waiting to carry out the TL1 order according to said, waits to carry out TL1 order carrying out syntactic analysis to said.
16. device as claimed in claim 15 is characterized in that, also comprises the adaptive entity of request, wherein:
Said knowledge base also is used to store the request frequency threshold value that TL1 orders;
Said syntactic analysis entity calls the adaptive entity of described request after the said syntactic analysis of waiting to carry out the TL1 order is passed through;
The adaptive entity of described request is used for the said request frequency of carrying out the TL1 order of waiting is analyzed, and judges that whether the said request frequency of carrying out the TL1 order of waiting exceeds request frequency threshold value, if surpass, then refuses the said TL1 order of waiting to carry out.
17. device as claimed in claim 16 is characterized in that, also comprises service processing entity, wherein:
Said knowledge base also is used to store TL1 process of commands mode and identifies;
Said command mapping assembling entity; Also be used for when the adaptive entity of described request judges that the said request frequency of waiting to carry out the TL1 order does not exceed described request frequency threshold value; Wait to carry out TL1 process of commands mode and identify and judge the said TL1 process of commands mode of waiting to carry out according to said; If processing mode is handled for adopting transparent transmission, then carry out the mapping relations information of said TL1 order of said inquiry and CLI config set; If processing mode is handled for adopting the business logic processing class, then call said service processing entity;
Said service processing entity is used for reading said path of waiting to carry out the business logic processing class of TL1 order from said knowledge base, according to this path, carries out corresponding service logical process 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 true CN102684894A (en) 2012-09-19
CN102684894B 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)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104503768A (en) * 2015-01-04 2015-04-08 华为技术有限公司 Call method and device for application programming interface (API)
CN106656599A (en) * 2016-12-22 2017-05-10 浙江鹏信信息科技股份有限公司 Method and system for sending network data configuration instruction
CN109274518A (en) * 2018-07-30 2019-01-25 咪咕音乐有限公司 A kind of device management method, device and computer readable 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
CN111723036A (en) * 2019-03-22 2020-09-29 华为技术有限公司 Data processing method, related device and computer storage medium

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

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104503768A (en) * 2015-01-04 2015-04-08 华为技术有限公司 Call method and device for application programming interface (API)
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
CN109274518A (en) * 2018-07-30 2019-01-25 咪咕音乐有限公司 A kind of device management method, device and computer readable storage medium
CN109274518B (en) * 2018-07-30 2021-11-23 咪咕音乐有限公司 Equipment management method and device and computer readable storage medium
CN111723036A (en) * 2019-03-22 2020-09-29 华为技术有限公司 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

Also Published As

Publication number Publication date
WO2012119340A1 (en) 2012-09-13
CN102684894B (en) 2014-12-10

Similar Documents

Publication Publication Date Title
EP3700132B1 (en) Supporting compilation and extensibility on unified graph-based intent models
US11689419B2 (en) Supporting concurrency for graph-based high level configuration models
CN110958131B (en) GraphQL-based queries supported on a YANG configuration data model
EP3722944A1 (en) Intent-based, network-aware network device software-upgrade scheduling
CN102171993B (en) Linkage strategy implementation method and apparatus, open platform veneer and device
EP1782215B1 (en) A generic framework for deploying ems provisioning services
CN102684894B (en) Method and device for realizing northboundbound interface
CN102571420A (en) Method and system for network element data management
US20130326050A1 (en) Method of Organic Cloud Discovery and Transformation of Network Assets
US20230308348A1 (en) Server to support client data models from heterogeneous data sources
Costa et al. Enhancing orchestration and infrastructure programmability in SDN with notoriety
JPWO2006051599A1 (en) Resource management program, resource management method, and resource management apparatus
Hemid Facilitation of The OpenDaylight Architecture
van der Meer et al. Ubiquitous Smart Space Management
Stamatelatos et al. Information model for managing autonomic functions in future networks
KR102590288B1 (en) Method and system for performing security management automation in cloud-based security services
Lyu Literature review on standards for data structuring in physical layer of optical network.
Ismaili et al. Web services research challenges, limitations and opportunities
Li et al. Design of General SDN Controller System Framework for Multi-domain Heterogeneous Networks
Khosravi Deployment of SDN Controller and configuring Juniper devices using NETCONF
Yang et al. Towards next generation internet management: CNGI-CERNET2 experiences
Pras et al. What Can Web Services Bring To Integrated Management?
Lin et al. Research on information models and modelling methods of the new generation of OSS for data management
Vasudevan et al. Malleable services
KR20090012554A (en) Scalable grid resource management based on wbem with upnp resource discovery

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